GitHub Public Presence

Hi all, as discussed last week let us set aside some time to brainstorm what we require of a public presence for our datasets on GitHub.

Attendees

Establish the goal
Enumerate the high-level requirements as user stories
Review the status of IP release
Determine least effort format for FGP ingest and to support baseline dissemination

Users not experienced with GitHub
Search discovery (browse, read documentation, visualize data, download/access)
Website oriented
Community engagement component (TBD): guideline series on how to use the products (could exist here...), training materials such as videos, support for a community of practice
- UNISDR has developed a Community Engagement module that we could use (https://www.preventionweb.net/english/professional/networks/)
Principle: transparency, provenance
Principle: FAIR
Move assets in private repo(s) into a public repo.
Is this the canonical source?
Could be nested pages, linking to other repo(s)
Could live under opendrr-platform repo

As a general public member (e.g. community planner) I would like to have a single source for published assets so that I don't need to search for them or browse repo(s)
As a programmer/analyst at a provincial/territorial/municipal agency, I would like to have access to the documentation so that I can understand and replicate the workflows in my jurisdiction (e.g. GEM colleagues that want to replicate the stack/workflow/indicators)
As a risk analyst, I would like to evaluate model outputs and trace back to model inputs for review and validation
- documentation critical
- links to the assets
As a developer, I would like to have access to the data with examples of usage (i.e. integration into a GIS or web application)

CSV
GeoJSON with indicators generated from PostGIS
GeoPackage with indicators generated from PostGIS
- look into including the styling (Should Have)