-
Notifications
You must be signed in to change notification settings - Fork 2
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
Failure to fetch bibliographic reference CC/R 1102:2013
#326
Comments
@andrew2net The query Relaton.fetch_async is making is:
Fetching either @andrew2net I think this is still a Relaton issue, even if |
@ronaldtse @opoudjis in the source dataset the document doesn't have ...
- id: CC/R1102-2013
title:
- type: title-main
content: Calendaring and Scheduling Glossary of Terms V2.2 (CD 1102)
language: en
script: Latn
format: text/plain
- type: main
content: Calendaring and Scheduling Glossary of Terms V2.2 (CD 1102)
language: en
script: Latn
format: text/plain
type: standard
docid:
id: CC/R 1102:2013
type: CC
version:
revision_date: '2013-05-02'
revdate: '2013-05-02' # <=REVDATE!!
abstract:
content: A Glossary of Calendaring and Scheduling Terms.
format: text/plain
fetched: '2020-06-23'
editorialgroup:
technical_committee:
name: CALCONNECT
doctype: report
uri:
xml:
pdf:
doc:
html:
rxl:
txt:
... Can we use the |
This is bad practice, the source data should have a published date. But yes, if you know for a fact that the document is published and not draft, but you do not have a published date or updated date, then you must use revdate; all published documents need a publication date for referencing (and as it turns out, for Relaton querying). |
We do not enforce a If the document is not published, we need to show the draft date, which is |
Fixed in relaton-calconnect v1.19.1 @ronaldtse @opoudjis please check |
@ronaldtse Did you want that as a warning or an abort in Metanorma? |
Error when using it in Metanorma-CC:
Error:
But it works in Relaton:
With year:
Without year:
FYI @andrew2net
The text was updated successfully, but these errors were encountered: