Skip to content
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

operation logs: untrack some changes. #2395

Merged
merged 1 commit into from
Sep 28, 2021

Conversation

zannkukai
Copy link
Contributor

@zannkukai zannkukai commented Sep 21, 2021

Co-Authored-by: Renaud Michotte [email protected]

Code review check list

  • Commit message template compliance.
  • Commit message without typos.
  • File names.
  • Functions names.
  • Functions docstrings.
  • Unnecessary commited files?
  • Cypress tests successful?

@zannkukai zannkukai self-assigned this Sep 21, 2021
@github-actions github-actions bot added f: activity-logs Everything around logging user or system activities f: circulation Concerns the circulation interface or backend labels Sep 21, 2021
@zannkukai zannkukai added this to the v1.5.0 milestone Sep 21, 2021
@zannkukai zannkukai force-pushed the zan-fix-issue-1779 branch 2 times, most recently from 89a1aa4 to 4c5a217 Compare September 21, 2021 11:49
@iGormilhit iGormilhit changed the title operation log: untrack some changes. operation logs: untrack some changes. Sep 22, 2021
Copy link

@iGormilhit iGormilhit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commit message proposition:

operation logs: untrack some changes

* Some changes should not be tracked by an operation log (!= an
  operation log for loan history). If a circulation operation is done,
  this will change the related item status, but should not generate an
  operation log as it will be shown in the operation history on resource
  such as item or document. Furthermore, the circulation operation are
  already tracked.
* Use the Invenio extensions to manage operation log creation.
* Closes rero/rero-ils#1779.

@iGormilhit iGormilhit changed the base branch from dev to v1.5.0 September 23, 2021 12:35
@jma
Copy link
Contributor

jma commented Sep 27, 2021

Nice job!

Copy link
Contributor

@rerowep rerowep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to have an api end or cli function to display the operation logs ordered by date for a given type and pid.

* Some changes should not be tracked by an operation log (!= an
  operation log for loan history). If a circulation operation is done,
  this will change the related item status, but should not generate an
  operation log as it will be shown in the operation history on resource
  such as item or document. Furthermore, the circulation operation are
  already tracked.
* Use the Invenio extensions to manage operation log creation.
* Closes rero#1779.

Co-Authored-by: Renaud Michotte <[email protected]>
@github-actions github-actions bot added f: data migration Data migration from a legacy system or a previous version dev: DB Database structure (models.py) labels Sep 28, 2021
@zannkukai zannkukai merged commit 923efff into rero:v1.5.0 Sep 28, 2021
@zannkukai zannkukai deleted the zan-fix-issue-1779 branch September 28, 2021 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev: DB Database structure (models.py) f: activity-logs Everything around logging user or system activities f: circulation Concerns the circulation interface or backend f: data migration Data migration from a legacy system or a previous version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a request on an item should not update the operation logs
4 participants