Left Menu Right Menu
May 6, 2016

Dublin Core Best Practices Approved!

The Alliance's Dublin Core Best Practices were approved by the Content Creation & Dissemination Team on April 27, adopting the recommendation of the Digital Content Joint Working Group.
The Dublin Core Best Practices are available in the Alliance's Documentation Center.
The best practices are the result of two years of work by Alliance groups. Here are the individuals who have contributed their expertise to this initiative:
Archive Engine West Working Group, 2014 September:
Stephanie Beene, Lewis & Clark College
Sam Meister, University of Montana
Tom Johnson, Oregon State University/Digital Public Library of America
Kira Homo, University of Oregon
Leigh Grinstead, Metadata Consultant
Jodi Allison-Bunnell, Alliance staff

Digital Content Metadata Working Group, 2015 September:
Ann Lally, University of Washington (chair)
Theo Gerontakos, University of Washington
Michael Boock, Oregon State University
Devin Becker, University of Idaho
Stephanie Beene, Lewis & Clark College
Rick Block, Seattle University
Jodi Allison-Bunnell, Alliance staff

Digital Content Metadata Working Group, 2016 March:
Ann Lally, University of Washington (chair)
Theo Gerontakos, University of Washington
Devin Becker, University of Idaho
Rick Block, Seattle University
Laura Buchholz, Reed College
Jodi Allison-Bunnell, Alliance staff
Here are some questions you may have about the DC Best Practices and how we are implementing them at the Alliance:
What is the purpose of the Dublin Core (DC) Best Practices?
The purpose of the Orbis Cascade Alliance’s Dublin Core Best Practices is to ensure a basic level of uniformity in the structure, encoding, and content of Alliance digital object metadata in keeping with the Mountain West Digital Library Dublin Core metadata application profile and other relevant standards, including the Digital Public Library of America metadata application profile.Promote interoperability within Alliance institutions’ metadata records developed from diverse repositoriesFacilitate access to digital content by end usersEnable implementation of the Aggregate Alliance Digital Content initiative for FY17 that was approved by Council in March. (see https://www.orbiscascade.org/file_viewer.php?id=3545 for more details)

Is use of the best practices required?
Like other Alliance best practices, use is only required for participation in shared systems, in this case digital content aggregation in the Shared ILS and (if the Alliance becomes a hub in 2017) the Digital Public Library of America.

If you do not want part or all of your digital content aggregated, you are under no obligation to make use of the DC best practices. However, use of the DC best practices is consistent with the Alliance’s Strategic Agenda: Do things once, do things together, do them the same.

Do I have to change all the metadata in my DAM or IR?
The DC Best Practices are an output standard, governing only the DC metadata that is sent to the Alliance for aggregation. Alliance institutions have two choices for creating those outputs: Change the metadata in the DAM or IR to conform with the best practices; Normalize the output to conform with the best practices
Many institutions have other places where they move or share metadata; creating this as an output standard rather than insisting on a particular input recognizes that reality.

What training will the Alliance offer in metadata cleanup?
We will offer training on metadata cleanup in FY17 based on member needs. We’ll ask about those needs, and also conduct a review of metadata to identify problem areas (beyond what we already know) systematically. If our LSTA grant application is funded, we’ll have additional staffing to support development and delivery of training. If that application is not funded, we’ll be relying on a working group to assist Alliance staff with development and training. We will receive news on our LSTA application in late May.

Will you help me enter metadata in my DAM or IR so that it creates the desired output?
Many institutions will want specific advice on how to create metadata in common systems, like CONTENTdm or Bepress, to create these outputs. That is part of the training and support we will offer in FY17. Training will consist of a mix of videos available anytime and scheduled workshops and will be on the Alliance website.

My institution doesn’t have time to do this right now. Am I obligated to start doing this work right away?
No, if your institution has other priorities, staffing shortages, or other complications you are not obligated. If we receive LSTA funding and are applying to be a DPLA hub, we’ll need 50,000 objects for the initial harvest, which is about 10% of the digital objects that Alliance institutions have in publicly available DAMs and IRs. We understand that institutions will participate at varying levels.

When will we start aggregating content in Primo?
We expect that this will happen in early 2017, depending on staffing (including outcomes of the LSTA grant application). Expect more details on this.

I’m concerned about how digital object records will function in Primo. How are we going to address this?
First, one of the assessment measures that the CCD set on this initiative calls for creating a clear organization-wide sense of what user outcomes we would like, and testing those with end users.

We can then use the he normal customer pathways with Ex Libris, including Priority Support issues and enhancement requests to get those concerns addressed. Given Ex Libris’ commitment to unified resource management, including a development initiative for managing digital objects in Alma, the company has good reasons to be responsive to the Alliance and other customers in this arena.

This action concludes the work of CCD's Digital Content Joint Working Group. A hearty thanks to its members:
Isaac Gilman, Pacific University, Chair (CCD)
Linda Crook, Lane Community College (Collaborative Workforce Representative)
Susan Hinken, University of Portland (Shared Content Representative)
Ping Fu, Central Washington University (Systems Representative)
Beth Blakesley, Washington State University (Discovery & Delivery Representative)
Rose Krause, Eastern Washington University (Content Creation & Dissemination Representative)
Jodi Allison-Bunnell, Alliance Staff
Back to Blog