Task #6339 (new)
Opened 13 years ago
Last modified 12 years ago
chgrp: log modifications
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | major | Milestone: | Unscheduled |
Component: | General | Version: | n.a. |
Keywords: | n.a. | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
Whether copy (#6297) or unlink is used when chgrp'ing complicated graphs, the event log should record what exactly happened. One option would be to record all the chgrp (and by extension, delete) actions in a file and then add the file to the eventlog:
id | entitytype | entityid | action | record 1 | Image | 199 | CHGRP | OriginalFile:123
Alternatively, all the values could be recorded in long form in the eventlog, but some basic checks should be made to see if:
- the values will be sufficiently queryable
- if a chgrp actions will overwhelm the size of the eventlog, in which case a separate table may need to be used.
Change History (5)
comment:1 Changed 13 years ago by jburel
comment:2 Changed 13 years ago by jburel
- Milestone changed from OMERO-Beta4.3.2 to OME-5.0
comment:3 Changed 12 years ago by jmoore
- Milestone changed from OMERO-Beta4.4 to OMERO-Beta4.4.1
Won't be making further changes in 4.4.0
comment:4 Changed 12 years ago by jburel
Referencing ticket #8100 has changed sprint.
comment:5 Changed 12 years ago by jmoore
- Milestone changed from OMERO-4.5 to Unscheduled
Moving to unscheduled with and in #8100
Referencing ticket #3532 has changed sprint.