Ticket #356 (assigned defect)

Opened 3 years ago

Last modified 3 years ago

Add extra options for ONTOLOGY template fields to template field description

Reported by: business@… Owned by: business@…
Priority: major Milestone: Must have
Component: Unknown Version: 0.6.3
Keywords: Cc:
Product: Operating system:
URL: Hardware:

Description

Right now, it's not possible to choose a value for an ONTOLOGY field that is not an ontology term. In some cases, this is a real user limitation, e.g. in a compound field, you should be able to choose 'placebo' but that will never become a term in the ontology of course.
Same with 'species' where you would like to be able to choose 'unknown' or 'none'.
We can use listEntries (being used for STRINGLIST already) to store these items in the template definition.

Change History

Changed 3 years ago by work@…

related to #353

Changed 3 years ago by business@…

  • milestone set to 0.7.0

Changed 3 years ago by work@…

we discussed this again, but we agreed to create an overview of all different options to have them discussed / decided upon later

Changed 3 years ago by work@…

see #353 for more information, moving to 0.7.1

Changed 3 years ago by work@…

  • milestone changed from 0.7.0 to 0.7.1

Changed 3 years ago by business@…

  • owner changed from robert@… to business@…
  • status changed from new to assigned

Changed 3 years ago by business@…

  • milestone changed from 0.7.1 to Must have

see also #192 and  https://trac.nbic.nl/grails-plugins/changeset/217, the 'Extendable stringlist' could also be an option in some cases.

Note: See TracTickets for help on using tickets.