CSStewardship
Choosing minimum record fields for a collection
How a small museum team can agree on the smallest set of fields every object record must contain, and keep it usable.
Entry checked on
Why agree on a minimum set of fields at all?
Because a record with no agreed floor drifts. One cataloguer writes a title and nothing else, another captures a full provenance chain, and the database becomes a pile of uneven entries that no one can search or trust. A minimum field set is the floor every object record must clear, no matter who creates it, what the object is, or how quickly the work is done. The U.S. National Park Service treats documentation as a core museum function, publishing guidance on managing, preserving, protecting, documenting, and accessing collections through its Museum Handbook (https://www.nps.gov/museum/publications/mhi/mhibe.pdf). A floor does not replace fuller records. It defines what "recorded" means for your institution.
What is the difference between a minimum field and a full catalogue record?
A minimum field is the mandatory core that makes an object findable, identifiable, and accountable. A full catalogue record adds research, condition history, exhibition history, and conservation detail. The minimum is what you would need if a colleague had to locate the object tomorrow with no help from you. Everything beyond it is enrichment. Small museums often blur the two and then abandon cataloguing because the full standard looks unreachable. Separating them makes steady progress possible.
Which fields belong in the smallest defensible core?
A workable core usually includes an object or accession number, an object name, a title or brief description, the number of items or parts, a current location, the acquisition method and date, and the source or donor. Add a short physical description: materials, dimensions where known, and any maker or associated place or date you can support. Add the date the record was created and the person who made it. Finally, add a rights or status note if you know it, even if it only says "not yet researched." That last field prevents a blank from being read as permission.
Use published documentation guidance as a naming reference rather than as a reason to delay. Aligning field names with wider practice keeps your data portable, but you can match vocabulary later. You cannot recover an object that was never given a number.
How should the team decide together rather than by decree?
Run one working session with everyone who touches records: registrar, curator, preparator, volunteer coordinator, and whoever answers research requests. Lay out sample records from your own collection, warts included, and ask which fields people actually used in the past year. Then ask what they wished existed when a question arrived and the answer was missing.
Test each proposed field against three questions. Does it help someone find the object? Does it help someone identify the object? Does it help someone account for the object? A field that fails all three can wait. At the end, read the list aloud and ask whether a new volunteer could complete it for a simple donation in fifteen minutes. If not, the list is too long for a minimum.
Which fields cause the most argument, and how do you settle them?
Title and description cause the most friction, because people disagree about whose words matter. Decide that a working title may be plain and revisable, and that it never overrides an inscribed or documented title. Dimensions create debate because measuring conventions vary. Agree on units and on whether you measure the object or its housing, and record which you did. Date fields stall when the object is undated. Permit a range, a circa, or an explicit "unknown." An honest unknown is more useful than a confident guess.
Rights and legal status deserve special care. A minimum record can note that rights are unresearched, but it should not state conclusions the museum has not verified. For anything involving ownership, cultural sensitivity, or restrictions on use, consult your current official guidance and qualified colleagues rather than relying on a field value alone.
Decision checklist for adopting a core field set
Use this as a working agenda, not a form to file.
| Step | Question to answer | Evidence of readiness |
|---|---|---|
| 1 | Who must be able to find any object without help? | Named roles, not job titles |
| 2 | Which fields answer find, identify, account? | Short list agreed aloud |
| 3 | What will we name each field? | Labels matched to one external standard |
| 4 | What do we accept as unknown? | Agreed wording such as unknown or circa |
| 5 | Who checks incomplete records? | One person and one review moment |
| 6 | When do we revisit the list? | A fixed date within a year |
How do you keep the minimum from becoming the maximum?
Write the core list on one page and post it where records are created. Any field beyond the core is optional, and optional fields should never block saving a record. Review the list once a year against real questions people asked. If a field stayed empty for twelve months, either train for it or remove it. A minimum that nobody fills is not a minimum; it is a wish.
What do you do when an old record fails the minimum?
Do not halt new work to fix the backlog. Flag incomplete records, fill the cheapest missing fields first, and schedule the rest. Prioritise objects that are requested, loaned, exhibited, or at risk. An inventory sweep is the natural moment to close gaps, and it helps to be clear about how inventory and catalogue records differ before you start (link: /collection-stewardship/inventory-vs-catalogue-records/). When you later write about an object's physical state, keep the wording reusable by others (link: /collection-stewardship/condition-reporting-language/). And if a new system is coming, clean the core fields before migration, not during it (link: /collection-stewardship/digital-catalogue-migration/).
How do you document the decision so it survives staff change?
Record the agreed core fields, the definitions, the accepted ways to write unknown, and the review date in a short internal standard. Name the person who owns it. When a new colleague arrives, the document answers most questions before they are asked. A stable core also makes reporting, loans, and exhibition planning calmer, because the museum can trust its own answers.
Conclusion
A minimum field set is a small act of collective discipline. It does not require a perfect database or a large budget. It requires a team willing to decide what "recorded" means, write it down, and defend the floor. Start with find, identify, account. Add only what you will genuinely maintain. Review it honestly each year. The objects rarely complain, but the people who come after you will be grateful.
