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: 2004-06-09

Establishing individual ASDD nodes: Case 1

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

small organisation with a small metadata collection; use existing Internet server machine; use freely available Z39.50 software; develop in-house expertise, do-it-ourself

Description of the organisation

As a supplier to the various makers of tourist maps, we provide specific spatial data as listings of point location data. Each dataset is a simple comma-delimited text file, one point per line with attributes.

We already use or Internet server as our main channel for product delivery. We have in-house expertise for manageing our Internet server - it is crucial to our business, so we retain control.

Expertise

Our staff comprise ...

  • a business manager who still does a little GIS work and also provides some direction for our Internet strategy
  • a competent assistant who also is in charge of our business promotional material
  • two GIS professionals who must concentrate on product delivery
  • one Internet services manager who also does technical support
  • everyone has technical skills and the understanding required to run our small business, we have always been a computer-based office

We want to develop in-house expertise, because we see our Web server and our ASDD node as core business. Our Internet services manager has the Web server settled down now and is in a postion to learn about Z39.50 search and retrieve.

Metadata entry and management will be the responsibility of the technical assistant. Metadata validation, metadata system implementation, Z39.50 server implementation and management will all be handled by the Internet manager.

Description of our metadata collections

We have about 100 datasets. Each is a point-location datafile for a particular map theme. A few of the datasets are really sub-datasets, as they have a parent dataset with some important supporting files.

Each dataset will have a concise dataset description with lots of useful words. The dataset descriptions will have links to our web-based order system, and have links to further information and example map products which utilise the dataset.

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

We will have one ASDD node holding all of our product metadata. In the future, we intend to sell map images which utilise our point listings - descriptions of those products will form another ASDD node.

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 use a freely available PC database and export the set of updated XML documents. The Technical Assistant enters all metadata and gets each document reviewed by the relevant product manager.

Our clueful Internet Manager has written a simple program which validates each XML document and generates presentation documents. It also automatically adds a supplementary information section to each metadata document, and adds links to some relevant supporting documentation. Later, we will either enhance our own metadata production system or maybe utilise third party services.

Internet server capabilities

We already have a strong Internet server machine, which runs our Web server and anonymous FTP server. The operating system is Linux, so we have a reliable UNIX server with the usual software for running general Internet services (e.g. Apache web server, Perl).

We have a dedicated machine at our local Internet Sevice Provider (ISP). We are able to securely log in to our server to compile and configure any software that we choose. We will also have a Z39.50 server running on our internal network. When metadata and software is fully tested, it will be replicated on our public server.

Description of our Z39.50 solution

We use freely available Z39.50 software. The Z39.50 server will index the collection of static XML documents. Our Internet Manager will learn in the usual way how to install and manage the server ... review avaliable documentation, investigate other Z39.50 services that use the software, experiment with a test installation on our internal server, discuss issues on relevant email listservers. The extensive ASDD technical documentation was a big help.

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: $A7,000 to $A10,000
Ballpark estimate for each year of operation: $A7,000 to $A12,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:
    IM 4 days, TA 2 days
  • liaise with ASDD and jurisdiction rep:
    IM 2 days overall
  • meetings for solution design:
    IM 2 days, TA 2 days, BM 1 day
  • prepare project plan:
    IM 4 days, TA 2 days
metadata preparation
(design, implement, operate)
  • Note: metadata management is separately funded
  • run batch validation and update ASDD node:
    IM 0.25 days per month, TA 0.25 days per month
  • Software fees: nil
Internet server costs
(existing server and ISP arrangements)
  • no increased direct costs
  • increased traffic costs, a bit less than web server
Z39.50 services solution
(design, implement, operate)
  • install Zserver, configure, test:
    IM 4 days
  • monitor Zserver and review logfiles:
    IM 0.5 days per month ongoing
  • Software fees: nil
ongoing project management and
services review
  • project management:
    BM 0.5 days per month ongoing, TA 0.25 days per month ongoing
  • services review twice yearly:
    IM 4 days per annum ongoing, TA 2 days 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.