March 25, 2011
I’ve spent some time in the last few days working through the latest information I have for the specification to see how prepared we are for this at the University of Glasgow and what work might be involved.
I understand an update spec and timeframe will be available to us soon.
It is clear to me that there will be considerable resource requirements for Research Organisations including those that are lucky enough to already hold a lot of the data on core systems already or at the other end of the spectrum where the RO may not want to provide data from core systems but will need to support academics entering data direct to the RCUK system.
There still seems to be considerable overlap between further funding, collaboration and IP which may cause confusion and cost time. However I am hoping where there is an overlap we can present once (.e.g. in further funding).
There are some requirements that suggest use of standard lists e.g. organisation codes for funders/collaborators frm a standard JeS list, country codes from ONS list. Standardisation is good however in the short to medium term I suspect many Research Organisations have thier own – or different standard – code structures for these so again this may be a bit problematic.
We also have concerns about resource requirements for checking data. I understand that RCUK wish to receive data that is suitable for the public domain. However we think that the University of Glasgow will have to apply some specialist checking to certain data e.g.
- Bio/Medical e.g. cell lines, antibodies
- Electronic e.g. data set, algorithm
- Physical e.g. new molecule, prototype
The other issue we have outstanding is Data Protection/confidentiality around staff development and wether it is appropriate for staff to be asked to comment on other staff as part of the return.
Having said all this I am expecting that the approach will be ‘supply what you can’ or perhaps focus on some key elements e.g. publications initially to allow time to set up local environments.
March 15, 2011
The code we amended for use in our mini-REF exercise will be available soon. We will advertise on this blog.
If you would like us to email you when it is released please email me email@example.com
In a hurry to get started with the code? We may be able to send you the zipped files and give you some support so please do ask.
March 11, 2011
I will be doing a short presentation on Enquire at the JISC Conference (#jisc11 for keen twitterers)
The session I will be part of is ‘Better Research Management: Strategies and Tools’ at 1.30pm so I expect to be speaking about 1.45pm
There will be a live stream from the event and the presentations will be available from the JISC website afterwards:
March 11, 2011
You may be interested in the MICE project looking at measuring impact under CERIF.
The Enquire project itself is now closed however we will still be blogging news from the sector and the University of Glasgow via this blog and hope to work with the MICE team to further prepare for reporting on outcomes and impact.
March 8, 2011
Many thanks to everyone who attended the workshop in Glasgow last Friday and contributed to the lively exchange. It was great to see so many colleagues travelling from near and far to take part and share their experiences.
The workshop consisted of a mix of presentations and discussions. The following report outlines some of the salient points raised:
RCUK new output fields
We were lucky enough to receive presentations from several speakers on their own experiences of reporting
Laura Tyler on Glasgow’s Mini REF
William Nixon on Enlighten at Glasgow
Helen Muir on QMU outputs collection process
Simon Kerridge on Sunderland’s outputs collection, and IRIOS & RMAS projects
A virtual presentation from Darren Hunter of RCUK RCUK slide show with accompanying sound file at http://www.gla.ac.uk/r-e/pub/special/ops/enquire/feb2011workshop.wma
If you have anything to add to the report, please don’t hesitate to get in touch using the comment button below or by email to firstname.lastname@example.org or email@example.com
Once again, thanks to everyone who helped to make this a success.