Editing REF CC (section)

==Version History==
===v1.6.1===
* Update Unpaywall harvester to gather a url_for_pdf from location data if this field has a value and if it is not present in the best_location data
===v1.6===
Version 1.6 introduces a number of changes broken down into three categories, updates to compliance checking, 3rd party checks for assessing audit probability, and miscellaneous/bug fixes.
====Compliance Checking====
* Gold OA now reports as compliant, not as out-of-scope
* Access Timing compliance test updated so that if an embargo date falls on or beyond the submission deadline, it will pass the test
* Items accepted or published after the submission deadline marked as out-of-scope (with the option to hide the REF CC tab for these items)

====3rd Party Checks====
* New 3rd Party Check tab in the REF CC tab when viewing an EPrint record, highlighting if the record meets the criteria as outlined in para 46b of the [https://www.ref.ac.uk/media/1164/ref-2019_04-audit-guidance.pdf Audit Guidance] relating to Unpaywall
* New 3rd Part Data section added to expandable "Data used to check compliance" section, listing the DOI used to perform the checks, and any data retrieved from Unpaywall.
* Audit data stored in new hefce_oa_audit dataset. hefce_oa_audit records linked to eprints via "eprintid" itemref field
* bin script to harvest data from Unpaywall on a routine basis. The script is rate limited to ensure it does not exceed over 100,000 calls a day and updates eprints based on when they were last updated (prioritising those who have not been recently updated)
* New report summarising Unpaywall data for all REF eligible eprints
====Misc. Fixes====
* Bug fix preventing Date of First Compliant Deposit being wiped if update data is imported for an EPrint
* Update exception mapping trigger to copy deposit exception text to further exception where deposit exception was 'g'.
===v1.5.1===
* Update trigger for mapping old exceptions to remove exception values no longer in use once the mapping has taken place.
* Add out of scope reporting to reports and report exports
* Add Gold OA field to the REF CC custom report search forms
===v1.5===
* Updated exception and policy text based on [https://www.ref.ac.uk/publications/guidance-on-submissions-201901/ Guidance on Submissions]
* Introduce a Gold OA field to mark items as being published via Gold OA (and therefore out of scope of the OA policy)
* Report when an item is out of scope using a grey tick icon
* Pre-commit trigger to map old exception values to new exceptions (and script to apply this trigger to all relevant records on demand)
* OA retraction period to allow an item which was had the 'Date of First Open Access' set by accident to be retracted after a specified number of days
* Panel deduction based on a mapping of division values to panels
* Configurable list of values for allowed document content values

'''Upgrade Advisory:'''
When upgrading to v1.5 the introduction of a new constant may produce the following error:

<pre>
EPrints System Error

Error in configuration:
Bareword "HefceOA::Const::EX_FUR" not allowed while "strict subs" in use at /opt/eprints3/lib/cfg.d/hefce_oa_tests.pl line 32.
</pre>

A graceful restart of apache and a refresh of the page should fix this and the plugin will have been successfully upgraded.

===v1.4.2===
* Bug fixes
===v1.4===
* Added blue status to reports to highlight items accepted before April 2016, for which compliance is not a concern.
===v1.3.1===
* Fix issue for multi-archive repositories ([https://github.com/eprintsug/hefce_oa/issues/42 Issue 42]).
===v1.3===
* See installation note: [[REF_CC#Upgrading_to_version_1.3.2B]]
*Traffic light system for reports, items with status of 'will become compliant' shown as amber (Generic Reporting Framework v2.0 prerequisite).
*Option to include 'will become compliant' records in report headline figure (Generic Reporting Framework v2.0 prerequisite).
*Custom reports search configuration (Generic Reporting Framework v2.0 prerequisite).
*Exports including fields relevant for determining REF compliance (Generic Reporting Framework v2.0 prerequisite)
*'Exclude from REF' checkbox in REF CC stage of deposit workflow, which when set prevents a record from appearing in a REF report.

===v1.1.2===
*Update Date of First Compliant Deposit rule to account for relaxed HEFCE rules: "If the Date of acceptance is before 1st April 2018, Date of first compliant deposit must be no later than three months after the Date of first online publication."

===v1.1.0===
*integration with new version of 'datesdatesdates' that supports publication and online-publication dates
*display of a [http://eprintsug.github.io/hefce_oa/#will-become-compliant will become compliant] status for items that have an embargoed document attached, but that are otherwise compliant.
*automatic population of embargo-length (months) field based on embargo end date for AAM/VoRs
*warning for incomplete dates that may affect calculation of compliance