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.
Import/Export
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
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
Imports with out of range dates are causing the import to fail.
release fixed: v2.7.2
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
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
- A double weighted output and the reserve are not included in the import file.
- The title of the reserve is before the title of the double weighted output in an alphabetical list.
Expected release fix: v2.8
Amendments being made to UOA33 output allocations to make them consistent for imports.
Expected release fix: v.2.8
REF1a/b
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.
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.
This will be changed to a warning error.
release fixed: v2.7.1
REF2
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
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
Character – causes an exception for ISBNs.
release fixed: v2.7.1
This is a bug which has been found to not have been fixed correctly last release.
Add a REF2 output, enter a correct ISSN and warning message always appears.
release fixed: v2.7.2
Characters ( or ) cause a validation error for URLs in supplementary info.
release fixed: v2.7.2
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
REF3
File imports including corroborating evidence field cause fails.
release fixed: v2.7.2
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
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
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
REF5
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
Soft hyphens within documentation uploaded to REF5b causes the upload to fail.
Expected release fix: v2.8
The word environment is spelt wrong in the reports.
Expected release fix: v2.8
This upload issue is causing the upload to not save.
Expected release fix: v2.8
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)
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
When running a validation report the environment statements are not included in the record count.
release fixed: v2.7.1