1 / 8

Workshop Session Repository Integration - Possibilities and Pitfalls

Workshop Session Repository Integration - Possibilities and Pitfalls. Bill Hubbard Head of Centre for Research Communciations. RSP ‘Goes back to’ School Matfen Hall, September 2009. Repository Darwinism. Repositories have mission creep? or Repositories are evolving?

ismail
Download Presentation

Workshop Session Repository Integration - Possibilities and Pitfalls

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Workshop SessionRepository Integration - Possibilities and Pitfalls Bill Hubbard Head of Centre for Research Communciations RSP ‘Goes back to’ School Matfen Hall, September 2009

  2. Repository Darwinism • Repositories have mission creep? or • Repositories are evolving? • Growing into a well-populated environment • Some turf has been well marked • Some clear and fertile pasture • Isolation will mean extinction • Mix that DNA!

  3. Repository Integration • What related interfaces/systems/databases are there in your institution? • What system tie-ups are desirable? • What ways can the repository be used? • What replication of information exists across systems? • What about workflows for gathering and using material -- and what systems/interfaces support these?

  4. Separate functions interfaces systems databases

  5. Exercise: model an ideal system • Identify all of the related interfaces, systems and databases in your institution • Place these on the model of interface/ system/ database • Identify overlaps, synchronicities, gaps - which could be filled with innovative and useful systems • Draw out workflows between each component • Identify owners of each component and each workflow

  6. Guidelines • Think about relationships between systems • Think about political aspects of control and authority • Ingest once, store once, use many times • Ensure authority for each point of information can be backtracked to an appropriate authority

  7. Bill Hubbard bill.hubbard@nottingham.ac.uk

  8. ----------------------------------------------------

More Related