Hi,
I'm wondering if it's possible to change geonetwork database structure and
adjust it to my requirements??
What should I do to change it? Which files I have to modify? Does anyone
know how to do this?
Thanks in advance
--
View this message in context: http://www.nabble.com/change-GN-database-structure-tf3957643s18419.html#a11229904
Sent from the geonetwork-devel mailing list archive at Nabble.com.
Hi,
You sure could. The question is if it is the best thing to do and for what. But the code is open source, so you can do what you feel like respecting the GPL license 
Ciao,
Jeroen
On Jun 21, 2007, at 11:50 AM, Lukasz_Sobotowski wrote:
Hi,
I'm wondering if it's possible to change geonetwork database structure and
adjust it to my requirements??
What should I do to change it? Which files I have to modify? Does anyone
know how to do this?Thanks in advance
--
View this message in context: http://www.nabble.com/change-GN-database-structure-tf3957643s18419.html#a11229904
Sent from the geonetwork-devel mailing list archive at Nabble.com.-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Hi,
I've successfully back ported the ISO19139 schema, parsing and xsls from 2.1 to 2.0.3 - in doing this I ran into a problem I had before and fixed when implementing the 19115 Marine Community Profile: elements that have the same name but different types (eg. gmd:date in 19139).
Previous schemas in GN such as ISO19115-DIS used the short element names from the ISO19115 standard which are guaranteed to be unique. This is important to GN because EditLib relies on this uniqueness - it uses the element name to extract types, type restrictions (eg. codelists) and minOccurs/maxOccurs from the parsed schema. This is broken by the use of long element names in schemas like 19139 and the Marine Community Profile where duplicate element names are allowed so long as they are in different metadata entities. To fix it I've changed the code in MetadataSchema.java, MetadataType.java, SchemaLoader.java and EditLib.java to use the parent to resolve these clashes (as suggested by the 19115 standard) when they occur.
I've also got a whole bunch of code changes to submit - including fixes to metadata-iso19139.xsl and a bunch of other changes I previously promised to the developers (eg. LDAP replacement for users/groups etc) - if you guys are still interested (and I apologise for my delay in doing this) can you suggest a simple way I can give all this to you - maybe as a complete version eg. GN2.0.4 and GN2.0.4+LDAP?
Cheers,
Simon