Dataset Versioning

[DavidBlaa]

Detailed user stories

• see Miro (link on request)

Scenarios/Settings to cover

• Type of version management (setting)

  • no (default): instances do not want to care; non-curated; current behavior
  • major: 1.0, 2.0
  • minor: 1.1, 1.2, 2.0

• Curated version management (setting)

  • no (default): user is allowed to set
  • yes: curation workflow - request to curator
  • q: Should it be more of a setting but behave like permission?
  • set flag for curated instances in the settings
  • access to edit version stuff - combination of feature, entity permissions and flag

• User permission

  • not logged in
  • logged in
  • logged in + edit

• combinations to consider: all permission & no or minor/major

Sub User Stories / Main Tasks

• [x] #1647
• [x] Creation / Editing of comments for all versions/releases
• [x] View of the history table
• [x] Access of versions via URL
• [x] Access of versions via API
• [x] Visibility (e.g., search)
• [ ] Request workflow & Curation view
• [ ] (automated) Integration with DOI

General Challenges

• update the dataset version without creating a new version (check, but should work)
• the latest visible tags could refer to older versions ( old always refer to older )
  • reduce filter options in the table view
  • performance issue for loading the table

Affected Modules / Feature

After adding the new concept of tagging versions, the system needs to update in different places to use the tags

• whenever a new version is created, the user wants to be able to enter a comment -> metadata edit / attachment upload / data upload / ....
• Search Index
• all API calls about Datasets
• DOI Workflow
• View Dataset
• MatView
• Curation view
• Constraint selection
• Entity selection

Related user stories

• [x] #1735
• [x] #1742
• [x] #1743
• [x] #1744

[ludmillafigueiredo]

I suggest replacing user stories #1640, #1641, #1642, #1643, which were written as examples in the dev/curator's meeting, with user stories #1735, #1742, #1743, #1744, written by me as product owner, following the user story template agreed on.

[geofranzi]

Thanks, I closed the four mentioned issues.

[DavidBlaa]

• rechte issues über separate Controller lösen