Store a dedicated date during the registration of metadata within the data manager #1276
Description
What are you missing?
Currently we don't store a dedicated registration date for the following entities within the data manager:
1.) Project
2.) Experiment
3.) Sample (Can be inferred from batch registration, however there we lose the granularity if samples are added to an existing batch, since batch creation date will not change only its modification date)
Why do you need a solution?
Track the usage of the data manager is crucial to see the performance of the application within it's user base. One KPI in this context is investigating on how much metadata is registered within the data manager over time. This is also key for reporting its adaption by the userbase to our stakeholders.
Additionally, it helps our users to track the timing of their project management process in collaborative settings.
Ideas
1.) Add a column within the database storing the registration date similiar on how it is handled in the measurement case.
2.) Show the registration date for experiments and projects within the data manager
Code of Conduct
- I agree to follow this project's Code of Conduct