| 30 | | || 8 || || 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? || || |
| 31 | | || 9 || || 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? || || |
| 32 | | || 10 || ||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. || || |
| 33 | | || 11 || ||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. ? || || |
| 34 | | || 12 || || 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? || || |
| | 30 | || 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] !) ? || || |
| | 31 | || 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? || || |
| | 32 | ||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? || || |
| | 33 | ||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. || || |
| | 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. ? || || |
| | 35 | ||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? || || |
| | 36 | ||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). || || |
| | 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]? || || |
| | 38 | || 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]? || || |
| | 39 | || 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. || || |
| | 40 | || 13 || || || || || |
| | 41 | || 13 || || || || || |
| | 42 | || 13 || || || || || |
| | 43 | || 13 || || || || || |
| | 44 | || 13 || || || || || |
