Between 6 a.m. and 9:15 a.m., museum-digital’s main server unfortunately experienced another outage. The immediate outage has been resolved now. The larger issue remained the same as so often during the rocky months last year: To bring back the server, we needed to: This was, to some extend, to be expected: PHP ran without issue …
December 2025 was an interesting month for museum-digital. An update to the PHP version used as well as a flood of requests by what is most likely AI scrapers forced us to make changes for improved stability, reducing and reformulating features rather than adding new ones and working on matters of systems administration over purely …
The recent issues with server instability have been solved. To do so, we had to significantly reduce resources available to the IIIF API. And in learning from the whole situation, a feed of the most recent relevant blog posts are now displayed to users directly in musdb.
Since the last post (i.e. the update to PHP 8.5 amid an onslaught of AI scrapers) and the later introduction of much stricter per-IP rate limiting, the stability issues around md are better – but they are not yet completely resolved. As such, we have expanded our efforts in rewriting and reformulating key resource-intensive functionalities …
Between Thursday last week (November 27th) and yesterday (December 6th), museum-digital has seen its most instable week in about four years. Now that the dust has settled a bit, there’s finally some time to discuss what happened and how we managed to tackle the multiple issues leading to the (very noticeable) instability.
Frontend musdb Importer Core Parser
A summary of recent updates and development around museum-digital in October 2025.
Recent (technical) development around museum-digital in September 2025.
A summary of the recent updates and (technical) development around museum-digital in August 2025.
Interoperability has been one of the focal issues around museum-digital practically since its inception. Offering different, simple ways to bring data into the system was a necessary requirement to even think of what we do. And offering simple ways to get the data out of the system again is just good practice – though all …
June and especially July were at first glance once again rather slow months in terms of development at museum-digital. Generally, the pace and type of development seems to have changed this year. Rather than doing many small improvements all over the place, there is less but larger and more labor intensive changes and new features. …
museum-digital can now be browsed in Hindi.
An overview about recent developments around museum-digital in May 2025.
museum-digital’s public portals can now be browsed in Telugu.
museum-digital’s public portals can now be used in Tamil.
Some minutes ago, our search server crashed. To bring everything back to normal, we will have to re-index, which will take a few hours. As that is being done, most of the frontend will remain operational without issue. musdb will, depending on the instance, be unavailable into the night.
Frontend musdb Importer
If you search for “run”, you want to find entries (objects, blog posts, etc.), that mention “ran”. If you search for inventory numbers like “*1”, you want to find “0001”. These are fundamentally different categories of search. In the first case, you want to have a language-aware full-text search. In the latter case, you simply …
In terms of development happening around museum-digital, February 2025 was a rather calm month. While more happened in the “machine room”, immediately visible changes are mostly restricted to bugfixes. And a whole new tool.
There’s lots of talk about the FAIR principles – publishing findable and accessible data. Logically, to be findable and accessible, the data should at the very least be described in the language of users, even if it is not itself translated. And that means, that before object information becomes multilingual, plattforms should become (more) multilinugal …
