Open Forum

 View Only

 Managing Digital Assets & Rights in Argus (or Other CMS Platforms)

Emilia Morales's profile image
Emilia Morales posted 07-15-2026 12:51 PM

Hello everyone,

My Institution, The Tennessee State Museum, is currently evaluating how to better organize and manage our digital image assets and rights documentation. We use Argus as our collections management system and are exploring whether it could also serve as a centralized repository for digital assets beyond accessioned objects.

Our goal is to create a searchable system that includes not only images of collection objects but also the many images we acquire and use for exhibitions, publications, marketing, educational materials, and research.

We're currently asking ourselves questions such as:

  • Do you use your collections management system (Argus or another CMS) to manage digital image assets in addition to collection records?
  • If you use Argus, have you created a separate module or record type for images or digital assets?
  • How do you manage images that are not part of your permanent collection (e.g., licensed images from archives, exhibition graphics, historical reference photographs, maps, marketing images, audiovisual materials, etc.)?
  • Do these assets receive their own records, or are they organized elsewhere?
  • How do you document copyright status, permissions, credit lines, and licensing agreements?
  • Are permissions attached directly to image records, or are they managed in a separate database or file system?
  • What metadata fields have you found most useful for making images searchable and reusable?
  • How do you prevent duplicate image records while still tracking where an image has been used (exhibitions, publications, marketing, websites, etc.)?

Our current thinking is to use Argus as the searchable database while storing the digital files themselves in our institutional storage system, with Argus serving as the primary point of access to the images and their associated rights information.

I'd be very interested in hearing how other museums—particularly those using Argus, but also those using other collections management systems—have approached digital asset management. What has worked well for your institution, and are there any lessons learned or pitfalls you would recommend avoiding?

Thank you in advance for sharing your experiences!

Elysian Koglmeier's profile image
Elysian Koglmeier

This is a really interesting question, and it's something we've seen many collecting organizations think through as their digital assets continue to grow beyond the permanent collection.

While our clients use Artwork Archive rather than Argus, one approach we've seen work well is using the collections management system as a searchable hub for digital assets and rights documentation. Organizations attach digital assets not only to object records, but also to contacts (artists, donors, photographers, lenders), exhibitions, locations, maintenance records, and other related records so everything stays connected.

For assets that aren't tied to a specific accessioned object, our organization clients use a dedicated document repository within their collections management platform. In Artwork Archive, clients use My Docs to store and organize digital assets that don't naturally belong on an object, contact, exhibition, or other record, while assets that do relate to those records can be attached directly to them. This provides a searchable home for all digital assets while preserving the relationships between files, people, and projects.

One lesson we've heard repeatedly is that establishing consistent metadata, naming conventions, and documentation practices upfront is just as important as deciding where the files live. The more consistently information about ownership, permissions, usage, and related projects is recorded, the easier digital assets are to find, manage, and reuse over time.

I'd be interested to hear how other Argus users have approached this as well.

Best of luck!

Elysian

Head of Partnerships

Artwork Archive