| 1 | || '''Date''' || 2010/03/25 || |
| 2 | || '''Contact(s)''' || Francois || |
| 3 | || '''Last edited''' || [[Timestamp]] || |
| 4 | || '''Status''' || Draft || |
| 5 | || '''Assigned to release''' || 2.5 || |
| 6 | || '''Resources''' || GéoSource [BRGM] || |
| 7 | || '''Ticket''' || || |
| 8 | |
| 9 | == Overview == |
| 10 | This proposal allows editor to add extent information based on keyword analysis. |
| 11 | In the editor a button is added to run the process : |
| 12 | 1. For each keywords |
| 13 | 1. Search for the keyword in thesaurus |
| 14 | 1. If keyword in the thesaurus has an extent |
| 15 | 1. Add an extent with a description and a bounding box to the metadata record. |
| 16 | |
| 17 | The process could be run in 2 modes : |
| 18 | * Add : Keep existing extent elements and add the new one at the end. Editor could clean the section after processing. |
| 19 | * Replace : Remove all extent having only a bounding box (temporal, vertical and bounding polygon are not removed), and add the new one at the end. |
| 20 | |
| 21 | |
| 22 | === Select your keywords === |
| 23 | |
| 24 | [[Image(bboxk-selectkeyword.png)]] |
| 25 | |
| 26 | === In edit mode, 2 new actions === |
| 27 | [[Image(bboxk-button.png)]] |
| 28 | |
| 29 | === After processing === |
| 30 | [[Image(bboxk-results.png)]] |
| 31 | |
| 32 | |
| 33 | |
| 34 | |
| 35 | |
| 36 | === Proposal Type === |
| 37 | * '''Type''': GUI |
| 38 | * '''App''': !GeoNetwork |
| 39 | * '''Module''': GUI |
| 40 | |
| 41 | === Links === |
| 42 | |
| 43 | * '''Email discussions''': |
| 44 | * '''IRC discussions''': |
| 45 | |
| 46 | === Voting History === |
| 47 | * Vote proposed by Francois the 22nd march 2010 |
| 48 | |
| 49 | == Proposal details == |
| 50 | Default configuration parameter is equivalent to current GeoNetwork behavior. |
| 51 | |
| 52 | Parameters are defined in config-gui.xml : |
| 53 | {{{ |
| 54 | <!-- Display or not category information : Categories are stored in the database and a metadata |
| 55 | record could be linked to one or more categories. --> |
| 56 | <category> |
| 57 | <!-- |
| 58 | To disable that feature |
| 59 | comment this out. This will hide categories in search criteria, |
| 60 | metadata editing and administration interface. |
| 61 | --> |
| 62 | <admin/> |
| 63 | |
| 64 | <!-- Display category as icon in search results. Categories could be : |
| 65 | * define from category table or |
| 66 | * define based on schema : iso19139 could be service or dataset and iso19110 is feature catalogue (internal category) |
| 67 | |
| 68 | mode attribute could be: |
| 69 | * all : all categories |
| 70 | * db : only from category table |
| 71 | * internal : only internal category |
| 72 | |
| 73 | <display-in-search mode="db"/> |
| 74 | --> |
| 75 | </category> |
| 76 | }}} |
| 77 | |
| 78 | |
| 79 | Icons could be added to images/category directory. |
| 80 | |
| 81 | |
| 82 | == Backwards Compatibility Issues == |
| 83 | None. |
| 84 | |
| 85 | == Risks == |
| 86 | |
| 87 | == Participants == |
| 88 | * Francois |