It would be helpful to be able to track title changes as they can cause deposit errors downstream and the problems can't be tracked backward to the change in title information.
Background
In a related issue (#711 (closed)), it was not possible to pinpoint issn changes in titles that caused deposit problems. As a result, the following was discussed:
The mystery is when the issn was removed from the admin since we don't keep a log of that (maybe we should add it to the log history?) so we don't know when it happened and what things got deposited weirdly in between.
Or we could have written the title update as a deposit type like doi transfers that include an uploaded file so that it left a history of what happened, when, and by whom.
We could add it to the admin, wouldn't know how exactly (although that might change with the new auth stuff) doesn't have to be deposited.
Definition of ready
-
Product owner: @SaraBowman -
Tech lead: -
Service:: label applied -
Definition of done updated -
Weight applied
Definition of done
-
Unit tests identified, implemented, and passing -
Code reviewed -
Available via a staging URL -
Knowledge base reviewed and updated -
Public documentation reviewed and updated -
Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed -
Acceptance criteria met -
AC 1 -
AC 2
-
Notes
Edited by Patrick Polischuk