#1. unfortunately I am already using the CE table formatter in order to display CE numbers in the proper format in exports.
#2. Thanks for the Audobon core extension recommendation and xml example. This solves this particular problem!
#3. This is the same problem as #1, since I use one formatted field already, I can’t have it occur more than once. It is true that you can define multiple formatters and select which one you want to use in query exports, but you can only do it one time per table per query, as far as I can tell.
#4. Could use use the audit log table to get at the modified date field?
I don’t think there’s any single audit log field that would work in the way that the dwc:modified term implies. But I could be wrong! I guess I could just leave the term out of the export.
#6. Not sure you would want to publish all collections as a single resource as there would be information specific to the collection as well as individual collection codes (I would assume) that you would want to preserve for each collection.
Since the query includes collectioncode and I map occurrenceID to a formatted field that includes the collectioncode as part of a GUID, I don’t see a reason why I shouldn’t export them as one DwCA. I have our bivalve, gastropod, and crustacean data stored in separate Specify collections principally because they use separate catalog numbering schemes (i.e. OSUM 1234 refers to a bivalve lot, a gastropod lot, and a crayfish lot that are entirely unrelated to one another). Many other institutions, USNM for example, have duplicate catNos for different phyla, but export combined occurrence datasets to GBIF. I don’t feel too strongly about this, it’s not a huge deal if this is not possible.