getodk / getodk/collect

Custom config fields/"form metadata"

Open
#443 15 comments 0 reactions 0 assignees View on GitHub
enhancement needs discussion
Dominant language
Kotlin
Stars
789
Forks
1.4k
Avg merge
4d 15h
Merged PRs (30d)
16

Description

The new "Form Metadata" activity described in #311 is awesome, and even more awesome would be the ability to define custom fields there so that data could be entered once at the app level and then included in all submissions. Examples could be a team name, region code, etc. This would prevent enumerators from having to fill out the same data over and over, thus reducing errors.

Things defined in this way would be accessible in forms via preloading, e.g. for a custom field with key `teamname`:

```

```

Additional notes:

* Keys should be forced to be unique
* Custom fields should be included in existing "bulk configuration" functionality

Contributor guide

Open the contributing guide

Research direction

Start with the Form Metadata activity described in #311 and inspect the existing bulk configuration functionality. Completion means supporting app-level custom fields with unique keys, making them available through the shown preload mechanism, and including them in bulk configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.