You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Querying researchers by name is problematic because of all of the false positives. Querying by ORCID iD returns no false positives (in theory) but it misses some publications. In short, there is a precision-recall trade off between these two querying strategies. As ORCID adoption increases, and data providers improve their metadata, querying by ORCID iD will replace the need to query by name strings. We need an experiment (in a jupyter notebook) that can be re-run periodically to see the current state of querying by ORCID iD.
Export a sample of SUL-Pub authors who have reviewed all of their publications AND gone through the ORCID integration.
Export all publications from SUL-Pub for these authors.
Query Dimensions, OpenAlex, PubMed, and WoS by ORCID id for these authors.
Compare publications sets with and without the WoS publications.
The results will help us understand the following questions:
Does querying by ORCID iD alone return sufficiently complete results to move away from name querying?
Does querying Dimensions, OpenAlex, and PubMed return sufficiently complete results to end our expensive WoS subscription?
The text was updated successfully, but these errors were encountered:
Querying researchers by name is problematic because of all of the false positives. Querying by ORCID iD returns no false positives (in theory) but it misses some publications. In short, there is a precision-recall trade off between these two querying strategies. As ORCID adoption increases, and data providers improve their metadata, querying by ORCID iD will replace the need to query by name strings. We need an experiment (in a jupyter notebook) that can be re-run periodically to see the current state of querying by ORCID iD.
The results will help us understand the following questions:
The text was updated successfully, but these errors were encountered: