We're in the process of updating this guide to reflect Objects & Order version 3.
The Structured List field type is ideal for capturing object data comprising multiple, related components of information, whether that be for provenance, bibliographic resources, exhibition history, or similar records. It lets you build an expandable, orderable list of related entries.
While you could include a list of items in a Long Text or Rich Text field type, or add a Select or Dataset field type that allows for multiple selections, a Structured List lets you rearrange entries and add detailed information.
For more information on selecting field types for specific use cases, see Setting Up Blueprint Fields.
Use Case: Bibliography
When you plan to add bibliographic citations for objects, you can add a Structured List field type to your Blueprint.
Structured List is one of the types available under the Fields tab. Click it and one will appear at the end of your Blueprint.
- First, we'll enter Bibliography as the field label.
- Then we'll indicate the maximum number of entries. By default, this begins at 50; here we've changed it to 100 items.
- Next, we've toggled on the Enable Markdown option (more about this below).
We'll look at the other toggleable options later.
You can also enter helpful data entry notes about preferred formatting, resources, or standards.
On an object page, when you add data in a Structured List form field, you'll add each item separately by clicking the plus (+) icon.
Here we've added two bibliographic entries. To italicize titles using Markdown, we've added an asterisk to either side of the title. Note that in the first example, punctuation goes after the asterisk: Motion*.
The formatting note appears below the entries, to help ensure data is entered correctly.
Now that we've added multiple entries, let's drag and drop them into alphabetical order using the dragger icon to the left of item. Remember to save.
Use Case: Exhibition History
You can also add a Structured List field type for inclusion in exhibitions. Here we've labeled the field Exhibition History and we've selected the Markdown option (since exhibition titles are italicized).
Use Case: Provenance
For Provenance, we'll add a Structured List field type.
- First, we'll enter Provenance as the field label.
- We'll set the maximum number of items at 25.
- We'll toggle on Enable Entry Label
- We'll toggle on Enable Markdown (to italicize auction catalogue titles, for example)
- We'll toggle on Internal. This means that this information will NOT be available to share in Exhibitions or Modules.*
*Currently, no Structured List data can be shared in Exhibitions or Modules, but this option will be introduced in a future update. When implemented, Markdown formatting will display (italicized titles, for example).
On an object page, under Provenance, add each item separately by clicking the plus (+) icon.
Since we toggled on the option to Enable Entry Label in our Blueprint, you'll see form fields for Entry Label and Content. The Entry Label allows you to provide a custom label you'll see first when you visit an object page.
Here, for example, we're using Date Range: Name (Nationality, Life Dates) in the entry label. You might only include the date range here, or only the owner's name, depending on the format that works best for you. Then, you can enter additional content below.
Again, you can reorder these entries using drag and drop, if necessary.
After provenance information has been entered for your objects, you can lock the form field to prevent further data entry. Go back to your Blueprint and toggle on Locked.
Now, when you view your object information, you'll see a blue padlock next to Provenance and the fields will be grayed out. To unlock the field for further data entry, just go back to the Blueprint.
The Structured List field type can be used whenever you need to create an expandable list of separate but related items that can be reordered with ease.
Need some help planning for structured lists? Don't hesitate to reach out!