OPAC Home > DAMS with Metasearch Features

All text is derived directly from the Web source linked & cited unless otherwise stated.

ARTstor. “Metasearch into ARTstor.”

  • The following organizations have implemented the ARTstor XML Gateway through their federated search products:
  • Serials Solutions
  • ExLibris Metalib
  • WebFeat

CONTENTdm. “Frequently Asked Questions: Miscellaneous.” http://www.contentdm.com/products/faq.html#misc

  • How open is the API? Can we develop custom interfaces to the CONTENTdm server?
    CONTENTdm has a well-defined API which allows for custom client development. If your interface is used simpldy for accessing your media collection through basic queries, customization is very straightforward. Development of your own application with updates or additions would involve disclosing the entire API and would require further licensing discussions.
  • OAI Harvesting
    CONTENTdm Servers support OAI harvesting by functioning as OAI repositories for customers who wish to make their metadata available for harvesting. Open Archives Initiative Protocol for Metadata Harvesting Version 2, or OAI-PMH v2, is a recognized standard that allows harvesting of metadata across a network

Gallery Systems

  • Z39.50 Plug-in for TMS
    Specify your data sources, perform interlibrary searches, and pull information directly into the TMS Bibliography module. Based on the Z39.50 protocol, this new utility makes it easy to add MARC import capabilities to your TMS 9.35 system.

IBM. “IBM Content Manager Enterprise Edition Product Documentation.”

  • Based on industry standards and internet protocols, the system is also designed to be fully open to any application.
  • Easy-to-use, highly interactive Web
    client (IBM WEBi) for “light weight”
    access to Content Manager EE and
    z/OS repositories that employs open
    standards and supports Web 2.0
    and Asynchronous JavaTM and XML
    (AJAX) technologies.
  • Robust and open framework
    IBM Content Manager is designed
    to be fully open. With a robust set of
    application programming interfaces
    (APIs), the full spectrum of content
    management function is available to
    application developers and integrators.
    APIs, including Web services, XML
    services, JavaBens and the core “ICM”
    Java and C++ API, handle different
    types of content for unified search,
    retrieval, workflow, access control
    managment and system administration.

iView MediaPro 3

XML (XSLT) Import & Export

  • XML protects your archive by storing it in an industry standard format that can be read by other applications. You can now export a MediaPro catalog and it’s metadata as database-friendly XML format data and optionally change the XML structure using XSLT (eXtensible Stylesheet Language Transformation).
  • Use XML data to create HTML pages, text documents or to import data into other applications. A wedding photographer, for example, could export a wedding catalog as XML and apply an XSL transformation to get the filename, capture date/time and caption formatted a particular way. This data could then be imported into an application like Adobe InDesign, for example, to create a print order form to send to the newlyweds.
  • MediaPro also now supports the import of XML data
  • This provides a complete workflow management solution because you can plug into any other application that supports XML – the best way of getting information out of your catalog and using it for other purposes.

LUNA Imaging. “Insight Support & Documentation.” http://www.lunaimaging.com/support/documentation.html

  • DTDs for the XML Gateway are listed on this page.

Madison Digital Image Database (MDID)

  • Madison Digital Image Database (MDID) Special Interest Group
    Meeting Notes
    , VRA Conference 2007, March 29th, Kansas City, MO
    *With the IMLS grant, will interoperability between MDID and a library OPAC be supported? In other words, if you searched for books, could the results page also return links to digital images in MDID?
    The goal is to have MDID support federated searches, so content that resides in MDID can be found through other systems.
    It is unlikely that we will have the resources to implement the full Z39.50 protocol, we will probably concentrate on the simpler SRW or similar protocols.
  • email update from MDID support, April 2008: “The grant is still ongoing; at this time there is no MDID release available that has related new functionality. I don’t have an estimated release date either.”


Re:discovery Z39.50:

  • Searching and Retrieving Information
    Re:discovery Z39.50 is a product for searching and retrieving information from a Visual Re:discovery database. The Z39.50 protocol is well established in the Library community as a client/server-based protocol for searching and retrieving information from remote databases. Z39.50 combined with Web technology offer the means for searching across multiple databases from different institutions simultaneously. Various Archives and Museum collection managers want to make data available on the World Wide Web through this same technology.
  • Supplier
    Visual Re:discovery is integrated with the Z39.50 server software supplied by Crossnet Systems Limited, England. Crossnet Systems Limited is an international leading provider of Z39.50 software products.
  • Standards
    “Z39.50” refers to the International Standard, ISO 23950: “Information Retrieval (Z39.50): Application Service Definition and Protocol Specification”, and to ANSI/NISO Z39.50. The Library of Congress is the Maintenance Agency and Registration Authority for both standards, which are technically identical (though with minor editorial differences)

OPAC Home| What is a Next-Gen OPAC? | So What? An Art and Visual Resources Library Perspective | Interviews | Conference Presentation | Next Generation OPAC Examples | DAMS & Metasearching | Bibliography

What’s Hot & What’s Not: Trends in Technologies and Services in Libraries