1 / 6

Islandora Implementation

Islandora Implementation. Nicole Garrett Smeltekop & Megan O’Neill Kudzia Albion College. Why Islandora?. Runs on commonly-used open-source software platforms Fedora Open Commons Drupal Granular security and permissioning Active, library-heavy user community

andren
Download Presentation

Islandora Implementation

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. Islandora Implementation • Nicole Garrett Smeltekop & Megan O’Neill Kudzia • Albion College

  2. Why Islandora? • Runs on commonly-used open-source software platforms • Fedora Open Commons • Drupal • Granular security and permissioning • Active, library-heavy user community • Allows editing and control of the public face

  3. WHere We Are • Fedora Open Commons installed • Drupal with Islandora module installed • Our Drupal permissions are goofy • Currently possible to ingest objects into the Fedora repository

  4. Our Challenges • We’re getting a Drupal “Access Denied” error • Devoting staff time to development is difficult • Workflow and training management • We are still considering other options

  5. More Challenges • We are working with: • MSU Digital Curation (shout-out Aaron, Shawn, Devin, Lucas, and Eric!) • Grinnell • The Islandora and Islandora-Dev Google Groups

  6. Where We’re Going • We need an Institutional Repository to: • Provide access and storage for digital objects (College publications, research, etc.) • Maintain preservation copies as distinct from access copies • Be easy for staff and end users to navigate • Be not ugly • Work for all our stakeholders (faculty, staff departments, students) • Be migrate-able

More Related