Difference between revisions of "HAMR: Human/Authority Metadata Reconciliation"
From Code4Lib
Line 14: | Line 14: | ||
* pubmed - Sample pubmed query (in Java): [https://wiki.duraspace.org/display/DSPACE/PubMedPrefill-PubmedPrefillStep.java DSpace PubMedPrefill] (From [https://wiki.duraspace.org/display/DSPACE/PopulateMetadataFromPubMed Populate Metadata from PubMed]) | * pubmed - Sample pubmed query (in Java): [https://wiki.duraspace.org/display/DSPACE/PubMedPrefill-PubmedPrefillStep.java DSpace PubMedPrefill] (From [https://wiki.duraspace.org/display/DSPACE/PopulateMetadataFromPubMed Populate Metadata from PubMed]) | ||
* crossref | * crossref | ||
+ | ** simply send the DOI to crossref, and get JSON back | ||
** example: http://api.labs.crossref.org/10.1111/j.1558-5646.2009.00626.x.json | ** example: http://api.labs.crossref.org/10.1111/j.1558-5646.2009.00626.x.json | ||
* google scholar - does it have an API? | * google scholar - does it have an API? |
Revision as of 15:48, 7 February 2011
HAMR: Human/Authority Metadata Reconciliation
Sean Chen, Tim Donohue, Joshua Gomez, Ranti Junus, Ryan Scherle
A tool for a curator to determine whether the various fields of a metadata record are correct. Takes a metadata record, locates any identifiers (e.g., DOI, PMID). Retrieves a copy of the metadata record from an authoritative source (e.g., CrossRef, PubMed). Displays a human-readable page that compares fields in the initial record with fields in the authoritative record. Each field is color-coded based on how well it matches, so the curator can quickly identify discrepancies.
Focus:
- Dublin core (maybe qualified)
- framework that allows multiple authority sources
- NOT focusing on author names (ORCID is already working on this), except the fact that they are strings, and we'll do basic string matching
Possible authority sources:
- pubmed - Sample pubmed query (in Java): DSpace PubMedPrefill (From Populate Metadata from PubMed)
- crossref
- simply send the DOI to crossref, and get JSON back
- example: http://api.labs.crossref.org/10.1111/j.1558-5646.2009.00626.x.json
- google scholar - does it have an API?
- mendeley - Mendeley API
- vivo
- bibapp