Replies: 3 comments
-
In general, @BartChris is right: the behaviour is inconsistent and the order opportunities of structural elements and metadata should be the same. I can only comment from the users perspective, but i cannot assess, if the behaviour can be adjusted. |
Beta Was this translation helpful? Give feedback.
-
The idea was: The order should follow the order of the If the Example: List of languages:
Rule: <permit key="language" unspecified="unrestricted">
<permit value="ger"/>
<permit value="eng"/>
<permit value="lat"/>
</permit> Sort order of options showing:
You can override this ruleset-internal sorting by specifying the "alphabetical" sorting property for the selected rule set in the rule set configuration of the project settings. In this case, everything is sorted alphabetically. Any behavior that differs from these two cases should be considered a bug. |
Beta Was this translation helpful? Give feedback.
-
I would then consider this a bug and created an issue #4967 |
Beta Was this translation helpful? Give feedback.
-
We stumbled over the fact that for structural elements the decision was made, that their order can be defined via the ruleset or in alphabetical order. (#3413 (comment) , #4190 )
In the case of metadata a different decision was made insofar as the metadata elements are always sorted alphabetically. ( #4664 ).
This behaviour appears inconsistent. There are scenarios were the ruleset allows the addition of many metadata elements but only some of the elements are used in most cases. Other elements are used only in special cases. Right now there is no way to define in the ruleset that the most used metadata elements should appear on top since the ruleset ordering is not considered in the UI. It would be preferable if the setting for structural elements does also apply for metadata.
@matthias-ronge @solth @andre-hohmann - could you maybe reconsider this behaviour?
Beta Was this translation helpful? Give feedback.
All reactions