The plugin uses two variables res_extras_eov_restricted and res_extras_keyword_restricted
#res_extras Without changing the CIOOS SOLR schema there are a few extra fields that allow placing custom fields into the database using dynamic fields
<dynamicField name="*_date" type="date" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="extras_*" type="text" indexed="true" stored="true" multiValued="false"/>
<dynamicField name="res_extras_*" type="text" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="vocab_*" type="string" indexed="true" stored="true" multiValued="true"/>
<dynamicField name="*" type="string" indexed="true" stored="false"/>
The wildcard field is not stored and *date and extras* are not multivalued which leaves res_extras_ and vocab_ as options
res_extras was chosen as it was the choice for the extra variables as it made sense to treat them as extra resource fields However, it is also a text field instead of string and gets tokenized, unlike the original eov and keyword fields
#Schema changes Right now the changes to cioos_siooc_schema.json involve copying the fields for 'keywords' and 'eov' and making another field for each.
These fields are the same as their originals except for the title and field name, as well as not being marked as required.
If any changes are made to either original field (say, more EOVs get added for example), the changes should be copied to the restricted version too
#Update 2022-06-29 As per Matt's recommendations the restricted fields will be moved to extras_
This means that the function to view available and hidden datasets through the facets will need to be changed since text is tokenized, unlike string In the future, giving restricted_eov and keywords their own field may be useful