Geoportal Server v 1.1 What's New
This section describes what's new for the Geoportal Server 1.1:
At version 1.1 the Geoportal Server has a new and improved metadata editor that includes the following:
- Supports multiplicity, the ability to repeat metadata elements.
- Tabbed based metadata editor that makes navigating the metadata elements easier.
- New display for validation notifications, which includes hyperlinks to the actual required element and instant status message updating when the field has been populated.
- Supports the metadata editor from older versions of the Geoportal.
- Nested Hierarchy
- Integration with 3rd party components such as GEMET (required for INSPIRE).
Defect ID #3192509 (see http://sourceforge.net/tracker/?func=detail&aid=3192509&group_id=306452&atid=1291151).
In Geoportal Server version 1.0, xsd schema validation for metadata profiles is not invoked even when schemas are referenced in the definition.xml files (found in the \\geoportal\WEB-INF\classes\gpt\metadata subdirectories of the geoportal web application). The resulting behavior is that only the definition.xml file rules are used for validation, and xsd schema validation is not invoked.
This fix addresses the issue by enabling the xsd schema validation to be invoked if an xsd is referenced in the definition.xml files. Out of the box, an xsd is referenced in the following definition.xml files, although an xsd reference can be added to any of the definition.xml files in the geoportal web application: iso-19115-definition.xml, inspire-iso-19119-definition.xml, nap-iso-19115-definition.xml, and nap-iso-19119-definition.xml.
Defect ID #3158338 (see https://sourceforge.net/tracker/?func=detail&aid=3158338&group_id=306452&atid=1291151)
The synchronizer for OAI correctly retrieves records from an OAI source, but returns the actual metadata content wrapped in an extra <metadata></metadata> wrapper. The result is that the metadata synchronized from the OAI source fails validation and does not publish to the geoportal.