Core problem:
Knowledge base developers are often uncertain as to how to apply
varying embargo terms, as the same terms can be used by different content providers in
different ways.
User impact:
Embargo terminology is complex, particularly in instances of a “1-year
embargo”, which might mean the previous 12 months are not available, or that the
current (or previous) calendar year is not available (i.e., from January of a certain year to
the present). Users cannot know with certainty if the article they seek will be found in a
given database when the issue date falls in or near the range of the embargo period.
Solutions:
Consistent usage of the ISO 8601 duration syntax, which allows multiple
types of embargo to be described, can mitigate this problem. See Section 5.3.2.14 for
details.
- Proceed to section 4.2.7 of the KBART report: data format and exchange
- Download PDF of KBART report: PDF 517kb
- Return to homepage of HTML report: HTML