embargo bundle without embargo, rename it to "collection", harmonise naming of things

[tilfischer]

Dear all,

Is your enhancement request related to a problem? Please describe. When users want to publish many reactions and samples (corresponding to a manuscript), they want to wrap them in a package that has its own DOI. This DOI will be referenced in a data availability statement of an article, while authors cannot add 20 DOIs to this statement in their manuscript. It has been possible to create such a package in Chemotion Repository for some time using the "Embargo Bundle" feature.

What is somehow missing is to get an embargo bundle DOI without an embargo. With the current terminology, this seems like a contradiction. Consequently, the naming of things might profit from some enhancements and at the same run this could be also harmonised how things are called.

In Publish Sample: (one sample)

--> here, it is called Embargo Bundle and Publish with Embargo Bundle.

Some samples:

--> here, TiFi_2022-11-28 is called Embargo

A sample:

--> here, TiFi_2022-11-28 is called data collection with DOI https://dx.doi.org/10.14272/collection/TiFi_2022-11-28 on the right side of the screenshot, while on the left it is called Embargo,

Describe the solution you'd like Give the same "thing" the same name and allow for "thing" DOIs without an embargo i.e. make it more transparent on the UI side. The term "embargo" would not fit anymore, if the "thing" must not necessarily have an embargo. I would suggest to call this "thing" Collection. Data is not needed, because this is what Chemotion is about.

For the second screenshot, Embargo could be substituted with Collection. For the third screenshot, data collection could be substituted with (solely) collection.

For the first screenshot, Publish with Embargo Bundle could be substituted with Create collection with/without embargo. This should create a collection (with a collection DOI at some time point) and may also allow to set an embargo period. Instead of only allowing for manually released embargos, as this is to the best of my knowledge currently the case, a drop-down list may allow to select an embargo period. RADAR does this and provide: 1 Month, 2 Month, 3 Month, 4 Month, ... 11 Month, 12 Month, 1 Year, while also 2 Years (and 3 Years) should be allowed and could be added. This would be an option to reduce user interaction and tackle the challenge that users forget to release their embargoed collections.

Moreover, unlimited embargo (or manually released) should be an option, to catch the current workflow as well as no embargo should be selectable.

If no embargo is selected, a checkbox should tell, "I know [or understand] that the collection that is submitted without the selection of an embargo period will be published immediately after a successful review."

Another check box could be added and displayed if an embargo (of any kind) is selected telling e.g., "I understand that the collection submitted with the selection of an embargo period will be published after the end of the embargo. The embargo period starts following a successful review."

Last but not least: For unlimited embargo period, "I understand that the collection submitted with the selection of an unlimited embargo period needs to be manually released after successful review to get published."

Consequently, the check box for samples or reactions to be published without being part of a collection should be rephrased e.g., "I know [or understand] that the data that is submitted which is not part of a collection and has no embargo period will be published immediately after a successful review"

Best, Tillmann