Zotero not pulling in a few Highwire fields for PubPub

gabestein
Hello,

I'm the Head of Product for PubPub (https://pubpub.org), an open-source academic publishing platform. I'm writing in because we're trying to implement citation meta tags (we have both dc and google/highwire), and we're struggling to get Zotero to recognize a few tags.

In particular, Zotero does not seem to be parsing citation_journal_title, whereas other sources like Scholar and Mendeley do.

Here's an example article where we're seeing the issue: https://hdsr.mitpress.mit.edu/pub/hx3pgxjc

I'm wondering if this is an issue with having both dc and highwire tags on the page, or something else we can address? We're planning to add more Highwire/Scholar tags (volume, issue, published at, etc.), but before we do I want to make sure Zotero will be able to parse them properly.

Thanks!

Gabe
  • gabestein
    Welp, figured this out. It's because we were using property instead of name for our meta tags.

    So, feature request: Zotero should look in both the name and property field in meta tags.
  • zuphilip
    edited December 10, 2019
    Any reason that you don't change your property attribute into a name attribute? This is what a lot of (all?) others are already doing and it is also suggested by Google Scholar for inclusion, cf. https://scholar.google.com/intl/en/scholar/inclusion.html#indexing .
  • gabestein
    Thanks! Yeah, we're going to change them. It's just a common mistake, since DC uses property, and it seems like other platforms (Mendeley, Scholar, etc.) actually do parse both the property and name attributes. So, could save some trouble down the line.
  • adamsmith
    That sounds right to me -- do you see any reason not to fall back to property if name isn't present @zuphilip ?
  • zuphilip
    In principal, I have nothing against adding it as a fall back. But I am just not convince that it is a "common mistake". Do we have any (other) example where this is used?

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.