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

(SI Brochure, URGENT) Brochure: Duplicate years on rendered CIPM/CGPM references #170

Closed
manuelfuenmayor opened this issue May 27, 2022 · 8 comments
Assignees
Labels
bug Something isn't working

Comments

@manuelfuenmayor
Copy link

In relation to metanorma/bipm-si-brochure#145

From metanorma/bipm-si-brochure#168, this markup:

* [[[CR1968-7, CGPM Resolution 1967-07]]]

Renders:
issue1

@manuelfuenmayor manuelfuenmayor added the bug Something isn't working label May 27, 2022
@ronaldtse ronaldtse moved this to Triage in Metanorma May 30, 2022
@ronaldtse
Copy link
Contributor

@opoudjis @andrew2net is this a Relaton BIPM issue, or a Metanorma issue?

@ronaldtse ronaldtse changed the title Brochure: Duplicate years on rendered CIPM/CGPM references (SI Brochure, URGENT) Brochure: Duplicate years on rendered CIPM/CGPM references May 30, 2022
@ronaldtse ronaldtse moved this from Triage to Urgent in Metanorma May 30, 2022
@ronaldtse
Copy link
Contributor

According to the data file, the year is already included in the "ID":
https://github.com/relaton/relaton-data-bipm/blob/d40968792b9fc8e90aefc23f6921e9c74dec1ae4/data/cgpm/resolution/1967-07.yaml#L22

Is this a Relaton BIPM rendering issue? @andrew2net

@opoudjis opoudjis moved this from Urgent to In Progress in Metanorma May 31, 2022
@opoudjis
Copy link
Contributor

opoudjis commented May 31, 2022

We're doubling up clearly on #164.

  • I actioned advice from BIPM that the year was to be added to the citation, but is a distinct thing from the identifier; so I added it on top of the ID
  • @andrew2net, acting on the same advice, added the year to the ID

@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.

@opoudjis
Copy link
Contributor

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.

@opoudjis
Copy link
Contributor

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.

@opoudjis opoudjis moved this from In Progress to Pending release in Metanorma May 31, 2022
@ronaldtse
Copy link
Contributor

ronaldtse commented Jun 2, 2022

@andrew2net this is an issue in Relaton-BIPM.

The raw data seems to be correct:

@ronaldtse
Copy link
Contributor

@opoudjis
Copy link
Contributor

opoudjis commented Jun 2, 2022

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.

@opoudjis opoudjis closed this as completed Jun 2, 2022
Repository owner moved this from Pending release to Done in Metanorma Jun 2, 2022
@ronaldtse ronaldtse removed this from Metanorma Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants