A blog on museum-digital and the broader digitization of museum work.

Joshua Ramon Enslin

Joshua Ramon Enslin is a student of Southeast Asian Studies at Goethe University Frankfurt. His main research interests concern contemporary labor migration, digitization, and the history of ideas in Indonesia and the Philippines. He has previously worked in translations from Indonesian to German and software development. At museum-digital he is mainly responsible for the further technical development of the frontend, musdb, and md:term. He has also contributed to the development of the "Themator", and contributed to the English and Indonesian translations of museum-digital.
Screenshot der OpenAPI-Beschreibung der API von musdb in Swagger UI

Managing object information using the musdb API

The public API of the frontend of museum-digital has long been in use – for example for embedding objects directly from museum-digital in a given museum’s website. The API is stable and well-established. In musdb, our inventorization and museum management tool, however, the situation is more complicated. On the one hand, musdb is simply much

Development musdb

files.museum-digital.org: Archive for Documents About museum-digital

Over the years, many presentations have been held about museum-digital. Articles have been written, and so have tutorials and other documents. To not let them fade into obscurity on the hard drives of their authors, we have now set up a document archive for such files: files.museum-digital.org. For the start we have compiled primarily presentations

Development General Präsentationen

IIIF and museum-digital

Many have seen it and the feedback has been consistently positive thus far: For many objects, museum-digital can now offer a revamped image viewer with improved features, such as a much better zoom function. This is made possible by the image viewer Mirador and our IIIF API. The fact that museum-digital offers an IIIF API

Development Frontend

“Smarter” Entry of Links to Vocabularies in musdb

Many imports of data confront us with Places like “Berlin ?” and times like “ca. 1328” konfrontiert. The import tool of museum-digital has been able to handle such entries for quite a time: “Berlin ?” is recognized to mean that the place is actually “Berlin”, but that the entry is not made with complete certainty.

Development musdb Terminology Translations

OpenSearch: Search museum-digital directly from the browser’s search bar

OpenSearch is an open web standard for describing search functions of web services. If a website supports it, the browser will take note and offer the user to install the website as a search machine. One especially nice aspect of it is, that OpenSearch can be implemented in just a few lines of code. It

Development Frontend General musdb

Using Textblocks in musdb

museum-digital has a lot of “hidden” features; hidden on purpose to not blur the users’ focus. One of these is the text blocks features in musdb, our inventorization and data input tool. Thus far, the text blocks had only been described in a presentation from mid-2018 (in German) – hence this blog post.

Development musdb
„Erwachendes Mädchen“ von Eva Gonzalès, Kunsthalle Bremen – Der Kunstverein in Bremen (CC BY-NC-SA)

Türkçe

The frontend of museum-digital is now available in Turkish. As a very nice side effect, this also unlocks the Turkish translations for keywords, and place and actor names we have been gathering for the last half a year. Image credits: Eva Gonzalès: „Girl Awakening“, Kunsthalle Bremen – Der Kunstverein in Bremen (CC BY-NC-SA)

Frontend General Translations