Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up existing graph metadata for PublishedVersion #1074

Open
steveraysteveray opened this issue Dec 10, 2024 · 6 comments
Open

Clean up existing graph metadata for PublishedVersion #1074

steveraysteveray opened this issue Dec 10, 2024 · 6 comments

Comments

@steveraysteveray
Copy link
Collaborator

No description provided.

@steveraysteveray
Copy link
Collaborator Author

@fkleedorfer, if you take a look at our published graph HTML pages, you will see that there are still a few tweaks needed in the pom.xml, I think. If you start here and click on each of the schema and vocab graph pages, you will see that:

  1. All the graphs have an extra "v2.1" in the latestPublishedVersion links
  2. The schema graphs don't properly update the date folder for the previousPublishedVersion links, such as https://qudt.org/doc/2024/09/DOC_SCHEMA-QUDT.html

Could you take a look? I'm happy to manually fix the pages, but wanted you to see what is generated before I change it.

@fkleedorfer
Copy link
Collaborator

fkleedorfer commented Dec 11, 2024

I forgot that the november release required special handling (v2.1 still in previous links), that I was going to remove before the december release. Will fix that in the pom, but the released files will have to be corrected manually for website publication I am afraid.

@fkleedorfer
Copy link
Collaborator

I don't know how '-v2.1' got in there. is it possible that it is modified in the publication process?

@fkleedorfer
Copy link
Collaborator

in #1075 I put year/month placeholders in the prev/current links so they do not look like they are getting progressively more out of date.

@fkleedorfer
Copy link
Collaborator

Looking into the 2.1.46 release, I cannot find any of the problems you mention. I suspect it's an artifact of the publication process.

@steveraysteveray
Copy link
Collaborator Author

OK, in some ways that's easier for me to debug because we don't need to do new releases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants