Matt

Forgot about the definition. Good point. Therefor, new workflow: curator must have Predicates created *before* import. Errors raised if not detected. This should allow us to more concisely reference the...

@LocoDelAssembly this becomes a priority for us, it's basically the last thing we need to "unlock" Brian's data. Note slightly similarities to #1773. In this case there is no existing...

Spaces technicaly won't matter in that we will ignore everything before the ':', but yes, best practices should exclude them.

They can currently find it through the data card for that predicate. New issue though- show it prominently in the Manage task.

Thanks for clarifying. Your representation is fine, though maybe we could refine the term to simplify it. Thought- could the importer find the label from the Predicate itself, and use...

@LocoDelAssembly was thinking- perhaps we need 2 (maybe more ultimately) specific DwC extensions). TaxonWorks could define behaviour based on the extension type (which I assume can be encoded in the...

@LocoDelAssembly Can you say a little more about that example? The column headers, that are not column headers, are supposed to be in the file in that way for processing...

>I don't think we going to ever be able to support this on a proper extension as it should exist beforehand and requires a fixed set of terms, Thanks for...

> dwc-archive also supports mapping right into meta.xml, but again will be flagged as unknown terms in GBIF's validator (like with ITIS's superfamily). This feels like the right approach? What's...

Feels like this is outdated given what we have implemented, can we close? @LocoDelAssembly @debpaul