-
Notifications
You must be signed in to change notification settings - Fork 769
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
Zenodo -> InvenioRDM, support more repositories #3206
Conversation
e25d490
to
e2314ca
Compare
I can't see why the checks are failing. The log says "Some translator tests failed", but on my systems all tests look OK. Is it possible to run the exact same checks locally, and hopefully get more explicit error messages? |
967fcf7
to
dc1632e
Compare
OK, a few comments. More generally, though, do we actually need two translators here? The changes seem very minimal. |
Thanks @AbeJellinek for your comments. I'll see if I can assemble both repository families into one single translator. |
Not ready yet. |
bc5dc01
to
39e4031
Compare
OK, ready for another round of review :-) |
- More straightforward path check in detectWeb - Add setTranslator() label comment - Set libraryCatalog to Zenodo when scraping Zenodo.org for clarity and consistency with old translator
d721238
to
230a6e5
Compare
Thank you! |
This pull request addresses issue #3057 .
Extending the Zenodo translator to support several InvenioRDM repositories that have been identified
Quick fix for tags that were not retrieved properly in the previous version
Recycling the previous Zenodo translator to support various repositories based on the former Zenodo code base