-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Historie van vernietigingsproces bij vernietigde metadata #502
Open
2 tasks done
Comments
SilviaAmAm
added a commit
that referenced
this issue
Nov 29, 2024
SilviaAmAm
added a commit
that referenced
this issue
Nov 29, 2024
SilviaAmAm
added a commit
that referenced
this issue
Nov 29, 2024
SilviaAmAm
added a commit
that referenced
this issue
Nov 29, 2024
SilviaAmAm
moved this from In Progress
to Has Pull Request
in Open Archiefbeheer - Sprints
Nov 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://dimpact.atlassian.net/jira/software/c/projects/PZ/boards/258?selectedIssue=PZ-4263
Als Records manager
Wil ik de historie van de gevolgde vernietigingsprocedure opnemen in de export van de lijst vernietigde zaken
Zodat ik kan verantwoorden dat de juiste procedure is gevolgd
Acceptatie criteria:
Todo
TimelineLogs
objects with templatedestruction_list_reviewed
and extra_data containing "approved: True" and add to the table the name of the user, the role, the datetime, and a column with "has approved" (even though this is a table of approvals, there should be a column saying "has approved"). [#502] Add review process to destruction report #526[ ] Log changes: Get the initial number of zaken from theTimelineLog
object with templatedestruction_list_ready_for_first_review
. Then, get theTimelineLog
objects with templatedestruction_list_review_response_processed
and extra_datanumber_of_zaken
less than the initial number of zaken. Log how many zaken were removed. Q: Do we need to log info about which zaken were removed?The text was updated successfully, but these errors were encountered: