{"action":"created","issue":{"url":"https://api.github.com/repos/StraboSpot/strabo-mobile/issues/140","labels_url":"https://api.github.com/repos/StraboSpot/strabo-mobile/issues/140/labels{/name}","comments_url":"https://api.github.com/repos/StraboSpot/strabo-mobile/issues/140/comments","events_url":"https://api.github.com/repos/StraboSpot/strabo-mobile/issues/140/events","html_url":"https://github.com/StraboSpot/strabo-mobile/issues/140","id":77714545,"number":140,"title":"Workflow and Content Models","user":{"login":"jessica-azgs","id":1493985,"avatar_url":"https://avatars.githubusercontent.com/u/1493985?v=3","gravatar_id":"","url":"https://api.github.com/users/jessica-azgs","html_url":"https://github.com/jessica-azgs","followers_url":"https://api.github.com/users/jessica-azgs/followers","following_url":"https://api.github.com/users/jessica-azgs/following{/other_user}","gists_url":"https://api.github.com/users/jessica-azgs/gists{/gist_id}","starred_url":"https://api.github.com/users/jessica-azgs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jessica-azgs/subscriptions","organizations_url":"https://api.github.com/users/jessica-azgs/orgs","repos_url":"https://api.github.com/users/jessica-azgs/repos","events_url":"https://api.github.com/users/jessica-azgs/events{/privacy}","received_events_url":"https://api.github.com/users/jessica-azgs/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-05-18T16:17:10Z","updated_at":"2015-05-18T17:31:38Z","closed_at":null,"body":"From @JEAndrew :\r\n\r\nThe point work flow:\r\n\r\n1. user clicks point on the map.\r\n2. brings up menu of attitudes, sample location or spots\r\n3. tabs open: 4 tabs. 1.=details (attitudes form); 2.= General (same); 3. = rock description (kobo form); 4. Spot (same).\r\n\r\nI have the attitudes form mostly populated and I am finishing the set up for skip and display of the items. I can upload xls and csv versions of the new kobo attitude form, if that helps.\r\n\r\nthe traces work flow will be similar.\r\n\r\n1. The user draws  aline on map.\r\n2. Menu comes up: A. = trace B.= spot\r\n3. I will make a kobo form called traces that incorporates the forms we already use in one package."},"comment":{"url":"https://api.github.com/repos/StraboSpot/strabo-mobile/issues/comments/103142972","html_url":"https://github.com/StraboSpot/strabo-mobile/issues/140#issuecomment-103142972","issue_url":"https://api.github.com/repos/StraboSpot/strabo-mobile/issues/140","id":103142972,"user":{"login":"jessica-azgs","id":1493985,"avatar_url":"https://avatars.githubusercontent.com/u/1493985?v=3","gravatar_id":"","url":"https://api.github.com/users/jessica-azgs","html_url":"https://github.com/jessica-azgs","followers_url":"https://api.github.com/users/jessica-azgs/followers","following_url":"https://api.github.com/users/jessica-azgs/following{/other_user}","gists_url":"https://api.github.com/users/jessica-azgs/gists{/gist_id}","starred_url":"https://api.github.com/users/jessica-azgs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jessica-azgs/subscriptions","organizations_url":"https://api.github.com/users/jessica-azgs/orgs","repos_url":"https://api.github.com/users/jessica-azgs/repos","events_url":"https://api.github.com/users/jessica-azgs/events{/privacy}","received_events_url":"https://api.github.com/users/jessica-azgs/received_events","type":"User","site_admin":false},"created_at":"2015-05-18T17:31:38Z","updated_at":"2015-05-18T17:31:38Z","body":"We can still use the tabs but it would be easiest if only one of the tabs had a form based off KoBo forms. The Notes Tab (Tab 2) can still have ID, Notes & Photos (those can be hardcoded), unless you want ID as part of the KoBo form on Tab 1. I would guess that the Notes field can get long depending how wordy people are with their notes so may be better to keep that in Tab 2. And definitely best to have the links and groups in Tab 3, but those don't use a KoBo form either, so that's fine.\r\n\r\nIf you are going to end up repeating a lot of the same fields between the point, line and polygon forms then, yes, it might be best to make them 1 form and then let skip logic handle which fields appear. You would need to make the very first field a drop down with the selection options of point, line and polygon so you could base skip logic off of that. I can hide that from the user in the app though and determine whether it is a point, line or polygon from what they draw on the map and then apply the skip logic."}}