ws metadata tipsandtricksslides

Metadata: Tips and Tricks Transcript

Copyright © 2005 ESRI

All rights reserved.

The information contained in this document is the exclusive property of ESRI. This work is protected under United States copyright

law and other international copyright treaties and conventions. No part of this work may be reproduced or transmitted in any form or

by any means, electronic or mechanical, including photocopying and recording, or by any information storage or retrieval system,

except as expressly permitted in writing by ESRI. All requests should be sent to Attention: Contracts and Legal Services Manager,

ESRI, 380 New York Street, Redlands, CA 92373-8100, USA.

The information contained in this document is subject to change without notice.

@esri.com, 3D Analyst, ADF, AML, ARC/INFO, ArcAtlas, ArcCAD, ArcCatalog, ArcCOGO, ArcData, ArcDoc, ArcEdit, ArcEditor,

ArcEurope, ArcExplorer, ArcExpress, ArcFM, ArcGIS, ArcGlobe, ArcGrid, ArcIMS, ArcInfo Librarian, ArcInfo, ArcInfo-

Professional GIS, ArcInfo-The World's GIS, ArcLocation, ArcLogistics, ArcMap, ArcNetwork, ArcNews, ArcObjects, ArcOpen,

ArcPad, ArcPlot, ArcPress, ArcQuest, ArcReader, ArcScan, ArcScene, ArcSchool, ArcSDE, ArcSdl, ArcStorm, ArcSurvey, ArcTIN,

ArcToolbox, ArcTools, ArcUSA, ArcUser, ArcView, ArcVoyager, ArcWatch, ArcWeb, ArcWorld, Atlas GIS, AtlasWare, Avenue,

BusinessMAP, Database Integrator, DBI Kit, ESRI, ESRI-Team GIS, ESRI-The GIS Company, ESRI-The GIS People, FormEdit,

Geographic Design System, Geography Matters, Geography Network, GIS by ESRI, GIS Day, GIS for Everyone, GISData Server,

InsiteMAP, JTX, MapBeans, MapCafé, MapObjects, ModelBuilder, MOLE, NetEngine, PC ARC/INFO, PC ARCPLOT, PC

ARCSHELL, PC DATA CONVERSION, PC STARTER KIT, PC TABLES, PC ARCEDIT, PC NETWORK, PC OVERLAY, PLTS,

Rent-a-Tech, RouteMAP, SDE, SML, Spatial Database Engine, StreetEditor, StreetMap, TABLES, the ARC/INFO logo, the ArcCAD

logo, the ArcCAD WorkBench logo, the ArcCOGO logo, the ArcData logo, the ArcData Online logo, the ArcEdit logo, the

ArcExplorer logo, the ArcExpress logo, the ArcFM logo, the ArcFM Viewer logo, the ArcGIS logo, the ArcGrid logo, the ArcIMS

logo, the ArcInfo logo, the ArcLogistics Route logo, the ArcNetwork logo, the ArcPad logo, the ArcPlot logo, the ArcPress for

ArcView logo, the ArcPress logo, the ArcScan logo, the ArcScene logo, the ArcSDE CAD Client logo, the ArcSDE logo, the

ArcStorm logo, the ArcTIN logo, the ArcTools logo, the ArcView 3D Analyst logo, the ArcView Business Analyst logo, the ArcView

Data Publisher logo, the ArcView GIS logo, the ArcView Image Analysis logo, the ArcView Internet Map Server logo, the ArcView

logo, the ArcView Network Analyst logo, the ArcView Spatial Analyst logo, the ArcView StreetMap 2000 logo, the ArcView

StreetMap logo, the ArcView Tracking Analyst logo, the Atlas GIS logo, the Avenue logo, the BusinessMAP logo, the Data

Automation Kit logo, the ESRI ArcAtlas Data logo, the ESRI ArcEurope Data logo, the ESRI ArcScene Data logo, the ESRI ArcUSA

Data logo, the ESRI ArcWorld Data logo, the ESRI Digital Chart of the World Data logo, the ESRI globe logo, the ESRI Press logo,

the Geography Network logo, the MapCafé logo, the MapObjects Internet Map Server logo, the MapObjects logo, the MOLE logo,

the NetEngine logo, the PC ARC/INFO logo, the Production Line Tool Set logo, the RouteMAP IMS logo, the RouteMAP logo, the

SDE logo, The World's Leading Desktop GIS, Water Writes, www.esri.com, www.geographynetwork.com, www.gisday.com, and

Your Personal Geographic Information System are trademarks, registered trademarks, or service marks of ESRI in the United States,

the European Community, or certain other jurisdictions.

Other companies and products mentioned herein are trademarks or registered trademarks of their respective trademark owners.

Copyright © 2005 ESRI. All rights reserved. 1

Presenter: Sally Swenson ESRI Redlands, California

Metadata:Tips and Tricks

Welcome to today’s live training seminar, Metadata: Tips and Tricks. My name is Sally Swenson,

and I’ll be your presenter.

Joining me today is Jason Cupp, a metadata specialist who will help me answer some of your

questions about working with metadata.


Copyright © 2004 ESRI. All rights reserved.

Seminar overviewTopics

Working with metadataLooking at metadata behind the scenesStreamlining your metadata workflow

FormatEach topic followed by a software demonstration, review, andQ & A session

Today we'll talk about different ways you can work with metadata, we'll look at what goes on

behind the scenes with metadata, and we'll explore ways to streamline your metadata workflow.



Working with metadata

And now we'll begin our first topic: Working with metadata.



OverviewThe standards

FGDC (Federal Geographic Data Committee)ISO (International Organization for Standardization)

Considerations when choosing a standardAlready using a standard? – Use itCreating data and metadata for international applications? – ISONeed detailed metadata? – FGDCJust getting started with metadata? – ISO

Let's get started by looking at the metadata standards. There are two supported by ArcGIS editors.

ESRI support for FGDC is complete. Development of the ISO standard is still in progress.

How do you go about choosing a standard if you're just getting started or have a special project to

deliver?

If you're already working with one of the standards, there's no compelling reason to change just

for the sake of change. If you're working with international applications, then you'll probably

want to work with ISO metadata. If you need detailed metadata, regardless of the data or purpose

for the data, FGDC metadata provides more elements than ISO at this point. But, if you're just

getting started with metadata and are learning the process, ISO might work for you, partly

because it has fewer elements for you to populate and partly because the ISO wizard is easy to

navigate.



Documenting metadataDocumentation versus properties

Documentation: you enterProperties: ArcGIS derives from the data

Where does information for documentation come from?You need to knowOther data• Your own in-house data• ArcGIS tutorial data• ESRI data and maps• ESRI course data • Geography Network• Other clearinghouses

Now that you've decided on a standard, let's make sure we're using the same terminology before

we move on. When we talk about metadata, there are two types of elements: elements that are

documentation and elements that are properties.

Documentation elements are entered via one of the editors. ArcGIS derives properties elements

from the data. For example, the number of features in a feature class is a property of the data.

ArcCatalog knows how to extract this information.

You need to know what to enter as documentation. If you're just getting started, you can look at

the metadata documentation for datasets that you already have access to, such as the tutorial data

that installs with the software, ESRI Data & Maps media, data from Virtual Campus courses or

instructor-led training, or browse the Geography Network or other clearinghouses.



Importing and exportingOutput formats

.xmlYesXML style sheet—contains FGDC and ISO

XML*

.htmYesFGDC ESRI style sheet HTML

.xmlYesSimilar to XML style sheet FGDC CSDGM (XML)*

.txtYes Similar to FGDC Classic FGDC CSDGM (TXT)

.sgmlYesN/A FGDC CSDGM (SGML)

.htmYesFGDC Classic style sheet FGDC CSDGM (HTML)

.htmYesFGDC FAQ style sheet FGDC CSDGM (FAQ)

Ext.ExportDisplays asFile format

Once you've created metadata, you will probably begin thinking about how you can save time and

reuse the metadata in other datasets. ArcGIS gives you the ability to export and import metadata.

In this table, you see the different export formats. Some formats export metadata to HTML that

anyone with a browser can view.



Importing and exportingOutput formatsHow to view

Web-enabled folders

YesXML style sheet—contains FGDC and ISO

XML*

NoFGDC ESRI style sheet HTML

YesSimilar to XML style sheet FGDC CSDGM (XML)*

Yes Similar to FGDC Classic FGDC CSDGM (TXT)

YesN/A FGDC CSDGM (SGML)

No FGDC Classic style sheet FGDC CSDGM (HTML)

NoFGDC FAQ style sheet FGDC CSDGM (FAQ)

ImportDisplays asFile format

The formats highlighted here can be imported and serve as reusable templates.

The XML format can be used for importing and exporting both FGDC and ISO metadata. As you

develop your metadata workflow, remember that you can export and import to create templates.

What exactly is XML? It's a markup language, something like HTML.



Customizing with XMLeXtensible Markup Language (XML)

Can be stored as a file

On the previous slides, you saw that metadata can be exported to an XML file. Many

organizations have specific metadata information that they want included in the metadata. This

information can include an abstract, legal constraints, plus the name and contact information for

the metadata author. You might consider creating a collection of templates containing this

information that you can reuse. When you export XML metadata to a file and store it on disk,

you've devised a handy way to create reusable information.

When metadata is stored in a stand-alone file like this, you don't need to be concerned with

metadata properties because there are none associated with metadata in this format.



Updating propertiesSynchronization

Metadata properties and dataYou control when to synchronize• Automatically when viewed• Manually• On import• Never—or, until specified

Set working synchronizers• Custom command

FGDCGeography NetworkISO

• Turn off metadata you don't want

Another part of your workflow will concern how and when you want to update metadata

properties. This process of updating properties from the data is called synchronization—in other

words, the metadata is synchronized with the data.

You have a number of opportunities for managing when these updates occur. You can choose to

synchronize automatically every time you view metadata; this is the default. You can choose to

update manually and update whenever you want by clicking the Create/Update button on the

metadata toolbar. You can choose whether to update when you import metadata from a file. If

you disable automatic updating when you import, the properties will not initially be updated with

information about the receiving dataset. You might want to do this in order to review the

metadata documentation without having to read through the properties.

Or, you can choose to turn updates off completely. Even manually updating will not override

synchronization when you have turned it completely off.

To control updating, you use the Customize dialog to add the Set Working Synchronizers

command to the Metadata toolbar. By default, all the synchronizers—for FGDC, Geography

Network, and ISO—are initially turned on. When you turn one or more of them off, the metadata


will not update when you view metadata, nor will it update when you use the Create/Update

metadata button.

Why would you want to turn off synchronization? Your organization may have chosen the ISO

standard and doesn't want any FGDC elements. By default, both FGDC and ISO will be stored in

the same XML. So, if you turn off synchronization of FGDC metadata, you ensure that no FGDC

metadata properties will be included with your ISO metadata. This reduces clutter and eliminates

confusion for a user who inadvertently chooses one of the FGDC style sheets to view the

metadata.



Editing metadataMultiuser editing of PGB or ArcSDE

Last metadata author to saveFor PGB, consider using Windows file or folder permissions

What happens when you edit metadata properties?Some properties can be edited• FGDC: projection information• FGDC: geographic bounding coordinates• But, not a good idea to edit these values

* = auto updated

You now know that you can export and import to reuse metadata. But, we've only touched briefly

on creating metadata documentation, the basis of templates. Is there anything in particular you

need to be aware of when editing?

If you have several different users who create and edit data, these might be the same people who

create and edit metadata. If multiple users edit the metadata in the same dataset, only the metadata

author who saves last will find that his metadata is intact.

When editing the personal geodatabase, consider using Windows permissions to manage who can

edit geodatabase metadata.

When you do edit, be aware that some properties can be edited. The FGDC decimal degree

Bounding coordinates element names that you see here display with blue text. That tells you that

these elements can be edited. The green asterisk flags elements that are automatically updated. It

isn't good practice to edit these values, because they will not be synchronized with the data if you

edit your data and add features beyond the current boundaries.



Editing metadataMultiuser editing of PGB or ArcSDE

Last metadata author to saveFor PGB, consider using Windows file or folder permissions

What happens when you edit metadata properties?Some properties can be edited• ISO: online location

* = auto updated

Here you see ISO metadata for distributing the data. Once again, notice the green asterisks that

flag properties that can be updated. In this case, the online location includes a computer name that

was updated automatically. For security reasons, you may not want to expose the names of your

in-house computers and might want to edit this element to show a more benign reference, such as

a Web site. Once you edit the value, it won't be automatically updated again.

Once a property is edited, it is no longer flagged with an asterisk.



Editing metadataFGDC Editor Help

Click

We've talked about editing, so let's find out how you can get help about the elements. When you

edit FGDC metadata, you can click the What's This? button in the upper-right corner and then

click the element.

In this case, you see that the Contact Person element is a mandatory text field.



Editing metadataISO Wizard

Table of contents shows mandatory elements (if missing)Optional elements not shown initiallyQuestions guide you through completing the forms

In the ISO Wizard, the table of contents flags mandatory elements with an asterisk. Although

Title is a mandatory element, the omission of an asterisk tells you that the Title element has

already been populated. Creation date and language, Abstract, and Metadata author are all

mandatory, as are theme codes. Currently, all of these elements are empty.

You can use the table of contents to go directly to the elements you want to edit. As you move

through the panels, you'll find leading questions that serve as help. On the right-hand side of this

graphic, just beneath the title, you see the question that asks you to choose the theme codes that

apply to your data.



Software demonstration

In this software demonstration, I'll show you how to distinguish properties and documentation,

plus how to get help in the editors.

I'll begin by displaying ArcCatalog and then I’ll go to a geodatabase that contains several feature

classes. I'll change to the FGDC style sheet and view the metadata for one of the aquifer feature

classes (aqpsfl01).

In the header (the green area at the top), you see some quick reference metadata.

Some of the metadata is informative. The file name is the same as the name of the feature class,

but the title at the very top isn't very descriptive. Also, the abstract is missing.

Let's link to the Identification Information section and view formatted metadata. Notice the title.

The green asterisk tells us that ArcCatalog automatically updates this property. By default, it

matches the name of the feature class in the Catalog tree. However, I'd like a more descriptive

title. If I change the title, ArcCatalog will no longer update this element—exactly what I want.


There's also a green asterisk next to File or table name property. I don't want to modify the value

for this element because I'll want this element value to match what appears in the tree even if I

rename the dataset.

The Abstract element is documentation, so it has no asterisk. There's no way for ArcCatalog to

derive this information from the data, so I must enter the text myself.

I want to make sure that I'll be editing with the FGDC Editor.

From the Tools menu, I'll click Options, then the Metadata tab.

I want to make sure that auto updates are checked, and then I'll set the Metadata Editor to FGDC

Editor and click OK.

From the Metadata toolbar, I'll click Edit metadata.

On the General tab, I see a hint that tells me that the Abstract element is required. To find out

more about this field, I'll click What's This? and then click in the Abstract text box. The Abstract

element is a mandatory text element that expects summary information. Rather than type in the

information, I'll paste it from another source.

Next, I'll click the Citation tab and then examine the Citation Title field in the same manner—by

clicking What's This?. I click in the text box and find that this is a mandatory text element. I’ll

save the changes.

Now I’ll view the metadata again with the FGDC style sheet. Notice the asterisk is gone for Title.

Both Title and Abstract now contain valid metadata. How does this process differ from editing

ISO metadata?

Let's begin by using the ISO style sheet to view the metadata. The title is not descriptive and no

abstract appears in the header information. Let's go to the Resource Identification section, where

these elements reside. The Title element has an asterisk, so that indicates automatic updating, but

there is no abstract.


To edit, I'll navigate to Tools > Options > Metadata and choose ISO Wizard.

Now I'll click Edit metadata to display the ISO Wizard.

Title is a required element and the absence of an asterisk in the table of contents tells me that it

has already been updated. I'll click Title to see its value. The wizard gives me a hint as to what it

expects as a value and the asterisk flags this as an element that is required.

I want to change the default title, so I'll do that now.

The asterisk next to Abstract in the table of contents indicates that this is a required element that

is currently empty. I'll click Abstract and read the hint at the top of the panel, which tells me it

expects a narrative summary. Now, I'll update the abstract. When I click Next to move to another

panel, notice that there is no longer an asterisk next to Abstract in the table of contents. I'll save,

then view the metadata using the ISO style sheet. Both the Title and Abstract are populated to my

satisfaction and the asterisks are gone. Let's link to the Resource Identification Section for

another look.

In this software demonstration, you saw how the style sheets use asterisks to identify elements

that update automatically. And, in both editors, I illustrated how you can get help on an element-

by-element basis.

This concludes the first software demonstration and now we'll return to the presentation.



Review and Q & AMetadata standardsDocumenting metadataImporting and exportingUpdating propertiesEditing metadata

We began this topic with a discussion of how to choose a metadata standard. You learned where

to find samples of metadata documentation. You found that exporting and importing lets you

create templates. You learned how to take charge of updating metadata properties. And, we

finished with some tips on getting help with the metadata editors.

Now, I'll turn the presentation over to Jason to answer some of your questions.

Question Are there plans to allow for the editing and importing and exporting of metadata using

ArcToolbox?

Answer So this idea about having geoprocessing tools for manipulating metadata in ArcGIS was

recently brought up by our developers here. This is the first time we've heard this idea from

outside ESRI and this is something we are considering. So David, if you’d like, send us your e-

mail through your form and maybe we can contact you and get an idea of what your workflow is

so that we can devise some plans.

Question Why would my organization invest time in metadata? We have not done so for 15

years, so why should we do it now?


Answer So this falls under the category “Metadata, what is it good for?” Well, metadata is good

for many things, I think. As an organization, one of the things that you would want to do is keep

track of your assets and metadata helps you do that. It helps you keep track of your inventory,

what things you have. It helps you categorize the things you have in many different ways. If

you're sharing your data out there with the public at large, metadata helps you carry the

information along with that such as descriptions, abstract, purpose statement, and maybe more

importantly, a statement of what the data is intended to be used for. That's very important for

legal reasons and for advertising as well. If your data is for sale, advertising is one way that your

metadata can be used, too. Also, the processing steps that you've done to create your data can also

be stored inside the metadata as well. So you’re giving somebody an idea of how the data was

made, and what were the steps that were used to create that, and the decisions that were made.

Question How do I know if synchronization is on or off?

Answer The best way is just to add the button that Sally mentioned, Set working synchronizers.

Add it to the Metadata toolbar. You can access it from the Tools > Customize dialog. Under the

commands, it's in the Metadata category. Not only is that tool good for turning synchronization

off and on, but it will give you the status.



Looking at metadata behind

the scenes

Thank you, Jason.

In our second topic, we'll look at metadata from other angles.



Viewing metadataMetadata on the Contents tab

Handy referenceBy default, name and type are displayedAccess via Tools > Options > Contents tab

Imagine you've just started ArcCatalog. Recall that on the right-hand side are three tabs:

Contents, Preview, and Metadata. By default, ArcCatalog opens to the Contents tab. To view

metadata, you'd click the Metadata tab. What if your organization wants you to scan the metadata

and find the author or other metadata for several datasets? Rather than using the Metadata tab, is

there a shortcut to finding this information? You may not realize it, but when you use the

Contents tab, you are viewing metadata. By default, you see the name of the dataset, its type, and

a thumbnail (if one has been created).

You can customize the information that displays on the Contents tab by adding some metadata

elements via the Tools menu’s Options dialog. Here, you can choose the elements to display on

the Contents tab. Now, in addition to the Name and Type elements, you see three other metadata

elements for the dataset: Author, Publication Date, and Projection.

Just about any of the objects you see in the ArcCatalog tree can have metadata, and when you

turn on additional metadata columns, ArcCatalog tries to find the information. To improve

performance, be sure to uncheck the additional metadata elements before you connect to the

Geography Network.



Customizing with XMLMetadata on the Contents tab

Where does this metadata come from?• Notice paths• These are the XML paths to the elements

Earlier, when we added metadata elements to the Contents tab in ArcCatalog, did you wonder

what went on behind the scenes?

As you see in the dialog to add columns, you can choose to add the default elements from a drop-

down list—even after you have inadvertently deleted one.

You can add Author, for example, by selecting it from the Caption drop-down list. In the Property

drop-down list, the first entry displays the XML path to the Author element. The FGDC XML

paths, or xpaths, for the other default columns, such as Title and Place and Theme keywords,

appear as well.



Customizing with XMLCustomizing metadata on the Contents tab

Example: Point of Contact• idinfo/ptcontac/cntinfo/cntperp/cntper• mdContact/rpIndName

Now that you've taken a glimpse of XML paths on the ArcGIS interface, let's look behind the

scenes so you can learn how to locate these paths yourself.

Here's how the dialog will look if you want to add FGDC Point of Contact information. Here you

see a segment of XML paths for FGDC metadata using the XML style sheet.

This contact information is under the idinfo section (or Identification Information), not visible in

the graphic.

On the right, you see comparable ISO XML for Point of Contact. Notice that the FGDC metadata

element names appear in lowercase, while the ISO element names display in a mix of upper- and

lowercase, sometimes referred to as “camel caps.”




Example: Point of Contact• FGDC• idinfo/ptcontac/cntinfo/cntperp/cntper

Once again, see the dialog to add an FGDC element to the Contents tab, then the actual FGDC

metadata and how it looks on the Contents tab. Once you've added the path, you can turn on the

elements you want to display, as you did before, from the Tools > Options dialog.




Example: Point of Contact• ISO• mdContact/rpIndName

How would you add ISO contact information? In the same manner.

In the dialog you see the ISO xpath in the Property text box.



More XMLMore about updating

XML: Sync = "TRUE"Edit outside ArcCatalog

Synchronization

Now that you've had a look at some XML, let's explore it further in the context of updating.

Notice the asterisk next to the Format name element. Also notice that there are no asterisks

associated with the Online source information.

Notice the reference to Sync=”TRUE” for Personal GeoDatabase Feature Class. This “sync” is

short for synchronization, and tells ArcCatalog to update the name of the data's format

automatically.





No synchronization

Now, let's revisit the Online location element. By default, it is a property that is automatically

updated… but it has been edited. Because it has been edited, Sync is no longer set to TRUE and

ArcCatalog will not update the element again—or at least not until someone edits the metadata

and manually restores synchronization. This type of editing needs to be done outside ArcGIS

Desktop.





Importing and exportingTemplatesStand-alone XML

<?xml version="1.0" ?><metadata></metadata>

Another way to edit metadata is to begin with an empty XML file. To do that, open a text editor,

then paste the three lines shown here into the document. Save the document with a meaningful

name and an XML extension, for example, VectorTemplate.xml. Do not use the name

metadata.xml or ArcCatalog will assume that the file is the metadata for the folder in which it

resides.




In our second software demonstration, we'll be working with XML in three completely distinct

situations.

First, let's begin by viewing the same elements we looked at in the first demonstration.

I'll bring up ArcCatalog and then view the metadata for the aquifer feature class (aqpsfl01) using

the XML style sheet.

Recall from the first demonstration that we looked at the File or table name element. When we

viewed the FGDC metadata, an asterisk displayed next to the element name.

Here's the XML syntax for the File or table name element. Notice <ftname

Sync="TRUE">aqpsfl01</ftname> f-t-name is the element. It will still be auto updated by

ArcCatalog, as confirmed by the reference to Sync=“TRUE”.

Now let's look at the XML for the Title element that I edited: <title>PESTICIDE DRASTIC

VULNERABILITY AREAS OF THE FLORIDAN AQUIFER SYSTEM</title>. You don't

see Sync="TRUE", so this element will not be automatically updated by ArcCatalog; it must be

edited.


Now, let's explore other elements that will be automatically updated. I'll scroll to the bounding

coordinates, where you see that each is flagged with Sync="TRUE" and will be auto updated.

In this part of the demonstration, you learned that Sync=”TRUE” tells ArcCatalog to update the

associated element.

For the second part of the demo, let's customize the metadata that appears on the Contents tab.

We'll begin by using the name of the contact person. To begin, where in the metadata is this

contact person information?

Let me select the Points of Interest feature class and display its metadata. I'll open the FGDC

metadata editor and navigate to the Identification Information section, then I’ll go to the Contact

tab > Details > Primary Contact > Person and make sure check Person is selected. The contact

person is Lewis Clark.

I'll close the editor so we can view the metadata using the FGDC style sheet. I'll link to the

Identification Information section and scroll just below the abstract. Once again, you see the

name of the primary contact.

Let's take a third look—this time at the XML. I'll collapse some of the XML opening tags for a

better view of the XML path.

At the top is <idinfo> (identification information), which you've seen twice already. Then,

<ptcontac> (point of contact). Then <cntinfo> for contact information, <cntperp> for primary

contact person, then finally <cntper>, or contact person.

Let's add that metadata to the Contents tab. I’ll go to Tools > Options > Contents tab. Notice that

we'll be adding a Metadata column. Click Add. In the Add Metadata Column dialog, for the

Caption, I'll enter FGDC Point of Contact. Then for the Property, I enter

idinfo/ptcontac/cntinfo/cntperp/cntper.

Now, at a glance, we can view the name of the contact person for this dataset and any others (e.g.,

majrds01 and cndbnd01) that also contain a value. When the value is empty (aqpsfl01), a blank

will display.


In this part of the demonstration, you saw a second way to use the XML by inserting its path to

add an element to the Contents tab.

In the third portion of this demonstration, I'll create an empty metadata file, suitable for beginning

a template.

I go to the Templates folder in the Catalog. No XML files are present. I’ll minimize ArcCatalog,

open WordPad, and paste the three lines I showed you earlier. Then I’ll save as WaterQual.xml.

In ArcCatalog, I’ll view using the FGDC and ISO style sheets. I want to edit the Abstract element

using the FGDC Editor. No properties will update because the XML is not associated with any

data. The XML can, however, be edited further or even imported to another feature class with just

the abstract as part of a metadata workflow.

In this software demonstration, we viewed metadata using three style sheets: FGDC, ISO, and

XML. With the XML style sheet, I showed you how to determine the XML path, or xpath, to an

element so that you can add the element to the display on the ArcCatalog Contents tab. We

concluded with a look at one way to create a reusable template.

This concludes the second software demonstration, so let's continue with the presentation.



Review questionWhat does synchronization do?

A) Updates data with information from metadataB) Updates metadata properties with properties from the dataC) Updates metadata documentation with properties from the dataD) Turns off automatic updates

To submit your answer, click A, B, C, or D and click the Send button.

And now we have a question for you. Locate the Review question link in the upper-left corner of

your browser window. Click this link now.

During the presentation, we talked about synchronization. What does synchronization do?

A – Does it update data with information from metadata?

B – Does it update metadata properties with properties from the data?

C – Does it update metadata documentation with properties from the data?

D – Or, does it turn off automatic updates?

To submit your answer, click A, B, C, or D then click the Send button. You'll learn the correct

answer after the question and answer session.



Review and Q & AViewing metadataCustomizing with XML

Now during this second topic, you learned how to view metadata on the Contents tab. You had a

glimpse of XML and you've found out that you can use XML to customize the ArcCatalog

Contents tab.

Now, let me turn the presentation over to Jason.

Question Dawn asks: Can I view metadata in ArcMap without opening ArcCatalog?

Answer Yes, this will be possible in 9.2. With 9.2, you will be able to do this without any use of

samples. Right now, if you want that functionality, you can download a sample and we'll say

exactly where those samples are in the next, say, minute, so watch for that.

Question Vince asks: Can metadata be created and maintained for ArcInfo coverages?

Answer Yes, this is possible. ArcCatalog does support keeping track of metadata for those.

Question John asks: When importing metadata, how do I not overwrite other existing metadata

when I import?


Answer Many of you have a similar question about the behavior of the import. What the import

does now is it does an overwrite. If you do import into anything, the metadata that was there is

gone and is replaced by the thing you imported from. What we did see is how you can merge

XML based on the FGDC contacts. The demonstration that you saw was an example of merging

two XMLs, or merging data from one source into an existing XML without losing everything. In

the future, we are considering ways to do a better merge and replace XML. So look for these at

9.2 either in the core software or as more samples and tools or scripts.

Question Richard asks: Is there a way to customize the metadata in ArcGIS 9.0? For example,

can we move input items in different tabs or remove the tabs altogether that we don’t want to use?

Answer So I guess we're talking about the FDGC Editor here. We are not considering this kind

of ability for the FDGC Editor at this time, but our plan is to extend this kind of functionality into

the ISO Wizard, so look for improvements in that area.

One thing, if some of you have questions about the Stylesheet drop-down list. When I pick a

different style sheet, I'm not actually changing the XML that my metadata is in, so if I do have

FDGC XML and I view it using the ISO style sheet, I'm just getting a different view of things. It's

not actually changing XML behind the scenes.

Now back to Sally.

Thank you, Jason. I'll take one more quick question from Nick in Denver, who asked about

creating metadata.

Question. Does it have to be FDGC- or ISO-compliant or can you just enter a few elements that

are important to your organization?

Answer We actually recommend that you at least make it minimally compliant. There are many,

many elements, some of which are optional. But probably the best approach is to at least make

sure that you are minimally compliant on the outside chance that you might find that you need to

share this information with someone, ultimately, outside of your organization, and in order to be

establishing good metadata documentation practices.



Review question resultsTo view the results, click the Review question link in the upper-left corner of your

browser window.

What does synchronization do?A) Updates data with information from metadataB) Updates metadata properties with properties from the dataC) Updates metadata documentation with properties from the dataD) Turns off automatic updates

Let's take a look at the review question. We actually have a tie between B and C. But the actual

answer is that synchronization updates metadata properties with properties from the data.



Streamlining your metadata workflow

So far we've talked about ways to use the tools of ArcCatalog for editing, updating, and viewing

metadata. Is there more? In this topic, we'll look at other ways to help you do your work.



Working with metadata more efficientlyHow you work with metadata

Manually editCreate templates from text filesConvert from other data typesUpdate properties

Let's begin by thinking about how you might interact with metadata in your daily work.

You can manually enter metadata using one of the editors. You can create and use templates to

avoid some of the repetition of manual editing. You can convert data to the geodatabase and use

existing metadata. And, you learned how you can manage the automatic updating of metadata

properties. Maybe there are other tasks that you do as well.



Working with metadata more efficientlyMetadata tasks

Create stand-alone XML files as base templates Import templates to several feature classesAdd contact information to metadata

What if you wanted to perform some of these tasks differently than you've learned so far?

For example, instead of creating a text file as your base template, would it be more convenient for

you to create the file in ArcCatalog? Or, you may find that several datasets need to be updated

from the template and you wonder whether there's a way to load the template into all of the

datasets at once. Or, your organization might name several people as points of contact and you'd

like to store their information in a database so you can extract it whenever you edit the metadata.



Creating XML files as base templatesArcCatalog context menus

Add button from Customize dialog

In the previous topic, you learned how to create an empty XML template using a text editor. If

you're already working in ArcCatalog, you might find it easier to create your empty template files

there but, as you see in the default context menus for the Catalog tree, there's no option to create a

new XML file. But, what if you could add the option?

It's possible to add the functionality to ArcCatalog and then add a button to the context menu.

With each click of the button, you can add a new XML document to the Catalog tree. Once

you've done that you can rename the documents and use one of the metadata editors to input your

metadata.



Importing templatesBatch Importer

Add to ArcCatalogSee instructionsChoose feature classesImport file typeLoad templateImport

What about situations when you have several datasets to update? If much of the metadata, such as

the abstract, theme codes, and some keywords, is the same for all of the datasets, consider

importing from a template. And, to work more efficiently, import to all of the datasets at the same

time. Here you see the dialog for a batch importer that you can add to ArcCatalog. It allows you

to import the same template to all the selected feature classes.

The importer includes usage instructions at the top of the dialog. Choose the feature classes you

want to update, and it lets you select the file type of your template. After you browse to the

location of the template, you're ready to import. When the process has completed, a dialog pops

up to confirm the datasets that were updated.



Adding contact information to metadataStore information in a database

Name, address, phone number, e-mail address

You just saw one tool that can be a real time-saver. Are there others?

Here you see contact information for the FGDC Metadata Reference section.

Both the FGDC Editor and the ISO Wizard offer multiple places where you can enter contact

information—such as the metadata author, the point of contact, and the person responsible for

distribution of the data. What if you could store the information in a database and then import the

information when you need it? The ISO Wizard offers a built-in database that does this. Is there

something similar for FGDC?





With the tool you see here, you can add the same convenience for FGDC metadata. This tool acts

like the import tool you use for importing template files. Except in this case you import a custom

format and navigate to the database where you've stored the contact information.





A dialog prompts you to choose one of the names and select where, that is, in which elements,

you want the information to be placed in the metadata. In the example shown here, the contact

information will be stored in the FGDC Metadata Reference section.



Beyond the basicsESRI provides many samples for youBenefits of using samples No programming skills neededLearn by doingSamples streamline metadata tasks

As you've probably deduced, we've moved beyond the default ArcCatalog interface.

ESRI provides many samples for you. Why would you want to use these samples? These were

written by developers at ESRI specifically to help you in your daily work and you can add them

to ArcCatalog. You don't need to be a programmer to use these tools. You can use them without

understanding what goes on the behind the scenes, although you can explore further if you'd like.

Or you can learn by doing; read the instructions to find out what the sample does, then run it.

You'll even find that you can make simple modifications to some of these samples to customize

them to do exactly what you want.

What do these samples do? They streamline or automate GIS-related tasks. You just had a

glimpse at three of these samples and found out that they do a variety of tasks related to working

with metadata.



SamplesArcGIS Desktop Help

Help for Developers

Here's a list of the samples. A checkmark flags the samples that we just talked about. You can see

many others that you can explore on your own.

Notice the icons. You see books; these are part of the help. You also see lightbulbs and wrenches.



Using tips and toolsCode samples divided into tips and tools

With instructionsTips: Visual Basic for Applications (VBA)

Small code examples or shortcutsCopy / Paste

Tools: DLLsMore complete examplesDownload

The icons you just identified divide the samples into two categories: tips (symbolized by a

lightbulb) and tools (symbolized by a wrench).

Regardless of type, the samples all come with documentation that describes what the sample does

and instructions for how to set up the sample and use it.

Tips are small code examples. They run in Visual Basic for Applications (VBA), which installs

with ArcGIS. One way to get started with the sample is to copy its code from the Help and paste

it into the VB Editor.

Tools are more complete examples in the form of DLLs. You can download them and, yes, it

takes a few more steps to set them up than it does for the VBA samples, but the instructions take

you through the process. After you've done this process once or twice, you'll be a pro.



Using tipsHelp for tip samples

Description

Notes

Software

Tip icon

Think back a few moments to the first sample we discussed—creating an XML file. You see that

there is a description of the sample with an optional note that the author added. Plus, up front you

see the software that you need in order to run the sample. And, in the upper-right corner you see

the tip icon, so you can quickly identify this sample type.



Using toolsHelp for tool samples

Description

Software

Tool icon

As you can see, the information for tools is formatted in the same way as the tip, with a

description and the requisite software. Notice that the wrench icon specifies that this is a tool.



Sources for samplesWhere to find samples

ArcGIS Desktop Help > Help for Developers • Follow links• Samples > Metadata

ESRI Online Support Center > For Developers • EDN > Code Exchange > View other code samples• Category > Metadata

ArcGIS Developer Kit• Optional installation with ArcGIS

How do you go about finding these samples? From ArcCatalog, you can access the ArcGIS

Desktop Help, then scroll to the very bottom to Help for Developers and follow the links. Or, go

to the ESRI Online Support Center. The For Developers tab will take you to the ESRI Developer

Network, where you'll find the Code Exchange that is the repository for the samples.

If you installed the ArcGIS Developer Kit, you'll already have the samples. Be aware that the

online resources are dynamic and may contain samples created after the release of the software.

In the demonstration, I'll show you one way to find the samples.




In our third demonstration, I'll show you how to work with one of the metadata samples.

I’ll begin by going to the ESRI Developer Network (http://edn.esri.com) to locate and learn about

the sample. Let me scroll down so you can see the Code Exchange. I'll change the Category drop-

down list to Metadata and then click SEARCH SAMPLES.

Once again, I'll scroll down until I find FGDC Contact Database Importer. Let's skim the

instructions to glean the basics of what we need to know. The sample is designed to work in

ArcCatalog and it provides an Access database for entering contact information. Do we need any

extra products installed? Anyone who has installed ArcGIS 9 meets these requirements.

Notice the "How to use" information. To save time, I already did the setup, so at the end of the

presentation I'll show you where you can find instructions on working with DLLs. As we

continue to scroll, notice the names of the files that will install and how to download. After

extracting the files from the ZIP, the folder now contains the files you see here.

Before we can use the database, we'll need to populate it. But if you try to use an empty database,

ArcCatalog will give you a friendly message.


http://edn.esri.com/

I’ll double-click ContactDB.mdb. For Name, we have N. Thomas, Position is GIS Analyst, and

the Organization is ESRI.

At the bottom of the dialog, I’ll click 2 to create another record. And this one has J. Smith as the

GIS Manager at ESRI. I’ll save that and close.

As you can tell already, this is a handy tool for entering information for several different people

who serve in the capacity of the organization's contacts.

In ArcCatalog, click the Metadata tab, and change to the FGDC style sheet. Select a feature class,

e.g., ptsint01. I’ll link to the Distribution Information section to see what's there.

Although it does contain some metadata, there is no contact information. Click Import metadata.

From the drop-down list, select FGDC Contact Database Importer (this reference was added by

the DLL, and does not display here by default). Navigate to the .mdb, and click OK. I'll select one

of the names, then choose Distributor of the data. I'll click Save and next, we'll view the change.

In ArcCatalog, click Distribution Information to view the change.

In this demonstration, you saw how this tool substitutes for manual editing. It makes it easy for

you to change the data when the contact person changes, as well as when there are personnel

changes within your organization and you need to assign a new contact person to the metadata.

This concludes our third and final demonstration and now we'll return to the remainder of the

presentation.



Review and Q & AWorking with metadata more efficientlyBeyond the basicsUsing tips and tools

In our third topic, we introduced ways to work more efficiently with metadata. You found out

how to go beyond the basics in ArcCatalog and learned how to use ESRI tips and tools in

ArcCatalog.

And, now, I'll turn to Jason for a final round of questions.

Yes, thank you, Sally. We just have time for a couple more questions.

Question Alan asks: Can I apply my own custom style sheets to ArcCatalog's metadata view?

Answer Yes, you can. If you follow ArcGIS, ArcCatalog, and the metadata folder where ArcGIS

is installed, there you will see those style sheets that appear in the drop-down list. You can

examine those files and take a look at that XSLT. You can drop your file there, close ArcCatalog,

and bring it back up, and your own style sheet should appear if you follow the same form that the

others are in.

Question John asks: Can I use the batch importer for the metadata records that are not associated

with the feature class?


Answer Yes, the batch importer will import into any object that ArcGIS knows supports

metadata and that should include stand-alone XML files.

Question When will the development of the ISO standard be complete?

Answer ISO 10139 is complete and should be an international standard by the end of the year, so

expect that 9.2 will support that brand new ISO schema. Again, if you have any questions, please

look to the samples. There you will find a lot of helpful bits of code and information to get you

going.

Thank you, Jason.

It looks like we're running out of time.



For more informationVirtual Campus courses

Creating and Maintaining Metadata using ArcGIS Desktop

Customizing ArcGIS 9

Product book or tutorialUsing_ArcCatalog.pdf

If you're just getting started with metadata, consider taking the Virtual Campus course Creating

and Maintaining Metadata Using ArcGIS Desktop. The course Customizing ArcGIS 9 steps you

through the process of adding VBA and DLL samples to ArcGIS. The PDF Using ArcCatalog

comes with the software and contains a metadata tutorial.

Additional resources will also be available on the What's Next page of the recorded seminar.


Thanks for participating

On behalf of ESRI, I'd like to thank you all for attending. We hope you enjoyed today's seminar.

In a few days, a recording of the seminar will be available on the Virtual Campus.

Your comments help us improve our seminars. Please take a moment to complete our survey—

just click the Give us feedback link to take the survey.

Thanks again.

Goodbye.


ws metadata tipsandtricksslides

Technology