Greetings.
Is there a way to do a conditional value label look up in either the current or in the new test version of EpiData?
For instance, if field disease equals A then field subtype has values 1,2,3 for selection, if field disease equals B then field subtype has values 4,5,6, etc.
Thank-you, and well done to the development team for excellent progress.
_______________________________________
Stephen Drew
Health Data Analyst
Region of Waterloo Public Health
Waterloo, ON
Hi all,
I'm trying to combine IF... THEN with LEGAL but somehow I'm having problems
with it. Basically, what I want to do is to determine valid values for one
variable based on the answer given to another variable. In the example
below, the two vars are stateid and countyid: If stateid = 1 then countyid
could be 01 or 04; if stateid = 2 then countyid could be 02, 03 or 05.
Example:
countyid
IF stateid = 1 THEN
LEGAL
01
04
END
ENDIF
IF stateid = 2 THEN
LEGAL
02
03
05
END
ENDIF
MUSTENTER
END
--
Thomaz A.
Dear friends, I can't normally export value labels to Stata 11 data file even using the newest sample.epx. Why?
RegardsRichard Zhou
> Date: Fri, 26 Aug 2011 12:00:29 -0500
> From: epidata-list-request(a)lists.umanitoba.ca
> Subject: EpiData-list Digest, Vol 94, Issue 13
> To: epidata-list(a)lists.umanitoba.ca
>
> 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. Re: New test versions (manager, entryclient, template cmd
> tool) (epidata-list(a)lists.umanitoba.ca)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 26 Aug 2011 13:25:02 +0200
> From: epidata-list(a)lists.umanitoba.ca
> Subject: Re: [EpiData-list] New test versions (manager, entryclient,
> template cmd tool)
> To: epidata-list(a)lists.umanitoba.ca
> Message-ID: <4E57828E.2030904(a)epidata.dk>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Dear All.
>
> As promised in our previous mail, we have released a new test version of
> EpiData Analysis on our website today.
>
> This test release have been modified to support the new XML structure
> used by the most recent versions of EpiData Manager and EpiData EntryClient.
>
> Along with this change, EpiData Analysis is now also capable of reading
> the zipped versions of the project files. That is, it is now possible to
> read the .epz files.
>
> With kind regards,
> Torsten Bonde Christiansen.
> EpiData Association.
>
>
> On 2011-08-24 16:38, epidata-list(a)lists.umanitoba.ca wrote:
> >
> > Dear All
> >
> > As previously announced the programs released today have had a
> > significant change to the underlying structure of the project file
> > (the .epx/.epz XML structure).
> >
> > The reason for this is that the previous structure could not be
> > described by a XML Schema file. A schema file is a standardised way of
> > describing the structure and internal logic of an XML file. Some of
> > the logical properties of the structure were inconsistent and
> > therefore changed. This has as a positive "side effect" that the
> > overall loading and saving time for a project file has improved quite
> > a bit.
> >
> > The changes will - as warned two times on this list - break
> > compatibility with
> > previously created files. An updated version of the sample.epx file is
> > provided with the downloads and additionally the EpiData Commandline
> > Tool has been updated (and release for all platforms) to support the
> > new XML structure.
> >
> > Please read previous mails on the list to see further explanation and
> > how you can avoid problems in relation to the changed XML structure.
> >
> > The currently available test version of EpiData Analysis does NOT
> > support the new XML structure. An updated version will be released in
> > a few days.
> >
> > Common fixes/changes:
> > * Updated XML structure
> > * Import from STATA 12 now supported.
> > * New saving algorithm, for improved speed.
> >
> > Manager:
> > * Fixed a bug where removing a control marked for copy would cause
> > breakdown if copy/paste was later invoked.
> > * Fixed shortcuts for MAC.
> > * Added boolean field to "other fields"
> > * Fixed bug with "delete all"
> > * Speed improvements for copy/paste and placing new controls (mainly
> > visible with very many controls).
> >
> > EntryClient:
> > * Fixed shortcut overlap in MAC
> > * Speed improvements with loading project files.
> > * Speed improvements when browsing records.
> >
> > EpiC:
> > * Updated to support new XML structure.
> >
> > Regards
> >
> > Torsten Christiansen and Jens Lauritsen
> > EpiData Association
> > _______________________________________________
> > EpiData-list mailing list
> > EpiData-list(a)lists.umanitoba.ca
> > http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
>
> ------------------------------
>
> ________________________________________
> EpiData-list(a)lists.umanitoba.ca
> http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
> End of EpiData-list Digest, Vol 94, Issue 13
> ********************************************
Dear All
As previously announced the programs released today have had a
significant change to the underlying structure of the project file (the
.epx/.epz XML structure).
The reason for this is that the previous structure could not be
described by a XML Schema file. A schema file is a standardised way of
describing the structure and internal logic of an XML file. Some of the
logical properties of the structure were inconsistent and therefore
changed. This has as a positive "side effect" that the overall loading
and saving time for a project file has improved quite a bit.
The changes will - as warned two times on this list - break
compatibility with
previously created files. An updated version of the sample.epx file is
provided with the downloads and additionally the EpiData Commandline
Tool has been updated (and release for all platforms) to support the new
XML structure.
Please read previous mails on the list to see further explanation and
how you can avoid problems in relation to the changed XML structure.
The currently available test version of EpiData Analysis does NOT
support the new XML structure. An updated version will be released in a
few days.
Common fixes/changes:
* Updated XML structure
* Import from STATA 12 now supported.
* New saving algorithm, for improved speed.
Manager:
* Fixed a bug where removing a control marked for copy would cause
breakdown if copy/paste was later invoked.
* Fixed shortcuts for MAC.
* Added boolean field to "other fields"
* Fixed bug with "delete all"
* Speed improvements for copy/paste and placing new controls (mainly
visible with very many controls).
EntryClient:
* Fixed shortcut overlap in MAC
* Speed improvements with loading project files.
* Speed improvements when browsing records.
EpiC:
* Updated to support new XML structure.
Regards
Torsten Christiansen and Jens Lauritsen
EpiData Association
Dear all
As I already informed on August 17th the next test release for Manager
and EntryClient will require ALL current EPX and EPZ files to be
recreated. The next test release will be available within the next few
days.
Obviously this can be annoying, but as previously announced we do need
to have the flexibility of changes all the way to release of version 1.
If you are preparing projects for future use I recommend that you either:
a.
- Export your data with current test version into stata format
- import again with the new test version (when this is ready)
- add jumps, calculations etc after the import.
(Labels will be imported correctly)
or
b
look at the template principles explained in
http://www.epidata.org/dokuwiki/doku.php/documentation:templateformat
and then use the template command tool to create the epx files. A
revised template tool will be released at the same time as the next test
release.
In other words: Do not spend too much time on fine tuning epx files at
this point. Datastructures are fine, but details must be expected to
change, e.g. specifications of jumps, range, notes etc.
The XML structure used in v1.0 will be supported for all future releases
after that.
regards
Jens Lauritsen
EpiData Association
I have a database with 2 unique keys: stickno and randid. The CHK file
contains the following code for these fields:
stickno
KEY UNIQUE 1
RANGE 1 500
MUSTENTER
END
randid
KEY UNIQUE 2
RANGE 100 1699
MUSTENTER
AFTER ENTRY
IF (randid>899) and (randid<1300) THEN
HELP "randid must be 100-899 or 1300-1699" TYPE=WARNING
ENDIF
END
END
Despite the KEY UNIQUE commands, I found 2 records with stickno=290 and
randid==227. I believe KEY UNIQUE was present in the CHK file prior to
beginning data entry, but even if not, when attempting to open the REC
file I should receive a warning alerting me to the duplicates. This
doesn't happen when I keep the EIX file in the same directory as the
database. After deleting the EIX file from the directory, when
attempting to open the REC file I do get a warning alerting me to the
duplicates. What information does the EIX file store? I've attached it
in case you're able to determine where the error lies. I haven't
attached the database because it contains data on real patients and I
can't edit it without changing the EIX file.
Any insights would be much appreciated.
Cheers,
Suzanna Vidmar
Senior Research Officer
Clinical Epidemiology and Biostatistics Unit
Murdoch Childrens Research Institute
Royal Children's Hospital
Flemington Road Parkville Victoria 3052 Australia
telephone: +61 3 9345 6372
facsimile: +61 3 9345 6000
email: suzanna.vidmar(a)mcri.edu.au
www.mcri.edu.au <http://www.mcri.edu.au/>
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
Dear all
Since last test release of July 15th summer vacation is now over and the
following has been fixed or worked on:
a. copy-paste bugs
b. other minor issues
c. develop a scripting tool to validate function (simulate user performance)
d. WIKI documentation updated
- e.g. see:
http://www.epidata.org/dokuwiki/doku.php/documentation:program_keys
e. Critical external review of the XML structure
The next test release will follow when these aspects are all covered.
More comments below.
Comments:
Yesterday a critical review of the current XML structure for the data
files was performed with the Danish Data Archive. It turns out that a
few issues requires some changes to the XML structure (tag-attribute),
to ensure consistence and possibility of developing a schema file for
the XML. Schema files are content describing files, which will enable
other software to read the epx files and validate contents against the
formal specification.
While this is rather technical - and of no interest - to most users, it
means that with the next test release the XML structure will change
(again). If you are preparing projects for future use I recommend that
you either:
a.
- plan to export your data with current test version into stata format
- import again with the new test version (when this is ready)
or
b
look at the template principles explained in
http://www.epidata.org/dokuwiki/doku.php/documentation:templateformat
and then use the template command tool to create the epx files. A
revised template tool will be released at the same time as the next test
release.
In other words: Do not spend too much time on fine tuning epx files at
this point. Datastructures are fine, but details must be expected to
change, e.g. specifications of jumps, range, notes etc.
The XML structure used in v1.0 will be supported for all future releases
after that.
regards
Jens Lauritsen
EpiData Association
Jens & Jamie,
Thank you for suggestions time to time on Epidata programming that I am
working on. We are replacing existing disease database (specific disease)
that is in Access plateform with Epidata. The access database was not stable
over the years, so lost a chunk of data few times. Hope Epidata is the
solution. I completed most programming including several calculated fields,
some are very complex assiging risk factors. The data is in MS Excel. It has
~ 2000 data with ~ 100 variables. All the data fields in both (Epiadta QES
and Excel) systems are identical except IDNUM is extra in Epidata.
I am looking the best way to migrate excel data into the blank epidata. May
be I should convert excel to .REC file first, then import, or may be .TXT is
better. I have tested with small dataset by cerating .REC file first then
import. It did work.
Any suggestion would be appriciated.
Thanks
Bijay
On Fri, Aug 12, 2011 at 11:01 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. Re: Export EpiData to Excel - is there a solution/an
> alternative? (epidata-list(a)lists.umanitoba.ca)
> 2. relational files on epodata analysis
> (epidata-list(a)lists.umanitoba.ca)
> 3. Re: relational files on epodata analysis
> (epidata-list(a)lists.umanitoba.ca)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 11 Aug 2011 19:03:19 +0200
> From: epidata-list(a)lists.umanitoba.ca
> Subject: Re: [EpiData-list] Export EpiData to Excel - is there a
> solution/an alternative?
> To: epidata-list(a)lists.umanitoba.ca
> Message-ID:
> <23065_1313082200_ZZh0y4eF~
> 8kfp.00_4E440B57.4040905(a)uni-bielefeld.de>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hey everybody,
>
> thank your so much for your efforts and the enormous help! I need some
> time to consider your proposals and the next steps now :-)
>
> My boss has done a lot of work with Excel and she is just worried 1.
> that we have to adapt to a new system and 2. that we can't combine the
> data from the Open Office sheets with already existing Excel sheets.
>
> Thanks again and greetings,
> Nina
>
>
>
> Am 11.08.2011 17:45, schrieb epidata-list(a)lists.umanitoba.ca:
> > I suppose the starting point really is to answer the question, "What do I
> want to do with the data in Excel?"
> >
> > ? look at it in a spreadsheet view? - EpiData Analysis can do this
> (Browse)
> > ? do some simple calculations on some fields? - EpiData Analysis can do
> this
> > ? do some really complicated calculations on some fields? - just export
> some key identifying fields and the fields you need into Excel and merge the
> results back into your EpiData file
> > ? do some special analysis that is only available in Excel? - same idea,
> but I can't think of any that would use very many fields
> > ? create a database that will support mail-merge ? - you won't need many
> fields for this
> >
> > If your boss has a fixation on an old version of Excel, then you are
> limited to exporting 256 fields (columns). Excel 2010 or newer can handle
> over 16,000 columns
> >
> > Jamie
> >
> >> thank you very much! I tried to suggest that to my boss but she is not
> convinced yet. Are there any other possibilities available?
> >
> > _______________________________________________
> > EpiData-list mailing list
> > EpiData-list(a)lists.umanitoba.ca
> > http://lists.umanitoba.ca/mailman/listinfo/epidata-list
>
>
> --
> Nina-Claire Himpe
> Wiss. Mit. von Prof. Dr. Ulrike Davy
> Lehrstuhl für öffentliches Recht, deutsches und
> internationales Sozialrecht, Rechtsvergleichung
> Fakultät für Rechtswissenschaft
> Universität Bielefeld
> Postfach 10 01 33
> 33 501 Bielefeld
>
> UHG T7-109
> Tel.: 0521 - 106 2508
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 11 Aug 2011 13:59:24 -0500
> From: epidata-list(a)lists.umanitoba.ca
> Subject: [EpiData-list] relational files on epodata analysis
> To: epidata-list(a)lists.umanitoba.ca
> Message-ID:
> <6c3a19b721250cea381f09c055a1d1f1.squirrel(a)webmail.uady.mx>
> Content-Type: text/plain;charset=iso-8859-1
>
> I woul like to request a simple exaple to relate 2 files and create a new
> one using epidata analysis.
> Thank you in advance
>
> Jose Farfan
>
>
> -----------------------------------------
> "Universidad Autónoma de Yucatán"
> http://www.uady.mx/
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 11 Aug 2011 16:50:49 -0400
> From: epidata-list(a)lists.umanitoba.ca
> Subject: Re: [EpiData-list] relational files on epodata analysis
> To: epidata-list(a)lists.umanitoba.ca
> Message-ID: <BLU0-SMTP24D73CD429C739981CD0C1FD220(a)phx.gbl>
> Content-Type: text/plain; charset="us-ascii"
>
> This is quite simple. Please read the help for the MERGE command in
> Analysis.
> Here is a simple example in a zip file.
>
I woul like to request a simple exaple to relate 2 files and create a new
one using epidata analysis.
Thank you in advance
Jose Farfan
-----------------------------------------
"Universidad Autónoma de Yucatán"
http://www.uady.mx/
Dear member of the team, dear all,
I am having the following problem and would be very grateful if there
was a solution (or alternative) to it:
The data I want to export to Excel consists of approximately 960 lines
in Epidata formats (= 960 colums in .xls). As I understand EpiData (and
as the test with the used data showed) it is impossible to export more
than 256 lines to Excel (version 2003) because of the Excel 2003 column
limit . Is there any way to export the 960 lines to Excel? Or is there
another alternative I should consider?
Thank you very much in advance!
Greetings,
Nina-Claire Himpe