Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need direct access to WoS & PubMed to meet the data coverage & quality dashboard requirements? #122

Open
jacobthill opened this issue Jan 29, 2025 · 3 comments
Assignees

Comments

@jacobthill
Copy link
Contributor

jacobthill commented Jan 29, 2025

https://docs.google.com/document/d/1y_Ua_6vfg3Ny1jRJlGsgeE5cVVpEZQWY8OcLVWar0i0/edit?tab=t.0#heading=h.ueu5im3rmyvm

What data does PubMed and WoS have that SUL-Pub is not harvesting?

  • PubMed offers full text for some OA publications.

Does SUL-Pub validate publication coverage? e.g. if the same publication (same doi) is available in PubMed and WoS, will the publication data exported from SUL-Pub reflect this?

  • There is a provenance column but it is unclear to me how the source is chosen? Is it whichever gets harvested first or does one API have priority when available?
@jacobthill jacobthill self-assigned this Jan 29, 2025
@peetucket
Copy link
Member

We do not expect new publications from direct connections since sul-pub already queries WoS and Pubmed by ORCID.

So the question is: is the metadata we have from sul-pub sufficient to provide data coverage without having to go directly to APIs?

@peetucket
Copy link
Member

sul-pub doesn't indicate which query was used to find a publication (e.g. by name vs by orcid)

if we only search OpenAlex and Dimensions by ORCID, to compare equally across all sources, we'd need to run the same type of query against WoS

@peetucket
Copy link
Member

Leaning towards adding WoS and Pubmed as additional connections via direct calls to API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants