iobis / non-matching-names

Workflow to build non matching names list
2 stars 2 forks source link

publishing non-matching names as verbatim? #9

Open claudenozeres opened 2 years ago

claudenozeres commented 2 years ago

Hello, I notice the non-matching names fall under 'scientific name', even for non-taxonomic terms like 'egg'. Could it be recommended to use the DarwinCore terms of verbatimIdentification or verbatimScientificName, and are these available when publishing data to an OBIS IPT?

pieterprovoost commented 2 years ago

@claudenozeres Yes, of course those values should not be in scientificName, and depending on the case verbatimIdentification and/or lifeStage would be appropriate. But this code is only about validating scientificName as this is the field we use for taxon matching with WoRMS. Note that verbatimScientificName is not a Darwin Core term, although GBIF adds this field to store the scientific name as provided to GBIF. In OBIS this is called originalScientificName but it would make sense to rename this.

pieterprovoost commented 2 years ago

Reading your question again I realize this may be about the presentation of the non matching names list. I'm not sure we should change this, as verbatimScientificName is not a Darwin Core term anyway.

Regarding publishing, all terms in the current core and extension definitions can be used to publish to OBIS.

claudenozeres commented 2 years ago

Thanks @pieterprovoost. I was intially asking about these name fields because we discovered while mapping our data in OBIS Canada IPT that the Darwin Core term of verbatimIdentification is not available. So I was looking for alternatives, and came here to get clues, and thought it may be a potential issues in published names that could be raised (terms showing up in scientificName because people do not know or have alternatives). Our IPT also does not does not seem to have originalScientificName, nor verbatimScientificName.

pieterprovoost commented 2 years ago

To be able to map to verbatimIdentification, it should suffice to synchronize the core defintions in your IPT from the Administration panel. The other two fields will not be available as these are not part of any core or extension definitions.