| 1 | = Define parent/child, service/dataset and feature catalogue/dataset relation between metadata records = |
| 2 | |
| 3 | || '''Date''' || 2009/12/03 || |
| 4 | || '''Contact(s)''' || Francois || |
| 5 | || '''Last edited''' || [[Timestamp]] || |
| 6 | || '''Status''' || Draft || |
| 7 | || '''Assigned to release''' || 2.5 || |
| 8 | || '''Resources''' || GéoSource, geocat.ch projects || |
| 9 | || '''Ticket''' || TODO || |
| 10 | |
| 11 | == Overview == |
| 12 | Metadata records could be related together based on ISO elements. Examples: |
| 13 | * parent identifier |
| 14 | * operates on element for service metadata |
| 15 | |
| 16 | This proposal define a user interface to set 3 kinds of relation: |
| 17 | 1. dataset metadata / service metadata (including a link to the data based on WMS layer name) |
| 18 | 2. parent / child relation |
| 19 | 2. feature catalogue / dataset metadata |
| 20 | |
| 21 | === View mode === |
| 22 | |
| 23 | |
| 24 | === Editing user interface === |
| 25 | |
| 26 | |
| 27 | === Proposal Type === |
| 28 | * '''Type''': Editor |
| 29 | * '''App''': !GeoNetwork |
| 30 | * '''Module''': Editor |
| 31 | |
| 32 | === Links === |
| 33 | |
| 34 | * '''Email discussions''': |
| 35 | * '''IRC discussions''': |
| 36 | |
| 37 | === Voting History === |
| 38 | |
| 39 | * Vote proposed |
| 40 | * Votes: |
| 41 | |
| 42 | ---- |
| 43 | |
| 44 | |
| 45 | == Motivations == |
| 46 | * Easy editing |
| 47 | * Metadata navigation between related records |
| 48 | |
| 49 | == Proposal == |
| 50 | |
| 51 | |
| 52 | == Risks == |
| 53 | |
| 54 | == Participants == |
| 55 | * As above |
| 56 | |
| 57 | |
| 58 | |
| 59 | |