Skip to content

Version 1.1.1

Jump to bottom
Marten Hogeweg edited this page Dec 14, 2012 · 1 revision

The list below includes enhancements and bug fixes in version 1.1.1.

Table of Contents

Publishing

At version 1.1 the Geoportal Server added a new and improved metadata editor that includes multiplicity, simpler navigation navigating, new display for validation notifications, nested hierarchy, and integration with 3rd party components.

Version 1.1.1 adds a configuration of this editor that supports full FGDC metadata.

Known Issues

System Environment

  • Apache Tomcat 6.0.13 and earlier not supported. If used, then when users access certain pages (Register Network Resource, the Search page), they'll be redirected to the Home Page. Logfile will show an error that the EL expression cannot be parsed. This is an issue with Apache Tomcat and not Geoportal code. Workaround is to use later version of Tomcat; recommended is version 6.0.24 and higher (but not Tomcat 7.x).

User Management

  • Geoportal does not support registering new users through Register page or changing a password through the My Profile page if configured with Active Directory.

Discovery

  • When the thumbnail in metadata is not found, an empty image displays in the search result/details page.
  • Thumbnails with partially encoded URL reference (e.g., http://www.testserver.com/images/Note%20the%20encoding%20here/but no encoding here.JPG), the h:graphicImage java server faces component renders the link with plus signs in the spaces. Workaround is to use fully encoded URLs in thumbnail links.
  • Searching ArcGIS.com through federated search allows users to choose Live Data and extent for a search criteria, but these are not supported by ArcGIS.com.
  • KML and KMZ file having html code in CDATA section as a description does not get rendered properly and show html string.
  • When a document title is long with no spaces, HTML rendering does not wrap the title in search results.
  • When OntologyService.war is deployed in weblogic without unzipping the .war file, the Ontology service does not return related terms.
  • If a bounding box is a point, foot print on a search map for the metadata is not correct and shows a random bounding box.

Publishing

  • Geoportal calendar does not work properly if a server is set with different locale in JVM such as Buddhist calendar.
  • When metadata status gets updated with the checkbox "Apply action to the entire result set", the status change gets updated in search and lucene index files when the next synchronization (to sync between lucene index and database) process runs and finishes.

Synchronization

  • For CSW protocol, incremental Synchronization will not reharvest metadata that have been deleted from admin interface.
  • If a repository doesn't support last updated date info, Incremental sync will act like full sync.
Clone this wiki locally