Feature Request: Enhanced Metadata for Curation Files

[berntpopp]

Summary:

Introduce additional metadata fields to curation files in the curation collection to provide better tracking and accountability of the curation process.

Description:

To enhance the traceability and accountability of curations, it's essential to include additional metadata within each curation file. This metadata should encompass creation and update dates, the curation schema used, and the users involved in the curation process. Additionally, we should explore the feasibility of maintaining a history of all curation files, even upon updates, and referencing the original file an update is based upon.

Acceptance Criteria:

• [x] Each curation file should include fields for the creation date, last update date, and the curation schema version used.
• [x] Each curation file should record the usernames or identifiers of all users involved in the curation.
• [ ] Explore and potentially implement a system to keep all versions of curation files, referencing the original file upon which an update is based.
• [ ] Ensure that the system for maintaining historical versions is efficient and doesn't lead to unnecessary clutter or confusion.

User Stories:

• As a curator, I want to see when a curation was created and last updated to understand its timeliness and relevance.
• As a team lead, I want to know which users have contributed to a curation to recognize contributions and maintain accountability.
• As an auditor, I want to access the history of curation files to understand the evolution and rationale behind changes.

Technical Notes:

• Implement fields for creation date, last update date, and curation schema version in the curation file structure.
• Develop a method for securely and efficiently recording user involvement in the curation process.
• Explore database capabilities for maintaining historical records of files and referencing previous versions.

Potential Challenges:

• Ensuring the accuracy and security of user data involved in the curation.
• Managing the increased storage requirements and complexity of maintaining a complete version history for curation files.
• Designing a user-friendly system for accessing and understanding the history and evolution of curation files.

Future Extensions:

• Develop a timeline or version tree visualization for curators to easily understand the history of a curation file.
• Implement alerts or notifications when a curation file has been updated or when a new version is available.
• Consider integrating with version control systems to leverage existing tools and practices for maintaining historical records.

---

By enhancing the metadata for curation files and potentially maintaining a complete version history, we aim to improve the transparency, accountability, and quality of the curation process.

[berntpopp]

This has to be implemented in the respective store based on the workflow config files.

[berntpopp]

Split the issue and make the part "implement a system to keep all versions of curation files" a own issue to implement later.

[berntpopp]

Make the implementation of the schemes into the respective stores an onw issue.

[berntpopp]

There needs to be a system to check and disallow duplicate entities.