MMM: SESAR logistics which need discussion

[ramdeensarah]

1. We should discuss which fields can be edited. For example, current_archive can be edited but if you map a field to original_archive, you can not edit the entry.
2. The list of possible fields for mapping is incomplete, we noticed some SESAR fields were missing. We were uncertain if this was intentional. If not, we should review what missing fields should be added (if there is a reason to not include all).
3. To add an optional field, there are only two SESAR fields listed as opposed to the complete list of supported SESAR fields. Is this intentional? We might need to discuss which options should be included.
4. We noticed that the names used in the SESAR mapping fields are our database names and not the customer facing names. This is a minor issue that we may be able to address in the documentation (it is also an issue in SESAR where we need to be consistent).

[bowring]

This should be 4 issues, but

1. This feature was added to help Scripps, but in general is a bad idea - the data should be uneditable.
2. This is intentional as we only had Scripps as a source and the SESAR list was unrelated for the most part. We should come up with a "likely" list to avoid ungainly choices.
3. These fields are metadata fields - i.e. they are true for all samples but not included in the data files. Further discussions warranted.
4. These are the database names by design - we are creating field maps to aid in uploading to a database - the customer looks at SESAR and gets the translation there.