-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACM: Journal article saved as document
#2162
Comments
Does someone have a contact at ACM that we could see if they can fix their CSL-JSON? |
The I guess a stopgap would be to manually create a mapping from their style to something that |
Fixed. Looks like it was a change — some tests were failing because of it. After treating |
Reported here: https://forums.zotero.org/discussion/82523/acm-article-saves-as-document
On https://dl.acm.org/doi/10.1145/3230742, Zotero detects a journal article but saves a
document
item, and because of that various fields are missing.If I'm reading things right, the new ACM translator by @GuyAglionby makes a request to ACM's
exportCiteProcCitation
endpoint, which returns JSON with a custom, invalid CSL style for BibTeX output along with some invalid CSL-JSON data. The translator lowercases their invalid uppercase types, but then just runs it throughitemFromCSLJSON()
. Unfortunately, that's not sufficient, since they're not actually serving CSL-JSON that accurately describes the item — their concern seems to just be outputting correct BibTeX or Refer, sotype="ARTICLE ARTICLE_JOURNAL ARTICLE_MAGAZINE ARTICLE_NEWSPAPER"
all simply output@article
in the BibTeX. (I'm not sure if they're using a custom CSL processor or just something that happens to be forgiving with invalid types and other validation errors.) In this case, the type isARTICLE
, but the (lowercased)article
CSL type isdocument
in Zotero, notjournalArticle
like it is from the BibTeX@article
.I haven't looked to see what other problems there might be in the CSL-JSON, but I'd guess that it'd be safer to simply use their BibTeX output instead and make some of the same tweaks to that.
@GuyAglionby, any reason we're not doing that?
The text was updated successfully, but these errors were encountered: