|
|
||||||||
![]() |
||||||||||||||||||||
Printable BTR |
||||||||||||||||||||
|
||||||||||||||||||||
|
|
||||||||||||||||||||
|
|
||||||||||||||||||||
Main Sections |
||||||||||||||||||||
|
[Biblio Tech Review] |
||||||||||||||||||||
ContentsIntroduction, System components, security, Searching, object support, data entry, The Future, Conclusions, Who should use it. users. |
||||||||||||||||||||
|
from ESP (Esprit Soutron Partnership) designed to provide a packaged
solution enabling users to build their own tailored solutions with a minimum of IT/programming experience. It can be thought of as a Content Management system for structured data sets.
xdirectory is based on server side Java technology with a choice of database back ends. It provides a toolkit for building database driven systems for a variety of information types and comes with the sort of features list expected for any catalogue and search tool. |
||||||||||||||||||||
This Month’s Stories |
||||||||||||||||||||
|
[2001] |
||||||||||||||||||||
|
A competent role-based user security system controls log-ons and presents functions to the user as required. At the top level an administrator can create new record types or complete new directories. Other users will be limited to data entry or just OPAC style searching and viewing. The system administrator builds an application by first defining a set of "categories" - top level divisions that define the main sections of the directory structure. Then types of record are defined - required fields can be selected from a basic list of pre-defined standard Dublin Core fields or user defined fields created as required for the particular type of record being created. Fields may be defined as repeatable, filled from a pick list etc. Their position in the edit screen, search results screen and OPAC full record screen can be changed by simply clicking on up/down arrows - there is no need to get into coding of any kind. The administration of records has been carefully designed with some thoughtful features for directory style information - e.g. you can have time driven display of records so that they only appear when required. Publishing of records can be monitored by the administrator so that authorisation can take place after a record is created by data input staff and before it is released to public gaze. |
||||||||||||||||||||
Printable BTR |
||||||||||||||||||||
|
|
|||
|
Summary result style is configurable and can include any fields from the record - including thumbnails for images. Final detailed display is again configurable by the administrator. Default styles for these levels of output are provided but creative designers can build their own. The data is clearly displayed but currently is limited to the data in the retrieved record. Onward navigation - apart from Web links or file downloads is not yet possible. For example you can find a record for a club or a person and display it but you cannot set the system to present the user with hyperlinks to retrieve all other clubs in that geographic area or in that area of activity as you might expect. Such "associative links" are planned for the next release and will add considerably to the power and navigability of the system. |
|||
|
|
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
[Biblio Tech Review] [Archive Issues] [Technical Briefings] [Supplier Directory] [Exhibitions] [Archive Reviews] [About BTR] |