FHIR Chat · IG releases · IG creation

Stream: IG creation

Topic: IG releases

Jose Costa Teixeira (May 07 2020 at 11:00):

I want to make an "official" release of one of my IGs. Is there any example of one so that I can see how it's done?

Grahame Grieve (May 07 2020 at 12:54):

there's plenty of examples - the process is not well documented but I have to run through it with @Ted Klein tomorrow

Oliver Egger (May 07 2020 at 14:52):

for our swiss ig we use the following steps for publication: https://github.com/ahdis/k8s-fhir.ch#publish-an-implementation-guide-ch-xyz-with-a-version-eg-010

Jose Costa Teixeira (May 07 2020 at 15:00):

that is interesting. I will check it for publication.

Jose Costa Teixeira (May 07 2020 at 15:18):

do you know how do I change this?
image.png

Lynn Laakso (May 07 2020 at 15:21):

Is that "the yellow box" at the top of the pages? It will be populated in an "official" release by the publication tooling when I put it out on the website. CI build fills it in automatically.

Jose Costa Teixeira (May 07 2020 at 15:23):

Thank you. This is not an HL7 Intl IG, it is an HL7 Belgium IG - will that also work?

Jose Costa Teixeira (May 07 2020 at 15:24):

In other words, do you also publish the HL7 Belgium IGs? I would like those to be hosted (also) locally on our site (assuming that is OK)

Lynn Laakso (May 07 2020 at 15:26):

No I don't. Not sure how those are published.

Jose Costa Teixeira (May 07 2020 at 15:29):

I haven't seen any guidance.

Grahame Grieve (May 07 2020 at 19:47):

the -publish-update step does that

Jose Costa Teixeira (May 07 2020 at 20:00):

i guess -folder is the output folder?

Jose Costa Teixeira (May 07 2020 at 20:00):

and where is the fhir-ig-list that i should point to?

Jose Costa Teixeira (May 07 2020 at 20:00):

(those are the things it asks me)

Grahame Grieve (May 07 2020 at 20:02):

this is my documentation that Lynn follows here: https://confluence.hl7.org/display/FHIR/Process+for+Publishing+a+FHIR+IG

Grahame Grieve (May 07 2020 at 20:11):

the process I'll be following with @Ted Klein to set up UTG for first publication is:

IG:

• Get the IG itself right. Then build with -publish flag

Web site:

• create an empty folder
• define publish.ini (there's only one per web site, but UTG is terminology.hl7.org)
• create an empty package-list.json (only the headers, no entries, per https://confluence.hl7.org/display/FHIR/FHIR+IG+PackageList+doco) then add a list entry for the ci-build for your IG
• copy in the history repo at https://github.com/HL7/fhir-ig-history-template
• choose the sub-folder that the IG is going to live at. HL7 uses \YYYYMMM or \[milestone] or you could use \[Ver] or anything else
• copy the IG into the subdirectory you chose
• optional, if this is a milestone (it is for UTG): copy the IG to the root folder that has the publish.ini. Say yes to overwrite files
• edit the package-list.json file, create a publication object in the list array, and fill out the details
• if you did a milestone release update current (note for future use: only one entry can have current : true , + the ci-build is current:true too)
• then make a clone of the IG-registry repo
• then run the -publish-update, and check the output for issues, and also check the IG that the publish box has been updated appropriately
• copy the folder to the server

Jose Costa Teixeira (May 07 2020 at 20:25):

what is "define publish.ini"? A file with only the location in it (you mean terminology.hl7.org as a url, right) ?

Jose Costa Teixeira (May 07 2020 at 20:25):

and where do i find fhir-ig-list.json (will i need it?) ?

Grahame Grieve (May 07 2020 at 20:56):

the publish ini is something like this:

[website]
style=fhir.layout
url=http://hl7.org/fhir
server=asp-new
org=HL7, Inc

[feeds]
package=package-feed.xml
publication=publication-feed.xml

Grahame Grieve (May 07 2020 at 20:59):

style={fhir.layout - magic value}
url={the URL this is known by on the web}
server={the server that is running - affects the redirects. one of apache | litespeed | asp-new}
org={stated organization for RSS feeds}

[feeds]
package={where to generate the package RSS feed}
publication={where to generate the publication RSS feed}

Grahame Grieve (May 07 2020 at 21:03):

fhir-ig-list.json is in https://github.com/FHIR/ig-registry. you need to get a clone of that repo, and then point -publish-update at that file. it will update the file with the correct entries for the IGs it finds, and then you can make a PR for the repo

Jose Costa Teixeira (May 07 2020 at 21:22):

and my ig will become part of that list, is that it?

Grahame Grieve (May 07 2020 at 21:24):

yes. and then that shows up here: https://registry.fhir.org/guides

you will need to edit the file by hand after the run to fill in the missing category

Jose Costa Teixeira (May 07 2020 at 21:25):

This is great info. I will start with step 1 - clean & trim my IG.

Jose Costa Teixeira (May 07 2020 at 21:25):

Should I take some notes to help in documenting for others (I assume we don't have a walkthrough yet)?

Grahame Grieve (May 07 2020 at 21:25):

sure. I haven't documented this, no.

Jose Costa Teixeira (May 08 2020 at 09:38):

@Etienne Cantineau @Robin Bosman this is interesting for us

Jose Costa Teixeira (May 15 2020 at 17:42):

I got this working (i will need to practice to make sure I can do it without looking at the sheet)

Jose Costa Teixeira (May 15 2020 at 17:42):

a few questions:

Jose Costa Teixeira (May 15 2020 at 17:45):

image.png

Jose Costa Teixeira (May 15 2020 at 17:48):

1. I know 2 is the sequence, but where does Ballot 1 come from?

Jose Costa Teixeira (May 15 2020 at 17:48):

(v2020May is correct, it is my version)

Grahame Grieve (May 15 2020 at 17:49):

all of it comes from package-list.json

Jose Costa Teixeira (May 15 2020 at 17:50):

2. I tried to change ballot to preview and normative, did not accept

Grahame Grieve (May 15 2020 at 17:50):

since you are saving a text file, 'did not accept' probably needs some clarification

Grahame Grieve (May 15 2020 at 17:51):

what is your "sequence" value?

Jose Costa Teixeira (May 15 2020 at 17:51):

the publisher did not accept that value

Jose Costa Teixeira (May 15 2020 at 17:51):

my sequence in the example above was 2

Jose Costa Teixeira (May 15 2020 at 17:52):

i am trying now with "normative" and no sequence to see the error I got

Grahame Grieve (May 15 2020 at 17:52):

have you read the documentation?

Jose Costa Teixeira (May 15 2020 at 17:53):

yes, this,
https://confluence.hl7.org/display/FHIR/FHIR+IG+PackageList+doco
...

Jose Costa Teixeira (May 15 2020 at 17:54):

and this
https://confluence.hl7.org/display/FHIR/Process+for+Publishing+a+FHIR+IG

Jose Costa Teixeira (May 15 2020 at 17:56):

I got also some information from @Oliver Egger which was precious just for me to understand the flow.

Jose Costa Teixeira (May 15 2020 at 17:57):

Exception in thread "main" java.lang.Error: unknown status normative
at org.hl7.fhir.igtools.publisher.utils.IGReleaseUpdater.state(IGReleaseUpdater.java:414)

Jose Costa Teixeira (May 15 2020 at 17:57):

this is the error I got

Grahame Grieve (May 15 2020 at 17:57):

sequence should be something like "1st STU" that stays constant across the set of releases leading towards a major milestone

Jose Costa Teixeira (May 15 2020 at 18:00):

I did not understand "Groups all the ballot publications and the final publication for the ballot sequence" so tbh I just left any value there, I did not think it was critical until the publisher "told me" it was needed

Jose Costa Teixeira (May 15 2020 at 18:01):

but I can change that. Does that have any impact on the "normative"?
What is the relation between this and the IG's releaselabel parameter?

Jose Costa Teixeira (May 15 2020 at 18:03):

and finally, I run this with parameters -folder an -root both pointing at my ig's root. I'm not sure that is right - Oliver's docu says it should be on the output folder, but if I do that, it doesn't work because my publish.ini is not in the output folder

Grahame Grieve (May 15 2020 at 18:10):

not the output folder. You copy the output folder into the maintained web folder, in one or two places, and then -publish-update is used on the web folder

Grahame Grieve (May 15 2020 at 18:10):

don't know what you mean by 'the "normative"'. Nor do I know what the releaselabel parameter is

Jose Costa Teixeira (May 15 2020 at 18:20):

IG Package list documentation says

status: the status of the publication - one of:
ci-build - the continuous integration build release (not stable)
preview - frozen snapshot for non-ballot feedback
ballot - frozen snapshot for ballot
trial-use - official release with 'trial use' status
update - official release with 'trial use' status - posted as an un-ballotedSTU update
normative - official release with 'normative' status
trial-use+normative - official release with mixture of trial use and normative content

Jose Costa Teixeira (May 15 2020 at 18:20):

Looking at the code, perhaps this has changed (i can update the confluence page in that case)?
"release" works

Jose Costa Teixeira (May 15 2020 at 18:24):

and this is in the template - perhaps also needs updating:
"IG must include a definition parameter with a code of 'releaselabel'. Value can be 'CI build' or some other status"

Grahame Grieve (May 15 2020 at 18:26):

apparently I updated this and didn't keep the code up to date. The relevant java code is:

private String state(JsonObject ig, JsonObject version) {
    String status = JSONUtil.str(version, "status");
    String sequence = JSONUtil.str(version, "sequence");
    if ("trial-use".equals(status))
      return decorate(sequence);
    else if ("release".equals(status))
      return "Release";
    else if ("qa-preview".equals(status))
      return "QA Preview";
    else if ("ballot".equals(status))
      return decorate(sequence)+" Ballot "+ballotCount(ig, sequence, version);
    else if ("draft".equals(status))
      return decorate(sequence)+" Draft";
    else if ("update".equals(status))
      return decorate(sequence)+" Update";
    else if ("normative+trial-use".equals(status))
      return decorate(sequence+" - Mixed Normative and STU");
    else
      throw new Error("unknown status "+status);
  }

It would be great if you could fix the doco

Grahame Grieve (May 15 2020 at 18:26):

presumably releaselabel should be consistent with it

Jose Costa Teixeira (May 15 2020 at 18:33):

i'll fix the wiki and ping you to revise the descriptions

Jose Costa Teixeira (May 15 2020 at 18:34):

for releaselabel : should I also add to the IG parameters page? it is not there.
and I guess the publisher does not really cross-check them?

Jose Costa Teixeira (May 15 2020 at 18:50):

updated documentation
https://confluence.hl7.org/display/FHIR/FHIR+IG+PackageList+doco
https://confluence.hl7.org/display/FHIR/Implementation+Guide+Parameters

Jose Costa Teixeira (Jun 14 2020 at 11:17):

I'm getting something I don't recall if I missed last time:

 version 2020May path http:\\hl7belgium.org\fhir\2020May not found (canonical = http://hl7belgium.org/fhir, path = http://hl7belgium.org/fhir/2020May)

Jose Costa Teixeira (Jun 14 2020 at 12:07):

what should I check for this?

Grahame Grieve (Jun 14 2020 at 19:35):

you have a mismatch between your local file set and the absolute path

Grahame Grieve (Jun 14 2020 at 19:35):

and the version specific pat h

Jose Costa Teixeira (Jun 15 2020 at 10:27):

(deleted)

Jose Costa Teixeira (Jun 15 2020 at 21:18):

Grahame Grieve said:

the process I'll be following with Ted Klein to set up UTG for first publication is:

IG:

• Get the IG itself right. Then build with -publish flag

Web site:

• create an empty folder
• define publish.ini (there's only one per web site, but UTG is terminology.hl7.org)
• create an empty package-list.json (only the headers, no entries, per https://confluence.hl7.org/display/FHIR/FHIR+IG+PackageList+doco) then add a list entry for the ci-build for your IG
• copy in the history repo at https://github.com/HL7/fhir-ig-history-template
• choose the sub-folder that the IG is going to live at. HL7 uses \YYYYMMM or \[milestone] or you could use \[Ver] or anything else
• copy the IG into the subdirectory you chose
• optional, if this is a milestone (it is for UTG): copy the IG to the root folder that has the publish.ini. Say yes to overwrite files
• edit the package-list.json file, create a publication object in the list array, and fill out the details
• if you did a milestone release update current (note for future use: only one entry can have current : true , + the ci-build is current:true too)
• then make a clone of the IG-registry repo
• then run the -publish-update, and check the output for issues, and also check the IG that the publish box has been updated appropriately
• copy the folder to the server

I followed these steps and created a repo step by step to show what I did and to check what I have done wrong

Jose Costa Teixeira (Jun 15 2020 at 21:19):

https://github.com/costateixeira/test-ig-publication/commits/milestone

Jose Costa Teixeira (Jun 15 2020 at 21:19):

not sure if this helps, but having traceable changes helps me

Jose Costa Teixeira (Jun 15 2020 at 21:20):

at this moment I get an error:

Problem with C:\ImplementationGuides\Publication\test-ig-publication\test-ig-publication\core\.\2020Jun\package.tgz: missing url
Problem with C:\ImplementationGuides\Publication\test-ig-publication\test-ig-publication\core\.\2020Jun\package.tgz: fhirVersions value mismatch (expected null, found 4.0.1
java.lang.NullPointerException
        at org.hl7.fhir.igtools.publisher.utils.IGPackageChecker.check(IGPackageChecker.java:101)
        at org.hl7.fhir.igtools.publisher.utils.IGReleaseUpdater.updateStatement(IGReleaseUpdater.java:265)
        at org.hl7.fhir.igtools.publisher.utils.IGReleaseUpdater.check(IGReleaseUpdater.java:142)
        at org.hl7.fhir.igtools.publisher.utils.IGWebSiteMaintainer.execute(IGWebSiteMaintainer.java:82)
        at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:7388)

Jose Costa Teixeira (Jun 16 2020 at 05:50):

silly me, I had made the repo private. I have now made it public

Jose Costa Teixeira (Jun 16 2020 at 06:49):

I don't know how to fix these issues:

1. package.tgz: missing url
2. package.tgz: fhirVersions value mismatch (expected null, found 4.0.1
3. NPE

Jose Costa Teixeira (Jun 16 2020 at 06:51):

same after I update the source package-list so that the package contains the fhirVersion

Oliver Egger (Jun 16 2020 at 22:09):

@Jose Costa Teixeira fhirversion needs to be written lowercase in package-list.json, see https://github.com/costateixeira/test-ig-publication/pull/1

Jose Costa Teixeira (Jun 17 2020 at 04:02):

this is great. thank you

Jose Costa Teixeira (Jun 17 2020 at 04:03):

now I got it working (after struggling with the -publish parameter

Jose Costa Teixeira (Jun 17 2020 at 04:03):

the only thing I need now is to make the history page also follow the IG's template

Jose Costa Teixeira (Jun 17 2020 at 04:17):

The history html page is hardcoded to the hl7 template

Jose Costa Teixeira (Jun 17 2020 at 04:21):

at a first glance, one way of applying the ig's template could be to
create a history.xml page in the template, let jekyll take care of that as it is taking care of the others

Oliver Egger (Jun 17 2020 at 06:19):

the history page is dynamically created from package-list.json (if you have an old ig and go to his history it shows you also the new version, so you cannot use directly jekyll). the last time we used it, it had a dependency on the webserver, for our ig's we have overwritten history.html with a javascript version, see https://github.com/ahdis/ig-template/blob/master/content/history.html if interested.

Grahame Grieve (Jun 17 2020 at 07:02):

the history page is generated from history.template. You can do what you want to that

Oliver Egger (Jun 17 2020 at 07:05):

thanks @Grahame Grieve , i have to revisit our publication, I have missed that step

Jose Costa Teixeira (Jun 17 2020 at 08:05):

history.html has different scripts and less content (menu, breadcrumbs) than the other pages. It's easy to manually apply the template, but will be harder to automate that than I thouhgt.
Anyway templating the history page is something I'd do once per project, so I don't think it's worth automating it for now.

Jose Costa Teixeira (Jun 17 2020 at 08:06):

I'm going to create a fresh repo with an accompanying document with steps from beginning to end. This can serve as instructions (and hopefully as a script to automate some parts)

Jose Costa Teixeira (Jun 17 2020 at 08:08):

question: which IG should I start with?
I started with the sample-ig but I had to trim it down because the resources had some urls that were conflicting with my base url, and there were spreadsheets in there.

Jose Costa Teixeira (Jun 17 2020 at 08:08):

any suggestion?

1. truncated sample ig
2. any other ig?

Jose Costa Teixeira (Jun 17 2020 at 08:09):

I will do this for IHE later - can also start with an empty IHE repo as an example, or a Belgian IG repo... but perhaps best to keep it in the family.

Jose Costa Teixeira (Jun 17 2020 at 11:11):

ok one final question:
Problem with C:\ImplementationGuides\Publication\ig-publication\website\.\package.tgz: expected url http://hl7belgium.org/fhir/core/2020Jun but found http://hl7belgium.org/fhir/core
I get this message now, after:

1. in my IG source folder, build with -publish http://hl7belgium.org/fhir/core/2020Jun, copy output to website\2020Jun\
2. in my IG source folder, build with -publish http://hl7belgium.org/fhir/core, copy output to website\
   is this the right way to do it?

Jose Costa Teixeira (Jun 17 2020 at 11:11):

during these steps, my package-list.json is

{
    "package-id" : "hl7.be.fhir.core",
    "title" : "Sample IG",
    "canonical" : "http://hl7belgium.org/fhir/core",
    "introduction" : "The introduction that should appear in the FHIR IG registry",
    "list" : [
        {
           "version" : "current",
            "desc" : "Continuous Integration Build (latest in version control)",
            "path" : "http://hl7belgium.org/fhir/core",
            "status" : "ci-build",
            "current" : true
           },
           {
            "version" : "2020Jun",
             "desc" : "2020 June Release",
             "path" : "http://hl7belgium.org/fhir/core/2020Jun",
             "status" : "ballot",
             "date" : "2020-06-15",
             "fhirversion" : "4.0.1",
             "sequence" : 1,
             "current" : true
            }
        ]
}

Jose Costa Teixeira (Jun 17 2020 at 11:20):

if I don't do step 2 above and I build with publish..../2020Jun and copy to website\, it does not complain, but then the history page does not point to the right location

Jose Costa Teixeira (Jun 17 2020 at 11:23):

image.png
i.e. this link should point to core/2020Jun but it points to core

John Moehrke (Jun 17 2020 at 15:14):

Jose Costa Teixeira said:

any suggestion?

1. truncated sample ig
2. any other ig?

Likely start from scratch. sample ig is got lots of history that weighs it down.

John Moehrke (Jun 17 2020 at 15:15):

is this new sample going to be FSH centric?

Jose Costa Teixeira (Jun 17 2020 at 15:22):

FSH-centric - that shouldn't change the publication.

Jose Costa Teixeira (Jun 17 2020 at 15:23):

If the question is however - is this sushi-centric? - I will do it for the canonical toolset. I presume sushi will still populate the same things even with the new config. So also here, it shouldn't change the publication - and if it does we can raise the flag

John Moehrke (Jun 17 2020 at 15:27):

okay, I might be behind on sushi use. Last I did a this, the build directory had only a FSH folder, and the FSH folder had ig-data folder with everything else. Is that not the layout now?

John Moehrke (Jun 17 2020 at 15:29):

I look forward to your streamlined version. Yesterday I spent many hours moving IHE PIXm word supplement into an sample-ig based build project with some IHE spices. Not hard, but not done.

Jose Costa Teixeira (Jun 17 2020 at 17:24):

The layout is fsh folder as a sibling of the input folder. I will put that in the IHE model IG or somewhere.

Jose Costa Teixeira (Jun 17 2020 at 17:24):

Now I'm hoping to see if Grahame, Oliver or anyone to advise on the one issue I'm missing - about package.tgz expected url X but found Y.

Grahame Grieve (Jun 17 2020 at 18:59):

the url in the package is different from the one you said it should have - is that true?

Jose Costa Teixeira (Jun 17 2020 at 19:02):

the URL in the package is created, not sure if from the package-list or from the command line I give it..

Grahame Grieve (Jun 17 2020 at 19:03):

no. the build process makes the package, and it doesn't use package-list.json as input.

Jose Costa Teixeira (Jun 17 2020 at 19:04):

My assumption is:
Milestone url = http://hl7belgium.org/fhir/core/2020Jun
ci-build url = canonical url = http://hl7belgium.org/fhir/core (without the 2020Jun)

Grahame Grieve (Jun 17 2020 at 19:05):

ci-build is never the canonical

Grahame Grieve (Jun 17 2020 at 19:05):

that would be awful

Jose Costa Teixeira (Jun 17 2020 at 19:06):

i thought it would be seen as a a "base " url

Jose Costa Teixeira (Jun 17 2020 at 19:06):

btw, it's here

Jose Costa Teixeira (Jun 17 2020 at 19:06):

https://github.com/costateixeira/ig-publication

Jose Costa Teixeira (Jun 17 2020 at 19:07):

so I should change the ci-build URL to .../core/development, and then rebuild with that new URL in the -publish parameter?

Grahame Grieve (Jun 17 2020 at 19:09):

the ci-build would usually point to the IG on build.fhir.org

Jose Costa Teixeira (Jun 17 2020 at 19:10):

yes, i'll do that (the build.fhir ci is what I use anyway)

Grahame Grieve (Jun 17 2020 at 19:16):

that doesn't resolve the problem though, which appears to be that the url in the package is wrong - have you checked what it says?

Jose Costa Teixeira (Jun 17 2020 at 19:26):

(waiting for rollback of the changes so that I can give proper information)

Jose Costa Teixeira (Jun 17 2020 at 19:33):

i had updated the package-list in my source folder (which I use for the -publish)
but not the one in the website (where I put the results and I use for the final build)

Jose Costa Teixeira (Jun 17 2020 at 19:33):

my 202Jun folder is stable, i don't touch it.
My package.json inside package.tgz has this

{
  "name": "hl7.be.fhir.core",
  "version": "2020Jun",
  "tools-version": 3,
  "type": "fhir.ig",
  "date": "20200617211504",
  "license": "CC0-1.0",
  "canonical": "http://hl7belgium.org/fhir/core",
  "url": "http://build.fhir.org/ig/hl7-be/be-core",
  "title": "Your User Friendly Name for MyIG Here",
  "description": "A brief description of what MyIG is about (probably the same text as in your readme) (built Wed, Jun 17, 2020 21:15+0200+02:00)",
  "fhirVersions": [
    "4.0.1"
  ],
  "dependencies": {
    "hl7.fhir.r4.core": "4.0.1"
  },
  "author": "HL7 International - [Some] Work Group",
  "directories": {
    "lib": "package",
    "example": "example"
  }
}

Jose Costa Teixeira (Jun 17 2020 at 19:34):

and my package-list has this:

{
    "package-id" : "hl7.be.fhir.core",
    "title" : "Sample IG",
    "canonical" : "http://hl7belgium.org/fhir/core",
    "introduction" : "The introduction that should appear in the FHIR IG registry",
    "list" : [
        {
           "version" : "current",
            "desc" : "Continuous Integration Build (latest in version control)",
            "path" : "http://build.fhir.org/ig/hl7-be/be-core",
            "status" : "ci-build",
            "current" : true
           },
           {
            "version" : "2020Jun",
             "desc" : "2020 June Release",
             "path" : "http://hl7belgium.org/fhir/core/2020Jun",
             "status" : "ballot",
             "date" : "2020-06-15",
             "fhirversion" : "4.0.1",
             "sequence" : 1,
             "current" : true
            }
        ]
}

Jose Costa Teixeira (Jun 17 2020 at 19:38):

i am getting this
Problem with C:\ImplementationGuides\Publication\ig-publication\website\.\package.tgz: expected url http://hl7belgium.org/fhir/core/2020Jun but found http://build.fhir.org/ig/hl7-be/be-core

Jose Costa Teixeira (Jun 17 2020 at 19:42):

why is it expecting http://hl7belgium.org/fhir/core/2020Jun now?

Jose Costa Teixeira (Jun 17 2020 at 19:42):

where does that expectation come from?

Grahame Grieve (Jun 17 2020 at 19:44):

so the package in http://hl7belgium.org/fhir/core/2020Jun claims that the URL for the package is http://build.fhir.org/ig/hl7-be/be-core - well, of course, it's not. The URL for the package is http://hl7belgium.org/fhir/core/2020Jun. The publication tooling is checking that you have all your links correct

Jose Costa Teixeira (Jun 17 2020 at 19:50):

i think i have messed up ci-build vs current

Jose Costa Teixeira (Jun 17 2020 at 19:53):

I built the 2020Jun and copied it to the website\core\2020Jun folder, that seems fine.
Now for the milestone, ie. the one that is going to be in http://hl7belgium.org/fhir/core and in my website\core folder, what do I need to change so that it assumes the correct url - http://hl7belgium.org/fhir/core ?

Grahame Grieve (Jun 17 2020 at 20:02):

I think that you need to build it again with -web

Grahame Grieve (Jun 17 2020 at 20:02):

but I'm not sure about that

Jose Costa Teixeira (Jun 17 2020 at 20:09):

i think that is what idid, trying that again:
running the same content as I used for the 2020Jun, running
-publish http://hl7belgium.org/fhir/core -web -milestone
...
the resulting package says
"url": "http://hl7belgium.org/fhir/core",

Jose Costa Teixeira (Jun 17 2020 at 20:10):

package list contains only the ci-build and the milestone - does it need to contain another entry?

Jose Costa Teixeira (Jun 17 2020 at 20:15):

same thing:
expected url http://hl7belgium.org/fhir/core/2020Jun but found http://hl7belgium.org/fhir/core

Jose Costa Teixeira (Jun 17 2020 at 20:15):

(sorry for all these, but after this I can make the documentation for others to avoid the same doubts I have now)

Jose Costa Teixeira (Jun 17 2020 at 20:39):

the history page now seems to be improved:
image.png
link 1 points to http://hl7belgium.org/fhir/core
link 2 points to buildfhir.org
link 3 points to http://hl7belgium.org/fhir/core/2020Jun

Grahame Grieve (Jun 17 2020 at 20:40):

so this is good now, right?

Jose Costa Teixeira (Jun 17 2020 at 20:51):

i still got the error

Jose Costa Teixeira (Jun 17 2020 at 20:51):

Problem with C:\ImplementationGuides\Publication\ig-publication\website\.\package.tgz: expected url http://hl7belgium.org/fhir/core/2020Jun but found http://hl7belgium.org/fhir/core

Jose Costa Teixeira (Jun 17 2020 at 20:51):

(When it's good I will celebrate loudly) :)
I mean I will throw it in a wiki page with a step by step for dummies like me

Grahame Grieve (Jun 17 2020 at 20:58):

what's with the \.\?

Jose Costa Teixeira (Jun 17 2020 at 20:59):

no idea how that got there

Jose Costa Teixeira (Jun 18 2020 at 08:29):

so the \.\ happened because of the command line i was using
java -jar ..\org.hl7.fhir.publisher.jar -publish-update -folder . -registry ..\ig-registry\fhir-ig-list.json

Jose Costa Teixeira (Jun 18 2020 at 08:30):

if I run it from a different folder the . is gone, result is the same : it still complains about the error but the links seem ok

Jose Costa Teixeira (Jun 18 2020 at 08:30):

do i need to use the -root parameter ?

Jose Costa Teixeira (Jun 18 2020 at 08:31):

I could not understand from the publisher code where it gets the "expected url" from.

Jose Costa Teixeira (Jun 18 2020 at 09:35):

Looking at the code :
I think it is looking at my package-list which says the version is 2020Jun and the path is .../core/2020Jun, which is why it mismatches, because when I build, i say the path for the milestone is .../core

Jose Costa Teixeira (Jun 18 2020 at 10:09):

so I think it is down to :
What should package-list look like when running the publisher with the -publish for the milestone? (i.e. not when running with -publish to generate the 2020Jun, nor the final publish-update)

Jose Costa Teixeira (Jun 18 2020 at 22:14):

while that settles..
image.png

Jose Costa Teixeira (Jun 18 2020 at 22:15):

I managed to apply the ig template to the history. Now I need to make this reproducible somehow.

Bob Milius (Mar 02 2021 at 21:52):

@Jose Costa Teixeira Have you resolved how to fix this? I'm getting similar errors when trying to generate my history file

Problem #15 with [blah]/myig/website/2021-03/package.tgz: expected url [blah]/myig/2021-03 but found [blah]/myig

Jose Costa Teixeira (Mar 02 2021 at 22:11):

Nope. I'm waiting for Grahame to produce some basic guidance, my publication is no longer working.

Jose Costa Teixeira (Mar 02 2021 at 22:12):

if you are further ahead @ Bob Milius I'd love to see how you are doing, then we can produce some documentation ourselves

Bob Milius (Mar 03 2021 at 01:16):

@Jose Costa Teixeira I had it working with an older version of the publisher (last summer). Now it's acting up in the way you describe in this thread. I'm in the process of re-tracing my steps.

Last updated: Apr 12 2022 at 19:14 UTC