These charts list the most useful metadata tools/models, when to use them, and problems they may cause. For more information, see the ArcGIS online documentation.
Name
| Synchronize |
Type
|
Tool
|
When to Use
|
When there is no metadata file yet or the dataset has changed.
|
Description
|
Uses the dataset to create or update technical metadata. This script will automatically run when you open the dataset in ArcCatalog in the Description tab (this is set in the ArcCatalog Options - Metadata tab. It will create or update many fields, including extent, coordinate system, geometry, format, size, and attribute field names.
Since this script can run automatically when opening the item in ArcCatalog, it is not often necessary to call the script manually. However, if you have the option to run automatically turned off in the options, it can be called to update the item.
It helpful to use for batch technical metadata creation or updating with an ArcPy script that iterates through datasets.
|
Warnings
|
Do not use this script for stand alone metadata files. It will have no effect.
|
Name
| Metadata Importer |
Type
|
Tool
|
When to Use
|
When a template of default information will be used at the beginning of the metadata creation process.
|
Description
|
Two metadata files in the ArcGIS 1.0 format can be merged. One file (usually a template) is imported into another file. Any elements from the source metadata will overwrite those fields in the target metadata. However, elements NOT present in the source metadata will not overwrite the target metadata to create blank fields.
|
Warnings
|
Existing metadata in the target file will be overwritten or erased. Technical metadata will remain or can be re-generated, but previously entered element values will be lost.
|
Name
| Translator |
Type
|
Tool
|
When to Use
|
When a standalone metadata file needs to be converted to another standard.
|
Description
|
This tool will change the format of an ISO or FGDC file to the ArcGIS 1.0 format using a combination of an XSLT and Python. It will transform an ArcGIS 1.0 format file to ISO or FGDC with just an XSLT.
This tool can also be used to create an ArcGIS 1.0 format file for Geodatabases. A new translator calling the exact_copy_of.xslt
|
Warnings
|
Translating directly from ISO to FGDC or in the reverse will cause technical metadata loss. A better strategy is to use the translator to first convert the FGDC to ArcGIS 1.0 format, then do ArcGIS to ISO.
|
Name
| Upgrade |
Type
|
Model (includes scripts plus the tools for transform, import, synchronize)
|
When to Use
|
When one or more datasets only have FGDC metadata files.
|
Description
|
This tool changes FGDC metadata into the ArcGIS 1.0 Metadata Format. It runs through many steps and takes about 25 seconds per file. When you open an FGDC file in ArcCatalog, a popup box will appear prompting you to Upgrade. The metadata file needs to be the same name as the dataset for ArcGIS to recognize it.
To use most of the ArcGIS metadata tools, it is necessary to have the metadata in the ArcGIS 1.0 Metadata Format. The Upgrade tool is not the only way to transform FGDC into ArcGIS 1.0, but it is the most comprehensive and easiest.
|
Warnings
|
Do not use this tool for standalone FGDC files, even though the popup box will still appear. It may erase technical metadata if the dataset is not present. Standalone files should use the translator tool. The FGDC file will not be retained. It will be replaced. If you wish to keep the original file, make a copy before running the tool.
|
Name
| Import Metadata |
Type
|
Model (upgrade/translate, import, synchronize)
|
When to Use
|
When you want to edit metadata that is stored in an external file in the ISO or FGDC format.
|
Description
|
This tool combines several steps and will import an external metadata file in the FGDC or ISO format into the dataset. It first transforms the metadata into the ArcGIS format. Next, it imports the metadata into an existing ArcGIS metadata file tied to the dataset. If the dataset does not have a metadata file, one will be created. Finally, it synchronizes the metadata.
This can be used when the descriptive (manual entry) metadata is stored in an XML file that is not linked with the dataset. This situation often occurs when metadata has been created outside of the ArcGIS environment, such as with the Minnesota Metadata Editor.
|
Warnings
|
ArcCatalog does not recognize files that are named “metadata.xml”
|
Name
| Export |
Type
|
Model (synchronize, translator)
|
When to Use
|
When exporting a single item by using a tool easily accessible from the GUI editor.
|
Description
|
This tool will first synchronize the dataset, and then use the translator tool to generate a new metadata file in a different standard.
A default Translator will be preselected in the dialog box, but the user can navigate to the ArcGIS Program files to select another option. Which default can be partially controlled by which Metadata Style is selected in the ArcCatalog Options window. |
Warnings
|
The dataset may not need to be synchronized first, so the translator tool may be faster in many cases.
|