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

Always use linking ISSN when it exists #11

Open
paulalbert1 opened this issue Jan 26, 2021 · 0 comments
Open

Always use linking ISSN when it exists #11

paulalbert1 opened this issue Jan 26, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@paulalbert1
Copy link
Collaborator

paulalbert1 commented Jan 26, 2021

Background

Looking up journal-specific metrics is easiest when we use linking ISSN to fill the ISSN column in the personArticle table.

Problem

In actuality, this code for import from s3 (and its counterpart for DynamoDB) prefers e-ISSN even when there's a linking ISSN.

if 'issn' in items[i]['reCiterArticleFeatures'][j]:

For example, here's the output for szd3005 and 33476307.

{
    "personIdentifier": "szd3005",
    "dateAdded": "2021-01-26T20:33:07.606+00:00",
    "dateUpdated": "2021-01-26T20:33:07.606+00:00",
    "reCiterArticleFeatures": [
        {
            "pmid": 33476307,
            "journalTitleVerbose": "The Journal of clinical investigation",
            "issn": [
                {
                    "issntype": "Electronic",
                    "issn": "1558-8238"
                },
                {
                    "issntype": "Linking",
                    "issn": "0021-9738"
                }
            ],

To populate ReCiterDB, we're pulling electronic ISSN as opposed to linking ISSN. Unfortunately, this is quite common.
image

Fix

The relevant Python scripts should preferentially use linking ISSN whenever it exists.

@paulalbert1 paulalbert1 added the bug Something isn't working label Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants