Changes between Version 21 and Version 22 of ChangesFromNGR


Ignore:
Timestamp:
Aug 24, 2009, 5:58:52 AM (15 years ago)
Author:
heikki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ChangesFromNGR

    v21 v22  
    2020'''5.''' Tabbed view of Metadata[[BR]]
    2121'''6.''' Local rating[[BR]]
     22'''7.''' Relevance as a percentage[[BR]]
    2223
    2324Another change proposal (INSPIRE support) will be separately described by [http://wiki.osgeo.org/wiki/User:Fxp Francois] and [http://wiki.osgeo.org/wiki/User:Heikki Heikki]. Yet another change proposal (replacing !InterMap by !OpenLayers) is already described [http://trac.osgeo.org/geonetwork/wiki/ReplacingIntermap here].
     
    3536
    3637=== Voting History ===
    37 Although presented together in one proposal, all 6 items will be put up for voting separately.
     38Although presented together in one proposal, all 7 items will be put up for voting separately.
    3839 * None as yet
    3940
     
    4950'''5.''' Better usability[[BR]]
    5051'''6.''' Local user feedback[[BR]]
    51 
     52'''7.''' Better usability[[BR]]
    5253
    5354
     
    6061A second performance gain is effected by a change to retrieving the regions data in the search service. In standard !GeoNetwork, the regions are retrieved from the DB at each search request; in this proposal, it happens only once, after which the regions data is kept in memory for application lifetime.[[BR]][[BR]]
    6162Performance metrics from [http://www.yourkit.com/ YourKit Java Profiler] show that this change leads to a 90% performance increase of the search service as such (excluding the creation of the search results page).
     63[[BR]][[BR]]
    6264
    6365'''2. Persistent validation results'''[[BR]]
     
    6769An icon indicating the validation status, that links to the validation report if the metadata is not valid, can be included in the search results page an/or in the show metadata page. This indicates something about the quality of the metadata to users, and may encourage metadata providers to produce more valid metadata.[[BR]][[BR]]
    6870TODO add screenshot
     71[[BR]][[BR]]
    6972
    7073'''3. Organizations'''[[BR]]
     
    7376TODO add class diagram[[BR]]
    7477[[Image(ngr.organizationpage.png)]]
     78[[BR]][[BR]]
    7579
    7680'''4. Service monitoring'''[[BR]]
     
    7882The uptime results for services are also claculated for all the services provided by one organization. On the Organizations page, this is displayed.
    7983TODO add screenshots
     84[[BR]][[BR]]
    8085
    8186
     
    8489[[Image(ngr.tabs.metadata.show.png)]][[BR]]
    8590TODO compare with BlueNetMEST
     91[[BR]][[BR]]
    8692
    8793'''6. Local rating'''[[BR]]
    8894In !GeoNetwork, users can rate metadata. The user's rating is broadcast to all !GeoNetwork nodes known to the one where the rating happens, and the results are thus shared between nodes. In [http://nationaalgeoregister.nl NGR] this does not happen and the rating is simply kept and calculated on only the user ratings on the GN node itself. This proposal wants to make this "local" rating behaviour an option to standard !GeoNetwork, configurable through the Admin interface.
     95[[BR]][[BR]]
     96
     97'''7. Relevance as a percentage'''[[BR]]
     98In standard !GeoNetwork search results can be ordered by relevance. This is based on the relevance score that the Lucene search engine gives to each item in the search results. However it is not shown to the user what the relevance score for each result *is*.[[BR]]
     99In [http://nationaalgeoregister.nl NGR] the relevance score is displayed with each search result. Because the Lucene score is an unattractive float between 0 and 1, the relevance score is normalized such that the highest score from the search results is set to 100, and all other results' scores are calculated relative to that.[[BR]]
     100[[Image(ngr.relevance.percentage.png)]][[BR]]
     101[[BR]][[BR]]
    89102
    90103
     
    97110'''5.''' none[[BR]]
    98111'''6.''' none[[BR]]
    99 
     112'''7.''' if implementations use the raw Lucene score for anything, this will be broken (not in standard !GeoNetwork)[[BR]]
    100113
    101114== Risks ==