Our duplicate entry check currently just checks if there is several times the same url string in our nfdi4bioimage.yml. But for zenodo entries there can be different versions of the same training resource and all of these versions have a different child-url. The parent-url should be extractable using the zenodo API. We have different versions to solve this problem:
- Use the parent-url
- Use child-url and metadata of the latest version and discard all other child-urls as well as the parent-url
- List all urls that exist (parent-url and child-urls) in one entry
I will try to look into option 1, because then we have one url per zenodo entry which is permanent and lines per entry.
An example where this Issue occurs is this training resource: https://zenodo.org/records/15858127
Our duplicate entry check currently just checks if there is several times the same url string in our nfdi4bioimage.yml. But for zenodo entries there can be different versions of the same training resource and all of these versions have a different child-url. The parent-url should be extractable using the zenodo API. We have different versions to solve this problem:
I will try to look into option 1, because then we have one url per zenodo entry which is permanent and lines per entry.
An example where this Issue occurs is this training resource: https://zenodo.org/records/15858127