Closed mihaibivol closed 7 years ago
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.
@annetteholtkamp what is the actual way we relate a book chapter to its book?
7730 contains the recid of the book. Usually the 773 field for a book chapter contains just 7730 and 773c (page range). But it may also be 773i (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
On Jul 20, 2016, at 9:55 AM, Samuele Kaplun notifications@github.com<mailto: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/inspirehep/inspire-next/issues/1349#issuecomment-233872772, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AM1-O9DTK2hckGO87oVAGZSr7CDAS2sQks5qXdSKgaJpZM4JPoVR.
@kaplun if you are not working on this, move back to ready and unassign :+1:
You are going to work on it?
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.
You self assign-it :P
This looks like a content decision. I think that @michamos should look at it and decide.
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 ?
That's a nice idea. The issue probably never came up before. But more and more books have a DOI, e.g. Springer books and proceedings. So it would be very useful if we can refer to a parent via its DOI.
On May 11, 2017, at 4:52 PM, Micha Moskovic notifications@github.com<mailto:notifications@github.com> wrote:
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?
@annetteholtkamphttps://github.com/annetteholtkamp ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/inspirehep/inspire-next/issues/1349#issuecomment-300814139, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AM1-O8XgQZh6rxcB2vnsxlmxdVdGJndgks5r4yCvgaJpZM4JPoVR.
This issue was moved to inspirehep/inspire-schemas#210
Currently we have these arrays inside the schema:
dois
isbns
publication_info
publication_info
also has anisbn
field. I think it might be better to move everything that is publication related withinpublication_info
. If we have only an ISBN then the publication info will contain only the ISBN information.