REF CC Internal flag used to trigger EPrint update Compliance Yes No Unknown Embargo length (months) REF panel REF Main Panel A or B REF Main Panel C or D Date of acceptance Date of first online publication Date of first compliant deposit Version of first compliant deposit Author Accepted Manuscript Version of Record Date of first compliant Open Access Deposit exception 252. The following exceptions deal with cases where the output is unable to meet the deposit requirements. In the following cases, the output will not be required to meet any of the open access criteria (deposit, discovery or access requirements).

a. At the point of acceptance, it was not possible to secure the use of a repository. b. There was a delay in securing the final peer-reviewed text (for instance, where a paper has multiple authors) c. The staff member to whom the output is attributed was not employed on a Category A eligible contract by a UK HEI (defined in paragraphs 52 to 63) at the time of submission for publication. d. It would be unlawful to deposit, or request the deposit of, the output. e. Depositing the output would present a security risk. Explanation Access exception 253. The following exceptions deal with cases where deposit of the output is possible, but there are issues to do with meeting the access requirements. In the following cases, the output will still be required to meet the deposit and discovery requirements, but not the access requirements. A closed-access deposit, where allowed, will be required. a. The output depends on the reproduction of third-party content for which open access rights could not be granted (either within the specified timescales, or at all). b. The publication concerned requires an embargo period that exceeds the stated maxima, and was the most appropriate publication for the output. c. The publication concerned actively disallows open-access deposit in a repository, and was the most appropriate publication for the output. Explanation Technical exception 254. The following exceptions deal with cases where an output is unable to meet the criteria due to a technical issue. In the following cases, the output will not be required to meet the open access criteria (deposit, discovery or access requirements). a. At the point of acceptance, the staff member to whom the output is attributed was employed at a different UK HEI, and it has not been possible to determine compliance with the criteria. b. The repository experienced a short-term or transient technical failure that prevented compliance with the criteria (this should not apply to systemic issues). c. An external service provider failure prevented compliance (for instance, a subject repository did not enable open access at the end of the embargo period, or a subject repository ceased to operate). Explanation Further exception 255. Two further exceptions to the policy are outlined below: a. ‘Other exception’ should be used where an output is unable to meet the criteria due to circumstances beyond the control of the HEI, including extenuating personal circumstances of the author (such as periods of extended leave), industrial action, closure days, and software problems beyond those listed in the technical exceptions. If ‘other’ exception is selected, the output will not need to meet the open access criteria (deposit, discovery or access requirements). b. The output was not deposited within three months of acceptance date, but was deposited within three months of the earliest date of publication. In this instance, the output will need to meet all other policy requirements. This exception does not need to be applied retrospectively to outputs compliant with the policy from 1 April 2016 to 1 April 2018 which fulfilled the policy requirements within three months of publication. Explanation Other exception 41. In very exceptional cases, it may not be possible for an output to meet the open access requirements set out by this policy for a reason not covered by the exceptions listed above. We will require a short written explanation for why the output could not meet the open access requirements at the point of submission to the REF. We expect that such cases should be extremely rare. We will establish the process for considering them as part of our more detailed work to develop the post-2014 REF. Yes
No Explanation Congratulations, this item complies with the Open Access policy Sorry, this item does not comply with the Open Access policy This item is not currently compliant. If the output (full text) is made open access by it will become compliant.
This date is calculated from an embargo length of months. Please see the 'Access' tab below for more details. This item falls outside of the scope of the Open Access compliance policy as it has a date of acceptance before 1 April 2016. This item falls outside of the scope of the Open Access compliance policy as it has been published via Gold open access. For more information see paragraph 239 of This item falls outside of the scope of the Open Access compliance policy as it does not have an ISSN. For more information see paragraph 223 of This item could become compliant Exceptions () Compliance Creators Dates This item is not currently compliant. If the output (full text) is made open access by it will become compliant.

More...

No exceptions. Data used to check compliance ? (deduced panel: ) The following fields have incomplete dates. Incomplete dates may lead to inaccurate reporting of compliance.

REF Compliance Accepted April 2015 - March 2016 Accepted April 2016 - March 2017 Accepted April 2017 - March 2018 Accepted April 2018 - March 2019 Accepted April 2019 - March 2020 Accepted April 2020 - March 2021 REF Compliance - Exceptions Accepted April 2015 - March 2016 Accepted April 2016 - March 2017 Accepted April 2017 - March 2018 Accepted April 2018 - March 2019 Accepted April 2019 - March 2020 Accepted April 2020 - March 2021 Core RIOXX REF Exceptions REF Problems Exclude from REF Gold OA 239. Some UK funders have a preference for gold open access. ‘Gold’ open access usually means the immediate, permanent, and free to access availability of the published version of record on the publisher’s website and with a licence that permits copying and reuse. Outputs that are made open access through the ‘gold’ route, at the point of first publication, in accordance with other funder’s requirements and definitions, meet the requirement of the REF 2021 open access policy. HEIs will need to confirm that outputs were available immediately after publication via the gold route. This item falls outside of the scope of the Open Access compliance policy as it has a date of acceptance before 1 April 2016. This item falls outside of the scope of the Open Access compliance policy as it has a date of acceptance before 1 April 2016. This item falls outside of the scope of the Open Access compliance policy as it has been published via Gold open access. This item falls outside of the scope of the Open Access compliance policy as it does not have an ISSN.