I am a computer engineer with a background in Computer Networks, highly interested in programming and infrastructure.
Recently I have been doing mostly backend development with Python, PostgreSQL and ElasticSearch.
I am actively working on my front-end skills with React and TailwindCSS - the latter I used to build my website!
🔭 I’m currently working on Zenodo, the world's largest open-access repository for research data, built to ensure everyone can join Open Science.
👯 Part of the InvenioRDM community and core developer of the InvenioRDM framework.
At Zenodo and InvenioRDM, I worked on multiple features such as:
Collections organize the contents of a Zenodo community in logical sets of records. For the European Open Repository, these can be a set of records that share the same funding or are from the same discipline (e.g. Natural Sciences).
📺 See this feature live at Zenodo 📺
I want to see screenshots!
Each collection can then be accessed to inspect its contents:
These records can be further filtered by using the left-hand facets, providing multiple layers of organization and discoverability of the community contents.
The underlying concept of collections is that they are tree-like structures that store an OpenSearch query (to fetch the records). Therefore, we store each collection in the DB as a tree-like structure using the materialized path pattern.
Read more
Here is a nice guide from the MongoDB folks:If you are curious (and courageous), you can read the Request for Comments document where all the technical nuts and bolts are discussed.
Zenodo archives openly disseminated software source code in Software Heritage, in a combined effort to "create an interconnected and interoperable academic ecosystem, (...) contributing to the global software commons" (blog post)
At the time of this writing, more than 5000 software records have been archived using this integration!
To fulfil the requirements, Zenodo needed to:
- Support software field in its metadata schema
- Integrate with Software Heritage
- Support metadata formats that are suited for the serialization of software-type records
Give me some screenshots, come on!
Zenodo's deposit form supports software-specific fields, including a controlled vocabulary of programming languages.
After a record is archived in Software Heritage, the user can navigate to the archive's landing page.
New export formats were added to support the serialization of software records to common software formats (e.g. CITATION.cff and CodeMeta)