Yesterday - We have identified a bug which have created incorrect data in a certain situation .
therefore - an updated EntryClient version has been uploaded (EntryClient 2.0.9.25) today.
The change is due to a serious bug in RELATED dataforms. With single dataforms there is NO problem.
For most projects with related dataforms the situation is:
1 New observations are added with unique key fields
(say "project id"+"date of visit")
2 key values are never changed.
Then you have NO problem and your data are correct.
But if a project has:
a. related set of dataforms (main + one or more child dataforms)
b. the key contains MORE than ONE field.
c. you have edited (changed) values in one of the
key fields after entering records "above" a child form
d. child records for more than one observation have the
same value in a key field which was edited at a higher level
AND you can say YES to all of a+b+c+d there is reason to check your data. If there is doubt for a given project you are welcome to contact us by mail at "info at epidata.dk" for further advice.
The situation arose when we changed a flat file structure to a related structure. We split the flat file to four subfiles and imported the data into a related structure. As a first step gave one of three fields of the key the same value, whereas obviously the combination of three fields was unique. Following import this was correct, but after changing all 1000 records we realized the problem.
We apologize very much for the inconvenience this might incur, but do hope that you will continue to report any strange behaviour. Only by meticulous observation can we find such unfortunate bugs.
regards
Jens Lauritsen
EpiData Association, Denmark
I am out of the office until 29/08/2016.
Please contact Tracey McCole on 071 9852900 if you require further
assistance, otherwise I will attend to your email when I return
Note: This is an automated response to your message "EpiData-list Digest,
Vol 152, Issue 2" sent on 17/08/2016 18:00:19.
This is the only notification you will receive while this person is away.
***************************************************************************
"Tá an fhaisnéis sa ríomhphost seo (ceangaltáin san áireamh) faoi rún. Baineann sé leis an té ar seoladh chuige amháin agus tá sé ar intinn go bhfaighfidh siadsan amháin é agus gurb iadsan amháin a dhéanfaidh breithniú air. Más rud é nach tusa an duine ar leis é, tá cosc iomlán ar aon fhaisnéis atá ann, a úsáid, a chraobhscaoileadh, a scaipeadh, a nochtadh, a fhoilsiú, ná a chóipeáil . Seains gurb iad tuairimí pearsanta an údar atá san ríomhphost agus nach tuairimí FSS iad.
Má fuair tú an ríomhphost seo trí dhearmad, bheadh muid buíoch dá gcuirfeá in iúil don.Deasc Seirbhísí ECT ar an nguthán ag +353 71 9820555 nó ar an ríomhphost chuig ICT.Helpdesk(a)hse.ie agus ansin glan an ríomhphost seo ded' chóras."
***************************************************************************
"Information in this email (including attachments) is confidential. It is intended for receipt and consideration only by the intended recipient.If you are not an addressee or intended recipient, any use, dissemination,distribution, disclosure, publication or copying of information contained in this email is strictly prohibited..Opinions expressed in this email may be personal to the author and are not necessarily the opinions of the HSE.
If this email has been received by you in error we would be grateful if you could immediately notify the ICT Service Desk by telephone at +353 71 9820555 or by email to ICT.Helpdesk(a)hse.ie and thereafter delete this e-mail from your system"
***************************************************************************
Hello. I'm using EpiData 3.1 on windows 7 to enter data into a set of
RELATEd .rec files:
HNPforms.rec (these are visits to households; data about the building)
Adults.rec (data about the adults living in the household)
Children.rec (data about the children living in the households)
Each visit to a household has a unique ID number, and that number is
propagated to a field in each adult's and child's record. There can
be multiple visits to each household, so an indicator of initial visit
versus revisit is included in HNPforms.rec and is propagated to the
records for the adults and children living in that household.
Using EpiData Analysis, is there a way to "connect" the child records
and the adult records to their own household records, for purposes of
analysis? Merging on the unique ID number, so to speak.
Thanks.
--Chris
About a month ago users experienced unexpected problems with the most
recently uploaded public version. The problems were basically very grave
and would not allow various aspects of core functionality, e.g. working
with value labels.
Due to the documented problems we have now implemented a new test
principle for EpiData Manager and EntryClient, which will be followed
before public release. The tests are structured in a spreadsheet format
and performed by local staff here in Denmark (public health students).
Based on the tests performed we have found un-disclosed errors, which is
a "proof of concept" of the idea to pre-test thoroughly before public
release. In contrast to relying on unstructured testing.
Early next week we will therefore release new versions for production
use and also the spreadsheet, which documents what we do test before
release.
For coming releases I therefore suggest that users assist in the
testing. You may then receive pre-release copies of the software, such
that the overall testing can be thorough. Recent experience has shown
that some combinations of operating system versions and types (32/64bit)
etc have given problems that we have no possibility of neither catching
or solving without the help of some of you.
In short therefore: be prepared to download new production versions of
EntryClient and Manager next week.
Regards
Jens Lauritsen
EpiData Association