museum voucher lookup service for basic sample/ event data

[mkoo]

I am getting alarmed by bad data reported for museum records. If a sample is being added to a project and it already is vouchered elsewhere (eg. a museum collection with access to gbif or idigbio) ideally we would be able to allow the user to reference the GUID, permit a lookup service to fetch the data from one of these repos and provide the basic sample and event fields we need. Then user only has to supply the diagnostic data.

Added bells to the geome record: add link to the collection portal (gbif or idigbio) based on GUID

let's discuss this possibility and how it fits either in geome or amphibian disease portal

[jdeck88]

i think the best spot for external references would be under occurrenceID So, publish either the link to arctos landing page (e.g. using DwC triplet) or GBIF landing page. This would be a URI and would show up on specimen record landing page.

John

On Tue, Dec 8, 2020 at 5:06 PM Michelle Koo notifications@github.com wrote:

I am getting alarmed by bad data reported for museum records. If a sample is being added to a project and it already is vouchered elsewhere (eg. a museum collection with access to gbif or idigbio) ideally we would be able to allow the user to reference the GUID, permit a lookup service to fetch the data from one of these repos and provide the basic sample and event fields we need. Then user only has to supply the diagnostic data.

Added bells to the geome record: add link to the collection portal (gbif or idigbio) based on GUID

let's discuss this possibility and how it fits either in geome or amphibian disease portal

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/BNHM/AmphibiaWebDiseasePortal/issues/107, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIZ3RN2ESVZRYXBR7IUNNDST3ERNANCNFSM4USYHYUQ .

-- John Deck (541) 914-4739

[mkoo]

we can do that-- include a URI in occurrenceID, but that alone doesnt address the core issue-- we need to increase data quality by reducing the burden on users reporting museum voucher data. I think this may be a standalone tool perhaps? I wonder how Futres and other teams are handling the additional info on pre-existing cataloged records

[mkoo]

Update from conversation with @jdeck88 and looking at GBIF API for occurenceID -- one scenario could be to offer a "museum catalog records checking" service prior to uploading data to Geome (as it does with validation only option), where values in institutionID, collectioncode, catalogNumber fields are used to search gbif api and checks for matching values in decLat, decLong, uncerntainty in meters, country, locality, collecting dates, etc or errors and returns Gbif values if they do not match. Users can then use that to populate their xlsx template.

need to investigate the correct api call. need to consider if this is done instead or in addition to loading to the Amphibiandisease API has applications beyond the ADP Team too!