Exhibitions and venues
In this and the following topic we describe how to manage exhibitions, venues and exhibition items. For this purpose we create at least two records in the Exhibitions and venues1 data source for each exhibition and link them together: a record for an exhibition and one or more records for the venues at which the exhibition takes place:
- We document and manage the status and details of an exhibition in an exhibition record (Record type = exhibition).
- We document and manage the status and details of a venue at which the exhibition takes place in a venue record (Record type = venue).
While it is obvious why we create a record for each exhibition, it may be less so for venues. In the context of an exhibition:
- A venue record does not simply hold details of a physical location, it captures details about a locale for the duration it is required for a specific exhibition (i.e. for a specific period of time).
- A venue may undergo a process of approval each time it is proposed for an exhibition, and we manage that approval process in a venue record unique to that exhibition.
- A venue record tracks the items that are present at the venue for the purposes of a specific exhibition, and this list of items is invariably different for each exhibition.
Why not simply list the exhibition items in the exhibition record? An exhibition record does list all items associated with the exhibition, including those that are ultimately rejected for some reason. However, in an exhibition that takes place across more than one venue, the items may differ from one venue to the next: we keep track of which items are present at a venue for the purposes of the exhibition in venue records.
Here we see the record for an exhibition titled Melbourne 2025, running from 1 January to 1 April 2025, scheduled to run at two venues over this period:
Tip: You can link exhibition and venue records from either side of the relationship.
The creation and management of Exhibitions and venues records are fairly straightforward; however it is worth highlighting the following:

When creating an Exhibitions and venues record the first step is to identify whether the record is for an exhibition or a venue:
Field |
Details |
---|---|
Record type / record_type (Df) |
Drop list. Select either:
For each exhibition we create at least two records in Exhibitions and venues and link them together:
Tip: In this and the following topic we describe how to document collection items that are present at a venue during an exhibition. In this case, a venue record is always linked to an exhibition record. However, this is not the only way to use the Exhibitions and venues data source and a venue does not need to be associated with an exhibition; you could, for instance, have a venue record that documents items in a room (gallery, hall, etc.) within your institution. In this case, you would not link the venue record to an exhibition record. Except for the differences noted above, the panels available for each record type are broadly the same. |

The Exhibition details panel displays when Record type = exhibition.
The purpose and use of many fields are clear and straightforward, and we only highlight those of particular importance below:
Panel |
Field group |
Field |
Details |
---|---|---|---|
Exhibition details |
Exhibition |
|
Provide various metadata describing the exhibition (Category and Exhibition type, both Linked fields |
Title / title (TN) |
Give the exhibition a title. |
||
Alternate title / alternative_title (vn) and Title type / alternative_title.type (vt) |
Provide an alternative title if required in Alternate title. Title type is a Linked field Details about working with the Find data for the field box can be found here. |
||
Category / category (CT) and Exhibition type / exhibition_type (ET) |
Provide various metadata describing the exhibition in Category (e.g. Artist spotlight) and Exhibition type (e.g. digital exhibition, physical exhibition) Both are Linked fields |
||
Reference number / reference_number (RN) |
A reference number for the record. If you do not provide a reference number, a number is automatically assigned when the record is saved. |
||
Dates |
Provide proposed and actual start and end dates. Type a date or click the Calendar |
||
Description / description (BE) |
Text field (will expand to hold a significant amount of information). Provide details about the exhibition such as the theme, content, layout, and any notable features or highlights. The description aims to give a comprehensive overview of what the exhibition entails. |
||
Reason / reason_text (RE) |
Text field (will expand to hold a significant amount of information). Provide details about the purpose or rationale for the exhibition: why the exhibition is being held, its objectives, and intended outcomes. The reason might include the goals of the exhibition, such as educating the public, showcasing a particular collection, or celebrating an anniversary, for instance. |
||
Attendee count / attendee_count (AT) |
Numeric field. Record how many people attended the exhibition. |
||
Total venues / total_venues (tv) | Numeric field. Record the total number of venues at which the exhibition will take place. | ||
Venue / part (nt) |
Repeatable Linked field Details about working with the Find data for the field box can be found here. The Title(part_of (bt)) field in each linked venue record will automatically update to display the title of this exhibition. |
||
Status
|
|
Manage the current status of the exhibition, including who set the status (Status by) and when (Date / Time); any additional information can be added to Status note (current_status.note (sN)). When you change the current status and save the record, the previous status details are recorded on the Status history panel so that a complete log of status changes is retained, including who made the change and when: |
|
Status / current_status (sS) |
Drop list of values. Track and manage the current status (approval) of the exhibition from pending through to completed:
|
||
Status by / current_status.name (sB) |
A Linked field Details about working with the Find data for the field box can be found here. |
||
Date / current_status.date (SD) |
The date on which the status was set. Type a date or click the Calendar |
||
Time / current_status.time(sT) |
The time at which the status was set. Click the Time |
||
Notes / current_status.notes (sN) |
Add any important details about the status change. |
||
Cascade status / current_status.cascade (sC) |
Select the Cascade status checkbox to copy the exhibition record's current status (current_status (sS)) to the Status (exhibit_item.status (OS)) field of all objects listed in the Object list table on the Items panel. The update to the exhibit_item.status (OS) field occurs when the deaccession record is saved. Alternatively, manage the status of each object individually on the Items panel OR in the Exhibition items records themselves. |
||
Sponsors |
|
Provide details, including contact details, of one or more sponsors of the exhibition. |
|
Publications |
|
List one or more publications associated with the exhibition (typically an exhibition catalogue) and provide a link to a website for the exhibition. |
|
Catalogue / publication.catalogue (EC) |
Repeatable Linked field The Associations panel provides more opportunity to list relevant publications. |
||
Exhibition URL / exhibition_URL (U2) |
An Application type field. Enter a URL for a website / page for the exhibition. When viewing the record in Display mode |

Tip: In this and the following topic we describe how to document collection items that are present at a venue during an exhibition. In this case, a venue record is always associated with an exhibition record. However, it is worth pointing out that this is not the only way to use the Exhibitions and venues data source and that a venue does not need to be associated with an exhibition; you could, for instance, have a venue record that documents items in a room (gallery, hall, etc.) within your institution. In this case, you would not link the venue record to an exhibition record.
The Venue details panel displays when Record type = venue.
As most of the fields on the Venue details panel operate similarly to the Exhibition details fields described above, or their purpose and use are clear and straightforward, we only highlight those of particular importance below:
Field group |
Field |
Details |
---|---|---|
Exhibition |
Title / part_of (bt) |
Linked field Note: If an exhibition record has listed this venue in the Venue (part (nt)) field on the Exhibition details panel (details above), this field will already list (and link to) that exhibition record. Start typing the exhibition title (if known) and select it from the drop list, or click the Link The Itinerary group of fields in the exhibition record will automatically update to list this venue (details above). Details about working with the Find data for the field box can be found here. |

Here we specify the overarching theme (or themes) and subthemes of the exhibition:
Themes and subthemes, which are defined as terms in the Thesaurus, represent a structured hierarchy of thematic concepts or subjects for an exhibition (an overarching theme broken down into a series of subthemes). While there is no definitive way to use these, they can be thought of as an intellectual or conceptual mapping of the subject matter of an exhibition; these could in turn be mapped to physical locations in a venue space (items with subtheme A are exhibited in Room 1, for instance).
Thesaurus records for exhibition themes and subthemes are structured in parent-child relationships: a top level term is given one or more narrower terms, each of which can have narrower terms (Narrower term (narrower_term (nt))), and so on, building a structured hierarchy of broader and narrower thematic concepts. Here we see a theme defined for Hawaiian Music, World music
, with three subthemes defined as Narrower terms:
There can be multiple levels to the hierarchy as a Narrower term can have its own Narrower terms: in the example above, Mainland
is a Narrower term (a subtheme) for Hawaiian Music, World music
; it is also a Broader term (broader_term (bt)) in its own right as it has two Narrower terms:
Here we see the full hierarchy:
- Level descriptor 1
Hawaiian Music, World Music
- Level descriptor 2
Mainland
- Level descriptor 3
Introduction to Hawaiian Music
- Level descriptor 3
Ukulele fever
- Level descriptor 3
- Level descriptor 2
Polynesia
- Level descriptor 3
Dance
- Level descriptor 3
Earliest Music
- Level descriptor 3
Tahiti
- Level descriptor 3
- Level descriptor 2
Portugal
- Level descriptor 3
Immigration
- Level descriptor 4
Ukuleles
- Level descriptor 5
Manufacture
- Level descriptor 5
- Level descriptor 4
- Level descriptor 3
- Level descriptor 2
Tip: Details about forming hierarchical relationships in the Thesaurus can be found here.
It is handy to open the Hierarchy browser alongside Record details View when working with records structured in parent-child relationships as all records in the hierarchy are listed and can be selected and viewed.
When building your hierarchy of exhibition themes, give the highest level (Hawaiian Music, World Music in this example) a domain A subset of records in an Authority data source, grouping similar sorts of records. When a search or Linked field is associated with a domain, only records in that domain are available to that field. For example, records for authors can be assigned to the AUTHOR domain (using the Name Type / name.type (do) field). When linking a record for a book to a record for its author, the Author Linked field will point to the AUTHOR domain, a subset of records in Persons and institutions exclusively for authors. In the Thseaurus, a record is assigned to a domain using the Term Type / term.type (do) field. / Term type (term.type (do)) of exhibition theme list; when the record is saved, it is automatically given a Level descriptor (level_descriptor (ld)) of
1
.
All other terms in the hierarchy are given a Term type (term.type (do)) of exhibition theme. In this example, when you save the Mainland
exhibition term, it is automatically given a Level descriptor of 2
, and so on.
Tip: It is not necessary to specify a Level descriptor for terms with a Term type of exhibition theme or exhibition theme list as the level is calculated and applied automatically when the Term type is selected and the record is saved. If you are using existing terms in your theme list however, it may be necessary to edit them and apply the correct Level descriptor.
The Level descriptor is used to filter which terms are listed in the Theme and Subtheme fields in an Exhibition and venues record.
Field group |
Field |
Details |
---|---|---|
|
Theme list / theme_list (TH) |
A Linked field When a Theme list is selected, the Theme, Subtheme 1, Subtheme 2, etc. fields will only list exhibition themes in the selected Theme list. Furthermore:
If there is no suitable Theme list, ignore this field and search for and select appropriate themes and subthemes in the Theme and Subtheme 1, Subtheme 2, etc. fields. |
Themes |
Theme / theme (T0) |
A Linked field Which terms are listed in Theme will depend on whether you selected a Theme list above:
|
|
Subtheme 1 / theme.subtheme1 (T1) etc. |
Linked fields Which terms are listed in Subtheme1 (etc.) will depend on whether you selected a Theme list above:
|

The Associations panel is only present for exhibition records (Record type = exhibition). The fields on this panel provide an opportunity to add a broad range of contextual and other associated details about the exhibition:
Many of these fields are Linked fields A type of field used to link one record to another. A Linked field is a drop list of values (records that the field can link to). When a link is made, the field stores a reference to the linked record (a linkref).: start typing a value into a Linked field and select it from the drop list, or click the Link
icon to display the Find data for the field box; search for the relevant value or create a record in the linked data source
The management of a collection can involve a vast amount of information about objects / items / books, people and organizations, events, administration and more. This information is stored as records in data sources. Each data source stores a specific type of information: details about collection items, people, events, loans, and so on. and link to it (if authorized to do so).
Details about working with the Find data for the field box can be found here.
Field group |
Field |
Details |
---|---|---|
Persons / institutions |
|
Repeatable group of fields. Identify one or more people or institutions involved with the exhibition in some way that is not recorded elsewhere in this record. |
Name / associated_person.name (kj) |
A Linked field |
|
Association / associated_person.association (kk) |
A Linked field to the Thesaurus with values such as featured artist. Select (or add) a term that captures the party's relationship with the exhibition. |
|
Notes / associated_person.notes (kn) |
Provide details about the person / institution's involvement with the exhibition. |
|
Subjects |
|
Repeatable group of fields. Compare to themes and subthemes (described above), which represent a structured hierarchy of thematic concepts for an exhibition. In Subjects you would list and describe one or more subjects that relate to the exhibition in some way but which are not part of the conceptual mapping defined by themes. Subjects are another way of categorizing and organizing the content of the exhibition. The availability of date fields (Start date and End date) when defining subjects allows you to provide a temporal context for a subject; for instance, if the subject is Fashion in the 60s, you could specify a suitable Start date and End date (e.g. 1 January 1960 to 31 December 1969). |
Events |
|
Repeatable group of fields. Name is a Linked field |
References / citations |
|
Repeatable group of fields. Both Catalogue and Citation are Linked fields to References and citations. List one or more catalogues (publications) for the exhibition and / or publications which cite the exhibition or items in it. |
Associated library material |
|
Repeatable group of fields. Title is a Linked field to the Library catalogue. List any publications relevant to the exhibition; include a page reference (in Page mark) and details in Note. |

The current status of the exhibition or venue is shown on the Exhibition details or Venue details panel. Any time the current status details are changed and the record is saved, the previous status details are recorded on the Status history panel, ensuring that a complete log of status changes is maintained:
Exhibition and venues records include the Expenses and income, Actions, Media, Digital references and Free fields panels.