Approval in nodac

backend/ar/action.json

@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way.",
+        "search_by_tag_inclusive": "Search objects linked to this tag or any of its subordinate tags.",
+        "search_by_tag_exclusive": "Search objects linked to exactly this tag (not those linked to any of its subordinate tags).",
+        "search_by_place_inclusive": "Search objects linked to this place or any of its subordinate places.",
+        "search_by_place_exclusive": "Search objects linked to exactly this place (not those linked to any of its subordinate places).",
+        "export_selection_directly": "Export selected entries directly",
+        "export_selection_directly_explica": "Exports the selected entities as they are displayed in the list. This export option will not contain any information that is not available in the overview. To trigger such an export, use the respective export functionalities (where available) or the API.",
+        "theming_explica": "musdb supports theming to a certain level. On the one hand, special layout adjustments can be loaded. On the other hand, alternative color schemes can be selected. Selecting multiple alternative layout components combines them."
     }
 }

backend/ar/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "No entity has been linked",
         "repeat": "Repeat",
         "repeat_explica": "Repeat the last content you entered in this same data field.",
-        "setup_missing": "Not set up yet"
+        "setup_missing": "Not set up yet",
+        "currently_configured": "Currently configured",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a programm. They thus allow programmers to build external applications on top of them.",
+        "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
+        "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday",
+        "no_title_selected": "No title selected",
+        "sensor_data": "Sensor data",
+        "translations": "Translations",
+        "places": "Places",
+        "actors": "Actors",
+        "times": "Times",
+        "sources": "Sources",
+        "edit_in_nodac": "Edit in nodac",
+        "title": "Title",
+        "vocabularies": "Vocabularies",
+        "ignore": "Ignore",
+        "url": "URL",
+        "is_capitalized": "Is",
+        "relevance": "Relevance",
+        "abort": "Abort",
+        "ids": "IDs",
+        "address": "Address",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/ar/data_history.json

@@ -99,6 +99,7 @@
         "querying_data_history": "Querying data history",
         "phone_number": "Phone number",
         "regular_space": "Regular location",
-        "acquisition": "Acquisition"
+        "acquisition": "Acquisition",
+        "webdav_gen_access_data": "Generate WebDAV access data"
     }
 }

backend/ar/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Type of document",
         "document_type_explica": "In what relation does the document stand towards the object?",
         "generate_inventory_number_explica": "Automatically generates the next inventory number based on your institution's inventory number scheme.",
-        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings."
+        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings.",
+        "pdf_publicinfo_explica": "A PDF displaying published or publishable data for the object in a presentable A4 template.",
+        "pdf_knorr_explica": "A PDF template following the Knorr format, still popular in parts of Germany.",
+        "pdf_a5simple_explica": "Default multilingual A5 PDF template.",
+        "pdf_fullobject_explica": "A multilingual PDF template that covers all recorded data on the object in a simple two-column layout.",
+        "pdf_kartya2_explica": "A5 PDF template prepared for Hungarian museums.",
+        "pdf_kartya3_explica": "A5 PDF template prepared for Hungarian museums.",
+        "object_object_links": "Object to object links",
+        "limit_search_to_selection_explica": "Further restricts the search query to return only the selected objects. The selection will thus be available for further processing via batch processing, analysis, and exports."
     },
     "ortart": [
         "",

backend/ar/object_basis.json

@@ -44,6 +44,7 @@
         "series_is_public": "Published series",
         "series_is_not_public": "Unpublished series",
         "series_is_public_explica": "If both the series and the object have been toggled public, the object will be publicly listed as part of the series.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventory number (padded numbers)"
     }
 }

backend/ar/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regular sending of reports",
         "edit_custom_reports": "Edit custom reports",
         "custom_reports_intro": "Using \"Custom report\" templates institutions can define their own exports in the form of CSV tables or HTML text documents.",
-        "hide_fields": "Hide data fields"
+        "hide_fields": "Hide data fields",
+        "add_new_custom_report_template": "Add new custom report template",
+        "custom_reports_see_lists_placeholders": "Click on a button to view the list of available placeholders",
+        "placeholders": "Placeholders",
+        "custom_report_target": "Target page",
+        "custom_report_target_explica": "The custom report will be available for the selected target page type. Placeholders may or may not be available for a given type of target page.",
+        "share_folder_share_link": "Via share link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Some functionalities of museum-digital's portals can be influenced by the institutions responsible for the respective content. Here the corresponding settings can be managed.",
+        "integrations_explica": "Some integration capabilities linking musdb with other programs are built-in with musdb. To actually use those integrations, musdb needs to be given access to the relevant other services on the levels of institutions and users. Note that these settings pertain to built-in integrations. Further integrations can be written using musdb's API.",
+        "webhooks_explica": "Webhooks are a simple mechanism for an application to let other applications respond to a given action in the source one. When a given action is executed, musdb's server will perform an HTTP query to a pre-defined URL in the background. Some context information on the performed action is provided in the POST-header (user data, the processed API call, and an optional secret to lock down the target script against unwarranted access). If you e.g. write a script that receives such an HTTP call upon the publication of objects, you can e.g. trigger the automatic posting of a the newly posted object record on your social media feed.",
+        "object_input_page_explica": "Here the object input page can configured. Additional fields can be made available and potentially set to be required fields for newly added objects.",
+        "alt_no_schemas_explica": "Alternative numbers for objects can be recorded on the object page's base tab. The category for such numbers are not a controlled list. But, depending on the type of alternative number, it might be fruitful to provide additional context information on this type of number. If a number schema set here has the exact same category name as has been entered for an object, the explanation will be provided in a tooltip when hovering over the alternative number on published object pages. Additionally, HTML5 validation patterns can be selected to ensure a consistent form for the recording of the given category of alternative object numbers."
     }
 }

backend/ar/sources.json

@@ -8,7 +8,7 @@
         "book": "Book",
         "phdthesis": "PhD thesis",
         "electronical": "Electronical",
-        "misc": "Miscelaneous",
+        "misc": "Miscellaneous",
         "author_creator": "Author \/ creator",
         "author_creator_explica": "The creator of the source. Type a name to select the author or creator. You can add multiple authors \/ creators for a work.",
         "title": "Title",

backend/ar/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Failed to locate any sensor data for this space",
         "get_url_for_logging": "Get URL for logging",
         "object_addendum_space_explica": "Select a space from the list. To add a new space press the \"+\" button. To see a log of the objects previous whereabouts right click on the selection field..",
-        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?"
+        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?",
+        "sensor_data": "Sensor data"
     }
 }

backend/ar/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Edged",
+        "layout_edged_explica": "Removes the rounded corners of visual elements that usually strongly feature them.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone is a color scheme designed to follow colors used in traditional Thai art. It was compiled by Pairoj Pittayamatee, and is the result of a ten year study about traditional color making and usage in Thai art history for his master's and doctoral degrees at Silpakorn University. (Wikipedia)",
+        "application_localstorage": "The selection of theme components is stored in the browser's local storage. As such, it will need to be re-applied if the browser cache is emptied.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized is a low-contrast color scheme optimized for readability and syntax-highlighting.",
+        "layout_main_aside_separated": "Separated sidebars",
+        "layout_main_aside_separated_explica": "Adds a more pronounced background color to the page and highlights sidebars and main page contents in separated boxes.",
+        "layout_submit_buttons_fullwidth": "Full width submit buttons ",
+        "layout_submit_buttons_fullwidth_explica": "Increases the width of submit buttons to the full width of the containing element.",
+        "layout_textareas_minimum_height": "Minimum height for text areas",
+        "layout_textareas_minimum_height_explica": "Sets a minimum height to textareas that automatically resize otherwise.",
+        "textareas_minimum_height": "Minimum height for text areas",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the red\/violet series, the red series and the achromatic series listed there.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the blueviolet series and the achromatic series listed there.",
+        "layout_icons_high_contrast": "High contrast icons",
+        "layout_icons_high_contrast_explica": "Removes the opacity setting from icons, so that they will be displayed in solid black \/ white colors.",
+        "layout_icons_large": "Increase icon size",
+        "layout_icons_large_explica": "Increases the icon size significantly. They are thus easier to see and click, but - importantly - are misaligned respective to the text. Use with caution."
+    }
+}

backend/ar/user.json

@@ -180,6 +180,9 @@
         "instance_level_contact_explica": "Enabling this toggle will automatically activate your user profile and make your profile listed as an instance-wide contact person in the navigation.",
         "invite_date": "Invite date",
         "publish_user_profile": "Publish user profile",
-        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region)."
+        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region).",
+        "account_disabled": "Account disabled",
+        "generate_auth_token": "Generate auth token",
+        "invalidate_auth_token": "Invalidate & remove auth token"
     }
 }

backend/ar/z_migration.json

@@ -0,0 +1,10 @@
+{
+    "z_migration": {
+        "pre_release_title": "Pre-release of musdb's upcoming UI rewrite",
+        "try_out_new_ui": "Try out the new UI",
+        "pre_release_intro": "For the last months we have been working on a complete rewrite of the musdb's user interface. While much remains essentially the same, the new UI aims to be much more streamlined and is based on an entirely different, more efficient architecture.",
+        "pre_release_intro2": "Some blog posts have already given previews to it. Now, we can release the new UI in a pre-alpha state: Quite some features are still missing from the old UI, but most regular workflows should already be supported in the new UI. Read more details about the current pre-release or try it out below. As usual, but especially now, any feedback is welcome!",
+        "read_blog_post": "Read blog post",
+        "pre_release_blog_post_link": "https:\/\/blog.museum-digital.org\/2026\/09\/30\/pre-release-of-musdbs-new-ui\/"
+    }
+}

backend/cs/action.json

@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way.",
+        "search_by_tag_inclusive": "Search objects linked to this tag or any of its subordinate tags.",
+        "search_by_tag_exclusive": "Search objects linked to exactly this tag (not those linked to any of its subordinate tags).",
+        "search_by_place_inclusive": "Search objects linked to this place or any of its subordinate places.",
+        "search_by_place_exclusive": "Search objects linked to exactly this place (not those linked to any of its subordinate places).",
+        "export_selection_directly": "Export selected entries directly",
+        "export_selection_directly_explica": "Exports the selected entities as they are displayed in the list. This export option will not contain any information that is not available in the overview. To trigger such an export, use the respective export functionalities (where available) or the API.",
+        "theming_explica": "musdb supports theming to a certain level. On the one hand, special layout adjustments can be loaded. On the other hand, alternative color schemes can be selected. Selecting multiple alternative layout components combines them."
     }
 }

backend/cs/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "No entity has been linked",
         "repeat": "Repeat",
         "repeat_explica": "Repeat the last content you entered in this same data field.",
-        "setup_missing": "Not set up yet"
+        "setup_missing": "Not set up yet",
+        "currently_configured": "Currently configured",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a programm. They thus allow programmers to build external applications on top of them.",
+        "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
+        "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday",
+        "no_title_selected": "No title selected",
+        "sensor_data": "Sensor data",
+        "translations": "Translations",
+        "places": "Places",
+        "actors": "Actors",
+        "times": "Times",
+        "sources": "Sources",
+        "edit_in_nodac": "Edit in nodac",
+        "title": "Title",
+        "vocabularies": "Vocabularies",
+        "ignore": "Ignore",
+        "url": "URL",
+        "is_capitalized": "Is",
+        "relevance": "Relevance",
+        "abort": "Abort",
+        "ids": "IDs",
+        "address": "Address",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/cs/data_history.json

@@ -99,6 +99,7 @@
         "querying_data_history": "Querying data history",
         "phone_number": "Phone number",
         "regular_space": "Regular location",
-        "acquisition": "Acquisition"
+        "acquisition": "Acquisition",
+        "webdav_gen_access_data": "Generate WebDAV access data"
     }
 }

backend/cs/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Type of document",
         "document_type_explica": "In what relation does the document stand towards the object?",
         "generate_inventory_number_explica": "Automatically generates the next inventory number based on your institution's inventory number scheme.",
-        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings."
+        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings.",
+        "pdf_publicinfo_explica": "A PDF displaying published or publishable data for the object in a presentable A4 template.",
+        "pdf_knorr_explica": "A PDF template following the Knorr format, still popular in parts of Germany.",
+        "pdf_a5simple_explica": "Default multilingual A5 PDF template.",
+        "pdf_fullobject_explica": "A multilingual PDF template that covers all recorded data on the object in a simple two-column layout.",
+        "pdf_kartya2_explica": "A5 PDF template prepared for Hungarian museums.",
+        "pdf_kartya3_explica": "A5 PDF template prepared for Hungarian museums.",
+        "object_object_links": "Object to object links",
+        "limit_search_to_selection_explica": "Further restricts the search query to return only the selected objects. The selection will thus be available for further processing via batch processing, analysis, and exports."
     },
     "ortart": [
         "",

backend/cs/object_basis.json

@@ -44,6 +44,7 @@
         "series_is_public": "Published series",
         "series_is_not_public": "Unpublished series",
         "series_is_public_explica": "If both the series and the object have been toggled public, the object will be publicly listed as part of the series.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventory number (padded numbers)"
     }
 }

backend/cs/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regular sending of reports",
         "edit_custom_reports": "Edit custom reports",
         "custom_reports_intro": "Using \"Custom report\" templates institutions can define their own exports in the form of CSV tables or HTML text documents.",
-        "hide_fields": "Hide data fields"
+        "hide_fields": "Hide data fields",
+        "add_new_custom_report_template": "Add new custom report template",
+        "custom_reports_see_lists_placeholders": "Click on a button to view the list of available placeholders",
+        "placeholders": "Placeholders",
+        "custom_report_target": "Target page",
+        "custom_report_target_explica": "The custom report will be available for the selected target page type. Placeholders may or may not be available for a given type of target page.",
+        "share_folder_share_link": "Via share link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Some functionalities of museum-digital's portals can be influenced by the institutions responsible for the respective content. Here the corresponding settings can be managed.",
+        "integrations_explica": "Some integration capabilities linking musdb with other programs are built-in with musdb. To actually use those integrations, musdb needs to be given access to the relevant other services on the levels of institutions and users. Note that these settings pertain to built-in integrations. Further integrations can be written using musdb's API.",
+        "webhooks_explica": "Webhooks are a simple mechanism for an application to let other applications respond to a given action in the source one. When a given action is executed, musdb's server will perform an HTTP query to a pre-defined URL in the background. Some context information on the performed action is provided in the POST-header (user data, the processed API call, and an optional secret to lock down the target script against unwarranted access). If you e.g. write a script that receives such an HTTP call upon the publication of objects, you can e.g. trigger the automatic posting of a the newly posted object record on your social media feed.",
+        "object_input_page_explica": "Here the object input page can configured. Additional fields can be made available and potentially set to be required fields for newly added objects.",
+        "alt_no_schemas_explica": "Alternative numbers for objects can be recorded on the object page's base tab. The category for such numbers are not a controlled list. But, depending on the type of alternative number, it might be fruitful to provide additional context information on this type of number. If a number schema set here has the exact same category name as has been entered for an object, the explanation will be provided in a tooltip when hovering over the alternative number on published object pages. Additionally, HTML5 validation patterns can be selected to ensure a consistent form for the recording of the given category of alternative object numbers."
     }
 }

backend/cs/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Nepoda\u0159ilo se naj\u00edt \u017e\u00e1dn\u00e1 data ze senzor\u016f pro tento prostor",
         "get_url_for_logging": "Z\u00edskat URL pro protokolov\u00e1n\u00ed",
         "object_addendum_space_explica": "Vyberte prostor ze seznamu. Chcete-li p\u0159idat nov\u00fd prostor, stiskn\u011bte tla\u010d\u00edtko \u201e \u201c. Chcete-li zobrazit z\u00e1znam o p\u0159edchoz\u00edm pobytu objekt\u016f, klikn\u011bte prav\u00fdm tla\u010d\u00edtkem my\u0161i na pole v\u00fdb\u011bru.",
-        "set_current_space_as_subordinate": "Nastavit aktu\u00e1ln\u00ed prostor jako pod\u0159\u00edzen\u00fd vybran\u00e9mu?"
+        "set_current_space_as_subordinate": "Nastavit aktu\u00e1ln\u00ed prostor jako pod\u0159\u00edzen\u00fd vybran\u00e9mu?",
+        "sensor_data": "Sensor data"
     }
 }

backend/cs/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Edged",
+        "layout_edged_explica": "Removes the rounded corners of visual elements that usually strongly feature them.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone is a color scheme designed to follow colors used in traditional Thai art. It was compiled by Pairoj Pittayamatee, and is the result of a ten year study about traditional color making and usage in Thai art history for his master's and doctoral degrees at Silpakorn University. (Wikipedia)",
+        "application_localstorage": "The selection of theme components is stored in the browser's local storage. As such, it will need to be re-applied if the browser cache is emptied.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized is a low-contrast color scheme optimized for readability and syntax-highlighting.",
+        "layout_main_aside_separated": "Separated sidebars",
+        "layout_main_aside_separated_explica": "Adds a more pronounced background color to the page and highlights sidebars and main page contents in separated boxes.",
+        "layout_submit_buttons_fullwidth": "Full width submit buttons ",
+        "layout_submit_buttons_fullwidth_explica": "Increases the width of submit buttons to the full width of the containing element.",
+        "layout_textareas_minimum_height": "Minimum height for text areas",
+        "layout_textareas_minimum_height_explica": "Sets a minimum height to textareas that automatically resize otherwise.",
+        "textareas_minimum_height": "Minimum height for text areas",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the red\/violet series, the red series and the achromatic series listed there.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the blueviolet series and the achromatic series listed there.",
+        "layout_icons_high_contrast": "High contrast icons",
+        "layout_icons_high_contrast_explica": "Removes the opacity setting from icons, so that they will be displayed in solid black \/ white colors.",
+        "layout_icons_large": "Increase icon size",
+        "layout_icons_large_explica": "Increases the icon size significantly. They are thus easier to see and click, but - importantly - are misaligned respective to the text. Use with caution."
+    }
+}

backend/cs/user.json

@@ -180,6 +180,9 @@
         "instance_level_contact_explica": "Enabling this toggle will automatically activate your user profile and make your profile listed as an instance-wide contact person in the navigation.",
         "invite_date": "Invite date",
         "publish_user_profile": "Publish user profile",
-        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region)."
+        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region).",
+        "account_disabled": "Account disabled",
+        "generate_auth_token": "Generate auth token",
+        "invalidate_auth_token": "Invalidate & remove auth token"
     }
 }

backend/cs/z_migration.json

@@ -0,0 +1,10 @@
+{
+    "z_migration": {
+        "pre_release_title": "Pre-release of musdb's upcoming UI rewrite",
+        "try_out_new_ui": "Try out the new UI",
+        "pre_release_intro": "For the last months we have been working on a complete rewrite of the musdb's user interface. While much remains essentially the same, the new UI aims to be much more streamlined and is based on an entirely different, more efficient architecture.",
+        "pre_release_intro2": "Some blog posts have already given previews to it. Now, we can release the new UI in a pre-alpha state: Quite some features are still missing from the old UI, but most regular workflows should already be supported in the new UI. Read more details about the current pre-release or try it out below. As usual, but especially now, any feedback is welcome!",
+        "read_blog_post": "Read blog post",
+        "pre_release_blog_post_link": "https:\/\/blog.museum-digital.org\/2026\/09\/30\/pre-release-of-musdbs-new-ui\/"
+    }
+}

backend/de/action.json

@@ -106,9 +106,9 @@
         "stats_md_contents": "Ver\u00f6ffentlichte Datenbankinhalte bei museum-digital",
         "your_usage_of_musdb": "Eigene Nutzung von musdb",
         "event_type": "Ereignistyp",
-        "space_input": "Einen neuen Raum anlegen",
+        "space_input": "Crearea unui spa\u021biu nou",
         "acquisition_input": "Einen neuen Erwerbungsvorgang anlegen",
-        "linked_to_objects": "Verkn\u00fcpft mit Objekt",
+        "linked_to_objects": "Conectat la obiect",
         "linked_to_loans": "Verkn\u00fcpft mit Leihe",
         "linked_to_literature": "Verkn\u00fcpft mit Literatur",
         "contact_input": "Neuen Kontakt anlegen",
@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Suche Objekte die dieser Sammlung oder einer der ihr untergeordneten Sammlungen zugeordnet sind.",
         "search_by_collection_exclusive": "Suche Objekte, die exakt dieser Sammlung - nicht den ihr untergeordneten Sammlungen - zugewiesen sind.",
         "search_by_space_inclusive": "Suche Objekte die diesem Raum oder einem der ihm untergeordneten R\u00e4ume zugeordnet sind.",
-        "search_by_space_exclusive": "Suche Objekte, die exakt diesem Raum - nicht den ihr untergeordneten R\u00e4umen - zugewiesen sind."
+        "search_by_space_exclusive": "Suche Objekte, die exakt diesem Raum - nicht den ihr untergeordneten R\u00e4umen - zugewiesen sind.",
+        "data_dissemination": "Datenweitergabe",
+        "data_dissemination_intro": "Links zu den Endpunkten, die genutzt werden k\u00f6nnen, um verschiedene Datenbest\u00e4nde der Institution in maschinenlesbarer Form und potentiell automatisiert abzurufen.",
+        "search_by_tag_inclusive": "Suche Objekte die diesem Schlagwort oder einem der ihm untergeordneten Schlagworte zugeordnet sind.",
+        "search_by_tag_exclusive": "Suche Objekte, die exakt diesem Schlagwort - nicht den ihm untergeordneten Schlagworten- zugewiesen sind.",
+        "search_by_place_inclusive": "Suche Objekte die diesem Ort oder einem der ihm untergeordneten Orte zugeordnet sind.",
+        "search_by_place_exclusive": "Suche Objekte, die exakt diesem Ort - nicht den ihm untergeordneten Orten - zugewiesen sind.",
+        "export_selection_directly": "Ausgew\u00e4hlte Eintr\u00e4ge direkt exportieren",
+        "export_selection_directly_explica": "Exportiert die ausgew\u00e4hlten Entit\u00e4ten, so wie sie in der Liste angezeigt werden. Dieser Export beinhaltet keine Daten, die nicht auch in der \u00dcbersicht angezeigt werden. Um einen solchen \"tiefergehenden\" Export auszul\u00f6sen sollten - so vorhanden - die relevanten Exportfunktionalit\u00e4ten oder die API genutzt werden. Der direkte Export der Listeneintr\u00e4ge kann hierf\u00fcr eine Grundlage bilden.",
+        "theming_explica": "musdb unterst\u00fctzt rudiment\u00e4res Theming. Einerseits k\u00f6nnen Anpassungen des Layouts aktiviert werden, andererseits k\u00f6nnen alternative Farbschemata geladen werden. Mehrere Layout-Anpassungen k\u00f6nnen gleichzeitig ausgew\u00e4hlt sein und werden dann miteinander kombiniert."
     }
 }

backend/de/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "Kein Eintrag verkn\u00fcpft",
         "repeat": "Wiederholen",
         "repeat_explica": "Wiederholt den letzten im selben Feld eingetragenen Wert und f\u00fcgt ihn beim aktuellen Objekt ein. ",
-        "setup_missing": "Noch nicht konfiguriert"
+        "setup_missing": "Noch nicht konfiguriert",
+        "currently_configured": "Derzeit konfiguriert",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Verstecken",
+        "api": "API",
+        "apis": "Programmierschnittstellen",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting beschreibt das automatische und regelm\u00e4\u00dfige abrufen von Datensets aus einer Datenquelle. Um einen vollst\u00e4ndig automatisierten Prozess zu erm\u00f6glichen, beschreiben offene Standards wie OAI-PMH standartisierte Schnittstellen um gr\u00f6\u00dfere Datenbest\u00e4nde Schritt f\u00fcr Schritt in kleineren, leichter bearbeitbaren Einheiten abzurufen. Die konkreten einzelnen Eintr\u00e4ge - im Falle von museum-digital die ver\u00f6ffentlichte Objektdatens\u00e4tze - werden dann mithilfe passender offener Standards wie z.B. LIDO beschrieben um etwa externen Plattformen regelm\u00e4\u00dfige und vollst\u00e4ndig automatisierte Datenabgleiche zu erm\u00f6glichen.",
+        "oai_pmh_explica_md": "Die OAI-PMH-Implementation von museum-digitals Portalen kann genutzt werden, um \u00fcber museum-digital ver\u00f6ffentlichte Objektdatens\u00e4tze stapelweise f\u00fcr einen Datenabgleich abzurufen. Sie ist dabei flexibel: Der Suchlogik folgend k\u00f6nnen die Daten einzelner Museen oder z.B. auch einzelner Sammlungen abgerufen werden. Direkt folgend findet sich die URL des OAI-PMH-Endpunktes, den externe Partner nutzen k\u00f6nnen, um einen Datenabgleich aller von einer Institution ver\u00f6ffentlichten Objektdatens\u00e4tze durchzuf\u00fchren.",
+        "apis_explica": "Programmierschnittstellen oder Application Programming Interfaces (APIs) bieten einen stabilen, maschinenlesbaren Zugang zu den Daten und Funktionen einer Anwendung. Programmierende k\u00f6nnen Sie nutzen um darauf aufbauende weitere Funktionalit\u00e4ten oder Anwendungen zu implementieren.",
+        "apis_explica_md": "Im Falle von museum-digital ist die zwingende erste Frage, welche Daten wie genutzt werden sollen. Die \u00f6ffentlichen APIs von museum-digitals Portalen bieten Lesezugriff auf die \u00fcber die Portale ver\u00f6ffentlichten Datens\u00e4tze. Diese Schnittstellen folgen der Logik der menschenlesbaren HTML-Seiten und sind gezielt einfach und ohne Authentifizierung zu nutzen. Reicht also ein lesender Zugriff auf publizierte Daten-Best\u00e4nde, dann sollten diese genutzt werden.",
+        "apis_explica_md_musdb": "M\u00f6chte man auch unver\u00f6ffentlichte Daten auslesen oder allgemein schreibend auf die bei museum-digital \/ \u00fcber musdb gespeicherten Datenbest\u00e4nde einwirken, so sind die \u00f6ffentlichen Schnittstellen ungeeignet. In diesem Fall werden die Schnittstellen von musdb ben\u00f6tigt. Um diese zu Nutzen ist ein daf\u00fcr gezielt eingerichteter Bot-Benutzeraccount n\u00f6tig, dessen Bereichtigungen exakt auf die geplante Anwendung zugeschnitten werden k\u00f6nnen. Mit diesem Benutzeraccount k\u00f6nnen sich nun externe Programme authentifizieren und - eingeschr\u00e4nkt durch die Rechteverwaltung - potentiell jede Action vornehmen, die auch menschliche Nutzende in musdb durchf\u00fchren k\u00f6nnen.",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-kompatible Dokumentation von museum-digitals \u00f6ffentlichen APIs (Lesezugriff, nur f\u00fcr ver\u00f6ffentlichte Daten)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-kompatible Dokumentation von musdbs API (lesend und schreibend)",
+        "weekday": "Wochentag",
+        "no_title_selected": "Kein Titel vergeben",
+        "sensor_data": "Sensordaten",
+        "translations": "\u00dcbersetzungen",
+        "places": "Orte",
+        "actors": "Akteure",
+        "times": "Zeiten",
+        "sources": "Quellen",
+        "edit_in_nodac": "In nodac bearbeiten",
+        "title": "Titel",
+        "vocabularies": "Vokabulare",
+        "ignore": "Ignorieren",
+        "url": "URL",
+        "is_capitalized": "Ist",
+        "relevance": "Relevanz",
+        "abort": "Abbrechen",
+        "ids": "IDs",
+        "address": "Adresse",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/de/collection.json

@@ -41,7 +41,7 @@
         "collection_has_been_edited": "Die Sammlung wurde bearbeitet",
         "collection_overview": "Sammlungs\u00fcbersicht",
         "collection_order": "Reihenfolge",
-        "no_collection_yet": "Sie (oder ihre Institution) haben noch keine Sammlungen angelegt.",
+        "no_collection_yet": "Dumneavoastr\u0103 (sau institu\u021bia dumneavoastr\u0103) nu a\u021bi creat \u00eenc\u0103 nicio colec\u021bie.",
         "collection_moved": "Die Sammlung wurde bewegt",
         "base_data": "Basisdaten zur Sammlung",
         "related_collections": "Verkn\u00fcpfte Sammlungen",

backend/de/data_history.json

@@ -99,6 +99,7 @@
         "querying_data_history": "Rufe Datensatzgeschichte ab",
         "phone_number": "Telefonnummer",
         "regular_space": "Regelm\u00e4\u00dfiger Aufenthalt",
-        "acquisition": "Erwerb"
+        "acquisition": "Erwerb",
+        "webdav_gen_access_data": "WebDAV-Zugangsdaten generiert"
     }
 }

backend/de/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Art des Dokuments",
         "document_type_explica": "In welchem Bezug steht das Dokument zum Objekt?",
         "generate_inventory_number_explica": "Generiert die n\u00e4chste Inventarnummer auf Basis des f\u00fcr die Institution eingestellten Inventarnummern-Schemas.",
-        "no_inventory_number_scheme_set": "F\u00fcr diese Institution wurde noch kein Inventarnummern-Schema definiert. Dies kann \u00fcber die institutionsspezifischen Einstellungen geschehen."
+        "no_inventory_number_scheme_set": "F\u00fcr diese Institution wurde noch kein Inventarnummern-Schema definiert. Dies kann \u00fcber die institutionsspezifischen Einstellungen geschehen.",
+        "pdf_publicinfo_explica": "PDF-Vorlage zur Darstellung ver\u00f6ffentlichter oder ver\u00f6ffentlichbarer Objektdaten in einem publizierbaren A4-Format.",
+        "pdf_knorr_explica": "Eine PDF-Vorlage entsprechend dem bis heute in Teilen von Deutschland popul\u00e4ren Knorr-Format.",
+        "pdf_a5simple_explica": "Standard-Vorlage f\u00fcr PDF-Abz\u00fcge in A5.",
+        "pdf_fullobject_explica": "Eine mehrsprachige PDF-Vorlage, die alle zu einem Objekt erfassten Datenfelder in einem einfachen zweispaltigen Layout wiedergibt.",
+        "pdf_kartya2_explica": "Eine PDF-Vorlage f\u00fcr ungarischsprachige Museen.",
+        "pdf_kartya3_explica": "Eine PDF-Vorlage f\u00fcr ungarischsprachige Museen.",
+        "object_object_links": "Objekt-Objekt-Beziehungen",
+        "limit_search_to_selection_explica": "Beschr\u00e4nkt die Suchergebnisse weiter auf die derzeit ausgew\u00e4hlten Objekte. Damit k\u00f6nnen eben diese Objekte mit der Stapelverarbeitung gezielt weiterbearbeitet, gemeinsam analysiert oder exportiert werden."
     },
     "ortart": [
         "",

backend/de/object_basis.json

@@ -40,10 +40,11 @@
         "toggle_query_language": "Anzeige in Abfragesprache an-\/abschalten",
         "right_click_list_favs": "Rechts klicken f\u00fcr Listen der gespeicherten und letzten Suchabfragen",
         "toggles_search_display_mode": "\u00c4ndert Anzeigemodus der Ergebnis-Seite",
-        "metadata_quality_score": "Metadata quality score",
+        "metadata_quality_score": "Metadaten-Qualit\u00e4ts-Wert",
         "series_is_public": "Ver\u00f6ffentlichte Objektgruppe",
         "series_is_not_public": "Interne Objektgruppe",
         "series_is_public_explica": "Wenn sowohl das Objekt als auch die Objektgruppe \u00f6ffentlich geschaltet sind, wird das Objekt \u00f6ffentlich als Teil der Gruppe gelistet.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventarnummer (Nummern padded)"
     }
 }

backend/de/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regelm\u00e4\u00dfiges Versenden von Reporten",
         "edit_custom_reports": "Report-Vorlagen anpassen",
         "custom_reports_intro": "Mit den \"eigenen Report-Vorlagen\" k\u00f6nnen Museen Exporte als Tabelle oder Textdokument selbst gestalten.",
-        "hide_fields": "Datenfelder verstecken"
+        "hide_fields": "Datenfelder verstecken",
+        "add_new_custom_report_template": "Neues Report-Template hinzuf\u00fcgen",
+        "custom_reports_see_lists_placeholders": "Mit einem Klick auf einen der Buttons kann die Liste der f\u00fcr den jeweiligen Typ von Eintrag verf\u00fcgbaren Platzhalter eingesehen werden.",
+        "placeholders": "Platzhalter",
+        "custom_report_target": "Ziel-Seite",
+        "custom_report_target_explica": "Der institutionsspezifische Report werden auf den hier ausgew\u00e4hlten Arten von Seiten verf\u00fcgbar sein. Die genutzten Platzhalter m\u00fcssen den f\u00fcr diesen Typen verf\u00fcgbaren entsprechen.",
+        "share_folder_share_link": "Per Link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Einige Funktionalit\u00e4ten der \u00f6ffentlichen Portale von museum-digital k\u00f6nnen durch die f\u00fcr die jeweiligen Inhalte verantworlichen Institutionen ge\u00e4ndert oder angereichert werden. Die hierf\u00fcr relevanten Einstellungen finden sich an dieser Stelle.",
+        "integrations_explica": "Hier k\u00f6nnen direkt in musdb implementierte Integrationen mit externen Programmen konfiguriert werden. Um sie tats\u00e4chlich nutzen zu k\u00f6nnen, sind weitere, benutzerspezifische Einstellungen n\u00f6tig. Wichtig zu bemerken ist, dass diese Einstellungen nur die direkt in musdb implementierten Integrationen betreffen. Weitere k\u00f6nnen \u00fcber die Programmierschnittstelle von musdb implementiert werden.",
+        "webhooks_explica": "Webhooks sind ein simpler Mechanismus f\u00fcr die Automatisierung.\r\nWird in musdb eine Aktion einer bestimmten Kategorie ausgef\u00fchrt, dann f\u00fchrt der Server von musdb im Hintergrund einen HTTP-Request auf eine vordefinierte URL aus und sendet Kontextinformationen zur durchgef\u00fchrten Aktion mit. Ein Anwendungsbeispiel: Man k\u00f6nnte etwa konfigurieren, dass ein solcher Aufruf immer geschieht, wenn ein Objekt ver\u00f6ffentlicht wird. Hinter der aufzurufenden URL k\u00f6nnte dann ein Script hinterlegt sein, das die Informationen von der \u00f6ffentlichen Seite des neu ver\u00f6ffentlichten Objektes abruft und diese automatisch auf die Social-Media-Kan\u00e4le der Institution postet.",
+        "object_input_page_explica": "Here kann die Objekt-Eingabeseite auf die Notwendigkeiten des Hauses angepasst werden. Zus\u00e4tzliche Felder k\u00f6nnen direkt auf der Eingabeseite verf\u00fcgbar gemacht und, so gew\u00fcnscht, als Pflichtfelder identifiziert werden.",
+        "alt_no_schemas_explica": "Auf dem Reiter \"Basis\" der Objekterfassungsseite lassen sich alternative Nummern f\u00fcr Objekte erfassen. Die Kategorie der dort erfassten alternativen Nummern ist ein Freitextfeld. Sollen zus\u00e4tzliche Kontextinformationen zu dieser Kategorie von alternativen Nummern verzeichnet werden, so kann das hier geschehen. Ist exakt derselbe Name f\u00fcr die Kategorie eingetragen, erscheint bei ver\u00f6ffentlichten Objekten und Nummern ein Tooltip, der die Erkl\u00e4rung zur Nummern-Kategorie anzeigt. Des weiteren k\u00f6nnen hier HTML5-Validierungsmuster eingetragen werden, um eine uniforme Erfassung der Nummern einer Kategorie zu erzwingen."
     }
 }

backend/de/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Keine Sensordaten erfasst",
         "get_url_for_logging": "URL zum Loggen aufrufen",
         "object_addendum_space_explica": "W\u00e4hlen Sie einen Raum aus der Liste aus. Um einen neuen Raum einzuf\u00fcgen k\u00f6nnen Sie den \"+\"-Button klicken. Ein Log der bisherigen Aufenthaltsorte des Objekts kann \u00fcber einen Rechtsklick auf das Auswahlfeld ge\u00f6ffnet werden.",
-        "set_current_space_as_subordinate": "Den derzeitigen Raum dem angeklickten unterordnen?"
+        "set_current_space_as_subordinate": "Den derzeitigen Raum dem angeklickten unterordnen?",
+        "sensor_data": "Sensordaten"
     }
 }

backend/de/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Eckig",
+        "layout_edged_explica": "Entfernt die abgerundeten Ecken der visuellen Elemente, die normalerweise besonders ausgepr\u00e4gte abgerundete Ecken haben.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone ist ein Farbschema, das die Farben der traditionellen Kunst Thailands abbilden soll. Es wurde von Pairoj Pittayamatee zusammengetragen und ist das Resultat einer zehnj\u00e4hrigen Forschungsarbeit \u00fcber die traditionelle Farb-erstellung und Nutzung in Thailand.",
+        "application_localstorage": "The Auswahl von optionalen Theming-Komponenten wird rein im Browser gespeichert. Ein Leeren des Cachen entfernt damit auch die getroffene Auswahl, sodass es sein kann, dass die Auswahl sp\u00e4ter - oder auf anderen Ger\u00e4ten - noch einmal getroffen werden muss.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized ist ein kontrastarmes Farbschema, optimiert f\u00fcr Lesbarkeit und Syntax-Highlighting.",
+        "layout_main_aside_separated": "Seitenspalte deutlicher getrennt",
+        "layout_main_aside_separated_explica": "F\u00fcllt den Hintergrund mit einer ausdrucksst\u00e4rkeren Farbe und hinterlegt Seitenspalten und Haupt-Inhalt der Seiten mit der regul\u00e4ren Hintergrundfarbe, um diese klarer als getrennte Elemente zu kennzeichnen.",
+        "layout_submit_buttons_fullwidth": "Abschicken-Buttons auf voller Breite",
+        "layout_submit_buttons_fullwidth_explica": "Erh\u00f6ht die Breite der Abschicken-Buttons auf die gesamte verf\u00fcgbare Breite.",
+        "layout_textareas_minimum_height": "Erh\u00f6hte Minimal-H\u00f6he f\u00fcr Textfelder",
+        "layout_textareas_minimum_height_explica": "F\u00fcgt eine erh\u00f6hte Minimalh\u00f6he f\u00fcr Textfelder (textarea) ein, die sich anderweitig frei der H\u00f6he des Inhalts anpassen.",
+        "textareas_minimum_height": "Minimal-H\u00f6he f\u00fcr Text-Eingabe-Boxen",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Farbschema auf Basis der Wikipedia-Liste der traditionallen japanischen Farben. Kombiniert: red\/violet series, red series, achromatic series.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Farbschema auf Basis der Wikipedia-Liste der traditionallen japanischen Farben. Kombiniert: blue\/violet series, achromatic series.",
+        "layout_icons_high_contrast": "Hoher Kontrast f\u00fcr Icons",
+        "layout_icons_high_contrast_explica": "Entfernt die Durchsichtigkeit von Icons, sodass diese mit in vollem schwarz bzw. wei\u00df angezeigt werden.",
+        "layout_icons_large": "Icon-Gr\u00f6\u00dfe erh\u00f6hen",
+        "layout_icons_large_explica": "Erh\u00f6ht die angezeigte Gr\u00f6\u00dfe von Icons betr\u00e4chtlich. Sie sind damit deutlich leichter zu erkennen und anzuklicken, aber - wichtig - brechen die Positionierung gegen\u00fcber dem umgebenden Text. Vorsichtig benutzen."
+    }
+}

backend/de/time.json

@@ -12,9 +12,9 @@
         "time_term": "Zeitbegriff",
         "zeitbegriff_explica": "(Fast) beliebige Eingabe<br><br>Beispiel 1: 16.02.1913 <br>Beispiel 2: Erste H\u00e4lfte 12. Jh.<br>Beispiel 3: 1655-1699<br><br>Die \"Zeitbegriff\"-Angabe wird f\u00fcr die Anzeige ben\u00f6tigt.<br><br><b>Bitte beachten:<\/b><br><b>\"1. Weltkrieg\", \"NS-Zeit\", ...<\/b><br>... historische \"Ereignisse\", <b>keine<\/b> Zeitangabe<br><b>\"Rokoko\", \"Klassizismus\", ...<\/b><br>... Stilepochen, <b>keine<\/b> Zeitangabe<br><b>\"R\u00f6mische Kaiserzeit\", \"Sp\u00e4te Jungsteinzeit\", ...<\/b><br>... werden verschieden gebraucht <b>keine<\/b> Zeitangaben<br><b>\"Mioz\u00e4n\", \"Cambrium\", ...<\/b><br>... sind <b>keine<\/b> eindeutigen Zeitangaben (Zeitraum-\u00c4quivalente werden von Wissenschaft st\u00e4ndig neu definiert)<br>(Derlei Nicht-Zeit-Angaben bitte als Schlagworte behandeln)",
         "begin": "Beginn [JAHR]",
-        "zeitbeginn_explica": "Bitte immer eine Jahreszahl (<b>vierstellig<\/b>) eingeben<br><br>- Bei Werten vor dem Jahre Null ein Minuszeichen davor setzen<br>- Bei Zeitbegriffen wie \"Vor 1830\", wenn also der Beginn ungekannt ist, bitte ein Fragezeichen eintragen<br><br>Beispiel 1: 1913<br>Beispiel 2: -1800<br>Beispiel 3: ?",
+        "zeitbeginn_explica": "Bitte immer eine Jahreszahl (<b>vierstellig<\/b>) eingeben<br><br>- Bei Werten vor dem Jahre Null ein Minuszeichen davor setzen<br>- Bei Zeitbegriffen wie \"Vor 1830\", wenn also der Beginn unbekannt ist, bitte ein Fragezeichen eintragen<br><br>Beispiel 1: 1913<br>Beispiel 2: -1800<br>Beispiel 3: ?",
         "end": "Ende [JAHR]",
-        "zeitende_explica": "Bitte immer eine Jahreszahl (<b>vierstellig<\/b>) eingeben<br><br>- Bei Werten vor dem Jahre Null ein Minuszeichen davor setzen<br>- Bei Zeitbegriffen wie \"Nach 1830\", wenn also das exakte Zeitraum-Ende ungekannt ist, bitte ein Fragezeichen eintragen<br><br>Beispiel 1: 1913<br>Beispiel 2: -1800<br>Beispiel 3: ?",
+        "zeitende_explica": "Bitte immer eine Jahreszahl (<b>vierstellig<\/b>) eingeben<br><br>- Bei Werten vor dem Jahre Null ein Minuszeichen davor setzen<br>- Bei Zeitbegriffen wie \"Nach 1830\", wenn also das exakte Zeitraum-Ende unbekannt ist, bitte ein Fragezeichen eintragen<br><br>Beispiel 1: 1913<br>Beispiel 2: -1800<br>Beispiel 3: ?",
         "counted": "Z\u00e4hlzeit",
         "year": "Jahr",
         "month": "Monat",

backend/de/user.json

@@ -59,7 +59,7 @@
         "remove_from_museum": "Verkn\u00fcpfung mit diesem Museum l\u00f6sen",
         "remove_from_collection": "Verkn\u00fcpfung mit dieser Sammlung l\u00f6sen",
         "remove_from_series": "Verkn\u00fcpfung mit dieser Objektgruppe l\u00f6sen",
-        "auth_token": "Authentifizierungs Token",
+        "auth_token": "Authentifizierungs-Token",
         "auth_token_explica": "Auf dieser Seite k\u00f6nnen Sie einen Authentifizierungs Token erhalten. Sie k\u00f6nnen das Token nicht erneut abrufen. Stellen Sie sicher, dass Sie sich das Token herunterladen und an einem sicheren Platz verwahren.",
         "confirm": "Best\u00e4tigen",
         "auth_token_generated": "Authentifizierungs Token erzeugt",
@@ -175,11 +175,14 @@
         "account_expiry_date": "Ablaufdatum",
         "account_expiry_date_explica": "Wird dieser Wert auf ein Datum in der Zukunft gesetzt, wird das Konto zum angegebenen Zeitpunkt automatisch gel\u00f6scht. Dies kann n\u00fctzlich sein, wenn man etwa ein Konto f\u00fcr Kollegen mit zeitlich beschr\u00e4nktem Vertrag einrichtet.",
         "agreed_on": "Zugestimmt am",
-        "institution_level_contact": "Institution-level contact person",
+        "institution_level_contact": "Kontaktperson im Museum",
         "instance_level_contact": "Kontaktperson f\u00fcr die Instanz",
         "instance_level_contact_explica": "Ist dieser Schalter aktiviert, wird das Benutzer-Profil automatisch auf \"sichtbar\" geschaltet und Kontaktdaten zum Konto in der Navigation als Ansprechpartner f\u00fcr alle Nutzer der Instanz gelistet. ",
         "invite_date": "Datum der Einladung",
         "publish_user_profile": "User-Profil ver\u00f6ffentlichen",
-        "publish_user_profile_explica": "Ver\u00f6ffentlichen Sie ihr Benutzerprofil, so wird es f\u00fcr andere Nutzer derselben Instanz von musdb einsehbar sein (f\u00fcr gew\u00f6hnlich bedeutet dies Kolleg*Innen aus derselben Institution und Region)."
+        "publish_user_profile_explica": "Ver\u00f6ffentlichen Sie ihr Benutzerprofil, so wird es f\u00fcr andere Nutzer derselben Instanz von musdb einsehbar sein (f\u00fcr gew\u00f6hnlich bedeutet dies Kolleg*Innen aus derselben Institution und Region).",
+        "account_disabled": "Nutzerkonto deaktiviert",
+        "generate_auth_token": "Authentifizierungs-Token generieren",
+        "invalidate_auth_token": "Authentifizierungs-Token invalidieren und entfernen"
     }
 }

backend/de/z_migration.json

@@ -0,0 +1,10 @@
+{
+    "z_migration": {
+        "pre_release_title": "Pre-release von musdb's neuer Benutzeroberfl\u00e4che",
+        "try_out_new_ui": "Die neue Benutzeroberfl\u00e4che ausprobieren",
+        "pre_release_intro": "\u00dcber die letzten Monate haben wir an einer tiefgreifenden \u00dcberarbeitung der Benutzeroberfl\u00e4che von musdb gearbeitet. W\u00e4hrend viel logisch gleich bleibt, haben wir versucht eine logischere, eindeutigere Benutzeroberfl\u00e4che zu schaffen und daf\u00fcr eine grundlegend andere, effizientere und modernere Architektur gew\u00e4hlt.",
+        "pre_release_intro2": "Einige Blog-Posts der letzten Monate haben bereits erste Vorschauen der neuen Benutzeroberfl\u00e4che geliefert. Heute k\u00f6nnen wir sie in einer ersten, noch unvollst\u00e4ndigen aber f\u00fcr die Meisten bereits funktionalen Form ver\u00f6ffentlichen. Eine ausf\u00fchrliche Liste der noch fehlenden Features findet sich im Blog. Die neue Version kann unten ausprobiert werden. Wir w\u00fcrden uns \u00fcber Feedback freuen.",
+        "read_blog_post": "Blog-Post lesen",
+        "pre_release_blog_post_link": "https:\/\/blog.museum-digital.org\/2026\/09\/30\/pre-release-of-musdbs-new-ui\/"
+    }
+}

backend/dsb/action.json

@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way.",
+        "search_by_tag_inclusive": "Search objects linked to this tag or any of its subordinate tags.",
+        "search_by_tag_exclusive": "Search objects linked to exactly this tag (not those linked to any of its subordinate tags).",
+        "search_by_place_inclusive": "Search objects linked to this place or any of its subordinate places.",
+        "search_by_place_exclusive": "Search objects linked to exactly this place (not those linked to any of its subordinate places).",
+        "export_selection_directly": "Export selected entries directly",
+        "export_selection_directly_explica": "Exports the selected entities as they are displayed in the list. This export option will not contain any information that is not available in the overview. To trigger such an export, use the respective export functionalities (where available) or the API.",
+        "theming_explica": "musdb supports theming to a certain level. On the one hand, special layout adjustments can be loaded. On the other hand, alternative color schemes can be selected. Selecting multiple alternative layout components combines them."
     }
 }

backend/dsb/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "No entity has been linked",
         "repeat": "Repeat",
         "repeat_explica": "Repeat the last content you entered in this same data field.",
-        "setup_missing": "Not set up yet"
+        "setup_missing": "Not set up yet",
+        "currently_configured": "Currently configured",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a programm. They thus allow programmers to build external applications on top of them.",
+        "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
+        "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday",
+        "no_title_selected": "No title selected",
+        "sensor_data": "Sensor data",
+        "translations": "Translations",
+        "places": "Places",
+        "actors": "Actors",
+        "times": "Times",
+        "sources": "Sources",
+        "edit_in_nodac": "Edit in nodac",
+        "title": "Title",
+        "vocabularies": "Vocabularies",
+        "ignore": "Ignore",
+        "url": "URL",
+        "is_capitalized": "Is",
+        "relevance": "Relevance",
+        "abort": "Abort",
+        "ids": "IDs",
+        "address": "Address",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/dsb/data_history.json

@@ -99,6 +99,7 @@
         "querying_data_history": "Querying data history",
         "phone_number": "Phone number",
         "regular_space": "Regular location",
-        "acquisition": "Acquisition"
+        "acquisition": "Acquisition",
+        "webdav_gen_access_data": "Generate WebDAV access data"
     }
 }

backend/dsb/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Type of document",
         "document_type_explica": "In what relation does the document stand towards the object?",
         "generate_inventory_number_explica": "Automatically generates the next inventory number based on your institution's inventory number scheme.",
-        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings."
+        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings.",
+        "pdf_publicinfo_explica": "A PDF displaying published or publishable data for the object in a presentable A4 template.",
+        "pdf_knorr_explica": "A PDF template following the Knorr format, still popular in parts of Germany.",
+        "pdf_a5simple_explica": "Default multilingual A5 PDF template.",
+        "pdf_fullobject_explica": "A multilingual PDF template that covers all recorded data on the object in a simple two-column layout.",
+        "pdf_kartya2_explica": "A5 PDF template prepared for Hungarian museums.",
+        "pdf_kartya3_explica": "A5 PDF template prepared for Hungarian museums.",
+        "object_object_links": "Object to object links",
+        "limit_search_to_selection_explica": "Further restricts the search query to return only the selected objects. The selection will thus be available for further processing via batch processing, analysis, and exports."
     },
     "ortart": [
         "",

backend/dsb/object_basis.json

@@ -44,6 +44,7 @@
         "series_is_public": "Published series",
         "series_is_not_public": "Unpublished series",
         "series_is_public_explica": "If both the series and the object have been toggled public, the object will be publicly listed as part of the series.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventory number (padded numbers)"
     }
 }

backend/dsb/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regular sending of reports",
         "edit_custom_reports": "Edit custom reports",
         "custom_reports_intro": "Using \"Custom report\" templates institutions can define their own exports in the form of CSV tables or HTML text documents.",
-        "hide_fields": "Hide data fields"
+        "hide_fields": "Hide data fields",
+        "add_new_custom_report_template": "Add new custom report template",
+        "custom_reports_see_lists_placeholders": "Click on a button to view the list of available placeholders",
+        "placeholders": "Placeholders",
+        "custom_report_target": "Target page",
+        "custom_report_target_explica": "The custom report will be available for the selected target page type. Placeholders may or may not be available for a given type of target page.",
+        "share_folder_share_link": "Via share link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Some functionalities of museum-digital's portals can be influenced by the institutions responsible for the respective content. Here the corresponding settings can be managed.",
+        "integrations_explica": "Some integration capabilities linking musdb with other programs are built-in with musdb. To actually use those integrations, musdb needs to be given access to the relevant other services on the levels of institutions and users. Note that these settings pertain to built-in integrations. Further integrations can be written using musdb's API.",
+        "webhooks_explica": "Webhooks are a simple mechanism for an application to let other applications respond to a given action in the source one. When a given action is executed, musdb's server will perform an HTTP query to a pre-defined URL in the background. Some context information on the performed action is provided in the POST-header (user data, the processed API call, and an optional secret to lock down the target script against unwarranted access). If you e.g. write a script that receives such an HTTP call upon the publication of objects, you can e.g. trigger the automatic posting of a the newly posted object record on your social media feed.",
+        "object_input_page_explica": "Here the object input page can configured. Additional fields can be made available and potentially set to be required fields for newly added objects.",
+        "alt_no_schemas_explica": "Alternative numbers for objects can be recorded on the object page's base tab. The category for such numbers are not a controlled list. But, depending on the type of alternative number, it might be fruitful to provide additional context information on this type of number. If a number schema set here has the exact same category name as has been entered for an object, the explanation will be provided in a tooltip when hovering over the alternative number on published object pages. Additionally, HTML5 validation patterns can be selected to ensure a consistent form for the recording of the given category of alternative object numbers."
     }
 }

backend/dsb/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Failed to locate any sensor data for this space",
         "get_url_for_logging": "Get URL for logging",
         "object_addendum_space_explica": "Select a space from the list. To add a new space press the \"+\" button. To see a log of the objects previous whereabouts right click on the selection field..",
-        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?"
+        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?",
+        "sensor_data": "Sensor data"
     }
 }

backend/dsb/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Edged",
+        "layout_edged_explica": "Removes the rounded corners of visual elements that usually strongly feature them.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone is a color scheme designed to follow colors used in traditional Thai art. It was compiled by Pairoj Pittayamatee, and is the result of a ten year study about traditional color making and usage in Thai art history for his master's and doctoral degrees at Silpakorn University. (Wikipedia)",
+        "application_localstorage": "The selection of theme components is stored in the browser's local storage. As such, it will need to be re-applied if the browser cache is emptied.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized is a low-contrast color scheme optimized for readability and syntax-highlighting.",
+        "layout_main_aside_separated": "Separated sidebars",
+        "layout_main_aside_separated_explica": "Adds a more pronounced background color to the page and highlights sidebars and main page contents in separated boxes.",
+        "layout_submit_buttons_fullwidth": "Full width submit buttons ",
+        "layout_submit_buttons_fullwidth_explica": "Increases the width of submit buttons to the full width of the containing element.",
+        "layout_textareas_minimum_height": "Minimum height for text areas",
+        "layout_textareas_minimum_height_explica": "Sets a minimum height to textareas that automatically resize otherwise.",
+        "textareas_minimum_height": "Minimum height for text areas",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the red\/violet series, the red series and the achromatic series listed there.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the blueviolet series and the achromatic series listed there.",
+        "layout_icons_high_contrast": "High contrast icons",
+        "layout_icons_high_contrast_explica": "Removes the opacity setting from icons, so that they will be displayed in solid black \/ white colors.",
+        "layout_icons_large": "Increase icon size",
+        "layout_icons_large_explica": "Increases the icon size significantly. They are thus easier to see and click, but - importantly - are misaligned respective to the text. Use with caution."
+    }
+}

backend/dsb/user.json

@@ -180,6 +180,9 @@
         "instance_level_contact_explica": "Enabling this toggle will automatically activate your user profile and make your profile listed as an instance-wide contact person in the navigation.",
         "invite_date": "Invite date",
         "publish_user_profile": "Publish user profile",
-        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region)."
+        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region).",
+        "account_disabled": "Account disabled",
+        "generate_auth_token": "Generate auth token",
+        "invalidate_auth_token": "Invalidate & remove auth token"
     }
 }

backend/dsb/z_migration.json

@@ -0,0 +1,10 @@
+{
+    "z_migration": {
+        "pre_release_title": "Pre-release of musdb's upcoming UI rewrite",
+        "try_out_new_ui": "Try out the new UI",
+        "pre_release_intro": "For the last months we have been working on a complete rewrite of the musdb's user interface. While much remains essentially the same, the new UI aims to be much more streamlined and is based on an entirely different, more efficient architecture.",
+        "pre_release_intro2": "Some blog posts have already given previews to it. Now, we can release the new UI in a pre-alpha state: Quite some features are still missing from the old UI, but most regular workflows should already be supported in the new UI. Read more details about the current pre-release or try it out below. As usual, but especially now, any feedback is welcome!",
+        "read_blog_post": "Read blog post",
+        "pre_release_blog_post_link": "https:\/\/blog.museum-digital.org\/2026\/09\/30\/pre-release-of-musdbs-new-ui\/"
+    }
+}

backend/en/acquisitions.json

@@ -1,7 +1,7 @@
 {
     "acquisitions": {
         "type": "Acquisition type",
-        "type_explica": "Here you can select how the acquisition was done. E.g. if the objects were a gift or if you bought them..",
+        "type_explica": "Here you can select how the acquisition was done. E.g. if the objects were a gift or if you bought them.",
         "name": "Acquisition name",
         "name_explica": "Name the can be used for identifying the acquisition process.",
         "date": "Acquisiton date",

backend/en/action.json

@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way.",
+        "search_by_tag_inclusive": "Search objects linked to this tag or any of its subordinate tags.",
+        "search_by_tag_exclusive": "Search objects linked to exactly this tag (not those linked to any of its subordinate tags).",
+        "search_by_place_inclusive": "Search objects linked to this place or any of its subordinate places.",
+        "search_by_place_exclusive": "Search objects linked to exactly this place (not those linked to any of its subordinate places).",
+        "export_selection_directly": "Export selected entries directly",
+        "export_selection_directly_explica": "Exports the selected entities as they are displayed in the list. This export option will not contain any information that is not available in the overview. To trigger such an export, use the respective export functionalities (where available) or the API.",
+        "theming_explica": "musdb supports theming to a certain level. On the one hand, special layout adjustments can be loaded. On the other hand, alternative color schemes can be selected. Selecting multiple alternative layout components combines them."
     }
 }

backend/en/actor.json

@@ -14,10 +14,10 @@
         "nameinst_explica": "Concrete name of an institution Example: Heavy machinery combine \"Ernst Th\u00e4lmann\"",
         "institution_short": "Abbreviation for institution",
         "kurznameinst_explica": "Some institutions have set abbreviations<br\/><br\/>Example:<br\/>Allgemeine Elektricit\u00e4ts-Gesellschaft -> AEG",
-        "short_description": "Short desription",
+        "short_description": "Short description",
         "kurzbeschinst_explica": "Short description <br\/><br\/>Example \"Founded 1897. Renamed... in 1904. Closed shop in 1921.\"",
         "hero_name": "Name",
-        "geistname_explica": "Example:<br\/>Zeus, Peleus, Red Riding Hood (fictional character)<br\/><br\/>Basically, you can add any person, that has no given name here! But, it must be possible to identify the person. If you just add \"Smith\" because you do not know the given name here you will cause incorrect links between the object to <b>anybody<\/b> named \"Smith\". In such cases, it is better, to not enter a name at all.",
+        "geistname_explica": "Example:<br\/>Zeus, Peleus, Red Riding Hood (fictional character)<br\/><br\/>Basically, you can add any person, that has no given name here! But, it must be possible to identify the person. If you just add \"Smith\" because you do not know the given name here you will cause incorrect links between the object to <b>anybody<\/b> named \"Smith\". In such cases, it is better to not enter a name at all.",
         "kurzbeschpers_explica": "Short description<br\/><br\/>Example: \"Painter, Author, Actor, born 1817 in Hamburg\"",
         "name_first": "First name(s)",
         "vorname_explica": "You can list all first names of a person<br\/><br\/>Example:<br\/>\"Georg Friedrich\" (H&auml;ndel)<br\/>\"Gotthold Ephraim\" (Lessing)<br\/><br\/>It makes little sense to add a person if only the surname is known (How could two people from the same family be distinguished?) If you do not know the first name you might add their occupation as a name (e.g. Blacksmith)",

backend/en/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "No entity has been linked",
         "repeat": "Repeat",
         "repeat_explica": "Repeat the last content you entered in this same data field.",
-        "setup_missing": "Not set up yet"
+        "setup_missing": "Not set up yet",
+        "currently_configured": "Currently configured",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a program. They thus allow programmers to build external applications on top of them.",
+        "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
+        "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday",
+        "no_title_selected": "No title selected",
+        "sensor_data": "Sensor data",
+        "translations": "Translations",
+        "places": "Places",
+        "actors": "Actors",
+        "times": "Times",
+        "sources": "Sources",
+        "edit_in_nodac": "Edit in nodac",
+        "title": "Title",
+        "vocabularies": "Vocabularies",
+        "ignore": "Ignore",
+        "url": "URL",
+        "is_capitalized": "Is",
+        "relevance": "Relevance",
+        "abort": "Abort",
+        "ids": "IDs",
+        "address": "Address",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/en/data_history.json

@@ -13,7 +13,7 @@
         "notes": "Remarks",
         "record": "Alternative language record",
         "resource": "Link with image or resource",
-        "rights": "Rights informationen",
+        "rights": "Rights information",
         "serie": "Link with object group",
         "tag": "Link with keyword",
         "visibility": "Visibility",
@@ -99,6 +99,7 @@
         "querying_data_history": "Querying data history",
         "phone_number": "Phone number",
         "regular_space": "Regular location",
-        "acquisition": "Acquisition"
+        "acquisition": "Acquisition",
+        "webdav_gen_access_data": "Generate WebDAV access data"
     }
 }

backend/en/listen.json

@@ -22,8 +22,8 @@
         "table_from_filter": "Table from filter",
         "table_from_watchlist": "Table from watchlist",
         "table_from_objectgroup": "Table from object group",
-        "export_xml": "Export objekts of table in XML",
+        "export_xml": "Export objects of table in XML",
-        "export_csv": "Export objekts of table in CSV",
+        "export_csv": "Export objects of table in CSV",
         "per_page": "Per page",
         "definition": "Definition",
         "order": "Order by",

backend/en/literature.json

@@ -26,7 +26,7 @@
         "id_in_museum": "ID (in museum)",
         "id_in_museum_explica": "The ID of the literature in the library of the museum",
         "annotation": "Annotations (internal)",
-        "annotation_explica": "Any remarks concerning this literatur will not be published",
+        "annotation_explica": "Any remarks concerning this literature entry will not be published",
         "isbn": "ISBN",
         "isbn_explica": "The ISBN of the book. It does not matter if you type in dashes or use ISBN10 or ISBN13.",
         "isbn_explica_auto": "The ISBN of the book. It does not matter if you type in dashes or use ISBN10 or ISBN13.<br>If you enther an ISBN here and store it, you will open the opportunity to retrieve information book from the Library of Congress (Washington) by clicking on the arrow to the right. If you like you can thus overwrite your entry.",

backend/en/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Type of document",
         "document_type_explica": "In what relation does the document stand towards the object?",
         "generate_inventory_number_explica": "Automatically generates the next inventory number based on your institution's inventory number scheme.",
-        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings."
+        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings.",
+        "pdf_publicinfo_explica": "A PDF displaying published or publishable data for the object in a presentable A4 template.",
+        "pdf_knorr_explica": "A PDF template following the Knorr format, still popular in parts of Germany.",
+        "pdf_a5simple_explica": "Default multilingual A5 PDF template.",
+        "pdf_fullobject_explica": "A multilingual PDF template that covers all recorded data on the object in a simple two-column layout.",
+        "pdf_kartya2_explica": "A5 PDF template prepared for Hungarian museums.",
+        "pdf_kartya3_explica": "A5 PDF template prepared for Hungarian museums.",
+        "object_object_links": "Object to object links",
+        "limit_search_to_selection_explica": "Further restricts the search query to return only the selected objects. The selection will thus be available for further processing via batch processing, analysis, and exports."
     },
     "ortart": [
         "",

backend/en/object_basis.json

@@ -44,6 +44,7 @@
         "series_is_public": "Published series",
         "series_is_not_public": "Unpublished series",
         "series_is_public_explica": "If both the series and the object have been toggled public, the object will be publicly listed as part of the series.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventory number (padded numbers)"
     }
 }

backend/en/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regular sending of reports",
         "edit_custom_reports": "Edit custom reports",
         "custom_reports_intro": "Using \"Custom report\" templates institutions can define their own exports in the form of CSV tables or HTML text documents.",
-        "hide_fields": "Hide data fields"
+        "hide_fields": "Hide data fields",
+        "add_new_custom_report_template": "Add new custom report template",
+        "custom_reports_see_lists_placeholders": "Click on a button to view the list of available placeholders",
+        "placeholders": "Placeholders",
+        "custom_report_target": "Target page",
+        "custom_report_target_explica": "The custom report will be available for the selected target page type. Placeholders may or may not be available for a given type of target page.",
+        "share_folder_share_link": "Via share link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Some functionalities of museum-digital's portals can be influenced by the institutions responsible for the respective content. Here the corresponding settings can be managed.",
+        "integrations_explica": "Some integration capabilities linking musdb with other programs are built-in with musdb. To actually use those integrations, musdb needs to be given access to the relevant other services on the levels of institutions and users. Note that these settings pertain to built-in integrations. Further integrations can be written using musdb's API.",
+        "webhooks_explica": "Webhooks are a simple mechanism for an application to let other applications respond to a given action in the source one. When a given action is executed, musdb's server will perform an HTTP query to a pre-defined URL in the background. Some context information on the performed action is provided in the POST-header (user data, the processed API call, and an optional secret to lock down the target script against unwarranted access). If you e.g. write a script that receives such an HTTP call upon the publication of objects, you can e.g. trigger the automatic posting of a the newly posted object record on your social media feed.",
+        "object_input_page_explica": "Here the object input page can configured. Additional fields can be made available and potentially set to be required fields for newly added objects.",
+        "alt_no_schemas_explica": "Alternative numbers for objects can be recorded on the object page's base tab. The category for such numbers are not a controlled list. But, depending on the type of alternative number, it might be fruitful to provide additional context information on this type of number. If a number schema set here has the exact same category name as has been entered for an object, the explanation will be provided in a tooltip when hovering over the alternative number on published object pages. Additionally, HTML5 validation patterns can be selected to ensure a consistent form for the recording of the given category of alternative object numbers."
     }
 }

backend/en/sources.json

@@ -8,7 +8,7 @@
         "book": "Book",
         "phdthesis": "PhD thesis",
         "electronical": "Electronic Resource",
-        "misc": "Miscelaneous",
+        "misc": "Miscellaneous",
         "author_creator": "Author\/Creator",
         "author_creator_explica": "The creator of the source. Type a name to select the author or creator. You can add multiple authors\/creators for a work",
         "title": "Title",

backend/en/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Failed to locate any sensor data for this space",
         "get_url_for_logging": "Get URL for logging",
         "object_addendum_space_explica": "Select a space from the list. To add a new space press the \"+\" button. To see a log of the objects previous whereabouts right click on the selection field..",
-        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?"
+        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?",
+        "sensor_data": "Sensor data"
     }
 }

backend/en/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Edged",
+        "layout_edged_explica": "Removes the rounded corners of visual elements that usually strongly feature them.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone is a color scheme designed to follow colors used in traditional Thai art. It was compiled by Pairoj Pittayamatee, and is the result of a ten year study about traditional color making and usage in Thai art history for his master's and doctoral degrees at Silpakorn University. (Wikipedia)",
+        "application_localstorage": "The selection of theme components is stored in the browser's local storage. As such, it will need to be re-applied if the browser cache is emptied.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized is a low-contrast color scheme optimized for readability and syntax-highlighting.",
+        "layout_main_aside_separated": "Separated sidebars",
+        "layout_main_aside_separated_explica": "Adds a more pronounced background color to the page and highlights sidebars and main page contents in separated boxes.",
+        "layout_submit_buttons_fullwidth": "Full width submit buttons ",
+        "layout_submit_buttons_fullwidth_explica": "Increases the width of submit buttons to the full width of the containing element.",
+        "layout_textareas_minimum_height": "Minimum height for text areas",
+        "layout_textareas_minimum_height_explica": "Sets a minimum height to textareas that automatically resize otherwise.",
+        "textareas_minimum_height": "Minimum height for text areas",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the red\/violet series, the red series and the achromatic series listed there.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the blueviolet series and the achromatic series listed there.",
+        "layout_icons_high_contrast": "High contrast icons",
+        "layout_icons_high_contrast_explica": "Removes the opacity setting from icons, so that they will be displayed in solid black \/ white colors.",
+        "layout_icons_large": "Increase icon size",
+        "layout_icons_large_explica": "Increases the icon size significantly. They are thus easier to see and click, but - importantly - are misaligned respective to the text. Use with caution."
+    }
+}

backend/en/user.json

@@ -180,6 +180,9 @@
         "instance_level_contact_explica": "Enabling this toggle will automatically activate your user profile and make your profile listed as an instance-wide contact person in the navigation.",
         "invite_date": "Invite date",
         "publish_user_profile": "Publish user profile",
-        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region)."
+        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region).",
+        "account_disabled": "Account disabled",
+        "generate_auth_token": "Generate auth token",
+        "invalidate_auth_token": "Invalidate & remove auth token"
     }
 }

backend/en/z_migration.json

@@ -0,0 +1,10 @@
+{
+    "z_migration": {
+        "pre_release_title": "Pre-release of musdb's upcoming UI rewrite",
+        "try_out_new_ui": "Try out the new UI",
+        "pre_release_intro": "For the last months we have been working on a complete rewrite of the musdb's user interface. While much remains essentially the same, the new UI aims to be much more streamlined and is based on an entirely different, more efficient architecture.",
+        "pre_release_intro2": "Some blog posts have already given previews to it. Now, we can release the new UI in a pre-alpha state: Quite some features are still missing from the old UI, but most regular workflows should already be supported in the new UI. Read more details about the current pre-release or try it out below. As usual, but especially now, any feedback is welcome!",
+        "read_blog_post": "Read blog post",
+        "pre_release_blog_post_link": "https:\/\/blog.museum-digital.org\/2026\/09\/30\/pre-release-of-musdbs-new-ui\/"
+    }
+}

backend/es/action.json

@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way.",
+        "search_by_tag_inclusive": "Search objects linked to this tag or any of its subordinate tags.",
+        "search_by_tag_exclusive": "Search objects linked to exactly this tag (not those linked to any of its subordinate tags).",
+        "search_by_place_inclusive": "Search objects linked to this place or any of its subordinate places.",
+        "search_by_place_exclusive": "Search objects linked to exactly this place (not those linked to any of its subordinate places).",
+        "export_selection_directly": "Export selected entries directly",
+        "export_selection_directly_explica": "Exports the selected entities as they are displayed in the list. This export option will not contain any information that is not available in the overview. To trigger such an export, use the respective export functionalities (where available) or the API.",
+        "theming_explica": "musdb supports theming to a certain level. On the one hand, special layout adjustments can be loaded. On the other hand, alternative color schemes can be selected. Selecting multiple alternative layout components combines them."
     }
 }

backend/es/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "No entity has been linked",
         "repeat": "Repeat",
         "repeat_explica": "Repeat the last content you entered in this same data field.",
-        "setup_missing": "Not set up yet"
+        "setup_missing": "Not set up yet",
+        "currently_configured": "Currently configured",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a programm. They thus allow programmers to build external applications on top of them.",
+        "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
+        "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday",
+        "no_title_selected": "No title selected",
+        "sensor_data": "Sensor data",
+        "translations": "Translations",
+        "places": "Places",
+        "actors": "Actors",
+        "times": "Times",
+        "sources": "Sources",
+        "edit_in_nodac": "Edit in nodac",
+        "title": "Title",
+        "vocabularies": "Vocabularies",
+        "ignore": "Ignore",
+        "url": "URL",
+        "is_capitalized": "Is",
+        "relevance": "Relevance",
+        "abort": "Abort",
+        "ids": "IDs",
+        "address": "Address",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/es/data_history.json

@@ -99,6 +99,7 @@
         "querying_data_history": "Querying data history",
         "phone_number": "Phone number",
         "regular_space": "Regular location",
-        "acquisition": "Acquisition"
+        "acquisition": "Acquisition",
+        "webdav_gen_access_data": "Generate WebDAV access data"
     }
 }

backend/es/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Type of document",
         "document_type_explica": "In what relation does the document stand towards the object?",
         "generate_inventory_number_explica": "Automatically generates the next inventory number based on your institution's inventory number scheme.",
-        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings."
+        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings.",
+        "pdf_publicinfo_explica": "A PDF displaying published or publishable data for the object in a presentable A4 template.",
+        "pdf_knorr_explica": "A PDF template following the Knorr format, still popular in parts of Germany.",
+        "pdf_a5simple_explica": "Default multilingual A5 PDF template.",
+        "pdf_fullobject_explica": "A multilingual PDF template that covers all recorded data on the object in a simple two-column layout.",
+        "pdf_kartya2_explica": "A5 PDF template prepared for Hungarian museums.",
+        "pdf_kartya3_explica": "A5 PDF template prepared for Hungarian museums.",
+        "object_object_links": "Object to object links",
+        "limit_search_to_selection_explica": "Further restricts the search query to return only the selected objects. The selection will thus be available for further processing via batch processing, analysis, and exports."
     },
     "ortart": [
         "",

backend/es/object_basis.json

@@ -44,6 +44,7 @@
         "series_is_public": "Published series",
         "series_is_not_public": "Unpublished series",
         "series_is_public_explica": "If both the series and the object have been toggled public, the object will be publicly listed as part of the series.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventory number (padded numbers)"
     }
 }

backend/es/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regular sending of reports",
         "edit_custom_reports": "Edit custom reports",
         "custom_reports_intro": "Using \"Custom report\" templates institutions can define their own exports in the form of CSV tables or HTML text documents.",
-        "hide_fields": "Hide data fields"
+        "hide_fields": "Hide data fields",
+        "add_new_custom_report_template": "Add new custom report template",
+        "custom_reports_see_lists_placeholders": "Click on a button to view the list of available placeholders",
+        "placeholders": "Placeholders",
+        "custom_report_target": "Target page",
+        "custom_report_target_explica": "The custom report will be available for the selected target page type. Placeholders may or may not be available for a given type of target page.",
+        "share_folder_share_link": "Via share link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Some functionalities of museum-digital's portals can be influenced by the institutions responsible for the respective content. Here the corresponding settings can be managed.",
+        "integrations_explica": "Some integration capabilities linking musdb with other programs are built-in with musdb. To actually use those integrations, musdb needs to be given access to the relevant other services on the levels of institutions and users. Note that these settings pertain to built-in integrations. Further integrations can be written using musdb's API.",
+        "webhooks_explica": "Webhooks are a simple mechanism for an application to let other applications respond to a given action in the source one. When a given action is executed, musdb's server will perform an HTTP query to a pre-defined URL in the background. Some context information on the performed action is provided in the POST-header (user data, the processed API call, and an optional secret to lock down the target script against unwarranted access). If you e.g. write a script that receives such an HTTP call upon the publication of objects, you can e.g. trigger the automatic posting of a the newly posted object record on your social media feed.",
+        "object_input_page_explica": "Here the object input page can configured. Additional fields can be made available and potentially set to be required fields for newly added objects.",
+        "alt_no_schemas_explica": "Alternative numbers for objects can be recorded on the object page's base tab. The category for such numbers are not a controlled list. But, depending on the type of alternative number, it might be fruitful to provide additional context information on this type of number. If a number schema set here has the exact same category name as has been entered for an object, the explanation will be provided in a tooltip when hovering over the alternative number on published object pages. Additionally, HTML5 validation patterns can be selected to ensure a consistent form for the recording of the given category of alternative object numbers."
     }
 }

backend/es/sources.json

@@ -8,7 +8,7 @@
         "book": "Book",
         "phdthesis": "PhD thesis",
         "electronical": "Electronical",
-        "misc": "Miscelaneous",
+        "misc": "Miscellaneous",
         "author_creator": "Author \/ creator",
         "author_creator_explica": "The creator of the source. Type a name to select the author or creator. You can add multiple authors \/ creators for a work.",
         "title": "Title",

backend/es/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Failed to locate any sensor data for this space",
         "get_url_for_logging": "Get URL for logging",
         "object_addendum_space_explica": "Select a space from the list. To add a new space press the \"+\" button. To see a log of the objects previous whereabouts right click on the selection field..",
-        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?"
+        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?",
+        "sensor_data": "Sensor data"
     }
 }

backend/es/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Edged",
+        "layout_edged_explica": "Removes the rounded corners of visual elements that usually strongly feature them.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone is a color scheme designed to follow colors used in traditional Thai art. It was compiled by Pairoj Pittayamatee, and is the result of a ten year study about traditional color making and usage in Thai art history for his master's and doctoral degrees at Silpakorn University. (Wikipedia)",
+        "application_localstorage": "The selection of theme components is stored in the browser's local storage. As such, it will need to be re-applied if the browser cache is emptied.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized is a low-contrast color scheme optimized for readability and syntax-highlighting.",
+        "layout_main_aside_separated": "Separated sidebars",
+        "layout_main_aside_separated_explica": "Adds a more pronounced background color to the page and highlights sidebars and main page contents in separated boxes.",
+        "layout_submit_buttons_fullwidth": "Full width submit buttons ",
+        "layout_submit_buttons_fullwidth_explica": "Increases the width of submit buttons to the full width of the containing element.",
+        "layout_textareas_minimum_height": "Minimum height for text areas",
+        "layout_textareas_minimum_height_explica": "Sets a minimum height to textareas that automatically resize otherwise.",
+        "textareas_minimum_height": "Minimum height for text areas",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the red\/violet series, the red series and the achromatic series listed there.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the blueviolet series and the achromatic series listed there.",
+        "layout_icons_high_contrast": "High contrast icons",
+        "layout_icons_high_contrast_explica": "Removes the opacity setting from icons, so that they will be displayed in solid black \/ white colors.",
+        "layout_icons_large": "Increase icon size",
+        "layout_icons_large_explica": "Increases the icon size significantly. They are thus easier to see and click, but - importantly - are misaligned respective to the text. Use with caution."
+    }
+}

backend/es/user.json

@@ -180,6 +180,9 @@
         "instance_level_contact_explica": "Enabling this toggle will automatically activate your user profile and make your profile listed as an instance-wide contact person in the navigation.",
         "invite_date": "Invite date",
         "publish_user_profile": "Publish user profile",
-        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region)."
+        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region).",
+        "account_disabled": "Account disabled",
+        "generate_auth_token": "Generate auth token",
+        "invalidate_auth_token": "Invalidate & remove auth token"
     }
 }

backend/es/z_migration.json

@@ -0,0 +1,10 @@
+{
+    "z_migration": {
+        "pre_release_title": "Pre-release of musdb's upcoming UI rewrite",
+        "try_out_new_ui": "Try out the new UI",
+        "pre_release_intro": "For the last months we have been working on a complete rewrite of the musdb's user interface. While much remains essentially the same, the new UI aims to be much more streamlined and is based on an entirely different, more efficient architecture.",
+        "pre_release_intro2": "Some blog posts have already given previews to it. Now, we can release the new UI in a pre-alpha state: Quite some features are still missing from the old UI, but most regular workflows should already be supported in the new UI. Read more details about the current pre-release or try it out below. As usual, but especially now, any feedback is welcome!",
+        "read_blog_post": "Read blog post",
+        "pre_release_blog_post_link": "https:\/\/blog.museum-digital.org\/2026\/09\/30\/pre-release-of-musdbs-new-ui\/"
+    }
+}

backend/fr/action.json

@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way.",
+        "search_by_tag_inclusive": "Search objects linked to this tag or any of its subordinate tags.",
+        "search_by_tag_exclusive": "Search objects linked to exactly this tag (not those linked to any of its subordinate tags).",
+        "search_by_place_inclusive": "Search objects linked to this place or any of its subordinate places.",
+        "search_by_place_exclusive": "Search objects linked to exactly this place (not those linked to any of its subordinate places).",
+        "export_selection_directly": "Export selected entries directly",
+        "export_selection_directly_explica": "Exports the selected entities as they are displayed in the list. This export option will not contain any information that is not available in the overview. To trigger such an export, use the respective export functionalities (where available) or the API.",
+        "theming_explica": "musdb supports theming to a certain level. On the one hand, special layout adjustments can be loaded. On the other hand, alternative color schemes can be selected. Selecting multiple alternative layout components combines them."
     }
 }

backend/fr/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "No entity has been linked",
         "repeat": "Repeat",
         "repeat_explica": "Repeat the last content you entered in this same data field.",
-        "setup_missing": "Not set up yet"
+        "setup_missing": "Not set up yet",
+        "currently_configured": "Currently configured",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a programm. They thus allow programmers to build external applications on top of them.",
+        "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
+        "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday",
+        "no_title_selected": "No title selected",
+        "sensor_data": "Sensor data",
+        "translations": "Translations",
+        "places": "Places",
+        "actors": "Actors",
+        "times": "Times",
+        "sources": "Sources",
+        "edit_in_nodac": "Edit in nodac",
+        "title": "Title",
+        "vocabularies": "Vocabularies",
+        "ignore": "Ignore",
+        "url": "URL",
+        "is_capitalized": "Is",
+        "relevance": "Relevance",
+        "abort": "Abort",
+        "ids": "IDs",
+        "address": "Address",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/fr/data_history.json

@@ -99,6 +99,7 @@
         "querying_data_history": "Querying data history",
         "phone_number": "Phone number",
         "regular_space": "Regular location",
-        "acquisition": "Acquisition"
+        "acquisition": "Acquisition",
+        "webdav_gen_access_data": "Generate WebDAV access data"
     }
 }

backend/fr/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Type of document",
         "document_type_explica": "In what relation does the document stand towards the object?",
         "generate_inventory_number_explica": "Automatically generates the next inventory number based on your institution's inventory number scheme.",
-        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings."
+        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings.",
+        "pdf_publicinfo_explica": "A PDF displaying published or publishable data for the object in a presentable A4 template.",
+        "pdf_knorr_explica": "A PDF template following the Knorr format, still popular in parts of Germany.",
+        "pdf_a5simple_explica": "Default multilingual A5 PDF template.",
+        "pdf_fullobject_explica": "A multilingual PDF template that covers all recorded data on the object in a simple two-column layout.",
+        "pdf_kartya2_explica": "A5 PDF template prepared for Hungarian museums.",
+        "pdf_kartya3_explica": "A5 PDF template prepared for Hungarian museums.",
+        "object_object_links": "Object to object links",
+        "limit_search_to_selection_explica": "Further restricts the search query to return only the selected objects. The selection will thus be available for further processing via batch processing, analysis, and exports."
     },
     "ortart": [
         "",

backend/fr/object_basis.json

@@ -44,6 +44,7 @@
         "series_is_public": "Published series",
         "series_is_not_public": "Unpublished series",
         "series_is_public_explica": "If both the series and the object have been toggled public, the object will be publicly listed as part of the series.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventory number (padded numbers)"
     }
 }

backend/fr/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regular sending of reports",
         "edit_custom_reports": "Edit custom reports",
         "custom_reports_intro": "Using \"Custom report\" templates institutions can define their own exports in the form of CSV tables or HTML text documents.",
-        "hide_fields": "Hide data fields"
+        "hide_fields": "Hide data fields",
+        "add_new_custom_report_template": "Add new custom report template",
+        "custom_reports_see_lists_placeholders": "Click on a button to view the list of available placeholders",
+        "placeholders": "Placeholders",
+        "custom_report_target": "Target page",
+        "custom_report_target_explica": "The custom report will be available for the selected target page type. Placeholders may or may not be available for a given type of target page.",
+        "share_folder_share_link": "Via share link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Some functionalities of museum-digital's portals can be influenced by the institutions responsible for the respective content. Here the corresponding settings can be managed.",
+        "integrations_explica": "Some integration capabilities linking musdb with other programs are built-in with musdb. To actually use those integrations, musdb needs to be given access to the relevant other services on the levels of institutions and users. Note that these settings pertain to built-in integrations. Further integrations can be written using musdb's API.",
+        "webhooks_explica": "Webhooks are a simple mechanism for an application to let other applications respond to a given action in the source one. When a given action is executed, musdb's server will perform an HTTP query to a pre-defined URL in the background. Some context information on the performed action is provided in the POST-header (user data, the processed API call, and an optional secret to lock down the target script against unwarranted access). If you e.g. write a script that receives such an HTTP call upon the publication of objects, you can e.g. trigger the automatic posting of a the newly posted object record on your social media feed.",
+        "object_input_page_explica": "Here the object input page can configured. Additional fields can be made available and potentially set to be required fields for newly added objects.",
+        "alt_no_schemas_explica": "Alternative numbers for objects can be recorded on the object page's base tab. The category for such numbers are not a controlled list. But, depending on the type of alternative number, it might be fruitful to provide additional context information on this type of number. If a number schema set here has the exact same category name as has been entered for an object, the explanation will be provided in a tooltip when hovering over the alternative number on published object pages. Additionally, HTML5 validation patterns can be selected to ensure a consistent form for the recording of the given category of alternative object numbers."
     }
 }

backend/fr/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Failed to locate any sensor data for this space",
         "get_url_for_logging": "Get URL for logging",
         "object_addendum_space_explica": "Select a space from the list. To add a new space press the \"+\" button. To see a log of the objects previous whereabouts right click on the selection field..",
-        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?"
+        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?",
+        "sensor_data": "Sensor data"
     }
 }

backend/fr/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Edged",
+        "layout_edged_explica": "Removes the rounded corners of visual elements that usually strongly feature them.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone is a color scheme designed to follow colors used in traditional Thai art. It was compiled by Pairoj Pittayamatee, and is the result of a ten year study about traditional color making and usage in Thai art history for his master's and doctoral degrees at Silpakorn University. (Wikipedia)",
+        "application_localstorage": "The selection of theme components is stored in the browser's local storage. As such, it will need to be re-applied if the browser cache is emptied.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized is a low-contrast color scheme optimized for readability and syntax-highlighting.",
+        "layout_main_aside_separated": "Separated sidebars",
+        "layout_main_aside_separated_explica": "Adds a more pronounced background color to the page and highlights sidebars and main page contents in separated boxes.",
+        "layout_submit_buttons_fullwidth": "Full width submit buttons ",
+        "layout_submit_buttons_fullwidth_explica": "Increases the width of submit buttons to the full width of the containing element.",
+        "layout_textareas_minimum_height": "Minimum height for text areas",
+        "layout_textareas_minimum_height_explica": "Sets a minimum height to textareas that automatically resize otherwise.",
+        "textareas_minimum_height": "Minimum height for text areas",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the red\/violet series, the red series and the achromatic series listed there.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the blueviolet series and the achromatic series listed there.",
+        "layout_icons_high_contrast": "High contrast icons",
+        "layout_icons_high_contrast_explica": "Removes the opacity setting from icons, so that they will be displayed in solid black \/ white colors.",
+        "layout_icons_large": "Increase icon size",
+        "layout_icons_large_explica": "Increases the icon size significantly. They are thus easier to see and click, but - importantly - are misaligned respective to the text. Use with caution."
+    }
+}

backend/fr/user.json

@@ -180,6 +180,9 @@
         "instance_level_contact_explica": "Enabling this toggle will automatically activate your user profile and make your profile listed as an instance-wide contact person in the navigation.",
         "invite_date": "Invite date",
         "publish_user_profile": "Publish user profile",
-        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region)."
+        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region).",
+        "account_disabled": "Account disabled",
+        "generate_auth_token": "Generate auth token",
+        "invalidate_auth_token": "Invalidate & remove auth token"
     }
 }

backend/fr/z_migration.json

@@ -0,0 +1,10 @@
+{
+    "z_migration": {
+        "pre_release_title": "Pre-release of musdb's upcoming UI rewrite",
+        "try_out_new_ui": "Try out the new UI",
+        "pre_release_intro": "For the last months we have been working on a complete rewrite of the musdb's user interface. While much remains essentially the same, the new UI aims to be much more streamlined and is based on an entirely different, more efficient architecture.",
+        "pre_release_intro2": "Some blog posts have already given previews to it. Now, we can release the new UI in a pre-alpha state: Quite some features are still missing from the old UI, but most regular workflows should already be supported in the new UI. Read more details about the current pre-release or try it out below. As usual, but especially now, any feedback is welcome!",
+        "read_blog_post": "Read blog post",
+        "pre_release_blog_post_link": "https:\/\/blog.museum-digital.org\/2026\/09\/30\/pre-release-of-musdbs-new-ui\/"
+    }
+}

backend/hi/action.json

@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way.",
+        "search_by_tag_inclusive": "Search objects linked to this tag or any of its subordinate tags.",
+        "search_by_tag_exclusive": "Search objects linked to exactly this tag (not those linked to any of its subordinate tags).",
+        "search_by_place_inclusive": "Search objects linked to this place or any of its subordinate places.",
+        "search_by_place_exclusive": "Search objects linked to exactly this place (not those linked to any of its subordinate places).",
+        "export_selection_directly": "Export selected entries directly",
+        "export_selection_directly_explica": "Exports the selected entities as they are displayed in the list. This export option will not contain any information that is not available in the overview. To trigger such an export, use the respective export functionalities (where available) or the API.",
+        "theming_explica": "musdb supports theming to a certain level. On the one hand, special layout adjustments can be loaded. On the other hand, alternative color schemes can be selected. Selecting multiple alternative layout components combines them."
     }
 }

backend/hi/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "No entity has been linked",
         "repeat": "Repeat",
         "repeat_explica": "Repeat the last content you entered in this same data field.",
-        "setup_missing": "Not set up yet"
+        "setup_missing": "Not set up yet",
+        "currently_configured": "Currently configured",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a programm. They thus allow programmers to build external applications on top of them.",
+        "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
+        "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday",
+        "no_title_selected": "No title selected",
+        "sensor_data": "Sensor data",
+        "translations": "Translations",
+        "places": "Places",
+        "actors": "Actors",
+        "times": "Times",
+        "sources": "Sources",
+        "edit_in_nodac": "Edit in nodac",
+        "title": "Title",
+        "vocabularies": "Vocabularies",
+        "ignore": "Ignore",
+        "url": "URL",
+        "is_capitalized": "Is",
+        "relevance": "Relevance",
+        "abort": "Abort",
+        "ids": "IDs",
+        "address": "Address",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/hi/data_history.json

@@ -99,6 +99,7 @@
         "querying_data_history": "Querying data history",
         "phone_number": "Phone number",
         "regular_space": "Regular location",
-        "acquisition": "Acquisition"
+        "acquisition": "Acquisition",
+        "webdav_gen_access_data": "Generate WebDAV access data"
     }
 }

backend/hi/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Type of document",
         "document_type_explica": "In what relation does the document stand towards the object?",
         "generate_inventory_number_explica": "Automatically generates the next inventory number based on your institution's inventory number scheme.",
-        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings."
+        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings.",
+        "pdf_publicinfo_explica": "A PDF displaying published or publishable data for the object in a presentable A4 template.",
+        "pdf_knorr_explica": "A PDF template following the Knorr format, still popular in parts of Germany.",
+        "pdf_a5simple_explica": "Default multilingual A5 PDF template.",
+        "pdf_fullobject_explica": "A multilingual PDF template that covers all recorded data on the object in a simple two-column layout.",
+        "pdf_kartya2_explica": "A5 PDF template prepared for Hungarian museums.",
+        "pdf_kartya3_explica": "A5 PDF template prepared for Hungarian museums.",
+        "object_object_links": "Object to object links",
+        "limit_search_to_selection_explica": "Further restricts the search query to return only the selected objects. The selection will thus be available for further processing via batch processing, analysis, and exports."
     },
     "ortart": [
         "",

backend/hi/object_basis.json

@@ -44,6 +44,7 @@
         "series_is_public": "Published series",
         "series_is_not_public": "Unpublished series",
         "series_is_public_explica": "If both the series and the object have been toggled public, the object will be publicly listed as part of the series.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventory number (padded numbers)"
     }
 }

backend/hi/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regular sending of reports",
         "edit_custom_reports": "Edit custom reports",
         "custom_reports_intro": "Using \"Custom report\" templates institutions can define their own exports in the form of CSV tables or HTML text documents.",
-        "hide_fields": "Hide data fields"
+        "hide_fields": "Hide data fields",
+        "add_new_custom_report_template": "Add new custom report template",
+        "custom_reports_see_lists_placeholders": "Click on a button to view the list of available placeholders",
+        "placeholders": "Placeholders",
+        "custom_report_target": "Target page",
+        "custom_report_target_explica": "The custom report will be available for the selected target page type. Placeholders may or may not be available for a given type of target page.",
+        "share_folder_share_link": "Via share link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Some functionalities of museum-digital's portals can be influenced by the institutions responsible for the respective content. Here the corresponding settings can be managed.",
+        "integrations_explica": "Some integration capabilities linking musdb with other programs are built-in with musdb. To actually use those integrations, musdb needs to be given access to the relevant other services on the levels of institutions and users. Note that these settings pertain to built-in integrations. Further integrations can be written using musdb's API.",
+        "webhooks_explica": "Webhooks are a simple mechanism for an application to let other applications respond to a given action in the source one. When a given action is executed, musdb's server will perform an HTTP query to a pre-defined URL in the background. Some context information on the performed action is provided in the POST-header (user data, the processed API call, and an optional secret to lock down the target script against unwarranted access). If you e.g. write a script that receives such an HTTP call upon the publication of objects, you can e.g. trigger the automatic posting of a the newly posted object record on your social media feed.",
+        "object_input_page_explica": "Here the object input page can configured. Additional fields can be made available and potentially set to be required fields for newly added objects.",
+        "alt_no_schemas_explica": "Alternative numbers for objects can be recorded on the object page's base tab. The category for such numbers are not a controlled list. But, depending on the type of alternative number, it might be fruitful to provide additional context information on this type of number. If a number schema set here has the exact same category name as has been entered for an object, the explanation will be provided in a tooltip when hovering over the alternative number on published object pages. Additionally, HTML5 validation patterns can be selected to ensure a consistent form for the recording of the given category of alternative object numbers."
     }
 }

backend/hi/sources.json

@@ -8,7 +8,7 @@
         "book": "Book",
         "phdthesis": "PhD thesis",
         "electronical": "Electronic Resource",
-        "misc": "Miscelaneous",
+        "misc": "Miscellaneous",
         "author_creator": "Author\/Creator",
         "author_creator_explica": "The creator of the source. Type a name to select the author or creator. You can add multiple authors\/creators for a work",
         "title": "Title",

backend/hi/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Failed to locate any sensor data for this space",
         "get_url_for_logging": "Get URL for logging",
         "object_addendum_space_explica": "Select a space from the list. To add a new space press the \"+\" button. To see a log of the objects previous whereabouts right click on the selection field..",
-        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?"
+        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?",
+        "sensor_data": "Sensor data"
     }
 }

backend/hi/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Edged",
+        "layout_edged_explica": "Removes the rounded corners of visual elements that usually strongly feature them.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone is a color scheme designed to follow colors used in traditional Thai art. It was compiled by Pairoj Pittayamatee, and is the result of a ten year study about traditional color making and usage in Thai art history for his master's and doctoral degrees at Silpakorn University. (Wikipedia)",
+        "application_localstorage": "The selection of theme components is stored in the browser's local storage. As such, it will need to be re-applied if the browser cache is emptied.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized is a low-contrast color scheme optimized for readability and syntax-highlighting.",
+        "layout_main_aside_separated": "Separated sidebars",
+        "layout_main_aside_separated_explica": "Adds a more pronounced background color to the page and highlights sidebars and main page contents in separated boxes.",
+        "layout_submit_buttons_fullwidth": "Full width submit buttons ",
+        "layout_submit_buttons_fullwidth_explica": "Increases the width of submit buttons to the full width of the containing element.",
+        "layout_textareas_minimum_height": "Minimum height for text areas",
+        "layout_textareas_minimum_height_explica": "Sets a minimum height to textareas that automatically resize otherwise.",
+        "textareas_minimum_height": "Minimum height for text areas",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the red\/violet series, the red series and the achromatic series listed there.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the blueviolet series and the achromatic series listed there.",
+        "layout_icons_high_contrast": "High contrast icons",
+        "layout_icons_high_contrast_explica": "Removes the opacity setting from icons, so that they will be displayed in solid black \/ white colors.",
+        "layout_icons_large": "Increase icon size",
+        "layout_icons_large_explica": "Increases the icon size significantly. They are thus easier to see and click, but - importantly - are misaligned respective to the text. Use with caution."
+    }
+}

backend/hi/user.json

@@ -180,6 +180,9 @@
         "instance_level_contact_explica": "Enabling this toggle will automatically activate your user profile and make your profile listed as an instance-wide contact person in the navigation.",
         "invite_date": "Invite date",
         "publish_user_profile": "Publish user profile",
-        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region)."
+        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region).",
+        "account_disabled": "Account disabled",
+        "generate_auth_token": "Generate auth token",
+        "invalidate_auth_token": "Invalidate & remove auth token"
     }
 }

backend/hi/z_migration.json

@@ -0,0 +1,10 @@
+{
+    "z_migration": {
+        "pre_release_title": "Pre-release of musdb's upcoming UI rewrite",
+        "try_out_new_ui": "Try out the new UI",
+        "pre_release_intro": "For the last months we have been working on a complete rewrite of the musdb's user interface. While much remains essentially the same, the new UI aims to be much more streamlined and is based on an entirely different, more efficient architecture.",
+        "pre_release_intro2": "Some blog posts have already given previews to it. Now, we can release the new UI in a pre-alpha state: Quite some features are still missing from the old UI, but most regular workflows should already be supported in the new UI. Read more details about the current pre-release or try it out below. As usual, but especially now, any feedback is welcome!",
+        "read_blog_post": "Read blog post",
+        "pre_release_blog_post_link": "https:\/\/blog.museum-digital.org\/2026\/09\/30\/pre-release-of-musdbs-new-ui\/"
+    }
+}

backend/hsb/action.json

@@ -125,6 +125,15 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way.",
+        "search_by_tag_inclusive": "Search objects linked to this tag or any of its subordinate tags.",
+        "search_by_tag_exclusive": "Search objects linked to exactly this tag (not those linked to any of its subordinate tags).",
+        "search_by_place_inclusive": "Search objects linked to this place or any of its subordinate places.",
+        "search_by_place_exclusive": "Search objects linked to exactly this place (not those linked to any of its subordinate places).",
+        "export_selection_directly": "Export selected entries directly",
+        "export_selection_directly_explica": "Exports the selected entities as they are displayed in the list. This export option will not contain any information that is not available in the overview. To trigger such an export, use the respective export functionalities (where available) or the API.",
+        "theming_explica": "musdb supports theming to a certain level. On the one hand, special layout adjustments can be loaded. On the other hand, alternative color schemes can be selected. Selecting multiple alternative layout components combines them."
     }
 }

backend/hsb/basis.json

@@ -418,6 +418,44 @@
         "no_linked_entity": "No entity has been linked",
         "repeat": "Repeat",
         "repeat_explica": "Repeat the last content you entered in this same data field.",
-        "setup_missing": "Not set up yet"
+        "setup_missing": "Not set up yet",
+        "currently_configured": "Currently configured",
+        "format": "Format",
+        "use_case": "Use case",
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a programm. They thus allow programmers to build external applications on top of them.",
+        "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
+        "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
+        "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday",
+        "no_title_selected": "No title selected",
+        "sensor_data": "Sensor data",
+        "translations": "Translations",
+        "places": "Places",
+        "actors": "Actors",
+        "times": "Times",
+        "sources": "Sources",
+        "edit_in_nodac": "Edit in nodac",
+        "title": "Title",
+        "vocabularies": "Vocabularies",
+        "ignore": "Ignore",
+        "url": "URL",
+        "is_capitalized": "Is",
+        "relevance": "Relevance",
+        "abort": "Abort",
+        "ids": "IDs",
+        "address": "Address",
+        "label": "Label",
+        "optional": "Optional",
+        "optional_inline": "optional",
+        "theming": "Theming",
+        "layout": "Layout",
+        "credits": "Credits"
     }
 }

backend/hsb/data_history.json

@@ -99,6 +99,7 @@
         "querying_data_history": "Querying data history",
         "phone_number": "Phone number",
         "regular_space": "Regular location",
-        "acquisition": "Acquisition"
+        "acquisition": "Acquisition",
+        "webdav_gen_access_data": "Generate WebDAV access data"
     }
 }

backend/hsb/object_addendum.json

@@ -394,7 +394,15 @@
         "document_type": "Type of document",
         "document_type_explica": "In what relation does the document stand towards the object?",
         "generate_inventory_number_explica": "Automatically generates the next inventory number based on your institution's inventory number scheme.",
-        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings."
+        "no_inventory_number_scheme_set": "Your institution has not yet defined an inventory number scheme. You can do so in the institution-level settings.",
+        "pdf_publicinfo_explica": "A PDF displaying published or publishable data for the object in a presentable A4 template.",
+        "pdf_knorr_explica": "A PDF template following the Knorr format, still popular in parts of Germany.",
+        "pdf_a5simple_explica": "Default multilingual A5 PDF template.",
+        "pdf_fullobject_explica": "A multilingual PDF template that covers all recorded data on the object in a simple two-column layout.",
+        "pdf_kartya2_explica": "A5 PDF template prepared for Hungarian museums.",
+        "pdf_kartya3_explica": "A5 PDF template prepared for Hungarian museums.",
+        "object_object_links": "Object to object links",
+        "limit_search_to_selection_explica": "Further restricts the search query to return only the selected objects. The selection will thus be available for further processing via batch processing, analysis, and exports."
     },
     "ortart": [
         "",

backend/hsb/object_basis.json

@@ -44,6 +44,7 @@
         "series_is_public": "Published series",
         "series_is_not_public": "Unpublished series",
         "series_is_public_explica": "If both the series and the object have been toggled public, the object will be publicly listed as part of the series.",
-        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record."
+        "puqi_explica": "The publication quality index evaluates the existence and completeness of an object record's publishable data. Based on this evaluation, hints are provided and a numeric score is computed to quickly summarize the quality of a record.",
+        "inventory_number_numbers_padded": "Inventory number (padded numbers)"
     }
 }

backend/hsb/settings.json

@@ -141,6 +141,18 @@
         "timed_sending_reports": "Regular sending of reports",
         "edit_custom_reports": "Edit custom reports",
         "custom_reports_intro": "Using \"Custom report\" templates institutions can define their own exports in the form of CSV tables or HTML text documents.",
-        "hide_fields": "Hide data fields"
+        "hide_fields": "Hide data fields",
+        "add_new_custom_report_template": "Add new custom report template",
+        "custom_reports_see_lists_placeholders": "Click on a button to view the list of available placeholders",
+        "placeholders": "Placeholders",
+        "custom_report_target": "Target page",
+        "custom_report_target_explica": "The custom report will be available for the selected target page type. Placeholders may or may not be available for a given type of target page.",
+        "share_folder_share_link": "Via share link",
+        "webhooks": "Webhooks",
+        "frontend_settings_intro": "Some functionalities of museum-digital's portals can be influenced by the institutions responsible for the respective content. Here the corresponding settings can be managed.",
+        "integrations_explica": "Some integration capabilities linking musdb with other programs are built-in with musdb. To actually use those integrations, musdb needs to be given access to the relevant other services on the levels of institutions and users. Note that these settings pertain to built-in integrations. Further integrations can be written using musdb's API.",
+        "webhooks_explica": "Webhooks are a simple mechanism for an application to let other applications respond to a given action in the source one. When a given action is executed, musdb's server will perform an HTTP query to a pre-defined URL in the background. Some context information on the performed action is provided in the POST-header (user data, the processed API call, and an optional secret to lock down the target script against unwarranted access). If you e.g. write a script that receives such an HTTP call upon the publication of objects, you can e.g. trigger the automatic posting of a the newly posted object record on your social media feed.",
+        "object_input_page_explica": "Here the object input page can configured. Additional fields can be made available and potentially set to be required fields for newly added objects.",
+        "alt_no_schemas_explica": "Alternative numbers for objects can be recorded on the object page's base tab. The category for such numbers are not a controlled list. But, depending on the type of alternative number, it might be fruitful to provide additional context information on this type of number. If a number schema set here has the exact same category name as has been entered for an object, the explanation will be provided in a tooltip when hovering over the alternative number on published object pages. Additionally, HTML5 validation patterns can be selected to ensure a consistent form for the recording of the given category of alternative object numbers."
     }
 }

backend/hsb/sources.json

@@ -8,7 +8,7 @@
         "book": "Buch",
         "phdthesis": "Doktorarbeit",
         "electronical": "Elektronische Resource",
-        "misc": "Weiteres",
+        "misc": "Miscellaneous",
         "author_creator": "Autor \/ Erschaffer",
         "author_creator_explica": "Der Sch\u00f6pfer einer Quelle. Geben Sie einen Namen ein um einen Autor oder Sch\u00f6pfer auszuw\u00e4hlen. Sie k\u00f6nnen zu einem Werk mehrere Autoren oder Sch\u00f6pfer eingeben.",
         "title": "Titel",

backend/hsb/spaces.json

@@ -18,6 +18,7 @@
         "no_sensor_data": "Failed to locate any sensor data for this space",
         "get_url_for_logging": "Get URL for logging",
         "object_addendum_space_explica": "Select a space from the list. To add a new space press the \"+\" button. To see a log of the objects previous whereabouts right click on the selection field..",
-        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?"
+        "set_current_space_as_subordinate": "Set the current space as subordinate to the selected one?",
+        "sensor_data": "Sensor data"
     }
 }

backend/hsb/theming.json

@@ -0,0 +1,26 @@
+{
+    "theming": {
+        "layout_edged": "Edged",
+        "layout_edged_explica": "Removes the rounded corners of visual elements that usually strongly feature them.",
+        "colors_thaitone": "ThaiTone",
+        "colors_thaitone_explica": "Thaitone is a color scheme designed to follow colors used in traditional Thai art. It was compiled by Pairoj Pittayamatee, and is the result of a ten year study about traditional color making and usage in Thai art history for his master's and doctoral degrees at Silpakorn University. (Wikipedia)",
+        "application_localstorage": "The selection of theme components is stored in the browser's local storage. As such, it will need to be re-applied if the browser cache is emptied.",
+        "colors_solarized": "Solarized",
+        "colors_solarized_explica": "Solarized is a low-contrast color scheme optimized for readability and syntax-highlighting.",
+        "layout_main_aside_separated": "Separated sidebars",
+        "layout_main_aside_separated_explica": "Adds a more pronounced background color to the page and highlights sidebars and main page contents in separated boxes.",
+        "layout_submit_buttons_fullwidth": "Full width submit buttons ",
+        "layout_submit_buttons_fullwidth_explica": "Increases the width of submit buttons to the full width of the containing element.",
+        "layout_textareas_minimum_height": "Minimum height for text areas",
+        "layout_textareas_minimum_height_explica": "Sets a minimum height to textareas that automatically resize otherwise.",
+        "textareas_minimum_height": "Minimum height for text areas",
+        "colors_tradjpn_redviolet": "Traditional colors of Japan: red\/violet series",
+        "colors_tradjpn_redviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the red\/violet series, the red series and the achromatic series listed there.",
+        "colors_tradjpn_blueviolet": "Traditional colors of Japan: blue\/violet series",
+        "colors_tradjpn_blueviolet_explica": "Color scheme based on Wikipedia's list of traditional Japanese colors. Combines the blueviolet series and the achromatic series listed there.",
+        "layout_icons_high_contrast": "High contrast icons",
+        "layout_icons_high_contrast_explica": "Removes the opacity setting from icons, so that they will be displayed in solid black \/ white colors.",
+        "layout_icons_large": "Increase icon size",
+        "layout_icons_large_explica": "Increases the icon size significantly. They are thus easier to see and click, but - importantly - are misaligned respective to the text. Use with caution."
+    }
+}

backend/hsb/user.json

@@ -180,6 +180,9 @@
         "instance_level_contact_explica": "Enabling this toggle will automatically activate your user profile and make your profile listed as an instance-wide contact person in the navigation.",
         "invite_date": "Invite date",
         "publish_user_profile": "Publish user profile",
-        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region)."
+        "publish_user_profile_explica": "If you publish your user profile, it will be visible to other users of the same instance of musdb (commonly your institution and other museum workers in your region).",
+        "account_disabled": "Account disabled",
+        "generate_auth_token": "Generate auth token",
+        "invalidate_auth_token": "Invalidate & remove auth token"
     }
 }