I have a newly created study (continuous study), with a handful of datasets. I just imported a few hundred records across a couple datasets. I was expecting study.patients to be auto-populated w/ the new IDs. Is this not how it works anymore? Do i need to specify something in the study config to tell LK to maintain the patient list for me?
Thanks,
Ben |
| |
| jeckels responded: |
2016-05-04 17:01 |
Hi Ben,
I also thought that the server would automatically maintain that table, but if you look at AbsoluteDateVisitManager.updateParticipantVisitTable(), you can see that it no-ops. It's been that way since at least 2010.
Thanks,
Josh |
| |
| Ben Bimber responded: |
2016-05-05 08:15 |
This applies to both study.participant (one row per participant) and participantVisit (a different table)? |
| |
| jeckels responded: |
2016-05-09 14:53 |
Hi Ben,
My mistake - I misinterpreted the sequence of calls when I read the code earlier.
I just tried to repro and trunk and it worked as expected. I created a new continuous study, added a dataset, inserted some data, and checked study.participant and had rows there.
I'm assuming that you've set Patient as the subject identifier, correct? Do you have a different set of repro steps?
Thanks,
Josh |
| |
| Ben Bimber responded: |
2016-05-16 10:28 |
Hi josh,
I'm using 16.1. I created a continuous study, set 'optr' as the subject column name ('patient' and 'patients' are the nouns). I created datasets, and then inserted rows into many of them. these rows have non-null values for OPTR, which they always need to have since they are datasets. however, the patient table is empty. any other debugging thoughts? |
| |
| Ben Bimber responded: |
2016-07-07 10:51 |
I'm still seeing this pretty consistently, both on our server and locally. One thing to note is that I'm bulk importing data using query controller's actions, as opposed to the study controller. i dont think this should matter, but thought i'd bring it up. |
| |
| jeckels responded: |
2016-07-11 16:27 |
|
| |
|
|