Resources
Everything else you might need
The brand files, where the documentation lives, the standards MediaINFO Digital Library speaks, and a straight account of where it runs and how it treats your data.
Documentation
Written for the people who run it
Administration, deployment, upgrading, security and the full behaviour of every capability — the same documentation our own engineers work from. It is for our clients and distributors, behind the partner portal's sign-in.
Downloads
The logo pack
The MediaINFO mark for use in partner material, conference programmes and institutional pages. Vector where you can, raster where you must; keep the proportions and leave clear space around it.
Standards
An archive that can be read by other systems.
Nothing here is a proprietary container. What goes in comes out, in the formats the sector already agreed on.
OAI-PMH
Harvesting endpoint for aggregators, one record per item. Administrators choose which collections are exposed and which browse facets become sets; a fresh installation exposes nothing until someone ticks a box.
Dublin Core
The default metadata mapping for harvest responses, configured per content type so your own field names translate into the standard.
Europeana Data Model
A second harvest mapping alongside Dublin Core, for participation in European aggregation networks.
Schema.org
Structured data embedded in public pages, built from the same mappings, so catalogues and search engines read your records correctly.
IIIF Image API
High-resolution images served from a built-in endpoint, so deep zoom works without pre-tiled derivatives and any compliant viewer or aggregator can render your images.
METS/ALTO
OCR interchange on import, alongside ALTO and other page-analysis formats, so text produced elsewhere comes in with its coordinates intact.
BagIt
A packaging format for bringing multiple related files in as one item; the platform supports a specific BagIt variant on import.
JPEG 2000
Lossless JP2 for preservation-grade deployments, with original source files optionally retained alongside derivatives.
HTTP APIs
Library, search, assets, processing, access and system APIs cover the whole platform, from programmatic submission and regular ingest from external systems to administration; an interactive reference comes with the licence.
Security, deployment and data
Your infrastructure, your rules
The one page to send to the colleague who asks where the data goes. Seven short answers, each of them a property of the platform as it ships.
- Where it runs
MediaINFO Digital Library is designed to run entirely on infrastructure you control: your material, your metadata and your users stay inside your perimeter.
An installation can be run with no outbound connection at all; the resident agent then never contacts the vendor, and releases arrive as signed offline bundles.
Analysis can be confined to a network segment with no route out, which your own network monitoring can verify.
- What leaves the network
Configured for on-premise processing, analysis happens on your own hardware and no media, metadata or result leaves your network; no external call is made.
Configured to use a hosted service, only the media a given operation needs is sent — never credentials, configuration or unrelated data — and the results come back to be stored as metadata on your own systems.
Each capability is set independently, so the two can coexist in one installation; for collections under data-residency obligations, every capability — face recognition included — can be pinned to on-premise processing.
- Identity and access
Identity is delegated to an identity broker, so no password is held by the platform itself; password login, directory passthrough, single sign-on and multi-factor authentication are all configured there.
Every part of the admin interface and the API is gated by granular permissions, granted only through roles — never directly to a person — so a permissions audit is a short job.
Anonymous visitors see exactly what an explicit Public role grants them, and nothing else; a collection's own access list can restrict it further, and that restriction is final.
- Audit
Every state-changing action in the admin interface and the API is written to an audit log with the acting identity, the time, the object and the change.
Those logs cover content edits, role and permission changes, analysis workflow runs and bulk-import outcomes; usage and job history are visible in the admin panel, so an institution can see what was processed, and how much.
- Updates and rollback
Updates are offered, never applied unattended: a release is applied when an administrator asks for it, health-checked, and reverted automatically if it does not prove itself.
Releases are verified against their digests before anything is loaded — fetched from the vendor, or from a signed offline bundle carried in.
A rollback restores the containers and the configuration, not your data: the database, the repository storage and the search index are never reverted by an upgrade, so take your own backup first.
- Personal data
Personal data — user profiles, recognised-face records, recorded activity — is stored locally and can be exported, deleted or pseudonymised with the standard admin tools.
The recognition data for the people in your own archive is scoped to your installation and is never matched against, or visible from, anyone else's; only public figures are shared.
Public-people packs are available in certain countries and regions and provide automatic name labelling, with aliases, of thousands of public figures.
- Storage
Storage on a local filesystem, on object storage, on a network share or over FTP and SFTP, with more than one backend active at once and each assigned its own use.
The repository can be placed on a share at install time, moved later with a dry run and a verified copy — nothing is deleted from the old location — or extended with a second storage location.
For preservation-grade holdings, a lossless archival encoding keeps a bit-perfect reproduction of every page.
Ask us the rest in a demonstration.
A guided demonstration of MediaINFO Digital Library on our demo server, with a few items from your collection if you wish.