[VIVO-1756] - Make data property richtext editor option selectable from UI

[gneissone]

JIRA Issue: [VIVO-1756]

• Other Relevant Links (Mailing list discussion, related pull requests, etc.)
  Follows up on comments in [VIVO-1528] Select an editor for input fields based on annotation #76

What does this pull request do?

Makes the rich text editor for data properties selectable via the UI

What's new?

Adds a drop down menu to the data property settings form. Selecting 'rich text' from this menu results in a triple being added for the data property in the form http://vitro.mannlib.cornell.edu/ns/vitro/0.7#editing "HTML" .

How should this be tested?

Add a new data property or edit an existing one.

Add the bottom of the form, there should be a new option for enabling the rich text editor.

Select rich text and confirm that the value 'HTML' is populated

Add or edit an instance of the property, confirm it uses the rich text editor.

Edit the property settings again to switch the editor back to the default. Confirm the rich text editor is no longer used.

Additional Notes:

'HTML' is currently the only value that has any effect, and it is hard coded into both the default form (https://github.com/vivo-project/Vitro/blob/master/webapp/src/main/webapp/templates/freemarker/edit/forms/defaultDataPropertyForm.ftl#L34) and the proposed DatapropRetryController.java here. Perhaps there's a more eloquent way to handle this but given the current situation it seemed sufficient.

Interested parties

@VIVO-project/vivo-committers

[awoods]

@gneissone : Is there value in additionally enabling a "textarea" option for larger textual content, per #76 (review) ?

[awoods]

Works as advertised. 👍

[gneissone]

@gneissone : Is there value in additionally enabling a "textarea" option for larger textual content, per #76 (review) ?

Yes, I think so. Do you have a suggestion for what value of the editing property should result in a bigger plaintext editor? Since it also requires changes to defaultDataPropertyForm.ftl I think it should be in a followup PR.

[awoods]

@gneissone : Is there value in additionally enabling a "textarea" option for larger textual content, per #76 (review) ?

Yes, I think so. Do you have a suggestion for what value of the editing property should result in a bigger plaintext editor? Since it also requires changes to defaultDataPropertyForm.ftl I think it should be in a followup PR.

A follow-up ticket/PR makes sense. I would defer to the ontologists for the term.

[awoods]

Follow-on ticket, per: #138 (comment)
https://jira.lyrasis.org/browse/VIVO-1757

[roflinn]

Approved