How to Identify Specifications for a New CMS

October 30, 2019

Last week we reviewed how to form an effective procurement team tasked with choosing the next museum collections management system (CMS). Now that your procurement team is in place it’s time to observe what stakeholder requirements exist for the new CMS and formulate a set of specifications.

These specifications will be used to help identify potential CMS options and evaluate them against museum stakeholder needs.

How to Identify CMS Specifications

CMS specifications will depend upon the museum, collection, staff, and future vision. The procurement team needs to review every current and anticipated CMS use in order to tease out what tools are required for staff to do their jobs effectively. Asking questions is a great way to explore what CMS specifications should be included. For the following example questions, the word “tool” represents any CMS feature or function that staff would use as a tool to do their job.

Questions each staff person should consider are:

  • What tools do I currently use that are required to do my job?
  • What tools do I not have currently that would make my job easier?
  • What tools do I consider as mandatory versus recommended?
  • What tools are so important that it’s a deal breaker if the CMS doesn’t offer that tool?

Next are questions that may be applicable to how the museum operates and how it intends to use the CMS.

Example questions:

  • Does the digital file backup meet preservation standards?
  • Are there digital file size storage requirements?
  • What administrative control levels are available?
  • What customization is needed (on both the front and back-end) and can the CMS accommodate those needs?
  • What reports or other automation tools are desirable to support museum staff?

In addition to staff tool requirements which are all internal, it’s equally important to review what tools may be required for external use.

Questions staff and external stakeholders should consider together:

  • Is streaming video a requirement?
  • Is the CMS ADA-compliant?
  • Can the CMS navigation and object information be translated to another language on the fly?
  • Can the CMS gather user contributions to object records?
  • Can the CMS external search include objects from a different CMS at a peer museum?
  • Is there a zoom feature or watermark feature for images?
  • Can users create and save their object searches?
  • Are users able to download object images and data or share them via social media?

How to Put it All Together to Create CMS Specifications

Once the procurement team has had a chance to identify all possible CMS requirements, it’s time to put them all together and determine what tools are required and which are OK to do without. This part of the process can be the most difficult as staff often have conflicting opinions on what is a required tool. To assist, staff should indicate to what degree they believe the tool is required. Once the tools have been identified and ranked, the procurement team can construct a specifications sheet to present to CMS companies and to evaluate how each CMS ranks.

Example of Museum CMS Specifications

Example of Museum CMS Specifications

What’s Next?

At this point a procurement team is in place and museum CMS specifications have been identified, ranked, and placed in a rubric. Next, use this rubric to evaluate collections management systems and select the highest-ranking CMS options for further testing and vetting. Testing, vetting and the purchase process will be covered in a future post.

<a href="https://lucidea.com/author/rachael_woody/" target="_self">Rachael Cristine Woody</a>

Rachael Cristine Woody

Consultant, author, and blogger Rachael Cristine Woody advises on museum strategies, collections management and grant writing for a wide variety of clients. Learn about Lucidea’s Argus solution for museum collections management and digitization and read more of Rachael’s blog posts here.  

Similar Posts

Leave a Comment

Comments are reviewed and must adhere to our comments policy.

0 Comments

Submit a Comment or not

Pin It on Pinterest

Share This
https://lucidea.com/blog/how-to-identify-specifications-for-a-new-cms/
lucidea.com
crawl=CC-MAIN-2019-47
188141
application/http; msgtype=response
sha1:H2MEFWK5FD4IT4PTREGEZCVSN2R7W6FS
<urn:uuid:3adcec69-df3d-4e0e-b3dd-0c87a58dd30b>
2019-11-19T12:37:59Z
35.203.43.206
text/html
sha1:HNT7QIFVQNDJ6E2GMVVHAZMJY5VR2NIF
<urn:uuid:fdcf6124-a619-4126-a79c-28af70d0432e>
https://lucidea.com/blog/how-to-identify-specifications-for-a-new-cms/
response
<urn:uuid:b971799e-8585-486d-9bd5-b1d5bf03e652>
isPartOf: CC-MAIN-2019-47
publisher: Common Crawl
description: Wide crawl of the web for November 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-161.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/