State of Dev, May 2025

Frontend

Tabs are available in the configuration when the site is installed as a Progressive Web App (PWA) (See also)

Duplicate search query parameters for objects associated with times before / after are removed.
Example: If one searches for “Objects after 1900, whose first recorded associated time is also after 2000”, this is a duplicate query. 2000 is always after 1900, so one of the two parameters can be removed.
Searches by time begin / end are also the foundation for the timeline. As the timeline is both beloved by web crawlers and resource-intensive to generate, this change significantly reduced server load.
Any links on timeline pages that do not reference single object pages are marked as rel=nofollow
Which is to say that bots are told to ignore them.

Tabs are available in the configuration when musdb is installed as a Progressive Web App (PWA) (See also)
New search option for objects: “Can be published”
Aggregate search for objects that have not yet been published and which comply with the minimum requirements for publication.
Separated measurements can now be batch-edited
Available via “assign results”
Institution-wide setting to enforce the use of the user-defined object editing interface for all users of the institution
Exhibitions can now be searched via the API (/exhibition/list)
A user’s user-agent is checked whenever a page is requested. If it changed, the user will be logged out automatically.
Protection against session hijacking.

Panorama images for tours through exhibitions / institutions are calculated down to 2400 px height rather than 1400 px height
The APIs for searching for entries in controlled vocabularies are now available via the main API
See e.g. /actor/search_linked_to_objects/{term} , /actor/search/{term} etc.

Fix: “Visiting scientists” couldn’t open the “location” tab (this erroneously required museum-wide editing permissions)
Fix: User-defined defaults for descriptions of new objects were ignored when new objects were to be added
Fix: Thumbnails were displayed as duplicate images linked to exhibitions (tag “images”)
Fix: Prefixing via the batch editing was broken

CSVXML Parser
- New literature-related fields (ISSN, editor, etc.) are now covered
- References to wikidata are now respected as tags are imported
The maximum length of any single given tag/keyword is centrally set to 95 characters

Some more recently added fields from the “admininstration” tag of musdb’s object pages had been read by the importer but their transfer into the database had not been implemented thus far.

Tabs are available in the configuration when nodac is installed as a Progressive Web App (PWA) (See also)