Changes between Version 36 and Version 37 of codesprint/201106-bolsena


Ignore:
Timestamp:
Jun 19, 2011, 7:34:40 AM (13 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • codesprint/201106-bolsena

    v36 v37  
    116116
    117117|| Wish || Explanation ||
    118 || faceted search || Search based on stats for terms indexed in Lucene - eg of facted search is http://well-formed-data.net/experiments/elastic_lists/ and most likely support for faceted search is the aim of the proposal by Francois http://trac.osgeo.org/geonetwork/wiki/NarrowYourSearchWidget - see also SOLR above ||
     118|| faceted search || Search based on stats for terms indexed in Lucene - eg of faceted search is http://well-formed-data.net/experiments/elastic_lists/ and most likely support for faceted search is the aim of the proposal by Francois http://trac.osgeo.org/geonetwork/wiki/NarrowYourSearchWidget - see also SOLR above ||
    119119|| search customisation || saving and replaying searches ||
    120120|| fragments/subtemplate editing || Already the subject of proposal http://trac.osgeo.org/geonetwork/wiki/proposals/SubTemplates ||
    … …  
    129129|| Editor tabs to be redesigned to suggest entry workflow || Should suggest a workflow through the metadata rather than an arbitrary grouping of elements based on the standard - an example of what is desired can be seen in the ANZMETLite editor (written in VB.Net) - download from http://geonetwork.globaldial.com/testdownloads/ANZMETLite_MCP_ALA.zip (warning: will only work under windows) ||
    130130|| More thought on how to integrate GeoNetwork with existing business systems in an organisation || Particularly important if GeoNetwork is seen as a tool for managing an organisations metadata as opposed to simply publishing an organisations metadata to the rest of the world ||
     131|| Harvest History mechanism for existing harvester manager || See proposal at http://trac.osgeo.org/geonetwork/wiki/HarvestingHistory which has been implemented in the ANZMEST sandbox - trunk support depends on whether the proposal to rewrite the harvesters and harvester interface is to be completed for 2.7 or not ||
     132|| Harvest Z3950 configuration from ISO19119 service metadata records || Rather than include a fixed configuration file describing Z3950 services, this configuration should be built by harvesting ISO19119 records and creating the config file - implemented in ANZMEST sandbox ||
    131133
     134 * Does anyone else share the same wishes? Is anyone else working on implementing any of these wishes?
    132135
    133136 * ...