Open alanorth opened 4 years ago
Suggest we follow other DCTERMS examples and use camel case: cg.reviewStatus
. What do you think, @marieALaporte?
I think this is better.
sounds good to me
@marieALaporte CGSpace currently uses the following values:
Also, I thought it might be better to follow naming convention of other DCTERMS / CG Core fields and use camel case: cg.reviewStatus
. What do you think?
Look at Nature review list for controlled terms
@marieALaporte Where is that? I searched Google for "Nature review list" but couldn't find anything relevant. Thanks!
Ryan mentioned yesterday during the meeting the recent Nature transparent peer review system (https://www.nature.com/documents/nature-transparent-peer-review.pdf) The change described in the issue were well accepted, by the group seen as an improvement. We were looking at possible externally maintained controlled list of terms that could be used for this. If if don't find any, we will publish our own, with our definitions of the terms. I was not able to find any list from Nature so far, but looked only quickly
I updated the pull request in #23 to change cg.peer-reviewed
to cg.reviewStatus
, which incorporates the comments here.
@marieALaporte should we add this to the v2.1 release also? Changing cg.peer-reviewed
to cg.reviewStatus
.
I think so, yes.
The current draft CG Core v2 schema recommends using
cg.peer-reviewed
with a boolean value "True" to indicate that a resource has been peer reviewed. CGSpace uses a non-standard Dublin Core field (dc.description.version
) for this, with values such as "Peer Review" and "Internal Review". We refer to this field as "Review status" in our item submission and display user interfaces.What do you think about expanding the scope of
cg.peer-reviewed
to include other types of review, and perhaps renaming the field to something more general likecg.review-status
?Cheers!