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 inventorization data, but knew musdb well, began to ask additional inventorization functionalities. And thus the approach of musdb changes: instead of being an input interface to a publication platform, it turned into an inventorization 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.'; $tlSoftware['frontend_portal'] = 'Frontend / Portals'; $tlSoftware['musdb'] = 'musdb'; $tlSoftware['themator'] = 'Themator'; $tlSoftware['term_nodac'] = 'md:term & nodac'; $tlSoftware['resources'] = 'Resources'; $tlSoftware['in_blog'] = 'Tech-Related News in our Blog'; $tlSoftware['third_party_tools'] = 'Third party tools';