Collection description text
The DMP should clearly articulate how sharing of primary data is to be implemented. It should outline the rights and obligations of all parties with respect to their roles and responsibilities in the management and retention of research data. It should also consider changes to roles and responsibilities that will occur if a project director or co-project director leaves the institution or project. Any costs stemming from the management of data should be explained in the budget notes.
The Healers interview collection consists of audio clips of interviews, as well as accompanying transcripts and translations, conducted through years of fieldwork throughout the Caribbean and the Pacific Northwest. These interviews broadly address the question: What does healing look like in the context of Afro-indigenous traditions? The interview collection will be shared with the general public using the University of Oregon’s cultural heritage digital library, Oregon Digital. It will also be deposited into the Digital Library of the Caribbean at the University of Florida. We are taking a multi-institutional approach to having the collection in both digital repositories because we believe in LOCKSS (Lots of Copies Keep Stuff Safe). However, the authoritative interviews will be held by the University of Oregon and aggregated through the Digital Library of the Caribbean not the University of Oregon.
- Alai Reyes Santos, Healers Project Principal Investigators, is the director and producer of the interview collection. She is responsible for interview collection development and complying with data management guidelines set by the Healers Project data managers. Interviews that are captured by Alai give her the authority to determine what is and is not included in the interview collection through the UO Libraries and the Digital Library of the Caribbean. It is important to note that all interviews in this collection are clips, not full interviews. This is because full explanation of the Healer’s customs and practices are restricted only to their communities. Alai is responsible for ensuring whatever interview clips become public have been approved for public sharing before archiving with UO and dLOC.
- Rachael Lee, Digital Humanities Research Assistant GE, is a Healers Project data manager. She is responsible for tracking and communicating with other Healer's data managers about all incoming interviews and organizing them within a content inventory before the interviews are treated for archival access and preservation. Rachael time on the project is grant funded and limited to its duration. Her responsibilities will be passed on to a new GE or Kate Thornhill.
- Elizabeth Peterson, UO Libraries, is a Healers Project data manager. She is responsible for managing the interview collections metadata, troubleshooting and setting up streaming media platforms, converting interview file formats, and aiding with other data curation activities.
- Kate Thornhill, UO Libraries, oversees all data management work for the Healers Project and the data management team. If any data managers leave the project, then she is responsible for their contributions and work on the interview project. She supports GEs and interns brought onto the project through data manager team training, understanding requirements and specifications for data to be formatted and interoperable for platform upload and access. She is also the administrative contact for any transcription and translation needs required through vendor services.
The DMP should describe the types of data, samples, physical collections, software, curriculum materials, or other materials to be produced during the project. It should then describe the expected types of data to be retained.
Project directors should address matters such as these in the DMP:
- the types of data that their project might generate and eventually share with others, and under what conditions;
- how data will be managed and maintained until shared with others;
- factors that might impinge on their ability to manage data, for example, legal and ethical restrictions on access to non-aggregated data;
- the lowest level of aggregated data that project directors might share with others in the scholarly or scientific community, given that community's norms on data;
- the mechanism for sharing data and/or making it accessible to others; and
- other types of information that should be maintained and shared regarding data, for example, the way it was generated, analytical and procedural information, and the metadata.
There will be a minimum of 20 interviews in this digital collection. The interviews that will be published on the web include audio (.mp3) and transcription and translation documents (.pdfs).
Data quantity: As of spring 2023, there are 20 interviews. These interviews are clips from longer ones. It is important to note that the collection will grow as more interviews are added. This means for every interview in the collection, data managers need also count the transcription and translation. So, if there are 20 interview clips then there are 20 transcriptions and 20 translations, which makes the collection contact 60 files.
Here is a breakdown of collection size, work type, file format, total number of assets, average file size, and average total size for a set of file types.
A project to generate a free and simple digital collection site using GitHub Pages given:
- a CSV of collection metadata
- a folder of JPEG images or PDF documents
Gather your digital objects together and create your metadata using the CollectionBuilder-GH Metadata Template. Then click the green "use this template" button above to create your repository, add your metadata and configure the repository to fit your collection and settings.
See Getting Started Docs for detailed information.
View the demo site.
Note:
Since collectionbuilder-gh uses GitHub Pages, it is only suitable for small collections, with lower resolution images. GitHub repositories are limited to 1GB.
If you'd like to demo CollectionBuilder, we've made a step-through tutorial using the following spreadsheet and zipped directory. (The tutorial uses items from our Psychiana Digital Collection, which is worth a visit!)
Metadata is drawn from the following Google Sheet:
Objects are collected in this zip file:
- Psychiana Digital Collection Media Files (Includes image files, pdfs, and mp3s)
These files are stored in this CollectionBuilder-gh Google Drive Folder, along with some other metadata sheets and zipped object directories that can be used for other workshops and demonstrations.
collectionbuilder-gh is intended as a simple template for hands-on teaching about digital libraries.
It can be used in a workshop setting to take participants through digitization and metadata creation, to having a live collection site hosted on GitHub.
collectionbuilder-gh aims to be well documented and easy to configure by following the example, with the potential to scaffold learning of a multitude of transferable digital and data skills.
A project in "minimal computing", it provides a depth of learning opportunities, allowing users to take complete ownership over the project and make their work open to the world.
Learn about:
- Git and GitHub basics
- Markdown, plaintext writing and content creation
- HTML, CSS, and JS literacy
- commandline literacy
- GitHub collaboration and project management
- Jekyll basics
- working in the Open, open source and open data
- digital libraries concepts such as "collections as data", minimal computing, data-driven design
We prefer commonly understood formats (such as CSV spreadsheets over YAML), and convention over configuration (follow the example over learn all the options).
- Jekyll for GitHub Pages
- Layout using Bootstrap 5
- Mapping using Leaflet.js
- Tables using DataTables
- Galleries using spotlight
- Simple lunr search
- Rich markup using Schema.org and Open Graph protocol standards
Check out the CollectionBuilder docs for how to get started, or visit the CollectionBuilder home for more information.
If you are interested in using CollectionBuilder, or are already using it, please drop us a line (libstatic.uidaho@gmail.com) since we would love to learn more about it's use in the wild. There are also currently opportunities to collaborate on CollectionBuilder.
CollectionBuilder documentation and general web content is licensed Creative Commons Attribution-ShareAlike 4.0 International.
This license does NOT include any objects or images used in digital collections, which may have individually applied licenses described by a "rights" field.
CollectionBuilder code is licensed MIT.
This license does not include external dependencies included in the assets/lib directory, which are covered by their individual licenses.