Table of Contents
Cases services for GDI.
- REST endpoint for uploading federated case descriptions
The general reasoning behind this solution is that
- a citizen can expect to be given a normalized, standardized and homogenized view of her involvment with a go (a Citverning entityy for example)
- the government has internallyu a plethora of various processes and software systems supporting dialogs (i.e. cases) with citizens
- Onboarding of case management systems should NOT rely on direct, ad-hoc runtime integration but rather frequent imports of current state in respective case management system
- Each case managament system exporter is responsible for
- publishing intervals
- data safety and governance (GDPR etc)
In order to run, some environment variables must be defined. This is easiest to do by
- ensuring there exists a local
.envin the project root - copy content from .env.example and change values to what gives meaning
- Improve testcoverage (MongoDB being an external dependency is currently a obstacle)
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
Distributed under the MIT License. See LICENSE for more information.