Ticket #192 (closed enhancement: fixed)

Opened 3 years ago

Last modified 3 years ago

Add Datatype user-extendible String list (as in ontology)

Reported by: e.vansomeren@… Owned by: robert@…
Priority: major Milestone: Must have
Component: General Version:
Keywords: Cc:
Product: Operating system:
URL: Hardware:

Description

For many fields, the data manager wants the user to try to select from a short list, but provide the user the possibility to extend this list if his/her desired option is not there. For example, a list of institute names. You don't want to be completely free to avoid all kinds of different names for the same institute, but want to allow the user to add a new institute.

Change History

Changed 3 years ago by work@…

  • owner set to business@…
  • status changed from new to assigned
  • milestone set to 0.7

Eugene, I understand your issue but experience shows that if you allow such things, you end up with garbage, duplicate entries etcetera. So if such functionality should be available, it should be implemented in such a way that those issues do not arrise. It actually sounds simpler than it is...

Setting this to milestone 7, we need to brainstorm about this request...

Changed 3 years ago by robert@…

  • priority changed from minor to major
  • owner changed from business@… to robert@…
  • milestone changed from Should have to Must have

This enhancement is also requested by the metagenomics group. Increasing the priority. I'll build in this field.

Changed 3 years ago by robert@…

  • owner changed from robert@… to work@…

Jeroen, I've implemented this template field in gdt, but I think it causes some database changes. The table 'subject_template_extendible_string_list_fields' (and the same for study, assay etc.) are created locally, after the change. Do you think it will cause problems?

Changed 3 years ago by work@…

  • owner changed from work@… to robert@…

it appears to be working properly on ci, so I assume grails has updated everything as expected?

Changed 3 years ago by robert@…

  • status changed from assigned to closed
  • resolution set to fixed

I guess so too. The creation of database tables is handled by grails correctly.

Note: See TracTickets for help on using tickets.