- EpiData-list - University of Manitoba Mailing Lists

mac os x data double entry issue
by epidata-list＠lists.umanitoba.ca 19 Jun '13

19 Jun '13

Hi, I plan to use Epidata for a clinical study. A problem / bug came up when I tried to do double entry of data. To prepare double entry, Epidata saves a copy of the project. But it is for me not possible to save this file. I get an error message "Error saving file! - this file filename.double.epx could not be saved" I have tried to rename the file and change destination, but still not working. Anybody else with this problem? I´m using Epidata project tools v1.4.1.1 (manager and entry client) OS X v10.8.4 on a MacBook Pro Best regards / Venlig hilsen Kresten Rickers PhD Student, MD Orthopedic Research Lab. University Hospital of Aarhus http://www.orf-aarhus.dk<http://www.orf-aarhus.dk/> +45 78 46 15 11 rickers(a)ki.au.dk<mailto:rickers@ki.au.dk>

1 0

fw: hey
by epidata-list＠lists.umanitoba.ca 14 Jun '13

14 Jun '13

http://www.lamimosavacanze.it/xgm.html __ louise knight

1 0

How to count the number of missing values in an observation/record/row
by epidata-list＠lists.umanitoba.ca 13 Jun '13

13 Jun '13

Dear sirs/madams, My name is Anh. I am a student from Vietnam. I would like to calculate the number of missing values/entered values in a record. I had a look at Epidata manual but I could not find any relevant instructions. Could you please help me with this problem? Thank you so much, Anh Dang ........................................................ Details of my problem: My checklist contains 5 variables. Each variable is given a score (0,1,2), but in some records, a few variables are left blank because they are not relevant. The final score is calculated by dividing the sum of score of each variable (don't take the missing into account) by the 'total number of entered variables'. id var1 var2 var3 var4 var5 1 2 1 1 0 final score = (2+1+1+0)/4 ( I use the command 'ignoremissing' to get the sum) 2 2 2 2 1 1 final score = (2+2+2+1+1)/5 3 1 1 final score=(1+1)/2

1 1

Bug on import in Manager (public release 1.4.1.0)
by epidata-list＠lists.umanitoba.ca 13 Jun '13

13 Jun '13

We have found a bug in the most recent public release version of EpiData Manager 1.4.1.0. With the bug import of epx and other files into a project with "renaming" of value label sets gives an error. This will be fixed and a new version uploaded within short time. (days) This is only relevant for the situation where you add files depending on naming of value label sets. If other bugs have been identified please report, such that we can fix these as well. regards Jens Lauritsen EpiData Association

1 0

Bug fix release Manager and EntryClient version 1.4.1.0
by epidata-list＠lists.umanitoba.ca 05 Jun '13

05 Jun '13

Version 1.4.1 of Manager og EntryClient has been uploaded for generel production usage from http://www.epidata.dk Changes are as follows: EntryClient: When F9 or "show value labels" is active the first value label is selected as the default. Manager: Validate duplicate issues with creation of verification file and selection of fields for comparison has been fixed. Default name of value label sets is now valuelabel_<fieldname> Reports and file lists now indicate cycle number (automatic version coding) Minor other text adaptations Export to DDI format now validates correctly against DDI-3.1 as can be verified on: http://snd.gu.se/sv/ddi/validator Just paste the created XML into the field "DDI xml" and hit "validate" All other aspects of function are the same as in the first 1.4.0 release last week. Regards Jens Lauritsen and Torsten Christiansen EpiData Association Denmark

1 0

Report any bug you find in public releases, please
by epidata-list＠lists.umanitoba.ca 03 Jun '13

03 Jun '13

The public version 1.4 of EpiData Manager and EntryClient, plus the minor adaptive release of EpiData Analysis were released on May 24. As noted in a previous mail there are some issues in relation to validate duplicate, DDI export and a few other issues. Since the number of public releases should be kept low I have decided to wait a few more days before uploading an updated bug-fix version of Manager and EntryClient. I am aware of some details reported in relation to Analysis and lifetable analysis. These will be taken care of soon. If you have found any issue not mentioned on this list, then please discuss as soon as possible, such that we can fix these issues - if needed. Meanwhile I can disclose, that the next expermental version for testing will contain a scripting facility, such that scripts can be run before and/or after entry in a given field. This will replace the current "calculate" tab in properties for fields. Examplescripts are: if V1 = 1 then goto V2 else if V1 = 2 then goto V3; V4 = V1 + V2 + V3 ; V5 = V1*V2*V3; regards Jens Lauritsen EpiData Association

1 0

Re: EpiData-list Digest, Vol 115, Issue 9
by epidata-list＠lists.umanitoba.ca 29 May '13

29 May '13

Thank you! When can I expect to be able to compare values in second file with what was already entered in the first file directly at entry? Is there an older version that allows this? Best, Natalie On Wed, May 29, 2013 at 10:00 AM, <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. Issue with double entry verification > (epidata-list(a)lists.umanitoba.ca) > 2. Re: Issue with double entry verification > (epidata-list(a)lists.umanitoba.ca) > 3. Aspects of function in updated public release of Manager and > EntryClient (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 28 May 2013 20:47:44 -0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Issue with double entry verification > To: epidata-list(a)lists.umanitoba.ca > Message-ID: > < > CAON-6PbqL-Rb_x3Nd2tBhf-hrP1v7T6c8Ju8RBKXrWR8wEmMdw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello, > > I am having an issue with double entry verification. I am using v1.4 on a > 64 bit Windows 7 PC. I am able to create a double file, but I am missing > any options like the manual indicates: > > *"*Options can be changed now: choose if textfields are to be ignore during > double entry (only data in numeric fields will be compared with original > data). > > Choose if records are to be compare by recordnumber or by a keyfield. If > the option "Match records by field" is unchecked, then records are compared > by recordnumber. If the option is checked, the user will be asked to point > out which data field should act as the keyfield. The keyfield must contain > unique data, i.e. a ID-number. > > Click OK and read the message stating that double entry varification is now > prepared." > > It simply only creates the double data file. I am also not able to get into > any sort of double entry mode in the epidata entry program. > > Is this a bug or am I not using it correctly? Thanks very much. > > -- > Natalie Sadler > Doctoral Student > Human Development Graduate Group > University of California, Davis > nsadler(a)ucdavis.edu > natalie.sadler(a)gmail.com > > > ------------------------------ > > Message: 2 > Date: Wed, 29 May 2013 09:12:41 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: Re: [EpiData-list] Issue with double entry verification > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <51A5AA69.1050200(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi. > > The double entry verification is a two-step process, which works > by first creating a duplicate of the the original project, but without > data. This is done with the "Prepare Double Entry"feature. > > Then you re-enter data into the second file, often namedlike > <filename>.double.epx. > > The last step is using the documentation feature "Validate > Duplicate Files" to compare the two files. It is within this feature > that you find your requested options, such as: > comparing using key fields, ignore text fields, etc. > > I hope this helps. > > Regards, > Torsten Bonde Christiansen. > EpiData Association. > > On 2013-05-29 05:47, epidata-list(a)lists.umanitoba.ca wrote: > > Hello, > > > > I am having an issue with double entry verification. I am using v1.4 on a > > 64 bit Windows 7 PC. I am able to create a double file, but I am missing > > any options like the manual indicates: > > > > *"*Options can be changed now: choose if textfields are to be ignore > during > > double entry (only data in numeric fields will be compared with original > > data). > > > > Choose if records are to be compare by recordnumber or by a keyfield. If > > the option "Match records by field" is unchecked, then records are > compared > > by recordnumber. If the option is checked, the user will be asked to > point > > out which data field should act as the keyfield. The keyfield must > contain > > unique data, i.e. a ID-number. > > > > Click OK and read the message stating that double entry varification is > now > > prepared." > > > > It simply only creates the double data file. I am also not able to get > into > > any sort of double entry mode in the epidata entry program. > > > > Is this a bug or am I not using it correctly? Thanks very much. > > > > > > ------------------------------ > > Message: 3 > Date: Wed, 29 May 2013 09:55:54 +0200 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Aspects of function in updated public release > of Manager and EntryClient > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <51A5B48A.6070202(a)epidata.dk> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Regarding the new versions 1.4 of Manager and EntryClient. > > Many changes have been implemented since first public release last year: > > Common: > * Encrypted data in project files > * Expanded headings to support 5 sizes/types. > * Added printing of dataform > * Key Fields (Unique keys) - including display of status of key at > record level > > Entry: > * Implemented a "Copy Record to Clipboard" function, with variable > format string. > > Manager: > * New improved drag/drop implementation (multiselect, copy/paste, > alignment) > * Double Entry Preparation/Validation > * Improved Study Information form. > * New improved export form, with more export formats. (SPSS, SAS, CSV, > DTA, DDI) > * Expanded process toolbar > > Obviously this is a remarked update and despite efforts to find and fix > problems in the testing uploads some issues have arisen in latest days: > > 1 Double entry > a > In EpiData Entry (old software): > - two different double entry modes are implemented: > 1. Compare values in second file with what was already entered in first > file directly at entry > 2. Compare two individually entered files > > In EpiData Manager (New software): > - Only type two is implemented at this point. Therefore you must (as > explained by T.Christiansen just before this mail) first enter data in > one file, then independently in the second. Following that compare the two. > > b > Validation has been extended with a new option such that a new field > can be added at record level (each observation) with the result of the > validation. When this field is added it makes sense to write a new file, > e.g. bromar.1.doubleentry-verification.epx. You can then read that file > into analysis and see which records are not validated. The values for > the created variable are: > 0 = Validated > 1 = Record does not exist in duplicate file > 2 = Failed due to different text > 3 = Failed due to different values > 4 = Duplicate key exists > > But currently in v1.4.0.0 the file is always created following > validation, and there can be a problem with the creation. This will be > changed, such that only when the user indicates addition of the field > the new file will be written and obviously also with the correct value. > > 2 > Aspects in relation to export: > a. Export to SPSS or SAS: the user is not informed of writing the > csv file > b. Export to DDI: the created xml is not correct in certain situations. > > Exported DDI meta data must validate correctly against the > DDI-Alliance standard v3.1. - with an external tool such as documented > on http://www.ddialliance.org/node/855 - The validator is found on > http://snd.gu.se/ddi/validator > > 3 > A few other aspects, such as default naming of valuelabel sets, term for > dataforms in reports and missing mentioning of cycle number > > The problems mentioned (1b, 2 and 3) will be fixed and a new public > update will be available later this week. > > Regarding cycle number this is a new feature which the end user is not > changing. Every time the project file is saved and there has been a > change in either study information, structure or value label sets > (metadata) or entered/edited observations/records the file will be saved > with a new "cycle number". On export this is part of the name of the > file. e.g. /home/jens/data/bromar_new.5.dta > > We will gradually implement usage of the cycle number in documentation > and verification of data in relation to in particular the implementation > of Good Clinical Practice guideline demands of verification. The notion > of a cycle comes from the DDI-alliance data-life cycle concept. You can > read more about that on: http://www.ddialliance.org/ddi-at-work > > regards > Jens Lauritsen > Epidata Association > > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 115, Issue 9 > ******************************************** > -- Natalie Sadler Doctoral Student Human Development Graduate Group University of California, Davis nsadler(a)ucdavis.edu natalie.sadler(a)gmail.com

1 1

Issue with double entry verification
by epidata-list＠lists.umanitoba.ca 29 May '13

29 May '13

Hello, I am having an issue with double entry verification. I am using v1.4 on a 64 bit Windows 7 PC. I am able to create a double file, but I am missing any options like the manual indicates: *"*Options can be changed now: choose if textfields are to be ignore during double entry (only data in numeric fields will be compared with original data). Choose if records are to be compare by recordnumber or by a keyfield. If the option "Match records by field" is unchecked, then records are compared by recordnumber. If the option is checked, the user will be asked to point out which data field should act as the keyfield. The keyfield must contain unique data, i.e. a ID-number. Click OK and read the message stating that double entry varification is now prepared." It simply only creates the double data file. I am also not able to get into any sort of double entry mode in the epidata entry program. Is this a bug or am I not using it correctly? Thanks very much. -- Natalie Sadler Doctoral Student Human Development Graduate Group University of California, Davis nsadler(a)ucdavis.edu natalie.sadler(a)gmail.com

1 2

Reply: Regarding exporting to SPSS
by epidata-list＠lists.umanitoba.ca 24 May '13

24 May '13

Dear Seng Aung, -You can directly export to SPSS. But the dataset gets saved as SYNTAX file with an extension of " .sps" - Then open this syntax file in SPSS (using open-syntax in menu bar) , you will get a list commands/syntax. Read the instructions at the top of that page. You have to go to the last command/syntax SAVE and remove the * mark to execute the SAVE command. After removing the * mark, just click the RUN in the menubar (RUN all) and your SPSS dataset (.sav file) is ready with labels and label values. -I checked with the EpiData manager and it is working. Dr. C. Palanivel, MD (Community Medicine) Assistant Professor, Indira Gandhi Medical College and Research Institute, (Government of Puducherry Institution) Kathirkamam, Puducherry-605009. Office: 0413-2277545 (Ex) 3123 Mobile: 9787825827 On Wed, May 1, 2013 at 10:31 PM, <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. Export from Epidata Manager to SPSS > (epidata-list(a)lists.umanitoba.ca) > 2. Export from Epidata Manager to SPSS > (epidata-list(a)lists.umanitoba.ca) > 3. Export from Epidata Manager to SPSS > (epidata-list(a)lists.umanitoba.ca) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 1 May 2013 14:56:28 +0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export from Epidata Manager to SPSS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <000ED2B2-B253-454F-B1D7-10EAFC19CB01(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > I cannot directly export from Epidata Manager to SPSS. > So, I exported to stata, then to SPSS. But I lost all my coding of missing > value. > > Please let me know how can I overcome this problem. > > Best, > Seng Aung > > ------------------------------ > > Message: 2 > Date: Wed, 1 May 2013 14:56:38 +0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export from Epidata Manager to SPSS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <899870FA-492C-4554-90A9-1FC98482545E(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > I cannot directly export from Epidata Manager to SPSS. > So, I exported to stata, then to SPSS. But I lost all my coding of missing > value. > > Please let me know how can I overcome this problem. > > Best, > Seng Aung > > ------------------------------ > > Message: 3 > Date: Wed, 1 May 2013 14:34:46 +0700 > From: epidata-list(a)lists.umanitoba.ca > Subject: [EpiData-list] Export from Epidata Manager to SPSS > To: epidata-list(a)lists.umanitoba.ca > Message-ID: <364AD808-5412-4D08-8711-E537DA688E01(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > I cannot directly export from Epidata Manager to SPSS. > So, I exported to stata, then to SPSS. But I lost all my coding of missing > value. > > Please let me know how can I overcome this problem. > > Best, > Seng Aung > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 115, Issue 1 > ******************************************** >

1 2

Reply: Regarding exporting to SPSS
by epidata-list＠lists.umanitoba.ca 15 May '13

15 May '13

Dear Dr. C. Palanivel, I've just downloaded and installed the latest EpiData Manager (1.1.2), but I can't find the export to SPSS feature - can you please point me in the right direction? In the Tools menu I only find "Export to Stata". Save Project As does not offer a SPSS or SYNTAX file format. Thank you in advance, Knud Larsen, Lab.Engineer, MScEE Aalborg University

1 2