Collection management systems manage information about the original but can include a digital

derivative. Examples include Past Perfect, CollectiveACCESS, eMU, and ArchiveSpace. Analog
objects are the primary focus of these systems.

Digital asset management software focuses on access to digital representation in the material.
Unlike CMS, the system could contain administrative images such as gallery shots from a
museum. Examples include CONTENTdm, Omeka, and Islandora.

Many systems of digital library software have been developed by veteran vendors like
Innovative Interfaces, Sirsi, etc that have traditionally built systems for cataloging collections.
There is often an add-on module on the backend. Individual digital objects are searched along
with traditional library materials.

Preservation systems often include an assortment of protocols and software applications. Focus
is on long-term monitoring for data loss over time.

Open source means software plus source code. Users participate in the development and
refinement of the software.

Some additional considerations are the initial setup, figuring out bugs and fixing them, running
the server, upgrading it, patching it, and securing it, upgrading software, design changes, and
modifying the system.

When choosing an asset management system, spend some time developing your requirements.
The end user requirements are the researcher’s needs for high resolution. The staff
requirements are needs of catalogers, preservation experts, and digitizers, and ease of use.

For functional requirements, an inventory is important. You likely won’t get everything so what is
essential and what could you live without for now?

Finally, understand that you’re choosing a system for now and that in a few years, you’ll likely be
moving/upgrading to a different system/product. Be sure that you have a clear understanding of
the migration features of the software.