Provide Sample XLSForm to Users

[wonderchook]

Add a link to the "Project Details" page to a sample XLSForm and documentation

Here is the form to use as the sample.
Minimum_cadasta_questionnaire_0.2.xlsx.

[wonderchook]

this needs to happen in conjunction with @fhpichel's platform update

[wonderchook]

@fhpichel we need a default sample form to use for this. Could you put something together?

[wonderchook]

moving to Sprint 8, waiting on @fhpichel

[clash99]

The documentation link in the details is broken. Are there instructions to accompany the sample form?

[wonderchook]

This link is a better one: http://docs.cadasta.org/en/08-XLSForms.html

[clash99]

Should we rename "questionnaire" to "data collection form" across the platform?

[fhpichel]

My vote would be yes

On Fri, Sep 2, 2016 at 4:48 AM, Chandra Lash [email protected]
wrote:

Should we rename "questionnaire" to "data collection form" across the
platform?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#403 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOME7bM02IehFDlol_dy02EGp-5RAB78ks5ql45qgaJpZM4JKh87
.

[ian-ross]

@fhpichel One thing we talked about some time ago was having a glossary for names of things in the platform (and also, probably separately, for land terms that everyone in Cadasta should know). There are a number of competing factors that go into choosing the names for things in the platform: clarity, correctness, lack of ambiguity, translatability and "friendliness" are only some of them. We have a lot of discussions within the dev team about what to call things, but it seems like it's really something we should hand off to you. What do you think? We tell you what it is, you tell us what it is (or should be) called...

[fhpichel]

@ian-ross agreed. I know we'd discussed that general glossary a while back, and certainly a need to be consistent / accurate within the platform. @clash had started on a glossary for the platform - best thing to do would be buil off of that? https://docs.google.com/document/d/1Xrn-VUhY0xIpdD4URdf_uafgGlgoGntj486Jl9fVOts/edit#heading=h.j9xpg26t020b

[ian-ross]

That's a good place to put things.

[clash99]

Please review and let me know if this is what we want to say:

Does it need more or less prominence? I could add a little icon to draw attention to the spreadsheets if needed. Let me know.

Sidenote: The user guide document we link to still has some "add image here" type of notes that we should clean up before the release.

[clash99]

Hmmm, I didn't start the glossary (maybe @wonderchook) but definitely a good idea! We should make sure that the user guide is using the same language (http://docs.cadasta.org/en/) or if the public facing and internal terms are different, note that in our internal glossary. It will be helpful in the long run.

@fhpichel - any feedback on the screenshot above?

[wonderchook]

Couple things:

1. Let's not change the labels in the platform right now.
2. @dpalomino as the product owner should be responsible for this. Yes he could get input from @fhpichel + @nastynoel but this really part of the vision of the platform. It also needs to fit appropriately into the branding/communications we are doing generally.

[dpalomino]

btw, I think we could update the standard questionnaire, for instance to include the new "geotype" capability (to select among geoshape, geotrace, etc). I will try to take a look and create a new version...

[wonderchook]

@dpalomino that is fine. We need it to be finalized before the end of the sprint since we will make it a regular file and save within the platform.

[clash99]

Updated screenshot for feedback:

[wonderchook]

"For assistance with questionnaires view our user guide. To help you get started to samples have been provided a minimal questionnaire and a standard questionnaire."

I'm thinking we should reuse the term questionnaire even though it is a bit repetitive. Thoughts?

[fhpichel]

I think we can get rid of the second use of questionnaire, ie ""For assistance with questionnaires view our user guide. To help you get started to samples have been provided a minimal and a standard questionnaire." @clash99 text and screenshot look good

[clash99]

Should these sample files be linked to in google docs like in the user guide or should we copy them into the platform and link there? For the second option, we will need to maintain the current file. The first option keeps it all in one place.

Let me know. Thanks!

[wonderchook]

@clash99 I think we should have a regular file people can download. I think how to download the file from Google Docs might not be obvious to all users.

[dpalomino]

I agree, I think a regular xlsx file would be easier. I still need to provide the sample file including the capability to select geoshape, geotrace, etc.

[clash99]

@dpalomino I am going to use the current one for now but its easy to update. We should make sure to update the one in google docs and in the platform together. Let me know when the new sample form is available.

[clash99]

Added xlsx versions of the form to our s3 bucket so we can update the form anytime without having to coordinate with a code release.

Updated text and links on project add and edit pages.

[wonderchook]

This all looks good to me.