Correct! The value Coded values should be the concept ids of the true/false or yes/no concepts.
Wyclif On Mon, Mar 12, 2012 at 11:35 AM, Darius Jazayeri <[email protected]>wrote: > Wyclif, so to clarify, if Christian looks in his database directly, obs > whose concepts are boolean should have valueNumeric is null and valueCoded > is not null, right? > > -Darius > > On Mon, Mar 12, 2012 at 7:18 AM, Wyclif Luyima <[email protected]> wrote: > >> The idea was to allow questions with boolean responses to be handled as >> value coded under the hood but allowing only 2 concept answers which are >> the values you specify for the global properties true/ false concepts, this >> design has the benefit in that it becomes easy to convert an obs to have >> value coded answers to allow addition of extra responses like 'Not Sure' to >> a question that previously required boolean answers. >> >> Wyclif >> >> >> On Mon, Mar 12, 2012 at 3:23 AM, Christian Neumann <[email protected]>wrote: >> >>> Thanks for the clarificatieon Wyclif. >>> >>> But I still need your help as I feel I don't get it. If there is no need >>> to change Obs, then what is the change doing at all? >>> >>> As far as I understand we moved away from Boolean Obs stored as 0 and 1 >>> numeric values (I have still some of them in the DB) to coded lists. These >>> global properties now point to the concepts that are used for true/false >>> with the potential to include more (e.g. unknown) in future. >>> >>> Seems like I'm missing something, but I don't know what and where. >>> >>> christian >>> >>> On Mar 8, 2012, at 5:56 PM, Wyclif Luyima wrote: >>> >>> See inline responses: >>> >>> What values should the global properties have; simply 0 and 1? >>> The values should be concept ids for the concepts that have names as >>> true/false or yes/no in your concept dictionary. >>> >>> Is there the need to change concepts with the datatype Boolean? >>> No. >>> >>> And if yes, do I need to change all Obs? >>> >>> Wyclif >>> >>> On Thu, Mar 8, 2012 at 10:15 AM, Christian Neumann <[email protected]>wrote: >>> >>>> Thanks Wyclif, >>>> >>>> A few followup questions: >>>> >>>> What values should the global properties have; simply 0 and 1? >>>> >>>> Is there the need to change concepts with the datatype Boolean? >>>> >>>> And if yes, do I need to change all Obs? >>>> >>>> christian >>>> >>>> On Mar 8, 2012, at 4:57 PM, Wyclif Luyima wrote: >>>> >>>> Hi Christian, >>>> >>>> Those global properties were existent prior to 1.7, may be they were >>>> removed or edited before you even upgraded, you can add them back if they >>>> don't exist or else check their values and set them accordingly. >>>> >>>> Wyclif >>>> >>>> On Thu, Mar 8, 2012 at 5:15 AM, Christian Neumann <[email protected]>wrote: >>>> >>>>> Hi, >>>>> >>>>> I've noticed a bunch of warnings in the Tomcat logs after upgrading to >>>>> OpenMRS 1.7. Seems like the handling of concepts has changed (as it is >>>>> noted in the changelog). >>>>> >>>>> WARN - ConceptServiceImpl.setBooleanConcepts(1507) |2012-03-08 >>>>> 10:38:00,576| Concept ids for boolean concepts should be numbers >>>>> >>>>> However it seems that something went wrong during my update process. >>>>> Doesn't look like concepts were migrated or the global_properties >>>>> concept.true and concept.false were created. >>>>> >>>>> Is there a best process to resolve this manually? I assume that I need >>>>> to modify the tables global_property, obs, and concept somehow. >>>>> >>>>> Thanks, >>>>> christian >>>>> _________________________________________ >>>>> >>>>> To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail >>>>> to [email protected] with "SIGNOFF openmrs-implement-l" in >>>>> the body (not the subject) of your e-mail. >>>>> >>>>> [mailto:[email protected] >>>>> ?body=SIGNOFF%20openmrs-implement-l] >>>>> >>>> >>>> ------------------------------ >>>> Click here to >>>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from >>>> OpenMRS Implementers' mailing list >>>> >>>> >>>> ------------------------------ >>>> Click here to >>>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from >>>> OpenMRS Implementers' mailing list >>> >>> >>> ------------------------------ >>> Click here to >>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from >>> OpenMRS Implementers' mailing list >>> >>> >>> ------------------------------ >>> Click here to >>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from >>> OpenMRS Implementers' mailing list >>> >> >> ------------------------------ >> Click here to >> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from >> OpenMRS Implementers' mailing list >> > > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-implement-l>from > OpenMRS Implementers' mailing list _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
