| Section | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Field groups are just that- groups of fields, a nice way to organize common content. For example, you could have a field group called "Creator" and in this group would be fields related to "Creator", such as "Creator Date", "Creator Nationality", etc. In the LUNA Viewer the fields will always display grouped as a set.
To create a new Field Group click New Field Group
To add fields to a field group, click on the field group and then click New Field.
| Note |
|---|
When editing a Template you can go back anytime and change a Field Group to an Authority or do the reverse. However, when editing a Data Schema, field groups are permanent and can't be changed. |
Repeating Fields
In the Record Editor, there are two ways to create repeating fields.
For a single field with repeating values, check "Multivalue" located in the field properties.
For multiple fields that repeat as a group, create a field group first and then add the fields to that group. In the example below you see a field group with the fields Title, Title Type and View repeated twice. Visit Record Editor help section for additional information on repeating fields.
In Library:
In Viewer:
Authorities
Authorities are a helpful way of providing data catalogers with a list of controlled vocabularies. This helps ensure data consistency across a collection. With the right permissions you can create new authorities, and upload a .csv list of authorities. Catalogers would then easily pick from the list of available data. Authorities are managed in the Library, and permission for managing authorities granted in the Administrator.
To create an Authority:
- Create and name a field group.
- Check the "Authority Field Group" box. All the fields in that field group will then be associated with that authority.
In the example below the "Location" field group is an Authority so the fields "City", "State of Provence", "Country" and "Country code" can all be populated with values from that specific "Location" authority.
| Note |
|---|
When editing a Template you can go back anytime and change an Authority to a Field Group or do the reverse. However, when editing a Data Schema, Authorities are permanent and can't be changed. |
...
- Display Name: give the field a name. This will display in both the LUNA Viewer and in the LUNA Library.
- Field Type: choose either text or Number.
- Text
- Number (Number must be a whole number with no formatting
- )
- Date (see Dates in LUNA)
- Text Box Type:
- single is just a single box
- expanding will allow you to enlarge the box to make room for lots of data
- autocomplete will complete the word based on the first few letters you type (autocomplete is based on the existing data in a collection)
- autocomplete + value list to open a list of values to select from based on existing data in collection or expose a list of values based on the letter(s) you type.
- Multivalued: allow for repeating values in a field
- Length of field: set a maximum and or minimum number of characters
- For display in LUNA Viewer: allow the data in the field to display in the LUNA Viewer, mostly this would be in the Detail View but could be in the thumbnail label, or media summary as well.
- Searchable in LUNA Viewer: allow the data in the field to be searchable in the LUNA Viewer.
- Sortable in LUNA Viewer: allow the data in the field to be sortable in the LUNA Viewer.
- MARC data field mapping (for use only when using MARC as source data).
...
| Note |
|---|
If you're not familiar with MARC records you might want to contact us for help. Please also read additional details on using MARC as source data in LUNA. |
Understanding the deletion and renaming of fields in a Schema
When you delete a field, it does not delete the underlying data (xml documents) in the LUNA Library repository. If you recreate the field with the exact same name, the data will come back. A deleted field's data will remain until the record is changed and saved.
When you create a field in LUNA, a field has two properties, the "field name" and the "display name". When you first create the field both of these are the same except the field name has underscores for spaces and is all lowercase. You can see these if you export as an XML document in the LUNA Library.
If you edit the schema, the field name always remains the same and only the display name changes. So if I start with a field called "Artist Rights" the display name is stored as "Artist Rights" and the field name is "artist_rights". If I change the field name to just "Rights" the field name remains "artist_rights"