DataONEorg / collections-portals-schemas

Enabling project and data paper views via MetacatUI, Metacat, and EML
Apache License 2.0
3 stars 3 forks source link

In the new schema, check whether any maxOccurs or minOccurs should be changed #94

Closed robyngit closed 3 years ago

robyngit commented 3 years ago

Decide whether we are requiring elements that could be optional, or whether we are restricting elements to one instance where it could be useful to allow multiple.

robyngit commented 3 years ago

Below is a summary of which elements are required, and which are limited to one in the proposed 1.1.0 Collection and Portal schemas. I think that the elements that we've decided to restrict or make required all make sense, except in the case of <choice> elements that occur within the custom search <choiceFilter> elements:


Required elements

The following elements are required within the element it occurs

Collections

Portals

Given these required elements, the most minimal portal needs only a label and a definition with one filter:

<portal>
    <label>MyMinimalPortal</label>
    <definition>
        <filter>
            <field>text</field>
            <value>arctic</value>
        </filter>
    </definition>
</portal>

Elements restricted to one

The following elements are limited to one of each within the element it occurs

Collections

Portals

robyngit commented 3 years ago

By the same logic as in the proposed change above, I think it would also make sense to allow multiple <trueValue> and <falseValue> elements in UIToggleFilterType. Setting the toggle to true (or to false) could add multiple search values to the query.