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

hep: Insertion of fields $schema and control_number in hep.json. #30

Closed
wants to merge 3 commits into from

Conversation

zzacharo
Copy link
Contributor

  • Insertion of the $schema and control_number fields in the hep schema
    as it is required for using invenio-records-rest PUT request upon updating
    a single record.

Signed-off-by: Zacharias Zacharodimos zacharias.zacharodimos@cern.ch

@@ -254,6 +258,9 @@
"type": "array",
"uniqueItems": true
},
"control_number": {
"type": "string"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be number. Zenodo also uses a field to store this old Invenio identifiers and defined them as numbers - https://github.com/zenodo/zenodo/blob/master/zenodo/modules/records/jsonschemas/records/record-v1.0.0.json

@jmartinm
Copy link
Contributor

Apart from the comment, LGTM.

 * Insertion of the `$schema` and `control_number` fields in the hep schema
   as it is required for using invenio-records-rest PUT request upon updating
   a single record.

Signed-off-by: Zacharias Zacharodimos <zacharias.zacharodimos@cern.ch>
 * Insertion of the `$schema` and `control_number` fields in the hep schema
   as it is required for using invenio-records-rest PUT request upon updating
   a single record.

Signed-off-by: Zacharias Zacharodimos <zacharias.zacharodimos@cern.ch>
@zzacharo zzacharo closed this Nov 3, 2016
@zzacharo zzacharo deleted the hep_schema_modification branch November 3, 2016 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants