Dear Open Foris Community, We struggle with the following problem regarding Collect and later the data analysis of the collected data. We have a code list for habitat features of our trees and the field teams can choose up to 10 variables at the same time. The problem at the moment is that they are transferred into the database in the order they were clicked on in the field and not chronologically into the columns with the applicable numbers. Is there any easy solution to this? We just thought that it would be easier if we didn’t have to do this manually during the cleansing phase. This is what we would wish for it to look like. (see table 1) https://drive.google.com/drive/folders/0B1GL4ASXM8jjYmRYQVFzZGlTZ0E At the moment it looks like this: (see table 2) https://drive.google.com/drive/folders/0B1GL4ASXM8jjYmRYQVFzZGlTZ0E But of course we are open to other ideas to solve this issue, we assume others have struggled with similar attributes. Possibly our approach is overcomplicating the whole process. Thank you for your help! asked 14 Jun '18, 09:05 beka |
Hi Beka! answered 14 Jun '18, 11:48 Stefano (OF) ♦♦ |
Hello Beka, I offer another solution. I assume that in your code list for habitat features there are more than 10 options. Anyway, create 10 (code) attributes for your entity, hab1..hab10. Set them as Not required, and add custom checks for hab2..hab10, as follows I am missing the custom error message in this example but that you can add as needed. This is not giving from Collect exactly that table what you are looking for, but in the data analysis you can get frequencies for categories in hab1..hab10 as necessary. Regards, Lauri answered 14 Jun '18, 14:42 Lauri (OF) ♦♦ Still as a comment: solution above is clumsy from the data entry point of view! It is lacking the advantage doing multiple selections at one time.
(14 Jun '18, 14:52)
Lauri (OF) ♦♦
|
Beka, OF Team programmer can help in that question regarding error message. I have - again - a bit different solution: add habitat selections into a calculated text field. This additional text field (Dist_txt below) can be set invisible (deselect Show in entry form). Use function shown below When exporting the data into CSV, all selections goes into one field, which requires parsing in R or Excel. -Lauri answered 14 Jun '18, 16:27 Lauri (OF) ♦♦ |
Dear OF team, Thanks for your help. I tried to follow the instruction you sent and I faced on the following problem (see the link): https://drive.google.com/drive/folders/0B1GL4ASXM8jjYmRYQVFzZGlTZ0E Thanks again, Best, Beka answered 14 Jun '18, 15:44 beka |