NEMO is a mobile data collection and analysis web application.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Kevin Cooper 7edad3a260 Explicitly remove bin/yarn so webpacker doesn't run it 4 weeks ago
.github/workflows 12029: Install inside of transformer for CI 1 month ago
.idea/runConfigurations Commit auto-updates to IDE configs 11 months ago
.tx Translation updates 8 months ago
app 12029: Hound, polish, cleanup, clarify 1 month ago
bin Explicitly remove bin/yarn so webpacker doesn't run it 4 weeks ago
config 12029: Hound, polish, cleanup, clarify 1 month ago
db 12029: Fix specs that rely on 'odk' as default 1 month ago
docs Add enketo upgrade instructions for v13 4 weeks ago
lib Bump minimist from 1.2.5 to 1.2.6 in /lib/enketo-transformer-service (#918) 1 month ago
public it works! yay! yaygit status 9 years ago
script Initial import. 11 years ago
spec 12029: Add permissions spec 1 month ago
vendor/assets 12029: Successfully load vendor print styles 1 month ago
.browserslistrc 10375: Re-run rails webpacker:install 3 years ago
.env Clarify .env port instructions 5 months ago
.env.production 11568: Add .env.production with NODE_ENV default 2 years ago
.env.test 11737: Add spec for notifier 1 year ago
.erdconfig stuffff 7 years ago
.eslintignore 9538: Split out vanilla vs. react ESLint configs 4 years ago
.eslintrc.yml 12053: Upgrade linters to attempt fix CI issue 9 months ago
.gitignore 12029: Init enketo-transformer-service under lib 1 month ago
.hound.yml 11093: Update rubocop to resolve dependency conflict 2 years ago
.nvmrc 12053: Upgrade node v10 => v16, including webpacker 9 months ago
.rspec 874: Gem cleanup and rspec tweaks 6 years ago
.rubocop.yml 12142: react to errors 6 months ago
.ruby-version 7817: Upgrade to Ruby v2.7 2 years ago
.scss-lint.yml 12029: Exclude new sass from hound 1 month ago
.stylelintrc Auto-fix a few hounds 9 months ago
.test.swp 9606: Improve handling of hidden things in ODK rendering 3 years ago
AUTHORS cleaned up root dir 9 years ago
Gemfile 12029: Dynamically transform the form to render 1 month ago
Gemfile.lock 12029: Dynamically transform the form to render 1 month ago
LICENSE Initial commit 9 years ago
README.md Clean up some docs links 1 year ago
Rakefile 10355: Run rubocop --safe-auto-correct globally 3 years ago
VERSION Bump version to 13.0 [skip ci] 4 weeks ago
babel.config.js 10375: Use default babel presets for webpacker 4 3 years ago
config.ru 11091: Auto-correct a whole new batch on v0.91 2 years ago
package.json 12029: Patch upgrade enketo in case it fixes it 1 month ago
postcss.config.js Yarn upgrade 6/n: Remove unnecessary postcss dependencies 9 months ago
yarn.lock 12029: Patch upgrade enketo in case it fixes it 1 month ago

README.md

NEMO

NEMO is a mobile data collection and analysis web application. Originally designed for the Carter Center, it can be used in many different contexts for data collection.

Consider NEMO if you need:

  • Integrated form design
  • Standardized form sets
  • Multiple data entry paths, including web, ODK Collect, and SMS
  • Multiple mission/project management
  • Advanced user management with multiple permission levels
  • SMS broadcasting
  • Custom, real-time reporting
  • Offline operation in poorly-connected areas

To learn more about the history and goals of the project, visit the project site. You can also learn more about The Carter Center here.

Documentation

Usage

See the NEMO Documentation for help on using your new NEMO instance!

Production Setup

You can follow the production setup guide to set up an instance on an Ubuntu server. For production scenarios, Sassafras Tech Collective also offers managed production instances. Contact them for details.

Contributing

NEMO is 100% open-source. We would like you to be part of the community! We accept and encourage contributions from the public. You can start by filing a bug report or feature request using a Github issue. Pull requests are also welcome, but discussing things first in an issue is always a good idea.

See the development environment setup guide to get started with the code. Contributors may also find our architecture guide and auto-generated Entity-Relationship Diagram (ERD) useful.