Changes between Version 22 and Version 23 of metadataworkflow


Ignore:
Timestamp:
12/13/11 15:27:51 (13 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • metadataworkflow

    v22 v23  
    49493. 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:
    5050
    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. They can use the link supplied in the email to access the submitted records.
     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. They can log in and click on the link supplied in the email to access the submitted records.
    5252
    5353{{{
     
    6868}}}
    6969
    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). The email received by the metadata record owner looks like the following. Again, the link supplied in the email will allow the user to access the submitted records.
     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). The email received by the metadata record owner looks like the following. Again, the user can log in and use the link supplied in the email to access the approved/rejected records.
    7171
    7272{{{