Clarify audit timelines and tests for the COUNTER API (#303) (#318)

source/09-audit/03-timelines.rst

@@ -13,11 +13,11 @@ Table 9.a (below): Audit Timelines
 
 .. only:: latex
 
-   .. tabularcolumns:: |>{\raggedright\arraybackslash}\Y{0.34}|>{\raggedright\arraybackslash}\Y{0.4}|>{\raggedright\arraybackslash}\Y{0.14}|
+   .. tabularcolumns:: |>{\raggedright\arraybackslash}\Y{0.34}|>{\raggedright\arraybackslash}\Y{0.28}|>{\raggedright\arraybackslash}\Y{0.38}|
 
 .. list-table::
    :class: longtable
-   :widths: 38 38 24
+   :widths: 27 32 41
    :header-rows: 1
 
    * - Process
@@ -26,23 +26,23 @@ Table 9.a (below): Audit Timelines
 
    * - Seeding
      - 1 calendar month
-     - February
+     - Seeding actions in February
 
    * - Usage processed, reports available
      - Up to 28 days from end of seeding month
-     - March
+     - Reports available by 28 March
 
    * - Report reconciliation
      - 4 to 6 weeks
-     - April
+     - Reconciliation during April
 
    * - Fixes after interim report
      - Up to 3 months
-     - May to July
+     - Interim report issued end April, fixes due by end July
 
    * - Report reconciliation after fixes
      - 1 month
-     - August
+     - Final report issued during August
 
 
 Extensions
@@ -51,11 +51,14 @@ Extensions
 Report providers may request extensions to the usual timelines under the following circumstances.
 
 * **Delayed seeding** - where a report provider is able to demonstrate that they have run the COUNTER Validator and are in the process of fixing problems identified by the validator before commencing an audit, they may apply for up to three months delay in the seeding process.
-* **Extension to the fix period** - where an Interim Report has identified significant problems with COUNTER reports, the report provider may apply for an extension of the fix period from three to up to six months.
+* **Extension to the fix period** - where an Interim Report has identified significant problems with COUNTER reports, the report provider may apply for an extension of the fix period from the standard three to a maximum of six months (i.e. an additional three months).
 
 Applications for extensions MUST be sent to both the Executive Director (code@countermetrics.org) and the auditor, and will be considered on a case-by-case basis. Only one extension of each type will be granted for any audit, and all extensions will be tracked in the Registry.
 
-There may be limited, unforeseen circumstances in which an additional extension may be granted. In these cases the report provider and auditor MUST explain the extenuating circumstances in a short report to the COUNTER Executive Committee. If the additional extension is granted, the report provider will not be required to start seeding an audit until three months after a successful audit pass.
+There may be limited, unforeseen circumstances in which an additional extension may be granted. In these cases the report provider and auditor MUST explain the extenuating circumstances in a short report to the COUNTER Executive Committee. Note that being unable to prioritise fixes in the development queue does not qualify as an unforeseen circumstance. If the additional extension is granted, the report provider will not be required to start seeding an audit until three months after a successful audit pass.
+
+In rare circumstances, a report provider might receive both a delayed seeding extension, and an extension to the fix period for a single audit. If their seeding month was scheduled for January, the combination of both extensions would result in their audit being completed in December. In this circumstance, COUNTER will reschedule seeding to start three months after completion of the delayed audit.
+
 
 .. _alternate-year-audits:
 

source/appendices/e-audit-requirements-and-tests/02-general-tests.rst

@@ -11,7 +11,7 @@ This section of the appendix outlines tests that MUST be run during all audits,
 E.2.1 COUNTER Validator
 """""""""""""""""""""""
 
-Once reports are available for testing (i.e. up to 28 days after the end of the seeding month), auditors MUST run the COUNTER Reports and Standard Views of COUNTER Reports that are within the scope of the audit through the COUNTER Validator. This test must include all attributes report providers are required to support, including attributes that are included only if called for.
+Once reports are available for testing (i.e. up to 28 days after the end of the seeding month), auditors MUST test the report provider's COUNTER API (formerly sushi) configuration as well as the COUNTER Reports and Standard Views of COUNTER Reports that are within the scope of the audit with the COUNTER Validator. This test must include all attributes report providers are required to support, including attributes that are included only if called for.
 
 Where report providers have elected to follow the pre-flight preparation step outlined in :numref:`audit` of the Code of Practice, this audit test should not result in any errors.