2017 11 20.md

LD4 Community Reconciliation Working Group Kick-off Call

Monday 20 November 2017, 9:00:00 am PDT, 11:00:00 am CDT, 12:00:00 noon EDT, 5:00:00 pm BST, 6:00:00 pm CEST, 16:00:00 UTC (GMT).

• Moderator/Gatekeeper:
• Notetaker:
• Connection information: Meeting Link is https://stanford.zoom.us/j/386303946 or click Details below for more connection information (calling in, mobile connections, international numbers, etc.)

Join from PC, Mac, Linux, iOS or Android: https://stanford.zoom.us/j/386303946

Or iPhone one-tap (US Toll):  +14086380968,386303946# or +16465588656,386303946#

Or Telephone:
    Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
    +886 277 417 473 (Taiwan Toll)
    +1 855 703 8985 (Canada Toll Free)
    Meeting ID: 386 303 946
    International numbers available: https://stanford.zoom.us/zoomconference?m=ASuUAQjV9YXnKeslCiUZNE3Ja5cqdVFx

Or an H.323/SIP room system:
    H.323: 
        162.255.37.11 (US West)
        162.255.36.11 (US East)
        221.122.88.195 (China)
        115.114.131.7 (India)
        213.19.144.110 (EMEA)
        202.177.207.158 (Australia)
        209.9.211.110 (Hong Kong)
    Meeting ID: 386 303 946

    SIP: [email protected]

---

Attendees

Roy, Tim, Ryan, Ruth, Chrissy, Arwen

Agenda

• Action items from last time
  • Start prioritization of items in work areas (on spreadsheet)
  • Tool & data evaluation

---

Notes

• Started with Algorithm Writing work group on the "Work Area to Requirements Grouping" - identified some things that we thought might be high priority and discussed.
  • There seemed to be some duplication between items (e.g. rows 23 & 21, rows 13 & 16)
  • Discussed cross system identifier matching - something which could be more approachable for specification and development (less variable then string matching) and could be leveraged in a number of contexts. Arwen will create an issue
  • Discussed pre-processing of data values (row 27) as something relevant for external reconciliation. Again, this seemed like it could be a relatively achievable goal. Arwen will create an issue
  • Discussed algorithms for various types of materials and entities, and how to approach developing these. A number of specific scenarios were presented in the use cases but it may be more efficient to start with developing (or identifying) a more generic baseline algorithm and then evaluate the specific work/entity type matching scenarios against this to identify whether there are more specific criteria that would improve results. Aside from how we approach the development, we probably will also need to compile a list and possibly prioritize the scenarios (again, many but not all, were listed in the submitted use cases), and it might be worth discussing how we want to document the requirements for these (how do we document what we want the algorithm to do). Ideally the later can also be used to document what the algorithm does and so could contribute to some of the provenance & transparency feature requests. I'm not sure about what issues to create here, it depends on how we want to approach the algorithm spec work and whether we need more discussion.
• Ran out of time but suggested that people mark items in the other work areas in green that they feel are priorities to facilitate discussion.
• Briefly discussed starting to collect tools and data source's for evaluation - thought we could start making a list in a wiki page and then possibly do evaluations in an issue

Action Items

• Arwen create issues for items discussed related to algorithm writing
• Arwen create wiki page for starting to collect tools and data sources
• Arwen close submitted use cases