Trust and procurement
The evidence an institutional review needs.
Institutional evaluation runs on documents, not demos. This section holds what your IT reviewers, procurement office, and grant funders will read, in the plain, verifiable terms they expect.
Last reviewed July 2026
- Deployment
- Cloud / Private
- Authentication
- SAML SSO · MFA
- Exports
- Standards-based, every stage
- Certifications
- None held yet
Four pillars
What a committee tests, in four parts.
The platform has to satisfy more than a demonstration. It has to hold up through migration planning, technical review, rights review, staff turnover, and the day your institution chooses to leave.
Standards in and out
Import records from CSV, EAD, MARC or MODS, and harvested OAI-PMH. Export Dublin Core, EAD 2002 or EAD3, MODS, METS with PREMIS, BagIt, and EAC-CPF. Serve and harvest OAI-PMH, and view media through IIIF.
IMPORT AND EXPORT · OAI-PMH · IIIF
Integrity you can inspect
Archively calculates SHA-256 checksums at upload, re-verifies fixity on a schedule, and alerts on change. It keeps published-version history and preserves an immutable record of every AI proposal.
SHA-256 · RECURRING FIXITY · VERSION HISTORY
Governed access
Seven archival roles plus an administrator, nine workflow stages, per-section permissions, and field-level audit trails. Staff sign in with SAML SSO and MFA. Every change is attributed to a person.
ROLES · WORKFLOW · AUDIT · SAML SSO · MFA
A real exit
Records stay exportable at every stage in standard formats. Portability is part of the architecture, not a concession you negotiate at renewal.
EXPORTABLE AT EVERY STAGE
The diligence file
Read the full file.
Each page below is written to be printed and forwarded. Start anywhere.
Bring the requirements your technical committee will test.
A working setup using your records, not a sales presentation.