Skip to content

good practice and innovation
about us infoKits Tools & Techniques Publications Events
You are here: Home » Case Studies » Research Excellence Framework Case Studies » Bangor University Case Study » Data Submission, Lessons Learned and Corporate Systems







Data Submission

The research outputs and staff tables were extracted from the in-house system into MS Excel spreadsheets using the supplied templates. All the information needed to build the link table was present but due to time pressure the table was not built at submission time. The link table was subsequently built by staff at Evidence Ltd (the company contracted by HEFCE as part of the pilot) using the process:

  1. Copied the fields 'Institution', 'InstitutionalStaffIdentifier', 'InstitutionalUniqueOutputId' from the Outputs table to a new Link table
  2. Then looked up (formulaically, not manually) the relevant HESAStaffIdentifier for each record using the InstitutionalStaffIdentifier to complete the Link table

Lessons Learned

Control of a largely unused institutional repository has been passed from the library to the Research Office and Research Office staff are now working on populating the repository. The local database is the definitive record and will form much of the input for the repository. The repository is a wider application than just the REF and will increase the visibility and accessibility of research materials created by the University.

In the longer term there is a need to develop an overarching data warehouse drawing on various data sources. The Research Office sees this as a bespoke project but will need the final REF definition before proceeding. The repository will be one element which will feed into the warehouse.

Corporate Systems

Bangor University has the following corporate systems:

Corporate Application Supplier /System
Human Resources Agresso/HR
Finance Agresso/Financials
Student Record Sungard/Banner

Bookmark and Share
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)