Skip to content
This repository has been archived by the owner on Nov 2, 2023. It is now read-only.

Add more form properties #154

Closed
yanokwa opened this issue May 24, 2017 · 3 comments
Closed

Add more form properties #154

yanokwa opened this issue May 24, 2017 · 3 comments

Comments

@yanokwa
Copy link
Member

yanokwa commented May 24, 2017

I love the return of form properties! And that return reminds me that http://xlsform.org/ref-table/ under the settings, as some form specific options that we should consider.

  • public_key for encrypted forms
  • submission_url, mostly for Google Drive support, but folks do use it to submit to a different server than the form was downloaded from.
  • instance_name to name submissions. There could be some clever UI where you build the name by choosing from the list of data names.
  • version for versioning. We might want to move the timestamp that build puts in the form id here and then give folks the change to override.
@issa-tseng issa-tseng added this to the 0.3.3 milestone Jun 12, 2017
@issa-tseng
Copy link
Member

I'm wrapping a fix to form_title to account for Form Properties "Title on Device" into this ticket.

@issa-tseng
Copy link
Member

Okay, so all of these also necessitate changes to Build's own XML output. For version, should that only be applied to orx:version (which we currently don't output at all), or also to instance id? And if we want to modify id, should the entirety of id be equal to version or just the timestamp suffix we currently apply? What if the user supplies an invalid version and this breaks id?

I maybe propose we implement the rest of these and kick version down the road a little bit, unless you have strong answers here.

issa-tseng added a commit to getodk/build2xlsform that referenced this issue Jul 7, 2017
* this accounts for the "Title on Device" form properties setting in the
  ODK Build UI.
* progress on getodk/build#154 .
@yanokwa
Copy link
Member Author

yanokwa commented Jul 7, 2017

I like the proposal of punting on version for now because it feels like a longer conversation. I've started a discussion with some of the key players here: https://forum.opendatakit.org/t/how-is-version-used-across-the-ecosystem/8964

issa-tseng added a commit to issa-tseng/odkbuild that referenced this issue Jul 7, 2017
…t XML.

* also add orx: namespace prefix to meta/instanceID while we’re in this
  code. not sure what the penalty for noncompliance is but we may as
  well comply.
* progress toward getodk#154, but still two more properties to implement.
issa-tseng added a commit to issa-tseng/odkbuild that referenced this issue Jul 7, 2017
…t XML.

* also add orx: namespace prefix to meta/instanceID while we’re in this
  code. not sure what the penalty for noncompliance is but we may as
  well comply.
* progress toward getodk#154, but still two more properties to implement.
issa-tseng added a commit to issa-tseng/odkbuild that referenced this issue Jul 8, 2017
…t XML.

* also add orx: namespace prefix to meta/instanceID while we’re in this
  code. not sure what the penalty for noncompliance is but we may as
  well comply.
* progress toward getodk#154, but still two more properties to implement.
issa-tseng added a commit to issa-tseng/odkbuild that referenced this issue Jul 25, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants