CSPro need to improve on CAPI for M/A and GPS recording

What would you like to see in CSPro?
Komin
Posts: 60
Joined: July 23rd, 2016, 1:27 pm

CSPro need to improve on CAPI for M/A and GPS recording

Postby Komin » December 18th, 2017, 2:03 am

Dear CSpro team,

based on my experiences with many projects by using CSEntry apps on tablet, could you please more update on these points as below to make CSEntry more professional and friendly than another software.

1). Multiply question by using Yes/No (1 or 0) as currently cspro team is using Alpha :idea:
2). GPS recording :idea:

Nice to see these update for next version as soon as possible.

Best regards,
Komin

khurshid.arshad
Posts: 315
Joined: July 9th, 2012, 11:32 am
Location: Islamabad, Pakistan
Contact:

Re: CSPro need to improve on CAPI for M/A and GPS recording

Postby khurshid.arshad » December 18th, 2017, 4:54 am

Dear Komin;

If I am not wrong, we can set a specific length in a numeric field in other applications. Your multiresposes can be more than the numeric field length. That is why the multiresponse field is in string/alpha.

"GPS Function" already exists in CSPro. Please see in CSPro help.

Best.
a.

arkagwa
Posts: 88
Joined: November 18th, 2014, 5:25 am

Re: CSPro need to improve on CAPI for M/A and GPS recording

Postby arkagwa » February 16th, 2018, 4:15 am

There is numeric technique which i normally do and it works perfect.
Say my question is (q) which meal did you take today? (multiple apply)
1. Pizza
2. Vegetables
3. Meat
4. Other

Then i code q numeric with length 1 (sub-items) because my choices are in range of (1-9) and i set occurrences=possible answers (categories)(=4 in this example). The choices will be the possible answers and NOT use YES/NO for each item. But make sure that you add an option 0=NIL in the valuesets to help data entrant to get out of the numeric variable when answers are less than possible choices (categories).

I find this very useful as compared to alpha/string variable which, when you export to SPSS or Stata its analysis is very tedious. e.g. ABC, ABC, ACD, A, B, C, CDE, in one column is very difficult to analyse you need to separate first. In numeric variables (sub-items)when exported each category choice becomes a data/variable column with labels g[1], q[2], q[3].....q[n] depending on number of possible categories/choices you coded


Return to “Feature Requests”