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

Skip publisher if it equals JSTOR. #2

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Skip publisher if it equals JSTOR. #2

wants to merge 1 commit into from

Conversation

lawlesst
Copy link

@lawlesst lawlesst commented Apr 8, 2016

The publisher is being reported as JSTOR for some journals when JSTOR is probably the DOI minting agency. This just skips the publisher if it equals JSTOR. We could also consider not adding publishers for journal articles because the publisher information would be coming from another source.

@grahamtriggs
Copy link

Thanks Ted,

I'm 50 / 50 on whether we should worry about this, for two reasons.

  1. We will be importing a large, curated journal set before "launch" and linking publications to that. In the case that the journal exists in the set, then we won't be creating journals or publishers anyway.

  2. There is a question as to how much we should try to fix the data in the ecosystem. Mostly what I've done is normalize data (e.g. common representation of names to aid the guessing of authors). The one serious issue I dealt with was to ignore ISSNs that were errorneously included on books and chapters (because that made a total mess of the data).

Part of the outcome of this should be to highlight the problems in the ecosystem. Certainly, we need to track this - and the issues outlined above - and make it visible that these problems exist. Knowing that we can't automatically fix everything, we might want to accept that some of these things will be visible in the imported data anyway.

I'll speak to Mike later, and check that we are documenting the issues that we are working on - e.g. including it on the poster - or if we should leave the data to highlight the problem.

@lawlesst
Copy link
Author

lawlesst commented Apr 8, 2016

Both reasons make sense to me. Thanks for the explanation.

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

Successfully merging this pull request may close these issues.

2 participants