-
Notifications
You must be signed in to change notification settings - Fork 3
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
(SI Brochure, URGENT) Brochure: Duplicate years on rendered CIPM/CGPM references #170
Comments
@opoudjis @andrew2net is this a Relaton BIPM issue, or a Metanorma issue? |
According to the data file, the year is already included in the "ID": Is this a Relaton BIPM rendering issue? @andrew2net |
We're doubling up clearly on #164.
@ronaldtse Given the ambiguity we have already discussed for these resolutions, whose numbering restarts each year, I will have to assume that all BIPM Resolutions/Recommendations/Decisions have the year attached to the ID (@andrew2net please confirm), and I will undo the change adding the year to the ID. |
At the moment, BIPM CGPM Resolution 1967-07 has a year in its ID, and BIPM CGPM Resolution 1 (or: 1889) does not: https://github.com/relaton/relaton-data-bipm/blob/d40968792b9fc8e90aefc23f6921e9c74dec1ae4/data/cgpm/resolution/1.yaml . However, this is being addressed by @andrew2net . So I am removing any injection of years into citations of Resolutions/Recommendations/Decisions, that is @andrew2net's responsibility, not mine. |
Note that PR will not currently work, because I am waiting for year to be added to BIPM CGPM Resolution 1 and BIPM CIPM Decision 105. |
@andrew2net this is an issue in Relaton-BIPM. The raw data seems to be correct:
|
@opoudjis , "CGPM Resolution (1889)" already has year : |
PR has passed. This should now be fine. Yes, I know they already have years, that is a fix as of relaton-bipm 1.1.3. That's why I'm no longer adding them. |
In relation to metanorma/bipm-si-brochure#145
From metanorma/bipm-si-brochure#168, this markup:
Renders:
The text was updated successfully, but these errors were encountered: