District Digital Dashboard

District Digital Dashboard

Service Hub - single state

Contacts

Name and URL

District Digital

Point of contact

Aaron Krebeck
Digital Services Librarian
Washington Research Library Consortium
krebeck@wrlc.org

Robert LaRose (DCPL) (Metadata + Ingest)
robert.larose@dc.gov

Gloria Sena (Metadata + Ingest)
sena@wrlc.org

Network Council Rep and Alternate

Paul Kelly, Representative

Staff Profile

District Digital is managed by Washington Research Library Consortium (WRLC) and DC Public Library (DCPL). Administration and outreach is handled by DCPL; technical operations are handled by WRLC. Together, WRLC and DCPL contribute services of two FTEs, with total shared responsibilities comprising roughly one FTE.

Number of Partners

8

Current Record Set

https://dp.la/search?partner=%22District%20Digital%22

Organization

Year accepted

2017

Date of First Ingest

May, 2018

Lead/Key Institutions

Principal partners: Washington Research Library Consortium and DC Public Library. Contributing partners: American University, Catholic University of America, Galludet University, Georgetown University, George Washington University, Marymount University, University of the District of Columbia.

Services Offered

Our service model is still developing.  We are planning the following:

 

  1. The formation of a committee to standardize metadata standards for submitting to District Digital.

  2. Possible training and support for organizations who would like to contribute to District Digital.

 

We plan to offer all services at no cost.

Hub Ingest Details

Feed location

https://repox.wrlc.org/repox2/OAIHandler

Metadata Prefix

qualified-dublin-core

Firewall

No

Sets to include

all

Aggregation Technology

District Digital utilizes a dark Islandora repository, and Repox for aggregation.

State/regional portal

n/a

DPLA Ingest Details

Ingestion Profile

n/a ingestion 3

MAP Crosswalk

crosswalk

Mapping (code)

ingestion3 mapping

Harvester

ingestion3 OAI harvester

DPLA ID based on

"dc" + <header><identifier>

For details of ingest scheduling see the Hub Re-Ingest Schedule