starts a search function for reuse of data from the database. Eg. authors, corporations, subject terms.Reindex is a 100 % web based library system using XML,XSLT and Z39.50 extensively.
Reindex is a service not software. Hence it is natural to minimize the thresholds of joining and getting out. As for getting out there is simply a button - where you get a XML datadump on your email. To join Reindex we offer free conversion (which in DK has been of a very high quality). Customers have to pay for training, which usually consists a three hour workshop at the time of service startup. Customers pay a yearly fee, (twice a year). Customers have free email support.
No more upgrade fuzz. Reindex uses micro updates released 2-3 times a month. Micro updates are easier to test and survey. Releases are usually tested by a requesting customer and they are documented on : http://forum.reindex.net/viewforum.php?id=2 as well as in the system-logs.
Reindex has just one code. All language and MARC-dialects run in the same software and all customers have the same release. It makes it very easy to support - everybody have the same flaws.
No module thinking. Reindex has functions and they are integrated in a surprisingly fluid manner on the interface. Access to functions are controlled by login-roles.
Data. We run normal backup (2 weeks turnover) and restore is tested once a week. Those activities are documentet and we are are obligated to do this. We run a full backup server which can take over immediately with the most recent backup in case of prim. server failure. Backup server not in the contract.
Access. There is a number of login profiles varying from no login to login with pincode and IP-number control and a login profile that automatically adds users. This can be applied flexibely to system groups.
Reindex has been tested OK with 2.6 millions bibl. records and 5.8 mill. items on very normal hardware. Biggest customer until now : 25 librarians.
Flexibility. Reindex has 5 system groups/login roles (Users are though their Usergroup member of 1 of the 5 system groups) : Admin,LibStaff,Staff,Users,Guests. Admin user can design the interface according to the services they may want to expose for each group. All texts and CSS-properties can be changed locally and they are not overwritten by new releases.
For the main functions (portal, desk, search, targets, marc-templates, thesaurus, letters, editor) you have control panels. Not all of the flexibility is exposed on the interface (dare not) The portal is RSS 2.0 based, most of the information on the portal can be exposed in other CMS-systems and is easily integrated in corporations and organisations.
Pricing. We have chosen a very affordable level and a pricing model that relies on the number of Admin+LibStaf login on the site.
The product is extended by "Prioritized development" and "Extended support". Former is 2 times yearly fee and latter an amount for each emplyoee. Prioritized development means that the customers needs moves on top of the list. Some customers pay to have functionality added.
Reindex supports and are permentantly tested on Microsoft Internet Explorer (5,6,7),Mozilla Firefox 2, Safari 2 and Opera 8+9. It might run on other (and older browsers).
Reindex is an extremely fast system. Try it yourself on the internet. If you have logged in as a guest in the DEMO database, you have access to a large number of records with a correspondingly large number of items.
Reindex uses access keys (shortcuts). Which keys have been used is described in the help page for each function. [F1] gives help, and that's a good place to start.
The help system is acccessed with [F1] or press Help on the topmenu for each page. For somewhat more complex topics there is a number of tutorials addressing those topics. The support link leads to Reindex support page. Currently maintained in danish/norwegian only.
An enduser can select english, norwegian, german, faroese or danish interface. Default language is set by the administrator. At setup MARC-format is seleted for each target. Supported MARC-formats : MARC21, Normarc and MARC21. ZThes (for thesauri) and Dublin Core are also supported by the editor.
One has immediate access to relevant z39 targets and SRW targets. These have been organised in four groups.
Which libraries are to be available is defined on the page with Targets.
The search box uses CCL, but also works well without search codes. If one does NOT use search codes, the system will right-truncate, otherwise there is no automatic truncation (truncation mark=?). More information under help [F1] on the search page.
Start search. and just enter searchwords without searchcodes - you may use and/or/not as operators.
Click on the headers : title or year. Default sort set on Search system, where you have a number of other search options. Hitlist defined at hitlist columns. Reindex can display covers from Amazon.
View new record in the editor.
In the MARC editor (Catalogue) one has full access to all fields in the MARC format. There are two ways of adding new fields
Icon for each field starts a search function for reuse of data from the database. Eg. authors, corporations, subject terms.
Reindex uses templates presenting the most commonly used fields for each document type. The templates may be defined on Templates.
Download can be done EITHER directly by clicking on Download in the editor. Try for example entering the ISBN 82-03-24745-8 (norway), 87-02-03910-9 (DK) or 0-596-52687-3 (US) or 9780596526870 if you read the bookshop (EAN) code with a scanner.
OR one downloads the records in connection with search in external sources - eg. when no ISBN is available. Click download on this title
In both cases one stores the record locally simply by clicking SAVE
You can Filter the record for not so wanted fields
You may automatically download bibliographic records on the basis of ISBN or EAN on Harvest records. It is possible to circulate a book not yet catalogued by entering sumaric data like title and shelf and wait for bibliographic records in other libraries.
Imports and proposals (endusers from the portal) can be viewed and inserted one by one from the catalogue repository.
Reindex can strip metadata and index the document by on all PDF-documents on the net. Just point to a document location and Reindex will index all text of the document and automatically extract metadata about the document. A freetext indexed document and its metadata is searchable like any other metadata documents and has specific searchcodes to search and access the document body.
End users (students, employees...) uses the system via the Portal. The portal can be used as a guest (if you dont close that possiblity). But as individualized services are exposed endusers are encuraged to log in. This may in some cases be combined with Single Signon so that everybody only needs to log in once on the network of the organisation. This userid subsequently follows the user in Reindex. There are a number of login profiles that can be set during initialization - ask for details. One may actually entirely skip transferring or creating users.
The portal displays the library's services. Exactly which services (selfservice loan, circulation, information profiles) the library offers the various usergroups one may set up oneself (see Rights). Select between 7 different portal Skinns.
Reindex portal has CMS qualities. On the portal definition page one may among other things set up
Most of the text elements on the portal are also RSS feeds. Some of them requiring authentication(cookie).
After login, endusers can select alert og news service for periodicals and new monographs/documents. This is done by maintaining of list of published subscriptions and a number of SDI terms.
Reindex has a graphical tree thesaurus system. It supports all sorts of classical thesauri and classification trees.
The thesaurus may search in the library's own collection or in any other (fast) Z39-Target.
A thesaurus is activated by checking Active in Settings.Interface. It is possible to create you own thesauri by adding one term with relations after one another, but thesauri and classification trees are normally imported by Reindex.
Reindex has a complete system for handling of e-journals and normal periodicals.
When receiving subscriptions one can either send serials to normal "old fashioned" circulation (physical circulation) or one notifies the users (those who subscribe to the library's service) that a new issue of XXX-serial, is now available in the canteen (or any other place) for like 14 days.
The administrator/librarian decides which information resources (for example journals or newsletters on the net) the users may subscribe to. The users see for example the following offer and choose themselves which information they want to subscribe to.
One may send out email notification when for instance a serial is received, but the idea is that the user orientates himself via the portal and there sees the recently arrived serials under his own news.
In the same way as subscription to serials the library may offer subscription to terms. For this one will normally create a brief topic list of broad topics that the users can orientate themselves in - see for example this example with law terms.
Here the user may choose which main topics he wants to be informed about. This is not necessarily limited to normal material on paper received in the library, but may as well be links to literature in other libraries or links to resources on the net.
More information about information profiles on Tutorials
The users belong through a usergroup a Sitegroup.
Rights for the SiteGroup are defined on the page for rights. (Use the help text [F1] for this page to see what the individual tags cover).One may in this way define, for example, whether employees/students are allowed to borrow books directly without the use of barcodes, reserve books, to see WHO has borrowed a book etc.
The user's rights are defined by the usergroup's rights.
Linked to a metadata record one may (like one creates items) create an order. Click on Add order.
Thereafter the order page is used to control processes regarding the order. Like for instance sending the order, reminders etc.
Reindex has a number of very flexible budget functions. Primary purpose is to provide a consistent view of the current financial allocations. You can view current allocation for each account, collection or status. Budget functions accounts for user contributions (fines, services), periodical subscriptions and acquisition.
Reindex supports 2 library-models : a centralized (normal) library where the collection is found in one or more rooms and a fragmented library where the collection is scattered within an organization. In the first case you have a normal lending procedure with patroncode and items barcode, in the latter case all PC's in the organisation can lend and return books without using a barcode or a scanner - just by pointing out the relevant item.
As an alternative to lending Reindex supports depots, where a subcollection is registrered as belonging to a location or a person. When a such person gets an other job there is a straigtfarward procedure to reregister the depot.
Reservation and requests (order an item on shelf) is supported. Handling is integrated in the procedures (lend out, return etc.). Library personel may use a control page with
Recall is initated by librarypersonel. Supported formats are letter or email. Request for SMS if needed.
Complete lending history on the items and general as statistics. Lending history may contain patrons names, but this can be turned off at setup time.
All sorts of lending statistics included. If you need another one. Just request it by Reindex.
User account is accessible via Account and Patron database. When the enduser is logged in - from the portal.
To run system functions user must have Admin rights.
Access to Reports and System logs. Some system logs may have actions attached to them.
With a Reindex account a Z30.50 and SRW compliant server is exposing your bibliographic data for the world for searching. This can be disabled and has a login-facility, so you can control access.
Supports iso2709, marcXchange and MARC-lineformat.
All occurrences of subject data, person and corporate names, publishers and series may be changed throughout the database. This function is disabled in the demo databases.
Checks and maintains resolve profiles and Alias' for URI. Alias is used to have a standard path to local documents. In case of server upgrade you can correct paths in one path.
All CSS-based styles and all texts in all languages can be changed by the admin user.
You find settings for many user driven functions on Interface definitions
Core data like Patron groups, Collections, Opening hours, Rules for lending, Terms and Budget plan are described at : Define core data