- EpiData-list - University of Manitoba Mailing Lists

New analysis
by EpiData development and support 06 Feb '21

06 Feb '21

Hello, For training, I'm trying to understand the new version of "Analysis". A few comments : - The command "freq var ! r;" (as shown in the guide) doesn't work, but "freq var ! pr" is OK. Strictly speaking and on the educational plan, the percentages presented with "freq" are in columns : "freq var ! c;" or "freq var ! pc;" would be more logical. - To select a part of the file, I noted, (as an example for a frequency) the command "select (var1 <3) do freq var2 ! pr;". Should we repeat with each command "select (var1 <3) do"? Is there a way, like the old "select", to select part of the file for further commands? - The command (example) "select (var1 = 3) do var1: = 2;" is quite complicated compared to that "if ... then ...." - How to create a new numeric variable with 3 digits and 2 decimal places? As in the old "define var ###. ##"? - When will the "regress" commands and the graph commands (including scatter with a regression line as in the old "Epi-Info" ...? Thank you for your help. Bernard BRANGER - 44000 NANTES - France

1 1

Happy (belated) New Year 2021
by EpiData development and support 14 Jan '21

14 Jan '21

Happy (belated) New Year 2021 Dear Jens and Epidata Team,                         There is absolute silence on the list. I hope Covid 19 impact is waning away and New Epidata Analysis development is in progress. Any news!! Shavinder Singh  

1 0

Re: [EpiData-list] Epidata 4.6.0.4 SPSS-Export
by EpiData development and support 15 Dec '20

15 Dec '20

Dear Michael, thank you for this hint! That makes things much easier. If someone nevertheless needs it, I attach a spss syntax, that produces a list of string variables in the datafile and than deletes all leading and ending quotation marks (the first and the last character) in these string variables. It can be included in the spss import syntax. Best Regards, Juergen Am 15.12.2020 um 10:32 schrieb EpiData development and support: > Dear Juergen, > this is right, the SPSS-Export doesn't work right. The used SPSS- > Command "data list" is a lit bit out of date and could not handle > qualifiers for Textvariables. > > This is a workaround: > Do the SPSS-Export. > Afterwards do a second export, the "CSV-Export", and overwrite the > existing file. > In the Specifications for the CSV-Export you can disable/delete the > Quote Character. > Greetings > Michael > > Am 15.12.2020 10:08 schrieb EpiData development and support: >> Dear all, >> >> I have a little problem with the SPSS-Export of the Epidata-Files. >> When you export string variables, you can specify the variable >> delimiter (e.g. "|") but not the text delimiter. The result is a csv >> file, that is imported in SPSS with quotation marks at the start and >> the end of every string variable, even if the variable is empty. I >> found no way to delete these quotation marks during the spss import >> process except with a quite complicated macro. >> >> Is it possible to change the SPSS export? >> >> Kind Regards, >> >> Juergen Spiegel >> >> >> -- >> *********************************************************** >> Freiburger Institut fuer angewandte Sozialwissenschaft e.V. >> FIFAS >> Erasmusstr. 16, D-79098 Freiburg >> >> Telefon: +49-761-288364 >> Fax: +49-761-2927493 >> Web: http://www.fifas.de >> E-Mail: info(a)fifas.de >> >> _______________________________________________ >> EpiData-list mailing list >> EpiData-list(a)lists.umanitoba.ca >> http://lists.umanitoba.ca/mailman/listinfo/epidata-list > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list -- *********************************************************** Freiburger Institut fuer angewandte Sozialwissenschaft e.V. FIFAS Erasmusstr. 16, D-79098 Freiburg Telefon: +49-761-288364 Fax: +49-761-2927493 Web: http://www.fifas.de E-Mail: info(a)fifas.de

1 1

Epidata 4.6.0.4 SPSS-Export
by EpiData development and support 15 Dec '20

15 Dec '20

Dear all, I have a little problem with the SPSS-Export of the Epidata-Files. When you export string variables, you can specify the variable delimiter (e.g. "|") but not the text delimiter. The result is a csv file, that is imported in SPSS with quotation marks at the start and the end of every string variable, even if the variable is empty. I found no way to delete these quotation marks during the spss import process except with a quite complicated macro. Is it possible to change the SPSS export? Kind Regards, Juergen Spiegel -- *********************************************************** Freiburger Institut fuer angewandte Sozialwissenschaft e.V. FIFAS Erasmusstr. 16, D-79098 Freiburg Telefon: +49-761-288364 Fax: +49-761-2927493 Web: http://www.fifas.de E-Mail: info(a)fifas.de

1 1

Issue with upwards shifting variables working from different computers
by EpiData development and support 16 Oct '20

16 Oct '20

Dear all, Could someone help us out with an issue regarding the change of layout of an EpiData file every time we open in EpiData manager/EntryClient on different computers? This issue occurs every time we edit the file in a different computer, as we are two persons working on the same file/project on different computer. More specifically, we noticed that the layout shifts upwards when you open the same file in on another computer. These upwards shifts of variables results in the (visual or complete?) loss of the created variables. This also makes the input of data through EntryClient challenging (because you don’t see all the variables anymore). Has this issue been encountered before? And would someone have a solution? All help would be much appreciated! Many thanks

1 1

Update of most recent public version of Analysis (due to error in the editor)
by EpiData development and support 03 Jul '20

03 Jul '20

Dear All Unfortunately there was an undisclosed bug in the public version released last week of new Analysis. One could exit Analysis without being asked to save an unsaved pgm file in the editor. This is now fixed. The most recent public version is therefore: _Manager_ *v4.6.0.2* _EntryClient_ *v4.6.0.2* _Analysis_ *v3.0.0.1* And the combined one for Windows: setup.all-in-one.4.6.0.5.exe The lacking finding of the error has been added to the pre-test for coming analysis. best wishes and apologies. Jens Lauritsen EpiData Association, Denmark

1 0

SPSS Export
by EpiData development and support 03 Jul '20

03 Jul '20

Dear Torsten, dear Jens, Epidata-Manager does the SPSS-Export in a indirect way. A SPSS-Syntax-File and a CSV-Data-File are created. You have to run the Syntax in SPSS to create a SPSS-Datafile. This is the current proceeding. For this proceeding I have some questions: - Is it very hard to create a SPSS-Datafile at once? - Why is the SPSS-CSV-Data-Export-File different to a direct CSV-Data-Export-File? The Structure is different. In my opinion it will be easier and a clear way to have ONE (adjustible) CSV-Data-Export-File. For that I recommend to replace the second Tab in " Tools/Export.../Type: SPSS 'SPSS-Options' " with the 'CSV-Options' (except for "Export Value Labels" because this is a great advantage of EpiData! Perhaps this Item stands better one the first Tab.) - Is it possible to change the default given SPSS-Syntax? The "Data List"-Command still works, but it is a little bit out of date. It does not work with the qualifier for Textvariables. So you have to edit the csv-File or have to write a new Syntax. "GET DATA" is the current Command. With kind regards Michael

1 1

Epidata 3.1 - Not Showing Correct Date
by EpiData development and support 02 Jul '20

02 Jul '20

Good morning. I received a ticket from one of our Epidata users. The user is using Epidata 3.1. According to her, the data entry sheets usually self-populate with the correct date. However, it seems to be stuck on 20/04/2020. Please see attached. Troubleshooting done: 1. Clear personalization and profile. 2. Re-install the software. Info: 1. There are 2 users of Epidata in this department. The 2 of them are experiencing this. 2. They are using VDI pool to access Epidata. What do you think is the problem and how it can be resolved. Thank you. Noel Bermejo Technical Analyst - Information Technology Yorkton Regional Health Centre - Yorkton Saskatchewan Health Authority | 306-786-0159 This email message may contain confidential and/or privileged information. It is intended only for the addressee(s). Any unauthorized disclosure is strictly prohibited. If you are not a named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system.

1 1

Epidata Analysis 3.00 and background colour
by EpiData development and support 28 Jun '20

28 Jun '20

Dear Jens and Team,                    Congratulations for this next step of Epidata Analysis 3.00 development. You have very kindly added the functionality of;Output background colour,Command background colour from Edit -- Colour pull down menu.I am not technically sure of the difficulties involved in adding "Editor background colour" option also in the software with cross platform compatibility.However if possible, please try to add that also in the next development release.Our rock solid Classical Epidata Analysis 2.2 ver was developed after year of hard work by Epidata Team. Replicating all those and additional functionalities in the new Epidata Analysis is a daunting task. However Epidata team has shown real perseverance .With regards and best wishes,Shavinder Singh   

1 0

Almost releasable new pre-public version of Analysis (please test)
by EpiData development and support 25 Jun '20

25 Jun '20

Dear list-readers A new updated version of EpiData Analysis (v1.7.99.1) has been placed for your testing on http://epidata.dk/testing.php Please find below a summary of the changes. In particular notice that the requirement of [_n] in pgm's has been removed, unless you refer to a given observation. I expect the release as public in the coming week or the week after. Please test and report to this list. As part of my job as a clinical epidemiologist and professor at the Odense University Hospital here in Denmark I have extensively tested the software during the last three months. We now use the pre-public version on a daily basis. Now we have a running system in new EpiData Analysis. It is run by secretaries, who have no experience in programming. They just click an icon to accomplish: a.import a csv file saved daily from our main IT-patient registration system (EpiData Analysis) b. merge with previously controlled observations to evaluate only new observations (EpiData Analysis) c. quality securing coding in the patient journal. (EpiData EntryClient) d. create SPC graphs in classic analysis (EpiData Analysis Classic) e. create lists for audit of patients where the quality standards were not met. To run the system in the revised new analysis we only lack possibility of creating graphs, which I expect to include in the coming months, if all goes well ready by the end of this year. One other aspect we need to tackle is the increasing demand for safety certificates and documentation in relation to secure systems. If any of you are experienced in this area please write me an e-mail (jl at epidata.dk) . Without the efforts of Torsten Bonde Christiansen (Software design and programming), Jamie Hockin (testing, programming, Mac adaptation) and Hans L. Rieder (testing, approving solutions) the software would not continue to develop. Please look into the website for inspiration: https://tbrieder.org/epidata/epidata.html Best wishes Jens Lauritsen, coordinator and initiator. EpiData Association, Denmark -------------------------------------------------------------------------------------------------------------------------------- Changes since v1.6.0.0 Major improvement: - [_n] is no longer needed, except when desired. - editor: Completely new. Many aspects improved. Works better in MacOs - new !output option with save command - allows saving output content as html - new "set" option to control format of saved output html|txt - new "set" option allows user definition of css styles in saved html output - new "set" option defines internal css or external reference to css file in html output - extended fast createdate function allows conversion of date strings with named months. - extended createdate function allows use of national month naming defined in set Other new aspects: - mergevar added as the last in a merged dataset - default dataset used after merge is the merged one - keyboard shortcuts unified and simplified. - main window opens immediately if started with a pgm - many commands: unified option naming, e.g. !l is labels Bug fixes: - all solved - keep : if used in a "for loop" errors could occur - Assignment: incorrect control of missing in string variables - validate duplicate : error if a variable was missing - many minor other bugs or inconsistencies Bug fixes: - partially solved - errors in calculations when dividing by zero. fixed in Linux and MacOS, but not in windows always. Known issues at this point: - Analysis does NOT handle header "variables" at all (except keeping defined ones). - Sometimes windows 10 gives a "list - index out of bounds" error in particular when running a selected block from the editor or when running several pgm files within a pgm.

1 1