[Roadmap]: Gaia Catalog

[tibbben]

With metadata federation and catalog interoperability as broad functionality requirements:

• define workflow for assigning concept IDs and other OHDSI vocabulary terms to catalog items
• evaluate json-ld model for cross walking data between catalogs
• incorporate metadata element for external ids for federation and sharing with other catalogs
• develop workflow for creating attr_spec and geom_spec metadata elements
• develop tool to facilitate metadata entry
• visual data exploration tools
• leverage variable and layer level concept ids for cohort definition
• shopping cart style data selection -> then ETL on confirmation

[fils]

• define workflow for assigning concept IDs and other OHDSI vocabulary terms to catalog items

Is this entity resolution? Are these IDs in a controlled voc or ontollogy? If so we could
look at things like entity resulution using Relik or Gliner

• evaluate json-ld model for cross walking data between catalogs

By "cross walking between catalogs" do you mean linking? If might that just be using PIDs and
shared instances of types to allow that to be discovered in query space?

• incorporate metadata element for external ids for federation and sharing with other catalogs

More PIDs? Or is this trying to assign dereferencable IRIs for resources in the catalog?

• develop workflow for creating attr_spec and geom_spec metadata elements

Not sure what this is, need more.

• develop tool to facilitate metadata entry

Tooling UI stuff like this is hard. An easy entry point is trying to provide spread sheets with
drop lists (where possible) and then using that to generate the serialization. One could try
forms too. If there was a large set of available coding resources and the desire, one could look
at things like https://github.com/mlcommons/croissant/tree/main/editor for inspiration.

• visual data exploration tools

Again, this is a big project. I'd recommend looking first to things like
https://github.com/gleanerio/archetype/blob/master/docs/tooling.md#network-visualization
and generating products from OHDSI-GIS that work with those, for exploring the graph as a network.
Note, tools like Qlever also have
support for GeoSPARQL and can disply maps leveraging OpenStreet Map. So you could graph query with
GIS connection there.

• leverage variable and layer level concept ids for cohort definition

Out of my wheelhouse ...

• shopping cart style data selection -> then ETL on confirmation

Shopping carts are hard too.. could you provide file serializations options as a parameter to the
the download URLs and let people collect and use those themeselves?

[fils]

Made an image for this discussion at https://github.com/fils/OHDSI-GIS-Metadata-Mapping/tree/master/docs/workflow