Open Graph and JSON-LD

janiko
Hi all,

I'm a new Zotero's user, and I'm a bit surprised that some formats are not well interpreted in Zotero (as far as I understand): Open Graph Protocol (https://ogp.me) and schemas like https://schema.org/NewsArticle.

I often find them in web articles I read and I'd like to add them in a Zotero library. Unfortunately, only a few fields are correctly imported form the websites.

Example of ogp-compliant AND ld+json compliant website : https://threatpost.com/biometrics-security-solution-issue/139781/

What can I do to integrate those links, without having to code a translator (which should only be used for specific sites and not for "standards").

Any help is welcome !
  • adamsmith
    Open graph should be relatively well supported -- I don't see any OG fields that aren't imported from the page you link to. Given its purpose it's a fairly minimal schema.

    JSON-LD/schema.org has an open ticket and should happen soon-ish: https://github.com/zotero/translators/issues/917 nothing you can easily do for now on that, though.
  • janiko
    edited January 2, 2019
    Well, in the case of the document I mentionned, there are only a few ogp fields but some of them could be useful and they are not used:

    meta property="og:type" content="article"
    ==> could be used for website type (maybe, though it's more a page type than a website type) or in the extra field

    meta property="og:title" content="Biometrics: Security Solution or Issue?" /
    ==> for website title or short title

    meta property="og:description" content="Issues still exist when it comes to securing biometrics." /
    ==> looks like a (very) small abstract

    Other markups are available (though they are optionnal): og:locale, og:site_name...

    JSON LD is much richer, but it looks less spread across websites...
  • adamsmith
    Of these -- content type "article" is used essentially for every written piece. It contains no meaningful information; I think we're right to ignore it.

    og:title is (imo correctly) imported as title. It's not the website title (which would be threadpost and could be in og:site_name which I believe we use)

    og:description imports as an abstract for me (though I think we prefer the generic description meta tag, which is identical here; but we'd fall back to og:description where description is missing).
Sign In or Register to comment.