Use case · Software, integration, operations
Anonymised, like all our use cases
An archive anyone can use.
For the documentation centre of a foundation in Berlin, we developed a research portal for its library and eyewitness archive. It runs on the web and on terminals on site, pulls objects straight from the museum database and is built for accessibility: with Easy Read, sign language, audio and a contrast mode.
Deployed in
Museum and documentation
Services
Software, integration, operations
Channels
Web and on-site terminals
Languages
German, English, Easy Read
Project start
2021
Research without barriers.
Interviews, books, documents and maps are all in one place. Search and filters lead quickly to the right result, and font size and contrast can be adjusted with a single click.
Six ways into the collection.
Each area has its own search. The team maintains the content itself; objects come from the museum database.
Integration
Discover
Themed insights into the collection, with objects and images straight from the museum database.
Software
Oral history
Eyewitness interviews with full-text search, filters by institution and language, and sorting by length.
Software
Library
Access to the catalogue, reading recommendations and specialist databases.
Software
Archival records
Reports and documents, prepared for research.
Software
Family history
Pointers to further databases for researching your own family history.
Software
Historical maps
Local maps and site plans to explore.
6
Areas for research, each with its own search
2
Channels: on the web and on terminals on site
4
Ways in: text, Easy Read, sign language and audio
2021
Project start, continuously developed ever since
What makes the difference.
Accessible from day one
Font size, contrast mode, Easy Read, sign language and audio are part of the portal, not tucked away in an extra menu.
Straight from the museum database
Objects and images come live from MuseumPlus. Images are scaled and cached automatically.
Kiosk mode on site
The terminals in the building run the same portal, with printing, a PDF viewer and an idle screen.
Custom CMS
The team maintains content in a lean CMS. The portal fetches it via an API.
What we built it with
- PHP
- Laravel
- Blade
- Sass
- Swiper
- MuseumPlus API
- Custom CMS
- REST API
- Image cache
- GitLab CI
Where should your content become more accessible?
In an intro call we look at how your collection, archive or knowledge can be made usable for everyone.