Import from CSL JSON ignores name particles and suffixes

nickbart
When importing CSL JSON, for example from the citeproc-js test suite file name_namepartAffixes.txt:

[
{
"author": [
{
"dropping-particle": "de",
"family": "Fontaine",
"given": "Jean",
"non-dropping-particle": "La",
"suffix": "III"
}
],
"id": "ITEM-1",
"type": "book"
}
]

"dropping-particle", "non-dropping-particle", and "suffix" are silently ignored.

"comma-suffix", when present, is ignored, too.
  • adamsmith
    Not sure to what extent this was ever intended to work on import - principally CSL JSON is an export format for ref managers to communicate with citeproc-js.
    Zotero would have to put those back together into its regular fields, which sure, could be done, but since pretty much no one actually uses CSL JSON as a data exchange format I'm not sure if it's worth the time to code.
  • nickbart
    Well, a few people using pandoc, including myself, seem to be interested, in particular since the output from pandoc's excellent biblio2yaml can easily be converted to CSL JSON, offering an interesting alternative import path from bib(la)tex. See http://groups.google.com/forum/?fromgroups=&hl=en#!topic/pandoc-discuss/gq0rRq4oiro
  • adamsmith
    fair enough - I don't think there'd be any objections if someone wanted to submit a patch (I'd have to look for the code snippet, but it's in the function itemFromCSLJSON ), otherwise I doubt it's going to be high priority at this time.
  • nickbart
    When importing from CSL JSON, is there any reason why Zotero does not accept the valid CSL variable "title-short", while it does accept "shortTitle"?
  • RintzeRintze
    Answered here: https://groups.google.com/d/msg/pandoc-discuss/gq0rRq4oiro/GyutnLMRP1gJ

    (the easiest solution would be to ask that all CSL processors map both the "title-short" and "shortTitle" (for legacy reasons) JSON fields to the "title-short" CSL variable)
Sign In or Register to comment.