You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to implement the possibility to add entries directly via their zbMATH id. I think this can be done quite easily by adjusting the zbMATH-Fetcher. I think this would be interesting as zbmath will become open access from January 2021 and thus no subscribtion for it is needed anymore.
The text was updated successfully, but these errors were encountered:
Thank you for the information. I already had a look at the code and found the zbMath fetcher :-) I won't have that much time this year but I will work on the fetcher the first week of January.
Hi,
I implemented the IdBasedParserFetcher interface for the zbmath fetcher and it worked on my Computer (with gradlew run.)
However, I have a problem testing jabref. Even on the master branch (without my changes) neither gradlew test nor gradlew check work. The "How to test" (https://devdocs.jabref.org/getting-into-the-code/testing) did not help me. What do I have to do in order to be able to test jabref?
Best
Isabel
Hi, it should be fine to just run the specific test for the fetcher from your IDE.
The Github Actions automatically execute the tests when you create the PR, so you can see the results there
JabRef supports adding entries via different kind of ids (https://docs.jabref.org/collect/add-entry-using-an-id). Right now, it is not possible to add an entry from zbmath.org via its zbMATH id, however it is possible to add entries by searching its database (https://docs.jabref.org/collect/import-using-online-bibliographic-database).
I would like to implement the possibility to add entries directly via their zbMATH id. I think this can be done quite easily by adjusting the zbMATH-Fetcher. I think this would be interesting as zbmath will become open access from January 2021 and thus no subscribtion for it is needed anymore.
The text was updated successfully, but these errors were encountered: