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.
Recently raised
This can be disregarded and should not prevent submission. Please do ensure your zip file has been added by viewing/downloading it.
To work around this remove the originally linked staff member before replace importing. Please contact us if this does not resolve the issue.
To work around this you will need to manually unlock the submission UOAs.
This is due to retrieved PDFs showing as succesful but indicated as not provided a PDF below. This should not prevent submission.
You will see this as an error in the validation report. Please let us know if you encounter this issue.
You will find this may cause the IC not to save and the screen may get stuck loading. To work around this delete one corroborator at a time.
This can be caused by some hyperlinks (often DOI ones) and can be resolved by removing the hyperlink.
Note the data is still in the database and will apeear on exports and reports. This is also the case for read only users.
Import/Export
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.
REF2
This is a bug which has been found to not have been fixed correctly last release.
REF3
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