Changes between Version 40 and Version 41 of codesprint/201106-bolsena


Ignore:
Timestamp:
06/19/11 23:16:27 (14 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • codesprint/201106-bolsena

    v40 v41  
    119119 * Maybe some of these will get funded....which is perhaps the biggest wish of them all!
    120120 
    121 || Wish ID || Wish || Explanation ||
    122 || 1 || 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 ||
    123 || 2 || search customisation || saving and replaying searches ||
     121|| Wish ID || Wish || Explanation || Anyone else interested? ||
     122|| 1 || 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 || ||
     123|| 2 || search customisation || saving and replaying searches || ||
    124124|| 3 || fragments/subtemplate editing || Already the subject of proposal http://trac.osgeo.org/geonetwork/wiki/proposals/SubTemplates ||
    125 || 4 || tracking changes to metadata || See initial ideas for a simple history table above ||
    126 || 5 || investigate ESRI !GeoPortal and GeoNetwork interoperability || This would be useful not only for GeoNetwork developers in terms of looking at how someone else has implemented a catalog, but also to do a feature comparison ||
     125|| 4 || tracking changes to metadata || See initial ideas for a simple history table above || ||
     126|| 5 || investigate ESRI !GeoPortal and GeoNetwork interoperability || This would be useful not only for GeoNetwork developers in terms of looking at how someone else has implemented a catalog, but also to do a feature comparison || ||
    127127|| 6 || Better documentation of GeoNetwork api || Would be very useful for those wishing to get started on making enhancements and modifications ||
    128 || 7 || Support for schemaPlugins || Added in proposal http://trac.osgeo.org/geonetwork/wiki/pluginprofiles but may need additional work to support services that relate to a schema/profile - see above ||
    129 || 8 || Support for time zones in temporal search terms || Calendar widget needs to include timezone specification ||
    130 || 9 || Better support for selecting default editor tab || Although this appears to be supported in config-gui.xml, strange things happen if you switch off the simple mode editor for example (this is actually a bug I think) ||
    131 || 10 || Harvested records are not obvious in search results || Should appear in search results as visual indicator ||
    132 || 11 || Massive operations on thumbnails || Assign a thumbnail to, delete a thumbnail from one or more records ||
    133 || 12 || 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) ||
    134 || 13 || 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 ||
    135 || 14 || 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 ||
    136 || 15 || 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 ||
     128|| 7 || Support for schemaPlugins || Added in proposal http://trac.osgeo.org/geonetwork/wiki/pluginprofiles but may need additional work to support services that relate to a schema/profile - see above || ||
     129|| 8 || Support for time zones in temporal search terms || Calendar widget needs to include timezone specification || ||
     130|| 9 || Better support for selecting default editor tab || Although this appears to be supported in config-gui.xml, strange things happen if you switch off the simple mode editor for example (this is actually a bug I think) || ||
     131|| 10 || Harvested records are not obvious in search results || Should appear in search results as visual indicator || ||
     132|| 11 || Massive operations on thumbnails || Assign a thumbnail to, delete a thumbnail from one or more records || ||
     133|| 12 || 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) || ||
     134|| 13 || 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 || ||
     135|| 14 || 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 || ||
     136|| 15 || 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 || ||
    137137
    138138=== R&D ===