Changes between Version 70 and Version 71 of Bolsena2010


Ignore:
Timestamp:
May 19, 2010, 2:17:31 AM (14 years ago)
Author:
josegar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Bolsena2010

    v70 v71  
    2222 ||Id || Priority || Topics || Comments || People interested In||
    2323 ||1 || ||Javadoc ||let's clean up the existing Javadoc and add new where it is missing. It'd be good to [http://java.sun.com/j2se/javadoc/ familiarize yourself] with how Javadoc works, before doing this; e.g. there should be no blank line between the Javadoc and the method it is about; the first sentence should end in a period; and things like that. || heikki: 4 ||
    24  || 2 || ||harvesters || Let's remove the harvesters' configuration from the "settings" table to its own, first-class-citizen table. Now, if you have many harvesters, it is nigh impossible to find anything in "settings". || heikki: 1 ||
    25  ||3 || || harvesters  || Related to before topic: rewrite harvesters client side code to remove unrequired ajax stuff. Just make "normal" forms for harvesters maintainment avoiding using ajax, except if really required for any functionality. || heikki: 1 ||
     24 || 2 || ||harvesters || Let's remove the harvesters' configuration from the "settings" table to its own, first-class-citizen table. Now, if you have many harvesters, it is nigh impossible to find anything in "settings". || heikki: 1 | jose: critical ||
     25 ||3 || || harvesters  || Related to before topic: rewrite harvesters client side code to remove unrequired ajax stuff. Just make "normal" forms for harvesters maintainment avoiding using ajax, except if really required for any functionality. || heikki: 1 | jose: critical ||
    2626 || 4 || || Javadoc|| Automatically add the Javadoc pages to this wiki, updated from a Hudson build process? For all of the branches? || heikki: 4 ||
    2727 || 5 || || Coding rules || Some people really like working with ''patches''; other people prefer using short-lived SVN branches for a similar purpose. Can we all agree on doing it one way or the other? || heikki: 4 ||
    2828 || 6 || ||Community || This wiki is a bit of a mess, in my opinion. I think it would be good if we could put maybe 3 people in charge to firstly, clean it up and better structure it; and secondly, to try to keep it that way. || heikki: 2 ||
    29  || 7 || || Database || Let's create SQL files that can fill an empty GeoNetwork database with only the minimum needed to run the program? The admin user, settings, regions, things like that. Not everyone is really eager to use GAST for anything. || Done by Jose? ||
     29 || 7 || || Database || Let's create SQL files that can fill an empty GeoNetwork database with only the minimum needed to run the program? The admin user, settings, regions, things like that. Not everyone is really eager to use GAST for anything. || Done by Jose? Yes, this is done. We can check how to provide upgrade slq files from previous versions and integrate in GAST this upgrade files(optional)  ||
    3030 || 8 || || Database || Can we agree that we'll provide SQL scripts to create the database, and SQL scripts to fill it with sample data? And let's phase out those DDF files and the unfortunate GAST altogether? And that we provide update SQL scripts with new versions of GeoNetwork, both for changes to database schema and for content (like, [http://geonetwork.tv/settings Settings] !) ? || heikki: 3 ||
    3131 || 9 || || Release Strategy|| Can we release GeoNetwork 3.0 (with the CSW/ebRIM interface)? Maybe we can have simultaneous "current releases" in both the GN2.x and GN3.x lineages, as do for example Lucene and Tomcat? || heikki: 3 ||
    3232 ||10|| || Database  || Does anyone like the function of the installer that it overwrites your JDBC credentials with randomly generated values? I certainly don't, as my DB lives very much longer than the many GeoNetwork installations I always do, so I have to edit {{{config.xml}}} everytime. How's about removing that? || heikki: 2 ||
    3333 ||11|| ||Community || Would it be an idea to appoint Language Managers for each of the supported translations? They would form the International Internationalization Committee (IIC, or CII in French) and they're summoned to maintain the i18n files for their language, before each new release. This might even be arranged in an [http://www.osgeo.org/ OSGEO]-wide manner. || heikki: 3 ||
    34  ||12 || ||Code Refactoring || The class {{{DataManager.java}}} and its sister {{{XMLSerializer.java}}} are in particularly bad shape, in my opinion. There are literally dozens of public methods that all do more or less the same thing. Of course it's not clearly documented why they are all there or when to use which. Would it be too drastic to propose that we keep 1 single public method for each of the functions ''createMetadata'', ''updateMetadata'', ''validateMetadata'', etc. ? || heikki: 1 ||
     34 ||12 || ||Code Refactoring || The class {{{DataManager.java}}} and its sister {{{XMLSerializer.java}}} are in particularly bad shape, in my opinion. There are literally dozens of public methods that all do more or less the same thing. Of course it's not clearly documented why they are all there or when to use which. Would it be too drastic to propose that we keep 1 single public method for each of the functions ''createMetadata'', ''updateMetadata'', ''validateMetadata'', etc. ? || heikki: 1 | jose: critical ||
    3535 ||13|| || RIA, Framework || Any relevant software going on that might be useful for GeoNetwork? Think of [http://mapproxy.org/ MapProxy], [http://chiba.sourceforge.net Chiba] and [http://geojquery.org/wiki/doku.php GeoJQuery]. Other ones? || heikki: 2 ||
    3636 ||14|| ||Editor enhancement || In the [http://nationaalgeoregister.nl NGR] project, a modification to the code around the editor called ''Inflation and Vacuum'' is implemented, that makes it much easier to create valid metadata from scratch. In essence it takes the function of {{{update-fixed-info.xsl}}} (which also tries to do some automatic adjustments to help things along) a whole seven miles further. What do the developers think of this? (I'll provide documentation sometime soon). || heikki: 3 ||
    37  ||15|| ||Framework / Refactoring ||Whether it's going to happen soon or not, I still think it good to repeat the subject of what to choose if we ever get to a drastic make-over of current GeoNetwork code, especially in terms of (1) GUI: use [http://wicket.apache.org/ Wicket]? [http://code.google.com/webtoolkit/ GWT]? (2) MVC: use [http://struts.apache.org/2.x/ Struts]? [http://static.springsource.org/spring/docs/2.0.x/reference/mvc.html Spring MVC]? (3) Persistence: use [http://www.hibernate.org/ Hibernate]? use [http://java.sun.com/developer/technicalArticles/J2EE/jpa/ JPA/EJB3]? (4) Web Services: use [http://ws.apache.org/axis2/ Axis2]? [http://jcp.org/en/jsr/summary?id=311 Jax-RS]? || heikki: 3 ||
     37 ||15|| ||Framework / Refactoring ||Whether it's going to happen soon or not, I still think it good to repeat the subject of what to choose if we ever get to a drastic make-over of current GeoNetwork code, especially in terms of (1) GUI: use [http://wicket.apache.org/ Wicket]? [http://code.google.com/webtoolkit/ GWT]? (2) MVC: use [http://struts.apache.org/2.x/ Struts]? [http://static.springsource.org/spring/docs/2.0.x/reference/mvc.html Spring MVC]? (3) Persistence: use [http://www.hibernate.org/ Hibernate]? use [http://java.sun.com/developer/technicalArticles/J2EE/jpa/ JPA/EJB3]? (4) Web Services: use [http://ws.apache.org/axis2/ Axis2]? [http://jcp.org/en/jsr/summary?id=311 Jax-RS]? || heikki: 3 | jose: major ||
    3838 || 16 || ||Editor enhancement (XForms) ||GeoNetwork needs a range of metadata editors and the XForms Editor (from geonetworkui sandbox) should be available as part of this range. An XForms engine is an alternative technology that potentially hides details of HTML and JavaScript from developers. (The usefulness of the XForms editor will be determined to a large extent by how well it works across browsers and how responsive it is. What does the "potentially hides details" bit actually mean? That's just wishful thinking, and adding XForms means yet another complicated technology for developers to master. Justification/Action: Develop XForms interface as providing a user friendly interface with the flexibility to meet the needs of different users. How does it relate to [http://chiba.sourceforge.net Chiba]? || heikki: 3 ||
    3939 || 17 || || Feedback / Enhancement  ||GeoNetwork needs a range of metadata editors and the ANZMet Lite (a wizard based editor available for download from [http://anzlicmet.bluenet.utas.edu.au here]) should be part of the toolkit. ANZMet Lite needs to be open sourced under (GPL) to be distributed with GeoNetwork. Comments: If the web interface were improved, the need for ANZMet Lite would be reduced.  There is a need for “offline” metadata creation when researchers or data collectors are not connected to the Internet – this is where ANZMet Lite has unique value. Why not improve the existing GeoNetwork editor (see geocat.ch editor, merge some of the features into the trunk)? Justification/Action: Add ANZMet Lite as a user friendly, Wizard based PC editing interface with the flexibility to meet the needs of different users. Simon Pigot has already added GeoNetwork upload/download to ANZMet Lite. || heikki: 4 ||
    4040 || 18 || ||API enhancements || GeoNetwork services and JavaScript API need to be documented so that the user interface can be replaced and/or the existing functionality reused or customized. A different user interface skin should be easy to apply. The new Jeeves test framework offers an opportunity to document the inputs and outputs of the services. Action/Justification: The existing JavaScript API (web/geonetwork/scripts/core) needs to be documented and extended – existing code that doesn’t use the API needs to be refactored. Note: !GeoNetwork xml services documentation exists in manual. || heikki: 2 ||
    41  || 19 || || Code cleaning (client part)||The technologies that are used in the user interface are not homogenous: XSLT, HTML and !JavaScript are often mixed and hard to separate - this makes development and modification of the user interface difficult - but given the current architecture of !GeoNetwork, a complete separation into components based on implementation language is impossible. Action: Separate the HTML, XML and JavaScript from each other so that a skilled interface designer does not need to know all three technologies to change the interface. || heikki: 4 ||
     41 || 19 || || Code cleaning (client part)||The technologies that are used in the user interface are not homogenous: XSLT, HTML and !JavaScript are often mixed and hard to separate - this makes development and modification of the user interface difficult - but given the current architecture of !GeoNetwork, a complete separation into components based on implementation language is impossible. Action: Separate the HTML, XML and JavaScript from each other so that a skilled interface designer does not need to know all three technologies to change the interface. || heikki: 4 | jose: major ||
    4242 || 20 || || XML fragment||Reusing fragments of metadata (XML) – “object reuse”. Fragments are implemented in various sandboxes. Metadata records can be composed from fragments using XLinks and there is an XLinks URL Resolver. Community action needs to be consolidated through the fragments proposal. Many organisations would like GeoNetwork to be able to harvest fragments from relational databases as they often generate full metadata records from relational databases using custom software. If the database information changes, these records then need to be re-harvested. Some organisations would also like to be able to edit the fragments in !GeoNetwork and return them to the database from which they were harvested. Action/Justification: Integrating fragments of metadata that are managed in an external system (i.e. relational database, authentication directory). There is a mechanism for implementation for metadata fragment harvesting from relational databases via a WFS in the BlueNetMEST sandbox. This work needs to be consolidated with work in the geocat.ch and geosource sandboxes and added to the trunk. This work should also be extended to allow metadata fragments in the relational database to be updated after editing in !GeoNetwork. Harvesting of fragments from authentication directories (eg. LDAP) should be added.  ||Partially done by Simon ? ||
    4343 || 21 || || Metadata versioning  || !GeoNetwork needs some form of version control to track changes made to a metadata record over time. Action/Justification: This can be done inside the database without needing to externalise the metadata records. That way you can index and search on the old versions as well, if desired. Alternatively it could be done externally using perhaps a Java interface to subversion or through an interface to existing enterprise document management systems or perhaps using a different database approach for the documents eg. CouchDB. See also [http://geoserver.org/display/GEOS/Versioning+WFS this] approach to versioning WFS content?|| heikki: 3 ||
    … …  
    4949 || 27 || || Metadata categories||!GeoNetwork categories are not related to metadata content – should be configurable from content. Action: !GeoNetwork should  be able to configure dynamic categories from a Lucene field. Eg. An administrator could create category names as unique values of the Lucene field name purpose (which might be mapped to gmd:purpose for ISO) – records would belong to the category described by purpose cf. also discussion on dynamic categories ie. categories that are placeholders for a saved search. || heikki: 4 ||
    5050 || 28 || ||Tag cloud || GeoNetwork currently does not manage its own tag cloud / Folksonomy. Action: !GeoNetwork could optionally manage these things internally rather than using a third party social networking site. [http://trac.osgeo.org/geonetwork/ticket/96 Ticket 96 suggests a way of doing this]|| heikki: 4 ||
    51  || 29 || ||Harvester / Network-crawling ||Network-crawling for geo-resources. Action: GeoNetwork needs to continue to be aware of and exploit initiatives for automatic harvesting of metadata from geo-resources. Eg. Metadata extraction tools such as the Talend Spatial Data Integrator suite etc || heikki: 3 ||
     51 || 29 || ||Harvester / Network-crawling ||Network-crawling for geo-resources. Action: GeoNetwork needs to continue to be aware of and exploit initiatives for automatic harvesting of metadata from geo-resources. Eg. Metadata extraction tools such as the Talend Spatial Data Integrator suite etc || heikki: 3 | jose: major ||
    5252 || 30 || ||Metadata identifier ||!GeoNetwork lacks the ability to consistently reproduce a unique identifier for the same geo resource (e.g. same dataset stored in two different locations) and/or use persistent identifier services. This is somewhere along the range from "easy enough" to "very difficult", need to spell out the precise details of the set of features you have in mind. Action: GeoNetwork needs to be able to generate, store and use metadata identifiers (eg, gmd:fileIdentifier) as well as data identifiers using the current stand alone UUID, but also (for data objects) MD5 (including what the checksum was generated from) and identifiers from external persistent identifier services (It should be possible to obtain persistent identifiers for both metadata and data from external persistent identifier services). || heikki: 4 ||
    53  || 31 || ||Interoperability / resources discovery||Better inter-application interoperability. GeoNetwork needs to rethink the interoperability with the emerging FOSS such as the way that OpenLayers is designing / redeveloping its interface. e.g. use of GeoExt; e.g. GeoNetwork needs to provide simple mechanisms to allow discovered resources to be exploited and utilised in complementary open source software; e.g. drag-and-drop discovered resources into OpenLayers or GeoServer. Action: Better intra-application interoperability. GeoNetwork needs to coordinate the discovery of resources with the publication of those same resources in FOSS such as GeoServer. || heikki: 2 ||
     53 || 31 || ||Interoperability / resources discovery||Better inter-application interoperability. GeoNetwork needs to rethink the interoperability with the emerging FOSS such as the way that OpenLayers is designing / redeveloping its interface. e.g. use of GeoExt; e.g. GeoNetwork needs to provide simple mechanisms to allow discovered resources to be exploited and utilised in complementary open source software; e.g. drag-and-drop discovered resources into OpenLayers or GeoServer. Action: Better intra-application interoperability. GeoNetwork needs to coordinate the discovery of resources with the publication of those same resources in FOSS such as GeoServer. || heikki: 2 | jose: major ||
    5454 || 32 || ||Data management ||!GeoNetwork assumes resources that are tagged as data for download in gmd:protocol are local. Action: GeoNetwork needs to allow for the fact that data tagged as data for download may not be local. || heikki: 1 ||
    5555 || 33 || ||Remote search||Remote search across a number of sites returns a pre-selected number of hits from all remote sites (pre-selected number is a search option) – it should return these hits from each site. Action: Presentation of pre-selected number of hits from each remote site – may require more delving into JZKit. || heikki: 3 ||
    5656 || 34 || ||Remote search||Presentation of returned hits from remote sites may be very slow because search is limited by the speed of the slowest site. Action: Presentations of first returned hits from first responding remote site should not have to wait on the slowest site – may require more delving into JZKit. || heikki: 3 ||
    5757 || 35 || ||Configuration||There are too many configuration files in too many places eg. repositories.xml.tem and not all configuration options are supported by the existing admin interfaces. Action: Continue to consolidate configuration options in the system configuration interface. || heikki: 2 ||
    58  || 36 || ||Web map client|| There is no documentation for the implementation of alternative web map clients to Intermap and this makes it appear that the process is far harder than it actually is. Given the enthusiasm for an OpenLayers-based interface, what "interface" there currently is will probably soon be rapidly-evolving - if not replaced completely. Action: Document the interface that GeoNetwork uses to call a web map client so that sites can substitute their own.|| heikki: 1 ||
     58 || 36 || ||Web map client|| There is no documentation for the implementation of alternative web map clients to Intermap and this makes it appear that the process is far harder than it actually is. Given the enthusiasm for an OpenLayers-based interface, what "interface" there currently is will probably soon be rapidly-evolving - if not replaced completely. Action: Document the interface that GeoNetwork uses to call a web map client so that sites can substitute their own.|| heikki: 1 | jose: critical ||
    5959 || 37 || ||Distributed search||Current capability of !GeoNetwork to use distributed searching is given a low priority and not being developed when compared with the local search. Action: More consideration is required towards distributed searches and proper attention should be given to it.|| heikki: 2 ||
    6060 || 38 || ||Distributed CSW search|| Distributed CSW searches are not available. Action: All OGC CSW standards and specifications should be implemented. || heikki: 1 ||
    … …  
    7676 || 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?|| heikki: 3 ||
    7777 || 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.  || heikki: 5 ||
    78  || 56 || ||Customization || Improve CSS management, clean CSS file and references to unused styles, replacing tables by divs, discuss on [wiki:ThemeCustomization]|| heikki: 1 ||
    79  || 57 || ||Maven migration ||Move to Maven as described here : [wiki:Maven] ||Mathieu (major) | heikki: 1 |
     78 || 56 || ||Customization || Improve CSS management, clean CSS file and references to unused styles, replacing tables by divs, discuss on [wiki:ThemeCustomization]|| heikki: 1 | jose: critical ||
     79 || 57 || ||Maven migration ||Move to Maven as described here : [wiki:Maven] ||Mathieu (major) | heikki: 1 | jose: major |
    8080 || 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 ||
    8181 || XX || || || || ||