-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
The APS style (with title) falsely pull "Number" into the field of "Page". #6785
Comments
This is probably a bug, but importing issue as "number" is also a bug: number for journal articles is the article number, so that import behavior (in Zotero?) should also be reported there |
I rarely see the genuine field of "Number" filled in Zotero, except for arXiv or some books. For Nature series papers, the other side of the problem is the publisher puts information like Having said that, a simple trick to temporally resolve the problem is to delete the line "Number: 7846" in the above example, or if want to keep the information, modify it into one line, i.e., |
Number is a valid piece of data for some electronic journals that use article numbers rather than page numbers (eg, APA style calls for separate formatting of article vs page numbers). If anything, this is a data import issue |
While indeed it may be a data import issue, since other styles, including APS (without title), don't have this problem, I guess it is at least also a style issue |
As the title states, American Physical Society (APS) style with title confuses "Number" with "Pages". This becomes problematic when the "Number" field is imported into the "Extra" field. When this happens, APS style (with title) skips "Pages" field and use "Number" as page number. However, "Number" is not necessarily "Pages". It commonly happens to Nature series papers, where the "Number" is actually "Isuue Number". The result is the APS style with title take issue number as page number, when ever "Number" appears in "Extra".
This does not happen for APS style without title.
The text was updated successfully, but these errors were encountered: