EpiData-list January 2010

epidata-list@lists.umanitoba.ca

1 participants
9 discussions

by epidata-list＠lists.umanitoba.ca

Je serai absent(e) du Ven 22/01/2010 au Mer 17/02/2010. Bonjour! Veuillez prendre note que je serai absente de mon bureau le 25 janvier au 15 février. I will be out of the office from January 25-February 15. I will reply to your message upon my return. Ruwan

14 years, 2 months

entering arabic letters

by epidata-list＠lists.umanitoba.ca

Dear All, At our office, we are using epidata since 2003 for our local applications. Using MS office 2003, windows XP, we were entering our data using epidata3.1 in English version, but we have kept some variables for entering names using Arabic letters. Later, the .rec file was exported to excel in order to search for duplicates using the Arabic letters. It has worked. Yesterday, we had a new desktop with MS office 2007. That function of entering data using Arabic letters has disappeared. Do you have any idea why this happened? And how can we solve this matter? Sincerely Nada Ghosn, Eman Chamas, Epidemiological Surveillance Program Ministry of Public Health Beirut Lebanon

14 years, 2 months

testing manager version 0.3.2.9

by epidata-list＠lists.umanitoba.ca

Heemskerk 28/01/2010 Hello JENS and ALL, While testing this I got a message when I tried to read a DBF file, it says that it is a corrupted ZIPfile !! In true it is a perfect DBF file made by EPIDATA 3.1. Reading TXT, CSV, REC, QES files works perfect. Shifting the fields on the screen with the mouse : OK. Would appreciate more explanation about the SETTINGS, not all clear to me. A possibility to change the type of an already existing field would be nice.. I add a recxml file that contains some remarks. Yours, Louk. <?xml version="1.0"?> <EPIDATA> <SETTINGS> <VERSION>0</VERSION> <DATESEP>/</DATESEP> <DECIMALSEP>.</DECIMALSEP> <MISSINGMARK>.</MISSINGMARK> </SETTINGS> <METADATA> <LABELS> </LABELS> </METADATA> <FIELDS> <FIELD TYPE="15"> <NAME>label_1</NAME> <TAG>F1</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="31" Y="19"/> <LABEL X="31" Y="19">Label text to clarify PURPOSE file.</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_2</NAME> <TAG>F2</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="31" Y="43"/> <LABEL X="31" Y="43">++++++++++++++++++++++++++++++++++++</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="1"> <NAME>V1-short string</NAME> <TAG>F3</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="68"/> <LABEL X="130" Y="73">[SHORTY]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="1"> <NAME>V2-long string100</NAME> <TAG>F4</TAG> <LENGTH>100</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="118"/> <LABEL X="123" Y="123">[VERYlong]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_5</NAME> <TAG>F5</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="144"/> <LABEL X="198" Y="144">Very nice that such a long field is possible !!!!.</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="0"> <NAME>V3-Integer</NAME> <TAG>F6</TAG> <LENGTH>4</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="194"/> <LABEL X="133" Y="199">[Number]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="6"> <NAME>V4-Floaty</NAME> <TAG>F7</TAG> <LENGTH>11</LENGTH> <DECIMALS>6</DECIMALS> <POS X="198" Y="224"/> <LABEL X="130" Y="229">[Floatfield]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="11"> <NAME>V5-Holiday</NAME> <TAG>F8</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="267"/> <LABEL X="112" Y="272">[Normaldate]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="16"> <NAME>V6-THISDAY</NAME> <TAG>F9</TAG> <LENGTH>10</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="297"/> <LABEL X="120" Y="302">[Todayfield]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="12"> <NAME>V7-IDfield</NAME> <TAG>F10</TAG> <LENGTH>4</LENGTH> <DECIMALS>0</DECIMALS> <POS X="198" Y="350"/> <LABEL X="74" Y="355">[RECORDNUMBER]</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_3</NAME> <TAG>F11</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="72" Y="399"/> <LABEL X="72" Y="399">NOTE ! Each time when I click in a field , this field moves one pixel to the bottom. !!!</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> <FIELD TYPE="15"> <NAME>label_4</NAME> <TAG>F12</TAG> <LENGTH>0</LENGTH> <DECIMALS>0</DECIMALS> <POS X="143" Y="428"/> <LABEL X="143" Y="428">Writing the FIEDLABELS between square brackets keeps the aspect tidy...</LABEL> <COLOUR>FFFFFF</COLOUR> </FIELD> </FIELDS> <RECORDS> </RECORDS> </EPIDATA>

14 years, 2 months

updated manager

by epidata-list＠lists.umanitoba.ca

An updated manager has been placed on the testing.php page now. Changes are shown on that page. Basicly bug-fixes for what was reported on the list since last week. e.g.: labels snap onto nearby fields access violation when using encrypted fields adapted and documented use of keyboard shortcuts If you place the pdf introduction document (also from testing.php) in a subfolder to the exe, you can call the pdf from the help menu (possibly not on Mac). Work will now concentrate on the first prototype of a dedicated EntryClient, after which adding checks and controls is in the workplan. The manager will only be fixed for reproducible bugs until an EntryClient exists. regards Jens Lauritsen EpiData Association

14 years, 3 months

New EpiData Manager ready for (next) test

by epidata-list＠lists.umanitoba.ca

The EpiData Data Manager will gradually replace the existing EpiData Entry software as development goes on. Why change to EpiData Manager ? Since release of first EpiData software in 1999 many aspects have changed. The main reasons for development of the new strategy are: • New users are increasingly ”graphicly” oriented and focused on mouse usage. ◦ not understanding the well known qes-chk-rec principle • There is a need for multiplatform development (Linux, Mac, Windows, PDA …..) • Font management is changing to UTF-8 to avoid nationalisation problems • We wish to implement GCP (Good Clinical Practice) required for many medical data projects. This demands encryption and logging of editing at a very detailed level. • There should be a common ”engine” for all EpiData software, such that handling of data and metadata (labels etc.) are based on the same internal routines. • When doing data entry it should not be immediately easy to change rules or structure for data entry personnel. Therefore a dedicated EpiData EntryClient will be developed – serving only data entry. How will a project manager see the new strategy ? The work process is more clearly divided into what the manager does and what the data entry persons do. The EpiData Manager is a tool for the project person, which: • Defines data structures, adds metadata (labels and definitions), documents data and exports for analysis. • Updates data with new fields, changed formats for fields (e.g. More decimals) and is used for control of data. • There is a choice of using computers with either Linux, Mac or Windows A short introduction document is found next to where the test application can be downloaded. See http://www.epidata.dk/testing.php Apart from fixing many bugs, the new version now includes an editor, a revised interface and allows for pasting from a qes file or the editor. Next phase is to add checks and develop the Entry Client. For the planning please comment on the new release, which includes an editor. Also we should have a discussion on which are the "core" check commands that almost everyone uses and which are enhanced. regards Jens Lauritsen EpiData Association

14 years, 3 months

Epidata and check

by epidata-list＠lists.umanitoba.ca

I am having a small problem with Epidata. I have this field with place for 2 numbers. How do I check that this field contains something? I need this because from this field I have to make a jump depending on whether this field is blank or not. Thank You. Venlig hilsen/Kind regards Antonio Sylvester

14 years, 3 months

additional core commands

by epidata-list＠lists.umanitoba.ca

Hello Please add these very important commands: 'comment legal show' 'comment legal use' confirm Thanks For implementation in the first updated entry client we need to define a basic core set of basic check commands Suggestion: (please comment): backup value label, legal, range and missing value definitions type comment jump / goto hide topofpage mustenter repeat message (help) key unique Did I miss any ? The core set of check commands will be part of the main recxml file, whereas further specifications will be contained in a separate (chk) file. regards Jens Lauritsen EpiData Association _______________________________________________ EpiData-list mailing list EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list Steve Blum

14 years, 3 months

Which check commands do you consider as the basic ones ?

by epidata-list＠lists.umanitoba.ca

For implementation in the first updated entry client we need to define a basic core set of basic check commands Suggestion: (please comment): backup value label, legal, range and missing value definitions type comment jump / goto hide topofpage mustenter repeat message (help) key unique Did I miss any ? The core set of check commands will be part of the main recxml file, whereas further specifications will be contained in a separate (chk) file. regards Jens Lauritsen EpiData Association

14 years, 3 months

EpiData-list

by epidata-list＠lists.umanitoba.ca

Good Happy Year for EPIDATA ! Thanks to Jens and his team for continuing EpiData development. Two small questions still relevant : - regression line (in or out of scatter plot) : this is very important for the teacher in statistics ++ - true P50 in lifetable : when ? Thank you for your work. Bernard BRANGER, Nantes, France -- J’utilise la version gratuite de SPAMfighter pour utilisateurs privés. Jusqu’à présent SPAMfighter a bloqué 1154 courriels spam. Nous avons en ce moment 6 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

14 years, 3 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 January 2010