Description
Sometimes the cache of an entry "not found" can be found in reality, but the cache was stuck to an old result of "not found".
e.g.
Using relaton-nist 1.14.9
...
$ bundle exec relaton fetch 'NIST CSWP 6'
[relaton] (NIST CSWP 6) not found.
No matching bibliographic entry found
From @andrew2net:
the message
[relaton] (NIST CSWP 6) not found.is from relaton gem, which acts as a cache. A response from the previous version of relaton-nist was stored in the cache. We had functionality that cleans a cache in case gem's version is changed, but we moved to schema version control. So it needs to runrelaton db clearnow.
Users will never be able to figure this out.
When the Relaton-xxx gem is updated, should the cache be wiped? At least the "not found" ones?
This information needs to be described in the output:
- it should say "not found in cache, if you wish to ignore cache please run with "ignore cache" command or wipe the cache
In any case, we must differentiate a "cache hit not found" vs the "actual not found", at the library level. And provide an "ignore cache" option.