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
The DCTERMS schema makes use of "camel case" for metadata field names that contain multiple words, for example bibliographicCitation and accessRights. I know it's a bit arbitrary and doesn't actually matter, but we already do this for some of our own fields and we should at least be consistent.
I propose that we adjust the following fields in CG Core v2 to follow the convention:
cg.peer-reviewed → cg.peerReviewed
cg.howpublished → cg.howPublished
cg.booktitle → cg.bookTitle
I think that's all of them...
The text was updated successfully, but these errors were encountered:
that's a good point, thanks.
Since we are going to need a new minor version of the schema (2.1 or something), we can add all minor changes at that time
OK that is great. So we move this to CG Core v2.1. I will create a GitHub "milestone" for that and tag it here.
BTW I added a CHANGELOG.md and we can add this type of thing there as well. Much easier to see major changes that way instead of looking in issues and git commit history.
alanorth
added a commit
to alanorth/cgspace-notes
that referenced
this issue
Jan 18, 2021
The DCTERMS schema makes use of "camel case" for metadata field names that contain multiple words, for example
bibliographicCitation
andaccessRights
. I know it's a bit arbitrary and doesn't actually matter, but we already do this for some of our own fields and we should at least be consistent.I propose that we adjust the following fields in CG Core v2 to follow the convention:
cg.peer-reviewed
→cg.peerReviewed
cg.howpublished
→cg.howPublished
cg.booktitle
→cg.bookTitle
I think that's all of them...
The text was updated successfully, but these errors were encountered: