FHIR Chat · tagging artifacts to indicate is new or updated · ig publishing requirements

Stream: ig publishing requirements

Topic: tagging artifacts to indicate is new or updated


view this post on Zulip Eric Haas (Feb 18 2022 at 06:06):

I think it would be swell to be able to tag an artifact as new or updated so that they could be highlighted in the artifact page or a liquid generated list. via the site .data files . I prefer it live on the source files rather than the config files. but then would need to be scrubbed from the output.

view this post on Zulip Lloyd McKenzie (Feb 18 2022 at 15:02):

It would also need to be scubbed on the next release.

view this post on Zulip John Moehrke (Feb 18 2022 at 17:37):

isn't that the role of the history analysis?

view this post on Zulip Lloyd McKenzie (Feb 18 2022 at 17:59):

History analysis isn't "in your face".

view this post on Zulip John Moehrke (Feb 18 2022 at 20:45):

but, doing it twice and with different mechanism seems really counter

view this post on Zulip Jose Costa Teixeira (Feb 18 2022 at 21:18):

agree

view this post on Zulip Jose Costa Teixeira (Feb 18 2022 at 21:19):

We can have discrete or screaming ways to show what has changed, but Iif the metadata is "this has changed", the mechanisms should be the same

view this post on Zulip Jose Costa Teixeira (Feb 18 2022 at 21:20):

If there is a difference - i.e. one thing is "This has changed" and the other one is "Look at this!", this might be two different mechanims

view this post on Zulip Lloyd McKenzie (Feb 18 2022 at 22:10):

History analysis also isn't smart enough to understand "this is new" vs. "this is a renamed version of that old thing" or "that old thing was split or merged into this". My initial instinct had been the same - to generate the value. But I don't think it will work well. Also, the 'starting point' will be different depending on the release. For a ballot, what matters is the prior release or ballot. For an official release, it'd need to be the last official release - ignoring any interim ballots.

view this post on Zulip John Moehrke (Feb 18 2022 at 22:41):

right, but that is why we all have a narrative section we write about the signficant enhancements. So I am not ignorant that there will be something hand crafted.. I just am not understanding why we would want TWO automated methods, and to have both methods based on totally different things.

view this post on Zulip Lloyd McKenzie (Feb 18 2022 at 22:54):

I didn't think Eric was asking for an automated method, merely something he could insert in a resource that would result in it being tagged.

view this post on Zulip Eric Haas (Feb 19 2022 at 03:53):

Yes. I did not consider the history feature and have not looked into it. But my motivation is to alert the reader to the nee red content. If can do that with history that would be fine


Last updated: Apr 12 2022 at 19:14 UTC