- EpiData-list - University of Manitoba Mailing Lists

EpiData classic v3.1 in 2020? Under 64bit?
by EpiData development and support 06 May '20

06 May '20

Dear EpiData list members, Use EpiData classic v3.1 in 2020? (last release in 2008) YES - that's what I have just been doing, based on good experience a decade ago under Windows 7 pro 32bit, and on guidance found regarding EpiData v4.6 versus v3.1 on <http://www.epidata.dk/download.php> (see below). HOWEVER, one important feature no longer seemed to be working under Windows 7 pro 64bit: DEFINEd variables were only locally available (i.e. in the same record), but not GLOBALly (i.e. across RELATEd tables). Question: Is anything known about this problem, or even a work-around? This would be important, because: 1- EpiData v3.1 uses a parsimonious language easy to retain e.g. for researchers who only occasionally are in the situation to program themselves a data entry tool (but then typically like to get it working quickly w/o learning new software); 2- According to http://www.epidata.dk/download.php (accessed today), "In special situations or when a given function is not yet developed in Manager, EntryClient and Analysis you could need ... EpiData (Classic) Entry v3.1 (get it here) (only for programmed checks, before/after end blocks)". HOWEVER, MANY will find essential what can be done with BEFORE/AFTER FILE/RECORD/(field) blocks and apparently can not (yet?) be done with v4.6; 3- The feature "DEFINE variable GLOBAL" is necessary for multiple-level hierarchies and longitudinal databases (and it proved feasible and effective when I did it 10 years ago under Windows 7 pro 32bit, communicating only by email between North-America and sub-Saharan Africa). Thanks in advance Rolf

1 1

Defining Entry Rights EpiData Manager v4.6.0.2
by EpiData development and support 10 Mar '20

10 Mar '20

Hello, I am testing the EpiData system as a possible solution for data management for a nutrition cohort study. I have been able to set up a dataform and create groups and users using the Extended Access capabilities. I am however unable to define entry rights (CTRL E) on the my test data form, when I click on it using the point click option or control E absolutely nothing happens and the window I expect to show up as shown in the page 4 (Step 3) of attached PDF does not appear. Anyone else experienced this problem? Or am I missing something? Edna

1 5

Export to R from epidata
by EpiData development and support 11 Jan '20

11 Jan '20

Dear Jens Is it possible to export the data in epidata to R data? Perhaps it can but i am not sure how Please could you advice again, much appreciate your teams tremendous works new year greetings Thambu

1 1

Re: [EpiData-list] Export to R from epidata (EpiData development and support)
by EpiData development and support 11 Jan '20

11 Jan '20

I have exported from EpiData to R successfully. I used both Stata-files to preserve value labels and CSV files. Work fine. Kind Regards Henning Langen Stokmo Consultant (Nuclear Medicine) // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital Radiology Resident // Department of Medical Imaging, Vestre Viken HF, Drammen Hospital PhD-student // Department of Nuclear Medicine, Oslo University Hospital | Oslo University Functional and Molecular Imaging Research Group ( https://www.ous-research.no/revheim/) ResearchGate: https://www.researchgate.net/profile/Henning_Langen_Stokmo On 11 January 2020 at 19:01:02, epidata-list-request(a)lists.umanitoba.ca ( 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 to R from epidata (EpiData development and support) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 11 Jan 2020 04:51:46 +0000 > From: EpiData development and support > <epidata-list(a)lists.umanitoba.ca> > To: "epidata-list(a)lists.umanitoba.ca" > <epidata-list(a)lists.umanitoba.ca> > Subject: [EpiData-list] Export to R from epidata > Message-ID: <1578718346010.92724(a)cmcvellore.ac.in> > Content-Type: text/plain; charset="iso-8859-1" > > Dear Jens > Is it possible to export the data in epidata to R data? > Perhaps it can but i am not sure how > Please could you advice > again, much appreciate your teams tremendous works > new year greetings > Thambu > > ------------------------------ > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > > End of EpiData-list Digest, Vol 188, Issue 2 > ******************************************** >

1 0

new public release of Analysis, Manager and EntryClient released
by EpiData development and support 09 Jan '20

09 Jan '20

Dear all Yesterday we moved the "pre-release" version announced on December 31st 2019 to the official public download page. You may review the changes in the announcement on that day. So from now please install and use the updated versions. Some important errors have been identified in previous versions of EntryClient, so you should update. You may always test which version you have in the help menu "check version online". EpiData Analysis: 1.6.0.0 EpiData EntryClient: 4.6.0.2 EpiData Manager: 4.6.0.2 You might have to contact a central IT office if there are restrictions on installation and use of software. E.g. in our hospital I have to install from a local network drive while having a local administrator right for 30 minutes. We have not had any major issues reported - but a few minor aspects were identified in-house and fixed. E.g. A lacking !label abbreviation in a command and a change when importing csv files (string variables identified shorter than about 70 characters will now be string and not memo). Four observations that you should know of: 1 In analysis the command keys have been changed a bit. Check the "window" menu and notice that in the editor "ctrl+a" will run all commands and "ctrl+d" will execute the current command or a block if you have selected a block of commands. 2 If in new analysis you wish to create a memo or upper variable these are found as options to the "new variable" command as options (!memo !Upper): e.g. new variable txt string !memo. 3 If you are creating password protection in Analysis, this is done at the project level, not at the variable or dataset level. An example of this is shown below. 4 Currently I am doing many SPC (Statistical Process Control) graphs in my work at the hospital for hip fracture patient quality assurance. The way this is done is that we extract from the main hospital registration system a number of variables for all hip fracture patients. This is saved once a day on a central server as a csv file. Then I import this file with the new analysis and save it for table analysis in new analysis with many variables including time and memo variables (analysisNew.epx). But when I need to do the SPC graphs in Classic Analysis the epx file is not read, since Classic Analysis cannot read this type of variable. The remedy is to save a separate epx file (analysisClassic.epx) and use that for the graphs. Then I can just copy the graphs to a common folder and an html file shows the current results. The principle is an extension of a system developed with Norwegian Colleagues recording data for local municipal reporting from health centers (Thanks Vegard Högli). best wishes to all Jens Lauritsen EpiData Association Denmark new p !l:="test project" !size:=100; New project created: test project .... (output omitted - project with 1 dataset and 100 observations created) // to add a password encryption on all data: edit p !pw:="test"; // to verify this : list p; (output omitted - exect for info on "encryption"): Project Encryption: simple password (data only); // to remove a password: edit p !pw:=""; list p; (output omitted - exect for info on "encryption"): Project Encryption: none

1 0

New test versions and a warning on time and memo variables
by EpiData development and support 31 Dec '19

31 Dec '19

Dear all users of EpiData As quite many of you have already experienced, we have placed new test versions of EpiData EntryClient, Manager and Analysis on the http://epidata.dk/testing.php page on December 18th. The changes implemented in the test versions are documented in detail in the "change lists" found under each software on the "public release page, http://epidata.dk/download.php. Current public release versions are 4.6.0 for EntryClient and Manager and 1.4.0 for Analysis. As the the updated test versions are numbered: 4.6.0.2 for EntryClient and Manager and 1.6.0 for Analysis the major changes are in Analysis, where we are preparing for introduction of graphs and other lacking functionality. 1.6.0.0 of analysis * new command: Recode - very strong including formation of labels and other documentation * See Commands.html for details (press F1) of changes to options and the other new commands: keep and version * Variable list, History, Project overview and Command tree have been moved to seperate windows * Revised shortcuts and option names, e.g. unification of label as !l * !h option works for all commands and prints a simple list of supported options for a given command. * Table may be used for only one variable (with options for frequencies) And many Many minor bugfixes, mostly involving statistic calculation and special cases (eg. 0 data) If no major problems are identified the current "test versions" on the testing page will be "public release versions" in early January. Warning: As a side-effect of the new variable types (memo and time) variable, you should notice that if you want to read epx datafiles into classic analysis, then in the new analysis change those variables to another form, e.g. one or more string variables. At this end of our year I wish to express my thanks to all who supported EpiData Software over the years, including anonymous donors in the recent year, but also in particular the core group of Torsten Christiansen, Jamie Hockin and Hans L. Rieder. I wish all a happy new year and do hope that You will welcome the new and coming further structured development. Without all of your support and ideas the project could not continue. Best wishes Jens Lauritsen EpiData Association

1 0

NEUTRALZING A RECORD
by EpiData development and support 19 Dec '19

19 Dec '19

Dear all, How can you neutralize a record in a data set (duplicate or else)? In Epi-Info, you just needed to do F6 on the data sheet It should have a possibility with Epidata Thanks Dr Pierre-Yves Robillard Réanimation néonatale et pediatrique, néonatologie Centre Hospitalier Régional Groupe Hospitalier Sud-Réunion BP 350. 97448 Saint-Pierre cedex Ile de la réunion _____ From: epidata-list-request(a)lists.umanitoba.ca To: epidata-list(a)lists.umanitoba.ca Sent: Wed, 18 Dec 2019 22:01:08 +0400 Subject: EpiData-list Digest, Vol 187, Issue 1 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. 64-bit version / MacOS Catalina (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Dec 2019 07:11:00 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: [EpiData-list] 64-bit version / MacOS Catalina Message-ID: <trinity-9c54c698-20c3-48e6-a35f-c400c76e47b2-1576563060099@3c-app-webde-bap14> Content-Type: text/plain; charset="us-ascii" An HTML attachment was scrubbed... URL: <http://lists.umanitoba.ca/pipermail/epidata-list/attachments/20191217/ca53a…> ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 187, Issue 1 ********************************************

1 2

News on software upgrades and EpiData software on Mac Catalina ?
by EpiData development and support 18 Dec '19

18 Dec '19

Dear all Within short time new "pre-public" versions of EpiData Software (Manager, EntryClient and Analysis) will appear on the testing.php page of EpiData. Apart from bug fixes the main upgrading is in Analysis. A dedicated mail will be posted once the updates are placed there. Another issue is that a few users have asked when EpiData software will be available for the MacOS Catalina. This is not to easy to answer since it seems that Apple has applied further special restrictions. In short we can guide you with this (unfortunated) message: Mac users of Epidata software should not upgrade their operating system to MacOS Catalina. Current Mac versions of Epidata will not run under this most recent version of MacOS because of restrictions Apple has put into the operating system. We are working on 64-bit Mac versions of the software that can be installed on MacOS Catalina and will advise users when these are ready. More news on this later when the tests are more extensive and time has permitted the development. Best wishes to all Jens Lauritsen EpiData Association Denmark

1 0

64-bit version / MacOS Catalina
by EpiData development and support 17 Dec '19

17 Dec '19

1 0

Unable to import .qes & .chk in iOS version?
by EpiData development and support 19 Nov '19

19 Nov '19

Dears, I work with local colleagues on TB mortality issues. I imported .rec from Windows version but can't for .chk and .qes Is this "normal", as mentionned in last thread related to iOS version of Epidata or do I miss something ? Thanks ! Gaël Claquin Tél Bénin: +229 99 00 37 17

1 1