isobib can't find the ISO/IEC Directives

[opoudjis]

... Because they do not show up in a search on the ISO website. (The Rice model does :-(

This is bad; bad enough, @ronaldtse, that it should be escalated to ISO. The gem is predicated on the assumption that all ISO publications are discoverable through the web search. In the interim, I will need to code an exception in the gem for the contents of http://www.iso.org/directives.

[ronaldtse]

OK I just emailed them, let's see if we get a reply.

[opoudjis]

I am restricting the manual exceptions in isobib to:

• ISO/IEC Directives, Part 1
• ISO/IEC Directives, Part 1 Consolidated ISO Supplement
• ISO/IEC Directives, Part 2

And the citations will need to appear exactly like that. I have no idea if there even is a document identifier for the other documents appearing in http://www.iso.org/directives, such as the Vienna agreement; and if ISO have not (the VA in the footer does not count), then I can't.

[ronaldtse]

And these? 😉

http://www.iec.ch/members_experts/refdocs/

e.g. "ISO/IEC Directives, IEC Supplement:2018"

[opoudjis]

Actually, that makes my life easier. If it's an ISO/IEC Directive, search for it in IECbib, not ISObib. OK, so I will defer this ticket till IEC is up and running, and then have relaton pass those queries to IECbib.

[opoudjis]

Unfortunately while the PDFs of ISO/IEC DIR are discoverable at IEC, which they are not at ISO, that's useless, because there is no associated landing page in the webstore, so there is no discoverable metadata about the PDFs. Nor will either ISO or IEC be motivated to create landing pages for them. The only way unfortunately is to create custom XML for these documents :( , and I'm not convinced that's worth it, when we are just using the title for these anyway. @ronaldtse ?

[ronaldtse]

Right, perhaps we can make a general mechanism that overrides Relaton Bib items.

For example, we could have a new repo called "relaton-iso-overrides" that details these “special cases” in some YAML file, and Relaton will use these to override.

I’m pretty sure we will run into these soon, not only for ISO, but also other orgs like IEC etc.

[opoudjis]

A separate YAML repo seems unnecessary: this can just be a local cache of XML within this repo. And I take it that's what you want me to do here.

[ronaldtse]

Or we could place that local XML cache is some internet accessible location that the bib gem can fetch :wink:

[andrew2net]

@ronaldtse so, how do we suppose to solve with this issue?

[ronaldtse]

@andrew2net we have to manually encode and either carry with the gem, or make it fetch from a location (all the overrides). I prefer we use Relaton YAML to encode.

[andrew2net]

@ronaldtse maybe create a static database in relaton gem?

[ronaldtse]

@andrew2net that works, but I'd prefer Relaton YAML that can be modified by humans easier.

[andrew2net]

@ronaldtse I think we can have a static database with YAML files. We already have the functionality to create a bibliographic item from YAML.

[ronaldtse]

Agree @andrew2net , could you help make it happen? Thanks. (and please help test https://github.com/metanorma/lapidist for Relaton release)

[andrew2net]

This issue is moved to https://github.com/relaton/relaton/issues/57

[ronaldtse]

@andrew2net can we keep this open? This specifically relates to relaton-iso, while the referred task is a generic task across Relaton. Thanks.

[ronaldtse]

@andrew2net is this done? Can you update metanorma.com on how to refer to these documents and close this? Thanks.

[andrew2net]

@ronaldtse the static cache is created. While we were discussing references format I switched to another task. So now we just need to make YAML files and put them to the static cache directory. The filenames should be lowercased references with symbols and break spaces replaced by underscores. There is one example https://github.com/relaton/relaton/blob/feature/support-un-fetchable-data/lib/relaton/static_cache/iso/iso_iec_directives_part_1.yml

[andrew2net]

Solved in https://github.com/relaton/relaton/issues/57