Design decision for Data Entry Client
Development of the stand alone Data Entry Client is progressing and we need to take some decisions.
In short the revised setup will be such that a project manager person will use the EpiData Data Manager to define data files, to document file contents etc. whereas the actual data entry will be done with a dedicated Entry Client, which can only do entry. On the list it was suggested earlier that it is important that the entry persons can get a quick overview, e.g. by data lists, spreadsheet view of the data or a codebook. We will look at this later.
I invite you all to discuss and comment on the following aspects:
a. Show field names on entry form. Could be either: A1 Be part of the data file definition (sort of built into the datafile) A2: Defined via an ini file for the client
I tend to think that this is part of the project managers decision, and therefore it should be A1, but I am not sure. Currently this is NOT part of the data file definition, but part of the ini file for the Manager . .
b. When the Entry Client opens a data file, which record should be shown ? b1. The first one b2. The last one b3. An empty "new" record - ready for entry (as in current EpiData Entry)
Would depend on the project. I suggest we decide on b2. This shows how far entry is and the user can then issue a specific action to continue adding (e.g. ctrl+N).
We can always discuss later if some of this could be controlled by commands or specifications, but a default must be defined now.
Regards Jens Lauritsen EpiData Association
Hi Jens, Very well documented. Keep it up. Nice day Caleb Ouma
Dataworld Research
P.O Box 1984-00200 NAIROBI ________________________________
Alt. E-mail: caleb@dataworldresearch.net oumacaleb@gmail.com Skype: calebouma ________________________________
________________________________ From: "epidata-list@lists.umanitoba.ca" epidata-list@lists.umanitoba.ca To: epidata-list@lists.umanitoba.ca Sent: Tue, August 10, 2010 10:16:59 AM Subject: [EpiData-list] Design decision for Data Entry Client
Development of the stand alone Data Entry Client is progressing and we need to take some decisions.
In short the revised setup will be such that a project manager person will use the EpiData Data Manager to define data files, to document file contents etc. whereas the actual data entry will be done with a dedicated Entry Client, which can only do entry. On the list it was suggested earlier that it is important that the entry persons can get a quick overview, e.g. by data lists, spreadsheet view of the data or a codebook. We will look at this later.
I invite you all to discuss and comment on the following aspects:
a. Show field names on entry form. Could be either: A1 Be part of the data file definition (sort of built into the datafile) A2: Defined via an ini file for the client
I tend to think that this is part of the project managers decision, and therefore it should be A1, but I am not sure. Currently this is NOT part of the data file definition, but part of the ini file for the Manager . .
b. When the Entry Client opens a data file, which record should be shown ? b1. The first one b2. The last one b3. An empty "new" record - ready for entry (as in current EpiData Entry)
Would depend on the project. I suggest we decide on b2. This shows how far entry is and the user can then issue a specific action to continue adding (e.g. ctrl+N).
We can always discuss later if some of this could be controlled by commands or specifications, but a default must be defined now.
Regards Jens Lauritsen EpiData Association _______________________________________________ EpiData-list mailing list EpiData-list@lists.umanitoba.ca http://lists.umanitoba.ca/mailman/listinfo/epidata-list
On Tue, Aug 10, 2010 at 09:16:59AM +0200, epidata-list@lists.umanitoba.ca wrote:
[...]
I invite you all to discuss and comment on the following aspects:
a. Show field names on entry form. Could be either: A1 Be part of the data file definition (sort of built into the datafile) A2: Defined via an ini file for the client
A1
[...]
b. When the Entry Client opens a data file, which record should be shown ? b1. The first one b2. The last one b3. An empty "new" record - ready for entry (as in current EpiData Entry)
How about:
b4. Define this in the data file definition, in the header/meta data section.
That could even allow opening at the last record that the user was looking at, which might not even be the last, e.g. if they were reviewing data that have already been entered.
David --
David Whiting, PhD | Epidemiologist and Public Health Specialist tel +32-2-6437945 | mob +32-496-266436 | David.Whiting@idf.org
International Diabetes Federation 166 Chaussée de la Hulpe, B-1170 Brussels, Belgium tel +32-2-5385511 | fax +32-2-5385114 info@idf.org | www.idf.org | VAT BE 0433.674.528
IDF | Promoting diabetes care, prevention and a cure worldwide
Jens,
I agree that A1 is best. This is a data manager decision as it will affect the screen layout. It can be in the .ini for Manager, but not for Entry. It also works for the single user application (e.g. outbreak). (My preference in the long run would be to have some control over placement of the field name, but I don't feel strongly about this, based on what I've seen so far.)
I also agree with David on b4. Let the data manager decide what record shows. This is a 'check file' operation in current version terms.
Jamie Hockin
On 2010-08-10, at 3:16 AM, epidata-list@lists.umanitoba.ca wrote:
a. Show field names on entry form. Could be either: A1 Be part of the data file definition (sort of built into the datafile) A2: Defined via an ini file for the client
I tend to think that this is part of the project managers decision, and therefore it should be A1, but I am not sure. Currently this is NOT part of the data file definition, but part of the ini file for the Manager . .
b. When the Entry Client opens a data file, which record should be shown ? b1. The first one b2. The last one b3. An empty "new" record - ready for entry (as in current EpiData Entry)
participants (1)
-
epidata-list＠lists.umanitoba.ca