Bind fields to concepts

Bind once, and the field is included in every standard. Binding is the real work. Export and validation take only a few clicks after that.

Open Data model › Metadata standards (status 9). Under Standards and Processes the overview shows one card each with its progress, such as 22 of 22 mapped. The card Minimaldatensatz (MDS) 1.2 (minimum data set) is a good place to start, because it is the smallest set that makes sense.
Click the card. The list shows the profile’s concepts in groups, and for each concept its level (Mandatory, Recommended …), Comes from and In the export. At the top the progress reads n of m mapped; the filter Open shows only the ones still missing. That is the right order for the first round.

Map one concept after another. Clicking a concept opens its dialog. There, under Comes from, choose a source with Add source:

Source	When
Field	The usual case. Link an existing field or create a new one
JSON field	When an entry repeats with an addition (a title per language, a dimension per reference)
Events of the object	For the concept Ereignis (event), optionally limited to certain event types
Files of the object	For the concept Mediendatei (media file)
Fixed value	For information that is the same for every object

If Moliri finds a field with the same or a similar name, the list shows a Suggestion, and the filter With suggestion shows exactly those concepts. If a project is selected under Fill level from, the filter Gaps shows the mapped concepts that do not have a value on every object there. Accept binds it.

Check the result. In the dialog, In the export shows what the mapping produces for an object, and with Show XML also as XML. If you choose a project under Fill level from above the list, you see real values instead of the sample content.

The concept “Objekttitel / Benennung” (object title / name) from the Minimaldatensatz in its dialog: at the top “In the export” with the sample values, below it “Comes from” with the sources Objekttitel, Alternativtitel and the JSON field Titel (mehrsprachig), at the bottom the standards and processes in which the concept applies.

Fixed values first

Everything that is the same for every object is the quickest to deal with.

Concept	Typical fixed value
Verwahrende Einrichtung (holding institution)	Name of the museum
ID verwahrende Einrichtung (holding institution ID)	ISIL or GND identifier
Sprache des Datensatzes (record language)	`de`
Datensatzart (record type)	The matching term from the LIDO terminology
Nutzungsrechte Metadaten (metadata rights)	The licence you chose, such as CC0
Datensatzerstellende Einrichtung (record source)	Name of the museum

That covers a large share of the mandatory nodes without touching a single field.

Have missing fields created

Where a concept has no field yet, Moliri can create one. The button Map n open … at the top of the list opens the dialog Map open concepts with all concepts not yet mapped. For each concept you can choose:

Choice	Effect
Create new (or Create n fields)	One or more fields are created and mapped
Link existing	A suggested existing field is mapped
Default mapping	The supplied default is applied
An existing field (by name)	This field is mapped
Skip	Nothing

With Set all (Create new, Existing only, None) you decide for all concepts at once. The line below tells you beforehand how many concepts will be mapped and how many fields created. Create & bind carries it out. The main field of a mandatory concept receives the condition not empty straight away.

If an existing field without a condition is mapped to a mandatory concept, Moliri does not change it on its own. Instead the list marks the concept with a red exclamation mark, and the detail column shows a note with Set condition. One click sets not empty on the field; the field’s other conditions remain. If several fields are mapped, you choose one of them in a small menu; the condition on one of them is enough. If you want a condition of your own, open the field with the link next to it, such as “Open Datensatzsprache”.

Separate fields or JSON field

Where a concept allows both, Moliri asks:

Variant	Property
Separate fields	One field per value. Can be searched, sorted and grouped
JSON field	Rows or sections within one field. Not reachable by the search, equivalent for the export

If you search, sort or group by the value, the values belong in separate fields. Otherwise the JSON field is enough. For the LIDO import only the separate-field mapping counts, see Set up the LIDO import .

Authority data where possible

Nodes whose value kind is an authority record (object type, material, technique, subject) should be bound to an authority data field , not to a text field.

A text field produces a label without an identifier. The record stays valid but is weak in substance: portals cannot link it with others. The authority data field outputs the term with its identifier.

Create a layout from a standard or process

In an open standard, Create layout creates a layout with the mapped fields, structured by the concepts’ groups. It is marked as Default for new projects and therefore appears in every new project. For the Minimaldatensatz this is described in its own area, Minimaldatensatz .

Besides the export standards there are Processes, compiled sets of concepts for procedures such as Objektzugang (object entry), Katalogisierung (cataloguing) or Leihannahme (incoming loan). They appear in the overview as cards of their own; what they cover is described in the Collections management area. For a process, Install brings the layout with it: the preview names the layout template that results from the mapped fields, and the concepts that have no field yet, with Create missing fields beside them. If a layout with the process’s name already exists, no new one is added. Who installed what and when is recorded under Log.

Processes create fields, link types and a layout. How the work is done is up to your museum.

Check before the first export

On a project’s Check tab, Completeness for standard exports shows how many objects meet the mandatory information of a profile and which concept is missing where. The export itself checks again before the file is created. Both are described in Export LIDO .