Version 1.2.4

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

Table of Contents Enhancements System Environment User Management Discovery Map Viewer Synchronization Portal for ArcGIS Integration Miscellaneous Known Issues System Environment User Management Discovery Publishing Synchronization

Enhancements

System Environment

• Support for Java 7 and Tomcat 7

User Management

• Support for searching user names containing special characters in the Manage User page

Discovery

• Support for DCAT with the capability to customize DCAT output through a configuration file, see Customize DCAT output
• Predefined filter on search page through URL to enable passing search terms as a search filter in the URL,search.page?filter=searchdata. Users can narrow the search further by entering additional search text and specify more search criteria. See Url filter customization.
• JSON response enhancements: split links in each record into links and resources, add references to each record, fix 'more' element on a header, and add resource type to each record
• Support geojson in the xjson response
• Support searching by dataset dates for ISO-19115, 19115-2, and FGDC records - see Indexing and Searching the Time Period of the Content
• Enhancements to resource URL handling so that correct resource URL is used when there is multiple URLs in the metadata (e.g., in the case of onlink)
• Optional integration with Apache solr to provide a faceting interface - see Geoportal Facets
• Make locator search in the search page disabled by default, and it can be enabled through configuration when needed
• Enhancements to geoportal functionality to better use FGDC service checker to display status for more service types

Map Viewer

• Upgrade default map viewer configuration with ArcGIS Viewer for Flex 3.3 and Geoportal FindData Widget
• Support image services for Add to Map

Synchronization

• Support harvesting from one Portal for ArcGIS instance to another Portal for ArcGIS instance through the Geoportal Server, see AGP-TO-AGP Harvesting with the Geoportal
• Support harvesting of ATOM feeds (ATOM 1.0)
• Fixed issue with harvesting ArcGIS Server services located in subfolders
• Improved robustness of harvest engine to improve harvesting efficiency and better handle network and database connection issues
• Add "Create and Close" and "Update and Close" button in the registration service page

Portal for ArcGIS Integration

It is now possible to integrate many of the Geoportal Server functionalities with Portal for ArcGIS, including:

• Add metadata editing capability for Portal for ArcGIS, including edit metadata within Portal for ArcGIS using either the GXE Editor in an existing Geoportal Server instance or an standalone Geoportal GXE editor instance
• Harvest items from one Portal for ArcGIS instance to another Portal for ArcGIS instances
• Conduct federated search within ArcGIS Portal instances such as search Geoportal metadata repository within a Portal for ArcGIS interface and display the results within Portal for ArcGIS
• Connect Portal for ArcGIS viewer to "Add to Map" in geoportal as a Map Viewer

Miscellaneous

• Geoportal context-sensitive Help launches Github Geoportal Server media wiki page by default
• Update to Desktop Clients
• Fixed issues in Linux database scripts
• Fixed Cross-Site Scripting issue
• Provide general exception message and hide details of exception containing system information when registering a LDAP user
• Fixed displaying issue for non-English characters
• Move the geoportal code to github

Known Issues

System Environment

• Apache Tomcat 6.0.13 and earlier not supported. If used, 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 a known issue with Apache Tomcat. Workaround is to use later version of Tomcat; recommended is version 6.0.32 and higher.

User Management

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

Discovery

• WMTS support the Javascript API has issues with certain instances of WMTS; also, most WMTS will not be able to be previewed.
• The ability for a WMS service to be previewed will depend on the projections supported by the service specified for the Geoportal Search map. See the Important Notes in the Changing the Map Service Topic for details.
• 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.
• KML files that use a geometry other than points or rectangles (e.g., lines, other polygons) will not be rendered on the Preview page.
• 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.
• For metadata records published with the first letter of their title being a diacritic letter, the records will be sorted with diacritic titles below the non-diacritic titles if Search results are ordered by title.

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.

---

Back to Release Notes