Support multiple table formats and aggregations

[grantfitzsimmons]

Is your feature request related to a problem? Please describe.
At this time, you can only add each table format or aggregation one time. The big issue

Describe the solution you'd like

• An (aggregated) or (formatted) table relationship should be able to be added more than once
• Each (aggregated) or (formatted) query field should enable the user to select a distinct table format / aggregation
• Each line in the query should be mappable in an export definition to a different DwC term

Describe alternatives you've considered
Post-processing data is currently necessary to achieve what multiple table formats can provide for presenting data in query exports and during data publishing. This approach is neither sustainable nor automated within the software.

Reported By
Our team, Nate Shoobs at Ohio Mollusks on the Speciforum, and many others

3. Our taxon table uses the WoRMS AphiaID to match taxa to WoRMS. In the DWC export, in order to conform to the dwc:taxonID and dwc:acceptedNameUsageID terms, the AphiaID should be exported with its LSID prefix (urn:lsid:marinespecies.org:taxname:), but I don’t record that prefix in the field because the WoRMS API / URL stems often use the aphiaID by itself. Is there a way I can format the AphiaID with a static text prefix that doesn’t use the taxon table formatter? Since I can only put one formatted record per table in a query, I can’t use it for both fields, and I am actually already using it for another dwc field.

[specifysoftware]

This issue has been mentioned on Specify Community Forum. There might be relevant details there:

https://discourse.specifysoftware.org/t/dwca-questions/2385/9

[grantfitzsimmons]

This was requested by CSIRO Specify Support via BoldDesk:

We have just been testing the latest release (v.7.11.2.1) and are very happy that we can now create multiple aggregator formats for a table and select different ones in a query. However it would be very useful to be able to select different aggregators for the same table in one query. An example for our Herbarium would be that we have collectors flagged as "primary" or "secondary", and it would be good to have a query with two columns separating them out - one with a list of primary and one with a list of secondary.