Stream: IG creation
Topic: Composed IGs
Jose Costa Teixeira (Jun 20 2019 at 12:13):
Are there yet any examples of
1. IGs further constraining other IGs (e.g. element is optional in core, mandatory in IG 1 and with a specific value in IG2)
2. IGs consisting of other IGs. Perfect example would be what we could have in IHE: the Pharmacy Framework contains the base IHE IG (front page etc.) plus a set of IGs - prescription, medList, MedFormulary, ...
?
Lloyd McKenzie (Jun 20 2019 at 12:21):
First is really about profiles, not IGs, and yes I've got lots of profiles that are 3, sometimes even 4 levels deep for derivation
Lloyd McKenzie (Jun 20 2019 at 12:25):
Second, you can kludge a set of IGs to behave like they're a single IG, but the base URLs will be different for each IG. You can however have a single IG that's organized into sections.
Grahame Grieve (Jun 20 2019 at 19:22):
IGs consisting of other IGs. Perfect example would be what we could have in IHE: the Pharmacy Framework contains the base IHE IG (front page etc.) plus a set of IGs - prescription, medList, MedFormulary
Depends on what you think 'contains' means. Do you mean 're-aliasing the canonical URLs'?
Jose Costa Teixeira (Jun 21 2019 at 07:54):
No necessarily re-aliasing, i think. Say I have one IG at ihe/pharm/presc and another at ihe/pharm/admin. Is there a way to have an ig at ihe/parm that acts as a frontpage/navigation?
Jose Costa Teixeira (Jun 21 2019 at 07:56):
not sure if related: ideally, none of those IGs would need to contain an index.html, or credits, or ... Those would all be appended by "adding" the IHE base IG to the presc and admin IG.
Jose Costa Teixeira (Jun 21 2019 at 07:59):
Rationale for the above: editors should work on their content (editor1 works on presc, editor 2 works on admin), and each can build that section locally. IHE works on the "common content" which then is added when the publisher glues all those IGs together.
Jose Costa Teixeira (Jun 21 2019 at 07:59):
@Lloyd McKenzie can i see one example of derived profiles?
Lloyd McKenzie (Jun 21 2019 at 11:54):
Look at the genomics2 reporting ig
Lloyd McKenzie (Jun 21 2019 at 11:57):
The scope of an IG is driven by the final publication, not who's working on what. With source control it's easy for everyone to work on their own bits. You'd still want the individual builds to check cross-references/dependencies.
Jose Costa Teixeira (Jun 21 2019 at 20:05):
true but i am looking at how to allow "partial" builds to be done independently
Jose Costa Teixeira (Jun 21 2019 at 20:06):
better: maintained independently
Grahame Grieve (Jun 21 2019 at 20:06):
just make a wrapping IG that refers to the others. Why complicate things?
Jose Costa Teixeira (Jun 21 2019 at 20:08):
i think that is what i am after - "refers to others": put the urls in the html content of the wrapper? or is there any other mechanism?
Grahame Grieve (Jun 21 2019 at 20:09):
well, you can list the other guides in the dependencies
Lloyd McKenzie (Jun 22 2019 at 02:21):
Partial builds are going to have cross-references that are broken - which down the road is going to create pain when integrating. Why not build the whole thing? Running the whole IG is going to be a matter of a few minutes for even a complex IG - and mere seconds if you leave it in continuous mode. (We manage largely without partial builds for the core spec which can take 40 minutes+)
Jose Costa Teixeira (Jun 22 2019 at 05:52):
Thanks. We must always build the whole thing (well, github will). These partial builds would be to enable people to work on their scope - different editors in different domains, possibly in offline mode, previewing their result before attempting to merge.
Jose Costa Teixeira (Jun 22 2019 at 05:56):
I was asking for examples to see what is being done on these areas and reuse or explore further as needed
Jose Costa Teixeira (Jun 22 2019 at 05:58):
for the wrapping IG, this means we put some Liquid(?) to produce the HTML based on the dependsOn entries? (Basically build a table of Contents)?
Jose Costa Teixeira (Jun 22 2019 at 06:01):
if so, the only question i have for now is : how to have standard content defined by "head office" and inherited by all "sub" IGs - title page, glossary, etc.
Jose Costa Teixeira (Jun 22 2019 at 06:03):
we can put some examples in github to make these questions more concrete.
Lloyd McKenzie (Jun 22 2019 at 12:05):
In theory, you could put all of the 'standard' stuff in the 'template' - though that would mean that each of the linked IGs would have distinct pages for glossary that said the same thing.
Grahame Grieve (Jun 22 2019 at 19:38):
I still don't see what the point of all this is. What does it gain over a cover sheet that references the IGs?
Last updated: Apr 12 2022 at 19:14 UTC
