zotero / translators

Zotero Translators
http://www.zotero.org/support/dev/translators
1.19k stars 743 forks source link

Cover other Invenio RDM repos in Zenodo translator #3057

Open marcschulder opened 1 year ago

marcschulder commented 1 year ago

There are a number of research data repositories that, like Zenodo, use Invenio RDM as their code base. Would it be possible to add them to the Zenodo translator or add a related translator? The former would be preferable with regard to code duplication, but I don't know how much the custom surface wrappers of the individual repositories or differences in how up-to-date their Invenio RDM version is might complicate things.

Examples of relevant repos are https://www.fdr.uni-hamburg.de/ (visually very close to Zenodo) and https://researchdata.tuwien.at/ (more heavily customised interface). I'd be happy to try and compile a longer list of eligible repos if that helps.

adam3smith commented 1 year ago

Yes, a full list would be great. Invenio URLs aren't distinctive enough to recognize based on regex. I know Caltech & NYU use Invenio here in the US

marcschulder commented 1 year ago

So this turned out to be rather more trickt than I had anticipated. I started out by looking at the list of InvenioRDM contributors, hoping that most would be hosting a repository. This was true in part, though several partners were service providers (I checked their customer lists where feasible) and in most cases the partner website hide its repo(s) pretty well. I eventually found a variety of repositories, though it was very difficult for me to determine whether they were actually running on InvenioRDM, some pre-RDM-rebrand Invenio version or some other software. In the end I mostly had to go by visual comparison. I also checked the Invenio showcase, but again ran into document repos that must evidently be running pre-DRM Invenio software. Here are my likeliest candidates:

Strong match to Zotero UI:

Differing but similar UI:

Fairly different UI, but (probably) related:

Candidates that already have a custom translator:

Special cases:

Hope this helps. Let me know if I can do anything else.

adam3smith commented 1 year ago

Thanks! The first group will be easy. The second group requires fairly substantial additions to the code since nothing seems to work quite the same (e.g. it's records, not record, the metadata formats get exported rather than displayed inline) so while doable, that'd take a good chunk of work (PRs welcome).

I don't see how the third group even makes sense within the same translator. The ones I looked at don't export to the same formats, so there's no overlap at all.

aborel commented 6 months ago

As far as I understand, Zenodo wasn't really using InvenioRDM when this issue was opened. It officially migrated to InvenioRDM in October 2023, and the Zenodo translator is now updated accordingly. Therefore, the easier targets should be group 2.

Servers in group 1 are probably using some variant of the weird Invenio version on which Zenodo was based. I assume that it would make sense for them to migrate to the actual InvenioRDM at some point, but obviously this is a non-trivial change and we cannot tell when they will be in a position to do it. Perhaps the previous Zenodo translator can be resurrected to support these repositories.

In group 3, I can say that https://arodes.hes-so.ch/ isn't using InvenioRDM. Like our own insitutional repository https://infoscience.epfl.ch/ , the platform is a variant of the old Invenio 1.2 (i.e. https://github.com/inveniosoftware/invenio instead of https://github.com/inveniosoftware/invenio-app-rdm)

adam3smith commented 6 months ago

Thanks for the context. @aborel would you be up for extending your Zenodo/Invenio translator to capture group 3 above?

aborel commented 6 months ago

@adam3smith Do you mean group 2?

adam3smith commented 6 months ago

yes, sorry

aborel commented 6 months ago

OK then :-) And thanks to @marcschulder for listing the candidates!