sample to questionnaire assign verification and validation for Lime relevance
Bug #1527158 reported by
Alex
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| queXS |
In Progress
|
Wishlist
|
Alex | ||
Bug Description
When relevance/condition with { SAMPLE: ... } record used in Lime tool:
To prevent mistakes with sample fields and Lime questionnaire run with improper relevance,
it's required to verify and validate that sample field required for Lime survey is present in sample being assigned to questionnaire with this Lime tool and equals to one mentioned in Lime relevance.
alert error info msg with column name and refuse to assign sample to questionnaire if not present/match.
| summary: |
- sample import verification and validation for Lime relevance + sample to questionnaire assign verification and validation for Lime + relevance |
Revision history for this message
| Adam Zammit (adamzammit) wrote | #1 |
| Changed in quexs: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Alex (ddrmoscow) wrote | #2 |
| Changed in quexs: | |
| assignee: | nobody → Alex (ddrmoscow) |
| status: | New → In Progress |
To post a comment you must log in.
I can see the benefit in this. I guess we would have to scan all the fields in the Limesurvey questionnaire for a SAMPLE condition and then if it exists confirm that it appears in the sample when assigning a sample.
Hopefully administrators will test their questionnaire to establish this in the mean time - but I can see how a typo in a sample column could have a big effect if SAMPLE conditions used for relevance.