Changes between Version 66 and Version 67 of Bolsena2010

Timestamp:

05/18/10 16:52:44 (15 years ago)

Author:

heikki

Comment:

--

Bolsena2010

@@ -68 +68 @@
  || 46 || ||Search||Community is seeking a way to deal with varying granularity of metadata records, such that fine scale records don’t swamp fewer broad scale records. Many fine scale records (highly granular) make the metadata system more powerful (useful).  Being forced to limit granularity only as a work around for basic search result presentation/visualisation would be a shame. || ||
  || 47 || || Vocab / Thesaurus||Support for external vocabulary services Vocab services are becoming more common and an ability to connect to a custodians vocab service would be beneficial and reduce duplication and creation of stale vocabs/ thesauruses in GN. Action: An interface is required to query for vocab definitions from external sources. || heikki: proposes OWL/ebRIM integration, see [http://geonetwork.tv/owl/ http://geonetwork.tv/owl/] ||
- || 48 || ||Reusable Objects || Reusable (Controlled) Objects, allow fields to be reusable. Currently, if a user were to enter multiple records, for each record that user would have to re-enter “owner” their details. Worse, if that person’s details were to change, they remain the same in old records for which they have edited. The person’s details should be held as a managed object for which all records reference. This would allow the updating of details be reflected in each record that uses them - see the fragment harvesting of contact info above.|| ||
- || 49 || ||HTTPS support || HTTPS support. Currently all logins to !GeoNetwork are going unsecured through HTTP and the GN configuration doesn’t allow the use of HTTPS enabling account sniffing attacks.|| ||
+ || 48 || ||Reusable Objects || Reusable (Controlled) Objects, allow fields to be reusable. Currently, if a user were to enter multiple records, for each record that user would have to re-enter “owner” their details. Worse, if that person’s details were to change, they remain the same in old records for which they have edited. The person’s details should be held as a managed object for which all records reference. This would allow the updating of details be reflected in each record that uses them - see the fragment harvesting of contact info above.|| heikki: 3 ||
+ || 49 || ||HTTPS support || HTTPS support. Currently all logins to !GeoNetwork are going unsecured through HTTP and the GN configuration doesn’t allow the use of HTTPS enabling account sniffing attacks.|| heikki: 2 ||
  || 50 || ||CRS management || EPSG code data from external service Action: At the moment EPSG codes have to be entered manually, but external online services are available with that data. GN should utilize this.||François works on that recently? ||
- || 51 || || Hierarchical keywords|| Keywords from external vocabularies should utilize hierarchical broader/narrower structures to ease searching capability.|| ||
+ || 51 || || Hierarchical keywords|| Keywords from external vocabularies should utilize hierarchical broader/narrower structures to ease searching capability.|| heikki: proposes [http://geonetwork.tv/owl/ http://geonetwork.tv/owl/] ||
  || 52 || ||Indexation enhancement|| Using Apache Tika to index content from files attached to metadata records in !GeoNetwork?|| ||
- || 53 || ||Indexation enhancement || Replace Lucene interface in GN with Apache Solr?|| ||
+ || 53 || ||Indexation enhancement || Replace Lucene interface in GN with Apache Solr?|| heikki: 1 ||
  || 54 || ||Schema management || !SchemaManager - redesign proposed by Mathieu: * use org.geonetwork.utils.xsd.XSD in the project "geonetwork-services-ebrim" to read schemas and query contents for driving the editor * GN uses a number of schemas for validation purposes eg. in OAI, could these be managed by schemamanager so that they do not need to be retrieved from net? * sometimes a document may introduce a new schema eg. !ListSets response in OAI harvester can introduce the oai_dc schema eg. when harvesting jOAI - if we need to validate these responses then creating a validator with a file based schema will cause the validation to fail as the schema is not present on disk, alternative to is create a validator with no file based schema which means that all schemas will be obtained from the net but use an entityResolver object to intercept those which are local so as to avoid unnecessary retrieval or perhaps use a Java Cache System (JCS) instance to cache all schemas locally like XLinks?|| ||
  || 55 || || Multi-editing || Attempting to introduce the ability to edit more than one document makes existing trunk interface confusing eg. editing documents in tabs both of which have login details. Things get out of sync - what to do? Maybe something like BlueNetMEST which is based on one window - the main search window (tabs for remote, advanced and mapviewer) with search results - editing/viewing by clicking on title opens editor/viewer in new window (multiediting is supported), clicking any of the menu options on main screen uses modalbox dialog and separate windows to keep search interface and results window untouched, log out/log in closes all editor/viewer windows to close, if editing in progress log out not allowed - this is not perfect but might be a way of thinking about how to introduce things like multiediting to trunk.  || ||
- || 56 || ||Customization || Improve CSS management, clean CSS file and references to unused styles, replacing tables by divs, discuss on [wiki:ThemeCustomization]|| ||
- || 57 || ||Maven migration ||Move to Maven as described here : [wiki:Maven] ||Mathieu (major) ||
- || 58 || ||Settings management || While at it can we change the code so that you can save settings from the GUI even if not all expected settings are present in your database?|| ||
+ || 56 || ||Customization || Improve CSS management, clean CSS file and references to unused styles, replacing tables by divs, discuss on [wiki:ThemeCustomization]|| heikki: 1 ||
+ || 57 || ||Maven migration ||Move to Maven as described here : [wiki:Maven] ||Mathieu (major) | heikki: 1 |
+ || 58 || ||Settings management || While at it can we change the code so that you can save settings from the GUI even if not all expected settings are present in your database?|| heikki: 1 ||
  || XX || || || || ||