INST0089 Chap.1 Description for Identity and Use
Description for Identity and Use
Description for Identity and Use begins with the resource rather than the form. A record must make clear what is being described, which level or boundary applies and what another person or system should be able to do. The teaching material groups useful description around identity, content and context. Identity distinguishes the resource through names, types, identifiers and versions.
Content states what it contains or concerns. Context situates it through creation, use, custody, relationships and rights. These layers support disambiguation, findability and reuse when values are accurate, controlled where appropriate and traceable to evidence. The chapter also treats uncertainty as part of accuracy. A qualified date or attributed title can be more reliable than a neat unsupported value.
Audience analysis then decides sufficient granularity. A lost-property task, retail search and conservation record may concern the same object but need different facts. The boundary stays explicit while the field selection changes with purpose.
What this chapter covers
- 01
Unit of description and descriptive boundary
- 02
Identity, content and context
- 03
Disambiguation and distinctive features
- 04
Findability through searchable controlled values
- 05
Reusability through rights, provenance and documentation
- 06
Audience tasks and sufficient granularity
Worked example · free
Describe one oral-history clip
- 2Define the clip as the record subject and keep the collection as a related resource.
- 2Use the title, resource type, local identifier and version for identity.
- 2Use concise subjects and a neutral summary for searchable content.
- 2Record creation, language, rights, access and collection relation as context.
Key terms
- Descriptive boundary
- The stated limit determining which resource one record is about.
- Disambiguation
- The use of verifiable detail to distinguish one resource from similar resources.
- Findability
- The capacity for an intended user or system to discover a resource.
- Provenance
- Recorded evidence about the origin, custody or history of a resource or value.
Description for Identity and Use FAQ
Why is a label not enough?
A label usually names a broad class, while a description supplies the identity, content and context needed to distinguish one resource and act on it. Calling something a poster or bottle cannot support reliable recovery, discovery or management until the record adds evidence such as identifiers, dates, relationships, distinctive features and rights.
How do I choose the correct descriptive level?
State the resource in one sentence and test every value against that subject. An item, folder and collection can share topics or creators but still need different dates, identifiers and rights statements. When a fact belongs to another level, preserve it through a relation instead of silently mixing levels in one record.
Should uncertainty be removed from a record?
Uncertainty should be represented honestly rather than hidden. Use qualified dates, attributed titles, notes or controlled status values when evidence is incomplete. A transparent uncertain value is easier to review and correct than a confident guess, especially when the record will be reused outside the original project context.
Assessment move
Begin revision with a boundary drill. Choose an everyday or archival resource and write separate statements for the item, its container and the collection. Allocate every observed fact to identity, content or context, then remove anything that belongs to a different level. Next, rewrite opinion and vague language as observable or attributable description.
Replace words such as important, old or large with evidence, measurement or a qualified statement only when the evidence supports it. Practise the three course purposes independently. For disambiguation, add stable identifiers, distinctive features and a clear level. For findability, test titles, subjects, types and synonyms against realistic searches.
For reusability, add rights, provenance, method notes and uncertainty documentation so someone outside the project can act without private knowledge. Change the audience while keeping the resource constant. Compare what a researcher, public visitor, conservator and internal manager would need, and explain why the selected granularity changes.
Maintain a short decision log containing the field, value source, user task and any limitation. Use that log to audit whether every descriptive choice has an evidence trail. Finish each practice record by handing it to an imagined stranger. Ask whether that reader can identify the resource, understand why it matched a query, follow its relationships and know what use is permitted.
If the answer depends on an unexplained local abbreviation or on information held only by the cataloguer, improve the documentation rather than adding decorative detail. Add a counter-record to every revision session. Keep the same object but change the descriptive level or audience, then mark which fields must change and which should remain stable. This contrast exposes assumptions that a single polished example can hide.
End by explaining one omission. Naming why a field was excluded, whether because evidence is unavailable, the value is sensitive or the user task does not require it, develops stronger judgement than filling empty spaces for appearance. Recheck the boundary after every relationship is added, because a relation can quietly import facts that belong to another record.