| Scott E. Siddall | |
| Denison University | |
| Prospective students envision their major by browsing your institution’s Repository of Student Scholarship | |
| Consortial faculty members share curricular and research materials because tools to catalog the content are effective | |
| Your alums read selected contributions that are reviewed and assembled into a virtual journal of creativity and scholarship |
| In 200 years… | ||||
| 29 million monographs | ||||
| 2.7 million recordings | ||||
| 12 million photographs | ||||
| 4.8 million maps | ||||
| 57 million manuscripts | ||||
| Today, globally, this volume of digital data is produced each 15 minutes | ||||
| 40% of our time spent searching; 70% of content is created anew | ||||
| [Center for Advanced Computing Research] | ||||
| Organize and use content today | ||
| Archive for the future | ||
| Of course… | ||
| Images, documents, music | ||
| But more… | ||
| Data sets, software, videos, compound items | ||
| And preserve access and authenticity | ||
| Repository with archive emphasis | |
| Metadata workflow manager | |
| Archive with granular access rights | |
| Preservation architecture |
| Flexible, modifiable | ||
| Costs: lower? Maybe, but certainly different | ||
| Technical details | ||
| Java application, Linux, Apache, Tomcat, relational database | ||
| Built on a community of innovation | ||
| Best-of-breed architecture | ||
| Modular | ||
| Interoperable, designed for integration | ||
| e.g., authentication via LDAP, CAS, AD | ||
| Group definitions | ||
| Fit easily into campus IT framework | ||
| Based on open standards | ||
| J2EE – Java program code | ||
| Mac/Windows/Unix agnostic | ||
| Metadata schema | ||
| Dublin core, METS | ||
| SQL | ||
| MySQL, PostgreSQL, Oracle | ||
| File formats | ||
| Tiff, PDF, XML, MP3 | ||
| Global Digital Format Registry | ||
| Permanent URI | ||
| Handle. net – name service from CNRI | ||
Hierarchy well-suited to consortia
| Communities | |
| Sub-communities | |
| Collections | |
| Items | |
| Bitstreams and bundles |
| Submitter | |
| Reviewer | |
| Coordinator | |
| Metadata Editor | |
| E-mail goes to each person at the appropriate step in the workflow | |
| Authorizations are set up in advance for each role in the workflow |
| Can edit metadata for own submission | |
| Can upload files for own submission | |
| Cannot do anything once item is submitted |
Reviewer and coordinator permissions
| Can review content of all files submitted to collection | |
| Can accept or reject all submissions to collection | |
| Can send a message explaining decision | |
| Rejection stops submission | |
| Acceptance lets submission go to next step (cannot edit metadata or change files) |
| Can edit metadata of all submissions to collection | |
| Submission automatically becomes part of DSpace after this step (any approval would have happened before) |
| Within a community or collection | |
| Across all communities and collections in one DSpace instance | |
| Federated searching across DSpace instances through OAI harvesting |
| News and announcements | |
| Notifications about collections | |
| Version tracking |
| Tuning the interface | ||
| Costs of metadata creation | ||
| Additional metadata schema | ||
| Small colleges | ||
| Are we consumers or developers or both? | ||
| Support – there are commercial offerings | ||
| Student theses, journals, monographs, digital collections (e.g., texts, images, multimedia) | |
| Open for submission by faculty-sponsored individuals on campus | |
| Metadata review |
| Representative management board | |
| Faculty sponsorship for collections | |
| Service level agreement |
| The university | ||
| provides routine web resources including server, space, backup, limited administrative support without any guarantees for performance or access | ||
| will maintain long-term access to content (stable URLs, archived copies, pointers to removed materials) | ||
| does not limit or charge for access to the content, and will not claim copyrights on the content | ||
| will from time to time promote the Denison University Digital Archive | ||
| The sponsor and contributor | ||
| are responsible for all content | ||
| must comply with the current Acceptable Use Policy | ||
| are fully and individually responsible for compliance with copyright laws and regulations | ||
| are responsible for page markup, uploading data, maintenance, updates, error corrections, optimization of graphics and multimedia elements, proper titling and initial metadata tagging | ||
| cannot charge for access | ||
| will apply for ISSN and will register online publication with abstracting and indexing services, if desired | ||
| retain full rights over the content, including the right to remove their archived content | ||
| Scholarly Communication – Yes! | |
| Scholarly Publication? Probably not (yet) | |
| A long-term institutional commitment |
| A demonstration site: | ||
| http://dspace.liberalarts.org/ | ||
| Login as guest@longsight.com | ||
| Password is dspaceguest | ||
| Return to home | ||