Changes between Version 28 and Version 29 of metadataworkflow


Ignore:
Timestamp:
Jan 2, 2012, 3:04:20 AM (12 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • metadataworkflow

    v28 v29  
    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 if the new state is 'Submitted', 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.
     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 if the new state is 'Submitted', the 'GeoNetwork 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{{{
     
    7676Subject: Metadata records APPROVED by reviewer@localgeonetwork.org.au (Reviewer)
    7777 on 2011-12-14T12:28:00
    78 To: "User One" <Simon.Pigot@csiro.au>
    79 Message-ID: <1064170697.31323826081004.JavaMail.root@pelion>
     78To: "User One" <userone@localgeonetwork.org.au>
     79Message-ID: <1064170697.31323826081004.JavaMail.geonetwork@localgeonetwork.org.au>
    8080Reply-To: Reviewer <reviewer@localgeonetwork.org.au>
    8181
     
    9999=== Backwards Compatibility Issues ===
    100100
    101 Metadata records receive status 'Unknown' by default if they don't have an existing status.
     101Existing Metadata records receive status 'Unknown' by default.
    102102
    103 In the past, editing a metadata record did not remove
     103In all versions prior to 2.7, editing a metadata record did not remove the privileges for the !GeoNetwork group 'All'. From 2.7 onwards, these privileges will be removed if the edit was not a 'Minor edit'.
    104104
    105105=== New libraries added ===