New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

healthsites-architecure #889

Open
markherringer opened this Issue Feb 2, 2017 · 8 comments

Comments

Projects
None yet
2 participants
@markherringer
Contributor

markherringer commented Feb 2, 2017

new architecture 1

(This copy needs to be updated to match the revised diagram..)

  1. OSM > OSM Field Worker Maps.me User > OSM
    Organisations who are consuming and sharing back data to OpenStreetMap through services like maps.me

  2. Partners > OSM
    Imports from Ministries of Health (trusted partners) running services like DHIS2
    Conflict free records inserted directly into OSM including the HS-UUID

  3. Partners > hs-db The Holding table
    Imports from Ministries of Health (trusted partners) running services like DHIS2
    Records in conflict kept in holding table for conflict resolution

  4. OSM > docker-osm The Cache > healthsites.io OSM API Client > OSM
    A service that checks OSM for updates and imports updates into healthsites.io

  5. healthsites.io OSM API Client > Record versions > hd-db The Metastore
    Updates to the cache telling the story of each record. This is the origin of the Location Validation Index framework.

  6. healthsites.io OSM API Client > OSM
    Validated records established following conflict resolution and updates received through engagement with trusted users like the Ministry of Health

@markherringer

This comment has been minimized.

Show comment
Hide comment
@markherringer
Contributor

markherringer commented Apr 27, 2017

@markherringer

This comment has been minimized.

Show comment
Hide comment
@markherringer
Contributor

markherringer commented Jun 19, 2018

new architecture

@timlinux

This comment has been minimized.

Show comment
Hide comment
@timlinux

timlinux Jun 25, 2018

Collaborator

Usage Policy tasks

To avoid having your access blocked, please discuss your requirement with system administrators either via their wiki pages or on the IRC channel prior to starting.

  • TODO Tim to contact Grant Slater to socialise
Collaborator

timlinux commented Jun 25, 2018

Usage Policy tasks

To avoid having your access blocked, please discuss your requirement with system administrators either via their wiki pages or on the IRC channel prior to starting.

  • TODO Tim to contact Grant Slater to socialise
@timlinux

This comment has been minimized.

Show comment
Hide comment
@timlinux

timlinux Jun 25, 2018

Collaborator

Batch upload tasks

  • Step 1 - Prerequisites
  • Step 2 - Community Buy-in
  • Step 3 - License approval @markherringer
  • for this we should open a ticket that on the upload form for new sites the uploader must give consent that the data will be published under OSM license and that they have the authority to do so.
  • also open another ticket (and add to our work plan) that when a user signs up on the site, they have to tick off a similar agreement that anything they edit or create directly on the site will be released under OSM license
  • Step 4 - Documentation @markherringer Task for you
  • Step 5 - Import Review - @markherringer please check with Grant if this would apply to us
  • Step 6 - Uploading - @markherringer same comment as above
Collaborator

timlinux commented Jun 25, 2018

Batch upload tasks

  • Step 1 - Prerequisites
  • Step 2 - Community Buy-in
  • Step 3 - License approval @markherringer
  • for this we should open a ticket that on the upload form for new sites the uploader must give consent that the data will be published under OSM license and that they have the authority to do so.
  • also open another ticket (and add to our work plan) that when a user signs up on the site, they have to tick off a similar agreement that anything they edit or create directly on the site will be released under OSM license
  • Step 4 - Documentation @markherringer Task for you
  • Step 5 - Import Review - @markherringer please check with Grant if this would apply to us
  • Step 6 - Uploading - @markherringer same comment as above
@timlinux

This comment has been minimized.

Show comment
Hide comment
@timlinux

timlinux Jun 25, 2018

Collaborator

Edits code of conduct

In general we will not be making batch changes / automated changes to the OSM data behind HS. When a user edits a single record we will push that straight to OSM. We should include as statement in out compliance wiki page saying that we will agree to abide with the CoC.

@markherringer TODO

Collaborator

timlinux commented Jun 25, 2018

Edits code of conduct

In general we will not be making batch changes / automated changes to the OSM data behind HS. When a user edits a single record we will push that straight to OSM. We should include as statement in out compliance wiki page saying that we will agree to abide with the CoC.

@markherringer TODO

@timlinux

This comment has been minimized.

Show comment
Hide comment
@timlinux

timlinux Jun 25, 2018

Collaborator

Step 2

Review how we will track changes. Perhaps we can use osmcha (https://osmcha.mapbox.com) to cross reference each change to a change in HS.IO.

Alternatively we need a way to propagate HS changeset ids through OSM and back to HS

Collaborator

timlinux commented Jun 25, 2018

Step 2

Review how we will track changes. Perhaps we can use osmcha (https://osmcha.mapbox.com) to cross reference each change to a change in HS.IO.

Alternatively we need a way to propagate HS changeset ids through OSM and back to HS

@timlinux

This comment has been minimized.

Show comment
Hide comment
@timlinux

timlinux Jun 25, 2018

Collaborator

When there is a change we should be able to use the WAY ID : CHANGESET ID as a unique identifier for each edit transaction.

  • @markherringer we need to establish if Aether will be able to give use back the way id, changeset id for inserts, edits and deletes
Collaborator

timlinux commented Jun 25, 2018

When there is a change we should be able to use the WAY ID : CHANGESET ID as a unique identifier for each edit transaction.

  • @markherringer we need to establish if Aether will be able to give use back the way id, changeset id for inserts, edits and deletes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment