Published on

Michael Emly's presentation on MIDESS at the CETIS MDR SIG meeting in Bolton on 6th May, 2008

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Sharing meta/data between repositories : lessons from the MIDESS Project Michael Emly 6th May 2008 University Library
  2. 2. <ul><li>Outline of the MIDESS Project </li></ul><ul><li>Z39.50 and information architectures </li></ul><ul><li>Metadata harvesting and OAI-PMH </li></ul><ul><li>Sharing digital objects with METS </li></ul><ul><li>Some outstanding questions </li></ul>Outline
  3. 3. <ul><li>Focused on repositories for storing digital images and other multimedia files </li></ul><ul><li>Funded by UK JISC and CURL </li></ul><ul><li>Project partners were: </li></ul><ul><ul><li>Leeds (lead site) </li></ul></ul><ul><ul><li>Birmingham University </li></ul></ul><ul><ul><li>London School of Economics </li></ul></ul><ul><ul><li>University College London </li></ul></ul><ul><li>Ran June 2005 – August 2007 </li></ul>The MIDESS Project
  4. 4. <ul><ul><li>To create demonstrator repositories at each partner site and populate with sample content </li></ul></ul><ul><ul><li>To explore the options for sharing and re-using content between institutions </li></ul></ul><ul><ul><li>To investigate the main IPR issues for this type of content </li></ul></ul><ul><ul><li>To establish appropriate metadata standards for this content </li></ul></ul><ul><ul><li>To explore the role of the repository within the institutional information architecture </li></ul></ul>Project Objectives
  5. 5. <ul><ul><li>A set of documents which can guide and inform other repository implementations: </li></ul></ul><ul><ul><li>User requirements specification based on an extensive survey of potential users </li></ul></ul><ul><ul><li>Technical and functional requirements specification </li></ul></ul><ul><ul><li>Case studies of implementation on 3 different software platforms </li></ul></ul><ul><ul><li>Major reports on </li></ul></ul><ul><ul><ul><li>Data preservation issues </li></ul></ul></ul><ul><ul><ul><li>Enterprise integration and information architecture </li></ul></ul></ul><ul><ul><ul><li>Metadata standards </li></ul></ul></ul><ul><ul><ul><li>IPR </li></ul></ul></ul><ul><ul><li>+ Investigation of OAI-PMH and METS for exchanging data between multimedia repositories (Work-packages 9 & 10) </li></ul></ul>Project Outputs
  6. 6. <ul><ul><li>Is it really different? </li></ul></ul><ul><ul><li>More diverse than “eprints” </li></ul></ul><ul><ul><li>More variation in size and use </li></ul></ul><ul><ul><li>Supporting various agendas: research, L&T, preservation … </li></ul></ul><ul><ul><li>More diverse metadata </li></ul></ul><ul><ul><li>Need to use a wider range of schemas </li></ul></ul><ul><ul><li>But users </li></ul></ul><ul><ul><li>Don’t care about technical issues </li></ul></ul><ul><ul><li>Don’t make the same distinctions between types of content </li></ul></ul><ul><ul><li>Just want what they need, wherever it is </li></ul></ul><ul><ul><li>And don’t want to reinvent the wheel if somebody has already done the work </li></ul></ul>Multimedia content
  7. 7. <ul><ul><li>Configured cross-searching of OPAC and repository at Leeds using Z39.50 </li></ul></ul><ul><ul><li>Used III Millennium LMS client – only limited configuration options </li></ul></ul><ul><ul><li>Conclusions: </li></ul></ul><ul><ul><ul><li>Field labels designed for MARC sometimes seemed odd when applied to the matching dublin core element </li></ul></ul></ul><ul><ul><ul><li>URL back to the repository object failed to display (though it was passed) so no indication of how to access the object </li></ul></ul></ul><ul><ul><ul><li>Construction of searches very different between OPAC and repository collections </li></ul></ul></ul><ul><ul><li>Better results using a federated search portal? (not available at the time) </li></ul></ul><ul><ul><li>Raised awareness of issues around information architecture – what is to be searched from where (and how) </li></ul></ul>What did we do? Z39.50
  8. 8. Active learning – one view Repository Search Student OPAC Search Library collections Digital objects E-resources Learning objects Web resources VLE Web Search Recommended reading Reading lists Directed learning Independent learning Recommended web-sites
  9. 9. And another …
  10. 10. <ul><ul><li>Institutional </li></ul></ul><ul><ul><ul><li>What is to be searched from where (and how)? </li></ul></ul></ul><ul><ul><ul><li>What protocols need to be supported? </li></ul></ul></ul><ul><ul><ul><li>What interactions are required >> system integration issues </li></ul></ul></ul><ul><ul><li>National / international </li></ul></ul><ul><ul><ul><li>What groupings of services/objects do our users wish to access </li></ul></ul></ul><ul><ul><ul><li>How do we move beyond the current focus on research outputs within the HE community? </li></ul></ul></ul><ul><ul><ul><li>Does the format of the objects matter? </li></ul></ul></ul>Information architecture: issues
  11. 11. <ul><ul><li>Harvested individual records from each system </li></ul></ul><ul><ul><ul><li>Issues around harvesting (service provider) </li></ul></ul></ul><ul><ul><li>Conducted functionality testing of each system using the University of Cape Town Dept. of Computer Science site </li></ul></ul><ul><ul><li>Tried using METS as the metadata format carried over the OAI-PMH protocol </li></ul></ul>What did we do? OAI-PMH
  12. 12. <ul><ul><li>Firewall restrictions </li></ul></ul><ul><ul><li>Support for flow control and similar compliance issues around technical compliance </li></ul></ul><ul><ul><li>Access to the object – is a URL included? </li></ul></ul><ul><ul><li>Metadata schemas </li></ul></ul><ul><ul><li>Collections within the repository – what is to be harvested? </li></ul></ul><ul><ul><li>Handling updates and deletions </li></ul></ul>Some issues in using OAI-PMH
  13. 13. <ul><ul><li>LSE – FEDORA </li></ul></ul><ul><ul><ul><li>No URL included </li></ul></ul></ul><ul><ul><ul><li>Requires Dublin Core metadata internally </li></ul></ul></ul><ul><ul><li>Birmingham – DSpace </li></ul></ul><ul><ul><ul><li>URL present </li></ul></ul></ul><ul><ul><ul><li>Only exposes Dublin Core </li></ul></ul></ul><ul><ul><li>Leeds – Curator </li></ul></ul><ul><ul><ul><li>No URL included </li></ul></ul></ul><ul><ul><ul><li>Exposes all schemas </li></ul></ul></ul><ul><ul><li>Leeds – Digitool </li></ul></ul><ul><ul><ul><li>URL present </li></ul></ul></ul><ul><ul><ul><li>Exposes all schemas </li></ul></ul></ul>Sharing metadata within MIDESS <ul><ul><li>X </li></ul></ul><ul><ul><li>X </li></ul></ul><ul><ul><li>X </li></ul></ul><ul><ul><li> ? </li></ul></ul>
  14. 14. <ul><ul><li>METS used for initial ingest of objects into Fedora at LSE </li></ul></ul><ul><ul><li>Exported METS objects from DSpace and tried to ingest into Fedora, Curator and Digitool </li></ul></ul><ul><ul><li>Fedora - ingest failed >> installed “Repository Bridge” software >> still no joy </li></ul></ul><ul><ul><li>Curator – ingest failed – but software was beta </li></ul></ul><ul><ul><li>Digitool – ingest failed – certain data in the amdSec section identified as incompatible >> manual edit >> successful ingest </li></ul></ul>What did we do? METS
  15. 15. <ul><ul><li>The standard is flexible so can be used in many different contexts </li></ul></ul><ul><ul><li>The standard is so that it cannot, in itself, guarantee interoperability! </li></ul></ul><ul><ul><li>And when it does, the receiving system must be able to process all the data contained within the object: </li></ul></ul><ul><ul><ul><li>Different schemas for descriptive metadata </li></ul></ul></ul><ul><ul><ul><li>Other metadata e.g. preservation or rights </li></ul></ul></ul>Some issues in using METS flexible
  16. 16. <ul><ul><li>Standards and protocols: </li></ul></ul><ul><ul><li>What are the implications of handling multimedia objects? </li></ul></ul><ul><ul><li>What application profiles need developing? </li></ul></ul><ul><ul><li>What will be the impact of new standards such as OAI-ORE? </li></ul></ul><ul><ul><li>Repository functionality: </li></ul></ul><ul><ul><li>What are the service drivers associated with various categories of digital object? </li></ul></ul><ul><ul><li>What developments are required in repository platforms for proper handling of multimedia? </li></ul></ul><ul><ul><li>Information architecture and service integration: </li></ul></ul><ul><ul><li>What are the key issues regarding information architecture which we need to address to meet our users’ needs? </li></ul></ul><ul><ul><li>How do repositories relate to and integrate with VLEs? </li></ul></ul><ul><ul><li>How do we integrate multimedia into a national/international information architecture? </li></ul></ul>Further work needed on …
  17. 17. <ul><ul><li>MIDESS project web-site: </li></ul></ul><ul><ul><li>http://www.leeds.ac.uk/library/midess/ </li></ul></ul><ul><ul><li>Contact Michael Emly </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul>For further information