Ignore DOI

seanoconnell
Hi, I'm developing a site that we wish to work with the Zotero plugin but we're encountering issues with DOIs on the page. Can I force the plugin to just read the meta-data and ignore any DOIs.

Any help much appreciated.
  • adamsmith
    we'll be switching the priority of the embedded metadata and DOI translators in the pretty near future and that should solve your problem, so if waiting a couple of weeks is an option, I'd do this. All other solutions are more involved.
  • seanoconnell
    That's great. Thank you for the swift response.
  • seanoconnell
    Any news on this update?

    What is the other solution?

    Many thanks.
  • bwiernik
    For the moment, you can choose alternative translators by clicking on the arrow menu to the right of the Zotero import button.
  • seanoconnell
    Hi, I'm looking for a solution which I can apply to the site I'm developing.
    I want the Zotero plugin to use the citation tags in the page rather than use the DOIs it finds. We're having problems when there are multiple DOIs on the page (one for the article being viewed and additional DOIs for external references). Is there anything I can add to the markup to force the Zotero plugin to use the metadata?
  • seanoconnell
    Why is the DOI translator using datacite.org instead of Crossref?

    The DOIs on our site are registered with Crossref but are not found on datacite.
  • adamsmith
    The DOI translator is going to CrossRef first, then DataCite if CrossRef comes back empty.
  • seanoconnell
    I know the DOIs are registered with Crossref. Could the issue be that the URL returned by Crossref doesn't correspond with the site as I'm running in a test environment?
    Any help very appreciated.
  • adamsmith
    Does the DOI work using the add by identifier tool in Zotero? (The magic wand)
  • adamsmith
    But we will still make the promised priority switch. I just haven't gotten to it as quickly as I wanted.
  • seanoconnell
    No, it does not. Here's the DOI I just tried : 10.1036/1097-8542.189400
  • adamsmith
    edited October 25, 2016
    ah OK -- we just can't read the metadata, so the translator throws an error. I don't think we've ever seen CrossRef dataset data before (and the unixref XML format isn't, I believe, super clearly defined).

    Edit: That's not actually true. The schema and documentation is up. We just didn't implement database/dataset.
  • seanoconnell
    Is there anything I can change to help? Although reloading data to Crossref won't be an option.
  • adamsmith
    We'd take PRs to https://github.com/zotero/translators/blob/master/CrossRef.js
    The reason I'm not particularly after this is that I'm hoping to switch DOIs entirely to the API provided by doi.org through content negotiation (https://github.com/zotero/translators/pull/1135 ). I'm just waiting on a CrossRef ticket to clear for this https://github.com/CrossRef/rest-api-doc/issues/152
  • seanoconnell
    OK. I'll try and be patient and wait for your update.
    Thank you for the quick responses.
  • seanoconnell
    edited October 26, 2016
    Hi Adam, can I push you for a potential release date for these changes. Specifically the priority switch for the translators.

    Can I also ask how I might get around this problem in the short-term. Will adding a direct link to a citation(Refworks, RIS, EndNote) on the page help?
  • noksagt
    Not merely a direct link, but yes: you may use a metadata sharing scheme that already has a higher priority. UnAPI or the various Context Object-based schemes are examples of general approaches (slightly more work than a mere link, but not much).
  • seanoconnell
    That's great. Can you provide some more details about what the translator is looking for on the page.
  • noksagt
    UnAPI requires you to make a simple web application that can point to one or more of those various standard file formats you list. It is documented on this archived page: https://web.archive.org/web/20140331070802/http://unapi.info/specs/

    COinS and other Context Object schemes are more limited, but allow you to embed data without needing a separate webapp to handle the query of record id+file format. See, e.g. http://ocoins.info/
  • adamsmith
    As for ETA for the priority switch -- I'm hoping this week and definitely before next, but that's expected, not promised.
  • seanoconnell
    Thanks Adam, I'll keep an eye on the change log.
  • adamsmith
    It won't show up in the changelog and the change is independent of Zotero version updates. Look at the commit log here: https://github.com/zotero/translators or specifically for the DOI and the Embedded Metadata translators in there.
  • adamsmith
    @seanoconnell -- the switch is now live: Zotero prefers embedded metadata over DOIs.
  • seanoconnell
    @adamsmith Thanks for the update.

    I've tried this with the Chrome Plugin and it still prefers the DOI. Firefox plugin offers a choice and the Embedded MetaData option behaves as expected. Will your code changes be picked-up immediately?
  • adamsmith
    should be within 24hs and may require a browser and Zotero restart.
Sign In or Register to comment.