-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Bug in American Medical Association 11th Edition, on Conference Proceedings #7219
Comments
You may also refer to this video reproducing the steps above. Thanks! AMA.issue.2024-09-18-720p.mov |
You could/should add "WaterAid" as a publisher for that citation. |
They should, I agree. But shouldn't the style itself accommodate scenarios where this field is missing? For instance IEEE generates this line without a publisher:
And this with a publisher:
(line breaks are from me to avoid horizontal scroll) As you can see, there aren't 2 commas or something just because the publisher field is missing, so in the case of AMA it looks maybe like a style definition bug, or maybe an issue with the style itself? The user gave us this link for reference, not sure what to make of it: https://sheridancollege.libguides.com/c.php?g=704219&p=5008563 . Thank you! |
Hello,
one of our users discovered an issue with the AMA style: for conference proceedings references with some combination of fields completed, it will generate a weird
. ;
sequence that is not correct.Steps to reproduce:
Edit
on the AMA style (either search or scroll to it)Example citations
in the top right cornerCitation 3
Advanced
, and paste this reference in json format:Expected output:
Carter RC, Harvey E, Casey V. User financing of rural handpump water services. In: IRC Symposium: Pumps, Pipes and Promises; 2010.
Actual output:
Carter RC, Harvey E, Casey V. User financing of rural handpump water services. In: IRC Symposium: Pumps, Pipes and Promises. ; 2010.
As you can see, there's an extra dot and space after the
container-title
field, which should not be there.Thank you for your time!
The text was updated successfully, but these errors were encountered: