Changes between Version 20 and Version 21 of metadataworkflow


Ignore:
Timestamp:
Dec 12, 2011, 6:28:37 PM (12 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • metadataworkflow

    v20 v21  
    3333This proposal adds to these components with:
    3434
    35  * a status value for any metadata record describing its current state in a lifecycle that ranges from 'Draft' or 'Unknown' through 'Submitted', 'Approved', 'Rejected' and 'Retired'. All status changes are kept in the !MetadataStatus table with the most recent status change being the current status. These states are localized and extra states can be added by adding additional status values to the '!StatusValues' and '!StatusValuesDes' tables.
    36  * Users with different profiles can set the status on one record through the 'Other Actions' menu
     351. A status value for any metadata record describing its current state in a lifecycle that ranges from 'Draft' or 'Unknown' through 'Submitted', 'Approved', 'Rejected' and 'Retired'. All status changes are kept in the !MetadataStatus table with the most recent status change being the current status. These states are localized and extra states can be added by adding additional status values to the '!StatusValues' and '!StatusValuesDes' tables.
     36
     372. Users with different profiles can set the status on one record through the 'Other Actions' menu
    3738
    3839[[Image(status-actions.png)]]
    … …  
    4647[[Image(status-interface.png)]]
    4748
    48  * A default pair of metadata status change actions defined in Java - see the class org.fao.geonet.services.metadata.!DefaultStatusActions.java
    49    * The first change action is called when a status change is required. The default action taken depends on the status change taking place:
    50      * when an 'Editor' changes the state on a metadata record(s) from 'Draft' or 'Unknown' to 'Submitted', the Content Reviewers from the groupOwner of the record are informed of the status change via email which looks like the following: {{{
     493. A default pair of metadata status change actions defined in Java - see the class org.fao.geonet.services.metadata.!DefaultStatusActions.java. The first change action is called when a status change is required. The default action taken depends on the status change taking place:
     50
     51 * when an 'Editor' changes the state on a metadata record(s) from 'Draft' or 'Unknown' to 'Submitted', the Content Reviewers from the groupOwner of the record are informed of the status change via email which looks like the following:
     52
     53{{{
    5154
    5255Date: Tue, 13 Dec 2011 12:58:58 +1100 (EST)
    … …  
    6467
    6568}}}
    66      * when a 'Content Reviewer' changes the state on a metadata record(s) from 'Submitted' to 'Accepted' or 'Rejected', the owner of the metadata record is informed of the status change via email AND the group 'All' is assigned all privileges except 'Editing' (ie. the record is publicly accessible)
    67    * The second status change action is when a record is edited and saved by a user. The default action taken applies to any metadata record with status 'Approved' and resets the status to 'Draft' then removes the privileges for the !GeoNetwork group 'All'.
    68    * These actions can be replaced with different behaviours by:
    69      * writing Java code in the form of a new class that implements the interface defined in org.fao.geonet.services.metadata.!StatusActions.java and placing a compiled version of the class in the !GeoNetwork class path
    70      * defining the name of the new class in the statusActionsClass configuration parameter in WEB-INF/config.xml
    71  * Metadata status along with the status change date is indexed in Lucene. The 'Advanced Search' interface has an additional 'Restrict to' option that allows search on status values. CSW search can also search on Metadata status by defining queries using the _status property name.
     69
     70 * when a 'Content Reviewer' changes the state on a metadata record(s) from 'Submitted' to 'Accepted' or 'Rejected', the owner of the metadata record is informed of the status change via email AND the group 'All' is assigned all privileges except 'Editing' (ie. the record is publicly accessible)
     71
     72The second status change action is when a record is edited and saved by a user. The default action taken applies to any metadata record with status 'Approved' and resets the status to 'Draft' then removes the privileges for the !GeoNetwork group 'All'.
     73
     74These actions can be replaced with different behaviours by:
     75 * writing Java code in the form of a new class that implements the interface defined in org.fao.geonet.services.metadata.!StatusActions.java and placing a compiled version of the class in the !GeoNetwork class path
     76 * defining the name of the new class in the statusActionsClass configuration parameter in WEB-INF/config.xml
     77
     784. Metadata status along with the status change date is indexed in Lucene. The 'Advanced Search' interface has an additional 'Restrict to' option that allows search on status values. CSW search can also search on Metadata status by defining queries using the _status property name.
    7279   
    7380