You need cookies enabled to use this website.
You need cookies enabled

The issues below are current issues in the live system.  They have been grouped by relevant pages of the submission system.  Each issue is referenced by an internal id which is used to track issues (eg #2989).  Fixed bugs will appear on the system release notes when they are resolved and will be removed from this page.


3714: Replace import does not delete if there is a save error and import with errors is enabled

When a save error is in a import file and a replace import is run with import with errors checked the import does not delete correctly and fails the replace import. Please not this if running a large import file with a error within it and replacing.

release fixed: v2.7.1

3715: Attribution error occurs whenever you import

When importing a REF1a/b and REF2 which are linked a validation error remains stating they are not linked to an output.

release fixed: v2.7.1

3729: Import not handling REF1b with contract date out of range

Imports with out of range dates are causing the import to fail.

release fixed: v2.7.2

3731: Output PDFs added using the output PDF API failing PDF validation check
Upload an output PDF using the API for uploading output PDFs on their own will result in the PDF file failing the PDF validation check.  This is because the check now uses the file size to check if a file is provided and the output PDF api does not add the file size if one is not provided by the user.
NOTE this also affects corroborating evidence ZIP files in that they fill fail the ZIP file validation check when uploaded using the corroborating evidence file API and not file size is provided.
release fixed: v2.7.2
3735: Replace import with output matching fails
The replace import with output matching can fail if any of the outputs to be removed have not been matched to the citation database.
release fixed: v2.7.2
3737: Import failing when starting the import before the import file has been uploaded to the file store

Imports can fail if the import starts before the import file has completed it transfer to the file store.  This can happen because the import message is added to the queue before the file is uploaded to the file store.  If the import engine picks the import message up quickly it then will start process the job before the file is available to process.

release fixed: v2.7.2

3741: Importing FALSE with trailing space makes staff member additional attributed

If an import with a staff output link and under IsAdditionalAttributedStaffMember is put to FALSE with the trailing space the staff member is not made as primary author.

Expected release fix: v2.8

3744: Replace import fails when removing double and its reserve
A replace import can fail when the following conditions occur.
  1. A double weighted output and the reserve are not included in the import file.
  2. The title of the reserve is before the title of the double weighted output in an alphabetical list.

Expected release fix: v2.8

3762: UOA33 output allocation option issues

Amendments being made to UOA33 output allocations to make them consistent for imports.

Expected release fix: v.2.8 


3663: Missleading permissions error if regular user tries to link output to staff member who does not exist in system

If a regular user with write REF1a/b and REF2 permissions attempts to import a staff output link between an output that does exist and a staff member that does not exist they receive an error which advises the member doesnt exist but also that the user does not have permission to view the resource which has confused a user of the system. If you repeat the same import as admin you are just told the staff member doesnt exist - no perms error. 


3756: REF1b contract HESA ID does not NULL when cleared, causes invalid HESA error

This is an issue in the database where it causes a validation error stating an invalid HESA ID is provided, when there is no HESA number entered.



3717: You can double weight and double attribute the same output in Main Panel D resulting in a count of 4

Currently you can create a single output and double weight it, add 2 staff members and attribute one as primary and one as additional. Then the single output carries a count of 4, this shouldn't be able to doubleweight a MPD.

release fixed: v2.7.1

3718: PDF issue in live, dummy.pdf submit error

Validation errors are showing for outputs stating format is not PDF. This is due to dummy data stored in the database triggering the error.

release fixed: v2.7.1

3719: Medium/Long hyphens causing exceptions in import/validate

Character  causes an exception for ISBNs.

release fixed: v2.7.1

3727: PDF error persists after release, some still have size: null

This is a bug which has been found to not have been fixed correctly last release.

3728: REF2 ISSN field always shows warning as possibly wrong

Add a REF2 output, enter a correct ISSN and warning message always appears.

release fixed: v2.7.2

3730: Supplementary Info has a submit error if URL contains ( or )

Characters ( or ) cause a validation error for URLs in supplementary info.

release fixed: v2.7.2

3734: Permissions error if standard/automated user running REF2 validation without output matching

If a standard/automated user has export and relevant REF2 permission but does not have the user output matching permissions and they run a validation, it fails with a permission error.

release fixed: v2.7.2


3736: REF3 import for corrob evidence failing

File imports including corroborating evidence field cause fails.

release fixed: v2.7.2

3746: If you update an IC with a ZIP attached to it, the update removes the ZIP

If a corroborating evidence is added to an REF3 record and then the recorded is editing it removes this file.

Expected release fix: v2.8

3748: REF3 IC Word document extract contains asterisks

Viewing the uploaded word documents in REF3 returns irregularities to the original file. This is a formatting issue by the word reader in the system.

Expected release fix: v2.8

3760: REF3 IC Word doc DOI formatting issue

A formatting issue with the word reader for uploads in REF3 causes some DOIs to appear incorrectly in the system document view.

Expected release fix: v2.8


3739: REF5b upload attachments are not saving

When attempting to save the uploads in REF5b the record does not complete the save and they only allows user to discard the changes to the record, meaning the file is not saved.

Expected release fix: v2.8

3745: Soft hyphen in REF5b word statement causes upload failure

Soft hyphens within documentation uploaded to REF5b causes the upload to fail.

Expected release fix: v2.8

3752: REF5b print report contains spelling error in title

The word environment is spelt wrong in the reports.

Expected release fix: v2.8

3757: REF5a word doc exception error EmbeddedObject

This upload issue is causing the upload to not save.

Expected release fix: v2.8

3762: Two new REF5b Word doc upload exceptions

Further issues with REF5b word document uploads are being fixed at present. These cause the import to fail.

Expected release fix: v2.8

Validation reports (bulk validation and import)

3709: Output validation fails when month not between 1 and 12

When adding a month not between 1 and 12 and the output is assigned to a former staff member then the output validation fails with an exception logged in the database.

release fixed: v2.7.1

3716: Validation report does not count the number of institution/unit environment statements validated

When running a validation report the environment statements are not included in the record count.

release fixed: v2.7.1