Moved from https://issues.library.cornell.edu/browse/NIHVIVO-3561, created 1/21/12
Could be triggered from the declaration of the datatype associated with a data property, except that we may want to specify short vs long entry (text input boxes vs. tinyMCE text areas) for data properties that are untyped or of type xsd:string
Probably important for the credibility of DataStaR editing.
Brian Caruso added a comment - 27/Jan/12 2:23 PM
Might a better approach to the problem of wanting different forms (text input boxes vs. tinyMCE text areas) be to specify a custom form on the data properties? Data properties that you want a text input box for would get one custom form and ones that needed tincyMCE could get a different custom form.
This prevents the problem where you get an ontology from someone and you want to use a short text input box but they have set the data property to xsd:string. You don't what to change their ontology, you want a custom form.
Huda Khan added a comment - 16/Feb/12 12:35 PM
Depends on particular implementation mechanism so more time may be required if additional ontology work is required.
Jon Corson-Rikert added a comment - 19/Jun/12 9:08 PM
Defer to 1.6 due to lack of time and Huda's need to focus on DataStar – implement in that context if it would prove more urgent there.