When: 12/11/2014 at 11:00 AM EDT
Where: Google Hangout
Participants: Scott, Niamh, Clara, Mark , Larry, Ed, Carl
Recorded Video: http://youtu.be/SqDPM2dYJzc
Agenda:
- The agenda will focus on beginning to draft a workflow around the management and sharing of terminologies/metadata for a facility registry. This will build off our previous conversation with Jack Bowie from the Terminology Service community.
Outcomes:
Questions Still To Resolve
Find 1 to 2 common types of things that aren't synced
Potentially hierarchies (Admin Divisions or facility types) and lists (Types of facilities)
Admin/geographic Divisions can also be represented in Organizational entity hierarchy of CSD. Need to have bi-directional mapping between the two.
Semantics of geocodes (Level of specificity -> when a facility location is gazetted to a town vs. the building location with x meters)
AID Data Group has done some work here to define a process.
Check the Kenya MFL list
Oasis Odata spec as example (CSDL) - for lists and Geo - uses a namespace for types that have lists and geo - not sure about hierarchies (action: look at example; ping authors). http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part3-csdl.html
Steps
Explicitly scope out the that this workflow focuses on the managing of versions of code sets, not necessarily how it is then migrated and processed.
Identifying what are the code sets being used are.
Focus on some types that are problematic for versioning or misunderstood semantics. (see above)
Agree on a way to expose those types in a TS (a discovery API) to detect what it says is an appropriate terminology matches what exists
- Finally, determine a way to read/import/etc the new dictionary from the TS