Skip to content
Clone of ODK Collect for use in the KoBoToolbox
Branch: master
Clone or download
Pull request Compare This branch is 5 commits ahead, 1065 commits behind opendatakit:master.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci
.github
collect_app
config Moves test coverage config to jacoco.gradle Mar 10, 2018
fastlane
gradle/wrapper
.gitattributes
.gitignore updated app logos, added node script for string replacements, updated… Apr 16, 2018
.hgtags Moved tag v1.4.6 rev 1049 for testing to changeset 1fced08f31e9 (from… Jun 3, 2015
CONTRIBUTING.md
LICENSE.md Add Apache 2 license file. Nov 28, 2016
README.md
build.gradle Update jacoco to latest release v0.8.0 (opendatakit#1993) Mar 9, 2018
codecov.yml
gradlew
gradlew.bat Upgrade Gradle to work with Java 9 (opendatakit#1834) Feb 6, 2018
kobo-string-replace.js
settings.gradle Simplify gradle files Oct 6, 2016

README.md

ODK Collect

Platform License Build status codecov.io Slack status

ODK Collect is an Android app for filling out forms. It is designed to be used in resource-constrained environments with challenges such as unreliable connectivity or power infrastructure. ODK Collect is part of Open Data Kit (ODK), a free and open-source set of tools which help organizations author, field, and manage mobile data collection solutions. Learn more about the Open Data Kit project and its history here and read about example ODK deployments here.

ODK Collect renders forms that are compliant with the ODK XForms standard, a subset of the XForms 1.1 standard with some extensions. The form parsing is done by the JavaRosa library which Collect includes as a dependency.

Table of Contents

Learn more about ODK Collect

Release cycle

New versions of ODK Collect are generally released on the last Sunday of a month. We freeze commits to the master branch on the preceding Wednesday (except for bug fixes). Releases can be requested by any community member and generally happen every 2 months. @yanokwa pushes the releases to the Play Store.

Setting up your development environment

  1. Download and install Git and add it to your PATH

  2. Download and install Android Studio

  3. Fork the collect project (why and how to fork)

  4. Clone your fork of the project locally. At the command line:

     git clone https://github.com/YOUR-GITHUB-USERNAME/collect
    

If you prefer not to use the command line, you can use Android Studio to create a new project from version control using https://github.com/YOUR-GITHUB-USERNAME/collect.

  1. Open the project in the folder of your clone from Android Studio. To run the project, click on the green arrow at the top of the screen. The emulator is very slow so we generally recommend using a physical device when possible.

Testing a form without a server

When you first run Collect, it is set to download forms from https://opendatakit.appspot.com/, the demo server. You can sometimes verify your changes with those forms but it can also be helpful to put a specific test form on your device. Here are some options for that:

  1. The All Widgets form from the default Aggregate server is here. You can also try example forms and test forms or make your own.

  2. Convert the XLSForm (xlsx) to XForm (xml). Use the ODK website or XLSForm Offline or pyxform.

  3. Once you have the XForm, use adb to push the form to your device (after enabling USB debugging) or emulator.

    adb push my_form.xml /sdcard/odk/forms/
    
  4. Launch ODK Collect and tap Fill Blank Form. The new form will be there.

Using APIs for local development

To run functionality that makes API calls from your debug-signed builds, you may need to get an API key or otherwise authorize your app.

Google Drive and Sheets APIs - Follow the instructions in the "Generate the signing certificate fingerprint and register your application" section from here. Enable the Google Drive API here. Enable the Google Sheets API here.

Google Maps API - Follow the instructions here and paste your key in the AndroidManifest as the value for com.google.android.geo.API_KEY. Please be sure not to commit your personal API key to a branch that you will submit a pull request for.

Debugging JavaRosa

JavaRosa is the form engine that powers Collect. If you want to debug or change that code while running Collect, you have two options. You can include the source tree as a module in Android Studio or include a custom jar file you build.

Source tree

  1. Get the code from the JavaRosa repo
  2. In Android Studio, select File -> New -> New Module -> Import Gradle Project and choose the project
  3. In Collect's build.gradle file, find the JavaRosa section:
implementation(group: 'org.opendatakit', name: 'opendatakit-javarosa', version: 'x.y.z') {
	exclude module: 'joda-time'
}
  1. Replace the JavaRosa section with this:
implementation (project(path: ':javarosa-master')) {
	exclude module: 'joda-time'
}

Jar file

  1. In JavaRosa, change the version in build.gradle and build the jar

    jar {
        baseName = 'opendatakit-javarosa'
        version = 'x.y.z-SNAPSHOT'
  2. In Collect, add the path to the jar to the dependencies in build.gradle

    compile files('/path/to/javarosa/build/libs/opendatakit-javarosa-x.y.z-SNAPSHOT.jar')

Contributing code

Any and all contributions to the project are welcome. ODK Collect is used across the world primarily by organizations with a social purpose so you can have real impact!

Issues tagged as quick win should be a good place to start. There are also currently many issues tagged as needs reproduction which need someone to try to reproduce them with the current version of ODK Collect and comment on the issue with their findings.

If you're ready to contribute code, see the contribution guide.

Contributing translations

If you know a language other than English, consider contributing translations through Transifex.

Contributing testing

All releases are verified on the following devices (ordered by Android version):

Our regular code contributors use these devices (ordered by Android version):

The best way to help us test is to build from source! If you aren't a developer and want to help us test release candidates, join the beta program!

Testing checklists can be found on the Collect testing plan.

If you have finished testing a pull request, please use a template from Testing result templates to report your insights.

Downloading builds

Per-commit debug builds can be found on CircleCI. Login with your GitHub account, click the build you'd like, then find the APK in the Artifacts tab.

Current and previous production builds can be found on the ODK website.

Creating signed releases for Google Play Store

Project maintainers have the keys to upload signed releases to the Play Store.

Maintainers have a secrets.properties file in the collect_app folder with the following:

// collect_app/secrets.properties
RELEASE_STORE_FILE=/path/to/collect.keystore
RELEASE_STORE_PASSWORD=secure-store-password
RELEASE_KEY_ALIAS=key-alias
RELEASE_KEY_PASSWORD=secure-alias-password

To generate official signed releases, you'll need the keystore file, the keystore passwords, a configured secrets.properties file, and then run ./gradlew assembleRelease. If successful, a signed release will be at collect_app/build/outputs/apk.

Troubleshooting

Error when running Robolectric tests from Android Studio on macOS: build/intermediates/bundles/debug/AndroidManifest.xml (No such file or directory)

Configure the default JUnit test runner configuration in order to work around a bug where IntelliJ / Android Studio does not set the working directory to the module being tested. This can be accomplished by editing the run configurations, Defaults -> JUnit and changing the working directory value to $MODULE_DIR$.

Source: Robolectric Wiki.

Android Studio Error: SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

When cloning the project from Android Studio, click "No" when prompted to open the build.gradle file and then open project.

Moving to the main view if user minimizes the app

If you build the app on your own using Android Studio (Build -> Build APK) and then install it (from an .apk file), you might notice this strange behaviour thoroughly described: #1280 and #1142.

This problem occurs building other apps as well.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.