new test release of EpiData Manager available (paste text as fields and read qes)
Dear All
Next test release of the EpiData Manager is now ready for testing. Added functionality is: 1. load datafiels and structure to a dataform. 2. open qes files as dataform files 3. write settings to an ini file 4. paste text from clipboard to a dataform as fields (or qes)
Please discuss function in general on this list and report reproducible errors to the flyspray database
The next development phases are: a. Prevent double naming of fields on a dataform b. Develop first test release of a dedicated Entry Client. c. Add timed backup and date named zip file copy to Entry Client function. d. Add control of entry (mustenter, range, value labels) to Entry Client. e. Add multilanguage capability to dataform definition and entry client.
See http://www.epidata.dk/testing.php for the operating systems Linux, Mac and Windows.
An updated introduction document has been placed on the testing page. ----------------------------------------------------------------------
When you first start the application you will see two sections, which can be moved, edited and deleted. these contain further definitions and guidance.
Torsten Christiansen and Jens Lauritsen EpiData Association
I am quite sure everyone can understand the amount of work involved in the current rewriting and the need to focus and set the scope for development at a realistic level.
One of the aspects that I currently consider not needed is the development of an editor. Power users will each have their own preference for an editor and for the EpiData Manager we can optimise usage of the clipboard instead of developing a new editor.
Another issue is the need for documentation tools. My current understanding is that we do need: - double entry verification (comparing two files and showing differences) - count by id function (show a list of how many times a given id is contained in a number of files) - data verification according to controls built into a given data file. e.g. whether all mustenter, range and value label definitions are met - verification of keys (unique) and listing of observations not meeting the defined key
And I also think these should be part of the Manager, whereas other functions such as: codebook, listing and viewing data should be part of analysis.
Comments on these aspects and the announced development phase sequence are welcomed on this list.
The next development phases are: a. Prevent double naming of fields on a dataform b. Develop first test release of a dedicated Entry Client. c. Add timed backup and date named zip file copy to Entry Client function. d. Add control of entry (mustenter, range, value labels) to Entry Client. e. Add multilanguage capability to dataform definition and entry client.
regards Jens Lauritsen EpiData Association
I agree with this approach Jens.
I rarely use the EpiData editor as most others let you keep multiple files open without locking them. It might be good to have the ability to specify our favourite editor in preferences/options and have epidata launch that application when we want to edit or look at the output of codebook, etc. This could default to Notepad in Windows, something else in Linux and (maybe) Textedit in Mac. There seems to be no builtin plain text editor for the Mac - Textedit assumes .rtf unless you tell it otherwise.
Double entry is good, but I would not bother with the form of double entry where differences are pointed out as you do the entry. Just allow comparison of two files, as you suggest.
Agree that Manager should do the data verification after entry (will this include transformation of the data as is now possible?). Keep the Entry client to doing entry with checks.
Jamie
On 2010-07-01, Jens wrote:
One of the aspects that I currently consider not needed is the development of an editor. Power users will each have their own preference for an editor and for the EpiData Manager we can optimise usage of the clipboard instead of developing a new editor.
Another issue is the need for documentation tools. My current understanding is that we do need:
- double entry verification (comparing two files and showing differences)
- count by id function (show a list of how many times a given id is contained in a number of files)
- data verification according to controls built into a given data file. e.g. whether all mustenter, range and value label definitions are met
- verification of keys (unique) and listing of observations not meeting the defined key
And I also think these should be part of the Manager, whereas other functions such as: codebook, listing and viewing data should be part of analysis.
participants (1)
-
epidata-list＠lists.umanitoba.ca