[jboss-jira] [JBoss JIRA] Updated: (JBRULES-646) Archiving (deletion) of assets, packages, states and categories

[Michael Neale (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBRULES-646?page=all ]

Michael Neale updated JBRULES-646:
----------------------------------

    Description: 
Archiving means we don't physically delete anything. 
Physical deleting will only ever happen by system administrators.

Archiving works by marking an item in JCR as archived, and then the GUI/service methods ignore the archived items (except when they are loaded up when viewing an hisitorical asset).

How to do this: 
* Modify the .cnd files in the repository to have a binary archive flag (default to false) - this includes , rules (assets), states, categories, packages.
* Modify RulesRepository (in drools-repository) functionality to honour this archived flag. Thus when the flag is set, the item will not be shown in a list that is returned (or iterator). 
  - AssetItems: when loading a list of assets from a category, or package this can be filtered out by looking at the flag. When listing the assets in a package, the query can be modified to look at that flag. You can't "un-archive" items - if you try to create one of the same, it will then automatically un-archive it.
  - CategoryItem: archived items are ignored, if you try to use a "archived" category then it will un-archive them. If you try to create a category of the same name as an archived one, it will just un-archive it.
 - StateItem: same as category. 
* Modify drools-repository to have the ability to show lists of assets with OR without archived items. 

* drools-jbrms front end should then be modified to have a checkbox when displaying lists of assets, to include archived ones. 
* drools-jbrms Package management screen to be modified to have a checkbox to show archived packages or not. 

* Performance concerns: as the number of archived items grows, this may slow query times for large rule sets - may need to consider moving archived items.

Future enhancement: items that have been archived for a long time may be deleted. 


  was:
Archiving means we don't physically delete anything. 
Physical deleting will only ever happen by system administrators.

Archiving works by marking an item in JCR as archived, and then the GUI/service methods ignore the archived items (except when they are loaded up when viewing an hisitorical asset).

How to do this: 
* Modify the .cnd files in the repository to have a binary archive flag (default to false) - this includes , rules (assets), states, categories, packages.
* Modify RulesRepository (in drools-repository) functionality to honour this archived flag. Thus when the flag is set, the item will not be shown in a list that is returned (or iterator). 
  - AssetItems: when loading a list of assets from a category, or package this can be filtered out by looking at the flag. When listing the assets in a package, the query can be modified to look at that flag. You can't "un-archive" items - if you try to create one of the same, it will then automatically un-archive it.
  - CategoryItem: archived items are ignored, if you try to use a "archived" category then it will un-archive them. If you try to create a category of the same name as an archived one, it will just un-archive it.
 - StateItem: same as category. 
* Modify drools-repository to have the ability to show lists of assets with OR without archived items. 

* drools-jbrms front end should then be modified to have a checkbox when displaying lists of assets, to include archived ones. 
* drools-jbrms Package management screen to be modified to have a checkbox to show archived packages or not. 



> Archiving (deletion) of assets, packages, states and categories
> ---------------------------------------------------------------
>
>                 Key: JBRULES-646
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-646
>             Project: JBoss Rules
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>
> Archiving means we don't physically delete anything. 
> Physical deleting will only ever happen by system administrators.
> Archiving works by marking an item in JCR as archived, and then the GUI/service methods ignore the archived items (except when they are loaded up when viewing an hisitorical asset).
> How to do this: 
> * Modify the .cnd files in the repository to have a binary archive flag (default to false) - this includes , rules (assets), states, categories, packages.
> * Modify RulesRepository (in drools-repository) functionality to honour this archived flag. Thus when the flag is set, the item will not be shown in a list that is returned (or iterator). 
>   - AssetItems: when loading a list of assets from a category, or package this can be filtered out by looking at the flag. When listing the assets in a package, the query can be modified to look at that flag. You can't "un-archive" items - if you try to create one of the same, it will then automatically un-archive it.
>   - CategoryItem: archived items are ignored, if you try to use a "archived" category then it will un-archive them. If you try to create a category of the same name as an archived one, it will just un-archive it.
>  - StateItem: same as category. 
> * Modify drools-repository to have the ability to show lists of assets with OR without archived items. 
> * drools-jbrms front end should then be modified to have a checkbox when displaying lists of assets, to include archived ones. 
> * drools-jbrms Package management screen to be modified to have a checkbox to show archived packages or not. 
> * Performance concerns: as the number of archived items grows, this may slow query times for large rule sets - may need to consider moving archived items.
> Future enhancement: items that have been archived for a long time may be deleted. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira