10/31/2005SFX/Verde Minutes 10/31 Present: E. Duranceau, T. Gabridge, M. Gaskell, N. Hennig, R. Lubas, B. Siers 1) Recap from last meeting & Verde training - Verde is still lacking functionality at this stage. We have 4 queries out to Ex Libris to see if they will be resolved by the spring release. Whether or not these queries are resolved will determine if the group recommends implementing Verde this spring or recommends waiting. 2) Technology & Third Party Interface Subgroup report Nicole reported on what she has learned about the Xserver since the group last met. It is loosely based on web services. This should help in taking data out of proprietary databases using XML to transfer. Metalib has an Xserver. Nicole is trying to nail down more detail of how the Xserver for Primo will work. Beth reported on some commercial products. AquaBrowser looks like it builds separate indexes. It claims to handle non-library data. The company recommends running it on a separate server from your ILS. WebFeat - this is primarily a search engine. It claims to display in the native interface of the information. There is no evidence of faceted browsing in this product. Nicole demonstrated Xerxes, which works on top of Metalib from UC San Marcos using the Xserver. It has broad subject groupings of databases. Xerxes doesn't yet contain e-journals. It is not live yet; the plans are to go live this spring. 3) Presenting to DLG/TSAC Discussion: Primo isn't doing database discovery. Maybe we could develop a database discovery tool based on metalib/Xserver, then implement Primo. Is there a case for metalib? It could offer… Database Access & Discovery - store metadata in Verde (subject categories) and write code to pull out using SOAP Metasearch/crosssearch/federated search functionality User personalization Of these reasons, the metasearch function is the key. We want this for our users and the Xserver gives us a boost in creating it. Another way to weigh it… Verde alone Metalib w/ Xserver --Flexibility --Structure
Could target preselected lists for coverage eg. Rochester (demo this for DLG/TSAC)
" Share new information " DROP Option 2 " Propose these steps: " Step 1 User needs assessment (During this time also learn more about Primo and other products) " Step 2 or 3 Database Discovery Tool development " Step 3 or 2 Develop a custom integrated UI or purchase a produce such as Primo, AquaBrowser Currently we are thinking the hypothetical case would be to develop the Database Discovery Tool first, giving time for commercial options to present themselves as more developed |
|
|