IGeLU 2007 - The good, the bad and the ugly


Published on

A comparison of Voyager and Aleph.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

IGeLU 2007 - The good, the bad and the ugly

  1. 1. Jonkoping University 2006 Library 6732 full time students 24 staff On ALEPH since 2001 676 staff Version 16.2 204825 bibs MetaLib SFX
  2. 2. Voyager 2005.0.1 Aleph 16.02 Oracle Oracle PC clients PC clients - Circulation -Circulation - CAT - CAT - ACQ - ACQ - Sysadmin - Administration - Reporter - ILL MS Access ARC
  3. 3. Client GUI Windows 3.11 client design ALEPH : one window with defined sections Voyager clients use defined sections, but also pop up windows and separate windows. User can define their own workspace within the program window
  4. 4. ALEPH Circulation
  5. 5. Voyager circulation
  6. 6. Voyager allows some personalization in the CAT Client where the user can choose font and colors for work area ALEPH clients can be fully translated Both systems rely on the use of macros by its users to speed up workflows in circ and cat Could get better with more short cut definitions
  7. 7. System administration in Voyager is done through the SYSADMIN client, it is intutive and most settings for the system can be done through it System administration in ALEPH is done either by editing config files on the server or by using the AlephAdm client. The AlephAdm client demands that you understand the nature of the system and what files or tables data are stored in
  8. 8. Voyager files are stored in a sort of logical structure and you can guess where things are happening ALEPH files are spread all over and you need to know where things are happening, I guess it makes sense if you know
  9. 9. ALEPH OPAC is more flexible then Webvoyage You have access to all of the components in use and can change them … and they are plenty
  10. 10. Webvoyage doesn’t give you total access to how the pages are constructed and there are plenty of things that you have to live with
  11. 11. Database structure Both systems allow direct access to data in Oracle and provides documentation for structure Voyager use a descriptive naming convention for tables so you can navigate the Table structure and understand what the different tables hold. Bibliographic and item data are stored in the same database ALEPH use a non descriptive naming convention for tables making it hard to Navigate if you do not know where to look Bibliographic and item data are stored in separate databases / schemas
  12. 12. Table names - examples
  13. 13. Batch jobs in Voyager are initiated on the server and processed with the Reporter module and MS Access Gives you control of output, but you must use Reporter and MS Acess
  14. 14. Batch jobs in ALEPH can be initiated from inside a client by a user with sufficient rights
  15. 15. ALEPH offers nifty serverside tools
  16. 16. ALEPH offers no certification Voyager offers certification 100, 300, 400, 500
  17. 17. User community culture A tradition of communicating problems user to user in the Voyager community. The user group has become a problem solving resource. A lot of people are solving things bythemselfs, sometimes by being very creative. We are in the same boat mentality ALEPH has a very loyal user group with confidence in the vendor and its ability to fix problems. Interesting to see how these two user group cultures will blend
  18. 18. Both ALEPH and Voyager are fine systems, they get the job done Both are patchworks with functionality added along the way ALEPH gives the libraries more or less control of every aspect of the system, more then most libraries are interested in? Voyager provides intutive tools for interaction and maintenance, the drawback is that you don’t have control of the system if you wish to tailor it to your unique needs.
  19. 19. Best of both worlds? Voyager – table naming convention, sysadmin functionality, client gui, intuitive file/data structure ALEPH – OPAC, server util, client functionality (batch job), control of system files
  20. 20. GOOD, BAD, UGLY?