Testing: Enable "URIs" and "Items" custom vocabularies

[jimsafley]

The enable-custom-vocab-uris-and-items branch enables "URIs" and "Items" vocabs from the CustomVocab plugin. Before, collecting forms only recognized "Terms" vocabs, ignoring all others.

Before testing, make sure you have a "URIs" and a "Items" custom vocab. Then, add/edit a collecting form and click "Add prompt". Select "Item property" prompt type, "Custom vocab" input type, and select a custom vocab that's a list of URIs. Click "Add changes" and save the form. Do the same for a custom vocab that's a list of items.

Add the form to a page and go to the public form. Make sure the select menus contain the correct custom vocabs, that the form submits, and that the URI and item saved to the collected item.

[aviannamiller]

Things look good in terms of custom vocabs for URIs and Items adding properly to collecting forms, select menus containing the expected vocab lists, and the correct information depositing to records upon user submission. The only issue I see is a styling one relevant to all themes except for Freedom and Lively. It seems that option titles that exceed ~95 characters are cut off, which is not the issue, but the longer titles are creating an excessive overflow for selects. This is especially true when a custom vocab can source from Items, which may very well have long titles over that threshold. Here's an instance of the overflow that I'm seeing across themes, with the property on the Date prompt pulling from an item set of resources with pretty lengthy titles:

Also, a question – I see in the edit form of a given collected item that the submitted metadata is available in text or URI fields, depending on what's appropriate. Is it possible / would there be a point to the fields instead taking on the dropdown menu typical of when a custom vocab is used within a data type? I could imagine a user wishing to adjust collected item metadata under the same parameters of the custom vocab.

[jimsafley]

The only issue I see is a styling one relevant to all themes except for Freedom and Lively. It seems that option titles that exceed ~95 characters are cut off, which is not the issue, but the longer titles are creating an excessive overflow for selects. This is especially true when a custom vocab can source from Items, which may very well have long titles over that threshold.

@kimisgold Would you look at this?

Is it possible / would there be a point to the fields instead taking on the dropdown menu typical of when a custom vocab is used within a data type?

I just pushed a change that should preserve the CustomVocab data types in collected items. Try it out.

[aviannamiller]

I just pushed a change that should preserve the CustomVocab data types in collected items. Try it out.

That works perfectly, thanks!

[kimisgold]

The selects should now remain constrained within the form container.

[aviannamiller]

Selects look much better on all themes except for Cozy, full page width:

and Thanks, Roy:

This is across Chrome, Firefox, Safari