Sandra McIntyre, Director
Rebekah Cummings, Assistant Director/Outreach Librarian
Tuesday, January 7, 2014
11:00 a.m.-12:00 noon MST / 10:00–11:00 a.m. PST
The Mountain West Digital Library (MWDL) provides a central search portal to over 800,000 digital resources from memory institutions in Utah, Nevada, Idaho, Arizona, and Hawaii. MWDL partners typically work with one of approximately 30 MWDL hosting hubs. Hubs assist partners by providing digital collections training, digitization services, and repository hosting services. Through the hubs model MWDL supports a distributed digital collections network around the Mountain West and works to expand digital library services to additional memory institutions in the region.
In this webinar, Sandra and Rebekah will provide background on the hubs model, explain the different kinds of MWDL hubs, and discuss the need to update the current model of service. Time will be allotted for questions and discussions about the needs of both hubs and partners, and for ideas about how MWDL can modify the hubs model in the future.
4. MWDL Partnership
Agreement
• Created March 14, 2008
• Not a legal contract but a
“statement of intent.”
• Outlines responsibilities of
partners, hubs, and MWDL as
well as
goals, governance, and
guidelines.
5. Infrastructure
Three tiered model
• Collections Partners Tier (“Partners”) –
Own and manage collections
• Hosting Tier (“Hubs”) Host the digital materials
• Central Aggregating
Server Tier (MWDL) –
Harvest metadata from hubs
6. Hub Levels
Three levels of Hosting Hubs (Tier 2)
• Level 1: Contributing Institutions –
Host their own collections and share at least
one collection with MWDL.
• Level 2: Regional Hosting Hubs –
Host material from at least one other
institution.
• Level 3: Full-Service Hosting Hubs –
Provide digitization services as well as
hosting services to partners.
7. Model 1: Contributing
Institutions
Contributing Institution:
•
•
•
•
•
Curates own content
Assigns own metadata
Digitizes own material (or contracts privately)
Has its own server and DAMS
Opens up its own collections for harvest
8. Model 2: Regional
Hosting Hub
Partners:
Regional Hosting Hub:
• Curate collections
• Assign metadata
• Digitize own materials
• Hosts the digital collections
of at least one additional
partner
• Trains partners in using DAMS
9. Model 3: Full-Service
Hosting Hub
Partners:
Full-service Hosting Hub:
• Curate collections
• Assign metadata
• Hosts digital collections
• Provides digitization services
• Trains partners in using DAMS
12. Currently harvested:
• University of Utah, J. Willard Marriott
Library, CONTENTdm Repository
• BYU, CONTENTdm Server Repository
• BYU, Finding Aid Repository
• UNLV, CONTENTdm Repository
• Idaho State Historical Society, CONTENTdm
Repository
• Arizona Memory Project
• UNR Libraries Digital Conservancy
• Utah State University, Digital Commons
• Utah State University, Digital Library
• Utah State Digital Archives
• Utah State Archives and Records Service
Indexes
• Southern Utah University, Sherratt Digital
Library Collections
• Weber State University Stewart Library
Digital Collections
• Utah Valley University Digital Archives
• Salt Lake Community College Digital
Collections
• Utah Digital Archives Finding Aids
List of hosting hubs/
repositories
In Progress/Not yet harvested:
• UNLV Digital Commons
• University of Idaho Digital Collections
• Northern Arizona University Cline Library
Special Collections and Archives
• Montana Memory Project
• Utah Division of Arts and Museums Digital
Repository
• Utah Education Network College eMedia
• Family Search International
• LDS Church History Library
• Stacks: The Idaho Digital Repository
• Boise State University
• Snow College Digital Repository
• BYU Howard W. Hunter Law Library
• Highway 89
On hold due to technical issues:
• Utah Government Publications Online
Digital Library
13. Benefits of
Tiered Network
• People who are closest to the materials
curate collections and assign metadata
• Provides flexible, scalable infrastructure
• Consolidates equipment and expertise
• Reinforces standards and policies
• Creates a platform for collaborative work
15. Metadata Standards
for Interoperability
• Created by a 12member task force of
UALC Digitization
Committee
• Qualified Dublin Core
• Metadata mappings to
QDC from other
systems
• 8 required fields; 2
other mandatory-ifapplicable fields
16. Training
• 2008: tied to Hub-Partner relationship
• Other options:
– MWDL centralized training – webinars and
workshops
– MWDL staff on-site training at Partner sites
– Third-party training organizations
18. Governance
• Selection of materials is up to Partners.
• Hubs are independent and selfmanaging, select services to offer to
Partners.
• MWDL is governed by UALC
Council, with policies recommended by UALC Digitization
Committee.
– In-person Committee meetings semi-annually
– Virtual meetings of task forces, ongoing
19. Current Task Forces
Active:
• Geospatial Discovery
Task Force
• DAMS Interest Group
• Outreach Task Force
• Training Task Force
• Pioneers in Your Attic
Forming/re-forming:
• Institutional
Repositories Task
Force
• Digital Preservation
Task Force
• Data Curation Task
Force
• Linked Data Task
Force
20. Governance
19
repositories
11
repositories
UALC UALC UALC UALC UALC
UALC UALC UALC UALC UALC
Hub Hub Hub Hub Hub
Hub Hub Hub Hub Hub
New New New
New New New
Hub Hub Hub
Hub Hub Hub
UALC UALC UALC UALC UALC
UALC UALC UALC UALC
Hub Hub Hub Hub Hub
Hub Hub Hub Hub
New New New
New New
Hub Hub Hub
Hub Hub
21. Funding
• LSTA: Start-up funds in early 2000s for four
hub servers and training
• Partners: discounted fees to Hubs for
services; no fees to MWDL
• UALC: $116,000 in 2009 for Ex Libris Primo
“piggyback” license
• UALC: approx. $90,000/yr. in Utah State
funds
– Director position
– Outreach supplies and travel
22. Funding
• In-kind support from J. Willard Marriott
Library at University of Utah
–
–
–
–
–
–
Discovery Services support (Primo)
Other IT support: servers, systems, etc.
Offices, computers, and telephones
Financial Management services
Human Resources services
Librarian appointments
23. Funding
• Digital Public Library of America: Grants
– 3 other staff positions through Dec. 2014
– 1+ position part-time through Aug. 2015
– Direct costs for program activities through
Aug. 2015
26. New infrastructure
options
• No hosting hub: Partner works directly
with CONTENTdm Quick Start program
• No regional digitization center: All local
digitization with inexpensive scanners
• No scanning required, with intense
metadata work: EAD finding aids
• No work by Partners: centralized projects
27. Continuing Change
• Need for digital preservation services
• New standards needed, e.g., geospatial
metadata and preservation metadata
• Additional collaboration opportunities
29. Collection
Partner
Level 1:
Contributing
Institution
Level 2:
Regional
Hosting Hub
Level 3:
Full-Service
Hosting Hub
MWDL:
Aggregating
Tier
Services provided
Curation of materials
✚
Metadata assignment
✚
✚
Digitization
✚
✚
✚
Training
✚
✚
✚
Hosting in DAMS
✚
✚
Harvesting metadata
✚
Central search portal
✚
Sharing with DPLA
✚
Standards
✚
Platform for collabora’n
✚
Digital preservation
?
?
?
?
?
30. Hubs Survey
• Informally interviewed 20 hub
representatives from 18 different
institutions.
• Three main questions:
– Would you prefer an in-person
or virtual hubs meeting?
– What would you like to
get out of a hubs meeting?
– What topics would you like to
discuss?
31. Hubs Survey:
Question 1
Would you prefer an you prefer an inperson or virtual hubs meeting?
• 100% of respondents said that some inperson element was necessary to
accomplish our goals.
32. Hub Survey:
Question 2
What would you like to get out of a hubs
meeting?
1. Networking with colleagues
2. Continued training
3. Clarification on the responsibilities of hubs and hub
status
4. Forum to talk about what people are doing and
possible collaborations
5. An updated price list
33. Hub Survey:
Question 3
What topics would you like to discuss?
1.
2.
3.
4.
CONTENTdm and other alternatives
Best practices
Geospatial and rights metadata
Background of MWDL and where we are going
(including partnership with DPLA)
5. Partnership Agreement
34. Questions for
consideration
• Does this infrastructure still work?
• Is there anything that isn’t clear?
• How do we feel about the current definition
of “hub”?
• If we were to take on many more small
partners, would this system still work?
• Are there additional services that you would
like to see MWDL provide? That hubs should
provide?
36. Looking forward
• We’ve looked at…
– our current
infrastructure
– important
developments since
2008
37. Hubs Meeting
•
•
•
•
March 2014 (exact date TBD)
Salt Lake City, UT
Doodle poll for 1½ days
MWDL decision-making
–
–
–
–
Partnership Agreement
Digitization Price List
Future services models
Future funding models
• Opportunity to connect with regional hub managers
– Share best practices
– Find out what other digital libraries are doing
– Discuss important digital library topics
38. Hosting Hubs Update
Webinar #2
• February 13, 2014
• Hosting Hubs Discussion: Evaluating the
Infrastructure of the MWDL Network
39. Revising MWDL
Partnership Agrmt
• Shared Google Doc to record
ideas, suggestions, and proposed
language
• Partnership Agreement Draft
REBEKAHThanks for joining us today for the fourth session in our Winter Webinar Series, “Hosting Hubs Updates: Services, Pricing, and Highlight”Today, Sandra and I will be leading a presentation and discussion on our hubs model where we will be talking about the infrastructure of MWDL as it was set up in 2008 and recent changes that are leading us to reevaluate and start a conversation about updates and changes to MWDL. This is going to be a little different from previous sessions in that we hope to have as much discussion as we do presentation, so we are shooting for 30 minutes for background and presentation followed by 30 minutes of discussion. I’ve sent a link out to the Google Doc where we will be taking notes during the discussion portion and we encourage all of you to take notes on the Google Doc as well. You may also notice if you’ve been with us in previous sessions, that we have a new system today. Instead of GoToMeeting, we are testing out Adobe Connect. If you are having any trouble with the system or any feedback on how its working for you, feel free to send a chat to me or Sandra and we will try to help you get that sorted out any problems you may have. During the presentation everyone’s mics will be muted but if you would like to ask a question, you can use the “raise your hand” feature in Connect or simply type your question into the chat box.
REBEKAHNow we are going to launch into some background of MWDL. Some of you may have been around when this infrastructure was set in place and for the most part it has worked really well. Pause for poll question #1 on familiarity: How familiar are you with the MWDL Partnership Agreement and the roles set out for hubs?
REBEKAHWe are going to talk about a few different documents today, but the most important one is the MWDL Partnership agreement. This is the first document that a potential new partner will see if they are interested in joiningt our consortium and we usually start moving forward with a new partner once they have read the partnership agreement and acknowledged, usually in an email, the roles and responsibilities of partners in the agreement.
REBEKAHThe Partnership Agreement is not a legal contract but a statement of intenet. At this point in time we don’t require partners to sign the partnership agreement, although that may change going forward. Any partner can withdraw from the agreement as long as they give us appropriate notice. Outlines the responsibilities…
REBEKAHThree tiered modelCollections PartnerHosting Tier There are three levels of hosting hubsMost confusionPartner and Hub are not mutually exclusive terms. An institution can be a partner and a hub. For instance, the University of Utah is a collection partner. They manage and own their own digital collections. But they are also a hub that hosts and delivers content to MWDL.Central Aggregating Server Tier (MWDL)
REBEKAHThe only confusing element of the partnership agreement for most people seems to be the three levels of hosting hubs that we outline in the Partnership agreement. When I did an informal survey of some of our hub managers many people inquired what level of hub they were and that is one of the things we would like to illuminate today. There are three levels of hosting hubs. Despite the name of Level 1, it is still a hub for our purposes in the sense that they host material and send records to MWDL.
REBEKAH
REBEKAH
REBEKAH
REBEKAHHere is the universe of MWDL with the central aggregating tier, the variety of hubs, and the partners that they serve. You may notice in this diagram that Contributing institutions still have one partner bubble adjacent to the hub and that is because every hub, like the University of Reno for instance, is also a partner and may even serve more than one department within their institutions. In other words there may be people within an institution who act as a partner like a Special Collections department and different people within the same institution that serve hub functions like Digital Operations. It adds another layer of complexity, but hopefully doesn’t make this diagram too much more confusing. Now we are going to pause for another quick poll: Which kind of hub describes you best? (If you are not a hub, describe the hub that you work with.)
REBEKAH Other tasks – set digitization priorities and secure funding, assure and assign usage rightsLast slide of the hubs model summarizes the services provided by the different tiers and levels of MWDL and it just summarizes what we’ve already talked about except that it also clearly shows the services currently provided by MWDL such as training, harvesting metadata, creation of standards, and that we act as a central search portal.
REBEKAH Here is our current list of hosting hubs and repositories. In other words, these are all of the different servers that we harvest from on a hopefully weekly basis. You can see by looking at this list how many new partners we’ve taken on on the right side. Where it says in progress/ not yet harvested, these are mostly new partners that will be onboarded in 2014.
REBEKAHThere are a lot of benefits to the tiered network model that I’ve just described and we think a lot of the strength of MWDL is in how distributed our model is and what a true consortium it is. Consolidates equipment and expertise – not everyone has to be good at everything. If one person does audio-visual preservation and another person has tons of experience with newspaper digitization we can go to those people with questions and assistance. Mention distributed networkThere are benefits to a centralized organization.
REBEKAH Very briefly, this is another document that we collectively created in 2008 and it is probably time to revisit and see if it still works for everyone or if we need to make some updates here as well.
REBEKAHAnother example of the standards that we’ve set collectively has been our work around metadata standards.
REBEKAHAnother service that has been provided by the MWDL network is training. Training has traditionally been provided within the hub-partner relationship, but we’ve expanded our training services this year to include more centralized training here at MWDL. Cory and Silvia provided fabulous on-site training in linked open data last fall and we are expanding our webinars.
SANDRA
SANDRAThis technical
REBEKAHHere are the task forces of the UALC Digitization Committee. Some of these, like the Geospatial Discovery Task Force, include members outside of UALC as well. New task forces will be assessing whether to open up to all MWDL partners as well.
SANDRA
SANDRA
SANDRA
SANDRA
SANDRA
SANDRA
SANDRA
SANDRAPause for poll question: What is the most important service (or which of these services are important to you) that MWDL provides to your hub or could potentially provide to your hub? (And feel free to add more information about your response in the chat window.)
Rebekah
SANDRA
REBEKAH
REBEKAHWe will get to the discussion in just a minute, but I am going to talk about how we plan on continuing this discussion over the next few months. Emphasize that we are moving forward collaboratively
REBEKAH
REBEKAH We’ve thrown a lot at you in this webinar as far as background and would like to have one more discussion before the Hubs Meeting. We are going to have one more web conferencing/webinar session on February 13th next month. I’ll get the page up for that on our website this week and send reminders out as that day gets closer.
REBEKAHShared space where we can record ideas, make suggestions and propose language for the new partnership agreement that we hope to draft at the Hubs Meeting