SmellBook
Menu

FOR INSTITUTIONS · HERITAGE RECORDS · FORMAT 0.4-DRAFT

Heritage record templates.

A heritage record describes a smell connected to an object, a document, a place or a practice, and links it to SmellBook by permanent identifier. The format is a draft for discussion; no institution has adopted it yet.

Four kinds of record

Every template as JSON, with the worked examples and their check results: /data/heritage-templates.json. The full format: JSON Schema.

What to write in each field

Worked examples

Worked examples are built only from evidence SmellBook has registered and are recorded by SmellBook from registered sources and their public catalogue or publisher records; the institutions named in them hold the sources and have not reviewed, endorsed or contributed the records. Illustrative records are invented, begin with EXAMPLE- and name no real institution. SmellBook has no institutional partners.

From a collection export

A LIDO or Dublin Core export describes the object, not its smell. The offline collection tool (node smellbook-collection-tools.mjs import export.xml) turns it into draft records: object fields are copied, smell fields are left for you, descriptions are never copied as smell descriptions, and subject terms that match a SmellBook name are only suggested.

LIDO elementBecomesNote
lidoRecIDrecordIdThe LIDO record identifier becomes the record ID.
objectIdentificationWrap/titleWrap/titleSet/appellationValuetitleThe first title.
objectIdentificationWrap/repositoryWrap/repositorySet/repositoryName/legalBodyName/appellationValueholdingInstitutionThe current repository holding the object; a repositorySet marked former is skipped.
objectIdentificationWrap/repositoryWrap/repositorySet/workIDobjectReferenceThe inventory number in the current repository.
recordWrap/recordInfoSet/recordInfoLinkobjectUrlOnly when it is an http(s) URL of the object record.
eventWrap/eventSet/event (production or creation)/eventDate/date/earliestDateperiodFromOnly from the production or creation event (eventType production or creation, or LIDO terms lido00007 and lido00012), and only a year or ISO date; the period basis becomes object-dating. Dates of other events (acquisition, exhibition) are never used.
eventWrap/eventSet/event (production or creation)/eventDate/date/latestDateperiodToAs earliestDate, from the same event.
eventWrap/eventSet/event (production or creation)/eventDate/displayDateperiodLabelThe date as displayed, from the same event.
eventWrap/eventSet/event (production or creation)/eventPlace/place/namePlaceSet/appellationValueplaceNamePlace name only, from the same event; link a SmellBook place or locality in placeEntity.
eventWrap/eventSet/event (other types)not copiedNot copied: an acquisition, exhibition or other event does not date the object.
rightsWorkWrap/rightsWorkSet/rightsType/termnot copiedNot copied: these are rights in the object itself, not the licence of a heritage record about its smell.
subjectWrap/subjectSet/subject/subjectConcept/termnot copiedNot copied. Terms matching a SmellBook name exactly are suggested as links to confirm.
objectDescriptionWrap/objectDescriptionSet/descriptiveNoteValuenot copiedNot copied: it describes the object. Write the smell in smellDescription.
objectClassificationWrap/objectWorkTypeWrap/objectWorkType/termnot copiedNot copied.
eventWrap/eventSet/event/eventActornot copiedNot copied: the object's maker is not the person recording the smell (recordedBy).

The Dublin Core mapping is in /data/heritage-crosswalk.json.

Back into your catalogue

The same tool (node smellbook-collection-tools.mjs export records.json --format lido) prints, for every valid record, the statements to add to your own catalogue so it points to SmellBook. SmellBook writes nothing into anyone's catalogue.