Erl10 web scale-gb-sg
•Télécharger en tant que PPT, PDF•
1 j'aime•6,661 vues
A description and comparison of various web scale discovery products and the implementation of Summon at the WMU University Libraries.
![[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](https://image.slidesharecdn.com/erl10-webscale-gbsg-100507090411-phpapp02/85/Erl10-web-scale-gb-sg-1-320.jpg)
![The Challenge – How Best to Serve the Users… ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
Similaire à Erl10 web scale-gb-sg
Similaire à Erl10 web scale-gb-sg (20)
Dernier
Dernier (20)
Erl10 web scale-gb-sg
- 19. Integrating Summon into our web site
Notes de l'éditeur
- VAC: create nebulous paths for existing products: Voyager, Aleph support will continue, but how much longer will it really be in EL’s interest to continue developing them, given URM? Some niche modules like Media Scheduling have already fallen by the wayside. How much longer will it make sense for us to stick with the current ILS? If libraries offer alternatives to the front-end, they’ll learn lessons about the backend too. The vendors know that in these budget times, we need better back-office efficiency. CLIR’s No Brief Candle report and plenty of other sources say we need to change. sometimes reduce choice as products are merged 360Search + WebFeat = ?? new products evolve rapidly See Primo -> services -> Central insert new consortia/vendors into existing markets Not just for “library automation” vendors anymore – using corporate relationships to leverage content (SerSol and ProQuest) OCLC’s WorldCat Local, now it’s adding articles and Web-scale acq, cat and circ functions One company sticks its neck out and does something innovative, and other companies and industry players then race to catch up to that: SerialsSolutions launched Summon, and now EBSCO, Ex Libris, and OCLC are all chasing after them into that market segment. Open source: Evergreen’s acq/serials not very mature yet, and many academics are hanging back to watch UPEI and Conifer for a while. We have the Michigan Evergreen consortium of public libraries, and the academics have had one conversation so far about it, but that’s all to date. Products years away: OLE’s still to work out funding to have something non-partners can use by mid-2013 (not to mention the tectonic shift that’s going to need to happen for enterprise IT to allow the library to leverage systems like Banner, PeopleSoft, and Blackboard rather than continuing to have a “patron database” in the ILS). Ex Libris just announced URM development partners, so who knows when there’ll be a mature URM that the larger customer base can implement? Flux, uncertainty and disruption force very careful choices in tight budget times – now’s not the time to be changing ILSs or implementing fed search tools, IMHO
- Nina McHale spoke about this at length yesterday. You can create some metasilos If one silo fails, you may get incomplete results PsycINFO may be fast, but what about other silos that are slower? WebFeat: you can’t do a three-term search with Booleans if all X databases haven’t implemented such functionality the same way It’s a starting point.
- Early Primo was an overlay that still showed you Voyager records, still ran a db search federated Later Primo started harvesting and using Web services so you didn’t have to see Voy anymore, but Vanderbilt still uses fed search – watch the timebar Now PrimoCentral is a big index that’s Web-scale/cloud based. Growing number of publishers joining. That’s three evolutions libraries and users have had to grok over 2-3 years. The best new systems use tools like Lucene/Solr: Ex Libris, VuFind, etc. Why bother cataloging things in such detail if we can’t use the fields? We need to choose how we index things (though public services and tech services may not agree – the more fields we include, the broader the search), though we need to think carefully about how much time to spend on things that go further and further down the long tail.
- Early Primo was an overlay that still showed you Voyager records, still ran a db search federated Later Primo started harvesting and using Web services so you didn’t have to see Voy anymore, but Vanderbilt still uses fed search – watch the timebar Now PrimoCentral is a big index that’s Web-scale/cloud based. Growing number of publishers joining. That’s three evolutions libraries and users have had to grok over 2-3 years. The best new systems use tools like Lucene/Solr: Ex Libris, VuFind, etc. Why bother cataloging things in such detail if we can’t use the fields? We need to choose how we index things (though public services and tech services may not agree – the more fields we include, the broader the search), though we need to think carefully about how much time to spend on things that go further and further down the long tail.