GXE Workflow

This section describes how to enable GXE and what Geoportal Server components are responsible for supporting it. For a general overview and other topics, see Geoportal XML Editor.

Integration with Geoportal Publication Workflow

The XML mappings supported by an instance of the Geoportal Server are declared within the schemas.xml file at [webapp]/WEB-INF/classes/gpt/metadata. An example of a mapping reference in the schemas.xml file is below:

<schema fileName="gpt/metadata/fgdc/fgdc-definition.xml"/>

Each declared mapping will have an associated XML-based definition file. To enable the editor for a specific mapping, add the editor fileName reference to the associated definition file. In the example below, we show adding the reference to the [webapp]/WEBINF/classes/gpt/metadata/fgdc/fgdc-definition.xml file:

<editor fileName="gpt/gxe/fgdc/fgdc-editor.xml"/>

Each editor will have a base definition file for the editor, and one or more files defining its content. An example from the [webapp]/WEB-INF/classes/gpt/gxe/fgdc/fgdc-editor.xml file is shown below:

<g:editor xmlns:g="http://www.esri.com/geoportal/gxe"
xmlns:h="http://www.esri.com/geoportal/gxe/html"
g:extends="gpt/gxe/editor.xml">

For the FGDC example, the files that define the editor are intended to represent a subset of the structure associated with XML schema at http://www.fgdc.gov/schemas/metadata/fgdc-std-001-1998.xsd. When a document is saved from the editor, its XML is submitted to the Geoportal Server REST endpoint via HTTP PUT: http://host:port/[geoportal]/rest/manage/document. The Java class com.esri.gpt.control.rest.ManageDocumentServlet handles the request; publication follows the same underlying flow as any other Geoportal publication process.

---

Back to Geoportal-XML-Editor

Forward to Core Geoportal XML Editor Definition Structure