Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAbstractNote import issue with RDF.js and Embedded Metadata.js #2164
Comments
I'm not sure this is a "bug" in the common sense of the word. As you note, the RDF translator is explicitly written to prefer Having looked at this briefly, it looks to me that the reason for this is terribly convoluted, related to the use of dc.description in the Zotero RDF format (for the extra field). This will require a more thorough dive than I'll be able to do in the coming months, I'm afraid, but I'll leave this ticket open for reference. I don't think the current behavior is correct -- I'd be surprised if dc: metadata isn't almost always better than og. |
vancleve commentedApr 19, 2020
•
edited
Running the
Embedded Metadata.js
translator onhttps://www.nature.com/articles/ncomms14906
returns
which is not the Abstract, but rather the content of
og:description
.From here,
translators/RDF.js
Line 1199 in 5a8e310
it looks like the Facebook OpenGraph (
og:description
) description element takes precedence overdescription
:translators/RDF.js
Line 1301 in 5a8e310
From the debug in
Embedded Metadata.js
, it looks like the RDF is being constructed with the correct abstract as:So, is this a "bug" that should be fixed in
RDF.js
orEmbedded Metadata.js
or inNature Publishing Group.js
?