Samples below represent a range of deliverables created for past projects to demonstrate ideation, documentation, and completion on a variety of platforms. For additional examples or to get in contact regarding opportunities contact me.

Sample data model for Archival Repository

Sample data model for Archival Repository

Data Modeling

The Ingalls Library and Archives required a system for long term preservation of important digital assets. As part of the process data models had to be developed to capture important information for archival and discovery. My role involved translating an Excel spreadsheet into an organized series of metadata fields built into the Samvera framework.

To do so I first identified and grouped existing properties as well as additional information which could be imported from external sources. Next came research into appropriate mappings from existing linked data standards such as the Getty Art and Architecture Thesaurus. Certain fields were identified with controlled values to help data normalization while others were free form.

The resulting data models were used to deploy effective metadata models for ingest, discovery, and preservation within Samvera. These also served as documentation for librarians, archivists, and support staff who had to manage and migrate the contents from one version of Fedora to the next.

Download PDF

Site Maps

Site map example for nonprofit organization

The Cleveland Touring Club was making a migration from a static HTML based site to a new platform. The legacy site contained a series of ad hoc layouts based on immediate requirements with no long term strategy.

As web administrator I organized existing content into logical groups. Certain sections were eliminated while others were added based on new functionality of the content management system. The resulting structure focused on the main requirements for the web site as indicated by club members - locating upcoming events, downloading a schedule of rides, and joining or renewing club membership.

The new design was rolled out over the course of a month with positive feedback from many members. Additional adjustments were made based on analytics to further fine tune the site so that it focused on social events and publication of leadership decisions. As of 2018 the site is still live.


The Avalon Media System is an open source framework developed by Northwestern University and Indiana University to assist in the archival and delivery of multimedia content. The Hydra framework drives the default interface and is based on Twitter Bootstrap with minimal customization.

As a developer I created a series of wireframes to document the ingest process from file upload to metadata attachment to organization and security of video segments. The initial designs were translated from pen and paper sketches and translated into interactive prototypes. These were then shared with stakeholders to refine the workflow with an emphasis on structure rather than visual design.

In a future sprint these wireframes were used to help implement a front end interface for manual ingest. Import from external systems, such as the library catalog, was also implemented as part of one development cycle. The documentation was then archived with other design documentation.

Download as PDF


Within the Avalon Media System different roles are supported such as archivist, instructor, or student. These wireframes were created to help document the experience from the perspectives of different user types.

The wireframes began by studying user stories to identify key features of emphasis for each user role. For instance professors should easily be able to locate and share a video. Students should be able to watch content in a variety of devices but be limited to only access media within a specific time window.

These user requirements were transformed into a series of sketches to refine important elements like wayfinding, discovery, and discussion threads. Once the layout had been converted to a digital format annotations were added to explain how a user, such as an archivist, would experience the interface.

The documentation was shared with stakeholders and other developers to help fine tune the initial interface. Further features have been added over time to slowly enrich the user interface.

Download as PDF