Skip to content
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

Request: Export issue/number field for journal articles by default? #232

Open
zoe-translates opened this issue Mar 22, 2023 · 0 comments
Open

Comments

@zoe-translates
Copy link

Context

First, please let me know whether I'm correct in saying that currently, the "issue" or "number" field is not exported by default by the fielded formatters (e.g. RIS, where the field IS is lacking). My reading is based on the comparison of this snippet for RIS formatter

if (export_format == self.EXPORT_FORMAT_REFMAN):
return (OrderedDict([('doctype', 'TY -'), ('title', 'TI -'), ('author', 'AU -'),
('aff', 'AD -'), ('pub', 'JO -'), ('volume', 'VL -'),
('pubdate', 'Y1 -'), ('page', 'SP -'), ('lastpage', 'EP -'),
('keyword', 'KW -'), ('url', 'UR -'), ('abstract', 'N2 -'),
('doi', 'DO -'), ('eprintid', 'C1 - eprint:'), ('issn', 'SN -'),
('endRecord', 'ER -')]))
vs. bibTeX formatter
('volume', 'volume'), ('issue', 'number'), ('eid', 'eid'),

This results in a missing field in the output where the "issue" or "number" field could have been made available.

Request

I wonder if the support for exporting the issue/number field in the record (see #175 for custom formats) could be extended to the default output of the fielded formatters too.

Further context

Although the issue/number field may not be that useful for the AAS/RAS journals, it is used in many other styles and by authors outside the "core" Astronomy communities.

This problem was found while I was working on zotero/translators#2998. To create a record as the user browsers the ADS, the Zotero translator (data-gathering routine) requests the RIS data from the API (RIS parsing is simple and fast). That was how I noticed that it's missing.

It could have been worked around by the client using the API for custom formats, but that would've been more difficult to maintain on the client side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant