Editing Using Issues for Quality Control (section)

===issues.xml===

Issues that relate to the properties of an individual item are defined in the configuration file ''archives/ARCHIVEID/cfg/issues.xml''.

The issues.xml file uses the [[EPrints_Control_Format|EPrints Control Syntax]] and [[EPScript|EPrints Script]] to define a series of tests that can be carried out on an item's metadata to work out which issues an item has. Each issue is then defined using an "<issue>..</issue>" construct.

'''Example 1''' Test the metadata fields '''date''' and '''ispublished''' - if the date is at least 2 years in the past and ispublished has the value "submitted" or "inpress", report the "old_but_not_published" issue for the item (this example is taken from the default issues.xml in EPrints 3.1.3).

   <epc:if test="date.is_set() and date lt today().datemath( -2,'year' ) and ( ispublished = 'submitted' or ispublished = 'inpress' )">
      <issue type="old_but_not_published">Date is <strong><epc:print expr="date" /></strong> but item is still marked as <strong><epc:print expr="ispublished" /></strong>.</issue>
   </epc:if>

'''Example 2''' An <issue> without a conditional test will always be reported.

 <issue type="always_reported">This issue is always reported.</issue>

[[Image:Always_reported.png]]

'''Example 3''' Report articles that do not have an ISSN.

   <epc:if test="type='article' and ispublished='pub' and !issn.is_set()">
     <issue type="published_but_no_issn">Item is published but has no ISSN. </issue>
   </epc:if>