Voyager library management system
The Library uses the Voyager library management system supplied by Ex Libris.
The Voyager Z39.50 server conforms to Z39.50-1995 (version 3) of the standard. A subset of attributes from the bib-1 attribute set are supported, and codes from the bib-1 diagnostic set are utilised.
Connection details & hours of availability
The database is available 24 hours a day, except for about 10 minutes daily at 2am for routine maintenance.
- Database: main collection
- Domain name: catalogue.slv.vic.gov.au
- Port: 7090
- Database name: Voyager
Z39.50-1995 (version 3) of the standard is supported. A subset of attributes from the bib-1 attribute set are supported, and codes from the bib-1 diagnostic set are utilised.
Z39.50 services supported
The Voyager server supports the following services:
The scan bit is on the Voyager init response, but scan is not supported.
The initialisation service is protocol version Z39.50-1995 (version 3). Options supported are search and present.
Preferred message size
The maximum message size is 16,000 bytes. If the requested size is larger than this, Voyager will negotiate the client down to 16,000 bytes. The client proposal will be accepted if it is less than 16,000 bytes.
A user ID and password are not required.
Only 'default' is a supported result set name. Use 'voyager' as the database name. Both names are case sensitive.
'B' (brief) and 'F' (full) are supported element set names.
Only type-1 is a supported query and only bib-1 is a supported attribute set ID.
The result set ID ('default') cannot be used in the operand. Qualifying searches are not supported.
Supported operators are:
Record syntaxes are MARC 21 and OPAC.
Email firstname.lastname@example.org for more information about:
- relation attributes supported
- structure attributes supported
- completeness attributes supported
- required and default attributes
- other attributes
Search term processing in Voyager system
Keyword search terms (name, title, subject, note) can appear anywhere in the field.
If multiple words appear in the same search term, the search term will be processed as a phrase.
If the words appear in separate operands (ANDed together), they can appear in different fields in the same record.
A keyword search term can be the first, middle or last name. If more than one name appears in the search term of a keyword search, the last name should precede the first name.
Keyword indexing does not include phrases that cross subfield boundaries. If the search term contains a phrase that may cross subfield boundaries (subject heading, LC call number, etc.), use a left-anchored (right-truncated) search. In other words, Position attribute = 'first-in-field'; Truncation attribute = 'right truncation'.
Phrase search terms (name, title, subject, note) can appear anywhere in the field.
Phrase searches that include the first-in-field position attribute should begin with the first significant word in the field.
The last name should appear first (with or without a comma) in order to match against entry fields in Voyager indexes.
Use a hyphen in all ISSN search terms (eg 1234-5678).
Do not include hyphens in ISBN or LCCN search terms.
LCCN search terms should be in normalised format (ie include any prefix, spaces or zero file). For example, LCCN 91-13 should be '91000013' in the search term.
Searches are not supported against previous result sets.
The questions mark is supported as a truncation character.
Records in keyword search result sets are in order by the Voyager control number (MARC field 001).
Records in left-anchored search result sets are sorted by the field being searched (eg title, subject, call number etc).
Search term length limitations
Search terms, after mapping from intersite syntax to the internal Voyager search system, must not exceed 255 characters.
Limitations of Voyager server
There is a limit of 10,000 records that can be retrieved in a result set.
It is not possible to search the authority files.
When the Voyager server result set is a medium or small set (based on the size of result set in relation to large-set, small-set and medium-set number parameters in the Search Request), the following encoding problems can result:
- When records are expected in the search response (eg a medium set or a small set), the presentStatus is a '0' (success) instead of a '5' (failure).
- When a non-surrogate diagnostic record is returned instead of result set records in the search response, the value of numberOfRecordsReturned is a '0' instead of a '1'.
- The non-surrogate diagnostic record never contains an addInfo, which is mandatory in the standard. If these problems are making interworking with the Voyager server difficult, it is suggested that the client small-set and medium-set number be set to '0' and the large-set to '1' (making every set a large set) until these server problems have been corrected.
Our catalogue includes records downloaded from Libraries Australia, a service for Australian libraries and their users that provides access to the national database of material held in Australian libraries.
Principles and guidelines on the use and transfer of records from Libraries Australia are available on its website.
Records may only be downloaded for private individual research purposes. Organisations requiring separate arrangements should contact Libraries Australia online or by calling 1800 026 155 (toll-free within Australia).
For more information, email email@example.com.