Logo of museum-digital

museum-digital

Software
BannerCourtesy NASA/JPL-Caltech.

Software

At museum-digital, we have developed a set of software solutions to facilitate an easy and inclusive process of digitization in museums. Originally, museum-digital was founded to publish object information online. We thus began by developing a public interface for viewing object information.

Since the original method of data input - the museums entered their data into their local database, sent it to the programmers, the programmers entered it to museum-digital - did not scale well, we then developed a simple online input interface, musdb. Some museums, that did not yet have a dedicated database for inventorized data, but knew musdb well, began to ask additional inventory functionalities. And thus the approach of musdb changed: instead of being an input interface to a publication platform, it turned into an inventory tool with the option to publish.

Soon after, requests for options to more thoroughly present digital narratives and stories became more frequent. While museum objects may be interesting by themselves, it is also a central task of museums to contextualize them. As a reaction to these requests, we created the Themator as an independent tool for writing and publishing stories online.

Early on, when developing the main frontend and musdb, we decided to use controlled vocabularies for all databases of a given language. Internally, we use our "norm data control tool" nodac for curating these. Since the vocabularies have grown considerably since, and have become a useful resource on their own by now, we have also developed a searchable frontend for these, md:term.


Logo Frontend/Portals Logo musdb Logo md:term Logo nodac Logo Themator

Tech-Related News in our Blog
Automatically enforcing consistent naming of places Importing actors Quality Assessments Like in musdb: Now For Everybody EODEM Version 1.0 released API documentation for frontend and md:term