Metadata with multiple options not saved without preset

[solth]

Metadata defined by a key with multiple options in the ruleset (resulting in a pulldown/selectOne menu) is can only be saved in the metadata editor if a preset is configured.

Metadata configured the following way can be saved:

<key id="metadata1">
	<label>Works</label>
	<option value="value1"/>
	<option value="value2"/>
	<option value="value3"/>
	<preset>value1</preset>
</key>

Metadata configured the following way cannot be saved:

<key id="metadata2">
	<label>Broken</label>
	<option value="value1"/>
	<option value="value2"/>
	<option value="value3"/>
</key>

[matthias-ronge]

I have now tested this with the ruleset_test.xml, which you made available to me yesterday, using the metadata LegalNoteAndTermsOfUse, which doesn’t declare a <preset>, on division "Volume".

• with minOccurs="1" and maxOccurs="1", multiline="false" is saved is not saved
• with maxOccurs="1", multiline="false" is saved
• with minOccurs="1", multiline="false" is saved
• unbounded, multiline="false" is saved
• unbounded, multiline="false" with alwaysShowing="true" is saved
• unbounded, multiline="true" with alwaysShowing="true" (list of checkboxes) is not saved → Always showing multi-select metadata is not saved  #4068
• with maxOccurs="1", multiline="true" (list of radio buttons) is not saved → Multi-line single-select metadata is not saved #4069
• with maxOccurs="1", without any <setting> (drop-down select) is saved
• with minOccurs="1" and maxOccurs="1", without any <setting> (drop-down select) is saved.

Summary: Pull-down seems to work for me, but there are saving issues here.

[matthias-ronge]

Just to be sure, I also tested with "metadata2" as you indicated above (no <label> elements), but it also saves.

[matthias-ronge]

Today I encounter the situation that with build of 37d56a0 the constellation minOccurs="1" and maxOccurs="1" is not saved, neither with explicit multiline="false" nor without <setting> at all.