Open pdfeeney opened 5 years ago
Looking at http://api.crossref.org/works/10.5555/suffixtest
The relevant part of the XML says:
<content_item component_type="other">
<titles><title>test item</title></titles>
<doi_data>
<doi>10.5555/suffixtest</doi>
<resource>http://www.crossref.org/afds</resource>
</doi_data>
</content_item>
So I think it's reasonable that Cayenne thinks that the content type is other
:
"type": "other"
The Query result also includes this item outside of the query record:
<doi type="book_content">10.5555/suffixtest</doi>
This appears not to be part of the members-supplied metadata.
We can make the change to Cayenne, if appropriate, once we've documented the route that this data takes.
However, the tag that contains the @type (with value 'other') is
Generally when we speak of content type, we are referring to the major divisions in the schema (journal, book,conf/proc,dissertation,standard, database.. etc).
We have 'other' as a type, but it includes both book and book child (chapter, usually). Other book / book child types are split out individually, these should be separated into separate types.
For example - this is registered as a book with book_type 'other': http://api.crossref.org/works/10.5555/suffixtest
This is registered as a content_item (child of 'book') with component_type 'other' and also has type 'other' in the JSON:
http://api.crossref.org/works/10.4337/9781781001639.00001