June 2016 - EpiData-list - University of Manitoba Mailing Lists

Jumps in Epidata Entry
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

Dear list, I have two questions regarding Jumps in EpiData Entry. 1) I want to jump to variable v10 if de score for v8 is 1 to 7. Of course this works: v8 RANGE 1 9 COMMENT LEGAL USE oplcat JUMPS 1 v10 2 v10 3 v10 4 v10 5 v10 6 v10 7 v10 END MUSTENTER END Is a shorter syntax possible and if so, how? 2) Is it possible to make a jump defination that depends on the value entered in a previous question? For example: After entering the value for variable v5 I want to jump to v8 if the answer on question v3=1. Kind Regards, Pieter van Groenestijn The Netherlands

2 3

fill fields from COMMENT LEGAL file
by epidata-list＠lists.umanitoba.ca 15 Jul '26

15 Jul '26

I'm studying the copydata example to learn how to extract several variables from a file identified in a COMMENT LEGAL statement. In A3.chk, the statement "TYPE COMMENT atransfer" appears. What is atransfer? I don't see where it has been defined as a variable and I don't find it as a system variable. Further, the program seems to be parsing the string in atransfer according to the position of punctuation. Where is the format of this string defined? Perhaps to be a bit more explicit: I have file with a list of CHWs: District, Village, CHW name and a survey conducted by the CHWs. As the data is entered for the survey, I'd like to present pick lists to facilitate entry. The data is quite strictly hierarchical: Villages occur within Districts, an CHWs live in villages. Thank you,

2 3

The old version Epidata - Control Function
by EpiData development and support 01 Jul '16

01 Jul '16

Dear Epidata Developers I use Epidata in a long time. There was the control function that allowed for a lot. There was a * .chk file in which you could write a basic useful language. I am trying to design an input mask, but now I seek the equivalent of this function, I can not find. Has it been removed? If there is how to use it? Best regards_______________________________________Konan Diby JP, MD, MPH Attaché de Recherche Labo. Biostatistique & Informatique Médicale UFR Sciences Médicale, Univ. F. Houphouët-Boigny 22 BP 1041 Abidjan 22, Côte d'Ivoire Tel./Fax: (+225) 22 401 403 GSM: (+225) 05 994 326 / 07 250 561 skype's: dibykonanjp

1 1

Re: [EpiData-list] EpiData-list Digest, Vol 150, Issue 8
by EpiData development and support 30 Jun '16

30 Jun '16

Dear Jens and T.Christiansen, Many many thanks, from me and a grateful user community best regards Thambu ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca <epidata-list-bounces(a)lists.umanitoba.ca> on behalf of epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Sent: Thursday, June 30, 2016 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 150, Issue 8 Send EpiData-list mailing list submissions to epidata-list(a)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(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)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. The old version Epidata - Control Function (EpiData development and support) 2. New public release EpiData Manager v 2.0.10.59 (EpiData development and support) 3. New experimental release of EpiData Manager and EpiData EntryClient (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Thu, 30 Jun 2016 10:01:36 +0000 (UTC) From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: Epidata <epidata-list(a)lists.umanitoba.ca>, "epidata-list-request(a)lists.umanitoba.ca" <epidata-list-request(a)lists.umanitoba.ca> Subject: [EpiData-list] The old version Epidata - Control Function Message-ID: <9169254.6772797.1467280896435.JavaMail.yahoo(a)mail.yahoo.com> Content-Type: text/plain; charset=UTF-8 Dear Epidata Developers I use Epidata in a long time. There was the control function that allowed for a lot. There was a * .chk file in which you could write a basic useful language. I am trying to design an input mask, but now I seek the equivalent of this function, I can not find. Has it been removed? If there is how to use it? Best regards_______________________________________Konan Diby JP, MD, MPH Attach? de Recherche Labo. Biostatistique & Informatique M?dicale UFR Sciences M?dicale, Univ. F. Houphou?t-Boigny 22 BP 1041 Abidjan 22, C?te d'Ivoire Tel./Fax: (+225) 22 401 403 GSM: (+225) 05 994 326 / 07 250 561 skype's: dibykonanjp ------------------------------ Message: 2 Date: Thu, 30 Jun 2016 14:12:42 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: "EpiData development and support" <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] New public release EpiData Manager v 2.0.10.59 Message-ID: <1467288762402.55581.73100@webmail3> Content-Type: text/plain; charset=UTF-8 Dear all The following changes have implemented in the Manager version 2.0.10.59, which replaces ALL previous versions: 2.0.10.59: * Fixed bug where rightclicking the designer, while editing a dataform caption would CAUSE a program crash. * Removed SAS Export as announced earlier (SPSS/PSPP is still there) * Visual change: All must-enter fields are now painted red, as in EntryClient. All changes with version can be seen here: <http://epidata.dk/epidatamanager.changelog.txt> For those who experienced problems with running 64bit versions on Windows and changed to Windows 32bit, please try the new replaced version. Please acknowledge the hard work done to accomplish this when possible. The planning and design is done by T.Christiansen and I in collaboration. We discuss with key users and I have secured funding from those mentioned on the funding page of the web - more on this aspect later. All specific internal design of the software routines and implementation of principles in the programming is done by T.Christiansen. Warm regards Jens Lauritsen EpiData Association Denmark > > ------------------------------ Message: 3 Date: Thu, 30 Jun 2016 16:32:06 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: "EpiData development and support" <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] New experimental release of EpiData Manager and EpiData EntryClient Message-ID: <1467297126440.119863.7904@webmail6> Content-Type: text/plain; charset=UTF-8 Dear all A short while ago I announced the public release of version 2.0 for general production use. Production versions are available from <http://epidata.dk/download.php> During development we prepare test and experimental versions. These are made with new features and therefore the epx files are of a different structure. This is why we urge You NOT to use them for real projects, but only for testing. From this version and unwards test and experimental versions will only be supplied in the form of downloadable zipped/tar archives, which you MUST extract before use. (see pps) The purpose of open testing is to allow users to comment and aid in the development direction. As you know this is a small project in budget compared to large software systems, such that we are depending on the help of users in the tests. A new experimental version has just been uploaded to the page : http://epidata.dk/testing.php <http://epidata.dk/download.php> I do hope that users will challenge the new features, which in short are: 1 User logging and control: Many places now require logging of entry and access to data (e.g. who entered which data on which days for GCP monitoring). Please read the document on how to define extended user access. The document is not a teaching guide for setup of user access principles in general, but a description of the specific implementation we have made. The document explains how user rights are defined in a project and how you can separate entryrights from password changing rights or other aspects of extended data control. See: <http://epidata.dk/php/downloadc.php?file=ExtendedAccess.pdf> and should be included with the software. 2 E-mail after entry of data: As part of the project properties you may define, that the epz backup file can be mailed to a given mail. The software does NOT send the message but gives the standard mail and name of the file to your own email client. This can be useful if you have many remote entry places and a central analysis office. In such cases ALWAYS add encrypted status to your project. 3 Content in statusbar: In particular when you have long or related dataforms it can be instructive to know values of fields in the Statusbar. This is now a feature of the dataform. Known previously as "type statusbar" in EpiData Classic. We will provide more information within the next week, but after that next development sequence starts in August. Such that comments and test results should be sent to us at the latest around August 1st. At that point we will plan in more detail for the autumn. As always - do report to this list of your comments and results. Al types of comments are welcomed including as well enthusiastic and critical comments on design choices on our part. Warm regards again Jens Lauritsen EpiData Association Denmark PS - as mentioned previously: Please acknowledge the hard work done to accomplish this when possible. The planning and design is done by T.Christiansen and I in collaboration. We discuss with key users and I have secured funding from those mentioned on the funding page of the web - more on this aspect later. All specific internal design of the software routines and implementation of principles in the programming is done by T.Christiansen. pps: If for some reason you need an installation version we can inform you how to get that - at least for the current test - it is a safety measure not to deliver installation versions, since a number of users previously installed the test version over the public release version - and had severe problems of project data that could no longer be used (without efforts that only few know of). Do also remember that we have NO WAY of regaining data if you forget a password. ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 150, Issue 8 ********************************************

1 0

New experimental release of EpiData Manager and EpiData EntryClient
by EpiData development and support 30 Jun '16

30 Jun '16

Dear all A short while ago I announced the public release of version 2.0 for general production use. Production versions are available from <http://epidata.dk/download.php> During development we prepare test and experimental versions. These are made with new features and therefore the epx files are of a different structure. This is why we urge You NOT to use them for real projects, but only for testing. From this version and unwards test and experimental versions will only be supplied in the form of downloadable zipped/tar archives, which you MUST extract before use. (see pps) The purpose of open testing is to allow users to comment and aid in the development direction. As you know this is a small project in budget compared to large software systems, such that we are depending on the help of users in the tests. A new experimental version has just been uploaded to the page : http://epidata.dk/testing.php <http://epidata.dk/download.php> I do hope that users will challenge the new features, which in short are: 1 User logging and control: Many places now require logging of entry and access to data (e.g. who entered which data on which days for GCP monitoring). Please read the document on how to define extended user access. The document is not a teaching guide for setup of user access principles in general, but a description of the specific implementation we have made. The document explains how user rights are defined in a project and how you can separate entryrights from password changing rights or other aspects of extended data control. See: <http://epidata.dk/php/downloadc.php?file=ExtendedAccess.pdf> and should be included with the software. 2 E-mail after entry of data: As part of the project properties you may define, that the epz backup file can be mailed to a given mail. The software does NOT send the message but gives the standard mail and name of the file to your own email client. This can be useful if you have many remote entry places and a central analysis office. In such cases ALWAYS add encrypted status to your project. 3 Content in statusbar: In particular when you have long or related dataforms it can be instructive to know values of fields in the Statusbar. This is now a feature of the dataform. Known previously as "type statusbar" in EpiData Classic. We will provide more information within the next week, but after that next development sequence starts in August. Such that comments and test results should be sent to us at the latest around August 1st. At that point we will plan in more detail for the autumn. As always - do report to this list of your comments and results. Al types of comments are welcomed including as well enthusiastic and critical comments on design choices on our part. Warm regards again Jens Lauritsen EpiData Association Denmark PS - as mentioned previously: Please acknowledge the hard work done to accomplish this when possible. The planning and design is done by T.Christiansen and I in collaboration. We discuss with key users and I have secured funding from those mentioned on the funding page of the web - more on this aspect later. All specific internal design of the software routines and implementation of principles in the programming is done by T.Christiansen. pps: If for some reason you need an installation version we can inform you how to get that - at least for the current test - it is a safety measure not to deliver installation versions, since a number of users previously installed the test version over the public release version - and had severe problems of project data that could no longer be used (without efforts that only few know of). Do also remember that we have NO WAY of regaining data if you forget a password.

1 0

New public release EpiData Manager v 2.0.10.59
by EpiData development and support 30 Jun '16

30 Jun '16

Dear all The following changes have implemented in the Manager version 2.0.10.59, which replaces ALL previous versions: 2.0.10.59: * Fixed bug where rightclicking the designer, while editing a dataform caption would CAUSE a program crash. * Removed SAS Export as announced earlier (SPSS/PSPP is still there) * Visual change: All must-enter fields are now painted red, as in EntryClient. All changes with version can be seen here: <http://epidata.dk/epidatamanager.changelog.txt> For those who experienced problems with running 64bit versions on Windows and changed to Windows 32bit, please try the new replaced version. Please acknowledge the hard work done to accomplish this when possible. The planning and design is done by T.Christiansen and I in collaboration. We discuss with key users and I have secured funding from those mentioned on the funding page of the web - more on this aspect later. All specific internal design of the software routines and implementation of principles in the programming is done by T.Christiansen. Warm regards Jens Lauritsen EpiData Association Denmark > >

1 0

Re: [EpiData-list] EpiData-list Digest, Vol 150, Issue 6
by EpiData development and support 22 Jun '16

22 Jun '16

Dear Jens Many of us use PSPP (free, legal and excellent) which requires export to SPSS sav style. This is because we cannot afford SPSS or STATA in many parts of dev world I know its more work that i cannot help with but if at all posible could the export to SPSS style be continued? sincerely Thambu ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca <epidata-list-bounces(a)lists.umanitoba.ca> on behalf of epidata-list-request(a)lists.umanitoba.ca <epidata-list-request(a)lists.umanitoba.ca> Sent: Tuesday, June 21, 2016 10:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 150, Issue 6 Send EpiData-list mailing list submissions to epidata-list(a)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(a)lists.umanitoba.ca You can reach the person managing the list at epidata-list-owner(a)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. Status of EpiData Development and a few questions (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 Jun 2016 14:05:17 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: "EpiData development and support" <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Status of EpiData Development and a few questions Message-ID: <1466510717716.8748.10152@webmail9> Content-Type: text/plain; charset=UTF-8 During this week our nights will again be longer and days shorter as a signal of change of season. Just now in Denmark sun is up at 04:39 and down at 22:05, further north even more bright hours. It is customary to make a status before summer vacation and the status for EpiData Development and maintenance is in short: Analysis: The first pre-prototype of a rewritten Analysis is the main development task just now. Core functionality of internal routines is in focus (e.g. how should the software read a command, how to add options etc). There is nothing to test for users until some months from now, but it is progressing as planned. The aim of the rewriting will be to recreate current EpiData Analysis commands, but with a slight modernisation and unification of approach and commands - more on that later. The EpiData List A few weeks back the list was not available, but this should have been fixed again, such that new list users can add themselves. First time you send a mail to the list we have to authorize it to secure against spam. Remember that files should be small and formatted as text (not html). EntryClient and Manager: The public versions are working efficiently with very few bugs, which we attempt to remove quickly. Recently errors in export of dates to Stata version 14 was fixed. There has been an issue when opening files with the 64 bit windows version, but this can be remedied by using the 32 bit version. Development versions of Manager and EntryClient: 1 Logging of user actions and control is in an in-house test. (e.g. someone can define dataforms and others only enter data). An issue of speed and actual control of what to add to logging is under consideration. 2 Configuration of Statusbar with contents of variables is working 3 Ability of automatic sending of backup file via email after entry is in test. The plan is to issue a new test version with this functionality within 2 weeks. I expect that we will no longer support export to SPSS and SAS since the maintenance of these two is cumbersome. The reason is that Stata format is fully documented and therefore easy to work with and R also reads Stata files. Therefore apart from the epx format - we will most likely restrict import and export with variable and value labels to Stata (dta) and without labels to csv (separated). Some users might find that restrictive, but in view of the overall size of the EpiData project priority must be given to secure sustainability. Such choices could lead to discussions on this list - which is highly welcomed. warm regards to all Jens Lauritsen Coordinator and Initiator of the Epidata Project ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 150, Issue 6 ********************************************

1 0

Status of EpiData Development and a few questions
by EpiData development and support 21 Jun '16

21 Jun '16

During this week our nights will again be longer and days shorter as a signal of change of season. Just now in Denmark sun is up at 04:39 and down at 22:05, further north even more bright hours. It is customary to make a status before summer vacation and the status for EpiData Development and maintenance is in short: Analysis: The first pre-prototype of a rewritten Analysis is the main development task just now. Core functionality of internal routines is in focus (e.g. how should the software read a command, how to add options etc). There is nothing to test for users until some months from now, but it is progressing as planned. The aim of the rewriting will be to recreate current EpiData Analysis commands, but with a slight modernisation and unification of approach and commands - more on that later. The EpiData List A few weeks back the list was not available, but this should have been fixed again, such that new list users can add themselves. First time you send a mail to the list we have to authorize it to secure against spam. Remember that files should be small and formatted as text (not html). EntryClient and Manager: The public versions are working efficiently with very few bugs, which we attempt to remove quickly. Recently errors in export of dates to Stata version 14 was fixed. There has been an issue when opening files with the 64 bit windows version, but this can be remedied by using the 32 bit version. Development versions of Manager and EntryClient: 1 Logging of user actions and control is in an in-house test. (e.g. someone can define dataforms and others only enter data). An issue of speed and actual control of what to add to logging is under consideration. 2 Configuration of Statusbar with contents of variables is working 3 Ability of automatic sending of backup file via email after entry is in test. The plan is to issue a new test version with this functionality within 2 weeks. I expect that we will no longer support export to SPSS and SAS since the maintenance of these two is cumbersome. The reason is that Stata format is fully documented and therefore easy to work with and R also reads Stata files. Therefore apart from the epx format - we will most likely restrict import and export with variable and value labels to Stata (dta) and without labels to csv (separated). Some users might find that restrictive, but in view of the overall size of the EpiData project priority must be given to secure sustainability. Such choices could lead to discussions on this list - which is highly welcomed. warm regards to all Jens Lauritsen Coordinator and Initiator of the Epidata Project

1 1

"hybrid" COMMENT LEGAL or RANGE
by EpiData development and support 17 Jun '16

17 Jun '16

Can I define in my chk file legal values like this, (for a field describing the number of housing units in a building): RANGE 1 7 COMMENT LEGAL 1 2 3 4 5 6 7 "more than 6" Thanks. --Chris Ryan

1 1

AUTO: CN=Louise Cullen/O=NWHB is out of the office. (returning 04/07/2016)
by EpiData development and support 16 Jun '16

16 Jun '16

I am out of the office until 04/07/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 150, Issue 4" sent on 16/06/2016 18:00:25. 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" ***************************************************************************

1 0