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.
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
ISis lacking). My reading is based on the comparison of this snippet for RIS formatter https://github.com/adsabs/export_service/blob/c4e8db37d2cbebf8a24c66c56ec957115ecbc41f/exportsrv/formatter/fieldedFormat.py#L157-L163 vs. bibTeX formatter https://github.com/adsabs/export_service/blob/c4e8db37d2cbebf8a24c66c56ec957115ecbc41f/exportsrv/formatter/bibTexFormat.py#L140This 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.