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

Upon import, run the DOI verification process on each new publication #1036

Closed
anaelizabethenriquez opened this issue Dec 5, 2024 · 2 comments · Fixed by #1060
Closed

Upon import, run the DOI verification process on each new publication #1036

anaelizabethenriquez opened this issue Dec 5, 2024 · 2 comments · Fixed by #1060

Comments

@anaelizabethenriquez
Copy link
Collaborator

anaelizabethenriquez commented Dec 5, 2024

When a new publication is imported from Activity Insight or from Pure, we should run the DOI verification process. Right now, that process only runs on publications that are in the Activity Insight OA Workflow.

(We also fill in DOIs during the OAB and Unpaywall imports. Those DOIs that get filled in get marked as verified. However, that process doesn't verify the DOIs that are already present.)

Why: Running this on all new publications will likely mean that it fills in DOIs for a lot of additional publications. This will improve the application in quite a few ways, including by reducing the number of unnecessary/"false negative" reminder emails. It will also help with #973 and with deduplication generally. Talking to Eric about that issue is why I'm writing up this one. Update: Actually, seems like the main benefit of this would be that it corrects DOIs that are present but do not match the rest of the metadata.

Related: #1037

@ajkiessl
Copy link
Contributor

Let's also do a DOI verification on Law School imports

@anaelizabethenriquez
Copy link
Collaborator Author

@jlandiseigsti Another thing I should have mentioned in the description for this issue is that publications with the type "Extension Publication" should not ever go through DOI verification. (Related to #962 )

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

Successfully merging a pull request may close this issue.

4 participants