Stream: IG creation
Topic: Coming rework of the IG publisher
Grahame Grieve (Aug 21 2018 at 23:28):
Now that the IGs are published, I'm turning my time to the question of forthcoming re-work of the IG publisher. These cascading options documented here:
http://wiki.hl7.org/index.php?title=IG_Publisher_Documentation#Fragment_.26_Template_Options
Are these useful? Why just not produce all the fragments, and then let the template use what it wants to use?
What would be useful, I think, is a single setting formats = xml|json etc so you say which formats the IG publisher should be producing for the IG as a whole... (in practice, I see a mix of json only, mixed xml/json, xml only, and then all formats, in that order)
Grahame Grieve (Aug 21 2018 at 23:28):
also, I have a request from a party that want to publish 70k profiles in an IG....
Sarah Gaunt (Aug 21 2018 at 23:43):
70,000??!!
Grahame Grieve (Aug 21 2018 at 23:43):
yes
Jean Duteau (Aug 21 2018 at 23:43):
how in the heck did they create 70k profiles? Variants of Observation?
Grahame Grieve (Aug 21 2018 at 23:44):
I think they are mostly observations, yes. I really need to work on observation patterns... will be doing that before Baltimore
Sarah Gaunt (Aug 21 2018 at 23:44):
And why?
Grahame Grieve (Aug 21 2018 at 23:44):
they might identify themselves here, if they want
Richard Townley-O'Neill (Aug 22 2018 at 01:09):
Could be sliced as VitalSigns is, only with a profile for every observation code in some large value set.
Eric Haas (Aug 22 2018 at 16:27):
@Grahame Grieve I proposed an observation patterns using ObsDef which was poorly received and we talked about this using forms. is that what you are talking about?
Eric Haas (Aug 22 2018 at 16:31):
Are these useful? Why just not produce all the fragments, and then let the template use what it wants to use?
I just produce them all so I never turn any off.
Eric Haas (Aug 22 2018 at 16:32):
so I don' t use this feature at all. ( of course Lloyd will be diametrically opposite :-) )
Eric Haas (Aug 22 2018 at 16:34):
What would be useful, I think, is a single setting formats = xml|json etc so you say which formats the IG publisher should be producing for the IG as a whole... (in practice, I see a mix of json only, mixed xml/json, xml only, and then all formats, in that order)
I turn off the views in my templates to reduce the clutter. but it would be a nice to have that. The fragments are still there but not 'clickable' you have to enter the url in the browser bar.
Eric Haas (Aug 22 2018 at 16:36):
In fact I kind of do this using jekyll front matter and liquing to control the layout page
Eric Haas (Aug 22 2018 at 16:37):
( if only I could get the config.yml file to actually work). Has anybody used that to set their own global parameters?
Lloyd McKenzie (Aug 23 2018 at 15:43):
Of course Lloyd is diametrically opposite :) My main reason for turning stuff off I don't use is to save on build time. Not sure how significant a savings that is though in the grand scheme of things. The other is to ensure that there's control over what appears in the IG. With fragments, if they'r enot referenced, they won't show up. But I don't think that same control exists for examples. If I don't want JSON or XML in my IG publication, then the publication process needs to ensure those don't show up - not in the zips, not on the website, etc.
Lloyd McKenzie (Aug 23 2018 at 15:45):
In my framework there's a single config file that controls whether XML, JSON and/or TTL show up. And I got config.yaml to work fine in mine...
Eric Haas (Aug 23 2018 at 20:35):
@Lloyd McKenzie I would really appreciate it if you could show me how to get Jekyll to pay attention to my config.yml file.
Grahame Grieve (Aug 23 2018 at 20:41):
i don't think it makes much difference to time; the time is all elsewhere doing validation and terminology and stuff. and I do indeed propose to leave precise control over the examples
Lloyd McKenzie (Aug 23 2018 at 21:13):
Not just the examples, but the way the profiles and value sets and other infrastructure artifacts are published too. (Not sure I agree with that, but I have at least one customer who didn't want to see JSON anywhere...)
Grahame Grieve (Aug 23 2018 at 21:15):
same rules as examples. I can't see why we would differ on that, and we don't now
Last updated: Apr 12 2022 at 19:14 UTC
