Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change Highlighting on Sample forms so geotrace is white #691

Closed
wonderchook opened this issue Sep 15, 2016 · 14 comments
Closed

Change Highlighting on Sample forms so geotrace is white #691

wonderchook opened this issue Sep 15, 2016 · 14 comments
Assignees
Milestone

Comments

@wonderchook
Copy link
Contributor

wonderchook commented Sep 15, 2016

In the documentation we instruct users to only modify the "white" parts of the xlsform. They should be able to change the geometry collection type so that needs to also be white.

image

/cc @bethschechter

@wonderchook wonderchook added this to the Sprint 8 milestone Sep 15, 2016
@wonderchook
Copy link
Contributor Author

@clash99 below are the updated forms. I don't think I have access to update them though.

standard_cadasta_questionnaire.xlsx
minimum_cadasta_questionnaire.xlsx

@clash99
Copy link
Contributor

clash99 commented Sep 15, 2016

@wonderchook: will do, have the ones linked to from the documentation also been updated? I hate that we have to do it in two places but can't think of another way right now...

@wonderchook
Copy link
Contributor Author

@clash99 not yet. That is something @bethschechter can do. Maybe we should update the links in the documentation to point at the ones in S3. Would that work?

@clash99
Copy link
Contributor

clash99 commented Sep 15, 2016

I think so but s3 has no versioning. Is that an issue?

@wonderchook
Copy link
Contributor Author

I think it would be okay. I think we want to be using the same files they find in the platform and the documentation.

@clash99
Copy link
Contributor

clash99 commented Sep 15, 2016

Files updated:

I noticed the documentation now uses the terms basic and expanded. I think the questionnaire note in the platform should be using the same terminology and we should even update the file titles to match. Is this change official? Its an easy change but keeping everything in sync is the challenge.

@bethschechter
Copy link

@clash99 @wonderchook rad! I had been linking to the Google docs but this is so much better. Thank you!

@wonderchook
Copy link
Contributor Author

@bethschechter thoughts on the language? I'm inclined to say we use standard and minimum since that is what the files say. And I don't think it matters too much

@bethschechter
Copy link

@wonderchook I like minimal vs. minimum, but that's my only thought
Also, I think I remember seeing that someone may change the standard form? David perhaps?

@wonderchook
Copy link
Contributor Author

let's stick with standard and minimum. Regarding the form being changed we should do that as part of releases, so we'll leave things the way they are now for the release on Monday.

@bethschechter
Copy link

ok, so for the docs, don't link to these new forms? or wait until Monday?

@wonderchook
Copy link
Contributor Author

Link to them now. I more meant we wouldn't be changing them again until the next release.

@bethschechter
Copy link

ok copy. thank you!

@clash99
Copy link
Contributor

clash99 commented Sep 15, 2016

Cool - looks like we can mark this one complete. Let me know if you need any assistance with the files @bethschechter or if we do decide on terminology updates. Thanks all!

@clash99 clash99 closed this as completed Sep 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants