It might make sense to have a posting for miscellaneous links and info for each next-gen product. We can either edit the original post to add material, or add material by appending to the original post via comments.
I'll get the Primo one started with this posting.
The April 2008 issue of Ariadne contains an article on Implementing Ex Libris’s Primo at the University of East Anglia.
Subscribe to:
Post Comments (Atom)
3 comments:
Here is an initial attempt to evaluate Primo.
Good Points
1. Ex Libris product
2. Book covers
3. Faceted navigation results
4. There is a ‘Did you mean?’ which recognizes common misspellings and offers options
5. ‘Get it’ link to provide a link to the live holdings on the live library catalog, to get around the item availability info that is not real-time (since Primo results are based on an availability pipe that runs at intervals throughout the day)
6. Showing books by popularity
7. An alternative search screen for mobile devices
8. Works with Metalib and SFX
9. Integrates with institutional repository
10. Follows FRBR, group-related records under a single record.
11. Claims it is interoperable with other products
Questions
1. Any documentation about migrating from Voyager to Primo?
2. Incentives for staying with Ex Libris?
3. Would it work with the DSpace digital repository? Is OAI publishing an option in DSpace?
4. How much time/staff would be required to normalize XML to PNX (Primo Normalized XML)?
5. Will it work with a CMS (content management system)?
6. “We also expect to see other technologies like AJAX being used, perhaps to cut down on the amount of data that needs to be loaded initially or to provide more real-time availability.” (Is this available now)?
Question 3. Would it work with the DSpace digital repository? Is OAI publishing an option in DSpace?
From DSpace site:
DSpace supports the Open Archives Initiative’s Protocol for Metadata Harvesting (OAI-PMH) v2.0 as a data provider. OAI support was implemented using OCLC’s OAICat open-source software to make DSpace item records available for harvesting. DSpace@MIT is registered as a data provider with the Open Archives Initiative. Other institutions running DSpace may choose to turn on OAI or not, and to register as a data provider or not.
From this report,
I see how this quote applies to Google Scholar over Metalib. "The reasons for preferring search engines like Google include ease and speed of use, relevance-ranked results, few authentication challenges, and what can be described as the overall aesthetic experience." I do not necessarily see this as a problem- There are many problems with Federated search that cannot be overcome by interfaces, given the issues revolve around copyright.
Primo positives:
1. Works with RefWorks
2. More forgiving search "The search functionality is more forgiving than a traditional library catalogue. There is ‘Did you mean?’ option which recognises common misspellings and offers options (e.g. if you type ‘mangment’ it will ask you if you meant ‘management’.) There is also a ‘still haven’t found what you are looking for?’ section which provides users additional guidance on what to do next if their initial search has been unsuccessful.
3. More visually appealing (book covers, etc.)
Questions: Does it generate Stable URLS?
Post a Comment