About CollectionBuilder

About CollectionBuilder

What is CollectionBuilder?

CollectionBuilder is a set of flexible, static web templates for creating digital collection websites. These templates are driven by metadata and powered by modern static web technology. Using three primary components—a spreadsheet of metadata, a directory of assets, and a configuration file—CollectionBuilder helps users to build and customize sustainable, digital collections and exhibits for free, learning valuable development practices in the process.

How does it work?

CollectionBuilder uses the static site generator Jekyll, together with some particular workflows, to help users generate digital collections and exhibits from their own spreadsheets and digital media.

Each CollectionBuilder template exists as a repository on GitHub that users are asked to copy and modify by replacing the default values, metadata spreadsheet, and digital objects with their own. Once replaced, CollectionBuilder iterates over a user’s data to create a series of static HTML, CSS, and JavaScript files that can be served from any web server. With these customized files, CollectionBuilder builds maps, timelines, word clouds, and other visualizations, as well as browsing features, item pages, and new, reusable data formats that can be downloaded by users and processed/indexed by machines.

How Can I Use It?

We have extensive documentation to get you started. In short:

  • Choose a template that matches your project goals.
  • Go to that template’s GitHub repository.
  • Copy the template by clicking “Use This Template.”
  • Upload your metadata to the _data directory
  • And then edit the _config.yml to point to that file.

You’ll need to make sure your metadata has a few required fields, but other than that, CollectionBuilder is adaptable to a wide variety of data.

Who’s Behind This?

CollectionBuilder is designed and maintained by librarians at the University of Idaho, following the Lib-STATIC approach, a methodology committed to leveraging static-web technologies and librarians’ specialized skills in metadata and classification to create engaging web publications.

The project comes out of work done at the library’s digital humanities center, the Center for Digital Inquiry and Learning.

CollectionBuilder has received support from the University of Idaho Library. From 2019-2021, we were supported by a National Leadership Grant from the Institute for Museum and Library Services (IMLS).

What are you using to build a CollectionBuilder site?

CollectionBuilder uses 4 main components:

  1. Jekyll - a static website builder (i.e. NO SERVERS!!!) that builds websites from data files using the Liquid templating language (which you don’t need to know, but which is easily readable and usable) and Markdown files for content
  2. Git/GitHub - a way to collaborate, track changes, and import pre-built services
  3. Bootstrap 4 - a CSS/Javascript Package for easier development
  4. Data Files - We use Comma Separated Values (CSV) files that are just simple version of a spreadsheet and text files written in YAML (.yml), which are basically lists formatted in a specific fashion.

What are you using to build the visualizations and display features?

Our visualizations and features are built using a combination of our own designs with a variety of open source libraries (all of which are contained within each repository to promote site sustainability). All code is available for customization.

The open source libraries include:

What is your Design Philosophy?

Well, I don’t know if we’d call it a philosophy …

CollectionBuilder builds digital collection and exhibit sites that encourage investigation and discovery. Our item and visualization pages are built with connections between them so that a user can follow their own interests when exploring a digital collection.

Our intention is to embed users in the contents and context of a collection in order for them to experience the accretive magic of the “special collections” that archivists and librarians have labored for years to preserve and make accessible.

How does that work in practice?

For example, if a user were interested in seeing all the images in our Barnard Stockbridge Photography Collection pertaining to the 1910 “Big Burn” forest fire, they could browse the collection by searching for “fire” on the browse page.

demo image

An illustrative diagram of the ways collection items are connected to the larger context of the digital collections in which they are presented

Then, when looking at individual item pages, they could link out to the year 1910 on the timeline page and see the wide variety of images collected during that year by the studio.

And perhaps that would lead them to investigate some other subject terms or to focus on a particular town via the map.

As one examines these collections more closely, one can get a larger sense of the collection and the era, as well as its connection to one’s own area and time frame.

In short: CollectionBuilder rewards high quality metadata and description by allowing users to interactively explore it.

What is your methodology?

We call the methodology we use to build CollectionBuilder Lib-STATIC.

Do you really need a “methodology”?

Not really. No. But as we built CollectionBuilder and other static tools like Oral History as Data, we noticed that our approach was increasingly divergent from most academic library web development practice. Basically, we brainstormed some principles we were following, thought of a catchy name, and Lib-STATIC was born.

So what is Lib-STATIC?

Lib-STATIC argues that the systems libraries have been locked into, particularly concerning digital collections, serve neither the librarians/GLAM professionals that maintain them and prepare their content nor the collections we are trying to promote using them.

CollectionBuilder, like other Lib-STATIC frameworks and projects, prioritizes pragmatic, sustainable, and simplified approaches to web development infrastructure, with a focus on leveraging the particular skills of digital knowledge workers in libraries and museums, empowering them to take control of their web systems.

I’m interested. How can I get involved?

If you, or some institution you know, might be interested in adopting this tool more seriously, we can help. Please get in touch and help us guide the future of CollectionBuilder.

  • Feedback! - If you have thoughts on the documentation, tool, visualizations, user interactions, or any other features in the tool, please please please provide us with feedback. Our intention in doing workshops and presentations is to gather feedback on the tool so that CollectionBuilder can continue to grow, becoming more useable and useful.
  • Ask Questions - Get in contact on the CollectionBuilder GitHub Discussion Forum to ask any technical questions or bring up issues you encounter.
  • Contribute - If you take to the static web development model and would like to provide contributions of your own to our tool, we would LOVE to work with you and incorporate any contributions you might make. We have a code of conduct for contributors.
Current CollectionBuilder Partners

Our highest hope for this project is to enable a small army of librarians to develop the type of tools and sites that keep the GLAM professionals in control and not subservient to bloated infrastructures and/or third-party contracts. We hope you will feel drawn to help us build that community.

Where is your support coming from?

CollectionBuilder receives ongoing support in the form of staff support, development time, and funding from the University of Idaho Library.

From 2019 to 2021, we were supported by a National Leadership Grants for Libraries from the Institute for Museum and Library Services (IMLS) that helped us to build, document, and promote CollectionBuilder.

We are also currently working with colleagues from the University of Oregon on a Digital Humanities Advancement grant from the National Endowment for the Humanities (NEH) to develop digital humanities instructional modules for static web based projects and learning outcomes.

How are others using CollectionBuilder?

CollectionBuilder sites continue to proliferate around the world. Below is a list of sites we’ve noticed “in the wild.”

CollectionBuilder in the Wild

Select digital collections from users outside of University of Idaho.

Where can I learn more?

We’ve presented and written a lot about CollectionBuilder. Below is a list of our publications, workshops, and presentations.

CollectionBuilder Presentations
  • Workshop: Olivia Wikle, Evan Williamson, and Devin Becker, “Creating Digital Collections with Minimal Infrastructure: Hands On With CollectionBuilder for Teaching and Exhibits”, DHSI, 2021, https://osf.io/5q976/
  • Presentation: Olivia Wikle and Cal Murgu, “Teaching Metadata and Collection Lifecycles in the Humanities Classroom using CollectionBuilder”, ACRL Digital Scholarship Section Digital Collections Discussion Group Lightning Talk Series: Enhancing Digital Collections in Teaching and Research with Digital Tools, 2021, https://osf.io/xbcrw/
  • Presentation: Olivia Wikle, Evan Williamson, and Devin Becker, “Growing CollectionBuilder: Developing an Agile, Library-Centric Approach to Digital Collections and Scholarship Projects”, Online Northwest, 2021, https://pdxscholar.library.pdx.edu/onlinenorthwest/2021/schedule/4/
  • Workshop: Olivia Wikle, Evan Williamson, and Devin Becker, “CollectionBuilder: A Static Web Approach to Digital Projects in Libraries”, ALA Core Classroom, 2021, https://osf.io/m6bpe/
  • Workshop: Devin Becker, Evan Williamson, and Olivia Wikle, “CollectionBuilder: A Static Web Approach to Digital Projects in Libraries”, ALA Core Classroom, 2020, https://osf.io/ku67f/
  • Article: Devin Becker, Evan Williamson, and Olivia Wikle, “CollectionBuilder-CONTENTdm: Developing a Static Web ‘Skin’ for CONTENTdm-based Digital Collections”, Code4Lib Journal 49, 2020, https://journal.code4lib.org/articles/15326
  • Article: Olivia Wikle, Evan Williamson, and Devin Becker, “What is Static Web and What’s it Doing in the Digital Humanities Classroom?”, dh+lib, Special Issue: Literacies in a Digital Humanities Context, 2020, https://dhandlib.org/2020/06/22/what-is-static-web-and-whats-it-doing-in-the-digital-humanities-classroom/
  • Presentation: Olivia Wikle, Andrea Green, and Erin Holmes, “Breaking Boundaries with CollectionBuilder: Iterative Digital Collection Software Development with Partners”, Digital Library Federation Forum, 2020, https://2020clirevents.aviaryplatform.com/collections/1172/collection_resources/31920
  • Presentation: Olivia Wikle, Evan Williamson, and Devin Becker, “CollectionBuilder: Developing an Agile Approach to Digital Collections”, Info2Go!, Idaho Commission for Libraries, 2020, https://youtu.be/PhXhY5G--p4
  • Workshop: Olivia Wikle, Evan Williamson, and Devin Becker, “CollectionBuilder: Using Static Web Technologies to Create Digital Collections and Teach DH Principles”, ADHO DH2020, 2020, https://collectionbuilder.github.io/dh2020/
  • Workshop: Evan Williamson, Olivia Wikle, and Devin Becker, “A Static Web Approach to Digital Collections: Hands-On with CollectionBuilder”, Code4Lib, 2020
  • Presentation: Olivia Wikle, Evan Williamson, and Devin Becker, “Metadata + APIs → Beauty: Building Engaging Digital Repository Skins With Static Web Tools”, Digital Library Federation Forum, 2019, https://osf.io/hteq3/
  • Workshop: Olivia Wikle, Evan Williamson, and Devin Becker, “Digital Collection Magic with Static Web Technologies: Improving CONTENTdm Front Ends using CollectionBuilder”, Learn@DLF, 2019
  • Presentation: Olivia Wikle and Evan Williamson, “CollectionBuilder: Creating & Teaching Digital Collections with Minimal Infrastructure”, ASIS&T Webinar Series, 2019, https://osf.io/pfhcy/
  • Presentation: Evan Williamson and Devin Becker, “GitHub-Pages CollectionBuilder: Teaching & Building Digital Library Collections using Minimal Computing Techniques”, DLF Forum, 2018, https://osf.io/d8e6b/

Who Runs This Ship?

Core team:

picture of Olivia Wikle
Olivia Wikle

Communications Director
Digital Initiatives Librarian, University of Idaho

picture of Evan Williamson
Evan Williamson

Technical Director
Digital Infrastructure Librarian, University of Idaho

picture of Devin Becker
Devin Becker

Project Director
Head, Data and Digital Services, University of Idaho

Collaborators:

  • Jylisa Doney, Social Sciences Librarian, University of Idaho
  • Marco Seiferle Valencia, Open Education Librarian, University of Idaho

Advisors:

  • Kim Christen, Washington State University
  • Alex Merrill, Washington State University
  • Alex Gil, Columbia University
  • Marii Nyrop, New York University
  • Laura Bucholtz, Reed College
  • Ammon Shepherd, University of Virginia

Former Graduate Assistants:

  • Chelsea Codling, MA Archaeology ‘20, University of Idaho
  • Michael Decker, MA English ‘21, University of Idaho

Partners