Australian Spatial Data Infrastructure logo
Header image.

Australian Spatial Data Directory (ASDD)
Site search:
home | about | feedback

ASDD Search

Metadata search
Advanced metadata search
Search help

Architecture of the ASDD

Architecture and technologies
Help
Node descriptions

Metadata Management

ANZLIC metadata guidelines
ANZMETA Document Type Definitions
Validation tool
Reports
OASIS Catalog

Z39.50 Protocol

Overview
Configuration

Establish Nodes

Requirements and Standards
Node status
Node Managers Interface
Implementing ASDD nodes
Modified: 2009-12-07

Establishing individual ASDD nodes: Case 4

Note: this is a mythical case study (overview page explains further)

small organisation with a small metadata collection; hosted node behind another organisation's server; minimal solution for now, we will grow later

Description of the organisation

We are a small Cooperative Research Centre which assesses the impacts of feral animal species on native wildlife. Our spatial data comprises GIS layers and georeferenced scientific reports.

Expertise

Our staff comprise ...

  • a business manager
  • a competent technical assistant who also is in charge of our business promotional material and does any technical support
  • two GIS scientific professionals

We do not yet want to learn about this Z stuff. We just want to concentrate on our scientific business. So we will use the "hosted node" option for the Z39.50 search services.

Metadata entry and management will be the responsibility of the technical assistant.

Description of our metadata collections

We have about 20 geospatial datasets as GIS layers. There are about 10 scientific reports with supporting listings of point locality data.

Each dataset will have a concise dataset description with lots of useful words. The dataset descriptions will have links to further information and example map products which utilise the dataset.

Some datasets are free, to offer enticement for our main products.

Metadata management

Note: Metadata management is a separately funded ongoing activity. We provide a simple overview of how we do it. No cost estimate is provided here. However, a component is included for preparing the metadata for indexing and delivery.

We have found an Applications Service Provider which gives us Internet-based metadata entry and editing facilities. The service caters for metadata validation and production of presentation documents. We just concentrate on adding the metadata content. When we have finished editing metadata, we copy the resultant documents back to our local computer.

Internet server capabilities

We have an existing Web server. We have a copy of our metadata documents on our Web server. This enables users to browse our metadata and enables stable URL references. The Z39.50 search services are provided by our hosting organisation.

Description of our Z39.50 solution

We have found an organisation that will host our node behind their existing server. They already have a Z39.50 server operating to provide their ASDD node. It is a simple matter of adding our document collection behind their Zserver and utilising the same indexing procedures. They will monitor the Zserver to ensure that both of our nodes are always available.

Whenever we want to update some of our metadata, we send a Zip file of the relevant documents to our hosting provider. They replace the documents, remove any that we ask to be deleted, then run the indexing procedure.

Overview estimates of the resources required

Note: estimates are for guidance only
IM ... Internet Manager
TA ... Technical Assistant
BM ... Business or Project Manager
MM ... Metadata Manager
PM ... Product Manager
Ballpark estimate for initial setup: $A2,500 to $A5,000
Ballpark estimate for each year of operation: $A4,000 to $A7,000 per annum
(add those two estimates together for the first year)
The table below provides a breakdown to the compents that comprise these ballpark estimates.
Task Resources
planning, background research,
project documentation
  • research and gather documentation:
    BM 2 days, TA 1 day
  • liaise with ASDD and jurisdiction rep:
    BM 1 day
  • meetings for solution design:
    BM 1 day, TA 1 day
  • prepare project plan:
    BM 2 day, TA 1 day
metadata preparation
  • Note: metadata management is separately funded
  • package updated metadata and send to hosting provider
    TA 0.25 days per month
Internet server costs
  • data traffic costs, a bit less than web server
Z39.50 services solution
(hosted node)
  • design solution, liaise with hosting provider
    BM 1 day
  • Fees for hosting: $A1,000 per annum
  • Software fees: nil
ongoing project management and
services review
  • project management:
    BM 0.25 days per month ongoing, TA 0.25 days per month ongoing
  • services review twice yearly:
    BM 2 days per annum ongoing, TA 1 day per annum
The ASDD is an essential component of the Australian Spatial Data Infrastructure (ASDI). The gateway to the ASDD is maintained by Geoscience Australia on behalf of ANZLIC - the Spatial Information Council, as part of its broader Australian Government responsibility for the ASDI.
The individual ASDD nodes are implemented by State/Territory jurisdictions, Australian Government agencies, and commercial organisations (for details see all node descriptions). It is the responsibility of individual nodes to maintain their own metadata and nodes in accordance with the ANZLIC Metadata Guidelines and the ASDD Requirements and Standards.