/geoportal-server

FGDC Biological Profile and Remote Sensing Extension

Christine White edited this page Jun 21, 2013 · 3 revisions
Clone this wiki locally

The FGDC metadata standard also includes a Biological Profile and a Remote Sensing Extension. Metadata that conforms to these profiles contains the general FGDC metadata elements, but also must include additional information.

In the case that your organization wants Biological and/or Remote Sensing records to be validated differently than general FGDC records - e.g., you would like to point to the biological profile xsd or remote sensing profile xsd for those records - then you can apply this customization. IMPORTANT: Please see the Biological or Remote Sensing FGDC xsds topic before referencing these xsds in your geoportal files.

This customization applies interrogation rules that will identify records that are biological or remote sensing. You will be downloading additional files for the \\geoportal\WEB-INF\classes\gpt\metadata\fgdc directory, making minor edits to them, and adjusting the \\geoportal\WEB-INF\classes\gpt\metadata\schemas.xml and \\geoportal\WEB-INF\classes\gpt\resources\gpt.properties file to accommodate the new profiles. Follow the steps as described below.

Table of Contents

Copy the new fgdc profile files

Edit the files to reference the biological and/or remote sensing xsds

  • Open the bio-fgdc-definition.xml file. In the <schema></schema> element, set the xsdLocation. Currently, it is set to a placeholder location that will not work; you must replace "location_of_bio_xsd/fgdc-std-001.1-1999_bio/fgdc-std-001.1-1999.xsd" with the actual accessible location of the biological profile.
  • Save the bio-fgdc-definition.xml file.
  • Open the remotesensing-fgdc-definition.xml file. In the <schema></schema> element, set the xsdLocation. Currently, it is set to a placeholder location that will not work; you must replace "location_of_remote_sensing_xsd/fgdc-std-012-2002_rs/fgdc-std-012-2002.xsd" with the actual accessible location of the remote sensing profile.
  • Save the remotesensing-fgdc-definition.xml file.

Update gpt.properties with the names of the profiles

The gpt.properties file maintains all the string names within the geoportal interface. Here, you will add the names of the biological and remote sensing profiles to this properties file.

  • Open the \\geoportal\WEB-INF\classes\gpt\resources\gpt.properties file.
  • Find where the schema names are defined - e.g., search for '# schemas'.
  • Add two new strings as shown - one for the biological profile and one for the remote sensing profile. These strings come from the <label></label> element in the bio-fgdc-definition.xml and the remotesensing-fgdc-definition.xml files, respectively:
catalog.mdParam.schema.fgdc.bioprofile
catalog.mdParam.schema.fgdc.remotesensing
  • Save the gpt.properties file.

Update the schemas.xml file to reference the new profiles

  • Open the \\geoportal\WEB-INF\classes\gpt\metadata\schemas.xml file.
  • Add the references to the x and y files just above the reference to the fgdc-definition.xml file, as shown below. IMPORTANT: The biological and/or remote sensing profiles must come before the fgdc-definition file reference because the order of interrogation of these profiles is from top to bottom. Because biological and remote sensing records do contain elements from the general FGDC standard, if you list these profiles after the fgdc-definition file, biological and remote sensing records will be identified as general FGDC records.
<schema fileName="gpt/metadata/fgdc/bio-fgdc-definition.xml"/>
<schema fileName="gpt/metadata/fgdc/remotesensing-fgdc-definition.xml"/>
<schema fileName="gpt/metadata/fgdc/fgdc-definition.xml"/>
  • Save the schemas.xml file.

Restart the geoportal web application

You must restart your geoportal web application for changes to take affect.

Back to Customizations