Use consistent "camel case" for field names #34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alanorth
force-pushed
the
camel-case
branch
2 times, most recently
from
e936dec to
7c2d363
Compare
This changes several metadata field names to follow a consistent "camel case" format used in Dublin Core and elsewhere in CG Core: - cg.peer-reviewed → cg.peerReviewed - cg.howpublished → cg.howPublished - cg.booktitle → cg.bookTitle - cg.HasMetadata → cg.hasMetadata
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes several metadata field names to follow a consistent "camel case" format used in Dublin Core and elsewhere in CG Core:
Closes #31