Manual curation logging

[tuli]

Is your feature request related to a problem? Please describe.
It's not really a problem. This ticket is to prompt a discussion about manual and automatic curation logging.

Describe the solution you'd like
I think most curation actions could results in automatic logging, with a manual log being used for exceptional or unusual events.
It would be good (if it's possible) for curators to edit an automatic log, to add any pertinent notes.

Describe alternatives you've considered
None.

Additional context
ticket arose from discussion in #1528

[only1chunts]

Thanks for starting the ticket @tuli , I've also added it to the Curation Tracking project, which includes more tickets about how we track who is doing what, when. That project will involve lots of changes to the curation logs so this discussion will fit well with that.

Some questions we should consider:

• Do we want EVERY little change we make logged?
  • If not, which things should / should not be logged?
• Should the curation log be public?
• Should the curation log be only for Pre-Publication datasets and then all the same things should then start being logged in the public dataset-History log instead of the curation log?

[rija]

Look into doing #54

[only1chunts]

The Miro Board here shows the workflow and includes various steps that should be automatically logged.
It does not show the points at which a curator OR user could make changes to the dataset, and those are the things we need to discuss about which should/should not be logged.

[pli888]

Seems like a workshop is required for people to discuss the requirements for a curation log tracking system. @only1chunts to organise with curators and or developers.

[only1chunts]

one thing that is definitely to go in the curation log is the when MintDOI button is clicked, see ticket #1667