Empire State Digital Network (ESDN) is a New York State service hub for DPLA. This brief project update was presented at the ASCLA Collaborative Digitization Interest Group at ALA Midwinter 2015 in Chicago.
Empire State Digital Network (ESDN) Project Update for ASCLA-CDIG, Midwinter 2015
1. EMPIRE STATE
DIGITAL NETWORK
New York Service Hub of the DPLA
Kerri Willette, ESDN Manager
ASCLA Collaborative Digitization Interest Group
January 31, 2015
4. Timeline
• Hire staff
• Convene advisory &
working groups
• Develop infrastructure
• Establish workflows
• Gather data from NY 3Rs
hosted collections
• Create and distribute
guidelines for contribution
• Outreach to LAMS
statewide
• Grow New York content in
DPLA
Phase 1
October 2013 - April 2015
Phase 2
May 2015 - April 2016
8. Mapping
MODS is mapped to the DPLA MAP (Metadata Application Profile)
http://dp.la/info/developers/map/
Closely follows DPLA’s preferred MODS implementation (NCDHC!)
9. Required/Recommended Fields
Required (per record)
Title
Rights
Link to record on local site
Link to content preview (where applicable)
Thumbnail
Other fields recommended and/or optional
Place
Subject
Date
Type
Language
http://www.mnylc.org/esdn/contributors/metadata-
requirements/
10. Next Steps
DPLA is harvesting our first set of almost 90,000 records now.
New York State content should be live in DPLA in late February.
We’ll open up contributions more broadly in April.
NY3Rs is a collaborative of 9 library resources councils statewide. ESDN is administered by the NY3Rs but we’re hosted and funded primarily by one of those regions, METRO.
There are 4 regionally supported collaborative digitation projects in the state. These are supported by the regional councils. Each of the councils has a digital services manager or coordinator on staff. ESDN is coordinating with these council liaisons to coordinate contributions to DPLA statewide.
So, When the ESDN was announced in OCT 2013, a 3-year project plan was put in place. The plan was divided into two phases.
As you can see, we are now in the home stretch of Phase 1 which has focused primarily on laying the necessary groundwork to get the hub up and running.
Now we’re preparing to move into phase 2 this spring. Phase 2 is when the hub will really open for business. That’s when we will begin to open up participation more broadly throughout the state.
Phase 1 – we primarily focused on hosted 3R’s collections in the state – ie. low hanging fruit. We used select collections from regional projects and a few additional partners to get our infrastructure and workflows ironed out.
Phase 1
First contribution to DPLA – happening now! 89,626 records
Schedule monthly ongoing harvests
Coordinate outreach and communication through 3R’s regional liaisons in preparation for Phase 2
So when we open up contribution more broadly in Phase 2 and begin bringing in content from all sorts of organizations statewide, we have some idea now of what our process needs to look like.
Phase 2
Broaden contribution
Streamline contribution processes
Continue adding regionally hosted content
Work with regional liaisons to include non-hosted partners statewide
Grow New York content in DPLA
Of course not every institution in the state has their digital content in one of these hosted projects. So, in addition to growing content from the existing hosted projects, regional liaisons will also facilitate partnerships with institutions that host collections locally.
The ESDN Regional Liaisons are already meeting as a group and working with ESDN staff to coordinate consistent and clear communication statewide.
Partner metadata coming from CONTENTdm, Islandora, CollectiveAccess, ArchivalWare, etc. – 71 institutions
Pull in data from multiple formats map to ESDN’s MODS model. We apply transformations to address weird system quirks, to fix inconsistencies in date fields and other provider idiosycracies. We output one single stream of normalized data to DPLA.
Mapping our “single stream of data”, MODS, to the DPLA Metadata Model.
Benefited from work of existing service hubs, like North Carolina Digital Heritage Center, who are also providing MODS to the DPLA
DPLA MAP specifies required/recommended fields
Few required fields, more optional and recommended fields
Low-barrier to entry
Work 1 on 1 with partners – do field mapping in spreadsheets – use some tools developed by NC to review various aspects of the data and send feedback to the institution to do clean-up or mapping changes.
Check for presence of required and recommended fields
Review data feed for inconsistencies and mapping issues
Help to configure/troubleshoot OAI
Provide feedback to partners
We don’t ever have direct access to our providers’ data. Sometimes we’re two or three steps away from direct contact with providers, so communicating changes can be cumbersome.