Using this document management facility you can describe your
collections of geospatial data. You will be guided through the procedure
of documenting a node description using fill-out forms.
Whenever you choose to update your node description, your existing
details will be presented in an HTML forms. Simple interfaces (with
pre-defined option lists and error checking) allow you to complete each
section of the document at your own pace. The application will ensure that
all required fields are present and legitimate.
Submitting the form will validate your node description, generate
presentation documents, and give you the option to publish. You can edit
the documents whenever, and as often as, you choose.
To give you better control over presentation, some fields can accept
either plain text (presented as a single paragraph) or a limited set of
HTML elements. The two tables below explain the "Inline text elements"
and "Block text elements" that can be used.
- The parser will report errors if you use these presentation elements
incorrectly.
- All tags must be closed ... <li> must finish with </li>
and <p> must finish with </p>. See general
discussion of HTML element usage
- Elements must be specified in lower-case only.
- The hypertext anchor element (<a>) is the only element
that can have an attribute
- e.g. <a href="http://www.anzlic.org.au/">ANZLIC</a>
- can only use the href attribute
- attribute value must be surrounded with double-quotation marks
Inline text elements
- used for formatting
- can only be used in the following metadata elements ...
- node-description
- description
- home-url
- about-metadata-url
- local-browse-url
- local-search-url
- other-url
| Inline text elements |
Description |
| tt |
teletype (fixed width font) |
| i |
italic |
| b |
bold |
| big |
big font |
| small |
small font |
| em |
emphasis (usually italic) |
| a |
anchor, hypertext link to Internet resource |
| br |
forced line break |
| sub |
subscript |
| sup |
superscript |
Block text elements
- used for layout
- can only be used in the following metadata elements ...
- node-description
- description
| Block text elements |
Description |
| p |
paragraph |
| pre |
pre-formatted (fixed width font) |
| ul |
unordered list |
| ol |
ordered list |
| li |
list item |
| dl |
descriptive list |
| dt |
descriptive list term |
| dd |
descriptive list definition |
See notes about known problems if
you are using MS Internet Explorer version 3.
After every editing session your document is validated against the set
of rules for node descriptions. Mandatory elements must be present and any
additional HTML elements must be valid.
The Guide to parser error messages
explains some of the error messages that you may encounter when producing
your documents, especially if you add HTML elements to enhance the
document presentation. The parser is strict.
An HTML presentation document is generated whenever you edit a node
description.
Any empty elements are not shown on the presentation document. So if you
do not want to publicise a contact phone number then simply leave this
optional element empty.
Some elements are never shown, such as manager contact details.
The documents that you generate will remain in your preparation folders
while you edit them, view them, and perhaps edit them again. When you are
satisfied with the presentation of your node description, and have gained
clearance, you can then choose to publish it.
Publishing happens immediately. The ASDD
node descriptions index page is automatically regenerated.
- Title
- The title of your node, as you want it to appear on the search
interface and the "Status
of nodes" page.
- Use a descriptive title with words as well as acronyms
- More than 2 characters and less than 80
- Cannot contain double-quote (") or pipe (|)
- Required
- Node type
- Simple classification of nodes
- Choose one or more from the scrolling list
- Required
- Node description
- Generally describe the purpose and content of the node.
- This can also contain certain HTML elements
which enable you to link directly to relevant URLs, present words as
bold or italic, etc.
- Maximum of 2000 characters (about 250 words).
- Required
- Hostname
- The hostname of the server as known by the Domain Name System
(DNS)
- Required
- Port
- the server port on which the Z39.50 server is listening
- Required
- Repository name
- The name of this node's searchable document collection
- Required
- Server latitude
- Approximate latitude of your server in decimal degrees
- use these online
services to find the coordinates of your location
- Desired
- Server longitude
- Approximate longitude of your server in decimal degrees
- use these online
services to find the coordinates of your location
- Desired
- Bounding coordinates
- The outer geographic extent of the whole current document
collection (not future expectations).
- N,S,E,W in decimal degrees
- These place name authority
lists will help with defining the Minimum Bounding Rectangle.
- Required
- Top search terms
- These terms occur frequently in the metadata collection. They
will give the user a starting point for conducting searches.
- Current terms, not future expectations.
- Comma-separated list of search terms, which must produce search
results.
- Desired
- References
- URLs at your local site to refer people to more information.
Supply the URL and title for each link.
- Home: required
- About metadata: desired
- Local metadata browse: desired
- Local metadata search: desired
- Other: optional
- Description of the organisation/jurisdiction
- Concisely describe the organisation/jurisdiction that is making
this document collection available. Otherwise a description of the
hosting node.
- This can also contain certain HTML elements
which enable you to link directly to relevant URLs, present words as
bold or italic, etc.
- Maximum of 2000 characters (about 250 words).
- Optional
- Manager name
- The name of the primary technical contact person
- Manager details wil not be published
- Required
- Manager email
- The email address of the primary technical contact person
- Manager details wil not be published
- Required
- Manager phone
- The telephone number of the primary technical contact person
- Manager details wil not be published
- Required
- Manager alert email
- Automatic alerts about problems with your node will be sent here
- Manager details wil not be published
- Comma-separated list of email addresses
- Required
- Contact details
- The organisation that users can contact for further enquiries
about the metadata collection.
- Contact organisation: required
- Postal address: optional
- City: optional
- State: optional
- Postal code: optional
- Email: desired
- Telephone: desired
- Fax: optional