- EpiData-list - University of Manitoba Mailing Lists

export to spss
by epidata-list＠lists.umanitoba.ca 11 Feb '09

11 Feb '09

Hi to All, I have a very simple question: when I am trying to export data to spss, the export menu transform the .rec files into .sps files, ie syntax and not .sav files, ie data files. Any idea why? Thanks for your help Best Regards Jean-Francois Dr Jean-Francois Trani Leonard Cheshire Disability and Inclusive Development Centre University College London 4 Taviton Street London WC1H 0BT Tel: +44 (0)20 7679 4886 Fax: +44 (0)20 7388 2291 Email: j.trani(a)ucl.ac.uk Website: www.lcdisability.org/idc Thank you for thinking of the environment before printing this message

1 1

Simple question
by epidata-list＠lists.umanitoba.ca 11 Feb '09

11 Feb '09

I am fairly new to epidata and wonder if someone can give me some advice on the following task: I am trying to determine if there is any significance in the difference between the number of days hospital outbreaks of norovirus last as against the length of community outbreaks. Is that something I could do in epidata, if so, which function would I use? Thanks Shakeel ----------------------------------------- ************************************************************************** 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

Link updata to learning/teaching material in portuguese
by epidata-list＠lists.umanitoba.ca 11 Feb '09

11 Feb '09

Lauritsen, Recently, I realized that the web adress to the Epidata Entry learning/teaching material in Portuguese changed. Therefore, the link right beside the Epidata entry portuguese file download is broken. Ther correct link from now on is: http://www.pesquisaclinica.ipec.fiocruz.br/cgi/cgilua.exe/sys/start.htm?inf… Best regards, -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Re: EpiData-list Digest, Vol 64, Issue 4
by epidata-list＠lists.umanitoba.ca 11 Feb '09

11 Feb '09

Hello Dr Jean-Francois! That is the default epidata export to SPSS . if you want to have access to the file in .sav format, please follow the procedure. 1. Launch your spss software. 2 Go to file menu ->Open-> Syntax. 3. In the syntax window, select all and click on run. With this steps you can have you files in data file(i.e .sav) instead of the syntax file. regards Mensah On Tue, Feb 10, 2009 at 6:00 PM, <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. export to spss (epidata-list(a)lists.umanitoba.ca) > > > ---------- Forwarded message ---------- > From: epidata-list(a)lists.umanitoba.ca > To: epidata-list(a)lists.umanitoba.ca > Date: Tue, 10 Feb 2009 16:14:13 +0000 > Subject: [EpiData-list] export to spss > Hi to All, > I have a very simple question: when I am trying to export data to spss, the export menu transform the .rec files into .sps files, ie syntax and not .sav files, ie data files. Any idea why? > Thanks for your help > Best Regards > Jean-Francois > Dr Jean-Francois Trani > Leonard Cheshire Disability and Inclusive Development Centre > University College London > 4 Taviton Street > London > WC1H 0BT > > Tel: +44 (0)20 7679 4886 > Fax: +44 (0)20 7388 2291 > Email: j.trani(a)ucl.ac.uk > Website: www.lcdisability.org/idc > Thank you for thinking of the environment before printing this message > > > ________________________________________ > EpiData-list(a)lists.umanitoba.ca > http://lists.umanitoba.ca/mailman/listinfo/epidata-list > > -- SEDZRO KOJO MENSAH P.O.Box AS 387 Ashaiman -Tema Ghana House : +233-22-300789 MOBILE : +233-244-458788 -------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

re: export to spss
by epidata-list＠lists.umanitoba.ca 10 Feb '09

10 Feb '09

Hi to All, > I have a very simple question: when I am trying to export data to > spss, the export menu transform the .rec files into .sps files, ie > syntax and not .sav files, ie data files. Any idea why? Thanks for > your help Best Regards Dr Jean-Francois Trani , London. The explanation is quite simple. SPSS, SAS and other commercial software companies like M$ are using closed (proprietary) data formats, which they are not documenting. Therefore we cannot export to .sav format. This is in contrast to e.g. EpiData or Stata, where the file formats are fully documented and available for general download. I suggest you write an e-mail to SPSS and ask why they have a secret data file format. I would be astonished if they even answered your mail. The system of closed formats is even more strange. Earlier we had (in my hospital department) license for SAS for some years (cost around 1200 Euro per year for one PC) for about what EpiData Analysis can do. And now we cannot even use our licensed exe files to read the data again...... This is one of the reasons why we develop EpiData Software. ... For users in extensive need of converting data I suggest to look at the EpiC utility we develop or you can look at StatTransfer, which is working quite well and has the policy "once paid - use as long as you like". Kind regards Jens Lauritsen EpiData Association

1 0

SPSS export
by epidata-list＠lists.umanitoba.ca 10 Feb '09

10 Feb '09

Did you try running the syntax to see what happens? My guess is that you going to have a good surprise!!! -- Abraço forte e que a força esteja com você, Pedro Emmanuel

1 0

Re: EpiData / External systems Integration
by epidata-list＠lists.umanitoba.ca 08 Feb '09

08 Feb '09

Mark from TriSano asked on the list about how to best integrate analysis with other systems. The whole issue of integration has a lot of room in the EpiData Project and a number of tools are already capable of solving various aspects of this. E.g.: 1. EpiC: Batch data conversion, documentation, validation, backup, encryption 2. EpiData Analysis: Reporting systems for repeated analysis. 3. Documentation and examples - see the documentation part of the main website. - in particular study the technical documents. The documentation for EpiC is available from the documentation site and the conversion process of this year for EpiData Analysis and EpiData Entry adds to the diversity of integration possibilities. I expect the whole documentation for this to be ready later the coming year, but would in general say that the path follows this line for using EpIData Analysis with data created in other systems. The first thing would be to know whether exported csv files from the other system can be read. If not we could extend the import routines based on the experiences. Errors or inconsistencies can be reported to the Mantis database. Looking forward to a possible collaboration in this sense. (I will contact TriSano directly off list.). regards Jens Lauritsen EpiData Association

1 0

EpiData / TriSano Integration
by epidata-list＠lists.umanitoba.ca 06 Feb '09

06 Feb '09

To introduce myself, I am the Program Manager for TriSano - an open source, next generation disease surveillance and outbreak management application: http://www.trisano.org We just finished planning for TriSano 1.1 and one item we are in the process of determining is if there is a statistical package we should integrate with. EpiData seems to have potential. I thought I would reach out to you to see if you could point us in the right direction for the best way to do this with EpiData. I cc'd a number of my TriSano collaborators. Thanks in advance, Mike -- Mike Herrick Program Manager, Collaborative Software Initiative mike(a)csinitiative.com M: +1 971.340.0302 O: +1 503.295.7970 Extension: 104 F: +1 503.295.7789 1 SW Columbia Street, Suite 640 Portland, Or 97258 http://www.csinitiative.com

1 0

Double entry for a longitudinal study
by epidata-list＠lists.umanitoba.ca 28 Jan '09

28 Jan '09

I am preparing a double entry verification dataset for a longitudinal study; each participant has 6 follow-ups. Obviously, I'd like the double entry to compare the original entry with the correct follow-up number. For example, ID 100 has 6 follow-ups. I'd like to compare the original entry of follow-up 6 for ID 100 to the new entry of follow-up 6. As far as I know, you can only use ONE identifiable number to compare each entry, which makes double entry for a longitudinal study inconvenient. Is there a way to use both the ID number as well as the follow-up number while doing double entry? Thank you for your time and attention! Lindsay Lindsay Iser, M.A. University of South Florida Florida Mental Health Institute Department of Aging and Mental Health 13301 N. Bruce B. Downs BlVd. MHC 1403 Tampa, FL 33612 Tel-(813)-974-1975 Fax-(813)-974-1968

1 1

Definition of copyrights for EpiData software and documentation
by epidata-list＠lists.umanitoba.ca 28 Jan '09

28 Jan '09

One of the topics for decision on the pathway to open-source of the software is declaration of copy-rights. Formally the copy-right of current products lies with the EpiData Association in combination with the authors of documents etc, which in principle is defined as the sum of persons involved (users, developers, initiators, contributors), but in practice a core group of more influential persons. See the credit pages of the website. There are an abundance of various software open-source/freeware/,..... formulations of copyrights and license principles. Basically as I see it there are three considerations a. By releasing the software one does not take responsibility for errors, timeloss or other losses by using the software (protection against claims from users). b. Someone else should not take the documentation and or software and use for their own purpose without proper referring to those who created the various parts. c. How can we protect the development for future use without restrictions imposed by patents, licensing or similar. And how can we make sure to keep it from being "taken over" under changed conditions. I am not asking for a lengthy discussion of this on this list, but should anyone have viewpoints on the topic let us know. Currently I am favouring the use of this one: "Creative Commons Attribution-Non-Commercial-Share Alike 3.0 Unported Licence" which can be seen at: http://creativecommons.org/licenses/by-nc-sa/3.0/ as well in English as many other languages. The "Unported" means not translated. Kind regards Jens Lauritsen EpiData Association

1 1