Development Infrastructure and Applications (DIAG) is the team within Digital Libraries and Scholarly Technologies charged with creating and integrating the software systems with which the library and its partners preserve, describe, publish, and manage digital collections.

Sustainable custodianship of these systems is DIAG's defining responsibility: We work closely with Libraries Technology Services to avoid the compounding security risks and corrective costs of lapsed maintenance. The team also shares responsibility for content management and back-office applications with other groups in Technology & Preservation, for faculty research consultation with Digital Scholarship, and for outreach and training with units across the libraries.

This list of Principle Languages, Platforms, and Tools offers a view into what the staff in DLST, particularly in DIAG, use in our work. 

Team Portfolios

Each DIAG team member acts as a technology lead on one or more of the following:

• Libraries' Collections Online
  • General catalog and specialized discovery platform (DLC)
  • Online Exhibitions
  • Online Archival Discovery (Finding Aids)
• Columbia Scholarly Output
  • Institutional Repository (Academic Commons)
  • Electronic Journals (OJS)
  • Original Research (Faculty collaborations and sites)
• Identification, Description and Publication of digital collections
  • Ingest, description. publication of CUL digital collections (Hyacinth)
  • Digital Object Deposit Infrastructure (Ingest APIs and Processes; Archivematica)
  • Reusable web publication of digital assets (IIIF and streaming media)
  • Citation infrastructure (DataCite and CrossRef DOIs)
  • Minimal publication tools for digital collections (Static sites/Wax)

Team Principles

As a team, we strive to organize our work around these guiding principles:

1. We anticipate changes to the projects, environments, and data with which we work, and pursue the currency of skill necessary to accommodate those changes strategically.
2. We build trust, capacity, and flexibility by cross-training team members in shared application support and committing to tested and documented code.
3. We maximize the results of our efforts when our expertise and solutions are reusable across projects and shareable with partners internal and external to the Libraries.
4. We support our colleagues in the library best by automating unnecessary rote interventions and building tools to support library staff in the unmediated maintenance of their collections' data.