Ticket #1 (closed enhancement: fixed)

Opened 4 years ago

Last modified 3 years ago

Relation between assay modules and assay templates

Reported by: jildau.bouwman@… Owned by: jildau.bouwman@…
Priority: major Milestone: Should have
Component: Study create/edit wizard Version:
Keywords: Cc:
Product: Operating system: Windows XP
URL: Hardware: PC

Description

In the step assays of the study capture tool one of the essential fields is the module where the data are stored. This drop-down is now empty (also not new links can be made).

Change History

  Changed 4 years ago by business@…

  • component set to Study create/edit wizard

New assays can be added via the URL /gscf/assayModule, however this is not very user friendly. An 'add new' item in the dropdown list would be helpful, with a nice user interface to add new assay modules.

  Changed 4 years ago by business@…

  • milestone set to 0.6.2

follow-up: ↓ 4   Changed 3 years ago by business@…

Actually users should normally not be able to add new assay modules. This is an 'administrator' feature, so add more... would be overkill. However, it would be nice if a help message is shown that says that the assay modules are administrated by the database administrator.
Also, this points out the broader issue of a database administration interface (database management, backup, security settings etc.)

in reply to: ↑ 3   Changed 3 years ago by business@…

See #151 for that.

  Changed 3 years ago by business@…

  • status changed from new to assigned
  • owner set to jildau.bouwman@…
  • type changed from defect to enhancement

The process of defining an assay can be streamlined a bit in terms of user experience: Right now, the user has to select the template, select the module, input the assay name, and come up with an assay identifier.

  • Maybe the assay identifier can be generated, something like <Study.code>_<Assay.name> capitalized and replace space by _?
  • It would be nice if the assay template and assay module were coupled. Probably the most logical approach would be: one module has at least 1 Assay module template, maybe more. Then in the wizard, the user first selects the target module (where will the data go?) and then after that, the default template gets set, but the user will be able to add another template if he/she wants to specify more data about the assay. Assinging ticket to Jildau to give feedback on this.

  Changed 3 years ago by business@…

  • summary changed from the module are cannot be chozen (or added) in the assay step to Relation between assay modules and assay templates

  Changed 3 years ago by business@…

  • owner changed from jildau.bouwman@… to j.a.m.wesbeek@…

The first mentioned thing (assay identifier generation) can already be implemented, assigning to Jeroen

  Changed 3 years ago by work@…

  • owner changed from j.a.m.wesbeek@… to work@…

  Changed 3 years ago by work@…

  • owner changed from work@… to business@…

Actually, this cannot be implemented as you need to know the Assay name to generate an ID. However the Assay Name and the Assay ID are in the same form so you don't know the name yet. Therefore I only put the study code in there + template name to make it a little bit eassier.

Change: r1162

Also part two of the idea goes for the whole application; not just 'assays'. But as that is pretty hard to accomplish (it's all dynamic and no relationship exists between for example -in subjects- species and template, or -in assay- template or module. So: wontfix

Assigning assayID fix back for testing...

  Changed 3 years ago by work@…

  • owner changed from business@… to business@…

  Changed 3 years ago by work@…

  • owner changed from business@… to robert@…

  Changed 3 years ago by robert@…

  • owner changed from robert@… to kees.vanbochove@…

Autogenerating the assay ID seems to be working. Assigning back to Kees in order to see whether the other parts of this ticket should be picked up.

  Changed 3 years ago by business@…

  • owner changed from kees.vanbochove@… to jildau.bouwman@…

Thanks, Jeroen, for picking up the first part and to Robert for testing. I consider this done now. I will have to discuss the assay template - module relationship with Jildau, so assigning back to her as she has also reported this issue in the first place. I will pick this up somewhere next week.

  Changed 3 years ago by s.h.sikkema@…

  • milestone changed from 0.6.2 to 0.7

  Changed 3 years ago by work@…

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

last update 2 months ago so it does not seem too important... closing issue

Note: See TracTickets for help on using tickets.