Extend FileMatcher to set id and acceptedName (acceptedNameUsage) columns in the config

[gaurav]

That would be sweet.

[gaurav]

Bear in mind that -- according to the spec at http://darwincore.googlecode.com/svn/trunk/terms/index.htm#acceptedNameUsageID -- this may be a globally unique ID. We could provide acceptedNameUsageID, and then look up acceptedName by taxonID if available in the same database. We definitely should not do this across multiple databases since we can't tell if http://darwincore.googlecode.com/svn/trunk/terms/index.htm#taxonID is globally unique or not.

[tucotuco]

This particular issue is not a priority for VertNet, as we have no NameUsageIDs in use anywhere in the network.

[gaurav]

Do you need accepted names at all? Or should BT just focus on matching names to checklists for now?

[tucotuco]

Well, what we expect back, given a submitted name, is an accepted name, no?

[gaurav]

Right now, we return the queried name, scientificName and the "acceptedName" (which I should really replace with http://terms.tdwg.org/wiki/dwc:acceptedNameUsage). However, if it's a checklist like ITIS, which uses acceptedNameUsageIDs instead of acceptedNameUsage, we can't figure out the accepted name. Is that okay for now?

[tucotuco]

It is OK for now, but without name resolution to a name, ITIS will be of
less utility.

On Mon, Dec 1, 2014 at 11:41 PM, Gaurav Vaidya [email protected]
wrote:

Right now, we return the queried name, scientificName and the
"acceptedName" (which I should really replace with
http://terms.tdwg.org/wiki/dwc:acceptedNameUsage). However, if it's a
checklist like ITIS, which uses acceptedNameUsageIDs instead of
acceptedNameUsage, we can't figure out the accepted name. Is that okay for
now?

—
Reply to this email directly or view it on GitHub
#1 (comment).