Entity View DOI Minting Broken
Description
In Synapse, you can "Create DOI for Entity View" to create a digital identifier pointing to a collection of files.
If a View Version has never been created (e.g. no versions), and a DOI is created by Entity View Tools menu, the DOI is automatically assigned a version of 1 (
10.7303/syn23662268.1). This creates a broken link (Snapshot not found) example:
The view version and DOI are not synced. Even worse, in my test case I created a view version 1 and the DOI link initially created re-directed to this view. The view now contains new, or incremented, file versions and potentially different data entirely.
Environment
Activity
Reported issue is fixed in staging.
I can’t reproduce it either.
If a DOI is minted on a view version, it does not show up in the UI; only if I click version history, I can see the DOI. I’m not suggesting it should, just noting that.
The unversioned fileview DOI points to the fileview in the state it was in when the DOI was minted. Is this desired for an unversioned view? I might expect it to behave like our Synapse files with versions, where a unversioned synId points to the most recent version.
You’re right , this is not the desired behavior. Unfortunately I wasn’t able to reproduce that. Do you have an example DOI you can share where this happens? If the DOI doesn’t have a version dot-number, then it should always resolve to the current version of the entity.
The DOI on a fileview with no version is now visible in the UI.
If I try to navigate to the fileview with the DOI, through doi.org for example, the DOI is no longer visible in the UI but that is obviously because the DOI points to our production site where the fix isn’t live yet!
Interestingly:
The unversioned fileview DOI points to the fileview in the state it was in when the DOI was minted. Is this desired for an unversioned view? I might expect it to behave like our Synapse files with versions, where a unversioned synId points to the most recent version.
Looking good. Created a DOI on fileview that had no version and it correctly showed afterwards, then on v1 correctly. Once in the createUpdateDoi dlg, looks like you can always pick any DOI but you get correct error (eg. if you pick one that already existed in a create operation it tells you). Will look more later. Note: not a regression, the behaviour in the dlg has not changed…
