**Geospatial OneStop Counselor Handbook**

**Second Draft**

**Janurary 26, 2006**

**Michelle Anthony -- <Anthony@usgs.gov>**

**Melissa Wegner -- <wegner@usgs.gov>**

**Table of Contents**

Introduction...........................................................................................................................2

Objective.................................................................................................................2

Counselor Assignments and Status
.....................................................................2

The Counselor
Process.........................................................................................................3

Provide Assistance to Transition from Clearinghouse to
GOS......................3

Identify Existing GOS Nodes to Match Clearinghouse Nodes
.................... 4

Check Harvesting
Status........................................................................................5

Harvesting By
ArcIMS..............................................................................................6

Harvesting By
WAF...................................................................................................6

Harvesting By CS-W.....................
.........................................................................6

Harvesting By Z39.50.....................
.........................................................................6

Harvesting By ???
......................................................................................................6

Resolving Harvesting
Issues.....................................................................................6

Resolving Validating and Publishing
Issues............................................................7

Outreach to Non-NSDI Clearinghouse
Publishers................................................................X

Barriers to
Counseling...........................................................................................................8

Appendix A: Isite Z39.50 Metadata
Server........................................................................8

# Notes: There are many ISSUES noted in red font throughout the document. These are issues that are either unanswered or the counselors do not know how to provide technical expertise in this area. These need to be addressed in order to develop a consistent counseling process. 

# 

# Introduction

### Objective 

This document should be used by counselors to assist in the counseling
process of GOS2 nodes. Each GOS counselor has been assigned a number of
clearinghouse nodes from the FGDC Clearinghouse system and they are
responsible for the migration of these metadata records into the GOS
system. The counselor assignments can be found in Appendix B or online
as described below.

### Counselor Assignments and Status

A report has been compiled that combines the FGDC Clearinghouse nodes,
the registered GOS nodes, and the counselor assignments so that a
comparison of completed and uncompleted nodes can be a resource for
counselors. This report will be referred to as the "Clearinghouse-GOS
Counselor report" throughout the remainder of this document.

Each counselor has the responsibility to update and confirm the node
information for their assigned nodes in this report. Use the following
process to open the Clearinghouse-GOS Counselor report and review and
update your assigned nodes with the latest information.

1.  Using your Internet browser, open <http://registry.fgdc.gov/reports>
    and click on the "Clearinghouse-GOS Counselor Report" in the
    "Available Reports" section. The report will open as an Excel
    report.

2.  Locate your assigned nodes using the "assignment" column

3.  Review the report to confirm that the information for your nodes.
    The initial data for this report was generated from inspections of
    existing Clearinghouse and GOS databases to best guess those nodes
    that have already transitioned to GOS. It is important to confirm
    this information.

> The color coding of the Excel report represents the following type of
> nodes:

a.  White Highlighted Nodes: These nodes have completed the
    Clearinghouse to GOS transition and have been linked between the two
    systems using the GOS2 Harvesting ID and User Name fields.

b.  Yellow Highlighted Nodes: These nodes do not have a corresponding
    record in the GOS system. Counselors should work with these nodes to
    contact the organization, assist with the registration and
    harvesting processes, as well as perform checks on the status of
    harvesting.

```{=html}
<!-- -->
```
4.  If a counselor discovers that the node information needs to be
    updated, send the appropriate information to Melissa Wegner
    <wegner@usgs.gov> so the report can be updated.

> **NOTE:** It is important to confirm that the "GOS2 Harvesting ID" and
> "GOS2 User Name" fields are correct as they provide the linkage
> between the Clearinghouse and GOS systems.

# 

# The Counselor Process

### The following processes describe how the GOS counselors should provide assistance to organizations that are transitioning from the Clearinghouse system to GOS. All processes below assume the counselor has a user account in GOS and access to the My Tools \> Administration reports.

### Doug -- do you want to include your decision tree here?

### 

### Transition from Clearinghouse to GOS using Z39.50

This section describes the registration, validation, and diagnostic
process of migration an existing Z39.50 metadata service to be visible
under geodata.gov. Counselors should confirm that all the individual
nodes assigned to them are registered and have set up harvesting,
upload, or form entry in the GOS system. Perform the following steps to
provide counseling for your individual nodes to help transition them
from the Clearinghouse to GOS.

1.  Contact the node administrator using the available FGDC contact
    information in the Clearinghouse-GOS Counselor report. If you need
    additional contact information, click on the link to view the full
    Clearinghouse record. Discuss with them if they are willing to
    participate in the migration to GOS and if they've already
    registered. Ask the node administrator to email you when they have
    completed the registration process and to include the 'Publisher
    Name' under which they registered.

2.  Walk the node administrator through the GOS registration and
    harvesting setup. This process is defined in the "Guidance Document"
    found at <http://registry.fgdc.gov/reports> under the "Counseling
    Documents" section.

    a.  Make a note of the publisher name used during the registration
        process as it will be used in the next steps.

Additional Notes:

a.  If a node/site is registered as a clearinghouse, then the site gets
    registered as a single metadata record about an interesting website
    to which one must go and start a whole new search. It does not go
    and harvest the metadata from the clearinghouse

```{=html}
<!-- -->
```
3.  Confirm that the node contact is registered as a GOS publisher

    a.  Within GOS, navigate to "My Tools", "Manage Publishers"

    b.  Sort the "Manage Publishers" Report by clicking on the Publisher
        Name column heading link.

    c.  Attempt to locate the new publisher using the information from
        the previous step.

    d.  Click the user name link to view the additional GOS registration
        information and confirm the match.

> ***FAQ***: ***When will the publisher appear in the publisher list?***
> Directly after completing the 'Become a Publisher' registration form,
> the publisher should appear in the publishers list.

4.  Confirm that the harvesting is set up and records have been
    published.

> ***FAQ***: ***When will the node show up in the harvesting list?***
> Directly after a publisher has registered a node, the information for
> this node is accessible from the publishers list for Administrators
> and Counselors.
>
> ***FAQ***: ***When will the node be harvested for the first time?***
> The site will be included in the schedule for frequency that the node
> is be harvested in. The site will then be harvested according to that
> schedule. For sites that have a schedule of harvesting once, the goal
> is to harvest these within a week after registering?

**QUESTION:** **Does the first time harvesting still require
administrative intervention? Is there an action that Counselors should
perform to kick start this manual process?**

**QUESTION:** **Did we not agree to have nodes schedule and get
immediately harvested? Then once harvested, change the nodes harvest
registration to the harvest interim they desire?**

a.  Within GOS, navigate to "My Tools" and "Reports and Statistics".
    From the search criteria, select the "Harvesting Report" from the
    pull down list.

b.  Scroll through the "User Name" column for the publisher name used in
    the previous step.

c.  Confirm that the records were harvested by checking the "Harvested"
    column in the Harvesting Report.

    a.  If the records were not harvested or if the record numbers
        appear to be incorrect, refer the below "Resolving Harvesting
        Issues" section for possible solutions.

### 

### Identify Existing GOS Nodes to Match Clearinghouse Nodes 

Much time has been devoted to transitioning metadata servers from the
Clearinghouse system to GOS. In order to track the status and progress
of the counseling task, we need to identify and link those organizations
and servers that have successfully completed this transition.

Counselors should identify their Clearinghouse nodes that do not have a
"GOS2 Harvesting ID" and "GOS2 User Name" in the Clearinghouse-GOS
Counselor Report (should be highlighted in yellow). Use the following
process to determine if these Clearinghouse nodes have been successfully
transitioned to the GOS system.

1.  Within GOS, navigate to "My Tools" and "Reports and Statistics".
    From the search criteria, select the "Harvesting Report" from the
    pull down list and select "Show Report".

2.  Attempt to find a match in the harvesting report to the existing
    Clearinghouse metadata server. Use the Registry z39.50 Server
    Address, Registry Contact, Registry Contact Email, Registry
    Organization, and Registry Node Information found in the
    "Clearinghouse-GOS Counselor Report".

3.  If names look similar but not exact, counselors may find it useful
    to perform an nslookup on the Registry and GOS2 server names to
    confirm that they point to the same server.

    a.  Open a DOS window by selecting Start, Run, and then type "cmd"

    b.  Type "nslookup \<servername\>" where \<servername\> is the
        machine name or IP address from the "Registry z39.50 Server
        Address" of the Clearinghouse-GOS Counselor report.

    c.  Compare each of the returned names and addresses for a match.
        Matching names will likely indicate the same node.

4.  If you cannot locate the node in the GOS harvesting list, contact
    the node administer using the available contact information and
    confirm that they have registered and set up for harvesting.

```{=html}
<!-- -->
```
a.  If the contact indicates that they are not registered and set up for
    harvesting, refer to the above section "Provide Assistance to
    transition from Clearinghouse to GOS" to assist them with the
    registration and harvesting setup of the node.

b.  If the contact confirms that they are registered and set up for
    harvesting with geodata.gov, contact Ginny Pyles
    <Ginny_Pyles@blm.gov> with the contact and node information to
    determine the status of the node.

```{=html}
<!-- -->
```
5.  Once the linkage between the Clearinghouse node and GOS node has
    been identified, contact Melissa Wegner (<wegner@usgs.gov>) with the
    GOS username and ID information to update in the Clearinghouse-GOS
    Counselor report.

### 

### Check Harvesting Results 

Each counselor needs to confirm that all the individual nodes assigned
to them are being successfully harvested. Perform the following steps to
provide counseling for your individual nodes from the Clearinghouse-GOS
Counselor report.

1.  Within GOS, navigate to "My Tools", "Reports and Statistics". From
    the criteria, select the "Harvesting Report" from the pull down
    list.

2.  Using the "GOS2 User Name", locate the node in the "Harvesting
    Report".

3.  Using the Harvested, Validated, and Published columns, determine if
    you node has been successfully migrated to GOS by the final number
    of records published.

The definitions for each column are the following:

-   Harvested- Number of records retrieved from node since the last
    harvest, this includes new and updated documents since last harvest,
    if the record is already on GOS and this is not an update then the
    record won't be retrieve.

-   Validated -- Number of records that passed the GOS harvesting
    validation

-   Published- Number of documents actually published.

    -   **ISSUE: This number can be lower than the validation number
        because of the following errors that are not checked in
        validation but might not be allowed because there were database
        errors:**

        -   **The title was \> 256 characters.**

        -   **Language didn't match specifications in xml schema**

        -   **Other items that may affect data loading**

**ISSUE:** **Does the error for the title being longer than 256
characters appear in the error report? Long titles were discussed in a
counselor's telecom. Best metadata practices encourage metadata creators
to include a level of information to enable distinquishing metadata
content by the title.**

> **ISSUE:** **We would like the protocol added to the harvesting
> reports to assist counseling MH: this can be accommodated in an
> enhancement.**
>
> ***FAQ: After changing the protocol errors, when will the node be
> re-harvested so the counselors can verify if the errors were
> corrected?*** The node will be re-harvested according to normal
> schedule (frequency) for the node using the new protocol information.
>
> **ISSUE: We should discuss the possibility of having a "Harvest Now"
> option so the user can immediately see the results and continue to
> correct errors in they still exist.**
>
> ***FAQ: Why do some publishers show that records were harvested and
> published but 0 records were validated? For example, see publisher
> cyang3.*** In these situations, validation has been turned off in the
> harvestor. This happens sometimes when testing harvesting nodes.
>
> **ISSUE: How do we know that the validation has been turned off? What
> should counselors do in these situations?**
>
> **ISSUE: Some publishers show a (-) negative item count. See
> publishers JBosch 777, pinde9, and stanfort.**
>
> **MH: we will look into this.**
>
> The "Item Count" represents the number of metadata documents (records
> from GOS1, records uploaded using the online form, xml record upload,
> and/or record harvesting) + the number of folders the publisher has on
> the site. These may come in through harvesting, through individual
> upload, through creation in the online form, or through reassigning
> ownership by portal admin.'s. It is well possible that this number is
> different from the number of harvested docs. (extracted from MH email
> 5/9/06 and GP email 4/5/06)
>
> ***FAQ: Many nodes show incorrect dates for the "Last Harvested Date".
> For example, 1/1/1900 and 1/1/2005 in the harvesting info access
> database. Why?*** The harvest access database is not part of GOS. The
> last harvest date when registering a new site defaults to old dates
> since the harvester uses this date to retrieve documents in the next
> harvesting cycle. A date of 1/1/1900 indicates that the site was not
> harvested at all. This may occur for nodes for which metadata was
> migration from GOS1 to GOS2.
>
> **ISSUE: Should there be an action associated with these situations?**
>
> ***FAQ: A few publishers show an item count \> 1 but where you look at
> the harvesting report history, there were not records harvested,
> validated, or published. What does this mean?*** This means that all
> the information was migration from GOS1 to GOS2. This migration did
> not use harvesting.
>
> **ISSUE: Should there be an action associated with these situations?**
>
> If all 3 columns contain the same number of harvested, validated and
> published records, the node is operating correctly in GOS and no
> action is required!
>
> If 0 records were harvested, refer the "Resolving Harvesting Issues"
> section of this document.
>
> If records were harvested but the validated and published totals
> differ, refer to the "Resolving Validating and Publishing Issues"
> section of this document.

4.  The number of published records should match the number of records
    from the "Manage Metadata" option found under "Administration" in
    the left side menu. When using this method do not count the
    "disapproved" records in the published number only "approved" and
    "reviewed" should be counted which both mean the record has been
    approved. Differences discoved between the number of records using
    this method and the number from selecting the publish option from
    the "Manage Publishers" section may be due to some records getting
    removed after they were published, most of these were during the
    move from GOS1 to GOS2 and due to duplicates that were removed.

-   Log In using your user account at geodata.gov.

-   Select "My Tools" from the tabs at the top of the page.

-   Select "Manage Metadata" from the left side menu.

-   Under metadata owner enter the user name for the account, you may
    use wild cards ex. instead of entering simolaur you could enter
    simol\* and get all records returned that match the criteria.

-   Change the "Updated date" to be something like 01-01-2001 and
    \<todays_date\>.

-   Change status to "Any".

-   Select "Submit".

### Resolving Harvesting Issues

1.  If the records were not harvested, check the metadata type (xml,
    sgml) and confirm that they selected the appropriate type when
    registering their node. If the node was migrated over from GOS1
    chances are that they did not have the option to select sgml when
    registering, in that case counselors will need to notify Melissa
    Wegner and request that the node be reharvested for sgml records.

> **MH email 5/9/06: As far as sgml/xml is concerned, there is an
> enhancement in the list (Nimbus) that would improve the way that users
> can indicate what metadata they have. Some sites overlap in the
> metadata between xml/sgml and some metadata is available in both
> formats, these cases should ideally be avoided. The best suggestion is
> to register one of the two types with GOS not both.**

2.  Confirm that the node/site did not register as a clearinghouse. If
    they did register as a clearinghouse, then the site gets registered
    as a single metadata record about an interesting website to which
    one must go and start a whole new search. It does not go and harvest
    the metadata from the clearinghouse.

3.  If the records were not harvested, check the harvesting protocol for
    errors.

    a.  Open the "Manage Publishers" report and search for the "User
        Name" field.

    b.  Select the link found under "Harvesting Sites" for the
        publisher. This will link to the number of sites in GOS.

    c.  Select the "Update" button in the new window to display the
        protocol information.

4.  To find out if a single record has been harvested.

    a.  View the xml record and scroll down to the bottom. Find "Input
        Source" and if it equals 0 the record was harvested.

5.  Based upon the protocol selected, ensure that the following rules
    have been followed:

**ArcIMS**

-   Use the repository URL to confirm that the ArcIMS service has
    http:// in the URL

-   ArcIMS reference must be to metadata server/service and cannot be to
    metadata explorer application

    a.  Verify that the ArcIMS is operating correctly by connecting to
        the node in ESRI ArcCatalog using the information provided in
        the node registration.

    b.  **ISSUE: What do we do if we are not running ESRI products on
        our machines? For example, Sharon does not.**

    c.  **QUESTION: For future registrations, can the node registration
        form detect if the site registered is an IMS server and the
        proper address is entered? At an earlier counselor's telecom,
        you indicated this could be accomplished.**

-   If ArcIMS 9.1 Z39.50 connector only returns 1 record
    (<http://forums.esri.com/Thread.asp?c=64&f=1336&t=179503#529053>)
    users should download the patch released by ESRI to resolve the
    issue.

    a.  <http://support.esri.com/index.cfm?fa=downloads.patchesServicePacks.viewPatch&PID=16&MetaID=1114>

**Web Accessible Folder (WAF)**

-   WAF must point to a folder and cannot point to a file. Confirm that
    a file is not referenced in the repository URL.

a.  Users that modify the folder location and do not see metadata
    changes that they make reflected on the GOS site should perform the
    following steps.

    1.  Navigate to the GOS website and log in with their username and
        password.

    2.  Go to "My Tools" and click on "Configure Harvesting".

    3.  If there is a previous entry users should modify it, if not,
        click on the button "Register a New Metadata Site" and enter the
        harvesting info to reflect the revised location of the metadata
        files in their WAF and save it.

    4.  Send an email to GOS requesting that they reharvest the node.
        The reharvest should happen within a week of the request.

    5.  There is a delay in processing the new content so users will
        have to wait to test it out.

-   The WAF folder must be accessible and the server name cannot be
    redirected. Open a browser window and copy/paste the URL to view the
    WAF files. If anything other than a list of files is shown, contact
    the node administrator and assist with resolving the issue

    a.  **QUESTION: Again, when registering a new node, can the
        registration page interpret if a file is being entered for the
        WAF and notify the registrant?**

**CS-W**

-   When registering a CSW, the user should put in the request for the
    capabilities of the CSW. For example:
    <http://gos2.geodata.gov/aimscsw/csw2.0?request=getcapabilities&service=CSW>

-   When registering a CSW, one can click the 'Show Capabilities'
    button. If the CSW Capabilities request is entered correctly, this
    will show the capabilities in a separate window. Otherwise, errors
    will be displayed (missing request, missing service)

> ***FAQ: What are the syntax rules for CS-W?** S*yntax for CSW is
> specified in the OGC documentation for this type of node.
>
> ***FAQ: How should a CS-W node be tested?*** Testing CSW nodes is
> complicated as each CSW may implement a different information model
> and API. Ideally, a document similar to the GOS API document should be
> provided for each CSW. Then there needs to be interaction between the
> harvesting team and the node as was the case for the FEMA CSW node and
> to some extent with the NBII node.

**OAI-PMH**

-   OAI catalogs may implement sets of metadata (similar to Z39.50
    entrypoints). The name of the set (if applicable) to be harvested
    has to be provided. OAI-PMH supports the dissemination of records in
    multiple metadata formats from a repository. The metadataPrefix is a
    string to specify the metadata format in OAI-PMH requests issued to
    the repository and needs to be provided.

-   The OAI node may be tested using HTTP requests such as
    http://martenh:8181/aimsharvester/oai2.0?verb=ListIdentifiers&metadataPrefix=esri_rawxml&set=TOOLKIT_Browse_Metadata

> ***FAQ: What are the syntax rules for OAI-PMH?** S*yntax for OAI is
> specified in the OAI specification
> (<http://www.openarchives.org/OAI/2.0/guidelines.htm>). In general,
> the URL is to a servlet that handles the requests (for example
> <http://www.example.com/aimsharvester/oai2.0>?).

**Z39.50**

-   Confirm that the host field does not contain http:// in the URL

    -   **QUESTION: Same as before, can the registration validate this
        rule?**

-   Confirm that the Z39.50 service and database are available by
    testing the Z39.50 services with the Isite software. See Appendix A
    for Isite information.

    -   Ping the Z39.50 service to confirm that the server is up with
        the following command:

*zping.exe \<server_name\> \<port_number\>*

> If the server reports down, contact the node administrator to restart
> the Z39.50 service

-   Send a search to the Z39.50 service.

*zclient.exe \<server_name\> \<port_number\> "\<database_name\>" "90
-180 -90 180\[1,2060\]"*

> Metadata records should be returned. Otherwise the node is not
> operating correctly and you need to contact the administrator and
> confirm that the software was set up correctly. Refer to Appendix A
> for more information.

### Resolving Validating and Publishing Issues

1.  Confirm that the records were validated by checking the "Validated"
    column in the harvesting report. If the number of validated records
    is lower than the number of harvested records, check for errors
    during the harvesting process.

```{=html}
<!-- -->
```
a.  Select the "Manage Publishers" report.

b.  Sort the report by "Publisher Name".

c.  Select the number link under "Harvesting Sites" to view the
    harvesting history

d.  Select the "History" link found under each site the publisher has
    registered to review the harvesting history

e.  Select "View Reports" to get detailed information about the records
    that were harvested and any errors during harvesting

f.  Notify the node contact about the harvesting results

```{=html}
<!-- -->
```
a.  Make the contact aware of the issue

b.  Suggest they validate their records

c.  Suggest they resolve any errors within the records

```{=html}
<!-- -->
```
2.  Confirm that the number of published records matches the number of
    validated records by checking the "Validated" and "Published"
    columns in the harvesting report.

```{=html}
<!-- -->
```
a.  If the number of published records is lower than the number of
    validated records

    a.  Select the number link under "Harvesting Sites" to view the
        harvesting history

    b.  Select the "History" link found under each site the publisher
        has registered to review the harvesting history

    c.  Select "View Reports" to get detailed information about the
        records that were validated, published, and any errors that may
        have occurred during the process.

    d.  Notify Ginny Pyles <Ginny_Pyles@blm.gov> and see if there were
        any errors when attempting to publish the records

b.  If the number of harvested, validated, and published records appear
    to match a previous harvest (ex. NASA ULRAC) there may have been an
    update or change to all of their records, in which case the existing
    records are updated and duplicates are not published.

```{=html}
<!-- -->
```
3.  Counselors are able to modify existing records by performing the
    below steps. Records that have been harvested should not be modified
    because it will just be overwritten during the next harvesting
    process. The harvested records should be modified by the node admin.
    in their database.

    a.  Transfer the record to your account.

    b.  Download the record and make the modifications.

    c.  Upload the record.

    d.  Transfer ownership back to the original owner.

# Outreach to Publishers Other Than NSDI Clearinghouse Nodes

Counselors are encouraged to identify and enlist publishers that
maintain geospatial data distribution, metadata collection, web mapping
services and other web-based data exploration and/or delivery services.
Special emphasis should be placed on the identification of statewide
web-based geospatial data resources.

1.  Review the companion document (Appendix?) *Assessment of State
    Participation in GOS* to determine the status of Statewide web-based
    geospatial data resources.

2.  Identify and contact the administrator of Statewide resources that
    have yet to be registered with GOS and follow the instructions
    provided earlier in this document at 'The Counselor Process'.

3.  Search for additional web-based geospatial data resources within
    your assigned region using resources such as Geography Network, GIS
    Publications, and listserver discussions. Once identified, contact
    the administrators of the resource and proceed as indicated in the
    prior step,

# Barriers to Counseling

***FAQ: How do we deal with disapproved records?** R*ecords may end up
being disapproved as a result of the manual review process or sometimes
when XML validation is turned off. None of the publishing/harvesting
options result in 'disapproved' records if the validation is turned on.
Disapproved records may be corrected at later harvestings, and get
approved through manual review.

# 

# Appendix A: Isite Z39.50 Metadata Server

-   Download the Isite installation document from
    <http://clearinghouse4.fgdc.gov/ftp> and following the installation
    steps to install the Isite software

-   Once you have the zserver running, you can test the Z39.50 service
    and database by opening a command window and navigating to the Isite
    directory that contains zping.exe and zclient.exe.

#   

# Appendix B: Counselor Node Assignments

The following table provides a list of all clearinghouse nodes listed
with their ID and title as assigned to each of the GOS Counselors.
Additional GOS information is also displayed to show the linkage between
the Clearinghouse and GOS systems. The GOS2 Harvesting ID and User Name
fields show the if a node exists in the GOS system. All nodes that are
not known to yet exists in GOS are highlighted in yellow.

  ------------ ------------------------------------------- ------------ -------------------
  **Registry   **Registry Title**                          **GOS2       **GOS2 User Name**
  ID**                                                     Harvesting   
                                                           ID**         

  **DOUG                                                                
  NEBERT                                                                
  ASSIGNED                                                              
  NODES**                                                               

  775          Testing Image Matters JZACS server                        

  774          Testing Image Matters ZACS server                         

  504          Alaska - Geographic Information Network of  3852         UA_GINA
               Alaska                                                   

  16           Alaska Geospatial Data Clearinghouse                      

  783          Alaska Ocean Observing System                             

  18           Alaska State Geospatial Data Clearinghouse  48           asgdc
               (ASGDC)                                                  

  250          Anchorage Alaska Geospatial Data                          
               Clearinghouse Node                                       

  9            California Environmental Information        36           rkunkel36
               Catalog                                                  

  120          Eastern Sierra Geospatial Data                            
               Clearinghouse                                            

  329          Forest, aquatic, and Rangeland Ecosystems                 
               in the Western USA                                       

  361          Geography Department SDSU Clearinghouse                   

  34           Geography Network                                         

  301          Hawaii GIS Clearinghouse Node               22           gosarc9

  228          Idaho Geospatial Data Clearinghouse         3717         bgodfrey

  51           K12 Geospatial Data Clearinghouse Node                    

  63           Montana State Library                                     

  88           Nevada Dataworks Spatial Data Warehouse     3677         duncanald

  257          Oregon - Portland Metro Spatial Data                      

  129          Oregon Coast Geospatial Clearinghouse                     

  256          San Bernardino Regional Geospatial Data     8            wri
               Clearinghouse, CA. USA                                   

  22           San Francisco Bay/Delta GIS @ REGIS, UC                   
               Berkeley                                                 

  542          Southern California Coastal Water Research                
               Project                                                  

  106          University of Montana                       3687         msweet

  116          Washington State Geospatial Clearinghouse - 3702         bjordan_uw
               All Nodes                                                

  118          Washington State ONRC Clearinghouse for the               
               Olympic Peninsula                                        

  339          Western Riverside Council of Governments                  

  **LYNDA                                                               
  WAYNE                                                                 
  ASSIGNED                                                              
  NODES**                                                               

  274          Alamo Area Council of Governments           3762         aacog

  153          Arkansas GeoLibrary                         9            CAST

  464          City of Fort Worth                                        

  496          Florida - Central Florida GIS (CFGIS) Data                
               Clearinghouse                                            

  17           Geological Survey of Alabama Geospatial                   
               Data Clearinghouse Node                                  

  37           Georgia GIS Data Clearinghouse                            

  261          Gulf Coast NASA/UL Lafayette Regional       5            NASAULRAC
               Application Center Node                                  

  521          Houston-Galveston Area Council              3952         cive1em
               Clearinghouse Node                                       

  399          Intergraph IMGS Test Server                 41           dvyoung

  54           Louisiana Geographic Information Center     3747         lagic

  337          Louisiana Universities Marine Consortium                  
               (LUMCON)\--Gulf Coast Data Center                        

  549          Lubbock City Metadata Service               3742         KevinMulligan

  537          Mississippi DEQ - Office of Geology         118          msdeq

  155          Mississippi State University Geospatial                   
               Clearinghouse Node                                       

  483          Oklahoma Center for Geospatial Information  3682         afinchum99

  444          Oklahoma Data Warehouse - Geo Information                 
               Systems                                                  

  100          Sabine River Authority of Texas                           

  338          Southern Assn of Marine Laboratories        31           LUMCON
               Cast-Net Eastern Gulf Coast Data Center,                 
               Dauphin Island Sea Lab                                   

  524          Strategic Consulting International Publicly 6            inteller
               Available Services                                       

  103          Texas Natural Resources Information System                

  24           Transboundary (US -Mexico) Metadata                       
               Clearinghouse                                            

  **MELISSA                                                             
  WEGNER                                                                
  ASSIGNED                                                              
  NODES**                                                               

  243          CEOS International Directory Network        84           jdivock

  258          Chesapeake Information Management System    62           cims
               Metadata Clearinghouse Node                              

  40           Chicago Regional Clearinghouse Cooperative  3737         jimbash

  128          Coastal Environmental Long-Term Data,       77           ginger69
               Baruch Institute, Univ of South Carolina                 

  32           Delaware Geospatial Information             4362         rdms
               Clearinghouse                                            

  262          Framework Data Survey                       23           morstad

  239          Global Change Master Directory              84           jdivock

  514          HRSA Geospatial Data Warehouse              40           gosarc9

  49           Illinois Natural Resources Geospatial Data  53           beaverson
               Clearinghouse                                            

  486          IndianaMap Data Clearinghouse               4307         jsaligoe

  259          Maryland State and Local Government         4272         dgeeraer
               Metadata Clearinghouse Node                              

  642          Meta-Door - Coastal Offshore Observing Data 3962         jcothran

  265          Michigan GIS                                3752         metzger

  520          Minnesota River Basin Data Center           4602         mrbdc

  62           Minnesota: Department of Natural Resources  3732         romaki

  395          Minnesota: Department of Transportation     35           mndot

  55           Minnesota: Land Management Information      108          lmic
               Center                                                   

  277          Minnesota: MetroGIS                         113          MetroGIS

  67           North Carolina Corporate Geographic         3767         dgiordano
               Database                                                 

  90           Ohio Geographically Referenced Information  127          otiogrip
               Program (OGRIP) Metadata Server                          

  148          Princeton University Library Geospatial                   
               Data                                                     

  359          Red River Basin Decision Information        1            RRBDIN
               Network                                                  

  95           Research Planning, Inc.                     3727         jdahlin

  341          Southern Association of Marine Laboratories 59           cast-net
               Cast-net Atlantic Coast Data Center, Baruch              
               Institute                                                

  526          Tennessee Spatial Metadata Server           85           jed4167

  645          Test Deployment of Earth Observing System                 
               Catalog Service                                          

  766          UNC Charlotte Center for Applied Geographic               
               Information Science                                      

  515          Virginia Access-Middle Atlantic Geospatial  64           cyang3
               Information Consortium                                   

  333          Virginia Geographic Information Network                   

  336          Virginia Natural Resources Geospatial       149          vnrgc
               Clearinghouse                                            

  121          West Virginia GIS Technical Center          155          wvgis

  119          Wisconsin Land Information Clearinghouse    45           wisc

  **MICHELLE                                                            
  ANTHONY                                                               
  ASSIGNED                                                              
  NODES**                                                               

  21           Arizona Clearinghouse Node for Spatial Data 10           azmetanode

  462          CIESIN New York City Dataset                              

  364          CIESIN/NASA - Socioeconomic Data and        145          svinayagamoorthy
               Applications Center                                      

  450          Colorado Metadata Clearinghouse             63           coM3ta

  655          Colorado Plateau Environmental Metadata     129          paullheinrich
               Clearinghouse                                            

  156          Connecticut \-- Geospatial Data                           
               Clearinghouse                                            

  30           Cornell University Geospatial Information   91           jrikert
               Repository                                               

  758          Harvard Navigator                                         

  484          Harvard-GIS - Boston Dataset                43           lovison

  478          Iowa Geospatial Data Clearinghouse          3672         igic

  52           Kansas Data Access and Support Center       97           knelson

  330          Maine GIS Data Clearinghouse                4522         davidkirouac

  287          Mifflin County GIS Department, Pennsylvania 138          simolaur

  354          Missouri Spatial Data Information Service   119          msdis
               (MSDIS)                                                  

  60           MIT/MassGIS Digital Orthophoto Project                    

  147          Mount Desert Region - Hancock County Maine                

  490          Nebraska Geospatial Data Center             4267         dnrmetadata

  68           Nebraska Geospatial Data Clearinghouse                    

  230          New Hampshire GRANIT Clearinghouse Node     47           AllanWright

  97           New Mexico - City of Santa Fe               46           dscholz

  56           New Mexico - McKinley County GIS Center     46           dscholz

  72           New Mexico Resource Geographic Information  95           kbene
               System                                                   

  89           New York State GIS Metadata Repository                    

  92           Pennsylvania Spatial Data Access            29           PASDA

  417          Rapid Online Mapping Network (romap.net)                  

  759          Rhode Island Geographic Information System                
               (RIGIS)                                                  

  83           Southwest Region Road Map of Natural                      
               Resource Data and Information                            

  266          Space Imaging 5-meter Digital Ortho Quads                 

  267          Space Imaging High Resolution Imagery                     

  270          Space Imaging IRS Imagery                                 

  111          Utah AGRC State Geographic Information      3            mpeters
               Database                                                 

  115          Vermont Geographic Information System       137          sharpie

  283          Wilkes University Center for Geographic                   
               Information Sciences                                     

  113          Wyoming Natural Resources Data              19           joakleaf
               Clearinghouse                                            

  122          Wyoming Spatial Data Clearinghouse          133          rmemme

  **SHARON                                                              
  SHIN                                                                  
  ASSIGNED                                                              
  NODES**                                                               

  327          BRD Bibliographic Metadata Node                           

  254          Bureau of Land Management Geospatial Data   89           joshsisco
               Clearinghouse                                            

  87           Bureau of Transportation Statistics - US                  
               DOT                                                      

  58           DOD Master Environmental Library                          

  552          Earth Observing System Catalog Service -                  
               test deployment                                          

  657          Earth Observing System Catalog Service PVC                
               OPS Test                                                 

  658          Earth Observing System Catalog Service PVC                
               TS1 Test                                                 

  659          Earth Observing System Catalog Service PVC                
               TS2 Test                                                 

  356          FEMA MMI Project (Q3 and HAZUS data)        12           weidu

  544          FEMA National Flood Map Service (WMS)                     

  530          Forest and Rangeland Ecosystem Science      107          lindsley
               Center Metadata Node                                     

  541          FSGeodata from the USDA Forest Service      4292         mshadley

  393          NASA ORNL DAAC EOS Land Validation - Earth                
               Observing System Land Validation Program                 

  392          NASA ORNL DAAC Holdings - Oak Ridge                       
               National Laboratory Distributed Active                   
               Archive                                                  

  391          NASA ORNL DAAC RGD - Regional and Global                  
               Data on Terrestrial Biogeochemistry from                 
               Related Sources                                          

  204          National Atlas of the United States         17           jpdonnelly

  66           National Biological Information             11           VHutchison
               Infrastructure Metadata Clearinghouse                    

  244          National Gap Analysis Program Metadata Node 33           VHutchison

  85           Natural Resources Conservation Service                    

  75           NOAA Cooperative Data (COOP) Node                         

  82           NOAA Environmental Satellite, Data and                    
               Information Services (SAT) Node                          

  402          NOAA NMFS Southeast Fisheries Science       104          kowens
               Center Node                                              

  123          NOAA Central Library Historical Data Sets   27           kowens
               (LISD) Node                                              

  73           NOAA Coastal Services Center                125          NOAA_CSC

  124          NOAA National Climatic Data Center (NCDC)   28           kowens
               Node                                                     

  757          NOAA National Coastal Data Development      3722         JBosch777
               Center                                                   

  125          NOAA National Geophysical Data Center       101          kowens
               (NGDC) Node                                              

  126          NOAA National Marine Fisheries Service      14           kowens
               (NMFS) Node                                              

  78           NOAA National Ocean Service (NOS) Node      3902         kowens

  77           NOAA National Oceanographic Data Center                   
               (NODC) Node                                              

  79           NOAA National Snow and Ice Data Center                    
               (NSIDC) Node                                             

  80           NOAA National Weather Service (NWS) Node                  

  94           NOAA NCDC Library Historical Data Sets      39           kowens
               (FDL) Node                                               

  81           NOAA Office of Atmospheric Research (OAR)                 
               Node                                                     

  770          PICES - NOAA NPEM (North Pacific Ecosystem                
               Metadatabase)                                            

  150          Tennessee Valley Authority Maps and Photo   32           tvamaps
               Records                                                  

  108          U.S. Army Corps of Engineers                30           jerry.roy

  433          U.S. Census Bureau                          61           census

  764          U.S. Department of Health and Human         3350         danmelnick
               Services                                                 

  248          U.S. Environmental Protection Agency -      93           jsykes
               Environmental Information Management System              
               (EIMS)                                                   

  489          U.S. Fish and Wildlife Service              67           deb_green@fws.gov

  300          U.S. Geological Survey Advanced Very High                 
               Resolution Radiometer                                    

  751          U.S. Geological Survey Commercial Data                    
               Purchases                                                

  472          U.S. Geological Survey Declassified         4            sneiers
               Satellite Imagery - 1                                    

  475          U.S. Geological Survey Declassified                       
               Satellite Imagery - 2                                    

  297          U.S. Geological Survey Digital Elevation                  
               Model 15-Minute                                          

  298          U.S. Geological Survey Digital Elevation                  
               Model 30-Minute                                          

  295          U.S. Geological Survey Digital Elevation                  
               Model 7.5-Minute                                         

  303          U.S. Geological Survey Digital Line Graph -               
               Large Scale                                              

  289          U.S. Geological Survey Digital Line Graph                 
               100K                                                     

  477          U.S. Geological Survey Digital Orthophoto                 
               Quadrangles-County                                       

  273          U.S. Geological Survey Digital Raster                     
               Graphics                                                 

  247          U.S. Geological Survey DOQ                                

  468          U.S. Geological Survey EO1 Advanced Land                  
               Imager                                                   

  469          U.S. Geological Survey EO1 Hyperion                       

  463          U.S. Geological Survey Geographic Names                   
               Information System (GNIS)                                

  497          U.S. Geological Survey High Resolution                    
               Photography                                              

  152          U.S. Geological Survey Landsat Enhanced                   
               Thematic Mapper Plus (LANDSAT 7)                         

  648          U.S. Geological Survey Landsat ETM+ SLC -                 
               off                                                      

  133          U.S. Geological Survey Landsat                            
               Multispectral Scanner Imagery                            

  134          U.S. Geological Survey Landsat Thematic                   
               Mapper Imagery                                           

  249          U.S. Geological Survey National Aerial                    
               Photography Program                                      

  493          U.S. Geological Survey National Atlas of                  
               the United States                                        

  471          U.S. Geological Survey National Elevation   7            sneiers
               Dataset (Pre-Defined Areas)                              

  255          U.S. Geological Survey National High                      
               Altitude Photography                                     

  503          U.S. Geological Survey Shuttle Radar        34           sneiers
               Topography Mission (SRTM) BIL                            

  13           U.S. Geological Survey South Florida        3757         hhenkel
               Ecosystem                                                

  362          U.S. Geological Survey Space Acquired                     
               Photography                                              

  492          U.S. Geological Survey SPOT                               

  344          U.S. Geological Survey Survey Photography   37           sneiers

  110          U.S. Geological Survey Water Resources                    
               Spatial Information                                      

  328          USGS-BRD-Columbia Environmental Research                  
               Center Metadata Node                                     
  ------------ ------------------------------------------- ------------ -------------------