Exhibition items

Introduced with the Standard Model, Items data sources are used to document and track collection items involved in day to day activities like loans and exhibitions. In prior Model Applications, when a collection item is on loan its Catalogue record (with details about the item) links directly to a Loans record (with details about the loan); what is lacking is somewhere to record details about the item in the loan, to track the status of each item as it navigates the loan workflow, or to plan actions that impact an item's involvement in the loan. The same is true of items involved in acquisitions, exhibitions and collections audits. Items data sources fill this gap by providing a place to manage and document each item individually as it participates in activities like loans and exhibitions. They include Acquisition items, Exhibition items, Loan items and Collections audit items.
An overview of Items data sources can be found here.
The primary use of the Exhibitions and venues1 data source is to document and manage the status and details of exhibitions and the venues at which they take place. In conjunction with Exhibition items, it is possible to document and manage individual items exhibited at each venue of an exhibition:
- We document and manage the status and details of an exhibition and the venues at which it takes place in Exhibitions and venues records.
- We document and manage the items associated with an exhibition in Exhibition items records.
Although records can be created in an Items data source in the usual ways (in Loan items for example) and from there manually linked to the relevant activity record (Loans, etc.) and Catalogue record, the recommended way to create Items records is to use the tasks designed for creating and linking records. That is the method described below.
In the case of Exhibition items records, the Create exhibition items task is run in the Catalogue after first marking Marking a record means selecting it by adding a tick to the record's checkbox in Result set View or Gallery View, and in Record Details View from Collections 1.15 onwards. One or more records can be marked and then actioned in some way (e.g. printed). one or more object records: to run this task there must be a record for each item in the Catalogue; typically there would already be a record for the exhibition in Exhibitions and venues and for each of the venues at which items are to be present.
When the task is run an Exhibition items record is created for each selected object; each Exhibition items record sits between the object's Catalogue record and at least two records in Exhibitions and venues: one for the exhibition (which lists ALL items associated with the exhibition, including those that are ultimately rejected for some reason) and another for the venue (listing ONLY items present at the venue for the purposes of the exhibition, including those that are not on display for some reason).
For this demonstration we have an exhibition called Melbourne 2025, which is documented in an exhibition record in Exhibitions and venues. The exhibition will take place at two venues, which are documented in venue records in Exhibitions and venues:
Note: We step through the creation of exhibition and venue records here.
To create one or more Exhibition items records:
- In the Catalogue, mark
Marking a record means selecting it by adding a tick to the record's checkbox in Result set View or Gallery View, and in Record Details View from Collections 1.15 onwards. One or more records can be marked and then actioned in some way (e.g. printed). the record for each item being considered for inclusion in the exhibition.
If an exhibition has multiple venues
At Step 3 we assign selected items to an exhibition and to the venue(s) at which they are required (where an item will be exhibited or where it is present but not on display).
Note: An item might not be displayed at a particular venue (perhaps it is not suited to that locale) but it travels with the other exhibition items, eventually moving on to a venue where it will be exhibited. In this case, the item is assigned to each venue where it is required and flagged as Not on display.
If an exhibition has multiple venues and all items are required at all venues, select the Catalogue records for all of the items and assign them to all venues (at Step 3 below).
If some items are NOT required at ALL venues:
- First select the items that ARE required at ALL venues and assign them to ALL venues (at Step 3 below).
- For the items that are only required at a subset of venues, select those items, repeat the Create exhibition items task but only assign the items to the venue(s) at which they are required (at Step 3 below).
- Repeat until all items are assigned to the appropriate venues.
The exhibition record will list ALL items exhibited throughout the exhibition; the venue records will only list the items that are required at that venue; and the Exhibition items records will only list the venue(s) at which the item is required.
- Select Create exhibition items from the Task
drop list in the Result set View toolbar.
The Create exhibition items pop-up will display:
- Complete the fields in the Create exhibition items pop-up:
Field
Details
Exhibition
Exhibition is a Linked field
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). to Exhibition and venues. Records in this data source hold high-level details about an exhibition event that may involve multiple items, each one of which is documented in its own Exhibition items record. You document and manage the overall status and details of an exhibition in an Exhibition and venues record; you document and manage the status and details of an individual item in an Exhibition items record.
If you know the name of the exhibition, start keying it into the field and select it from the drop list when it displays:
Otherwise click the Link
icon to display the Find data for the field box; search for the relevant exhibition event or create a record for the exhibition and link to it (if authorized to do so).
Details about working with the Find data for the field box can be found here.
Venue
An exhibition can be held at one or more venues. When you specify the name of the exhibition in the Exhibition field, the Venues drop list is automatically filtered to venue(s) already specified for this exhibition (in the exhibition's Exhibition and venues record):
Here we assign the items selected at Step 1 to the venue(s) at which they are required:
- Select the first venue for the exhibition in Venue 1; a Venue 2 drop list will be added. If the exhibition only has one venue, ignore the Venue 2 drop list and move on to Step 4.
If an exhibition has multiple venues and all items are required at all venues, select each venue from the drop lists.
Note: An item might not be displayed at a particular venue (perhaps it is not suited to that locale) but it travels with the other exhibition items, eventually moving on to a venue where it will be exhibited. In this case, the item is assigned to each venue where it is required to be and flagged as Not on display where appropriate.
If some items are NOT required at ALL venues, repeat the Create exhibition items task for items that are only required at a subset of venues (explained above), only selecting venues where those items are required.
-
Click OK to create the Exhibition items record(s).
When the task is run, an Exhibition items record is created for each item selected in the Catalogue at Step 1; all of them are listed on the Items panels in the Exhibition and venues record for the exhibition AND the Exhibition and venues record(s) for the nominated venues. Here we see the Items panel in the record for the exhibition:
Both venues records selected above include these details:
In the Catalogue record for each item selected at Step 1, the Exhibitions panel now includes details about the exhibition event (linking to an exhibition record in Exhibitions and venues) and the Exhibition items record created for the item:
You will probably want to add more detail to the Exhibition items record(s) created by this task, and may want to update the status of each item as it progresses through the approvals process (they have a status of pending by default). To do so, search the Exhibitions items data source for a record to provide far greater detail about the item and its involvement in the exhibition.
Tip: It is useful to open Related records View alongside Record details View and / or Result set View when working with Items records as all linked records are identified and can be navigated to with ease.

As you work with Exhibitions and venues records and Exhibition items records you will discover that much of the same sort of information is recorded in different places, from the high level exhibition record down to the granular exhibition items record. A good example is Status. The status of items in an exhibition can be managed and tracked in various places:
- In the high-level exhibition record in Exhibitions and venues all exhibition items are listed on the Items panel and it is possible to manage the status of each item's participation in the exhibition here (this is an efficient way to manage the status of all items in a single record).
- In the Exhibition items record for each item it is also possible to manage and track the item's participation in an exhibition on the Exhibition item details panel (any changes to the item's Status here are tracked on the Status history panel); on the Venues panel it is also possible to manage the status of each item's installation at a venue.
It is up to your institution how detailed and granular you need such information to be when recording details about exhibitions, venues and exhibition items.
Exhibition items panels
Below we look at the key panels in an Exhibition items record:

The Exhibition item details panel includes a record summary (displaying critical details about the exhibition item), details about the status of the item, details about the object and the exhibition (linking to the Catalogue and Exhibitions and venues records):
Some of this information is pulled from linked records and is read-only, some can be edited; in particular you will want to update the Status information as the item progresses through the approvals process:
Field group |
Field |
Details |
---|---|---|
Default theme / section |
|
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). You will find details about how exhibition themes and subthemes are defined in the Thesaurus, and how they are used in Exhibitions and venues, here. In the record for the exhibition in Exhibitions and venues, the overarching theme (or themes) and subthemes can be specified on the Themes panel. In Exhibition items records we are able specify which of those themes and subthemes apply specifically to the item. |
Theme / theme (T0) |
A Linked field Note that the record for the exhibition in Exhibitions and venues may already identify and list the overarching theme(s) and subthemes for this exhibition and your selection here must be from that list of terms (details here). A theme can have one or more subthemes defined; if so, the Subtheme fields will be filtered to include only those subthemes defined for the theme you select here. |
|
Subtheme 1 / theme.subtheme1 (T1) etc. |
Linked fields Start typing the term for the subtheme that applies to this item and select it from the drop list, or click the Link |
|
Theme notes / theme.notes (TO) |
Add any important details about the themes. |
|
Position / theme.position (TP) |
Here you could identify the relative importance of this item within the theme / subtheme (perhaps indicating the prominence of its location in a venue). |
|
Publications
|
|
If one or more catalogues / publications have been produced for the exhibition, you can link to their record in References and citations here. Multiple occurrences |
Catalogue / publication.catalogue (PC) |
A Linked field Details about working with the Find data for the field box can be found here. |
|
Catalogue number / publication.catalogue_number (TC) |
If the item is referenced in the publication with a number, record it here. |
|
Status
|
The participation of an item in an exhibition is a journey marked by changes in the item's status as it undergoes a process of approval. When the Exhibition items record was created, a status of pending was set for all items selected at Step 1. Going forward, the status of each item can be tracked and updated in its Exhibition items record. 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: Note: While it is also possible to update the status of an exhibition item on the Items panel in an Exhibition and venues record, this will not update the exhibition item's Status history. |
|
Status / current_status (sS) |
Drop list of values. Select the current status of the item's participation in the exhibition:
Note: The status of the item's participation in a venue can also be managed on the Venues panel. |
|
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. |
|
Loan item associations |
Reference number / loan_item (G0) |
A Linked field If you know the Loan items reference number, start typing it into the field and select it from the drop list; otherwise click the Link Details about working with the Find data for the field box can be found here. |

When Exhibition items records are created with the Create exhibition items task, items are assigned to one or more venues, and these are automatically listed on the Venues panel. Here it is possible to specify the start and end dates between which the item is present at the venue; it is also possible to manage the status of the item at the venue and to specify themes and subthemes relevant to the item's participation at a venue (in the event that the themes / subthemes differ from one venue to another).
All of the fields on this panel are a grouped occurrence If a field in the current record can have more than one value, we add an occurrence of the field for each value (e.g. a book can have multiple authors so we add an occurrence of the author.name (au) field for each author). An occurrence can be a member of a group of fields, and adding an occurrence of the field adds all members of the group at once. and can be repeated as a group or deleted as a group as required. There will be a group of fields for each venue that an item is assigned to with the Create exhibition items task:
Field |
Details |
---|---|
Venue / venue (VN) |
A Linked field Although it is possible to add another venue to the Venues panel (select Occurrences>Add row above/below from the Record details View toolbar), it is recommended that you use the Create exhibition items task to assign items to an exhibition and venue. It is possible to unassign an item from a venue by removing its occurrence on this panel. This will remove all of the fields in this occurrence group. Tip: It is also possible to unassign an item from a venue in the venue's Exhibitions and venues record by removing the item's row (occurrence) from the Object list table on the Items panel. Details about working with the Find data for the field box can be found here. |
Not on display / venue.not_on_display (DX) |
A checkbox used to flag that an exhibition item is present at the venue but not exhibited. The Not on display checkbox might be used when an exhibition has more than one venue and an exhibition item is not exhibited at every venue, perhaps because a venue is not suited to the item: the item has travelled to the venue with the other exhibition items (it is present at the venue but not exhibited) and it will travel on to a venue where it will be exhibited. |
Start date / venue.start_date (vs) End date / venue.end_date (ve) |
Specify the start and end dates for the period during which the exhibition item is present at the venue. Type a date or click the Calendar |
Status / venue.status (Vs) |
Drop list of values. Select the current status of the item's installation at the venue:
|
Status date / venue.status_date (VD) |
The date on which the status was set. Type a date or click the Calendar |
Theme / Subthemes Order / position |
The purpose and management of themes and subthemes is explained above. It is possible that the themes and subthemes vary from one venue to the next; if so, identify the themes / subthemes / order / position as they relate to this item in this venue. |

The Actions panel is a basic workflow tool designed for managing tasks (actions) relating to the current record. The type of action tracked depends on the data source you are working in (actions in the Catalogue will not necessarily be the same as actions in Loans for instance); actions might include anything from scheduling meetings, reviews, to photography sessions, etc. Managing tasks might entail scheduling an action (a meeting for instance), tracking an action's progress (the crate has been ordered) or documenting that an action has been performed (the object was moved). This functionality is not meant to replace dedicated project management software, but it can be used to prescribe standard procedural tasks (setting default actions) and to track and log tasks relating to the current record.
Default and conditional actions
Application Administrators can define default actions for any new record in the System admin – occurrence defaults data source.
If an action is required when certain conditions are met, occurrence defaults can be set up to facilitate this; for example, in Acquisitions and acquisition proposals a Send Deed of Gift action can be added when a record has an Acquisition method (method (sm)) of gift and a Status (current_status (sS)) of approved.
Provide details of various actions (selected from the Type field) which affect this item throughout the loans process:
The purpose and use of many fields are clear and straightforward, and we only highlight those of particular importance below:
Field / System name |
Details |
---|---|
Type / action.type (U0) |
A Linked field Actions might include: acquisitions meeting, conservation review, meet with donor, etc. Tip: Application Administrators can add additional action types in the System lists data source. Details about working with the Find data for the field box can be found here. |
Responsible / action.person_responsible (UA) |
A Linked field Details about working with the Find data for the field box can be found here. |
Requested by / action.requested_by (U6) |
A Linked field |
Request date / action.request_date (uA) |
The date on which the request was made. Type a date or click the Calendar |
Priority / action.priority_level (Uc) |
Drop list of values. Indicate the priority of the action:
|
Date due / action.date_due (u2) |
The date the action should be completed. |
Start date / action.date_start (U1) |
The date the action commenced. |
Date completed / action.date_complete (U4) |
The date the action completed. |
Confidential? / action.confidential (U9) |
Checkbox indicating the sensitivity of the action. Tip: Although selecting the checkbox does not trigger any action in the software, it could be used by a script to exclude confidential actions when running a report, for instance. |
Status / action.status (U8) |
Drop list of values. Select the current status of the action:
|
Status date / action.status_date (u8) |
The date the status was set. |
Rec. Ref. / action.record_reference (u9) |
Short for Record reference: if an action is part of a larger project, enter the reference number for that project. Although there is currently no functionality built around this or the following field, Job no., it is anticipated that an Action Request tool will become available in a future release that will connect individual actions back to an original request or project. |
Job no. / action.job_number (uB) |
Used for internal numbering of individual actions. This is useful if actions are generated (or referenced) by an originating Action Request. |
Description / action.action_text (u1) |
Provide detail about the action. As Type is a Linked field, Description can be useful for providing nuance for what is expected from an action. |
Notes / action.notes (u7) |
Document any outcomes, problems, or information that might be helpful for completing the action. |

Associate media such as images, video and audio with the current record by linking to or uploading media:
Note: See Adding documents, URLs and PDFs above if linking digital documents (e.g. Word documents or PDFs) with the current record.
If the media you want to associate with the current record is already available in the Multimedia documentation data source, select the Link icon in the Reference field to open the Find data for the field box. Search for and select a media record to link to the current record
The record currently displayed in Record details View or highlighted (with a solid grey background) in Result set View or Gallery View for instance. (full details about using the Find data for the field box can be found here).
If you want to upload new media and associate it with the current record, select the Upload option to locate a file accessible to your device. When a media file is uploaded and the current record is saved, a basic record is automatically created for the media in the Multimedia documentation data source, and it is linked to the current record's Reference field.
Once you save the current record, the media will be visible in Media viewer.
There is a lot more to working with media and full details can be found here.

On the Digital references panel we link to relevant digital documentation (Word docs, PDFs, URLs etc.):
Word docs and URLs (and other digital references) are linked to a record using a field with an Application data type such as File (File (RF)) on the Digital references panel. A field with an Application data type is associated with an application, such as a PDF reader; depending on your browser's configuration, clicking the underlined file name for a .pdf
file will open the document in a browser tab:
Alternatively, click the Download icon to download and view the document.
Use these repeatable fields to link to one or more digital documents (Word docs, PDFs, URLs etc.) relevant to this acquisition item.
Field / System name |
Details |
---|---|
Type / Type (Ro) |
A Linked field |
File / File (RF) |
If you know the path to the digital reference, type it into this field; alternatively, for digital documents, select the Upload |
Description / Description (RT) |
Enter a brief description of the digital reference. |

Most fields in Collections are intended to hold a specific piece of information (an object number, a title, a birth date, and so on) often defined by an industry standard (SPECTRUM or ISAD(G), for instance). Free fields, which are found on a Free fields panel typically near the bottom of the list of tabs in Record details View, provide more flexibility; while not new to Collections, their use in the past was mostly limited to holding data migrated from fields in legacy systems that had no obvious equivalent in Collections.
Note: In systems running Model Applications prior to the Standard Model, there is a single text type of free field.
The release of the Standard Model saw a significant increase in the number of fields and data sources available in Collections so that there is almost certainly a suitable field to hold your data without the need for customization. This has allowed for a new approach to the use of free fields in systems running the Standard Model, and Free fields panels are now intended as an alternative, where appropriate, to customization of the application. To that end, Free fields panels are now available across more data sources; and it is no longer necessary to store all types of data in a generic text field as there are now free fields to hold text, dates and numbers, and there is also a checkbox variant:
Their use is straightforward. You specify the purpose of the field in Type (name the field) and enter the value in the Content field:
Note: As values in the Type field are managed in the System lists data source2, Application Administrators ($ADMIN
users) are free to add new values as required.
As each group of fields on the Free fields panel (Texts, Dates, Checkboxes, Numbers) is a repeatable group of fields, you can use the Occurrences drop list in the Record details View toolbar to add / remove / move a group of fields.
If there is no native field for a piece of data, consider whether a free field can be used to hold it, avoiding the need to customize the application.