Yeager-Renfrow Oral Histories

This repo was constructed from a cb-oralhistory fork of the original https://github.com/CollectionBuilder/cb-oralhistory project COMBINED with elements of CollectionBuilder base repo (with Grinnell College specifics) that was itself derived from a CB experiment housed in https://github.com/Digital-Grinnell/black-library-CB-CSV-experiment.

The documentation below the cb-oralhistory and CollectionBuilder-CSV headings are specific to the original repos and preserved here for reference only.

Yeager Collection

| Link | Description |
| --- | --- |
| https://docs.google.com/spreadsheets/d/1z2W5L8JVdNcqaPdNZyXAThw2wnf7TSUK2Y2giO9i6NM/edit?gid=663101020#gid=663101020 | The project's public metadata spreadsheet. | | | main branch deployed to Azure Static Web Apps |
| https://docs.google.com/spreadsheets/d/1z2W5L8JVdNcqaPdNZyXAThw2wnf7TSUK2Y2giO9i6NM/edit?gid=823757564#gid=823757564 | "From the Documentation" portion of our Google Sheet | | | OneDrive folder |

Building as an Azure Static Web App

Following the guidance provided in Deploy your web app...

I choose the jekyll build option rather than Custom and got this workflow file AND the env: section was added to complete the Azure config...

```yml name: Azure Static Web Apps CI/CD

on: push: branches: - main pull_request: types: [opened, synchronize, reopened, closed] branches: - main

jobs: buildanddeployjob: if: github.eventname == 'push' || (github.eventname == 'pullrequest' && github.event.action != 'closed') runs-on: ubuntu-latest name: Build and Deploy Job steps: - uses: actions/checkout@v3 with: submodules: true lfs: false - name: Build And Deploy id: builddeploy uses: Azure/static-web-apps-deploy@v1 with: azurestaticwebappsapitoken: ${{ secrets.AZURESTATICWEBAPPSAPITOKENYELLOWGRASS080915210 }} repotoken: ${{ secrets.GITHUBTOKEN }} # Used for Github integrations (i.e. PR comments) action: "upload" ###### Repository/Build Configurations - These values can be configured to match your app requirements. ###### # For more information regarding Static Web App workflow configurations, please visit: https://aka.ms/swaworkflowconfig applocation: "/" # App source code path apilocation: "" # Api source code path - optional outputlocation: "site" # Built app content directory - optional ###### End of Repository/Build Configurations ###### env: # Add environment variables here JEKYLLENV: production TZ: America/Chicago

closepullrequestjob: if: github.eventname == 'pullrequest' && github.event.action == 'closed' runs-on: ubuntu-latest name: Close Pull Request Job steps: - name: Close Pull Request id: closepullrequest uses: Azure/static-web-apps-deploy@v1 with: azurestaticwebappsapitoken: ${{ secrets.AZURESTATICWEBAPPSAPITOKENYELLOWGRASS080915210 }} action: "close" ```

Following the aforementioned procedure eventually produced the site https://yellow-grass-080915210.5.azurestaticapps.net/.

This workflow uses GitHub Actions to deploy and you can see the status of deployment at https://github.com/Digital-Grinnell/yeager-collection/actions.

Set Up a Custom Domain in Azure Static Web Apps

Followed the procedure documented in https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain-external AFTER Mike C. setup the necessary CNAME record in the grinnell.edu domain in order to link this site to https://yeager-collection.grinnell.edu.

Filters

The presence of a _data/filters.csv file causes CB to display the "Topics:" and "Filter by Topic" elements you see below.

Removing that configuration file produces a display without those elements as you see below.

Timeline and Time-Span

The CB documentation talks about Editing the Home Page including a sub-topic to Delete a Home Page Feature.

Since our data has no meaningful timeline elements (dates) we've elected to remove it by commenting out the {% include index/time.html %} statement in the _layouts/home-infographic.html file.

Suppressing Pages

The original config-nav.csv file looked something like this:

display_name,stub,dropdown_parent Home,/, Browse,/browse.html, Visualization,/ohdviz.html Subjects,/subjects.html, Locations,/locations.html, Map,/map.html, Timeline,/timeline.html, Data,/data.html, About,/about.html,

For this project we wanted to suppress the Visualization and Map pages so the file was modified to include only this configuration:

display_name,stub,dropdown_parent Home,/, Browse,/browse.html, Subjects,/subjects.html, Locations,/locations.html, Timeline,/timeline.html, Data,/data.html, About,/about.html,

People

Our initial "People" cloud tag was dominated by the interviewer, "Stuart Yeager", and I didn't want to remove his name from every interview transcript. Fortunately Libby directed me to look deeper and I found https://collectionbuilder.github.io/cb-docs/docs/advanced/cloudpage/#create-a-new-cloud-page-using-cloud-layout-and-front-matter in the documentation and introduced the name of our interviewer as a cloud-stopwords frontmatter element in pages/people.md and it works nicely!

The new line in the frontmatter is:

cloud-stopwords: yeager, stuart;

Subjects

Like our "People" page, our initial "Subjects" cloud tag was dominated by a single common phrase but we didn't want to remove it from line of the metadata CSV. So, as with "People" I used https://collectionbuilder.github.io/cb-docs/docs/advanced/cloudpage/#create-a-new-cloud-page-using-cloud-layout-and-front-matter in the documentation and introduced cloud-stopwords frontmatter in pages/subjects.md and it works nicely! To make this work I also had to change the cloud-fields: element of the frontmatter.

The new frontmatter is:

```

title: Subjects layout: cloud permalink: /subjects.html

Default subject page is configured in "_data/theme.yml"

cloud-fields: subject cloud-stopwords: black experience at grinnell college;

Leave cloud-fields as "site.data.theme.subjects-fields", but stopwords did NOT work until cloud-fields was changed?

cloud-fields: site.data.theme.subjects-fields

---

```

footer_description

We wanted to distinguish and differentiate our site.description data from the material that appears in the page footer so a new site.footer_description field was added to the _config.yml data AND a reference to site.description was changed to site.footer_description in the _includes/footer.html template.

cb-oralhistory

cb-oralhistory is a mix of CollectionBuilder-CSV and Oral History as Data (OHD). It's meant to serve as a starter repository for those wanting to build oral history collections with CollectionBuilder.

The current demo site features a small mix of transcripts. Item pages are generated by a CSV metadata file that includes the display_template "transcript" as a field.

About Oral History as Data

Oral History as Data (OHD) provides a static web framework for users to publish and analyze coded oral history and qualitative interviews on the web.

Oral History as Data was first built in 2018, coming out of work at the University of Idaho Library's Center for Digital Inquiry and Learning (CD?L). The framework served as the foundation for several digital humanities projects, including Voices of Gay Rodeo, Idaho Queered, and CTRL+Shift.

The look for OHD is different than CollectionBuilder. Check out the a demo site to see the differences.

There is some documentation for OHD that might be helpful in this context. More fully developed documentation for this project is being developed, but there are several places linked here to get you started.

About CollectionBuilder-CSV

CollectionBuilder-CSV is a robust and flexible "stand alone" template for creating digital collection and exhibit websites using Jekyll and a metadata CSV. Driven by your collection metadata, the template generates engaging visualizations to browse and explore your objects. The resulting static site can be hosted on any basic web server (or built automatically using GitHub Actions).

Visit the CollectionBuilder Docs for step-by-step details for getting started and building collections!

Brief Overview of Building a Collection

The CollectionBuilder Docs contain detailed information about building a collection from start to finish--including installing software, using Git/GitHub, preparing digital objects, and formatting metadata. However, here is a super quick overview of the process:

• Make your own copy of this template repository by clicking the green "Use this Template" button on GitHub (see repository set up docs). This copy of the template is the starting point for your "project repository", i.e. the source code for your digital collection site!
• Prepare your collection metadata following the CB-CSV template (see our demo metadata template on Google Sheets and metadata docs). Your metadata will include links to your digital files (images, pdfs, videos, etc) and thumbnails wherever they are hosted.
• Add your metadata as a CSV to your project repository's "_data" folder (see upload metadata docs).
• Edit your project's "config.yml" with your collection information (see site configuration docs). Additional customization is done via a theme file, configuration files, CSS tweaks, and more--however, once your "config.yml" is edited your site is ready to be previewed.
• Generate your site using Jekyll! (see docs for how to use Jekyll locally and deploy on the web)

Please feel free to ask questions in the main CollectionBuilder discussion forum.

---

CollectionBuilder

https://collectionbuilder.github.io/

CollectionBuilder is a project of University of Idaho Library's Digital Initiatives and the Center for Digital Inquiry and Learning (CDIL) following the Lib-Static methodology. Powered by the open source static site generator Jekyll and a modern static web stack, it puts collection metadata to work building beautiful sites.

The basic theme is created using Bootstrap. Metadata visualizations are built using open source libraries such as DataTables, Leafletjs, Spotlight gallery, lazysizes, and Lunr.js. Object metadata is exposed using Schema.org and Open Graph protocol standards.

Questions can be directed to collectionbuilder.team@gmail.com

License

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.

Black Library Project Resources

|https://grinco-my.sharepoint.com/:f:/r/personal/caveelizabethgrinnelledu/Documents/Black%20Library%20items?csf=1&web=1&e=7e6prh| OneDrive folder |

| Link | Description |
| --- | --- |
| https://docs.google.com/spreadsheets/d/17uNXLP5aTSCfYZ8FXBqTvDd-z0F19FJeAOK5TsCr-PI/edit | The project's public metadata spreadsheet, built from https://docs.google.com/spreadsheets/d/1nNk4JQB4LJraIzns7WcM3OXK-xxGMQhW1shMssflNM/edit#gid=1973435486 and our SHEETS predecessor. | | https://zealous-rock-08144ee10.4.azurestaticapps.net | main branch deployed to Azure Static Web Apps |
| https://docs.google.com/spreadsheets/d/17uNXLP5aTSCfYZ8FXBqTvDd-z0F19FJeAOK5TsCr-PI/edit#gid=823757564 | "From the Documentation" portion of our Google Sheet | | https://grinco-my.sharepoint.com/:f:/r/personal/caveelizabethgrinnell_edu/Documents/Black%20Library%20items?csf=1&web=1&e=7e6prh | OneDrive folder |

---

Running Locally

zsh bundle exec jekyll serve

objectid Convention

grinnell_<index> denotes a legacy object imported from Digital.Grinnell.
dg_<epoch> denotes a new object NOT imported from Digital.Grinnell. <epoch> is a simple 10-digit UNIX epoch time generated when the object is cataloged.

Building as an Azure Static Web App

Following the guidance provided in Deploy your web app...

I choose the jekyll build option rather than Custom and got this workflow file...

```yml name: Azure Static Web Apps CI/CD

on: push: branches: - main pull_request: types: [opened, synchronize, reopened, closed] branches: - main

jobs: buildanddeployjob: if: github.eventname == 'push' || (github.eventname == 'pullrequest' && github.event.action != 'closed') runs-on: ubuntu-latest name: Build and Deploy Job steps: - uses: actions/checkout@v3 with: submodules: true lfs: false - name: Build And Deploy id: builddeploy uses: Azure/static-web-apps-deploy@v1 with: azurestaticwebappsapitoken: ${{ secrets.AZURESTATICWEBAPPSAPITOKEN<GENERATEDHOSTNAME> }} repotoken: ${{ secrets.GITHUBTOKEN }} # Used for Github integrations (i.e. PR comments) action: "upload" ###### Repository/Build Configurations - These values can be configured to match your app requirements. ###### # For more information regarding Static Web App workflow configurations, please visit: https://aka.ms/swaworkflowconfig applocation: "./" # App source code path apilocation: "" # Api source code path - optional outputlocation: "site" # Built app content directory - optional ###### End of Repository/Build Configurations ######

closepullrequestjob: if: github.eventname == 'pullrequest' && github.event.action == 'closed' runs-on: ubuntu-latest name: Close Pull Request Job steps: - name: Close Pull Request id: closepullrequest uses: Azure/static-web-apps-deploy@v1 with: azurestaticwebappsapitoken: ${{ secrets.AZURESTATICWEBAPPSAPITOKEN }} action: "close" ```

Following the aforementioned procedure eventually produced the site https://zealous-rock-08144ee10.4.azurestaticapps.net.

This workflow uses GitHub Actions to deploy and you can see the status of deployment at https://github.com/Digital-Grinnell/black-library-CB-CSV-experiment/actions?query=workflow%3A%22Azure%20Static%20Web%20Apps%20CI%2FCD%22%20branch%3Amain.