Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
04/24/13 14:55:41 (11 years ago)
- Author:
-
jamoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
- Property Cc wmoore ux@… added
-
|
initial
|
v1
|
|
| 1 | | Multi-file images (MFIs) are logically grouped into filesets during import time. The clients (Insigh, Web) need to provide the user with feedback when work is done with MFIs. |
| | 1 | Multi-file images (MFIs) are logically grouped into filesets during import time. The clients (Insigh, Web) need to provide the user with feedback when certain operations are performed on them. |
| | 2 | |
| | 3 | == Current state == |
| | 4 | |
| | 5 | The 2 primary operations under consideration are chgrp and delete. |
| | 6 | |
| | 7 | **Chrgrp** is an issue since it is not currently possible to have the same underlying binary data (the original filesets) contained in 2 separate groups. Therefore if one image from an MFI is moved to another group, it will become unviewable. Therefore, for demo 2, the chgrp operation was completely disallowed. |
| | 8 | |
| | 9 | **Delete** is an issue because a user may accidentally delete more data than was intended. One image of an MFI present in a dataset that is being deleted, does not guarantee that the user intended to delete all the other images in the MFI in all datasets. The current state of delete as of demo 3 is that dangerous deletes are permitted. |
| | 10 | |
| | 11 | == Goals for demo 4 == |
| | 12 | |
| | 13 | Primarily, this story is about getting these permission-related operations for MFIs into a generally releasable state. There are further, more extensive solutions possible (including deep copies and an abstracted IO system) but these will only be considered once base functionality is in a "safe" state. The changes to bring us there include: |
| | 14 | |
| | 15 | * graph definitions on the server should be conservative by default, preventing users from doing things they don't expect; |
| | 16 | * clients need to be aware of this conservative behavior and inform users of possible corrective actions; |
| | 17 | * and where possible, clients should provide users feedback (and "training") about what MFIs via subtle hints in the UI. |
| | 18 | |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.15217 sec.)
