Closed opoudjis closed 1 year ago
So, you've applied the solution of https://github.com/relaton/relaton-doi/issues/9 to https://github.com/relaton/relaton-doi/issues/8. But https://github.com/relaton/relaton-doi/issues/9 applies to inbook, inproceedings, incollection; it does NOT apply to articles. So you currently have done:
<relation type="includedIn">
<bibitem>
<title format="text/plain">D-Lib Magazine</title>
</bibitem>
</relation>
but we do still require, instead,
<series>
<title>D-Lib Magazine</title> # container-title
</series>
<extent>
<localityStack>
<locality type="volume"><referenceFrom>16</referenceFrom></locality> # volume
<locality type="issue"><referenceFrom>11/12</referenceFrom></locality> # issue
<locality type="page"> # NOT supplied in this reference!
<referenceFrom>...</referenceFrom>
<referenceTo>...</referenceTo>
</locality>
</localityStack>
</extent>
We would also require the extent in https://github.com/relaton/relaton-doi/issues/9
The extent is now there. The relation/[@type = 'includedIn']
still needs to go away for articles. (Strictly speaking it is harmless, but it is currently a time-consuming lookup. But hold on this until I confirm that we don't need disambiguation.)
While we're at it, could we really migrate away from the awkward names inherited from BibTeX, e.g. "inbook", "inproceedings", etc. to a proper consistent pattern that we use for all the other relationship names?
doi:10.1045/november2010-massart fetches successfully, but is missing journal information:
This is derived from JSON:
This is missing the following necessary information for any journal article:
It is very important that, for any entry in DOI that has volume, issue, or page, that those extents should be extracted.
The container-title must also be extracted for article, inproceedings, inbook. For inproceedings, inbook it is the host title:
/bibitem/relation[@type = 'includedIn']/bibitem/title
.