JISC research information management phase 1 technical synthesis
Upcoming SlideShare
Loading in...5

JISC research information management phase 1 technical synthesis






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

JISC research information management phase 1 technical synthesis JISC research information management phase 1 technical synthesis Presentation Transcript

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