Need more data about the repository

[jupiter007]

Task:
Investigate the re3data API and making a recommendation on pulling it each time they get to here, or pulling it into our DB once a month or so so that we have more information to show about repositories.

In the current dmptool, when users are searching to add preferred repositories, the interface includes lots of data about the repository (see screenshot below):

In the rebuild,there is no additional data. It currently just looks like:

The thought is that we should make more info available to the client.

[bofstein]

First step is investigating the re3data API and making a recommendation on pulling it each time they get to here, or pulling it into our DB once a month or so.

[sfisher]

I started writing code to test the re3data api. I thought that it would require a bunch of comparison of the different APIs, https://www.re3data.org/api/doc/ . I was specifically interested in the OpenSearch suggest endpoint, but it returns the same set of data no matter what the search string is set to.

Examples:

https://www.re3data.org/api/opensearch/suggest?search=dryad

https://www.re3data.org/api/opensearch/suggest?search=cat

https://www.re3data.org/api/opensearch/suggest?search=geology

All return exactly the same set of items. It fills in the search term in the response so it seems clear it got the search term but it is functionality that always gives the same results no matter what is asked for. 🙃

I submitted a question to the re3data contact form about the functionality in case I missed anything, but to me it just seems as though their functionality is just broken unless I missed something non-obvious.

Their HTML forms seem to work so we could screen scrape (yuck), but aside from that it seems like the solution is to get the entire set of data from the API and do search and filtering locally from the full data. This means probably re-implementing what was done in dmptool roadmap (updating in DB and creating our own filter/search rather than relying on re3data suggest).

There is also a beta api, but it seems to duplicate the same basic functionality of the current api which is basically to list all the stuff and to get details of an individual record.

[briri]

@bofstein would it be worth reviewing the FAIR Sharing API at this point to see what they offer? Here's the Dryad reposity (called "database", not "Repository", in their system) record in their system https://fairsharing.org/search?q=Dryad and here's their API doc https://fairsharing.org/API_doc