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

Improve how the KnownPubsDB gets updated #1

Open
tnabtaf opened this issue Sep 29, 2017 · 0 comments
Open

Improve how the KnownPubsDB gets updated #1

tnabtaf opened this issue Sep 29, 2017 · 0 comments

Comments

@tnabtaf
Copy link
Owner

tnabtaf commented Sep 29, 2017

Right now, the Known Pubs DB (a TSV spreadsheet) is updated in two ways:

  1. By running PubSpork. This updates it with information from the latest alerts, and from the relevant pubs library itself.
  2. By opening it in a spreadsheet program and manually updating the state and annotation columns. These columns are set when a publication is irrelevant, or is relevant, but we just can't curate it yet.

I'd really like to improve that manual updating step. I'm just not sure how.

In my ideal world, the generated HTML report (that drives the curation process) would also include forms/pulldowns/whatever to flag a paper as irrelevant and say why. We wouldn't need to open and manually update the spreadsheet.

This might requiring moving the DB to, say, SQLite. I like having the spreadsheet, but I could adapt to SQLite too.

Suggestions (and fixes!) are encouraged.

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