Approval in backend

backend/ar/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/de/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/dsb/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/hu/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/id/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/it/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/iw/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/kn/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/nl/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/pl/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/pt/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/ro/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/ru/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/ta/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/te/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/tl/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/tr/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/uk/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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/zh/settings.json

@@ -148,6 +148,11 @@
         "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"
+        "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."
     }
 }