[REST APIs] - Choose a library to interact with Zenodo

[garciagenrique]

• [ ] Get familiarised with the different Open Source existing libraries to interact with the Zenodo API

  • [ ] zenodopy
  • [ ] zenodo-client
  • [x] eOSSR
  • [ ] Any other Zenodo wrapper you might discover

• [x] Translate the 'fetch-communities' script into a script using the chosen library

• Set up few testing scripts with the chosen library

  • [x] Within all the examples, think and implement of a way to ask/request for the ZENODO user token
    • [ ] Think of a way to manage a return payload with +100 answers.
  • [x] Search and return any entries with software as a resource type
  • [x] Search and return entries with different file formats (.txt, and .root, for example)
  • [x] Search and return entries with medata file
    • [ ] #27

[mrzengel]

Something we'll have to address in the future: there's a rate limit for the Zenodo REST API, so we can only get 100 records with each request. This shouldn't be too much of a problem, but something to keep in mind.

[mrzengel]

Script that returns records with resource type "Software" Script that returns records with a specified file type Script that returns records with codemeta.json file

[garciagenrique]

Something we'll have to address in the future: there's a rate limit for the Zenodo REST API, so we can only get 100 records with each request. This shouldn't be too much of a problem, but something to keep in mind.

How does it look and how do you interact with a requests answer containing more than 100 (for example) entries ?