Old Notes (Fall 2010)

  • Possible questions to explore for each product:
    • What can they do? What can't they do?
    • How do they work?
    • Differences between products / comparisons with other products.
    • What libraries are using it? Are any nearby libraries using it?
    • Cost and staff time - during initial setup and to support it once it's running. Who does this work? How much of their time does it take?
    • Do the products interface with other software? Link resolvers, other discovery layers?

MetaLib Features
  • Simple keyword search and advanced boolean search
  • Simple and advanced workflows
  • Merging
  • De-duping
  • Can group results by subject
  • Can group results by facets - author, date, journal, or other attributes
  • Uses Z39.50, HTTP, XML gateways, and proprietary APIs.
  • MetaLib can use OAI-PMH to harvest OAI-compliant repositories so that these repositories can also be searched by MetaLib.(Digitool?)
  • For some resources, Metalib uses native display to show search results and full records.
  • Interface is HTML based and "many elements" are customizable
  • Users can save queries, make lists of frequently used resources, make "e-shelf" of links to records, and create alerts that run searches automatically and notify them periodically of new results.
  • Interfaces with Primo discovery layer.
  • MetaLib X-Server (included?) - allows integration of metalib resources with library webpages (sounds like MyLibrary), create course guides, embed search boxes in web pages, etc.
  • Area libraries using
    • New York University
    • MIT (under the name Vera Multi-Search)
    • Boston College
    • Columbia University
    • McGill University
    • Harvard University
    • Syracuse University
    • University of Rochester (Emails from Judi Briden at Rochester and screenshots of their custom interface here.)