islandora webinar: building a repository roadmap
TRANSCRIPT
Thank you for logging in.The webinar will begin shortly.
Islandora Webinar: Building a Repository Roadmap
March 25, 2015
Alan Stanley, Developer and Subject Matter Expert Erin Tripp, Business Development Manager
Agenda
Introductions• discoverygarden• Islandora
Building a Repository Roadmap • Pilot Projects• Selecting Stakeholders • Defining Scope and Requirements• Interrogating your Content
Questions
Introductions
About discoverygarden
• UPEI commercialization project launched discoverygarden in 2009
• discoverygarden is a Partner in the Islandora Foundation
• Both the Islandora Foundation and discoverygarden are dedicated to the long term sustainability of Islandora
About discoverygarden
• Primary committer of the Islandora code base
• Positioned as the leading subject matter experts on all things Islandora
• Services include installation, audit, assessment and consulting, custom development, migrations, training, etc.
• discoverygarden’s employs solution architects, developers, degree-holding librarians, quality assurance testers, and support staff boast a complete understanding of current standards.
Islandora Software Stack
Presentation & Collaboration Search & Discovery Storage & Preservation
Islandora Software: Drupal
● Provides a powerful theming layer enabling us to: ○ Utilize the latest web design trends○ Develop responsive (mobile friendly) designs
● Provides a robust administrative interface to: ○ Facilitate User, Role, Permissions○ All end user to configure Islandora○ Create content both inside and outside of Islandora
● Metropolitan New York Library Council is a great example: http://dcmny.metro.dgicloud.com/
Islandora Software: Solr
Apache Solr is an enterprise search server used for Search and Discovery in Islandora
● Provides full-text search capabilities● Near real-time indexing● Faceted search and filtering● Geospatial search capabilities
Islandora Software: Fedora Commons
Fedora commons provides a powerful framework for storage and preservation.
● Adheres to OAIS reference model ○ Support for SIPs, AIPs and DIPs
● RDF support for millions of objects● Auditing and Fixity checks● Support for virtually any file/metadata
type● Highly extendable
Islandora Solution Packs
● Standard Image● Large Image● Book● Newspaper● PDF● Audio● Video● Binary/File● Compound● Entity (person, place, event, org) ● and many more…
Islandora Community
Islandora Community
http://islandora.ca/islandora-installations
Building a Repository Roadmap
Avoid the Grocery List Approach
• A good grocery list doesn’t guarantee a good meal!
• It’s easy to get distracted by modules and tech skipping directly to the “What” and the “How”
• Consequences of building a project plan based on a list of technologies includes:• Details are overlooked
• Workflows, usability• Unforeseen integration consequences
Pilot Projects • Identify and test software
• Spend a little time/ money to save a lot
• Evaluate feasibility, time, cost, experience, performance, etc. of a scaled repository
• Gain support for a full scale project
Credit: andinuryadin
Selecting Stakeholders• Who are we planning the repository for?
• Who will be curating/ interacting with the content?• Researchers, students, technicians,
“the web”...
• Who do we want to be happy with the system?• Partners, funders, donors
• Who will be maintaining the system?
Credit: bugmenot
Defining Scope
Focus on the WHY to find your pilot objectives
• Get to know your stakeholders
• Watch users working with existing systems• Find pain points
• Ask obvious and silly questions
Credit: spadassin
Defining Requirements
Focus on the WHO to determine functional requirements
• Create user personas• e.g. Librarian, is keen on data interoperability,
prefers minimal UIs
• Create user stories to define functional requirements• As a _____ I want _____ so that _____
• Process provides context for implementers! Credit: lmproulx
Planning for Iteration
•Prioritize! Decrease complexity with a phase approach
•Determine components and dependencies
•Plan time for systems related tasks: •Building and maintaining environments, deployments
•Plan time for feedback: •Seeing working software clarifies requirements. •This is Agile project management
Credit:lmproulx
Interrogate your Content• Verify formats, locations, and identify outliers
• Sample data is 10 % of entire set, representative of the whole • Can be used to verify and identify important info• Scripted review of data is common for this process
• How will it map to the new software’s Information Architecture (i.e. datastream structure)
• Outline detailed expectations of the migrated content
• Do you have customizations your staff/ users want to maintain?
Interrogate your Content (cont..)• The nature of your content will influence:
XML FormsSolr indexing configSolr display configCollection structure
• Changes to content mapping late in the process can cascade into more issues
<titleInfo> <title>12th Street rag</title> </titleInfo> <titleInfo type="alternative"> <title>Twelfth Street rag</title> </titleInfo> <typeOfResource>notated music</typeOfResource> <genre authority="local">sheet music</genre> <originInfo> <place> <placeTerm type="code" authority="marccountry">mou</place Term> </place>
Example Repository Plan• Conduct initial tests on software (trial/ sandbox…)• Short list software/ vendor• Get pilot project approved• Identify stakeholders • Identify scope• Define requirements • Test software against requirements (standard services and features)• Revise requirements• If customization is needed, have customization professionally assessed by
a service provider• Execute phased repository project
Questions?
