| 1 | | This is the test page |
| | 1 | = Metadata status: capturing the lifecycle of a metadata record = |
| | 2 | |
| | 3 | || '''Date''' || 2011/12/12 || |
| | 4 | || '''Contact(s)''' || Simon Pigot || |
| | 5 | || '''Last edited''' || 2011-12-12T19:10:00 || |
| | 6 | || '''Status''' || in progress || |
| | 7 | || '''Assigned to release''' || 2.7 || |
| | 8 | || '''Resources''' || Resources available || |
| | 9 | || '''Ticket #''' || #XYZ || |
| | 10 | |
| | 11 | == Overview == |
| | 12 | |
| | 13 | 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 during this workflow. This proposal is about: |
| | 14 | |
| | 15 | * adding state (or status) to records in GeoNetwork: 'Unknown', 'Draft', 'Submitted', 'Approved', 'Rejected', 'Retired' |
| | 16 | * providing email notifications to different users when status changes eg. when status changes from 'Draft' or 'Unknown' to 'Submitted' then all relevant 'Content Reviewers' are notified via email |
| | 17 | |
| | 18 | === Proposal Type === |
| | 19 | * '''Type''': GUI Change, Core Change |
| | 20 | * '''App''': !GeoNetwork |
| | 21 | * '''Module''': eg. Kernel, Data Manager, Metadata Import, Lucene Index, Search Interface |
| | 22 | |
| | 23 | === Voting History === |
| | 24 | * Not yet proposed for voting. |
| | 25 | |
| | 26 | ---- |
| | 27 | |
| | 28 | == Motivations == |
| | 29 | |
| | 30 | GeoNetwork already has some components of a metadata workflow in the form of: |
| | 31 | |
| | 32 | * users have a profile that gives them different levels of privilege over a metadata record eg. only a content reviewer (or admin) profile user can assign rights to a metadata record that would allow an unregistered user to see the record in search ie. only a content reviewer can assign rights to the special GeoNetwork groups 'All' or 'Internet' |
| | 33 | |
| | 34 | This proposal adds: |
| | 35 | * a status value to each metadata record describing its current state in a lifecycle that ranges from 'Draft' or 'Unknown' through 'Submitted', 'Approved', 'Rejected' and 'Retired' |
| | 36 | * Users with different profiles can set the status on one record through the or any number of selected records through the 'Actions on selected records' |
| | 37 | * Notification of status change to relevant users: |
| | 38 | * When an 'Editor' changes the state from 'Draft' or 'Unknown' to 'Submitted', the 'Content Reviewers' |
| | 39 | |
| | 40 | == Proposal == |
| | 41 | An in depth proposal can be found here : link |
| | 42 | ... |
| | 43 | |
| | 44 | === Backwards Compatibility Issues === |
| | 45 | |
| | 46 | === New libraries added === |
| | 47 | Explain which and why new libraries are required for that proposal ... |
| | 48 | |
| | 49 | == Risks == |
| | 50 | |
| | 51 | == Participants == |
| | 52 | * List of participants and role (if necessary) in current GIP |
