FGDC XML Metadata Help

The metadata process has changed from an HTML format to an XML format. Creating the metadata in the XML format is possible using ArcCatalog. This XML format will allow us to publish our data in the Metadata Server and also to allow the metadata file to be included with the coverage. This makes the metadata available with each dataset rather then in a separate location as in the past. A template is available and should be further customized for your particular needs in order to streamline the process when creating new metadata.

First, Open ArcCatalog. Select Options from the Tools pull down menu. Select the Metadata Tab. Make sure Metadata Editor is set to FDGC Editor. Show me FDGC is the format agreed on by Southern Nevada GIS (SNGIS).
Open the metadata_template.xml file in ArcCatalog. Make changes to the file adding in all general information that is consistent throughout your metadata. Save as _template.xml. This should only have to be done once, then use your customized template for all your metadata.
Export your template to your workspace (on your H: or P: drive) using the Export Metadata tool.
Copy the coverages you will be creating metadata for in to your workspace.
Open ArcCatalog and navigate to your workspace.
Select the metadata Tab and choose the metadata editing tool to Create/Update Metadata.
Select the Import Metadata*tool and navigate to the _template.xml. This will import all of the general information you have created in your xml template.
* Importing the metadata template after you have begun to edit your metadata file will result in a loss of data.
Fill in all fields marked REQUIRED**. Other fields may be filled in if data exists. Besides those fields listed as "Required", you also need to fill-in/edit the "Title". If using the template, it may show as "metadata_template.xml". The title should be something descriptive so the layman will know what it is. For example, SCL_P doesn't really show that it is a Street Centerline polygon coverage. The title for this example would be better to show: "Street Centerline polygon coverage ". This would mean much more to the user. If this field is blank, the metadata will not publish.
** All fields with a REQUIRED in their box must be completed in order to publish to the Metadata Server.
There are a few other REQUIRED items as well.
Create a thumbnail for the metadata. To do this you must select the Preview Tab. Zoom in to the area you would like displayed (may be full extent or a portion of the coverage). Select the Create Thumbnail icon.

This document was created to offer some help and tips creating metadata. For additional help and understanding of creating and editing metadata, go to ArcGIS Desktop Help, under index find: "metadata, creating", or "metadata, FGDC".

Using the FGDC metadata editor

Top of page

How the editor is organized

Identification
Data Quality
Spatial Data Organization
Spatial Reference
Entity and Attribute
Distribution
Metadata Reference

The section titles across the top of the FGDC metadata editor correspond to these sections. When you click a section title in the editor, several tabs appear that represent the different groups of metadata elements that are defined within the section.

Citation Information
Time Period Information
Contact Information

These supporting sections are included where appropriate within the main sections.
At first, the organization of information in the FGDC editor may seem confusing, but as you become familiar with this standard, you will find it easier to locate the elements that you want to edit. In the meantime, click the Help button in the editor to see a page that shows you where to find the mandatory FGDC elements.

Creating and updating metadata

Top of page

About creating and updating metadata
By default, metadata is automatically created or updated when you view it in the Metadata tab. ArcCatalog gets the selected item's properties and records those values in its metadata. This ensures the metadata is kept up to date as the data changes over time. For example, the extent and count of a shapefile's features will be current when you look at its metadata, even if new features were recently added.

If you want more control over this process, you can turn off automatic metadata creation or updates. This can be accomplished either for all items by changing the settings in the Options dialog box or for individual items by changing the settings in the Metadata Properties dialog box. You might turn off automatic updates for a single item after work on the item has been completed.

You can manually create or update an item's metadata by clicking the Create/Update Metadata button on the Metadata toolbar. You might do this if automatic metadata creation is turned off or if you modify an item using its Properties dialog box while you are viewing the metadata in the Metadata tab. Even if automatic metadata updates are turned off for an item, you can update its metadata by clicking the Create/Update Metadata button or by changing its thumbnail-these are both manual processes.

How to create and update metadata:

Top of page

Choosing how metadata is created and updated:
Top of page
Creating and updating metadata manually:
1. In the Catalog tree, click the item whose metadata you want to create or update.
2. Click the Metadata tab.
3. Click the Create/Update Metadata button on the Metadata toolbar.
Top of page
Turning off automatic updates for individual data sources:
1. In the Catalog tree, click the item for which metadata should not be updated automatically.
2. Click the Metadata tab.
3. Click the Metadata Properties button on the Metadata toolbar.
4. Click the Options tab.
5. Check Do not automatically update metadata.
6. Click OK.

Top of page

Other Required Items

When publishing a metadata document to metadata server, these documents can only be published if they contain a title, publisher, spatial extent, theme, and content type for the resource. Either the FGDC or ISO metadata editor may be used to provide the required information.

A common question that comes up is, "Where is the required Publisher filed located"? Show me where to find the publisher field.

If you use the FGDC editor, you need to type the theme and content type codes exactly as specified (case sensitive); the ISO editor lets you pick values from a list. If you use the ISO editor, you need to remove default values that are placed in the FGDC elements by the FGDC synchronizer before publishing the metadata.

Theme code FGDC editor field location and definitions link The theme codes for the FGDC editor are:
biota boundaries climatologyMeteorologyAtmosphere economy elevation environment farming geoscientificInformation health imageryBaseMapsEarthCover	inlandWaters intelligenceMilitary location oceans planningCadastre society structure transportation utilitiesCommunication

Content type FGDC editor field location link The content type codes for the FGDC editor are:
Live Data and Maps Downloadable Data Offline Data Map Files	Static Map Images Other Documents Applications Geographic Services	Clearinghouses Geographic Activities

The drawback of the FGDC editor is that you must type in the content theme and content type codes; the ISO editor lets you pick them from a list. With the FGDC editor you can define any number of theme keywords; the requirement is for one of those keywords to come from the Metadata Service's content theme code list.

For example, metadata for a soils dataset might have existing keywords: soil, clay, and corn. To publish the metadata, add the theme code "farming" to that list. If you want to keep the content theme code separate from the existing set of keywords, add a new group of keywords and define that group's thesaurus as "Metadata Service Theme Categories".

Alternatively, leave your FGDC theme keywords list the way it is and use the ISO editor to define the content theme code. Similarly, when defining the content type code, the FGDC editor's Resource Description text box must contain one of the Metadata Service's codes. That text box can't contain additional information. If your metadata contains an existing resource description, you have a few alternatives: put the existing information in another metadata element; add a second distribution information section by clicking the plus sign under the General tab, then add the content type code; or use the ISO editor to define the content type.

Note: The metadata file you've created is stored in the coverage directory and will be called metadata.xml. Once you've complete the metadata let Brian Bolduc know and he'll copy the metadata.xml file into the CR.