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

Metadata fields cg.reviewStatus to become mandatory for journal articles #44

Open
valentina-dc opened this issue Feb 6, 2023 · 1 comment
Labels
question Further information is requested

Comments

@valentina-dc
Copy link

Dear @alanorth and @ayabowork

Given that CGSpace submitters are sometimes inconsistent in using the cg.reviewStatus metadata tag, would it be possible to add it as a mandatory field in CGSpace - at least for journal articles?

This will help in the future the Quality Assurance process since when cg.reviewStatus is not in the metadata, PRMS will show the item automatically as non-peer-reviewed.

Thank you.

@valentina-dc valentina-dc changed the title Metadata filed cg.reviewStatus to become mandatory for journal articles Metadata fields cg.reviewStatus to become mandatory for journal articles Feb 6, 2023
@alanorth alanorth added the question Further information is requested label Feb 6, 2023
@alanorth
Copy link
Collaborator

alanorth commented Feb 6, 2023

Not all journal articles are peer reviewed, and some are peer reviewed but to low standards (predatory journals). The CGSpace submission form does have some guidance asking whether the item was internally or peer reviewed, but it is optional:

Screenshot from CGSpace submission form

This problem cannot be solved automatically—we need to increase awareness among the submitters. I think for the PRMS reporting period it was just too chaotic, so I don't fault the submitters for making mistakes.

On that note, we do need to prepare a sort of "best practices" guide, do more trainings, and have an in-person meeting of all the library people (:wink:) to create a sense of belonging.

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

No branches or pull requests

2 participants