EpiData-list June 2015

epidata-list@lists.umanitoba.ca

1 participants
12 discussions

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 13

by EpiData development and support

Thanks, that was the case. The chk file was not residing in the same folder as the rec file. martin On 27 June 2015 at 17:00, <epidata-list-request(a)lists.umanitoba.ca> wrote: > 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. Version 3.1 used to keep the value labels in documents|view > data (EpiData development and support) > 2. Re: Version 3.1 used to keep the value labels in > documents|view data (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 26 Jun 2015 17:19:46 +0000 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Version 3.1 used to keep the value labels in > documents|view data > Message-ID: > <CAMUv7ZSFxFB0rP==gK55_pTa6K3gfiygH=KpHpmpY= > L0tj5hag(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > I am using Epidata 3.1,When I open the data in Document | View data, from > Edit, I see the the data are checked to "Show labels", but the labels are > not shown. That means when I export to say, Stata, I don't have the > labels. I remember this used to work. Is there anything I am doing wrong? > > > regards > > -- > Martin Alhassan Adjuik > Statistician > Cell : +233 (0) 243714441 > madjuik(a)gmail.com > > > ------------------------------ > > Message: 2 > Date: Sat, 27 Jun 2015 12:32:41 +0200 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> > Subject: Re: [EpiData-list] Version 3.1 used to keep the value labels > in documents|view data > Message-ID: <7C0F38CC-BD35-4DD9-9D98-64BEA7F6B5E5(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8 > > Most likely your chk file is not residing in the same folder as your rec > file or has a different name. > Regards jens Lauritsen > Epidata association > > On 26. jun. 2015 19.19.46 CEST, EpiData development and support < > epidata-list(a)lists.umanitoba.ca> wrote: > >I am using Epidata 3.1,When I open the data in Document | View data, > >from > >Edit, I see the the data are checked to "Show labels", but the labels > >are > >not shown. That means when I export to say, Stata, I don't have the > >labels. I remember this used to work. Is there anything I am doing > >wrong? > > > > > >regards > > > >-- > >Martin Alhassan Adjuik > >Statistician > >Cell : +233 (0) 243714441 > >madjuik(a)gmail.com > >_______________________________________________ > >EpiData-list mailing list > >EpiData-list(a)lists.umanitoba.ca > >http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 139, Issue 13 > ********************************************* > -- Martin Alhassan Adjuik Statistician Cell : +233 (0) 243714441 madjuik(a)gmail.com

8 years, 9 months

Re: [EpiData-list] Importing data to Epidata (v.2.0.5.51)

by EpiData development and support

Thank you very much Jamie, your help was indeed very helpful. I believe it also makes sense to convert yes/no/NA cells to have a numerical value e.g. 1,2,3 ? Is there a way to change the field type afterwards other than touching the XML code and if so, is it wise/dangerous? Pekka Jamie wrote: > > I have found that import from the clipboard works well if the Excel data > are prepared for the import. Here is what I do. > > In Excel, format the columns they way you want them to appear in EpiData > (text columns, numbers with set decimal places, dates as YYYY/MM/DD is > best). > I usually then format the columns to fit the data > No spaces in your column names - these should be valid EpiData field names > for consistency > Make sure that the first and last rows of data are complete; I often put > dummy data in these and then delete the records in EpiData. I believe the > main thing here is to have valid data (not empty cells) in the last column > of data for the first and/or last rows. > Ideally, have no blank cells - put missing values in. This is probably not > necessary, as EpiData handles empty cells well. > > > You may find that fields are not the length that you want. You can safely > edit these fields to change the size. Text, number and data fields should > all come through with the correct type. > > I don?t know of any simple way to convert data for an Excel column to > coded values with ?value labels?. Unless your data set is massive, there is > no real penalty to keeping the values in full. > > When I had to automate repeated conversion of messy Excel data to EpiData, > I made a new sheet within the Excel file and used formulas to put copies of > the original data into the new sheet, with all of the cleaning. For > example, we had some inconsistencies in coding province, so I used a lookup > table to convert the original values (Ontario, Ont, ON) to be consistent > (ON). This is one way to do your data coding, by the way, but you still > cannot automate getting the value labels into EpiData. In my case, the data > set was small and existing data might change, so I just kept importing the > whole thing. You can also just convert the new data, import to a new > EpiData project and then append this to your complete project. > > You will have problems with import from the clipboard if you have commas > in your text fields. In my testing, the import fails without an error > message. > > EpiData is very fussy about importing data, as it should be, since it does > such a good job of maintaining the integrity of data when you use it for > data entry. Import of csv data does work, but you have to be very sure to > have clean data and to not have stray delimiters in your data. In any case, > your data should be in good shape since it originates in a database (what > database?? Maybe there is another more direct way to get into EpiData) > --? > Jamie > > Pekka wrote: > What I want to do is to import a spreadsheet with field labels and data to > Epidata. The spreasheet contains field names on the top row and records on > the following rows. Once I have imported the initial data, I would like to > ammend the records with additional fields, i.e. have the initial > spreadsheet data as the seed data in records. I think this is a very normal > practice to do, but I have run into several difficulties: > > 1. I have tried to import the spreadsheet with "File/Import file" but I > don't seem to get it working. I have turned the spreasheet from Excel to > CSV, but the dialogue box that opens doesn't recognize data. I made a > workaround by copying a part of the spreadsheet and used "File/Import from > clipboard" and that did work. The downside is that you have to do it part > by part, and the fundamental problem is why it doesn't work in the first > place. Is Epidata Manager very picky as to what field separators are used > in CSV? I have tried changing field separators but with no luck. Clipboard > seems to be the only workaround, but even still I have to do it in parts. > (I am using Ubuntu and the latest Linux 64-bit version) > > 2. With the copy-paste method I noticed that Epidata was smartly able to > interpret some fields with the right type (e.g. date, but not all > date-fields, but I believe this is the issue of my spreadsheet), but not > all. I have not discovered a way to change the field type afterwards, is it > at all possible? The only hack I figured out was to manually change the > field type in XML code directly, but I would be very hesitant to do it. If > I touch XML code directly, will that mess up everything, or is it the > simple fix to the problem? > > 3. Value-labels: My spreadsheet contains no value labels, obviously. It has > for example field "Country of origin" and the value is string "Nepal". Is > there a way for me to easily convert strings of text into value labels as a > part of the import process? String values are consistent (the spreadsheet > is an output file from a database), so I should imagine it would be > possible do so. > > 4. Provided I get questions 1,2 and 3 adequately resolved, I should be fine > with the initial data import. But what do I do if I want to later import > additional records from the same spreadsheet structure to my Epidata > project? Is this something that Append is supposed to do? There I have the > same issue with the spreadsheet compatibility: The CSV file does not open > in a recognisable way, hence I haven't been able to play around and test it > either. > > > >

8 years, 9 months

Version 3.1 used to keep the value labels in documents|view data

by EpiData development and support

I am using Epidata 3.1,When I open the data in Document | View data, from Edit, I see the the data are checked to "Show labels", but the labels are not shown. That means when I export to say, Stata, I don't have the labels. I remember this used to work. Is there anything I am doing wrong? regards -- Martin Alhassan Adjuik Statistician Cell : +233 (0) 243714441 madjuik(a)gmail.com

8 years, 9 months

transfer questionnaire created in Mac version (2) to same version in PC?

by EpiData development and support

Dear friends apologies for this is a very simple question - may be I missed it in the documentation I would like to create a questionnaire on my Mac then take it to the field where there will be PCs. Will this work? Also using the data entry tool for PCs with a questionnaire created in the MAC programme? grateful for your advice Hilary

8 years, 9 months

Importing data to Epidata (v.2.0.5.51)

by EpiData development and support

Hello, I am a newcomer to Epidata, so I apologize if my questions are not sophisticated. I am exploring the latest version and it is fantastic with many ingenious features, great work and great programming philosophy, thank you! As the version is new, I understand that the documentation is not yet fully developed, and hence if someone can help me with these questions, I think they can be of use to many others as well. What I want to do is to import a spreadsheet with field labels and data to Epidata. The spreasheet contains field names on the top row and records on the following rows. Once I have imported the initial data, I would like to ammend the records with additional fields, i.e. have the initial spreadsheet data as the seed data in records. I think this is a very normal practice to do, but I have run into several difficulties: 1. I have tried to import the spreadsheet with "File/Import file" but I don't seem to get it working. I have turned the spreasheet from Excel to CSV, but the dialogue box that opens doesn't recognize data. I made a workaround by copying a part of the spreadsheet and used "File/Import from clipboard" and that did work. The downside is that you have to do it part by part, and the fundamental problem is why it doesn't work in the first place. Is Epidata Manager very picky as to what field separators are used in CSV? I have tried changing field separators but with no luck. Clipboard seems to be the only workaround, but even still I have to do it in parts. (I am using Ubuntu and the latest Linux 64-bit version) 2. With the copy-paste method I noticed that Epidata was smartly able to interpret some fields with the right type (e.g. date, but not all date-fields, but I believe this is the issue of my spreadsheet), but not all. I have not discovered a way to change the field type afterwards, is it at all possible? The only hack I figured out was to manually change the field type in XML code directly, but I would be very hesitant to do it. If I touch XML code directly, will that mess up everything, or is it the simple fix to the problem? 3. Value-labels: My spreadsheet contains no value labels, obviously. It has for example field "Country of origin" and the value is string "Nepal". Is there a way for me to easily convert strings of text into value labels as a part of the import process? String values are consistent (the spreadsheet is an output file from a database), so I should imagine it would be possible do so. 4. Provided I get questions 1,2 and 3 adequately resolved, I should be fine with the initial data import. But what do I do if I want to later import additional records from the same spreadsheet structure to my Epidata project? Is this something that Append is supposed to do? There I have the same issue with the spreadsheet compatibility: The CSV file does not open in a recognisable way, hence I haven't been able to play around and test it either. Help is much appreciated, thank you! Pekka

8 years, 10 months

EpiData Project: Current development focus and Strategy over next 1-2 years

by EpiData development and support

Development these months is focused on getting towards compliance with the legal regulations on access to data containing health information. In short this concerns: - definition of users and what they can do (change structure, modify users, export data ....) - logging of which users did what The total development list contains as well: - inclusion of scripting during Entry. Could be used for user defined functions such as summation af scales or reading of data from external lookup software). - rewriting of Analysis based on the new xml file format. And extension with more specific functions for routine reporting. A number of International Standards describe requirements of user control and logging in detail (piles of descriptions). This is difficult legal and technical documentation. For those using ISO standards this referes to ISO 27001 and 27002. A formal certification with an external auditing body would be a huge investment and NOT possible within the economic constrains of the EpiData project. Just as an example rewriting from one standard to another would cost 5000 Euro. Which is better spent on development. But implementation of the principles is required to secure continued use in some countries and some situations. E.g. for research in pharmaceutical products. More news will follow on this development, which is also dependent on continued donation of funding for the development of the EpiData software products. The remaining development is expected to take about 2-2½ years. Software will be released as open-source, when specific modules are ready with all decided functionality. The reason for working in this way is that before principles are settled it is a highly fragile situation. There is however continued correspondance and exchange of components with other users applying the Free-Pascal solution in Lazarus, which is the basis of EntryClient and Manager programming. Regards Jens Lauritsen EpiData Association.

8 years, 10 months

bug fix release for Manager

by EpiData development and support

Just before the weekend a bug-fix release has been made available for general download from http://www.epidata.dk The changes in Manager are always available as a short list on this link: <http://epidata.dk/epidatamanager.changelog.txt> as well as in EntryClient on this link: <http://epidata.dk/epidataentryclient.changelog.txt> For the most recent Manager this is: 2.0.5.51: * Fixed bug in double entry validation, that could lead to A/V due to incorrect order of adding selectiong of key fields * Fixed bug where 32-bit Windows could drop the .epx/.epz extension with "Save As" on existing projects. * Fixed bug where double clicking a locked Keyfield, would cause A/V * ExportForm: changed filename edit to regular edit, to avoid confusion regarding paths. A/V indicates Access Violation. Stata 13/14 export will be implemented with next release of Manager, but Stata 13/14 import was implemented already in 2.0.4.43 regards Jens Lauritsen and Torsten Bonde Christiansen EpiData Association

8 years, 10 months

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 6

by EpiData development and support

Dear Hans, Thanks for your concern. I'm on a 64 bit system, however the 64 bit software version won't work at all on my computer. I looked through the archives and saw that other people with 64 bit systems were complaining about this, and finally and successfully installed the 32 bit software version on their machine. Best regards, Michael van Straten -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Thursday, June 18, 2015 8:00 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 139, 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. Re: EpiData-list Digest, Vol 139, Issue 3 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Wed, 17 Jun 2015 20:06:40 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 3 Message-ID: <5581B730.3040308(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Michael: Do you indeed have a 32-bit architecture on your Win 8 machine? I am asking to exclude a mismatch between software version and PC architecture. Regards, Hans On 17-Jun-15 16:50, EpiData development and support wrote: > Dear Torsten, > > Sorry for my late reply. > > 1. Version: EpiData Manager > Program Version: 2.0.4.43 r1156 > Core version: 2.0.0.0 r1161 > FPC Version: 2.6.4 > Platform: i386-Win32 -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 139, Issue 6 ********************************************

8 years, 10 months

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 8

by EpiData development and support

Dear Hans, Thanks for the clarification. I guess then that it's back to square 1 for me.. Best regards, Michael van Straten -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Sunday, June 21, 2015 8:00 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 139, 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. Re: EpiData-list Digest, Vol 139, Issue 6 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Sat, 20 Jun 2015 20:03:29 +0200 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 6 Message-ID: <5585AAF1.1040308(a)tbrieder.org> Content-Type: text/plain; charset=utf-8; format=flowed Dear Michael: I'm afraid then, that this mismatch is the cause of the problem. In some systems, a 32-bit version of EpiData software appears to work (superficially), but then one runs into a problem sooner or later. Unfortunately, a 64-bit PC requires the 64-bit software. We need thus to figure out why 64-bit software does not work on your 64-bit PC. It is not a Win 8 problem per se (we tried it and it works). Unfortunately, I run out of suggestions on what to check next... Regards, Hans On 19-Jun-15 11:43, EpiData development and support wrote: > Dear Hans, > > Thanks for your concern. I'm on a 64 bit system, however the 64 bit > software version won't work at all on my computer. I looked through > the archives and saw that other people with 64 bit systems were > complaining about this, and finally and successfully installed the 32 > bit software version on their machine. > > Best regards, > > Michael van Straten -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Skype: hansleonhardrieder Web: http://www.tbrieder.org ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 139, Issue 8 ********************************************

8 years, 10 months

Re: [EpiData-list] EpiData-list Digest, Vol 139, Issue 3

by EpiData development and support

Dear Torsten, Sorry for my late reply. 1. Version: EpiData Manager Program Version: 2.0.4.43 r1156 Core version: 2.0.0.0 r1161 FPC Version: 2.6.4 Platform: i386-Win32 2. Yes. There was an error message but the program closed down so fast I could just see it flash for a moment, with no chance of reading it. The program just closes down. Disappears. Nothing is saved and I am returned to my desktop. 3. I open the program, start a new project, open a new data form and add a string variable. In the field properties box, the moment I try to add a value label by pressing on "new", the program shuts down without saving anything. Scenario 2: I open a new data form, add a string variable without a value label, save the project and close the program. Then I open the project and try to add a value label to the existing string variable: the same thing happens. Program close down. This happens also when I try to add a value label via "Project Details" >> "Value labels". I hope this helps understand the problem. TIA, Michael van Straten -----Original Message----- From: epidata-list-bounces(a)lists.umanitoba.ca [mailto:epidata-list-bounces@lists.umanitoba.ca] On Behalf Of epidata-list-request(a)lists.umanitoba.ca Sent: Friday, June 12, 2015 8:00 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 139, Issue 3 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. Re: EpiData Manager closing down on Windows 8.1 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Fri, 12 Jun 2015 11:17: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: Re: [EpiData-list] EpiData Manager closing down on Windows 8.1 Message-ID: <557AA39D.6090105(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Hi Michael. I have tried to make a few simple projects in Windows 8.1 here and I am not able to reproduce what you describe. Can you please elaborate on the following: 1: Version of EpiData Manager you have tested with (use "Help" -> "Copy Version Info...") 2: Was there any errormessage 3: Please make a more detailed description of the steps you took for this happen Regards, Torsten B. Christiansen. EpiData. On 2015-06-08 12:57, EpiData development and support wrote: > Dear users, > > I have installed EpiData Manager on a machine working on Windows 8.1 > 64 bit. I used the latest versions available: 2.0.4.43 r1156 > > 1. At first I used the 64 bit version but could not open or save projects: this led to the program shutting down. In the archives I saw other users experienced similar problems. > 2. I then uninstalled the above and installed the 32 bit version (Platform i386-Win32). This version seemed to be working well, until I tried to set value labels: when I do this, either by using the "Field properties" box or by trying to access through "Project Details" >> "Value labels", the program shuts down. I am just able to see that some error notice appears but the program shuts down so fast I cannot read it. > > Any suggestions? > > Thanks in advance, > > Michael???? ?????? ??????? ??? > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 139, Issue 3 ********************************************

8 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

EpiData-list June 2015