Stream: ig publishing requirements
Topic: Importing resources
Jose Costa Teixeira (Jan 06 2022 at 14:00):
https://github.com/HL7/ig-template-base/issues/173
One way to do this could be:
- add an IG parameter or extension (on ig.definition.resource?) which indicates that the resource is to be downloaded (e.g. a valueset)
- the ant script can spot that, download and add to the resources and that's it (is it?)
Jose Costa Teixeira (Jan 06 2022 at 14:00):
comments?
Lloyd McKenzie (Jan 06 2022 at 15:41):
I think you'd want a regular 'resource' entry - Things like title, definition, grouping, order of appearance, etc. would all matter in terms of generating the table of contents, artifact lists, etc. The trick would actually be deleting the resources themselves so they weren't present in the resulting IG package - as they'd collide with the ones in the imported package.
Jose Costa Teixeira (Jan 06 2022 at 17:07):
Lloyd McKenzie said:
he trick would actually be deleting the resources themselves so they weren't present in the resulting IG package - as they'd collide with the ones in the imported package.
@Lloyd McKenzie you mean deleting the jsons/xmls in the package?
Jose Costa Teixeira (Jan 06 2022 at 17:08):
I would want the resources to be processed, like expanding the valuesets... but indeed after that they should not be in the final package.
Jose Costa Teixeira (Jan 06 2022 at 20:30):
is there a way to exclude some resources from appearing in the final package?
Grahame Grieve (Jan 06 2022 at 20:55):
no.
Lloyd McKenzie (Jan 06 2022 at 21:01):
More specifically, "not yet" :)
Grahame Grieve (Jan 06 2022 at 21:05):
it's not a simple proposal either. none of this that you imagine is easy. an IG is a web. the node lives embedded in the web, bi-directional links between if and it's peers, millions of them
You want to take a node (well, a set of nodes) from one web, and "copy" it into another. But what happens to all the bi-directional links? I try to think through I could make this work, and I simply can't imagine how I could even approach this. There's a reason why things work how they do
Lloyd McKenzie (Jan 06 2022 at 21:25):
Yeah. The hyperlinking is the real pain. When does a reference resolve to the source of truth location and when does it resolve to the localized location. Including when you then derive a child IG from an IG that "imported" content from its parent. Does the link in the grandchild point to the page in the parent IG or the grandparent IG. Suppressing the XML and JSON files from the published package is the easy part.
Jose Costa Teixeira (Jan 06 2022 at 21:56):
pinging @Luke Duncan
Jose Costa Teixeira (Jan 09 2022 at 08:19):
Is it an option to "import" the resources and not suppress them, but simply mark them as "This is just a copy, this is defined elsewhere"? i.e. a flag that can be used by the UI and by the tools?
Lloyd McKenzie (Jan 09 2022 at 16:48):
Not without messing up everyone's package handling. And again, suppressing the inclusion of stuff in the package isn't the big problem. The hyperlinking is.
Last updated: Apr 12 2022 at 19:14 UTC
