[SHA-315] [Delete] Delete an existing Model Created: 08-Jul-14 Updated: 17-Jul-20 Resolved: 01-Apr-15
|Reporter:||Mike Farman||Assignee:||Closed Issues|
|Σ Remaining Estimate:||0 minutes||Remaining Estimate:||Not Specified|
|Σ Time Spent:||2 days, 6 hours, 30 minutes||Time Spent:||Not Specified|
|Σ Original Estimate:||2 days, 7 hours||Original Estimate:||Not Specified|
|Epic Link:||Custom Model Management|
|Sprint:||CMM Sprint 3, CMM Sprint 4, CMM Sprint 5|
"As a model manager I can delete a property group definition if it is in the DRAFT, DEPLOYED or PURGED states" so that it no longer appears in the list of Property Groups"
|Comment by David Draper [X] (Inactive) [ 31-Oct-14 ]|
Mike Farman The concept of disabling a group was something that I discussed with JN.... I also think it would be useful to have a "DRAFT" state as well, to prevent a Property Group being used before it is ready. There definitely needs to be a well established life-cycle for them.
|Comment by Mike Farman [ 31-Oct-14 ]|
David Draper [X]Yep, absolutely having a life-cycle makes a lot of sense
|Comment by David Draper [X] (Inactive) [ 04-Nov-14 ]|
I was thinking about the lifecycle stages and think we should have (as a minimum):
|Comment by Andrew Hind [X] (Inactive) [ 07-Nov-14 ]|
The life-cycle stages are fine but I would like more clarity on what they mean and what may affect the transitions.
Are there life-cycles for models and the things the model contains?
In the DRAFT stage the models and all they contain will not be in the dictionary as they are not active.
I am not clear if property groups are independent or can inherit/combine others which introduces life-cycle relationships.
DEPLOYED -> ACTIVE is an uncontrolled transition - and could happen at any time.
Currently all models loaded in the dictionary will only allow limited changes to be applied unless they are removed first.
Restrictions upon changes that can be made to ACTIVE models I believe are addressed in the CMIS 1.1 spec.
DISABLED on the repository seems to imply deprecation of some sort. The aspect can exists but can NOT be applied.
I would prefer a state where the aspect/property is being purged/removed.
|Comment by Mike Farman [ 25-Nov-14 ]|
The intention at this stage is manage the model lifecycle from a UI perspective only, it would still be possible to work with the model that was disabled i.e. programatically, at least for this user story. Enforcement of livecycle states at the repo level should be address as a separate set of stories.
For this story, a deletion would require a DB query to check for the usage of the property group i.e. it's aspect(s) (maxitems>=1). If, it was in use an error along the lines of "cannot be deleted, property group (or aspect name(s)) in use". The is not an expectation that any any automatic cleanup/removal is provided as part of this story. It would be up to an admin to tidy this up.
|Comment by Christine Thompson [X] (Inactive) [ 22-Apr-15 ]|
Setting Fix Version for first release