- EpiData-list - University of Manitoba Mailing Lists

New testversions for EpiData Manager, EntryClient and Analysis
by EpiData development and support 15 Mar '18

15 Mar '18

We have just uploaded new testversions on: http://www.epidata.dk/testing.php Analysis: 0.9.3.6- EpiData EntryClient: 4.3.0.6- EpiData Manager: 4.3.1.119 We are still approaching public releases, but still lack some aspects. Remember to ALWAYS work on copies of data. In particular with this release if you use encryption since we have updated the strength of encryption to a stricter (modernized) level - SHA512. The following changes has been made in particular in relation to securing that we meet new demands for encryption and logging in relation to the regulatory requirements. During the coming week our inhouse complete test will be applied. But please do report any aspects you find problematic or strange. In manager we have done a bit of re-arrangement of the menu's, such that defining a "key" is now part of the properties for the datasets (dataforms). On the route to open-source we have done a test of having all source code installed in Canada by Jamie Hockin, who provided an updated "means" calculation in analysis, such that this should now be more precise. This was a promising test. A list of all changes is shown below. Best wishes Jens Lauritsen & Torsten Bonde Christiansen EpiData Association, Denmark. Manager: * Jumps to fields can now also be key fields * Moved key selection from own windows to dataset properties * Added tools: Export Securitylog * Fixed several bug in exporting to Stata 13+ EntryClient: * Bugfixes related to jump * Bugfixes related to logging with Extended Access * Added posibility to mark a record as Verified - observations that are "Marked for Deletion" cannot be directly marked as verified, but MUST be unmarked from deletion first. (under Extended Access this requires READ rights on the dataset) * Added additional information to the email body if the project is setup to create an email on close. Common: * Added "Days between password change" to Extended Access projects (and enforcement thereof) * Extended logging capabilities when using Extended Access * Better handling of recent files across Manager/Entryclient/Analysis * Updated cryptography of both Single Password and Extended Access from SHA1 to SHA512 Analysis: Consequential changes of the above to ensure reading and writing files accordingly.

1 0

time variable without seconds
by EpiData development and support 14 Mar '18

14 Mar '18

Is there any way to create a time variable in a dataform that does not require the seconds to be entered (ie would accept 08:15 instead of 08:15:00) Thank you ... Ian Dohoo -- Ian R. Dohoo DVM, PhD, FCAHS Professor Emeritus - Epidemiology U. of Prince Edward Island Charlottetown, PEI C1A 4P3 CANADA dohoo(a)upei.ca

1 1

new experimental build of analysis 0.9.3.0 released today
by EpiData development and support 09 Feb '18

09 Feb '18

From today v0.9.3.0 is released at the bottom of : Http://www.epidata.dk/testing.php Notice that the commands.html and the "how to adapt your pgm" help files found in the help menu of the main window. Please test and report to this list or in case of severe problems send an email to info at epidata.dk. We do hope that there are no more bugs in the released test version. But we do also encourage you to report such errors here. More info below Best wishes Jens Lauritsen , Torsten Bonde Christiansen EpiData Association Denmark ------------------------------------------------------------------------------------------------------------------- Example: read a file change value in a variable and display a browser before and after: // ----example: read "myfile.epx"; new variable v12 s; v12:= "unknown"; browse age v12 !caption:="Data before change"; v12 := iif( age[_n] > 18, "adult", "young"); browse age v12 !caption:=("Data after change" + now()); // ... end Here it would be natural to ask, why do I need the [-n]. This is a consequence of the way the internal machinery (parser) works. We will think over and attempt to see whether it is possible to leave out this, but until further notice you need that part. We have made it easy to add the [_n] - if you press alt+n with focus in the command prompt or in the editor the sequence "[_n]" will be added. Please do remember to work on copies of data. Real data should only be used in production release versions for actual data-analysis or data management Changes from last experimental version are: Documentation * fixed errors and inconsistencies in commands.html * fixed calling error - which would not open the commands.html in IE browser Adapted syntax * valuelabels: edit vl name <type> ( value, text) ( value, text) etc. Added functionality * automatic variables and memo fields may be created * list project * funtion user(), returning defined users in a project with extended access * Altered shortcuts on MAC (Editor) Bug fixes: * merge had several issues - and should now be complete, including documentation - could overwrite mergevar * editing of !related parameters !childobs and !afterobs * errors in certain variable expansion aspects and special combinations, e.g. save a project without variables * report validate, report cby , check relate could fail. * check relate -> would indicate incorrectly that a 1-many relation was not correct. * createtime(...) will return sysmis with illegal time value

1 0

new test version of EpiData Analysis released today 0.9.2.0
by EpiData development and support 23 Jan '18

23 Jan '18

We are rapidly approaching the first pre-public test version of the new analysis, but before getting to that stage. From today v0.9.2.0 is released at the bottom of : Http://www.epidata.dk/testing.php Changes from last experimental version are: * a unified and simplified option naming convention expected to be the final choice (many options are one or two letter only, not a long word, which may be misspelled) * You may set "mark for deletion" and "verified" at observation (record level) (and remove again) * Reorder ændrer ny på visuel struktur * reorder command will also change the sequence in a saved file * unification of the shortcuts and function. e.g. exit editor and exit browser * New reports: count by (variables, eg id visitdate) , validate double entry files) * The browser now shows observations marked for deletion or verification * new functions to summarize numerical data: sum(..) and strings: concat(..) * frequency command can show confidence intervals * common naming of result variables after running variables (try: list r) * renamed set options and added some for default browser, colours etc. (to see these, issue: set - or open editor and add set from edit menu) * commands to alter the structure of projects. e.g. "un-relate" a related project, append or merge whole projects or single datasets within a given project. * fix many minor bugs and error situations, which would give a strange error. * all errors are now shown regardless of setting of: set "echo" := "on/off"". They are only hidden if you issue the set "show error" := "off"; Notice that the commands.html and the "how to adapt your pgm" references are found via the help menu in either the main analysis form or the editor. But also that several browsers may be open . Please test and report to this list or in case of severe problems send an email to info at epidata.dk In particular test data management features and the ability of the software to read all files created (rec, dta, epx, csv) . Save them again after some data-management, e.g. summation or reordering, and see in Manager or EntryClient that it actually worked. Please do remember to work on copies of data. Real data should only be used in production release versions for actual data-analysis or data management Work now continues with the table command and other issues, e.g. ability to shift from txt to html output or simple encryption and decryption of projects. Notice that without the efforts from assisting other members of the list we could not have made the software to the current level. In particular thanks to Hans Rieder and Jamie Hockin for a lot of structured testing and feed-back. best wishes Jens Lauritsen , Torsten Christiansen EpiData Association Denmark

1 0

User manual and podcast
by EpiData development and support 01 Jan '18

01 Jan '18

Dear Jens Can we have a user manual and podcast on the new analysis software? Thanks Regards Thambu ________________________________________ From: epidata-list-bounces(a)lists.umanitoba.ca [epidata-list-bounces(a)lists.umanitoba.ca] on behalf of epidata-list-request(a)lists.umanitoba.ca [epidata-list-request(a)lists.umanitoba.ca] Sent: Friday, December 22, 2017 11:30 PM To: epidata-list(a)lists.umanitoba.ca Subject: EpiData-list Digest, Vol 166, Issue 6 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. Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files) (EpiData development and support) 2. Re: Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files) (EpiData development and support) 3. New experimental Analysis for testing released - v0.9.0.15 (EpiData development and support) ---------------------------------------------------------------------- Message: 1 Date: 22 Dec 2017 07:57:56 -0000 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files) Message-ID: <20171222075756.22767.qmail(a)f4mail-235-247.rediffmail.com> Content-Type: text/plain; charset="UTF-8" Dear Hans,Sub - Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)Using Analysis for relating rec files is a good option.A PGM can easily save the updated rec files to epx files and relate also.I could save two related rec files to epx files.When I issued the Merge command,Read "D:\EpidataAnalysis0.9.0.0\FG\AgeSex2.epx";Merge FFNO !fn :="D:\EpidataAnalysis0.9.0.0\FG\FAMILY2.epx" !Table;Following  error message was dislayed; ERROR: External lookup table dataset "ds1" has a non-unique key combinationPlease use the integrity tool to get a complete list of non-unique valuesWhat is this integrity tool and how to get a complete list of non-unique values using this tool?.......................................................The following command is also not working.edit var sex !valuelabel := label_sex              !label : = "Examinee's sex";What is the need to edit Label option before conversion to epx files?Dr. Shavinder  ------------------------------ Message: 2 Date: Fri, 22 Dec 2017 09:04:26 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: epidata-list(a)lists.umanitoba.ca Subject: Re: [EpiData-list] Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files) Message-ID: <0df0bf45-05a5-21d4-9550-246df47e53f8(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Today we will give out a new experimental test version, where the check command (data integrity test) is very efficient, e.g. to find duplicates in a file check key v1 v2 v3; will tell which observations are duplicate in the combination of v1 v2 v3 In the new version colour of fonts and background is also working. Jens Lauritsen EpiData Association On 12/22/2017 08:57 AM, EpiData development and support wrote: > Dear Hans,Sub - Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)Using Analysis for relating rec files is a good option.A PGM can easily save the updated rec files to epx files and relate also.I could save two related rec files to epx files.When I issued the Merge command,Read "D:\EpidataAnalysis0.9.0.0\FG\AgeSex2.epx";Merge FFNO !fn :="D:\EpidataAnalysis0.9.0.0\FG\FAMILY2.epx" !Table;Following  error message was dislayed; ERROR: External lookup table dataset "ds1" has a non-unique key combinationPlease use the integrity tool to get a complete list of non-unique valuesWhat is this integrity tool and how to get a complete list of non-unique values using this tool?.......................................................The following command is also not working.edit var sex !valuelabel := label_sex              !label : > = "Examinee's sex";What is the need to edit Label option before conversion to epx files?Dr. Shavinder  > _______________________________________________ > EpiData-list mailing list > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list ------------------------------ Message: 3 Date: Fri, 22 Dec 2017 17:07:18 +0100 From: EpiData development and support <epidata-list(a)lists.umanitoba.ca> To: EpiData development and support <epidata-list(a)lists.umanitoba.ca> Subject: [EpiData-list] New experimental Analysis for testing released - v0.9.0.15 Message-ID: <a4e6fab4-11e3-e70d-2680-c166752f1945(a)epidata.dk> Content-Type: text/plain; charset=utf-8; format=flowed Dear all users We have released next experimental version for testing, which you may find from the page: Http://www.epidata.dk/testing.php Many issues have been fixed since the latest public test in early december. A complete list is found at the bottom. In particular we have fixed and quality assured the data integrity command: check data, check key, check relate But also many other issues, e.g. colour control. These lines will turn output and command line into yellow on black background. set "COMMANDLINE BG COLOUR"?? := "#000000"; set "COMMANDLINE FONT COLOUR" := "#FFF000"; set "OUTPUT BG COLOUR"??????? := "#000000"; set "OUTPUT FONT COLOUR"????? := "#FFF000"; Many other aspects have been fixed, e.g. search and replace in editor in windows. Next in line is the implementation of tables command and a few more issues in relation to data-management, which will then be announced as a pre-public version. Please do some testing to ------------------------------ ________________________________________ EpiData-list(a)lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list End of EpiData-list Digest, Vol 166, Issue 6 ********************************************

1 1

Merge command and rec to epx conversion
by EpiData development and support 23 Dec '17

23 Dec '17

Dear Jens,I have tested the recent experimental versionEpidataAnalysis0.9.1.5. (Windows version)GOOD PREGRESS -Colour commands for output and command lineis welcome addition. Please add similar commands for Editor also.As mentioned earlier, EpidataAnalysis0.9.1.5. is really fast. It canread files with more than 1,00,000 records easily.ISSUES REQUIRING ATTENTION -MERGE Command was tetsed with following PGM.Patient and visit epx files were used  from course of https://tbrieder.org/epidata/epidata.html//TRY.PGMcd "D:\EpidataAnalysis0.9.1.5\EX";close;read "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epx";merge idpat !fn := "d_ex01_patient" !table;save "combined10.epx" !replace;close;read "combined10.epx";  When this PGM is run it gets stuck at Merge Command. Following outputis obtained..cd "D:\EpidataAnalysis0.9.1.5\EX";D:\EpidataAnalysis0.9.1.5\EX.close;Project Closed!.read "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epx";Loaded file: D:\EpidataAnalysis0.9.1.5\EX\d_ex01_visit.epxCycle: 10 Datasets: 1 Modified: 10-11-2016 21:34:21.merge idpat !fn := "d_ex01_patient" !table;ERROR: Unable to open the file: D:\EpidataAnalysis0.9.1.5\EX\d_ex01_patientFile is corrupt or does not exist.Unable to open file "D:\EpidataAnalysis0.9.1.5\EX\d_ex01_patient"ERROR: Error loading file:Same problem I was facing with my relational database files.Hence this command needs revision..........................When rec file is read in this software, the variables and data entered do not tally.Conversion from rec file to epx file results in variable with actual data appearingunder other variables..........................Since there is no check file, Hans suggested following commandedit var sex !valuelabel := label_sex              !label := "Examinee's sex";This command (edit) is also not working.It is hard work to write such software. Surely these issues will be addressedin future releases. Keep it up.I wish you and epidata team all success and happy new year 2018.With regards,Dr. Shavinder 

1 0

New experimental Analysis for testing released - v0.9.0.15
by EpiData development and support 22 Dec '17

22 Dec '17

Dear all users We have released next experimental version for testing, which you may find from the page: Http://www.epidata.dk/testing.php Many issues have been fixed since the latest public test in early december. A complete list is found at the bottom. In particular we have fixed and quality assured the data integrity command: check data, check key, check relate But also many other issues, e.g. colour control. These lines will turn output and command line into yellow on black background. set "COMMANDLINE BG COLOUR" := "#000000"; set "COMMANDLINE FONT COLOUR" := "#FFF000"; set "OUTPUT BG COLOUR" := "#000000"; set "OUTPUT FONT COLOUR" := "#FFF000"; Many other aspects have been fixed, e.g. search and replace in editor in windows. Next in line is the implementation of tables command and a few more issues in relation to data-management, which will then be announced as a pre-public version. Please do some testing in particular of saving files after changes to variables and structures, followed by entry in EntryClient and report to the list of your experiences. Best wishes for the coming end of year festivitas and a merry christmas for those who celebrate the christmas traditions. Jens Lauritsen and Torsten Christiansen EpiData Association Denmark. Complete list: * Removed the result variable $SYSTEMDIR and replaced with the function cwd() * Editor "open file" now opens in current directory * Options may now be a global that holds other options: - new global OPT s := "!cum !d0" - freq sex !OPT // this will effectively act as freq sex !cum !d0 * Fixed a number of bugs in "check relate" and "check key" * Added additional result variables to "check relate" and "check key" * Fixed bugs in relation to names already used in sections/headings * Editor: Inserting history/set-options * "list var" and variable information (F3) now shows variables that are part of key with a "*" * Added sub-command "edit data" with option !del -> marks all record in current select for deletion * Added command "report users" * Added option !del to "browse" and "list data" to show ONLY records marked for deletion * Browser: Added shortcut "CTRL + G" which shows a dialog for jump to observation * Added SET OPTIONS for COLOUR control og OUTPUT, COMMANDLINE and Browser * Added option !output [:= "html | text"] to "save" command. This saves the output buffer to text or html. * And many minor bug fixes.

1 0

Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)
by EpiData development and support 22 Dec '17

22 Dec '17

Dear Hans,Sub - Fonts and Background (Actual thread title should be file conversion from rec to epx and relating the files)Using Analysis for relating rec files is a good option.A PGM can easily save the updated rec files to epx files and relate also.I could save two related rec files to epx files.When I issued the Merge command,Read "D:\EpidataAnalysis0.9.0.0\FG\AgeSex2.epx";Merge FFNO !fn :="D:\EpidataAnalysis0.9.0.0\FG\FAMILY2.epx" !Table;Following  error message was dislayed; ERROR: External lookup table dataset "ds1" has a non-unique key combinationPlease use the integrity tool to get a complete list of non-unique valuesWhat is this integrity tool and how to get a complete list of non-unique values using this tool?.......................................................The following command is also not working.edit var sex !valuelabel := label_sex              !label := "Examinee's sex";What is the need to edit Label option before conversion to epx files?Dr. Shavinder 

1 1

Fonts and backgrounds Epidata Analysis ver 0.9.0.0
by EpiData development and support 13 Dec '17

13 Dec '17

Dear Jens,Separate selection of Fonts in the Output, Command line and Editor isvery good feature. One can read rec file but cannot relate with other rec file.Merge command is not working with parent child rec files.Please retain the feature of choosing the background as black and white(as it was in Classical Epidata Analysis). Otherwise this feaure should change with  Windows colour scheme selection. Only white background results in lot of glare.Startup.pgm could not be located. It is faster than classical epidata analysis.It can read large data sets (more than 35,000) easily. Keep it up.With regards,Dr. Shavinder

1 2

New test release of EpiData Analysis v0.9.0.0 (experimental)
by EpiData development and support 11 Dec '17

11 Dec '17

Dear all users A test version of the new EpiData Analysis was released today. Get it from: Http://www.epidata.dk/testing.php All data management and check of data should now be ready and work similarly in EntryClient, Manager and New Analysis, e.g. help menu. Data management includes: Reading of files (rec, epx, stata, csv, clipboard), creation of new variables, labels, browsing, check data command, saving data in files (epx, stata, csv, copy to clipboard from browser), but also running pgm files with comprehensive loops etc. But since it is in development: MAKE SURE YOU WORK ON COPIES OF REAL DATA Extract the appropriate files (depending on Windows, Linux, Mac version) and make sure you maintain the folder structure. Then start epidataanalysis. The main changes since October 13th (v0.8.4.0) are: * Now all three Operating Systems are supported (Linux, Mac, Windows). * Hit F1 to get automatic search based on content (command line or editor) * observation identifier may be used, e.g. : new var id i := _n; * observations can be checked with the [_n] reference, e.g.: v1:= v1[_n-2] ; (add [_n] with alt+n in the editor or command line) * Browser shows a snapshot of data and you may open several browsers (after browse - use right click to copy or adapt data). * Complex formulations of command syntax allowed (References to variables, loops, expansions of variable names) * Font control (all windows) and custom startup.pgm for preferences * More set options to change aspects of the interface. Faster output. * Recent files are shared with Manager and EntryClient. * More commands, functions and options are added (Hit F1 to see these) example: erase "tempfile.epx" If you have not used the new analysis before, please start the software and look in the help menu (Tutorials local), where you find more explanatory files, including how to adapt old pgm files for the new syntax. To see more aspects, please see the mail from announcement of version (0.8.4.0) (http://lists.umanitoba.ca/pipermail/epidata-list/2017q4/002815.html) If problems arise please report to this list. But make sure you WORK on COPIES OF DATA until we have the first public release. It is of particular interest for us if you can challenge creation and modification of projects (epx files) with subsequent addition of data in EntryClient and view or change of structure in Manager. Our internal standard is about 500 automatic tests, but we cannot test how saved epx files work in EntryClient and Manager automatically. Best wishes Jens Lauritsen and Torsten Christiansen EpiData Association, Denmark The main changes to the command syntax are: 1. use ; at the end of each command in a pgm file 2. use := to give variables a new content . e.g. v1 := 10; 3. options are indicated with ! instead of /, e.g. freq v1 !cum ; means age !t; 4. filenames must contain extension, and enclosed in "projectmain.epx". 5. Similar aspects are grouped, e.g. list data; list variables; list datasets 6. Defining and editing variables have a common structure: new var; edit var; drop var; 7. Many additions allow comprehensive programming

1 1