Found total 104 new or updated records for this month at 20 nodes.
All ASDD nodes are automatically interrogated once every day to
generate the listing.
Warning: This application is a robot that contacts each node in turn
and conducts the search. You may see problems with some of the remote search
services, due to server configuration and data management issues. That is the
responsibility of each distributed search node. All that we can do is to
attempt to detect and explain these inter-operability issues.
- No response from node
- - Their Z39.50 search service could not be contacted (e.g. machine is
off-line, server is not running, very busy server, network congestion)
see Status of ASDD Nodes.
- Unsupported Use Attribute: 1012
- - Their Z39.50 search service is not configured to respond to
searches using the "Metadata Date" attribute (metd=1012).
- Cannot conduct search
- - Their Z39.50 search service failed to carry out the search.
- - The most probable causes are that they are using server software that
is way out-of-date, or their server is poorly configured.
- Cannot present titles
- - Their Z39.50 search service failed to present the list of results.
- - The most probable causes are that they are using server software that
is way out-of-date, or their server is poorly configured.
- Cannot connect
- - Our robot cannot connect to their server (there seems to be some
drastic inter-operability problem).
- Results are consistently zero hits, yet i know that there are
modified records
- - Server configuration and data management issues - many possibilities.
- - e.g. their metadata records are not properly updated, see the
"Metadata Date" field.
- - e.g. their metadata records have not been properly validated to ensure
reliable structure and content.
- - e.g. their search server is poorly configured, and only partially
responds to the date search.
- There are some dataset descriptions that i know are new, but they
are not being listed
- - Perhaps their metadata author has not properly updated the
"Metadata Date" field.
- Other notes
- - Early in the month, the record counts could be zero of course
(look at the date generated below).
- - Sorry, the distinction between Updated and New cannot be determined, as
the ANZLIC metadata would need a "Metadata Revision Date" field
and a "Metadata Publication Date" field,
rather than a solitary "Metadata Date" field.
- - The history summaries prior to 2002-03 will have slightly skewed results,
because they started being recorded on that date and were generated for
the past (e.g. a document that was updated in 2001-09 and again in 2001-11
will only get recorded for the latter).
- - One month is the best reporting period. The data custodians may update
their document repositories in batches, so a daily search would easily
omit recent records.
- - Maximum 100 record titles are listed from each node.
- News
- - news and notes about the Z-alert ASDD service
- Who to contact about suspected problems
- - the results of all searches depend on proper configuration of the
remote search server by the data custodian
- - See ASDD node descriptions
for their contact details
Perhaps you want to build your own network service based upon
automated use of the structured log and summary files that are
generated by this service - please contact
IndexGeo Pty Ltd.
- www.indexgeo.net/zalert/
- generated on 2003-05-31