Come up with a predictable ordering for aggregate fields

[dannymandel]

For the aggregate fields (e.g. description), we should have some kind of ordering for how they appear. Right now, it feels a bit haphazard, and downstream consumers of our API will appreciate having them appear in the same order.

[smrgeoinfo]

@dannymandel - can you give me some examples?

[dannymandel]

Here are a few Smithsonian examples from unit tests:

'description': 'basisOfRecord: MaterialSample | occurrenceRemarks: Specimen '
                "voucher located at Museum National d'Histoire Naturelle, "
                'Paris. | catalogNumber: 439549.12401721 | recordNumber: '
                'mbio324 | fieldNumber: Moorea F-06-05 | type: PhysicalObject '
                '| individualCount: 1 | disposition: in collection | '
                'startDayOfYear: 71 | endDayOfYear: 71',

'description': 'basisOfRecord: MaterialSample | catalogNumber: '
                '1452351.13337038 | recordNumber: XMOO_0121 | fieldNumber: '
                'MBIO/080605_minv_006 | type: PhysicalObject | '
                'individualCount: 1 | disposition: in collection | '
                'associatedMedia: 15114501 | startDayOfYear: 157 | '
                'endDayOfYear: 157',

'description': 'basisOfRecord: MaterialSample | catalogNumber: '
                '1475352.15797427 | recordNumber: JC754 | type: PhysicalObject '
                '| individualCount: 1 | sex: male | lifeStage: II | '
                'disposition: in collection'

'description': 'basisOfRecord: MaterialSample | catalogNumber: '
                '406026.14643823 | recordNumber: CUR11026 | fieldNumber: '
                'CUR11-04 | type: PhysicalObject | individualCount: 1 | '
                'disposition: in collection | startDayOfYear: 141 | '
                'endDayOfYear: 141',

'description': 'basisOfRecord: MaterialSample | catalogNumber: '
                '1428583.12896321 | recordNumber: BMOO-07287 | fieldNumber: '
                'MBIO/BIZ-064 | type: PhysicalObject | individualCount: 1 | '
                'disposition: in collection | startDayOfYear: 302 | '
                'endDayOfYear: 302',

[dannymandel]

Notes from iSamples tech call 7/30/21:

• Maintain the String format with pipe delimiters
• For Smithsonian records, eliminate startDayOfYear, endDayOfYear, basisOfRecord, disposition, and anything that is just a number
• We need a consistent set of guidelines across partners that should guide what we put in this field
• For the advanced schema, these might move to new fields in formatted key/value pairs, but this simple approach is good for the simple schema and first prototype
• For now, we are ok leaving these unordered