First sprint for first presentation to Infrastructure call

[Sigfried]

Sprint 1 decided

Candidates for sprint 1

• [x] #120
• [x] #113
• [x] #115
• [x] #121
• [x] #122
• [x] #118
• [x] #116
• [ ] #123
  • [ ] D3.js-type expandable nodes?
  • [ ] concept set inclusion
  • [ ] Venn diagrams (#119) -- Harold: I would suggest a further visualization: a Venn diagram summarizing the table we're looking at.
• [x] #117
• [ ] #112
  • [ ] codeset_id, version
  • [ ] author, reviewer, etc.
  • [ ] provenance, limitations, etc.
  • [ ] arbitrary metadata with formatting mechanism so card layout isn't bound to N3C cset metadata
• [x] #114
• [ ] Allow useful sorting of concepts -- but then what happens to hierarchy?

As of 2022-09-22:

Marking up this image of where TermHub CSet Comparison stands as of 2022-09-20:

A week earlier:

[joeflack4]

Oh wow, lots of detail. Can discuss more tomorrow.

If they don't find this table as useful as another type of visualization (e.g. a tree), than some of these improvements will be moot. But I do like these suggestions.

[Sigfried]

The new data structure should be easier to work with. http://127.0.0.1:8000/cr-hierarchy?codeset_id=818292046|484619125|400614256

[
  {
    "concept_id": 317009,
    "concept_name": "Asthma",
    "level": 0,
    "parent": -1
  },
  {
    "concept_id": 4119298,
    "concept_name": "Late onset asthma",
    "level": 1,
    "parent": 317009
  },
  ...

Partly because it's more flexible than the one we're using now, I think

[hugwuoke]

@joeflack4 This might be ready to close as well.

[joeflack4]

I think you're right. Even though some unclosed sub-issues, this 'first sprint' is long completed, and much has changed since. I forgot that I wrote that initial page with all the X's and O's, lol.