Giter Club home page Giter Club logo

oamonitoring's People

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

oamonitoring's Issues

Make README more general and move specific information to the Wiki?

I went through the README and saw that is focused on the Utrecht situation with precise data from when files have been exported, etc. I would suggest to move this specific information to the Wiki and let the README be more general and really about the code itself and mock input and output. I can then also add information about the Leiden situation to the Wiki. What do you think?

How to resolve green from CRIS data?

It is hard to predict what elements are present in a CRIS that can be used to resolve green OA.

In 2018, Utrecht University used a combination of columns indicating what kind of document was submitted in their CRIS (Author Accepted Manuscript or Published Version), and the presence of an embargo period. This is hard to replicate and generalize. For one, the notation in another CRIS may be different. Secondly, the presence alone of an embargo period is not a good indicator for something being openly available (though if embargo dates are present, they could be read as dates and confirmed to exist in the current year?).

Unpaywall tends to overestimate green, but has a more sophisticated ability to look into this (I believe they screen the pdfs themselves for copyright information?). Unpaywall also provides a link to documents, so they also confirm that the document is hosted on a repository.

Unpaywall is the best generalizable option we have at the moment to confirm green... Any other ideas?

Ask user if they want to mine API or use saved data

At the moment, the APIs for DOAJ and Unpaywall are used. Mining this api takes a while, and the data is saved, along with a date stamp of the record. It would be good if saved data can be used in future iterations of the project, but it should be optional: a user should be able to get current data from an API or refer back to saved data, depending on their wish.

How can we do this?

  • With a simple option in the config file
  • With a user question when the API is accessed

Which route is preferable? And how do we execute it?

Include a license

We should include a license. At the Leiden University Libraries we usually use GPL 3.0 for our developed software. Do you agree with that? I am also fine with MIT, Apache 2 or another permissive license.

Additional labeling options

Many universities used Taverne to make output available via the university repository last year. It would be interesting to be able to score these papers separately. Additionally, other universities may have other projects that they want to label independently.

We could envision having the option of either providing a list of DOIs (or system IDs) for papers that a university wants to classify separately, as well as the classification (GOLD/HYBRID/GREEN -- or even an additional option?) and the source.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.