Changes between Version 20 and Version 21 of CMDI 1.2/Lifecycle management

Timestamp:

02/11/14 16:26:15 (10 years ago)

Author:

twagoo

Comment:

--

CMDI 1.2/Lifecycle management

@@ -77 +77 @@
 Status can be mapped to views, see [[ComponentVersioning#Viewsworkspacesandregistries|ComponentVersioning]]. Besides that, the Component Registry will have to provide inputs for the user to manage the status of their own components. Part of the information gathering can be automated (!DerivedFrom).
 
-'''Status filtering'''
+====== Status filtering ====== 
 The browsing mode of the Component Registry, as well as the REST service through which the list of components and profiles can be requested, needs te be filterable. Currently, there is a switch between private and public components. With the proposed set of status values, this needs to be revisited. A suitable paradigm seems to consist of two main views: components visible by the logged in user and components visible to the public - there may be an overlap. Then the following filter toggles are available for the latter view, both OFF by default:
 
@@ -83 +83 @@
 * deprecated components
 
-'''Usage warnings'''
+====== Usage warnings ====== 
 
 The default filter settings described above are the first and most important step in discouraging users to use non-production components. In addition, warnings can be given at two stages:
@@ -89 +89 @@
 * through a modal dialogue when a user actively decides to include such a component (through 'edit as new' or by dragging it into a component being edited)
 
-'''Automatic 'derived from''''
+====== Automatic 'derived from' ====== 
 
 When a component is created by selecting an existing component and clicking 'edit as new', the !DerivedFrom header value should automatically be populated with the ID of the original component. However it should be possible for the user to remove this or put another ID in place (but this should clearly be an advanced option!).
 
-'''Nice to haves'''
+====== Owner notifications ====== 
+The following automatic notifications would be nice to have:
+
 * Notification of component owners when a component referenced in one of their components becomes deprecated
 * Notification of component owners when a derivative of one of their components is created
+
+RSS or e-mail could be used as a means of notification
 
 ===== Tools: metadata editing =====