Changes between Version 2 and Version 3 of HierarchicalKeywords


Ignore:
Timestamp:
Dec 14, 2009, 12:58:38 AM (15 years ago)
Author:
stegherr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • HierarchicalKeywords

    v2 v3  
    1010== Overview ==
    1111
    12 Currently keywords appear in a flat structure. It should be possible to create a first level keyword 'Geophysics' and a second level keyword 'DayLST' depending on the keyword 'Geophysics', both of them appear at the same level in the search box. Right now we enter the keywords as 'Geophysics | DayLST' but it means we cannot search on the 'Geophysics' keyword. It would be nice to have the possibility to search the keywords by level as displayed on the picture below:
     12Currently keywords appear in a flat structure. It should be possible to create a first level keyword 'Geophysics' and a second level keyword 'DayLST' depending on the keyword 'Geophysics', both of them appear at the same level in the search box. Right now we enter the keywords as 'Geophysics | DayLST' but it means we cannot search on the 'Geophysics' keyword. It would be nice to have the possibility to search the keywords by level as displayed on the pictures below:
    1313
    1414[[Image(Keywords_now.jpg)]] [[Image(Keywords_improved.jpg)]]
    … …  
    3030
    3131== Motivations ==
    32 The current configuration is .... A change to ....
     32The motivations for this change are:
     33
     34 * Less entries in search -> less confusion
     35 * Search for broader terms, which include second-level keywords possible
     36 * If necessary or too many results, drilling down to detail possible
    3337
    3438== Proposal ==
    35 An in depth proposal can be found here : link
    36 ...
     39The current thesaurus manager is storing keywords in SKOS/RDF format, which allows creating term relationships (e.g. skos:broader, skos:narrower, etc) between keywords.
     40
     41These relationships can be used to create a hierarchical structure between the keywords and list them according to this in the search interface.
     42
     43Further development can include using web service based thesauri instead of local ones.
    3744
    3845=== Backwards Compatibility Issues ===
    … …  
    4148
    4249== Participants ==
    43  * List of participants and role (if necessary) in current GIP
    44 
     50 * As above