RE: EpiData-list Digest, Vol 123, Issue 5
Dear Sir IN relation to the old epidata entry software, As most databases are relational could you clarify what is meant by "in situations with relational databases ."
Dr Thambu David S Professor and Head Medicine Unit 2 Christian Medical College, Vellore 632004, India
________________________________________ From: epidata-list-bounces@lists.umanitoba.ca [epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request@lists.umanitoba.ca [epidata-list-request@lists.umanitoba.ca] Sent: Tuesday, January 28, 2014 11:31 PM To: epidata-list@lists.umanitoba.ca Subject: EpiData-list Digest, Vol 123, Issue 5
Send EpiData-list mailing list submissions to epidata-list@lists.umanitoba.ca
To subscribe or unsubscribe via the World Wide Web, visit http://lists.umanitoba.ca/mailman/listinfo/epidata-list or, via email, send a message with subject or body 'help' to epidata-list-request@lists.umanitoba.ca
You can reach the person managing the list at epidata-list-owner@lists.umanitoba.ca
When replying, please edit your Subject line so it is more specific than "Re: Contents of EpiData-list digest..."
EpiData-list mailing list ___________________________________
Today's Topics:
1. New public release of Manager and EntryClient (version 1.4.4) (epidata-list@lists.umanitoba.ca)
----------------------------------------------------------------------
Message: 1 Date: Mon, 27 Jan 2014 22:43:53 +0100 From: epidata-list@lists.umanitoba.ca Subject: [EpiData-list] New public release of Manager and EntryClient (version 1.4.4) To: EpiData-list@lists.umanitoba.ca Message-ID: 52E6D319.8010408@epidata.dk Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Dear all
The only problems reported with the test version last week was some visual problems on Mac computers when browsing data in Manager and EntryClient.
We have therefore today released the next version 1.4.4 of Manager and EntryClient for general production use. Please find the updated versions on: http://www.epidata.dk/download.php
We suggest that all users update to this version, since all reported issues (to the best of our knowledge) have been solved, including the problematic "start up" issue on MAC, and program crash when the user removed fields involved in Jumps, Compare values or Calculations.
The download page is now suggesting users to get the epx based Manager and EntryClient and only use the old "Classic Epidata Entry" in situations with relational databases and need for extended calculations during entry.
In short the enhanced functionality since 1.4.2 are:
Common to Manager and EntryClient: * Introduces a new .lock file principle, indicating that a given file is already in use. * Prevents loading project files created with "future" (experimental) versions of the programs. * On Linux/Windows a new and improved dataset viewer. Much faster on very large datasets. * Show progressbar when loading/importing files.
Manager: * New "Data Validation Report", for a list of possible errors in current dataset. * New field tools: Clear Data and Recode Data. * Added EPX as export (save partial or whole project as a new epx) * Improved support for DDI export, including compliance with Danish Data Archive specifications (See http://samfund.dda.dk/dda/default-en.asp) * Improved Stata import and SPSS export. * Improved Study Information * Improvements to text-reports including Study Information. * Export report documenting export to any format.
EntryClient: * Valuelabel and/or range information is show as note upon entry to a field. * New path for placing backup files, rather than same place as original file * Use of "+" on Date or Time field automatically inserts current date or time.
Development will now continue with aspects of relational databases in the preparation of securing user access and logging. More on that later.
Should any problem arise do not hesitate to report these on this list. A report from a user last week of dysfunction of this list could not be replicated. Most likely it could be due to someone sending posts with html formatted mail instead of text .
Torsten Christiansen and Jens Lauritsen EpiData Association, Denmark
------------------------------
________________________________________ EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
End of EpiData-list Digest, Vol 123, Issue 5 ********************************************
Regarding relational databases:
The reality at this point in development is that if you have multiple files in a given project (that is relational databases), then you can do the following: EpiData Classic (3.1): set up a complete relational system, which secures the levels and compliance with rules for 1:1 or 1:many in subfiles.
One example of this is the well known house-person-visit example or the extended example found in a village survey in Burkina Faso. You will find other examples here: http://epidata.dk/examples.php:
EpiData Manager & EntryClient: Each file and subfile will be a separate project (EPX), which you define and enter data into without the appropriate control of 1:1 or 1:many relation. The status for a given project can be followed by reports which will document this . It is the "Count by Id" part of the documentation menu. This "Count by ID" allows the user to select as many fields as desired for identification of a given respondent.
During the coming months the "true" relational setup will be developed. Until then one can do as a user reported last week to have several EntryClients open at the same time and then "manually" change from one project file to the other by selecting on the screen the appropriate project. In each of the projects involved you would define the fields identifying a given observation would be defined as a key, e.g. "id + date" of visit or "id + reason + date of visit + time of day".
EpiData Analysis As well epx and (rec+chk) files can be used for merging relational structures. Although at this point epx files with encryption (password protected) cannot be read into Analysis.
Regarding extended checks Pre-release versions of a scripting language similar to the CHK file contents is now only at the level of "in-house" testing, but this will also come in the test versions later. But assumingly only after relational databases can be setup.
I hope this explains the intentions and limitations.
regards
Jens Lauritsen EpiData Association
Den 30. jan. 2014, epidata-list@lists.umanitoba.ca skrev:
Dear Sir IN relation to the old epidata entry software, As most databases are relational could you clarify what is meant by "in situations with relational databases ."
Dr Thambu David S Professor and Head Medicine Unit 2 Christian Medical College, Vellore 632004, India
"my quote:"
The download page is now suggesting users to get the epx based Manager and EntryClient and only use the old "Classic Epidata Entry" in situations with relational databases and need for extended calculations during entry.
Thanks Jens:
This explanation is very helpful for me. I use relational databases in most of the cases of complex studies. I'm actually needing it right now. And with this explanation I would plan a project starting with the EpiData Classic and maybe when relational and extended checks were implemented in the newer version, I will switch to it importing the database.
Regards,
El 30/01/14 04:57, epidata-list@lists.umanitoba.ca escribió:
Regarding relational databases:
The reality at this point in development is that if you have multiple files in a given project (that is relational databases), then you can do the following: EpiData Classic (3.1): set up a complete relational system, which secures the levels and compliance with rules for 1:1 or 1:many in subfiles.
One example of this is the well known house-person-visit example or the extended example found in a village survey in Burkina Faso. You will find other examples here: http://epidata.dk/examples.php:
EpiData Manager & EntryClient: Each file and subfile will be a separate project (EPX), which you define and enter data into without the appropriate control of 1:1 or 1:many relation. The status for a given project can be followed by reports which will document this . It is the "Count by Id" part of the documentation menu. This "Count by ID" allows the user to select as many fields as desired for identification of a given respondent.
During the coming months the "true" relational setup will be developed. Until then one can do as a user reported last week to have several EntryClients open at the same time and then "manually" change from one project file to the other by selecting on the screen the appropriate project. In each of the projects involved you would define the fields identifying a given observation would be defined as a key, e.g. "id + date" of visit or "id + reason + date of visit + time of day".
EpiData Analysis As well epx and (rec+chk) files can be used for merging relational structures. Although at this point epx files with encryption (password protected) cannot be read into Analysis.
Regarding extended checks Pre-release versions of a scripting language similar to the CHK file contents is now only at the level of "in-house" testing, but this will also come in the test versions later. But assumingly only after relational databases can be setup.
I hope this explains the intentions and limitations.
regards
Jens Lauritsen EpiData Association
Den 30. jan. 2014, epidata-list@lists.umanitoba.ca skrev:
Dear Sir IN relation to the old epidata entry software, As most databases are relational could you clarify what is meant by "in situations with relational databases ."
Dr Thambu David S Professor and Head Medicine Unit 2 Christian Medical College, Vellore 632004, India
"my quote:"
The download page is now suggesting users to get the epx based Manager and EntryClient and only use the old "Classic Epidata Entry" in situations with relational databases and need for extended calculations during entry.
EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
participants (1)
-
epidata-list＠lists.umanitoba.ca