You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 31, 2020. It is now read-only.
MNRAS typically issues a temporary identifier before assigning a final reference, with bibcodes that look something like this: 2016MNRAS.tmp..123A.
Often, when I run adsbibdesk in update mode, it finds that an arXiv entry now has a temporary MNRAS ID and so it updates to that new ID, but there's currently no way to check for and update these temporary MNRAS IDs to their final IDs, along with associated final reference details. A DOI is issued by MNRAS along with the temporary ID, but not the final year and month of publication, the volume number or the pages.
I can see two possible ways to deal with this:
when checking for arXiv updates, ignore the update if it is a temporary MNRAS bibcode.
keep the existing behaviour (where arXiv bibcodes get updates to MNRAS.tmp bibcodes), but add an extra check to find+update MNRAS.tmp bibcodes.
I don't know which would be easier to implement/work better.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
MNRAS typically issues a temporary identifier before assigning a final reference, with bibcodes that look something like this:
2016MNRAS.tmp..123A
.Often, when I run adsbibdesk in update mode, it finds that an arXiv entry now has a temporary MNRAS ID and so it updates to that new ID, but there's currently no way to check for and update these temporary MNRAS IDs to their final IDs, along with associated final reference details. A DOI is issued by MNRAS along with the temporary ID, but not the final year and month of publication, the volume number or the pages.
I can see two possible ways to deal with this:
I don't know which would be easier to implement/work better.
The text was updated successfully, but these errors were encountered: