Changes between Version 9 and Version 10 of metadataworkflow

Timestamp:

Dec 12, 2011, 7:14:44 AM (13 years ago)

Author:

simonp

Comment:

--

metadataworkflow

@@ -11 +11 @@
 == Overview ==
 
-Metadata records have a lifecycle that typically goes through one or more states. eg when a record is created and edited by an 'Editor' user it is in the 'Draft' state. Whilst it is reviewed by a 'Content Reviewer' user it would typically be in a 'Submitted' state. If the record is found to be complete and correct by the 'Content Reviewer' it would be in the 'Approved' state and may be made available for casual search and harvest by assigning privileges to the !GeoNetwork 'All' group. Eventually, the record may be superseded or replaced and the state would be 'Retired'. At present !GeoNetwork doesn't have a formal process by which the state of the record can be captured and thus no workflow exists to take a metadata record through these states. This proposal adds:
+Metadata records have a lifecycle that typically goes through one or more states. eg when a record is created and edited by an 'Editor' user it is in the 'Draft' state. Whilst it is reviewed by a 'Content Reviewer' user it would typically be in a 'Submitted' state. If the record is found to be complete and correct by the 'Content Reviewer' it would be in the 'Approved' state and may be made available for casual search and harvest by assigning privileges to the !GeoNetwork 'All' group. Eventually, the record may be superseded or replaced and the state would be 'Retired'. At present !GeoNetwork doesn't have a formal process by which the state of the record can be captured. This makes it more difficult to manage and administer metadata records. This proposal adds:
 
- * state (or status) to records in !GeoNetwork: 'Unknown', 'Draft', 'Submitted', 'Approved', 'Rejected', 'Retired'. The status is held in a database table called !MetadataStatus 
- * two status change action hooks (in Java) that can be used by sites to provide specific behaviours: The first action (statusChange) is called when status is changed by a user eg. when 'Draft' records are set to 'Submitted' and could be used for example to send notifications to other users affected by this change. The second action (onEdit) is called when a record is edited and saved and could be used for example to reset records with an 'Approved' status to 'Draft' status. A default set of actions is provided.  
+ * state (or status) to records in !GeoNetwork: 'Unknown', 'Draft', 'Submitted', 'Approved', 'Rejected', 'Retired'. The status is held in a database table called !MetadataStatus. Extra states can be added to this table if required.
+ * two status change action hooks (in Java) that can be used by sites to provide specific behaviours: The first action (statusChange) is called when status is changed by a user eg. when 'Draft' records are set to 'Submitted' and could be used for example to send notifications to other users affected by this change. The second action (onEdit) is called when a record is edited and saved and could be used for example to reset records with an 'Approved' status to 'Draft' status. A default set of actions is provided. These can be customised or replaced by sites that wish to provide different or more extensive behaviour.  
   
 === Proposal Type ===