|
The Aurora components were developed first as stand-alone products – e.g. the Z39.50 client Aurora
Explorer. Building on this, and other key software components like the Aurora cataloguer, they now have a full integrated library system.
Aurora is a client server system utilising a fairly thin client - and component style development - as you
would expect from its history. It is based exclusively on MS technology -the client talks to the server via ODBC which allows the server technology to be a choice of either Access for the smaller clients or SQL
Server for the larger systems. The server OS is Windows NT and its web server.
Aurora has adopted a consistent approach to screen design with restrained use of colour. Icons are not
over big and functions like editing and searching are similar throughout the system. Although there is not a true Multiple Document Interface MDI) which allows several sessions against the database at one time,
cataloguing does allow multiple record editing within one window. Navigation through the system via hyperlinks is fairly well implemented and is extended into a useful Thesaurus display of subject headings.
The basic quality of any library system can be determined by how the bibliographic database is
organised – its capabilities in this area limit much of what can be done in the way of functionality – searching, authority control, serials, acquisitions etc. Aurora uses a relational database – SQL server or
Access to maintain format independent bibliographic files. The bibliograhic files are fully MARC capable and, indeed can store any MARC format or MARC like format records e.g. MAB. The format is held at
the record level and so formats can be mixed and maintained for export and cataloguing if desired. Although a single format must be declared for editing.
Windows - Aurora Explorer
The Windows based OPAC is a "multi-pane" client with clear areas for defining basic search parameters
to define what is being searched, an intuitive location filter and a summary results screen.
Navigation is via clicking on headings and follows a logical course through to the choice of full display -
ISBD, labelled or MARC diagnostic. There are some nice advanced features like folders for personal storage of records and user driven messaging for requesting.
Both browsing of headings and keyword searching, via the Fulcrum text engine for the bigger systems, is
available. Heading browsing includes transparent see and see also references enabling the user to move easily from unused headings.
Summary results use icons to indicate types of materials - a big help within multi-media catalogues.
Hyperlinks from the main display aid onward searching. Holdings information is shown on the same screen as the main display. and conforms to NISO guidelines for serials.
Altogether this is a useful workhorse for the professional searcher. The one thing missing for the time
being is the integration of the Z39.50 search features that are available to the cataloguers. This strong feature is being reworked to make it sit more sensibly in an OPAC environment.
Web OPAC
The Web OPAC uses the same indexes and access points for browsing and keyword searching. The
core functionality of the OPAC can be embedded in an Intranet house style as desired.
Based, as it is, on a very flexible database structure, the Aurora cataloguer module has some very nice
"big system" features. You can set the display to show MARC tags or labels and tags are validated as they are entered. MARC tags and subfields are prompted and are context sensitive – e.g. a
non-repeatable tag or subfield is not presented if it already exists in a record. Local tags and rules can
be defined. Templates with default data can be set up and used to make repetitive tasks easier and quicker. A single MARC format must be defined for use in editing (although any format can be entered,
stored and exported) since there must be a single set of validation rules.
There are many nice thoughtful features that will make the cataloguer's life much easier - not only in the
creation of new records in house but also via the integrated Z39.50 client Aurora Locator with which you can select, download and add to your catalogue any record found on the Internet. This is no ordinary
Z39.50 client either, it is a fully featured resource discovery tool with many features for grouping and defining Z-targets e.g. by subject and country, to make full and easy use of global resources. Result sets
can be interfiled and de-duplicated. This tool is also available in Acquisitions.
Batch record importing and export - with original formats being maintained - often overlooked in modern
systems, is well implemented allowing the cataloguer to specify treatment of duplicates as individuals or as a batch file of rejects.
As you would expect the authority control conforms to the major standards. During the cataloguing
function, you can browse, select and create new authorities and do global updates and merge headings.
A very nice feature of Aurora is the ability to display subject headings in true Thesaurus style as
demanded in many special libraries. Terms are displayed in a tree structure showing the various relations between terms e.g. related term, wider term, narrower term etc. and can be navigated to via hyperlinks.
The circulation user interface has an uncluttered look and acts as a competent control panel with
hyperlinks to the main information required. I would like to see a little a little more data displayed about
the user once the card is read - without having to navigate to it but - as with all circulation clients the true
measure of the interface is how it performs in a real library - plus the speed of operation. And on this latter pint there is a response time log so the systems librarian can monitor performance closely if required.
Control within circulation has a good basis - the main parameters of loan period ad loan limit are built on
a three dimensional matrix of User/copy/location. And a nice touch is the ability to set a due date via
picking from a pop-up calendar. Both "seen" and "unseen" renewals are controlled.
There are some other nice touches throughout the circulation function - for instance the display showing
items on loan highlights the overdue items and shows how overdue they are with estimated fines.
Like many systems, early customers have influenced some aspects of the design. In Aurora's case, the
Royal Blind Society of New South Wales has meant the development of a useful feature for controlling loan suggestions by profile and previous titles read. This can be useful in many other environments like
academic research where a log of what has been read can be useful.
Reserve book Room
The short loan / reserve book room function is not yet complete with just a simple hourly loan control
capability and as yet no booking facility. There is a Media scheduling module in development.
Is an interesting module - the user interface is slightly different - it sports a "road map"
- a set of broad functional sub-functions. This has echoes of the new Geac Acquisitions client which uses
the concept in an MS “Outlook” style sidebar whereas Aurora's are placed central screen. Remaining to be developed is EDI which will be built to EDIFACT standards.
Serials is always interesting to observe in a new system since it taxes the best of developers.
Aurora have done a good job here - to start with, it complies with the Z39.71 bibliographic and serials holdings standard for enumeration and chronology. Defining obscure publication
patterns and, in particular ones that use more than the normal 2 levels (vol. issue), is easy. Several nice features for setting up of the publication pattern including previewing (getting it
right before you order a title is never easy), ability to change the calendar start point where volume and issue change mid year and other subtle aspects of serials control are well catered
for. You can link to also link to Table of Contents services from the OPAC record.
A modern library system must be able to handle objects i.e. link to and retrieve for display on the desktop
the full gamut of likely electronic resources that might be held in a modern library. Aurora uses embedded viewing capabilities within MS Windows 98 for viewing most file formats but can also use
external viewers (helper applications) where required. Multiple objects are handled e.g. several images can be attached to one catalogue record – and desktop functions such as zoom and rotate are possible.
Where Aurora will need to add to its functionality in this area is in the management of file location and integration of scanning functions as provided by the more specialist products such as Endeavor and Sirsi.
The potential market for Aurora is bigger than for most new entrants since it has all the capabilities of
addressing both the smaller and larger system markets. The difficulty with such a product is presentation to the market place since once a product becomes known in one niche, it can be difficult to break into the
other sectors. However, there is evidence that the somewhat artificial barriers are starting to crack. Some of the traditionally Academic players in the UK for example are now eyeing up the public library
market. Esprit - the distributors in the UK - are planning to go for the Academic and Special/Corporate markets to begin with and have scored an early success with the winning of Bournemouth University.
Aurora has a solid, fundamental design and incorporates many big system features together with some
nice touches that are sought in the special and even public library market places. This first view was impressive and the product looks in good shape from the design and demonstration viewpoint. The
experience of the early adopters, Bournemouth University in the UK for example, will be watched with interest. |
