1. DSpace

2. TM 2 Agenda  Introduction to DSpace  DSpace community  Institutional Repository  Easy to add/find content in DSpace  Building Online Communities  DSpace Demo  Q&A

3. TM 3 What is DSpace?  Captures  Digital research material in any formats  Directly from creators (faculty)  Large-scale, stable, managed long-term storage  Describes  Descriptive, technical, rights metadata  Persistent identifiers  Distributes  Via WWW, with necessary access control  Preserves  Bitstream guaranteed

4. TM 4 History In yr 2000 Hewlett Packard Labs and M.I.T collaborated to create an open source software solution for archiving digital content

5. TM 5 History of DSpace Formation of Foundation summer 2007 to support the community and develop the platform

6. TM 6 Community  ~250 registered live sites  World-wide adoption  >1m digital assets and growing fast, largest sites several hundred thousand items  Profile  Primarily research and higher education institutions  Cultural heritage organizations, state libraries/archives  Some commercial users and service providers  Goals  Open Access/Content sharing  Long-term archiving and preservation  Branding and promotion through aggregation

7. TM 7 A select list of current installations  MIT MIT  University of Cambridge, England  University of Michigan  University of Texas  Glasgow University, Scotland  Beihang University, China  University of Minnesota University of Minnesota  University of Delaware  New York University  University of Toronto  University of Illinois, Urbana Champaign  Cornell University Cornell University  University of Tokyo, Japan  Australia National University Over 250 organizations worldwide

8. TM 8 Key Factors to DSpace’s adoption  Open source, freely available  Great support network of current users World Wide  Easy to use as packaged  Can handle a multitude of digital formats  Initially developed by leading institutions  Content all accessible through Google ScholarGoogle Scholar

9. TM 9 Institutional Repository  Institution-based  Scholarly material in digital formats  Cumulative and perpetual  Open source and interoperable  Potentially new publishing models  Provides faculty with long-term storage of research data and publications

10. TM 10 Why Libraries?  Expertise  Large-scale collection management  Assessment/collection policies  preservation  Metadata  Solid business practices  Commitment  Long time frames  Fits with Libraries’ mission

11. TM 11 Digital Preservation  Philosophy  Lots of digital material is already lost  Most digital material is at risk  Better to have it, do bit preservation than to lose it completely  Need to capture as much information as possible to support functional preservation  Cost/benefit tradeoffs

12. TM 12 DSpace Information Model  Communities  Research units of the organization  Collections (in communities)  Distinct groupings of like items  Items (in collections)  Logical content objects  Receive persistent identifier  Bitstreams (in items)  Individual files  Receive preservation treatment

13. TM 13 Possible DSpace Content  Articles  Preprints, e-prints  Technical Reports  Working Papers  Conference Papers  E-theses  Audio/Video  Datasets  Statistical, geospatial  Images  Visual, scientific  Teaching material  Lecture notes, visualizations, simulations  Digitized library collections

14. TM 14 Communities  Departments, Labs, Research Centers, Programs, Schools, etc.  Localized policy decisions  Who can contribute, access material  Submission workflow  Submitters, approvers, reviewers, editors  Collections definition, management  Communities supply metadata  Or contract with library

15. TM 15 Easy to Use  Easy to add content  Easy to browse and search content  Permanent identifier for your content

16. TM 16 Submitting Content

17. TM 17 Searching/Browsing Content

18. TM 18 Search  All metadata and text is indexed and fully searchable  Can customize which fields you want to enable browsing  Can choose what fields and text you want to index for search

19. TM 19 Content indexed in Google Scholar

20. TM 20 Rights management  Can assign creative commons license to your work to allow others to share, remix or reuse if you wish  Creativecommons.org Creativecommons.org

21. TM 21 Metadata  Currently uses standard Dublin core descriptive metadata  Possible to extend fields as you wish  Possible to import MARC and MODs but lose hierarchal structure  Supports any named space flat non-hierarchal metadata schema

22. TM 22 Other areas you can customize  Submission process- you can configure the submission steps to suit your organization  Browse and search terms- can set what fields and files you choose to index and display in the browse interface  Database- can choose Postgres or Oracle  OAI-PMH-can expose your catalog for harvesting and access  Extend DSpace to work with other web services- using Light Network Interface you can pull or push content to/from DSpace  User interface- you can create your own user interface

23. TM 23 Next Steps: Build a Community  Work with DSpace team on campus to create a Community  Add content  Use metadata (keywords, descriptions) to aid search and retrieval  Update community’s content with new research

24. TM 24 For More Information Go to www.DSpace.orgwww.DSpace.org  FAQs  Articles on DSpace  Case studies  Information on scholarly communication, digital preservation, etc.

25. TM 25