Refine by Date


Refine by Format


Refine by Collection


Our Technologies and Tools

MarkLogic Server

MarkLogic logo

MarkLogic Server is our digital library application platform. It is a native XML database that can handle a variety of data formats and metadata schemas. MarkLogic Server is a next-generation, NoSQL database that moves beyond the limitations of relational databases. We create all our digital library applications in-house using the XQuery programming language, along with XSLT, HTML5, CSS and JavaScript.

Image server

Our digital images are stored on a Windows network server. We use TIFF and JPEG 2000 file types for our archival images, and we derive JPEG images for general use. Image creation is done by the Internet Archive scanning center located in the Library or through other outsourcing. Our staff does limited image work, such as quality assurance, rotation and resizing as needed.

Amazon S3

Amazon Web Services logo

We maintain highly redundant offsite backup of our digital images using Amazon S3. This is an example of using cloud computing for the storage and preservation of our valuable digital resources.


Trello logo

The Digital Collections team is committed to agile project management. To facilitate this approach, we use Trello, a web-based tool that helps us track our daily tasks, plan future work and manage the numerous details that are part of any complex software development project.


Confluence logo

As a team, we maintain and share our Digital Collections documentation, policies, and procedures using Confluence, a web-based collaboration system that provides a wiki and other collaboration tools. While much of our day-to-day information is tracked in AgileZen (see above), Confluence allows us to capture detailed workflows and important policy decisions that might otherwise get lost in the shuffle as we move from one digital project to the next.

Assembla (Subversion)

Assembla logo

We track changes made to our programming code and metadata using Assembla, a web-based user interface that streamlines our use of version control. Assembla provides a central repository based on the open-source Subversion system, allowing us to track every revision in every file in our source code and metadata documents.

oXygen XML Editor

oXygen logo

Much of our metadata and programming work is done using oXygen, an XML editor. For our metadata work, we edit the XML documents directly, so members of the team working on metadata are trained to be proficient with the XML markup language. We also use oXygen for writing programming code, since it provides an integrated development environment for XML-related programming languages such as XQuery and XSLT.

Prince (XML to PDF)

Prince logo

We use the Prince software program to dynamically generate PDFs for our digital resources. When a user clicks on the PDF icon in our toolbar, HTML is generated on the fly and is used by Prince to transform the digital images and deliver a PDF for a printable version of the resource.

Selenium WebDriver

Selenium logo

Selenium WebDriver is a tool for automatically carrying out a series of actions in a web browser. We use it to perform automated testing on our web applications. With WebDriver, we create and run scripts that control or “drive” a web browser, performing the mouse clicks and other interactions that a user would make during typical use of our web applications.


CrossRef logo

CrossRef is an official Digital Object Identifier (DOI) registration agency that we use to register and maintain our DOIs and their accompanying metadata. CrossRef provides a way for scholars to click a citation and get the full digital article. By assigning DOIs we create unique identifiers which act as persistent links to the Seminary’s online journal articles. While the location or metadata may change for the digital resource, DOIs remain unchanged, which is important for scholarly research in a fluid digital environment.

Metadata Standards

We employ a variety of metadata standards, including METS, MODS, MARCXML, Dublin Core, MIX, EAD, and TEI. For each project, we select the appropriate standard based on the nature of the material and the needs of the project.