-
Notifications
You must be signed in to change notification settings - Fork 25
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
feat: implement new SearchSources #120
Comments
Hi, Ich hätte Lust dieses Issue zu bearbeiten :) |
Ich bin dabei! |
Ich wäre auch daran interessiert an diesem Issue mitzuarbeiten :) |
Hallo, ich wäre auch an dem Thema interessiert. |
Ich auch🤚 |
@frxdericz: die Nachmeldung ist ausnahmsweise ok, da die Gruppe noch nicht voll war. |
Hallo ihr Lieben, hat für den Milestone schon ein Treffen stattgefunden? |
Hi, |
@Cohen2000 |
Hi, stand jetzt sind wir zu viert, heißt wir haben noch einen Platz frei. Du kannst mir auch gerne unter '[email protected]' deine Handynummer schreiben, dann kann ich dich noch hinzufügen :) |
@Cohen2000 vielen Dank :) habe dir gerade ne Mail geschrieben! |
FYI: #187 recently introduced changes relevant to the local settings. |
A quick update on ERIC: there is a |
@geritwagner können sich bitte nochmal assignen :) ich hatte mich gerade vertippt |
Feature Request
Describe the Feature Request
Additional SearchSources should be implemented (see #106 for an overview).
Describe Preferred Solution
The ERIC database would be a good starting point because it is similar to the Crossref API, which is already supported (see crossref SearchSource). In fact, the code skeleton for the ERIC SearchSource already exists. To support API-based searches, the run_search(...) method needs to be implemented (parsing the json response from ERIC). To add a new ERIC-API-based search (and the search parameters), the add_endpoint method needs to be extended.
The arXiv API provides a different format (xml). The code for the pubmed SearchSource provides a good starting point for parsing xml content.
The IEEXplore database is a more challenging example because it requires a registration (an API key). You need to apply for it before you can access the API. The implementation of run_search(...) in the corresponding code skeleton is similar to the ERIC case. The only difference is that the API key must be stored in a local settings file (as a secret). To create a local settings file, code for the project settings (especially the load_settings() and save_settings()) would be useful. The settings should be handled by the environment_manager and available through the review_manager.
Expected Effort Required
2 months, 5 people.
The text was updated successfully, but these errors were encountered: