opensrp / opensrp-server-configs Goto Github PK

• Add supply catalog table as defined in here

• The table should store most of the data in json with only the search fields being saved on their own columns

Strip configs for dependencies that have been removed

• ActiveMQ
• MySQL
• Quartz
• Maven properties
• Motech
• Couchdb Lucene
• Ziggy

• Add Migration scripts for Unique Id table.

• The table should be moved from MYSQL to PostgreSQL

Add server version on json tables

• event
• client
• report
• location
• structure
• location
• plan
• task
• settings
• view configuration

Related to opensrp/opensrp-server-core#366

• Enable schedule under sms-notifications profile

• Query structures with radius from coordinates

• Query family details

• Make residence field on Client JSON index-able on client_metadata

• Upgrade postgres on travis to 10 and install Postgis 2.4

• Scripts for manually installing Postgres, the Travis image has older JSON-C Libraries breaking the Geoqueries

Create table creation scripts for Team module tables

• organization
• practitioner
• practitioner_role
• organization_location
• organization_plan

• Add Keycloak Account URL Config

• Add Keycloak Realm Config URL

• Allow Configuration of the scheduled Tasks under applicationScheduler so that one can configure the duration the tasks run

• Add a maven profile to disable scheduling so that scheduling is done in 1 node of horizontally scaled nodes

Tables:

1. user
2. user_role
3. users_catchment_area
4. location
   function: core.get_location_tree
   view: core.vw_location

Fields:
event_metadata
district
division
branch
Village
event
district
division
branch
Village
provider_id
event_type
form_submission_id
base_entity_id
client_meta
address1
address2
address3
village_id
district
division
branch
village
client
server_version
base_entity_id
district
division
branch
village
base_entity_id

Add numerical PK to organization_location to simplify assignment

Rename the settings table scripts they are using the timestamp of last year, its not possible to execute them for existing deployments

20180904141214 ...pending... create settings table.sql
20180904141237 ...pending... create settings metadata table.sql
20181012141507 ...pending... add settings metadata columns team id team location id and provider id
20181012145616 ...pending... alter settings metadata column identifier remove constraint

Create core.template table with the following fields

Template table (core.templates)
Id (int) id
Template Id - (int unique) (identifier)
Template (Json) (template)
Type (String) (e.g. plan)(type) - in case we want to have templates for other entities in future
Version - (int) (version)

• Define the Callback URL so that when generating the tokens the call back URL is restricted

• Upgrade Spring beans to Spring 5
• Remove motech configuration
• Remove couchdb profile and persistence beans configuration

• make location tag name unique

• replace bigint with bigserial

Avoid creating tablespaces again, if they already exist, to prevent the mybatis migration scripts from failing (not good forcing the scripts to continue if one migration fails).

Since the changelog table is within the opensrp database, while tablespaces live outside this database, we end up in issues if the database is recreated (while the tablespaces still exist).

• Add location Tags tables as per below
  table : location_tag
• id auto increment bigint primary key
• name varchar primary key
• Description varchar

table : location_tag_map

• location_id bigint
• location_tag_id bigint

• Define Oauth2 database creation scripts

• Define Oauth2 default client configs

• Strip out Schedules and Configs as they will not be used hence forth

In order to support versioning of locations we need to make the following adjustments to the location metadata table

• Add a version column
• Remove unique constraint on the geojson_id field
• Add a unique constraint on (geojson_id, vresion) fields

Add an index on the server_version field for the following tables :-
core.event_metadata
core.task_metadata
core.location_metadata
core.structure_metadata

Currently we have a problem with the current organization table. If one revoked assignments for today its not possible to create another assignment for today.

The solution involves

• Adding a check constraint such that to_date is always larger than from_date

• Delete unique constraint organization_location_organization_id_location_id_plan_id_key

• Add a duration dateRange column that will store the duration

• Create an index for organization_id, location_id, plan_id, duration

• Create an exclusion constraint on organization_id, location_id, plan_id, duration such that we can't have overlapping durations

Current default setting setting makes the server fail on start up

• Enable district report generation cron schedule under the district-report profile

Create core.plan_processing_status with the following fields :-

Id id
Plan Id FK plan_id (nullable)
Event Id FK event_id (not null)
Template Id FK template_id (Points to core.templates.identifier) (not null)
Status status ( (null|initial - 0) | processing - 1 | complete 2)
Here we can store it as a Postgres Enum. Should be expressive but still efficient as ints.
Date_created date_created timestamp (only on insert)
Last_updated date_updated timestamp (insert, update record)

• Remove couchdb configuration

• Make identifier & filename unique

Create sequence for generating server versions for

• Events

• Clients

• Locations

• Structures

• Tasks

• Plans

• Settings

• View configuration

• Stock

• Reports

• Populate the Sequences with the current Max server version

Following the discussions here it is necessary to:

• Add Settings' schema migrations
• Add Settings' data migrations