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

RFC: isbns and dois in Literature schema #1349

Closed
mihaibivol opened this issue Jul 19, 2016 · 11 comments
Closed

RFC: isbns and dois in Literature schema #1349

mihaibivol opened this issue Jul 19, 2016 · 11 comments
Assignees

Comments

@mihaibivol
Copy link
Contributor

Currently we have these arrays inside the schema:

  • dois
  • isbns
  • publication_info

publication_info also has an isbn field. I think it might be better to move everything that is publication related within publication_info. If we have only an ISBN then the publication info will contain only the ISBN information.

@kaplun
Copy link
Contributor

kaplun commented Jul 20, 2016

The only issue I have is that ISBNs in publication info mean that the given document is a chapter inside a the referred book. Instead when the ISBN is in its own field it means that this record is about the book itself. At that point we should also have the imprint information (i.e. place, editor and year).

At the same time we have the concept of being part of which currently doesn't seem to be part of the hep.json schema. There is however a MARC tag for that: 78708 i.e. related record.

@kaplun
Copy link
Contributor

kaplun commented Jul 20, 2016

@annetteholtkamp what is the actual way we relate a book chapter to its book?

@annetteholtkamp
Copy link

773__0 contains the recid of the book. Usually the 773 field for a book chapter contains just
773__0 and 773__c (page range).
But it may also be 773__i (for ISBN) and 773__c.

One could also imagine using the DOI of the book to refer to it. In principle it would be great if many identifiers are allowed to save cataloguers the work of looking up the recid.

We also have links via report number. E.g..
773__r may refer to a CERN yellow report

  • Annette

On Jul 20, 2016, at 9:55 AM, Samuele Kaplun <notifications@github.commailto:notifications@github.com> wrote:

@annetteholtkamphttps://github.com/annetteholtkamp what is the actual way we relate a book chapter to its book?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com//issues/1349#issuecomment-233872772, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AM1-O9DTK2hckGO87oVAGZSr7CDAS2sQks5qXdSKgaJpZM4JPoVR.

@david-caro
Copy link
Contributor

@kaplun if you are not working on this, move back to ready and unassign 👍

@kaplun kaplun removed their assignment May 11, 2017
@david-caro david-caro self-assigned this May 11, 2017
@kaplun
Copy link
Contributor

kaplun commented May 11, 2017

You are going to work on it?

@david-caro
Copy link
Contributor

Are you asking or assigning? ;), but in any case, move to ready then, if you want me to work on it assign it to me too.

@kaplun
Copy link
Contributor

kaplun commented May 11, 2017

You self assign-it :P

@jacquerie
Copy link
Contributor

This looks like a content decision. I think that @michamos should look at it and decide.

@michamos
Copy link
Contributor

I am not sure I understand the issue. In publication_info, parent_isbn, parent_record and parent_record_number are defined. Maybe we also need parent_doi which is not currently defined?

@annetteholtkamp ?

@annetteholtkamp
Copy link

annetteholtkamp commented Jun 5, 2017 via email

@jacquerie
Copy link
Contributor

This issue was moved to inspirehep/inspire-schemas#210

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

No branches or pull requests

6 participants