INST0089 Chap.4 Dublin Core Record Design
Dublin Core Record Design
Dublin Core Record Design applies a broad element set without treating it as a checklist. Simple Dublin Core contains Title, Creator, Subject, Description, Publisher, Contributor, Date, Type, Format, Identifier, Source, Language, Relation, Coverage and Rights. Selection begins with the resource boundary and user task.
Close elements assert different relationships: Creator and Contributor separate primary responsibility from another contribution; Type and Format separate content nature from manifestation; Identifier and Source separate reference from derivation; Relation and Coverage separate connected resources from spatial or temporal scope. Value formation matters as much as element choice.
Sortable dates, concise subjects, stable identifiers, defined language tags and attributable rights statements support later use. Repeated properties usually preserve multiple values better than one joined sentence. A project may add qualifications or local extensions, but it must document their meanings and mappings.
What this chapter covers
- 01
Simple Dublin Core element set
- 02
Creator and Contributor roles
- 03
Subject and Description values
- 04
Type and Format distinctions
- 05
Identifier, Source and Relation
- 06
Coverage, Rights and value evidence
Worked example · free
Build a community-poster record
- 2Transcribe or attribute the title and encode the event date according to the project date rule.
- 2Assign the organiser to Creator or Contributor only when the evidence supports that relationship.
- 2Use concise subjects, a neutral description, content Type and the actual digital Format.
- 2Record the collection Relation and an attributable Rights statement from the archive evidence.
Key terms
- Simple Dublin Core
- A resource-description element set containing fifteen broad properties.
- Creator
- An entity primarily responsible for making the content of a resource.
- Contributor
- An entity responsible for another contribution to the resource content.
- Coverage
- The spatial, temporal or jurisdictional scope of resource content.
Dublin Core Record Design FAQ
Do I need to fill every Dublin Core element?
No. Select elements supported by evidence and required by the user scenario. An optional field filled with a guess or repeated boilerplate reduces quality. Document intentional omissions and blank states, especially where attribution, rights or sensitive information limits what can be asserted or published.
How are Type and Format different?
Type describes the nature or genre of the content, while Format describes its physical or digital manifestation, such as a media type, size or duration. An interview recording and its transcript may need related records because their content types and file formats differ even when they represent the same event.
When should a property repeat?
Repeat a property when the resource has several independent values, such as multiple subjects, creators or relations. Separate values are easier to filter, transform and validate than a comma-separated sentence. The project should still define ordering, roles and the vocabulary used for each repeated statement.
Assessment move
Learn Dublin Core through distinctions and record building. Create a two-column list of element pairs that students commonly confuse: Creator and Contributor, Subject and Description, Type and Format, Identifier and Source, Relation and Coverage. For each pair, write the relationship asserted and one counterexample showing why substitution would be wrong. Build compact records from original everyday or community resources.
Begin with a boundary sentence, then choose only the elements needed for identification, discovery, connection and reuse. Write the value source beside every entry: displayed text, deposit documentation, project rule, controlled vocabulary or cataloguer analysis. Practise dates by distinguishing creation, publication, event, deposit and coverage roles.
Use a consistent sortable pattern only when the evidence supports the precision. Practise subjects by replacing sentences with concise terms, then test whether the terms support useful filtering without erasing local language. Treat identifiers as contextual promises. Check uniqueness, stability and resolvability where relevant. Separate derivation through Source from broader relationships through Relation.
Audit rights through attributable evidence rather than visibility. A file accessible on the web is not automatically licensed for reuse. After building several records, sort and group each property across the set. Inconsistencies become visible when dates, names, types or relations are compared together. Finish by handing a record and its value rules to another reader. Ask them to recreate the record from the resource.
Differences reveal where definitions, examples or boundaries need improvement. Build one deliberately incomplete record and explain every omission. This stops completeness from becoming a visual goal detached from evidence. Then transform the record into a simple table and inspect whether repeated properties and relations remain separate. If the transformation creates ambiguity, revise the value rule or document the loss.
End by comparing the record against a realistic search, identification and reuse task, because element correctness is only one part of fitness for purpose. Keep the failed search terms as evidence for the next vocabulary review.