Published on

  • Be the first to comment

  • Be the first to like this


  1. 1. DSpace: Or How an Electronic Resource Management Enterprise at MIT Solved all the Problems of the Digital World. Butch Lazorchak CRADLE July 14, 2003
  2. 2. DSpace: What is it, exactly? <ul><li>A Digital “Depository” </li></ul><ul><li>A Digital “Repository” </li></ul><ul><li>An Open Source Software Platform </li></ul><ul><li>A Groundbreaking Digital Library System </li></ul><ul><li>A Specialized Type of Digital Asset Management or Content Management System </li></ul>
  3. 3. Commercial Digital Asset Management Systems (DAMS) <ul><li>Documentum </li></ul><ul><li>MediaBin/Interwoven </li></ul><ul><li>North Plains Systems-Telescope product </li></ul><ul><li>Artesia </li></ul><ul><li>Oracle Intermedia </li></ul><ul><li>Lots of others… </li></ul>
  4. 4. Welcome to Acronymland! OCW-Open Courseware DSpace-“digital space,” “design space,” “dissemination space” or some combination of all or none of those Invent@MIT, the HP-MIT Alliance (a joint venture) MIT Libraries operate DSpace at MIT MITCET-MIT Council on Educational Technology
  5. 5. <ul><li>MIT libraries has a particular mission for the MIT instantiation: </li></ul><ul><li>to provide stable long-term storage to house the digital products of MIT faculty and researchers; </li></ul><ul><li>to provide long-term preservation for digital materials in a variety of formats, including text, audio, video, images, datasets and more; </li></ul><ul><li>and to enable remote access to those materials through one coherent interface. </li></ul>
  6. 6. <ul><li>DSpace: What’s it look like? </li></ul>
  7. 7. Why is Dspace all the hype? <ul><li>Complete, easy-to-read documentation, understandable by non-technologists </li></ul><ul><li>Standards-based (Dublin Core, XML, established/robust open source software), allowing it to easily co-exist with established/co-developing systems </li></ul><ul><li>An implementation design plan that is easy to follow (even if earlier versions of the software were buggy) </li></ul><ul><li>The design originated in the library system (as opposed to the CS department), emphasizing the importance of library considerations (and bolstering the techno-confidence of librarians everywhere) </li></ul><ul><li>Sexiness of the name (relatively speaking), the MIT connection, the dollar power of HP, and first to market (of the research solutions?) </li></ul>
  8. 8. They’ve figured it all out: <ul><li>Complete digital asset management system </li></ul><ul><li>Open source solution </li></ul><ul><li>Support for long-term preservation </li></ul><ul><li>All data types supported, including ones that haven’t even been invented yet </li></ul><ul><li>Protects and guarantees the authenticity of the digital materials over time </li></ul><ul><li>Bundles rights management information with each digital artifact </li></ul><ul><li>Supports interoperability </li></ul>
  9. 9. DSpace: the elegant integration of user-centered and system-centered capabilities <ul><li>Users </li></ul><ul><ul><li>Contributors </li></ul></ul><ul><ul><li>Researchers </li></ul></ul><ul><ul><li>End Users </li></ul></ul><ul><li>Content and Services </li></ul><ul><ul><li>Content Types </li></ul></ul><ul><ul><li>Submission Process </li></ul></ul><ul><li>Technology </li></ul>
  10. 10. Who are These “Users” <ul><ul><li>Contributors </li></ul></ul><ul><ul><ul><li>MIT Faculty exclusively (at the moment) </li></ul></ul></ul><ul><ul><li>Researchers </li></ul></ul><ul><ul><ul><li>Federators (Columbia, Cornell, Ohio State, U’s of Rochester, Washington, Toronto) </li></ul></ul></ul><ul><ul><li>End Users </li></ul></ul><ul><ul><ul><li>Everybody in the whole, wide world </li></ul></ul></ul>
  11. 11. Content and Services <ul><li>Content Types- </li></ul><ul><ul><li>Any kind of digital content imaginable </li></ul></ul><ul><ul><li>Long-term preservation support for the actual bits is guaranteed </li></ul></ul><ul><ul><li>Software types are maintained and supported through the use of a bitstream manager </li></ul></ul><ul><li>Submission Process </li></ul><ul><ul><li>A Sharium! Decentralized submission process </li></ul></ul><ul><ul><li>Ingest process which incorporates human-edited and machine-annotated processes </li></ul></ul><ul><ul><li>Provenance and authentication through the use of checksums </li></ul></ul><ul><ul><li>Handle System persistent identifiers </li></ul></ul><ul><ul><li>Rights management utilizing Creative Commons licenses </li></ul></ul>
  12. 12. Technology <ul><li>Open Source-get it at SourceForge </li></ul><ul><li>Scalable-from your laptop to the mountaintop (as long as it’s a Unix-type environment) </li></ul><ul><li>Dublin Core DC-LIB metadata schema, but SIMILE (Semantic Interoperability of Metadata and Information in unLike Environments) is on the way ( http://web.mit.edu/dspace-dev/www/simile/ ) </li></ul><ul><li>Interoperability (Semantic Web, OAI); Intelligent Agents; Complex metadata schemas </li></ul>
  13. 13. DSpace: Good <ul><li>A Complete Scalable System </li></ul><ul><ul><li>Providing for Long-term </li></ul></ul><ul><ul><ul><li>ACCESS </li></ul></ul></ul><ul><ul><ul><li>PRESERVATION </li></ul></ul></ul><ul><ul><ul><li>AUTHENTICITY </li></ul></ul></ul><ul><ul><ul><li>RIGHTS MANAGEMENT </li></ul></ul></ul><ul><li>Outside of propriety constraints </li></ul><ul><li>And with a vision of how digital information can serve us in the future </li></ul>
  14. 14. <ul><li>It is important to note that the DSpace system operates entirely within the open-source software framework, freeing it from the encumbrances of proprietary software. The prerequisite software for DSpace includes a UNIX-like operating system (HP/UX, Linux, Solaris or Macintosh OS X), though the application itself is written in Java. The tested versions of the following software are also required; Java 1.3 or later; Tomcat 4.0; Apache 1.3; Ant 1.4; and PostgreSQL 7.2.3 [i] . DSpace also utilizes Lucene, a Java freeware search engine, and the user interface Resin, a Java Servlet engine which also provides support for Java Server Pages. The user interface is entirely web-based at this time, which provides for very simple interaction with the system. </li></ul><ul><li>In terms of hardware, DSpace has no specific requirements (the software is designed to run on everything from a laptop to an expensive server), but they do include general recommendations for a system designed for a research university: a reasonably good server (e.g. Sun Fire 280R Server, two 900Mhz UltraSPARC-III Cu processors, 8MB E-cache, 2GB memory, two 36GB 10,000rpm HH internal FCAL disk drives, DVD) and a decent amount of disk storage (e.g. 436-GB, or 12 x 26.4 Gbyte 10K RPM disks, Sun StorEdge A1000 rackmountable w/1 HW RAID controller, 24MB std cache). With tape backups and accessories the system above should cost around $30,000. [ii] </li></ul><ul><li>[i] &quot;DSpace System Documentation: Operation,&quot; http://dspace.org/technology/system-docs/operation.html (accessed 22 February 2003). </li></ul><ul><li>[ii] &quot;FAQ: DSpace: MIT Libraries,&quot; http://dspace.org/what/faq.html (accessed 22 February 2003). </li></ul>Do you want to set up a DSpace system?