Changes between Version 5 and Version 6 of proposals/MetadataEditorSuggestion
- Timestamp:
- Jan 27, 2011, 10:34:40 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
proposals/MetadataEditorSuggestion
v5 v6 11 11 == Overview == 12 12 13 This proposal aims to '''improve metadata quality and help metadata editor make better metadata records'''. The main principle is to provide a set of suggestions based on metadata records analysis. A suggestion checks for a rules and improveprovide a mechanism to fix or improved the metadata record on a particular point.13 This proposal aims to '''improve metadata quality and help metadata editor make better metadata records'''. The main principle is to provide a set of suggestions based on metadata records analysis. A suggestion checks for one or more conditions and provide a mechanism to fix or improved the metadata record on a particular point. 14 14 15 15 Suggestions are defined on a schema basis and could be used on any kind of schema (iso19139 and others). … … 22 22 2) Analyze a metadata record according to a set of suggestions|processes 23 23 24 3) Trigger a particular process to apply the suggestion solutions (require metadata editor a ction)24 3) Trigger a particular process to apply the suggestion solutions (require metadata editor agreement) 25 25 26 26 27 27 Some examples of suggestions: 28 a) Explode keywords containing com a (ie. ',').28 a) Explode keywords containing comma (ie. ','). 29 29 30 b) Check if scale denominator contains '1/' or '1:' or ' ' and remove them.30 b) Check if scale denominator contains '1/' or '1:' or ' ' characters and remove them once triggered. 31 31 32 32 c) Compute extent if keyword of type place are available based on thesaurus analysis. (see http://trac.osgeo.org/geonetwork/wiki/BoundingBoxFromKeyword) … … 37 37 38 38 39 b) is already available since GeoNetwork 2.5.x but the "compute action" button is available even if no keyword of type pace exists. Suggestion analysis phase allows to only suggests actionrelevant to current metadata record in the editing session.39 b) is already available since GeoNetwork 2.5.x but the "compute extent" button is available even if no keyword of type pace exists. Suggestion analysis phase allows to only suggests actions relevant to current metadata record in the editing session. 40 40 41 41 … … 142 142 }</params> 143 143 }}} 144 (Basically JSON based in order to be easily processed by a JS client ).144 (Basically JSON based in order to be easily processed by a JS client to generate a form). 145 145 146 146 "gurl" and "lang" could be considered as reserved parameter's name and the client should automatically set these value to geonetwork http url (eg. http://localhost:8080) and lang to the current GUI language (and optionnaly hide them from end user). Default values are provided using XSL param default values. eg. … … 155 155 === Sample client interface for metadata suggestion === 156 156 157 A suggestion manager could use metadata.suggestion?id=currentMetadataId&action=list to retrieve the list of processes registered for the metadata schema. It could then check if processes have suggestions for the metadata record using metadata.suggestion?id=2&action=analyzeto analyze for all known processes or158 using metadata.suggestion?id=2&action=analyze&process=keywords-comma-exploderto analyze for only one process.157 A suggestion manager could use '''metadata.suggestion?id=currentMetadataId&action=list''' to retrieve the list of processes registered for the metadata schema. It could then check if processes have suggestions for the metadata record using '''metadata.suggestion?id=2&action=analyze''' to analyze for all known processes or 158 using '''metadata.suggestion?id=2&action=analyze&process=keywords-comma-exploder''' to analyze for only one process. 159 159 160 160 The result could be displayed as a list of elements:
