- EpiData-list - University of Manitoba Mailing Lists

Overlapping text/ answer box
by epidata-list＠lists.umanitoba.ca 11 Nov '10

11 Nov '10

I don't use epidata very often, so this is probably a very basic question. I have created a form, but when I preview it, there are a few questions where the questions and answer boxes overlap (as shown in the attached). There is no overlap in design view and I am struggling to work out why this is happening. Any suggestions would be most welcome. Thanks, Shakeel Suleman ----------------------------------------- ************************************************************************** The information contained in the EMail and any attachments is confidential and intended solely and for the attention and use of the named addressee(s). It may not be disclosed to any other person without the express authority of the HPA, or the intended recipient, or both. If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it. This footnote also confirms that this EMail has been swept for computer viruses, but please re-sweep any attachments before opening or saving. HTTP://www.HPA.org.uk **************************************************************************

1 1

test version of analysis ready (read epx file - new Odds Ratio calculation)
by epidata-list＠lists.umanitoba.ca 07 Nov '10

07 Nov '10

A new test release of EpiData Analysis has been placed for download on the testing page. http://epidata.dk/testing.php The zip file contains a complete working copy, including updated help file. When you unzip please maintain folder structure. An EPX formatted version of bromar data is included in the zip file. Changes from previous releases are: A. Ability to read xml formatted files created by EpiData Manager (EPX) files (NOT EPZ zipped files) B. The default principle of Odds Ratio calculation has been changed from: MLE based to: Standard simple with Robins, Greenland, Breslow 95% CI to get the new default Odds Ratios use: /o , to use the same as previously: /oex Output is slightly changed, example: . tab runok sex /o /oex Outcome:Marathon race completed ? Sex of runner 1 0 Total 2 3119 418 3537 1 437 53 490 Total 3556 471 4027 Exposure: Sex of runner = 2Outcome: Marathon race completed ? = 1 Odds Ratio = 0.90 (95% CI: 0.67-1.23) (Robins,Greenland,Breslow CI) Exact (MLE) Odds Ratio = 0.90 (95% CI: 0.66-1.23) pORex<=1.0 = 0.2872 With this test release users are more than welcome to challenge the whole cycle of creating files in Manager (including import fra Stata, Rec, QES files, pasting via clipboard or editor etc), entering data with the EntryClient and analysing the data in Analysis. You may use the Manager to export data to Stata for comparisons of results. Anything not working - or comments to the way we have implemented aspects - please report to this list or if you find reproducible errors it is easier for us, if you can report to the flyspray system - see link on the testing page. regards Jens Lauritsen

1 2

EpiData-list Digest
by epidata-list＠lists.umanitoba.ca 06 Nov '10

06 Nov '10

Hello, Thank you for your response about police and presentation in future Epidata Manager, I understand the problem. But is it possible only for the size of the police for the titles for example..... ??? Also, in Epidata Analysis, there are two things that cause problems for teachers and users: - Following the command "freq", numbers order is not exactly descending in case of negative numbers. - Following the command "lifetable", P50 is sometimes wrong (if small population). .... and another thing that would make life easier: - Following the command "scatter", a regression line, like in EPI-INFO DOS with "/r", would be interesting . I have a method but is longer (with creation of new variable with equation of the line through "var result", and scatter with three variables). Thanks for EPIDATA. Bernard Branger, Nantes, France -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 2261 courriels spam. Nous avons en ce moment 7 millions d’utilisateurs de par le monde entier. Les utlisateurs payants n’ont pas ce message. Vous pouvez télécharger la version gratuite: http://www.spamfighter.com/lfr

1 0

font selection and text appearence in data forms
by epidata-list＠lists.umanitoba.ca 04 Nov '10

04 Nov '10

Dear all A question was raised regarding specification of underline, bold etc and specification of fonts in data forms created by the Manager and used for entry with the EntryClient. I think what could be realistic to aim for is something like: at section level: choose background colours for data fields: show field border (implemented) choose font, size and colour for all fields (question text) for heading "lines" choose font, size and text colour for all heading lines However I doubt if we will get to the point of applying underline, bold or italics for single words . The amount of work is still immense for all the data management, documentation, rewriting analysis etc. So do not expect any developments in this text fomatting area before all the core functionality has been attained. regards Jens Lauritsen EpiData Association

1 2

EpiData course material
by epidata-list＠lists.umanitoba.ca 04 Nov '10

04 Nov '10

A friend suggested that I may post this information: The 27th course of the International Union Against Tuberculosis and Lung Disease (The Union) in collaboration with the EpiData Association and a group called "EpiData Promoters" was given in Paris in the last week of October to 12 operations research fellows of a training program of The Union from 10 countries. The updated course material is available at www.tbrieder.org (click "EpiData course" in the navigation panel). The entire course exists of four parts. In Part A, the use of EpiData Entry is taught, in Part B, EpiData Analysis is introduced, in Part C, EpiData software is applied to operations research, and in Part D more sophistication in the use of EpiData software is taught. In the one-week course, only Parts A and B were taught. Parts C and D will be given to three exceptional performers in a supplementary course. The course is taught sequentially as one exercise builds on the previous one. For those interesting in only perusing quickly, you might look at the end of each Part for the solution PDF, or at the very bottom for the PDF file of the entire course (220 pages). The zip files in the solutions contain the EpiData files that are produced in each exercises. Regards, Hans -- Hans L Rieder, MD, MPH Jetzikofenstr 12 3038 Kirchlindach Switzerland Tel: +41 31 829 4577 Mob: +41 79 321 9122 Web: http://www.tbrieder.org

1 0

RE: EpiData-list Digest, Vol 84, Issue 17
by epidata-list＠lists.umanitoba.ca 01 Nov '10

01 Nov '10

Hello, Are there plans in future EPIDATA MANAGER : - To change the font for a word or phrase without changing police from the another parts of a questionary? - To open multiple pages in a questionary? Thank you Bernard Branger, Nantes, France PS The link to "Course materials in French" in EPIDATA ENTRY / FRENCH is : http://www.reseau-naissance.com/joomla/index.php?option=com_content&task=vi… -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 2235 courriels spam. Nous avons en ce moment 7 millions d’utilisateurs de par le monde entier. Les utlisateurs payants n’ont pas ce message. Vous pouvez télécharger la version gratuite: http://www.spamfighter.com/lfr

1 0

An error message while executing the command in Epidata analysis
by epidata-list＠lists.umanitoba.ca 29 Oct '10

29 Oct '10

Dear all, I got an error message while executing commands of Epidata analysis on a new machine with Windows 7. Please see the message within the quotation marks. " Cannot open file "C:\Users\Gateway\AppData\Local\Temp\TMPCC04.Tmp". The process cannot access the file because it is being used by another process " This happened when I hit F8 or F9 and the command was not executed. But it did work when I hit F8 for several times. Could anybody tell me why it happened and how to solve this problem? Thank you for your support. Zaw Myanmar

1 1

Datetime conversion resource
by epidata-list＠lists.umanitoba.ca 27 Oct '10

27 Oct '10

Hi list members From time to time on the list we have discussed the value of having a datetime variable in Epidata. This is something I would find like, as the 'epidemic curve' is something that is an important part of any outbreak investigation. For short outbreaks that carry on over more than one day both the time and date are useful so youcan show numbers becoming ill every 6 hours for example over two or three days. The ability to map by datetime is one reason I often use EpiInfo for outbreak analysis, although I enter data in Epidata. I wanted to let any interested members know that a colleague has developed a simple text file that can be run as a programme in EpiINfo that coverts data entered in EPidata to a single datetime for use in EPiInfo. If you have entered an onset date as a date and onset time as a number with a decimal (e.g. 15.30) the programme converts the information into a single datetime variable - it can then be mapped using the EpiInfo histogram graph. Jens if you think this is useful at all would you like me to post this somewhere? Also is there any thought of creating a time field in Epidata? thanks Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 22/10/2010 10:47 p.m. >>> For all users Today new versions of Entry Client and Manager have been placed on thehttp://epidata.dk/testing.php page for general download and testing. Apart from some minor points and errors reported to the Flyspray bug database the current release is what we see as the first release candidate for general usage following key developments mentioned below. level 1: Basic functionality at field level level 2: Extended functionality with value labels, basic checks etc We are at level 1 now and production release will include level 2. Main news since last release are: a. bug fixes and enhancements b. availability of two file formats: epx: the basic xml structure containing all information for a given project epz:The same file, but zipped, which often reduces the overall size to about 10-30% of the epx file c. export of data to stata d. short introduction to the EntryClient Currently the users should find and test the following: Manager a. all aspects of creating new projects with one database table/file per project a1. importing (loading) old rec files and stata files a2. Pasting from qes files or editor files onto a dataform a3. Saving these data as a project file with options for entry b. exporting data to Stata (regardless of whether you have Stata) EntryClient b. data entry of project files created with manager b1. Securing that data are saved and shown as read b2. Editing and browsing in data b3. Backup of files after entry b4. Timed recovery function if systems break down during entry What are the next steps ? c1. Adaptation of EpiData Analysis to be able to read the xml structured files (epz and epx) c2. Following users tests in the coming weeks further error removal will be done in EntryClient and Manager Please report if possible to the flyspray database system. (But also if you cannot get the flyspray system to work let us know on this list) Kind regards Torsten Christiansen, Jens Lauritsen EpiData Association -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1

Input for decision of sequence in development of new functionality, please comment
by epidata-list＠lists.umanitoba.ca 26 Oct '10

26 Oct '10

Priority of developments The current sequence of developments until the first production release contains these elements. 1. Release of test version of EpiData Analysis, which can read EXP files (possibly EXZ) - expected this week. 2. "show structure" form to Manager 3. Control structures level 1 (value labels, range) --- test release 4. Multi language in forms and labels 5. Control structures level 2 (mustenter, jumps, "type comment") 6. Control structures level 3 (define unique key and search in data) --- test release 7. Solve known deficiences (from Flyspray and list) - e.g. idnum fields 8. Printing of dataforms in EntryClient --- test release 9. Enhancements for production of fast datasets, e.g. copy from question banks 10. Further developments, e.g. GCP (Good Clinical Practice Principles). Please discuss on this list at what level of function You find first release should be made - provided obviously at that level the function as such is stable. My current decision is after point 8. It would also be good to get statements during the coming months of which decisions you make locally on the conversion to the new principles - e.g. you are ready to use it at that moment, or you find the current EpiData Entry better for your purpose, or you decided to start using other software and the reasons for that. Regards Jens Lauritsen EpiData Association Denmark

1 1

Re: [EpiData-list] New test versions available for EpiData EntryClient and EpiData Manager
by epidata-list＠lists.umanitoba.ca 26 Oct '10

26 Oct '10

Hi Jens and the Epidata team thank you for all the work you are doing on the new development. In terms of the timeline I am wondering about when the new build might be stable enough to be used for training courses? At the moment I teach one or two courses a year to public health staff on using Epidata and EpiInfo to investigate disease outbreaks. They use the current version of Epidata and I am wondering about when I should try and change to the new version. thank you Christine Christine Roseveare Analyst Regional Public Health 570 9194 027 495 9671 >>> <epidata-list(a)lists.umanitoba.ca> 22/10/2010 10:47 p.m. >>> For all users Today new versions of Entry Client and Manager have been placed on thehttp://epidata.dk/testing.php page for general download and testing. Apart from some minor points and errors reported to the Flyspray bug database the current release is what we see as the first release candidate for general usage following key developments mentioned below. level 1: Basic functionality at field level level 2: Extended functionality with value labels, basic checks etc We are at level 1 now and production release will include level 2. Main news since last release are: a. bug fixes and enhancements b. availability of two file formats: epx: the basic xml structure containing all information for a given project epz:The same file, but zipped, which often reduces the overall size to about 10-30% of the epx file c. export of data to stata d. short introduction to the EntryClient Currently the users should find and test the following: Manager a. all aspects of creating new projects with one database table/file per project a1. importing (loading) old rec files and stata files a2. Pasting from qes files or editor files onto a dataform a3. Saving these data as a project file with options for entry b. exporting data to Stata (regardless of whether you have Stata) EntryClient b. data entry of project files created with manager b1. Securing that data are saved and shown as read b2. Editing and browsing in data b3. Backup of files after entry b4. Timed recovery function if systems break down during entry What are the next steps ? c1. Adaptation of EpiData Analysis to be able to read the xml structured files (epz and epx) c2. Following users tests in the coming weeks further error removal will be done in EntryClient and Manager Please report if possible to the flyspray database system. (But also if you cannot get the flyspray system to work let us know on this list) Kind regards Torsten Christiansen, Jens Lauritsen EpiData Association -- The information contained in this email and any attachments is confidential and may be legally privileged. If you have received this message in error, please notify the sender immediately and remove all copies of the message, including any attachments. Any views or opinions expressed in this email (unless otherwise stated) may not represent those of Hutt Valley DHB. Thank you. ** Disclaimer added by HVDHB ** ______________________________________________________________________________ This email has been scrubbed for your protection by SMX. For more information visit http://smxemail.com ______________________________________________________________________________

1 1