## Zenodo Extension
### Updates
Past week:
- Migration to new Zenodo/ inveniordm API done
- successfully avoid getting rate limited
- remove/ simplify api calls
- lots of refactors
- introduce a consistent composite ID for records: `(record_id : number, status : "draft" | "published")`
- necessary because there can be a draft and published variant of the same record with the same id, ugly but avoiding this only causes problems
- new: show both variants in the dropdown
- This is not what the Zenodo website does but more intuitive in my opinion. Please complain if unwanted
- new: separate downloads for drafts and published versions
- small new features (e.g. "discard draft" button)
To Do this week:
- Finally create a pretty UI
- More docs and docstrings
- Tests
- Meet the student script and video
### Questions
- Uploading to the draft version of an already published record gives 403 if file editing is still locked. How do i deal with this? I cannot reliably check if file editing is unlocked, can I?
- => maybe add this as an issue
- Some of the logic around downloads is not fully "intuitive". Do any of these bother us enough that i have to take care of them immediately or can i just document and postpone this?
- When a record file is deleted from zenodo and reuploaded, it will show as “downloaded” in the extension even when the downloaded file is outdated and the content does not match anymore.
- probably rare and not important, but most potential to confuse users
- When a record transitions from draft to published, the files will show as “not downloaded” even if it has been downloaded when the record was still in draft state
- probably very rare (because most users will use downloads only for public records)
- When files are uploaded to a record from the extension, they will show as “not downloaded” even though they are on the file system because they were uploaded from there
- common (happens whenever a user uploads a file) but questionable if this would actually confuse users
- => Are any of these cases important enough so that I should invest time in fixing them? If not, I can just e.g. document them somewhere
### Meet the student
"Meet the student: A slightly longer, individual video where you can introduce yourself and talk about your project, your experience and your results."
Example video from previous year: https://nextgentriggers.web.cern.ch/meet-the-students-sara-abdelrazeq
- => about 2 minutes
- I assume we have to prepare the script ourselves
- We probably also have to give the social media person some keypoints to put in the description of the post (see example) but she hasnt said anything about that, will ask
#### Initial draft for script (takes about 2min to read)
Hi, my name is Elisabeth Jüttner. I’m from Germany, and I’m studying for a master’s degree in computer science at the University of Bonn, where I also work as a student research assistant.
My project here at CERN focuses on improving the digital research environments used by scientists and making it easier to include open science in their everyday workflows.
Research involves much more than running experiments. Researchers also analyse data, write code, document their methods, collaborate with others, and eventually preserve and publish their results.
Research outputs can be shared through online platforms such as Zenodo. Zenodo is a generalist research repository developed and hosted at CERN. It allows researchers from many different disciplines to publish and preserve datasets, software, papers and other digital research outputs. It also makes these outputs citable and provides persistent identifiers for proper preservation. It has more than 400k (correct?) users and is used by researchers across the world.
The goal of my project is to integrate Zenodo into JupyterLab, which is an open source platform that allows scientists to combine code, data, visualisations, and computational results in one place.
The aim is to enable researchers to interact with Zenodo directly from the environment where they are already doing their work. For example, they should be able to discover existing research outputs, access datasets for their analysis, and share files they have created without constantly moving between separate platforms.
Our project is also fully open source. This means that I am not just creating a tool specific to CERN, but something that can be used and improved by anyone.
While this makes it more challenging because my tool needs to function across different deployments, I’m excited to see how the project can continue to develop and support more open, connected, and reproducible research.
Working at CERN openlab has also allowed me to collaborate with people from different scientific and technical backgrounds and has been an amazing experience.
