Stream: committers
Topic: Capturing IG QA details
Lloyd McKenzie (Dec 27 2019 at 20:30):
As part of the updates to the IG publisher, we've agreed to start exposing maturity levels on the IG as a whole as well as on the individual resources. In core, we support the maturity levels by filling out a huge Google sheet. I'm wondering how we want to manage quality assessments for HL7-balloted IG content. Do we want to put it in an XML spreadsheet? Some sort of XML syntax? Something else? Any suggestions on what would make doing this as pain-free as possible would be welcome. (The reality is that tracking quality requirements on a per-artifact basis is going to come with a fair bit of pain and effort. But, given that IG content often isn't all at the same level of maturity, individual tracking is rather necessary.)
Jose Costa Teixeira (Dec 27 2019 at 20:42):
extension on each resource?
Lloyd McKenzie (Dec 27 2019 at 21:32):
That's possible, but that then imposes complexity on all of the resource editing tools (Forge, Trifolia, spreadsheets, etc.) to support maintenance of that content. And it's the sort of thing where the details of the extension are likely to evolve over time. So my leaning is to have it maintained in something else, even if we merge it into the resources as extensions as part of the publication process.
Vassil Peytchev (Dec 27 2019 at 22:38):
Google Sheets are JSON objects - would that make it possible to use Google Forms and Google Sheets as the data entry tool, and use the JSON content for publishing?
Grahame Grieve (Dec 27 2019 at 23:16):
the conversion process from a google spreadsheet to a github artifact is a challenge. I don't want to have that anymore than we already do
Last updated: Apr 12 2022 at 19:14 UTC
