Changes in 0.2-dev

README.md

@@ -29,6 +29,8 @@ Other more useful resources exist if you have general questions about the scope
 of [the Risk Data Library project](http://riskdatalibrary.org/), or are looking for a more [high-level introduction to 
 the standard and its key concepts](https://docs.riskdatalibrary.org/).
 
+* **Any suggestions of data to include in the RDL Catalog or discussions about specific data sets should be directed by email to the RDLS team / take place in the associated private repository.**
+
 ## How to contribute
 
 The [Contributors guide](CONTRIBUTING.md) covers the different ways in which you can contribute to this project to 

SteeringCommittee/Minutes Steering Committee No. 7 - 14 Sept 2023.md

@@ -0,0 +1,86 @@
+# Minutes of RDLS Steering Committee No. 7
+
+14 September 2023 / 09:00-10:30 EDT, 14:00-15:30 GMT / via Teams
+
+## Attendees
+
+Pierre Chrzanowski, Mattia Amadio, Stuart Fraser (GFDRR) 
+Rachel Vint, Jen Harris (Open Data Services)
+
+**SC members:** 
+- Paul Henshaw, GEM Foundation
+- Stephen Hutchings, JBA Risk Management
+- Nick Moody, IDF/GRMA
+
+**Absent**
+- Tiziana Rossetto, UCL EPICentre
+- Matt Donovan, ODS
+- Beat Aeberhardt, Swiss Re
+
+**Others**
+Johanna Carter (ODS)
+Hamish Patten (IFRC)
+
+**Agenda**
+- Updates to documentation and request for any feedback as you review (Stuart)
+- Tools – Availability and use of the metadata creation and validation tool (Jen)
+- Update on Fellowship projects and recent workshops (Pierre/Andy/Mattia)
+- Communications plan for the RDLS (v0.2) – overview of blogs, webinar plans and channels for communications (Pierre).
+- Request for update from Joh/Matt on Oasis integration of RDLS metadata (Joh/Matt)
+- Others?
+
+Presentation
+https://docs.google.com/presentation/d/1UnudkTN0LqS9_gKT8mLaHxkZ8TxNgeVSYMJeZfVbYBY/edit#slide=id.g149d21ab14c_0_77
+
+## Notes
+
+**Updates to documentation and request for any feedback as you review (Stuart)**
+- Request for data documentation: PH: MWI data not his, but checking. GEM data is in the Db format - knew data  commonly used by GEM would fit, but interested to see others - agriculture, etc. Suggest to make use of other data - interoperability of data where data is used by others, or produced by others - the value for GEM is not the use of RDLS internally - already document their data in internal formats. 
+PC: We should communicate on GEM involvement in RDL project - how to keep up on their progress, and how pushing for adoption / adopting the standard. 
+- NM: Value is clear but what are forces and barriers to adoption. Is adoption clear in WB, or limited to GFDRR currently? PC: Strategy in WB is to go by different sectors, projects first - framework contract for risk assessment - pre-selected set of firms. TOR requests use of RDLS when sharing outputs.
+- SF: how can we promote adoption in organisations. SH: TOR are a stick to drive takeup, but support from the RDL that eases the process would be v helpful.  PH: Convertors are helpful. Oasis convertors would be helpful. Possible for exposure. More diff for Vuln. Talking about data. HP: modular is nice, each category is clear. IFRC - our data might be able to be converted into format but in some cases it can’t - loss&damage not in the same language. Specific contexts where its 1:1 from differetn standards, examples where there are exceptions where the standard may not align. SF: follow up on examples of misalignment with IFRC.
+- PC: tooling component - SC could look at what is needed for development and adoption
+
+**Tools – Availability and use of the metadata creation and validation tool (Jen)**.
+- JH: convertor demo. Highlighting errors, link to share metadata for 7 days. 
+- SH: can we capture (download the errors) 
+- JC: does the json file get generated with errors? - JH: - yes, with errors contained
+- PH: Additional fields added? - JH: Will be added in JSON - present in the object/sheet where you added it in spreadsheet. PH: Is this what we want? Action - consider how to treat add. Fields
+- CH: what is ultimate output - for NGOs, etc? Not the tool and validation of data. PC/SF: different levels of outputs - convertor tool is to help technical level of adoption. We will produce videos to promote at higher level - how the RDLS benefits operational projects e.g. on RDLS maximising impact of data generated [this is also the carrot for WB TTLs during internal meetings].
+
+**Fellowship updates**
+- AG: Have held several Fellow workshops including SF/MA / HP and own fellows, highlighting Zia and Isa project work. Will be promoting RDLS at Colombia Uni conference, and in WB - and during a week of WB meetings in DC. PC: Dedicated workshop at WB HQ - November 14th. To incl data sprint, in full week of activities.
+
+**Communications plan**
+- From Oct 2nd (see presentation for full schedule)
+- Request for any specific work done with RDLS to go into blog of organizations in first week of Oct.
+- Invitation to present at the external webinar on work done. 
+- Video tutorials and high-level comms video
+- Stakeholder mapping - need to add names, and create links with orgs. 
+- HP: Links with HDX - could create a bolt-on, ‘would you like to convert your data into RDLS’? - could be a driver of adoption.
+- PC - yes - could provide a way to access exposure information. SF: Would want them to host RLDS metadata as first step
+- HP: agrees but lots of data types on there - may throw up areas of misalignment.
+- NM: Mapaction has a data scientist embedded in HDX - possible useful linkage?
+- CH: Would repost if SRF are tagged, wouldn’t have something on their website.
+  - Blog needs to promote benefits to end users - make it less WB focussed. How can each stakeholder use it.
+  - External webinars - already in 4 weeks - who is doing invitations
+  - Need to clarify more for Carolina
+  - Oct 10th is Swiss holiday
+  - Do we need different webinars for different audiences? Tech and high level 
+- PH: really useful to highlight different use cases with different messages. Should be clear that RDLS is bringing advantage to these communities.
+
+
+ **AOB**  
+
+  ## Actions:  
+- Document what happens with additional fields
+- Set up call with HDX
+- Set up call with IFRC - loss and damage focus.
+- Add high level video production into comms plan. Focus on communicating the benefits to sectors to drive adoption, not tools/validation level technical information.
+
+  ## Proposed agenda to include:  
+- Final planned SC meeting under Swiss Re Foundation funding
+- Communications, take-up activities since September
+- Plan for further SC involvement 
+
+

SteeringCommittee/Minutes Steering Committee No. 8 - 7 Dec 2023.md

@@ -0,0 +1,150 @@
+# Minutes of RDLS Steering Committee No. 8
+
+7 December 2023 / 09:00-10:30 EDT, 14:00-15:30 GMT / via Teams
+
+## Attendees
+
+Pierre Chrzanowski, Mattia Amadio, Stuart Fraser, Andy Garcia (GFDRR) 
+Jen Harris (Open Data Services)
+
+**SC members:** 
+- Stephen Hutchings, JBA Risk Management
+- Hamish Patten, Justin Ginetti (IFRC)
+- Carolina Hess (SwReFoundation)
+- Thomas Phillips (SwRe)
+
+**Absent**
+- Tiziana Rossetto, UCL EPICentre
+- Matt Donovan, Oasis ODS
+- Beat Aeberhardt, Swiss Re
+- Johanna Carter, Oasis ODS
+- Paul Henshaw, GEM Foundation
+- Nick Moody, IDF/GRMA
+- Rachel Vint, Open Data Services
+
+**Agenda**
+- Update on launch and RDL Fellows week, DC, November 2023
+- Current status and plans for 2024
+- Technical changes in WB Data Catalog – internal change in process but greater potential for better user access, APIs…
+- Opportunities for using RDLS outside of WB
+- Please highlight any, as we continue to work on this.
+- Update from Joh on Oasis integration 
+- Update from Steve on JBA testing of RDLS integration
+- Stuart – GRMA applying RDLS in TORs
+- Tiziana – update on MVDat
+
+Presentation
+n/a
+
+
+
+
+## Notes
+- Update on launch and RDL Fellows week, DC, November 2023
+  - Successful webinar to launch RDLS
+  - RDL presented at AAGS at U. Columbia. Fellows presented projects, RDLS presented by Mat, one fellow invited to give lecture.
+  - Successful workshop with fellows working with data in RDLS.
+
+- Current status and plans for 2024
+  - Potential funding to be announced - can support further development including risk data portal.
+    - Common platform needed to encourage network effect 
+  - GFDRR grants - c. 100 p.a. with substantial number producing risk data - mandating use of RDLS metadata and RDL Collection submission.
+  - Discussion with HDX to review their datasets, identify risk data and apply RDLS.
+  - Carolina proposal to keep SC going, to continue work and direction. Agreed by GFDRR as valuable and IFRC happy to continue. Potential lower frequency in non-development times. SwReFoudnation / GFDRR happy to facilitate
+  - GFDRR to coordinate feedback on who should attend, proposed frequency, content / direction to take.
+
+
+- Outreach
+  - UR 2024 - session submitted
+  - Paper to update from Murnane 2019.
+  - Humanitarian Networks Partnerships Week, Geneva, 6-10 May 24: **seems we cannot propose a session**
+      - https://www.unocha.org/events/humanitarian-networks-and-partnerships-weeks-hnpw
+      - The first week (29 April to 3 May) will be held remotely, the second week (6 to 10 May) will be organized face-to-face at the CICG in Geneva.
+      - Who can register sessions and exhibition stands: Only the networks and partnerships that are members of the Leading-Edge Programme (LEP), the governing body of the HNPW, are invited to organize sessions and exhibition stands at the HNPW. Please see tab "Networks and Partnerships" above for an overview of registered networks and partnerships.
+      - Who can participate in remote and face-to-face sessions:
+          - Invited persons: Invitations will be sent directly by the networks and partnerships to their members and stakeholders for the sessions they organize.
+          - Persons who did not receive an invitation: Most session will be open for public access, where also those without invitation can register to attend. Once participant registration is open, sessions can be found by keyword or organizing network/partnership in the online event program.
+          - Participant registration will be opened in February 2024 
+  - Weather and Society Conference, February 26th to March 1st 2024, online only: **May not fit social science aspect but Propose to submit, its free, online only, could do poster or presentation in RISK KNOWLEDGE session?**
+      - https://www.weatherandsociety.de/
+      - The themes and sessions of the conference will focus on the **social science contribution to the four pillars of EW4ALL and the cross-cutting enablers** which connect across and within all aspects of the early warning value cycle:
+        - Risk knowledge and management
+        - Observations and forecasting
+        - Dissemination and communication
+        - Preparedness to respond
+        - Cross-cutting enablers, particularly partnerships and locally-led action
+        - Monitoring and evaluation
+
+
+- Technical changes in WB Data Catalog – internal change in process but greater potential for better user access, APIs…
+  - Moving to Azure, data lakes, new APIs, causing delays on our data upload pipeline.
+
+- Opportunities for using RDLS outside of WB
+  - Potential to promote within SwissRe - create event with industry partners - need to propose content, participants with CH / Thomas.
+
+  - IFRC
+    - have used schema and modified for use in the Global Crisis Databank
+      - consider it well thought-out but maybe consider how it can be made more flexible.  
+    - Could push retrospective analysis of event losses back to RDL Collection
+    - 
+
+  - Oasis ODS integration: 
+    - ODS Steering Committee: no resistance and some support to adopt RDL metadata standards.
+    - There is no formal action plan yet, following the scoping report from ODS team
+    - Oasis is keen to improve model standards and accessibility.
+    - 2024: upgrade and improve free models available and make them more accessible
+      - Includes adding more model metadata linked to RDLS
+      - Enabling test of RDLS and metadata import tool
+    - Pushing the standard into Oasis and ODS relies on having some examples (public GitHub model repositories complete with metadata) and support from model developers
+
+  - Update from Steve on JBA testing of RDLS integration
+    - Tested with flood hazard data – 2 WB projects - new hazard maps (Vietnam) and climate change event sets (Tunisia) 
+    - Spreadsheet template easy to populate; Converter is simple to use
+    - Sufficient supporting documentation
+    - Requires time to become familiar with the templates and supporting information: a need for some introductory training to assist uptake 
+
+    - Spreadsheet templates:
+      - Relatively easy to complete the spreadsheets and the drop-down menus help to speed the process up. Links to the schema and code lists particularly useful for accessing documentation
+      - Thorough: no obvious missing options for flood hazard
+      - Lots of options, time-consuming to provide information for all the options listed in the spreadsheets
+
+    - Useful:
+      - toggle on the “required” fields only
+      - Company-specific project codes
+      - Clearer instructions on dataset ID
+      - Generic email (company, team)
+      - Better guidance on event set (optional tabs)
+      - Clunky jumping between spreadsheet and online resources - simple interface could be helpful
+
+    - Supporting documentation:
+      - Plenty of it, thorough
+      - New user – time required to understand all of it – a call helped, tutorial / video would be useful
+      - Potentially too many links and too much supporting information but that’s probably not a bad thing!
+
+    - .json converter: 
+      - Useful error messages helps to troubleshoot errors in the input spreadsheet templates 
+      - Helpful to list spreadsheet tab name in error message (did deliberate error testing)
+
+- Stuart – GRMA applying RDLS in TORs
+  - GRMA mandating use of RDLS in TORs - working in MDG, PAK, CRI, NGA
+
+- Tiziana – update on MVDat
+  - TR not available to give update.
+
+
+ **AOB**  
+
+
+
+## Actions:  
+- Set up next SC calls - quarterly for now.
+- Email to request feedback from SC group.
+- Attend next Tuesday 21:00 CET IFRC call
+- Set up call with IFRC in Jan 2024 - loss and damage focus, moderations to schema, following 
+- Feedback from JBA into github
+- Plan with Carolina & Thomas an event with SwReFound / SwRe to share RDLS
+- Write up paper on RDLS
+- Assess / submit sessions - Humanitarian Network Partnership Week and Weather and Society Conference.
+
+
+

SteeringCommittee/Minutes Steering Committee No.5 - 11 May 2023.md

@@ -35,11 +35,11 @@ Absent:
 
 3.  Update on Fellowship program
   * Sharing project descriptions, review for interest in collaborating / further work
-  * Arrange a fellowship workshop, in which steering committee can share their work/projects
+  * Arrange a fellowship workshop, in which the steering committee can share their work/projects
 
 4.  Update on aligning Open Data Standards and RDLS - Oasis team developing use of hazard and vulnerability metadata into Oasis models. Last meeting, requested use cases for having hazard and vulnerability standard wrapped around data in Oasis.
 
-5.  IFRC - Global Risk Databank - possiblity to use RDLS and data from Data Catalog.
+5.  IFRC - Global Risk Databank - possibility to use RDLS and data from Data Catalog.
 
 6.  Propose next SC meetings
   * Wednesday 12 July 2023
@@ -63,21 +63,21 @@ Absent:
 - Can adopt in ODS package - Johanna Carter checking what ODS needs, / doesn’t - what might be missing in RDL.
 - PH: Nasdaq “Key Facts” document provides a brief description of the most important aspects of a Model.  If Nasdaq were happy to share their template this might be useful since many OASIS vendors are already producing such documents for their models.
 - MD: Question on the integration of the ODS into RDLS - SF: lots we can learn from Oasis file structure - speaking with Joh.
-- PH: Humanitarian is still separated from the Insurance sector (humanitarian models often focus on data points such as fatalities, etc. while OASIS models can produce insured/reinsured losses).  RDLS has been designed to be taxonomy neutral. Don’t replicate or build new functions if existing in RLDS or ODS - re-use.
-- JC: it would make sense to have the Financial Terms in the RDLS exposure data given RLDS Loss component include ec/ins loss perspectives
+- PH: Humanitarian is still separated from the Insurance sector (humanitarian models often focus on data points such as fatalities, etc. while OASIS models can produce insured/reinsured losses).  RDLS has been designed to be taxonomy-neutral. Don’t replicate or build new functions if existing in RLDS or ODS - re-use.
+- JC: it would make sense to have the Financial Terms in the RDLS exposure data given RLDS Loss component includes ec/ins loss perspectives
 - Presentation of the Global Risk Data Bank by Marcus Elten
 - A project between UNDRR and IFRC - concept note
   - Middle of phase 2; A first demo 2-3 weeks
   - SteerCo includes NASA, WMO…
   - The first step is to provide a consistent database of historical event impacts - footprints, impact. 
   - SF: Ideal situation that GRD and RLDS represent the same information, GRD using RDLS metadata about historical events - GRD data into modellers to represent the event as best as possible; modellers share information beach to GRD on modelled impacts? Can SC propose some use cases to support this need?
-- CH: Data from Global Risk Datankbase could be used for parametric insurance product trigger setting (based on an understanding of past impacts)
+- CH: Data from the Global Risk Database could be used for parametric insurance product trigger setting (based on an understanding of past impacts)
 - Marcus suggested SteerCo as a place GFDRR can contribute.
 
 ## Actions
 - GFDRR to share Fellowship project descriptions.
 - Have a Fellow Workshop to share info from SC members' organisations/experiences/opportunities. AG to share workshop dates, and plan agenda.
-- ODS/Stu to log GitHub issues, email SC when bulk is done.
+- ODS/Stu to log GitHub issues, and email SC when the bulk is done.
 - Stu - set up a conversation about tax. strings. 
 - Tax type and version need to be in the metadata
 - Implementing occ/con types in separate fields - or as one string?