Changes between Version 2 and Version 3 of pluginprofiles
- Timestamp:
- 09/06/10 19:57:05 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
pluginprofiles
v2 v3 10 10 == Overview == 11 11 12 Metadata Schemas (including profiles) should be pluggable in GeoNetwork. This means that a user/admin should be able to use a service to add a profile/schema to their existing GeoNetwork installation without having to make changes toJava code, xslts and javascript.12 It should be possible to plug-in Metadata Schemas (including profiles). This means that a user/admin should be able to use a service to add a profile/schema to their existing !GeoNetwork installation without having to make manual changes to config, Java code, xslts and javascript. 13 13 14 14 === Proposal Type === … … 28 28 29 29 == Motivations == 30 To add a schema to GeoNetwork a user currently has to:30 To add a schema to !GeoNetwork a user currently has to: 31 31 32 32 * add the schema and ancillaries to web/geonetwork/xml/schemas directory … … 37 37 * add schema detection code to the autodetectSchema method in DataManager.java 38 38 * add namespaces used for elements to the tooltip javascript (web/geonetwork/scripts/editor/tooltip.js and web/geonetwork/scripts/editor/simpletooltip.js) 39 * schemas added to GeoNetwork exist inside the web application deployment making it more difficult to manage upgrades and new deployments ofGeoNetwork39 * schemas added to !GeoNetwork exist inside the web application deployment making it more difficult to manage upgrades and new deployments of !GeoNetwork 40 40 41 This is not only tedious but requires a fair bit of knowledge to ensure that the installation is not broken by inappropriate or incorrect changes. In some cases these changes are large enough that communities with national schemas/profiles will create their own branch of GeoNetwork to support their schema/profile. This should not be necessary.41 This is not only tedious but requires a fair bit of knowledge to ensure that the installation is not broken by inappropriate or incorrect changes. In some cases these changes are large enough that communities with national schemas/profiles will create their own branch of !GeoNetwork to support their schema/profile. This should not be necessary. 42 42 43 Removing the need to make code changes and consolidating schema information will make adding a schema to GeoNetwork much easier. Having plug in schemas/profiles will also remove the need to create a code branch to support the schema/profile.43 Removing the need to make code changes and consolidating schema information will make adding a schema to !GeoNetwork much easier. Having plug in schemas/profiles will also remove the need to create a code branch to support the schema/profile. 44 44 45 45 == Proposal == … … 51 51 * provide the ability to rewrite xslt imports using a URI resolver and oasis catalog file 52 52 * allow users to rewrite schemaLocation hints using an oasis catalog file/files 53 * add a SchemaManager class to encapsulate and provide schema information to other classes in GeoNetwork53 * add a SchemaManager class to encapsulate and provide schema information to other classes in !GeoNetwork 54 54 * rewrite the Info service so that it no longer requires the namespace URI to be provided by the tooltip requests (will use SchemaManager to get this info instead) 55 55 * change schema autodetection code to use information from the SchemaManager (may also use enhanced schema autodetect approach from Dominic Owen of USGIN) 56 56 * add a services that accept a zip file (or URL of a zip file) containing a schema, unpacks the schema into the schemaPlugins directory, and adds the schema to the list of schemas that GeoNetwork knows about (no config changes required) 57 * Move codelist and label xml file caching for schemas from Jeeves guiservices to GeoNetwork guiservices - no longer necessary to add these files to the gui section of web/geonetwork/WEB-INF/config.xml57 * Move codelist and label xml file caching for schemas from Jeeves guiservices to !GeoNetwork guiservices - no longer necessary to add these files to the gui section of web/geonetwork/WEB-INF/config.xml 58 58 59 59 === Backwards Compatibility Issues === … … 72 72 * Simon Pigot 73 73 * Dominic Owen, USGIN - schema autodetect code 74 * Other members of the GeoNetwork community. In Australia: Craig Jones - IMOS/eMii, John Hockaday - OSDM, AuScope.74 * Other members of the !GeoNetwork community. In Australia: Craig Jones - IMOS/eMii, John Hockaday - OSDM, AuScope.
