UKOLN is supported  by: RIM1 technical synthesis (work in progress) 30 March 2011 Rosemary Russell, UKOLN, University of B...
* Work in progress*   <ul><li>‘ Technical’ synthesis…  </li></ul><ul><ul><li>relating to use of standards (eg CERIF), meta...
RIM1 <ul><li>5 diverse projects </li></ul><ul><ul><li>2 management-focused (UCL, Imperial) </li></ul></ul><ul><ul><li>3 mo...
Lack of integration <ul><li>Imperial - almost every institution cited a fragmented research system suite and lack of integ...
RIM requirements <ul><li>difficulty of articulating RIM requirements (because RIM is complex) - surfaced many times in Imp...
Data quality <ul><li>Data quality identified as big issue by Imperial interviews </li></ul><ul><li>UCL - data was the sing...
Person identification <ul><li>Issue very frequently cited… </li></ul><ul><li>Huddersfield - principal difficulty lies when...
CERIF <ul><li>Only CRISPool and BRIM used CERIF (Enquire ‘looked at’) </li></ul><ul><li>CRISPool findings support EXRI con...
CERIF issues (CRISPool) <ul><li>Fragmentation of CERIF-XML into many individual XML files </li></ul><ul><ul><li>very resou...
Moving targets <ul><li>Enquire project affected by RCUK change of plan  </li></ul><ul><ul><li>not been able to deliver def...
Research staff <ul><li>Imperial – widespread dissatisfaction with current research systems (particularly academics) </li><...
Collaborative working  <ul><li>Imperial recommendation – more collaboration (institutions and funders), minimise duplicati...
Technical synthesis <ul><li>Next step  </li></ul><ul><ul><li>stand-alone document, or integrated within Infokit…  </li></u...
Upcoming SlideShare
Loading in …5
×

JISC research information management phase 1 technical synthesis

386 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
386
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

JISC research information management phase 1 technical synthesis

  1. 1. UKOLN is supported by: RIM1 technical synthesis (work in progress) 30 March 2011 Rosemary Russell, UKOLN, University of Bath
  2. 2. * Work in progress* <ul><li>‘ Technical’ synthesis… </li></ul><ul><ul><li>relating to use of standards (eg CERIF), metadata etc, in addition to systems/software/infrastructure issues </li></ul></ul><ul><ul><li>Attempted to identify common technical themes running through the 5 projects </li></ul></ul><ul><li>Based on project final reports </li></ul>Overview…
  3. 3. RIM1 <ul><li>5 diverse projects </li></ul><ul><ul><li>2 management-focused (UCL, Imperial) </li></ul></ul><ul><ul><li>3 more ‘technical’ (BRIM, Enquire, CRISPool) </li></ul></ul><ul><ul><ul><li>CRISPool most technical ie end-to-end system - from requirements, specification, mapping to CERIF, through to pilot implementation (although not public) </li></ul></ul></ul>
  4. 4. Lack of integration <ul><li>Imperial - almost every institution cited a fragmented research system suite and lack of integration as the fundamental problems </li></ul><ul><li>Apart from Imperial no institution had mature enough systems to consider system integration … </li></ul><ul><li>CRISPool demonstrated that institutions with an integrated research system or CRIS have distinct advantage (when adopting CERIF) </li></ul><ul><ul><li>eg St Andrews able to create CERIF-XML files directly from PURE (resource intensive (or impossible) for others) </li></ul></ul>
  5. 5. RIM requirements <ul><li>difficulty of articulating RIM requirements (because RIM is complex) - surfaced many times in Imperial report </li></ul><ul><li>BRIM main task - capture RIM requirements and create prototype (that integrated with existing business processes, using standard interfaces) </li></ul><ul><li>CRISPool finding - taking time initially to define requirements was very important </li></ul><ul><li>However, Imperial recommendation - do not spend too much time on requirements – allows less time to build the system… </li></ul>
  6. 6. Data quality <ul><li>Data quality identified as big issue by Imperial interviews </li></ul><ul><li>UCL - data was the single greatest cause for concern for researchers </li></ul><ul><li>CRISPool – importance of sample files </li></ul><ul><li>Resources for data cleansing must be identified (consistent area of difficulty) </li></ul><ul><li>Imperial - absence of high level frameworks and standards in the UK with regard to data collection and data sharing </li></ul>
  7. 7. Person identification <ul><li>Issue very frequently cited… </li></ul><ul><li>Huddersfield - principal difficulty lies when members of staff enter their co-contributors’ details = a lot of manual reconciliation of names </li></ul><ul><li>CRISPool used UK Learner Provider number as a prefix to institutional IDs </li></ul>
  8. 8. CERIF <ul><li>Only CRISPool and BRIM used CERIF (Enquire ‘looked at’) </li></ul><ul><li>CRISPool findings support EXRI conclusion that CERIF should be used as the exchange format within the UK research information sector </li></ul><ul><li>BRIM - by adopting much of the structure of CERIF we were being guided in understanding and capturing the implicit structure of the data we are required to manipulate </li></ul><ul><ul><li>decided to only focus on a portion of the CERIF model (some parts superfluous to current needs) </li></ul></ul>
  9. 9. CERIF issues (CRISPool) <ul><li>Fragmentation of CERIF-XML into many individual XML files </li></ul><ul><ul><li>very resource intensive to process </li></ul></ul><ul><li>All required elements mapped except: </li></ul><ul><ul><li>contact details against person, not person-organisation relation; worked around using classification </li></ul></ul><ul><ul><li>single URI per publication (one-to-one relationship for euroCRIS) - opted for DOI not IR handle as more data; could have been addressed with classification </li></ul></ul>
  10. 10. Moving targets <ul><li>Enquire project affected by RCUK change of plan </li></ul><ul><ul><li>not been able to deliver definitive output specifications that comply with RCUK requirements. </li></ul></ul><ul><ul><li>instead produced generic specifications for impact and some key outputs - can be modified if different specifications are published </li></ul></ul>
  11. 11. Research staff <ul><li>Imperial – widespread dissatisfaction with current research systems (particularly academics) </li></ul><ul><li>Need easy to use interfaces </li></ul><ul><li>UCL - people are required, to ensure that systems fit with researcher needs and workflows </li></ul><ul><li>Enquire workshops - need to minimise burden on academics </li></ul>
  12. 12. Collaborative working <ul><li>Imperial recommendation – more collaboration (institutions and funders), minimise duplication </li></ul><ul><ul><li>establishment of network or body to facilitate institutional links and mapping core processes </li></ul></ul><ul><li>Cross-fertilisation eg CRISPool worked with JISC projects Enquire, ERIS, used R4R mapping advice and examples </li></ul><ul><li>Enquire further modified EPrints RAE add-on developed by JISC IRRA project – to include impact information (code to be available via the EPrints Bazaar) </li></ul>
  13. 13. Technical synthesis <ul><li>Next step </li></ul><ul><ul><li>stand-alone document, or integrated within Infokit… </li></ul></ul>

×