Zenodo translator turns software into report


When I browse to https://zenodo.org/record/580337 my browser switches the Zotero icon to software/code, but upon importing, the item becomes a report.

Despite Software, while neither "article", nor "preprint", nor "report" appear in the source of that page, which might effect this behaviour, according to https://github.com/zotero/translators/blob/master/Zenodo.js.

Firefox 52.6.0
Chrome 63.0.3239.132

Is this happening to other people as well? What could be the reason? Thanks for any hints!
  • Zenodo puts "article" into the CSL JSON, which we use for import. That's not a mistake on their part (I suggested this to them), but due to the fact that CSL doesn't have a software item type (yet).

    I think the easiest way to fix this would be to re-set the item type using the detectWeb function, i.e. something like item.itemType = detectWeb (doc, url) (untested)
  • Thanks for explaining and the suggestion :-)

    Do you mean that the time is ripe for a PR to change this behaviour? Or that I should apply it to my fork? I would be interested in the latter, but would rather inquire about the reasons for the original suggestion?

    I have incomplete understanding of this situation, but I can't help thinking that maybe stopping to use work-arounds (even while downstream support (CSL) is lacking!) would help to resolve such chicken-or-egg-type conundrums?
  • I mean a PR. There's absolutely no reason for this other than that either I overlooked it when writing the translator or that there was something different about Zenodo's CSL JSON back then.

    Not quite sure I understand the workaround part -- are you just saying we should fix this in the Zotero translator (agreed) or something else?
  • "work-around" in that Zenodo applied it back then to avoid any risk of issues with the CSL intepretation of the items downstream.

    I'll try to update the translator. Maybe only in March, because the first free slot in my schedule occurs then.
  • they certainly shouldn't be inventing CSL item types -- that could cause all sorts of problems; I don't think staying within a given standard is a workaround. They also use misc as a bibtex item type for the same reason.
  • edited 12 days ago
    The "misc" vs. "software" as BibTeX types is a good example, about which might learn more at https://www.wias-berlin.de/WCMS/program.jsp?MMSDays2018. Did using the "software" item type cause any problems in your tests? I added some "software" items to a .bib, let pandoc build a document from it and found no issues. Except the silent downgrade to "misc".
  • I don't know about software in particular, but the fact that everyone just keeps inventing things in bibtex and there's no stable standard has been a huge nightmare. See e.g. the mess that's citing a webpage: https://tex.stackexchange.com/questions/3587/how-can-i-use-bibtex-to-cite-a-web-page
    Having dealt with having to make compromises around "most common" practices based in BibTeX for many years now, I'll fight tooth and nail to keep CSL and its input standardized to avoid that.
Sign In or Register to comment.