On September 28-29 the InvenioRDM project team gathered again (though sadly, again, without fondue) for the Virtual Project meeting. Over 50 partners and team members were present and a great deal of helpful feedback was shared as we worked to develop the roadmap for the next stage of the project. Thanks to everyone for your contributions to the discussion, they are much appreciated!

The InvenioRDM project team would not be so robust without the thoughtful contribution of each of its members. Thank you to all of you who were able to commit the requested 1.5 person months to the project for the next year, in some cases more. The work of each partner site results in unique and valuable contributions to the team. We’d like to use this post to highlight, in a summarized format, the contributions that each project partner highlighted for us at the meeting. Here’s the amazing compendium of work that you have contributed over the past year:

  • BNL: Integrating the keycloak OAuth plugin module a part of the InvenioRDM framework.

  • Caltech: DataCite 4.3 support and JSON REST API for DOI Registration. Registering very complete metadata records with DataCite.

  • Data Futures GmbH: IIIF Presentation API record serializer, IIIF powered search view thumbnails, embedded Mirador 3.0 IIIF previewer.

  • EkoKonnect: InvenioRDM part of Open Science cloud platform.

  • Geo: Predefined queries for GEO Priority Areas, map preview/reference.

  • HZDR: Documentation of deployment steps, testing.

  • INFN: Community survey, requirements gathering, testing functionalities, participating in Metadata Working Group, commitment to REST API testing, writing of guides on how to integrate InvenioRDM APIs with programming languages used by research communities.

  • JRC: Invenio-records-resources feature to support one of January Release functionalities.

  • Northwestern: Various core contributions, including implementing OpenID Connect / OAuth at NU (includes SSO and MFA) and sharing local migration process and local implementation rollout.

  • NYU Contributed usability study findings and presented to Telecon; proof of concept geo previewer / viewer for vector GIS data; working toward extending the concept of index sample metadata records via the command line tool.

  • NII Testing based on local scenarios; knowledge sharing for InvenioRDM operation on Kubernetes (Monitoring, Logging and Backup strategies, etc.).

  • TIND Simple k8s demo setup (helm-invenio).

  • Tubitak Provided Turkish translations to InvenioRDM; will maintain and participate in release testing and Interest Group participation.

  • TU Graz: Ongoing work: 18n of the python modules; i18n of the react modules; OAI-PMH, core sprint participation.

  • TU Wien: During development sprints, helped implement Access Control (v1.0), Share-by-Link (v2.0), and Keycloak SSO (v4.0). Would like to contribute to Communities code in future.

  • Universitat Hamburg: Contribution highlights: S3 plugin, initial SAML integration. Committed to: Help with testing, documentation, dissemination.

  • Universitat Munster: Development of helm chart, to deploy InvenioRDM inside a Kubernetes infrastructure; implementation/documentation of Kubernetes based architecture (https://github.com/ulbmuenster/inveniordm-2-production); tests of REST API by automated (OAI-PMH based) import of datasets from the WWU document repository miami (https://miami.uni-muenster.de) into InvenioRDM.

  • Universitat Tubingen: Contributions planned if production status reached: dissemination, acquiring funding for development needs in interdisciplinary research projects, participation in NFDI’s (nationwide infrastructural developments in domain-related RDM).

  • Universitat Freiburg: Regular testing of new releases and features; automatic deployment & recovery strategies; basic UI customization.

  • ZHB Luzern: Testing: usability of setup resources (e.g. invenio-cli) & customization and styling; evaluation of metadata standard.

Thanks again, everyone, for your contributions! Hope to see you in person at the next project meeting.