Defining a new schema in 2.4.1 is broken?
|
|
Martin Aubrey
|
Geonetwork mavens,
We've been happily using 2.2, and have defined several of our own metadata schemas. We followed the online HowTo: http://geonetwork-opensource.org/documentation/how-to/geonetwork-shema-template-howto And this worked well under 2.2. But it is now broken under 2.4.1. When we upgraded to 2.4.1, Geonetwork autodetects the schema and no longer allows XML import of user-defined schemas (throwing an exception "Root element not set"). Metadata in a user-defined schema is defaulted to 'iso19139'. The old 2.2 Importer doesn't autodetect, and supports user-defined schemas, selected from a drop-down menu. The new 2.4.1 importing code (org.fao.geonet.mef.Importer) calls DataManager.autodetectSchema(). This appears to allow only the predefined schemas, iso19115, iso19139, fgdc-std, dublin-core, defaulting to 'iso19139' if not recognized. Is there a new procedure for adding your own schema? Thanks in advance for any help, Rich and Marty ===================================================== Martin Aubrey CIRES, National Geophysical Data Center/NOAA P (303) 497-6337 F (303) 497-6513 http://ngdc.noaa.gov ===================================================== ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ GeoNetwork-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork |
||||||||||||||||
SimonPigot
|
Hi Rich and Marty,
Just added Marine Community Profile (mcp) to 2.4.2 to check this - 'Metadata insert' with MEF file containing an mcp record seems to work fine for me (no error, and inserted with correct schema detected by Datamanager.autodetectSchema). In brief: - mcp metadata has root element mcp:MD_Metadata with namespace URI http://bluenet3.antcrc.utas.edu.au - directory containing mcp schema, codelists and xslts in web/geonetwork/xml/schemas is iso19139.mcp (the rule is that a profile of iso19139 is placed in directory that begins with iso19139, then dot separator, and ends with prefix of root element/targetnamespace - in this case mcp) - Note: many steps from the reference you defined are compressed into this statement :-) plus one extra - add an extract-gml.xsl file for spatial indexing - basically, use the iso19139 dir as a starting point to make sure you have everything you need (maybe check the iso19139.mcp directory in the BlueNetMEST sandbox for any other details) and check the logs on startup to make sure the schema and details have parsed correctly. This should be enough to test inserting metadata with this profile. To go further (ie. setup profile for use by editor/viewer) you would also (using the mcp example again): - add mcp namespace to web/geonetwork/scripts/editor/simpletooltip.js and web/geonetwork/scripts/editor/tooltip.js - basically follow steps 6 and 7 from the online HowTo you cite (you've probably already done this but might as well mention it again) eg. - build your metadata-iso19139.mcp.xsl (place it in web/geonetwork/xsl) to handle presentation of any elements that you want to do differently or which don't exist in vanilla iso19139 - modify other config files eg. include metadata-iso19139.mcp.xsl in metadata-utils.xsl etc You would also need to define any profile specific presentation that you want the csw server to do for your profile - current brief/summary/full xslts in web/geonetwork/xml/csw/schemas may do what you want as at least some of the templates they use do matches on gco:isoType. Francois and I may make some small changes to support profile specific presentations shortly - keep an eye on the commits for this. BTW: I think the DataManager.autodetectSchema code is a bit more discerning than you make out :-) - it checks for a match between the namespace of root element or the targetnamespace attached to the root element and the primary namespace of schemas GeoNetwork knows about in web/geonetwork/xml/schemas. Maybe the root element of metadata from your profile is not using either of these two methods and is being mistaken for vanilla iso19139? I hope we will shortly be able to update the how-to to include this and more info and perhaps have profile installer packs or failing that, at least have a few example profiles included for starter purposes. Hope this helps in the meantime. Cheers, Simon ________________________________________ From: Martin Aubrey [[hidden email]] Sent: Saturday, 17 October 2009 8:49 AM To: [hidden email] Subject: [GeoNetwork-devel] Defining a new schema in 2.4.1 is broken? Geonetwork mavens, We've been happily using 2.2, and have defined several of our own metadata schemas. We followed the online HowTo: http://geonetwork-opensource.org/documentation/how-to/geonetwork-shema-template-howto And this worked well under 2.2. But it is now broken under 2.4.1. When we upgraded to 2.4.1, Geonetwork autodetects the schema and no longer allows XML import of user-defined schemas (throwing an exception "Root element not set"). Metadata in a user-defined schema is defaulted to 'iso19139'. The old 2.2 Importer doesn't autodetect, and supports user-defined schemas, selected from a drop-down menu. The new 2.4.1 importing code (org.fao.geonet.mef.Importer) calls DataManager.autodetectSchema(). This appears to allow only the predefined schemas, iso19115, iso19139, fgdc-std, dublin-core, defaulting to 'iso19139' if not recognized. Is there a new procedure for adding your own schema? Thanks in advance for any help, Rich and Marty ===================================================== Martin Aubrey CIRES, National Geophysical Data Center/NOAA P (303) 497-6337 F (303) 497-6513 http://ngdc.noaa.gov ===================================================== ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ GeoNetwork-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ GeoNetwork-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork |
||||||||||||||||
Sarah_S
|
Hi Simon,
thanks for your explanation. I´m seeing forward for update the howto or/and installer packs or examples. I was looking for this extract-gml.xsl at BlueNetMest sandbox but I didn´t find such one. Only there https://geonetwork.svn.sourceforge.net/svnroot/geonetwork/sandbox/geocat.ch/tags/RC3/web/geonetwork/xml/schemas/iso19139.che/ I can find such one. Is this file missing at BlueNetMest sandbox? And what about the search files at web/geonetwork/xml/search? Do they need much modifications? Can you perhaps give a little overview about autodetect() and some other one mentioned here http://geonetwork3.fao.org/workshops/workshop2007/metadata-schemas.pdf? What of these are relevant at Gn 2.4? Any help is very appreciated. Thanks. best regards Sarah
|
||||
|
SimonPigot
|
Hi Sarah,
BlueNetMEST sandbox is still based on gn2.2 - we have a development version which is not yet committed that is based on 2.4 - however unless your profile has changed the geographic extent elements in identificationInfo, you should be able to just copy the one used for iso19139 - it is used to extract/build gml elements that are used in the new spatial index committed and developed by the geosource sandbox team (Francois and the other developers can explain this much better than I can if required :-)). As far as the search xslts are concerned, these (and the csw search interface) operate on lucene fields with the mapping from the metadata standards/profiles to lucene fields handled by the index-fields.xsl in the schema/profile directory. So unless you want to add an interface for a new field in your profile that you are indexing in lucene via index-fields.xsl, you wouldn't need to change these. As far as the links given are concerned, we will use the new info for 2.4 plus the workshop 2007 presentation and the geonetwork.opensource howto to create the new howto. I'll leave the rest for the howto.... Cheers, Simon ________________________________________ From: Sarah_S [[hidden email]] Sent: Monday, 19 October 2009 8:40 PM To: [hidden email] Subject: Re: [GeoNetwork-devel] Defining a new schema in 2.4.1 is broken? Hi Simon, thanks for your explanation. I´m seeing forward for update the howto or/and installer packs or examples. I was looking for this extract-gml.xsl at BlueNetMest sandbox but I didn´t find such one. Only there https://geonetwork.svn.sourceforge.net/svnroot/geonetwork/sandbox/geocat.ch/tags/RC3/web/geonetwork/xml/schemas/iso19139.che/ I can find such one. Is this file missing at BlueNetMest sandbox? And what about the search files at web/geonetwork/xml/search? Do they need much modifications? Can you perhaps give a little overview about autodetect() and some other one mentioned here http://geonetwork3.fao.org/workshops/workshop2007/metadata-schemas.pdf? What of these are relevant at Gn 2.4? Any help is very appreciated. Thanks. best regards Sarah SimonPigot wrote: > > Hi Rich and Marty, > > Just added Marine Community Profile (mcp) to 2.4.2 to check this - > 'Metadata insert' with MEF file containing an mcp record seems to work > fine for me (no error, and inserted with correct schema detected by > Datamanager.autodetectSchema). In brief: > > - mcp metadata has root element mcp:MD_Metadata with namespace URI > http://bluenet3.antcrc.utas.edu.au > - directory containing mcp schema, codelists and xslts in > web/geonetwork/xml/schemas is iso19139.mcp (the rule is that a profile of > iso19139 is placed in directory that begins with iso19139, then dot > separator, and ends with prefix of root element/targetnamespace - in this > case mcp) - Note: many steps from the reference you defined are compressed > into this statement :-) plus one extra - add an extract-gml.xsl file for > spatial indexing - basically, use the iso19139 dir as a starting point to > make sure you have everything you need (maybe check the iso19139.mcp > directory in the BlueNetMEST sandbox for any other details) and check the > logs on startup to make sure the schema and details have parsed correctly. > > This should be enough to test inserting metadata with this profile. To go > further (ie. setup profile for use by editor/viewer) you would also (using > the mcp example again): > > - add mcp namespace to web/geonetwork/scripts/editor/simpletooltip.js and > web/geonetwork/scripts/editor/tooltip.js > - basically follow steps 6 and 7 from the online HowTo you cite (you've > probably already done this but might as well mention it again) eg. > - build your metadata-iso19139.mcp.xsl (place it in web/geonetwork/xsl) > to handle presentation of any elements that you want to do differently or > which don't exist in vanilla iso19139 > - modify other config files eg. include metadata-iso19139.mcp.xsl in > metadata-utils.xsl etc > > You would also need to define any profile specific presentation that you > want the csw server to do for your profile - current brief/summary/full > xslts in web/geonetwork/xml/csw/schemas may do what you want as at least > some of the templates they use do matches on gco:isoType. Francois and I > may make some small changes to support profile specific presentations > shortly - keep an eye on the commits for this. > > BTW: I think the DataManager.autodetectSchema code is a bit more > discerning than you make out :-) - it checks for a match between the > namespace of root element or the targetnamespace attached to the root > element and the primary namespace of schemas GeoNetwork knows about in > web/geonetwork/xml/schemas. Maybe the root element of metadata from your > profile is not using either of these two methods and is being mistaken for > vanilla iso19139? > > I hope we will shortly be able to update the how-to to include this and > more info and perhaps have profile installer packs or failing that, at > least have a few example profiles included for starter purposes. Hope this > helps in the meantime. > > Cheers, > Simon > > ________________________________________ > From: Martin Aubrey [[hidden email]] > Sent: Saturday, 17 October 2009 8:49 AM > To: [hidden email] > Subject: [GeoNetwork-devel] Defining a new schema in 2.4.1 is broken? > > Geonetwork mavens, > > We've been happily using 2.2, and have defined several of our own > metadata schemas. > > We followed the online HowTo: > > > http://geonetwork-opensource.org/documentation/how-to/geonetwork-shema-template-howto > > And this worked well under 2.2. But it is now broken under 2.4.1. > > When we upgraded to 2.4.1, Geonetwork autodetects the schema and no > longer allows XML import of user-defined schemas (throwing an exception > "Root element not set"). Metadata in a user-defined schema is defaulted > to 'iso19139'. The old 2.2 Importer doesn't autodetect, and supports > user-defined schemas, selected from a drop-down menu. > > The new 2.4.1 importing code (org.fao.geonet.mef.Importer) calls > DataManager.autodetectSchema(). This appears to allow only the > predefined schemas, iso19115, iso19139, fgdc-std, dublin-core, > defaulting to 'iso19139' if not recognized. > > Is there a new procedure for adding your own schema? > > Thanks in advance for any help, > > Rich and Marty > > ===================================================== > Martin Aubrey > CIRES, National Geophysical Data Center/NOAA > P (303) 497-6337 > F (303) 497-6513 > http://ngdc.noaa.gov > ===================================================== > > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > GeoNetwork-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/geonetwork-devel > GeoNetwork OpenSource is maintained at > http://sourceforge.net/projects/geonetwork > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > GeoNetwork-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/geonetwork-devel > GeoNetwork OpenSource is maintained at > http://sourceforge.net/projects/geonetwork > > -- View this message in context: http://n2.nabble.com/Defining-a-new-schema-in-2-4-1-is-broken-tp3838557p3848068.html Sent from the GeoNetwork developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ GeoNetwork-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ GeoNetwork-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork |
||||||||||||||||
|
Sarah_S
|
Hi Simon,
thanks again for the explanation! It would e great if someone coud explain a little more about identificationInfo (there are some files which are related to it) and such stuff:-) So am I right that I have to change index-fields.xsl if I want to add a new field to my profile? And furthermore I make changes to identificationInfo if my geographic extent is changed? Thanks. best regards Sarah
|
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
