Approval in backend

backend/ar/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/ar/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/ar/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/ar/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/ar/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/de/basis.json

@@ -302,6 +302,10 @@
         "all": "Alle",
         "content": "Inhalt",
         "unit": "Einheit",
-        "versioning": "Versionierung"
+        "versioning": "Versionierung",
+        "autogenerate": "Autogenerieren",
+        "suggestions": "Vorschl\u00e4ge",
+        "generated_by": "Generiert von",
+        "formulate_automatically": "Automatisch formulieren"
     }
 }

backend/de/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Hier kann man das Verschenken eines Objektes vermerken",
         "50": "Hier kann man das Vererben eines Objektes von einem Eigent\u00fcmer an einen Anderen vermerken",
         "51": "Haupts\u00e4chlich f\u00fcr Schriftgut. Beschreibt den zentralen Gegenstand des Objektes (z.B. des Textes). Eine Stadt w\u00e4re etwa Hauptgegenstand ihrer   Gr\u00fcndungsurkunde.",
-        "52": "F\u00fcr anorganische Objekte die nicht von Menschenhand entstanden sind. Etwa unbearbeitete Steine."
+        "52": "F\u00fcr anorganische Objekte die nicht von Menschenhand entstanden sind. Etwa unbearbeitete Steine.",
+        "53": "Besteht ein Objekt aus verschiedenen Materialien, kann die Herstellung dieser hier vermerkt werden.",
+        "54": "Bitte verwenden, wenn Objekt z.B. ein Brief oder Dokument ist und darin ein Ort erw\u00e4hnt wird.",
+        "55": "Bitte verwenden, wenn Objekt z.B. ein Brief oder Dokument ist und darin eine Zeit prominent erw\u00e4hnt wird.",
+        "56": "Kann zum Vermerken eines bekannten, aber unbestimmten, Transfers des Eigentumstitels \u00fcber das Objekt genutzt werden (wenn etwa nicht bekannt ist, ob das Objekt verschenkt oder verkauft wurde)",
+        "57": "Kann zum Vermerken eines bekannten, aber unbestimmten, Transfers des Eigentumstitels \u00fcber das Objekt genutzt werden (wenn etwa nicht bekannt ist, ob das Objekt verschenkt oder verkauft wurde)"
     }
 }

backend/de/object.json

@@ -136,6 +136,6 @@
         "all_exhibitions": "Alle Ausstellungen",
         "assign_tag": "Schlagwort zuordnen",
         "visibility_explica": "Publiziert bzw. versteckt das Objekt. Nur Objekte, die mindestens eine verkn\u00fcpfte Abbildung und eine Beschreibung von mindestens 25 Buchstaben L\u00e4nge haben, k\u00f6nnen ver\u00f6ffentlicht werden.",
-        "batch_transfer": "Adat\u00e1tvitel"
+        "batch_transfer": "Feldinhalte \u00fcbertragen"
     }
 }

backend/de/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Inventarnummer generieren",
         "transfer_invno_suggestion": "Vorschlag f\u00fcr Inventarnummer transferieren",
         "scan_inventory_number": "Inventarnummer scannen",
-        "main_measurement_types": "Basis-Ma\u00dfe"
+        "main_measurement_types": "Basis-Ma\u00dfe",
+        "can_be_published": "Kann ver\u00f6ffentlicht werden",
+        "generating_description_take_time": "Beschreibung wird generiert. Dies kann einige Sekunden dauern. Zeit: ",
+        "click_to_select_suggestion": "Klicken, um einen vollen Vorschlag zu lesen. Noch einmal auf den Text klicken, um ihn auszuw\u00e4hlen. In der Folge k\u00f6nnen weitere Bearbeitungen gemacht werden.",
+        "display_prompt": "Prompt anzeigen",
+        "redact_ai_generated_desc": "KI-generierte Objektbeschreibung redigieren",
+        "suggest_desc_by_ai_explica": "Nutze anderweitige Metadaten, um mithilfe von Large Language Models Formulierungsvorschl\u00e4ge f\u00fcr die Objektbeschreibung zu generieren.",
+        "custom_object_page": "Benutzerdefinierte Objekt-Seite",
+        "toggle_custom_object_page_explica": "Aktiviert oder deaktiviert die benutzerdefinierte Ansicht der Objektbearbeitungsseite. Die benutzerdefinierte Ansicht arbeitet im Gegensatz zum herk\u00f6mmlichen, Reiter-basierten Design mit einem voll einstellbaren, Widget-basierten Design.",
+        "caching_suggestions_for_object_descriptions": "Vorschl\u00e4ge f\u00fcr Objektbeschreibungen zwischenspeichern",
+        "pregenerate_suggestions_for_object_descriptions": "Vorgenerieren von Vorschl\u00e4gen f\u00fcr Objektbeschreibungen",
+        "generating_description_requires_tag_event": "Bitte beachten: Damit eine Objektbeschreibung generiert werden kann, m\u00fcssen zum Objekt mindestens ein Schlagwort und ein Ereignis vorliegen.",
+        "disposal_recipient": "Empf\u00e4nger (Deakzession)",
+        "disposal_recipient_explica": "Empf\u00e4nger des deakzessionierten Objektes. Wurde das Objekt an ein anderes Museum weitergegeben, k\u00f6nnte dieses hier angegeben werden. Wurde es vernichtet, k\u00f6nnte die daf\u00fcr zust\u00e4ndige Firma hier angegeben werden."
     },
     "ortart": [
         "",

backend/de/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Begrenze die Schlagworte, die als Material verwendet werden d\u00fcrfen durch Angabe von IDs",
         "limit_tags_for_materials_by_id_explica": "Nach ungarischem Gesetz m\u00fcssen Sammlungsmanagementsysteme den Museen erlauben Materialarten aus einer \"museumsspezifischen\" Liste von Werten auszuw\u00e4hlen. musdb arbeitet im Allgemeinen mit gemeinsam genutzten kontrollierten (statt museumsspezifischen) Vokabularen - was ja eine seiner gr\u00f6\u00dften St\u00e4rken ist.\r\nUm dennoch den Erfordernissen des genannten Gesetzes gerecht zu werden, k\u00f6nnen Museen dieses Eingabelfeld nutzen um IDs einzutragen, f\u00fcr Begriffe, die als Materialart erlaubt sind. Beispielsweise \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Begrenze die Schlagworte, die als Technik verwendet werden d\u00fcrfen durch Angabe von IDs",
-        "limit_tags_for_techniques_by_id_explica": "Nach ungarischem Gesetz m\u00fcssen Sammlungsmanagementsysteme den Museen erlauben Techniken aus einer \"museumsspezifischen\" Liste von Werten auszuw\u00e4hlen. musdb arbeitet im Allgemeinen mit gemeinsam genutzten kontrollierten (statt museumsspezifischen) Vokabularen - was ja eine seiner gr\u00f6\u00dften St\u00e4rken ist.\r\nUm dennoch den Erfordernissen des genannten Gesetzes gerecht zu werden, k\u00f6nnen Museen dieses Eingabelfeld nutzen um IDs einzutragen, f\u00fcr Begriffe, die als Technik erlaubt sind. Beispielsweise \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "Nach ungarischem Gesetz m\u00fcssen Sammlungsmanagementsysteme den Museen erlauben Techniken aus einer \"museumsspezifischen\" Liste von Werten auszuw\u00e4hlen. musdb arbeitet im Allgemeinen mit gemeinsam genutzten kontrollierten (statt museumsspezifischen) Vokabularen - was ja eine seiner gr\u00f6\u00dften St\u00e4rken ist.\r\nUm dennoch den Erfordernissen des genannten Gesetzes gerecht zu werden, k\u00f6nnen Museen dieses Eingabelfeld nutzen um IDs einzutragen, f\u00fcr Begriffe, die als Technik erlaubt sind. Beispielsweise \"1,21,521\"",
+        "object_citation_guide": "Hinweise zum Zitieren von Objekten",
+        "explica_object_citation_guide": "Ist dieses Feld nicht leer, wird sein Inhalt als zus\u00e4tzliche Notiz im \"Zitieren\"-Overlay der \u00f6ffentlichen Objektseiten angezeigt. So kann festgehalten werden, wie die Objekte selbst (im Gegensatz zum Datensatz) zitiert werden sollten.",
+        "object_citation_guide_text": "Hinweise und Vorschl\u00e4ge zum Zitieren von Objekten, die Nutzern auf \u00f6ffentlichen Objektseiten angezeigt werden sollen.",
+        "hide_duplicate_fields": "Doppelte Felder verstecken",
+        "explica_hide_duplicate_fields": "Mit den Jahren sind f\u00fcr einige Aufgaben konkurrienrende Felder in musdb implementiert worden - einmal als Freitextfeld, einmal als Verkn\u00fcpfung mit einem dedizierten Datentyp. Z.B. lassen sich Standorte \u00fcber Freitextfelder auf dem Reiter \"Verbleib\" der Objektseite eintragen. Oder direkt daneben als Bezug auf das R\u00e4ume-Modul. Letzterre Option bietet verbessertes Logging, deutlich bessere Suchoptionen, etc. Die neueren Verkn\u00fcpfungsoptionen sind daher f\u00fcr ein effektives Arbeiten in musdb unbedingt zu bevorzugen.\r\n\r\nUm Verwirrung ob der doppelten Felder zu reduzieren, lassen sich die \u00e4lteren Freitextfelder hier verstecken.",
+        "hide_free_text_object_location": "Freitextfelder f\u00fcr Standort von Objekten verstecken",
+        "hide_free_text_object_location_explica": "Versteckt die Freitextfelder f\u00fcr den Standort eines Objektes. Stattdessen kann der Standort \u00fcber Verkn\u00fcpfungen zu R\u00e4umen festgehalten werden. Auf diese Weise erh\u00e4lt man verbesserte Suchm\u00f6glichkeiten, ein detailliertes Log der Standortverschiebungen, sowie die M\u00f6glichkeit, die Objektdaten mit Sensordaten f\u00fcr die Klimamessung zusammenzuf\u00fchren.",
+        "hide_free_text_object_exhibitions": "Freitextfelder f\u00fcr Ausstellungen von Objekten verstecken",
+        "hide_free_text_object_exhibitions_explica": "Ausstellungen k\u00f6nnen mit Objekten entweder \u00fcber das Freitextfeld auf dem Reiter \"Verbleib\" oder \u00fcber den eigenen Reiter \"Ausstellung\" verkn\u00fcpft werden. Werden sie \u00fcber den eigenen Reiter mit Ausstellungen aus dem Ausstellungsmodul verkn\u00fcpft, ergeben sich verbesserte Suchm\u00f6glichkeiten (z.B.: \"Objekte, die gerade ausgestellt sind\").",
+        "hide_free_text_object_loans": "Freitextfelder f\u00fcr Leihverkehre von Objekten verstecken",
+        "hide_free_text_object_loans_explica": "Leihvorg\u00e4nge k\u00f6nnen mit Objekten entweder \u00fcber das Freitextfeld auf dem Reiter \"Verbleib\" oder \u00fcber den eigenen Reiter \"Leihverkehr\" verkn\u00fcpft werden. Werden sie \u00fcber den eigenen Reiter mit Leihverkehren aus dem Leihverkehrsmodul verkn\u00fcpft, ergeben sich verbesserte Suchm\u00f6glichkeiten (z.B.: \"Objekte, die gerade verliehen sind\").",
+        "hide_free_text_object_entry": "Freitextfelder f\u00fcr Zugang von Objekten verstecken",
+        "hide_free_text_object_entry_explica": "Auf dem Reiter \"Verwaltung\" der Objektbearbeitungsseite finden sich eine Reihe von Freitextfeldern, mit denen sich der Zugang eines Objekets erfassen l\u00e4sst: Vorbesitzer, Art des Zugangs, etc. Alternativ dazu kann das Objekt mit einem Erwerbungsvorgang verkn\u00fcpft werden. Geschieht Letzteres, k\u00f6nnen \u00fcber das Kontakt-Modul z.B. die Kontaktdaten des Vorbesitzers als Vorschau eingebunden werden.\r\nDes Weiteren entsteht bei der blo\u00dfen Erfassung \u00fcber Freitextfelder ggfs. ein logisches Problem im Falle von Konvolutank\u00e4ufen. Hier ist kein eindeutiger Ankaufspreis pro Objekt ermittelbar, da mehrere Objekte zusammen gekauft wurden. Auch das l\u00e4sst sich nur \u00fcber das Erwerbungsmodul sinnvoll abbilden.",
+        "enforce_custom_object_page": "Verpflichtende benutzerspezifische Objektbearbeitungsmaske",
+        "explica_enforce_custom_object_page": "Macht die Benutzung der benutzerspezifisch angepassten Objektbearbeitungsmaske f\u00fcr alle Nutzer des Museums verpflichtend. Die regul\u00e4re, tab-basierte Anzeige ist damit nicht mehr verf\u00fcgbar."
     }
 }

backend/de/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Zugang zu Statements",
         "disable_adding_to_vocabs": "Neuanlegen in Vokabularen verbieten",
         "disable_adding_to_vocabs_explica": "Falls dieser Schalter aktiviert ist, ist es dem Benutzer nicht mehr m\u00f6glich neue Vokabulareintr\u00e4ge anzulegen. Bestehende k\u00f6nnen weiterhin verkn\u00fcpft werden. So k\u00f6nnen Kollegen die regelm\u00e4\u00dfig und trotz Belehrung falsche oder den Regeln widersprechende Vokabulareintr\u00e4ge generieren davon abgehalten werden.",
-        "remove_remember_me_tokens": "Entferne \"erinnerte\" Logins auf anderen Ger\u00e4ten (erzwinge erneutes Login)"
+        "remove_remember_me_tokens": "Entferne \"erinnerte\" Logins auf anderen Ger\u00e4ten (erzwinge erneutes Login)",
+        "disallow_publishing_objects": "Ver\u00f6ffentlichen von Objekten verbieten",
+        "disallow_publishing_objects_explica": "Verhindert, dass der oder die Benutzer\/in Objekte ver\u00f6ffentlichen kann. Dies kann eingesetzt werden, falls der oder die Benutzerin wiederholt und entgegen vorheriger Absprachen schlecht erfasste Objektdaten publiziert."
     }
 }

backend/dsb/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/dsb/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/dsb/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/dsb/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/dsb/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/en/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/en/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/en/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/en/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/en/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/es/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/es/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/es/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/es/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/es/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/fr/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/fr/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/fr/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/fr/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/fr/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/hsb/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/hsb/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/hsb/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/hsb/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/hsb/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/hu/basis.json

@@ -302,6 +302,10 @@
         "all": "\u00d6sszes",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Verzi\u00f3kezel\u00e9s"
+        "versioning": "Verzi\u00f3kezel\u00e9s",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/hu/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Itt lehet megadni, hogy a t\u00e1rgyat \"mikor?\", \"hol?\" \u00e9s \"ki?\" adom\u00e1nyozta.",
         "50": "Itt lehet megadni, hogy a t\u00e1rgyat \"mikor?\", \"hol?\" \u00e9s \"ki?\" \u00f6r\u00f6k\u00f6lte.",
         "51": "Els\u0151sorban dokumentumok \u00e9s sz\u00f6veg alap\u00fa t\u00e1rgyak t\u00e9mak\u00f6r\u00e9nek a megad\u00e1s\u00e1hoz javasoljuk. Ezzel az esem\u00e9nyt\u00edpussal egy m\u0171t\u00e1rgy k\u00f6zponti t\u00e9m\u00e1j\u00e1t lehets\u00e9ges megadni. Pl. egy v\u00e1ros alap\u00edt\u00f3 okirat\u00e1nak t\u00e9m\u00e1ja a telep\u00fcl\u00e9s neve.",
-        "52": "Ez az esem\u00e9ny\u00edtpus a term\u00e9szetben l\u00e9terj\u00f6tt t\u00e1rgyak keletkez\u00e9s\u00e9nek  a\"hol?\" \u00e9s \"mikor?\" adatainak a r\u00f6gz\u00edt\u00e9s\u00e9re alkalmas. (pl. \u00e1sv\u00e1nytani gy\u0171jtem\u00e9nyek eset\u00e9n)"
+        "52": "Ez az esem\u00e9ny\u00edtpus a term\u00e9szetben l\u00e9terj\u00f6tt t\u00e1rgyak keletkez\u00e9s\u00e9nek  a\"hol?\" \u00e9s \"mikor?\" adatainak a r\u00f6gz\u00edt\u00e9s\u00e9re alkalmas. (pl. \u00e1sv\u00e1nytani gy\u0171jtem\u00e9nyek eset\u00e9n)",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/hu/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Lelt\u00e1ri sz\u00e1m gener\u00e1l\u00e1sa",
         "transfer_invno_suggestion": "Lelt\u00e1ri sz\u00e1m kioszt\u00e1sa",
         "scan_inventory_number": "Lelt\u00e1ri sz\u00e1m szkennel\u00e9se",
-        "main_measurement_types": "Alapvet\u0151 "
+        "main_measurement_types": "Alapvet\u0151 ",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/hu/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Korl\u00e1tozza az anyagk\u00e9nt hozz\u00e1adhat\u00f3 kulcszavakat ID alapj\u00e1n",
         "limit_tags_for_materials_by_id_explica": "A magyar rendeletek szerint a gy\u0171jtem\u00e9nykezel\u0151 rendszereknek lehet\u0151v\u00e9 kell tenni\u00fck, hogy a m\u00fazeumok saj\u00e1t kulcssz\u00f3list\u00e1b\u00f3l v\u00e1laszthassanak. A musdb \u00e1ltal\u00e1ban megosztott, kontroll\u00e1lt sz\u00f3k\u00e9szletekkel dolgozik \u2013 val\u00f3j\u00e1ban ez az egyik legnagyobb er\u0151ss\u00e9ge.\r\n\r\nAhhoz azonban, hogy megfeleljen a fent eml\u00edtett k\u00f6vetelm\u00e9nynek, a m\u00fazeumok haszn\u00e1lhatj\u00e1k ezt a mez\u0151t annak \u00e9rdek\u00e9ben, hogy egy vessz\u0151vel elv\u00e1lasztott list\u00e1ban feh\u00e9rlist\u00e1zz\u00e1k a kulcsszavaknak az azonos\u00edt\u00f3it (ID) P\u00e9ld\u00e1ul: \u201e1,21,521\u201d.",
         "limit_tags_for_techniques_by_id": "Korl\u00e1tozza a technikak\u00e9nt hozz\u00e1adhat\u00f3 kulcszavakat ID alapj\u00e1n",
-        "limit_tags_for_techniques_by_id_explica": "A magyar rendeletek szerint a gy\u0171jtem\u00e9nykezel\u0151 rendszereknek lehet\u0151v\u00e9 kell tenni\u00fck, hogy a m\u00fazeumok saj\u00e1t kulcssz\u00f3list\u00e1b\u00f3l v\u00e1laszthassanak. A musdb \u00e1ltal\u00e1ban megosztott, kontroll\u00e1lt sz\u00f3k\u00e9szletekkel dolgozik \u2013 val\u00f3j\u00e1ban ez az egyik legnagyobb er\u0151ss\u00e9ge.\r\n\r\nAhhoz azonban, hogy megfeleljen a fent eml\u00edtett k\u00f6vetelm\u00e9nynek, a m\u00fazeumok haszn\u00e1lhatj\u00e1k ezt a mez\u0151t annak \u00e9rdek\u00e9ben, hogy egy vessz\u0151vel elv\u00e1lasztott list\u00e1ban feh\u00e9rlist\u00e1zz\u00e1k a kulcsszavaknak az azonos\u00edt\u00f3it (ID) P\u00e9ld\u00e1ul: \u201e1,21,521\u201d."
+        "limit_tags_for_techniques_by_id_explica": "A magyar rendeletek szerint a gy\u0171jtem\u00e9nykezel\u0151 rendszereknek lehet\u0151v\u00e9 kell tenni\u00fck, hogy a m\u00fazeumok saj\u00e1t kulcssz\u00f3list\u00e1b\u00f3l v\u00e1laszthassanak. A musdb \u00e1ltal\u00e1ban megosztott, kontroll\u00e1lt sz\u00f3k\u00e9szletekkel dolgozik \u2013 val\u00f3j\u00e1ban ez az egyik legnagyobb er\u0151ss\u00e9ge.\r\n\r\nAhhoz azonban, hogy megfeleljen a fent eml\u00edtett k\u00f6vetelm\u00e9nynek, a m\u00fazeumok haszn\u00e1lhatj\u00e1k ezt a mez\u0151t annak \u00e9rdek\u00e9ben, hogy egy vessz\u0151vel elv\u00e1lasztott list\u00e1ban feh\u00e9rlist\u00e1zz\u00e1k a kulcsszavaknak az azonos\u00edt\u00f3it (ID) P\u00e9ld\u00e1ul: \u201e1,21,521\u201d.",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/hu/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "Ha enged\u00e9lyezve van, ez a felhaszn\u00e1l\u00f3i fi\u00f3k t\u00f6bb\u00e9 nem haszn\u00e1lhat\u00f3 \u00faj bejegyz\u00e9sek bevitel\u00e9re az ellen\u0151rz\u00f6tt sz\u00f3k\u00e9szletekbe. Ez hasznos lehet annak megakad\u00e1lyoz\u00e1s\u00e1ra, hogy a koll\u00e9g\u00e1k ism\u00e9telten rossz\/azonos\u00edthatatlan\/szab\u00e1lynak ellentmond\u00f3 sz\u00f3kincsbejegyz\u00e9seket adjanak be.",
-        "remove_remember_me_tokens": "\"Eml\u00e9kezz r\u00e1m\" elt\u00e1vol\u00edt\u00e1sa"
+        "remove_remember_me_tokens": "\"Eml\u00e9kezz r\u00e1m\" elt\u00e1vol\u00edt\u00e1sa",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/id/basis.json

@@ -41,7 +41,7 @@
         "already_known": "Telah terkenal",
         "back": "kembali",
         "found": "Ditemukan",
-        "or": "or",
+        "or": "atau",
         "literature": "Sastra",
         "weblink": "Tautan internet",
         "document": "Dokumen",
@@ -103,7 +103,7 @@
         "room": "Kamar",
         "image": "Gambaran",
         "menu_items": "Menu Items",
-        "backgrounds": "Backgrounds",
+        "backgrounds": "Latar belakang",
         "transcription": "Transkripsi",
         "record_language": "Bahasa terjemahan",
         "article": "Artikel",
@@ -116,7 +116,7 @@
         "notes": "Catatan",
         "preview": "Pratinjau",
         "restore_last": "Gunakan masukan terkini",
-        "reception": "Reception",
+        "reception": "Resepsi",
         "source": "Sumber",
         "fill_out_select_from_list": "Please type and select an entry from the drop-down list",
         "page_museumshowobject": "Tunjukkan benda",
@@ -135,48 +135,48 @@
         "podcasts": "Podcast",
         "podcast_episodes": "Episode podcast",
         "previous": "Previous",
-        "next": "Next",
-        "comparison": "Comparison",
+        "next": "Lanjut",
+        "comparison": "Pembandingan",
         "language": "Bahasa",
         "import": "Impor",
         "start": "Start",
         "controlled_vocabularies": "Kosakata",
         "own_last_edits": "Own last edits",
-        "contact": "Contact",
-        "uncertainty": "Uncertainty",
-        "certain": "Certain",
-        "uncertain": "Uncertain",
-        "unknown": "Unknown",
-        "discussions": "Discussions",
+        "contact": "Kontak",
+        "uncertainty": "Ketentuan",
+        "certain": "Tentu",
+        "uncertain": "Tidak tentu",
+        "unknown": "Tidak dikenal",
+        "discussions": "Diskusi",
         "improvement_suggestions": "Suggestions for improvement",
-        "search_term": "Search term",
-        "and": "and",
-        "not": "not",
+        "search_term": "Istilah pencarian",
+        "and": "dan",
+        "not": "tidak",
         "refine_search": "Refine search",
-        "exact": "Exact",
-        "greater_than": "Greater than",
-        "lower_than": "Lower than",
-        "empty": "Empty",
+        "exact": "Persis",
+        "greater_than": "Lebih dari",
+        "lower_than": "Kurang dari",
+        "empty": "Kosong",
         "submit_go": "Go",
-        "submit": "Submit",
-        "contributors": "Contributors",
+        "submit": "Kirim",
+        "contributors": "Kontributor",
         "link_a_tag": "Link a tag",
-        "add_new_tag": "Add a new tag",
-        "favorites": "Favorites",
-        "view": "View",
-        "qrcode": "QR Code",
-        "open_url": "Open URL",
+        "add_new_tag": "Tambahkan kata kunci baru",
+        "favorites": "Favorit",
+        "view": "Lihat",
+        "qrcode": "Kode QR",
+        "open_url": "Buka URL",
         "qrcode_scan": "Scan QR code",
         "user_interface": "User interface",
         "query_language": "Query language",
         "tab": "Tab",
-        "help_current_page": "Current page",
+        "help_current_page": "Halaman ini",
         "clear": "Clear",
         "status_thus_far": "Current status",
         "link_recently_used": "Link recently used entries",
         "published": "Published",
         "user": "User",
-        "subscribe": "Subscribe",
+        "subscribe": "Berlangganan",
         "appointment": "Event",
         "calendars": "Calendars",
         "now": "Now",
@@ -186,7 +186,7 @@
         "media_licenses": "Media licenses",
         "frontend": "Frontend",
         "research_questions": "Research questions",
-        "enabled": "Enabled",
+        "enabled": "Diaktifkan",
         "required": "Required",
         "space": "Space",
         "spaces": "Spaces",
@@ -195,14 +195,14 @@
         "free_text": "Free text",
         "temperature": "Temperature",
         "humidity": "Humidity",
-        "note": "Note",
-        "pages": "Pages",
+        "note": "Catatan",
+        "pages": "Halaman",
         "cancel": "Cancel",
         "status": "Status",
         "owner": "Owner",
         "process": "Process",
         "processes": "Processes",
-        "end": "End",
+        "end": "Akhir",
         "projects": "Projects",
         "tasks": "Tasks",
         "task": "Task",
@@ -212,7 +212,7 @@
         "completed_before": "Completed before",
         "current": "Current",
         "upcoming": "Upcoming",
-        "past": "Past",
+        "past": "Lalu",
         "unsubscribe": "Unsubscribe",
         "podcast": "Podcast",
         "context": "Context",
@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/id/data_history.json

@@ -85,15 +85,15 @@
         "move_to_space": "Updates current location",
         "object_object_link": "Object-to-object link",
         "external_id": "Updated an external ID",
-        "shipment": "Shipment",
+        "shipment": "Transpor",
         "visibility (addendum)": "Visibility (specific to field)",
         "museum": "Link with a museum",
-        "publication": "Publication",
-        "document": "Document",
-        "link_place": "Linked a place",
-        "link_time": "Linked a time",
-        "categorization": "Categorization",
-        "measurement": "Measurement",
-        "open_versioning": "Open versioning"
+        "publication": "Publikasi",
+        "document": "Dokumen",
+        "link_place": "Tempat ditautkan",
+        "link_time": "Waktu ditautkan",
+        "categorization": "Kategori",
+        "measurement": "Ukuran",
+        "open_versioning": "Buka sejarah versi"
     }
 }

backend/id/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/id/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/id/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/id/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/it/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/it/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/it/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/it/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/it/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/iw/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/iw/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/iw/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/iw/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/iw/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/kn/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/kn/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/kn/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/kn/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/kn/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/nl/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/nl/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/nl/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/nl/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/nl/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/pl/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/pl/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/pl/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/pl/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/pl/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/pt/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/pt/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/pt/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/pt/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/pt/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/ro/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/ro/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/ro/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/ro/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/ro/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/ru/basis.json

@@ -302,6 +302,10 @@
         "all": "\u0412\u0441\u0435",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/ru/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "\u0417\u0434\u0435\u0441\u044c \u0432\u044b \u043c\u043e\u0436\u0435\u0442\u0435 \u0437\u0430\u043f\u0438\u0441\u0430\u0442\u044c, \u043a\u043e\u0433\u0434\u0430 \u043f\u0440\u0435\u0434\u043c\u0435\u0442 \u0431\u044b\u043b \u043e\u0442\u0434\u0430\u043d \u0438 \u043a\u0442\u043e \u044d\u0442\u043e \u0441\u0434\u0435\u043b\u0430\u043b.",
         "50": "\u0417\u0434\u0435\u0441\u044c \u043c\u043e\u0436\u043d\u043e \u0437\u0430\u043f\u0438\u0441\u0430\u0442\u044c, \u043a\u043e\u0433\u0434\u0430 \u043e\u0431\u044a\u0435\u043a\u0442 \u0431\u044b\u043b \u043f\u0435\u0440\u0435\u0434\u0430\u043d \u043a\u043e\u043c\u0443-\u043b\u0438\u0431\u043e \u043f\u043e \u043d\u0430\u0441\u043b\u0435\u0434\u0441\u0442\u0432\u0443.",
         "51": "\u0412 \u043e\u0441\u043d\u043e\u0432\u043d\u043e\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u0442\u0441\u044f \u0434\u043b\u044f \u043f\u0438\u0441\u044c\u043c\u0435\u043d\u043d\u044b\u0445 \u0440\u0430\u0431\u043e\u0442. \u041e\u043f\u0438\u0441\u044b\u0432\u0430\u0435\u0442 \u0446\u0435\u043d\u0442\u0440\u0430\u043b\u044c\u043d\u0443\u044e \u0442\u0435\u043c\u0443 \u043e\u0431\u044a\u0435\u043a\u0442\u0430. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u0443\u0447\u0440\u0435\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u044b\u0439 \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442 \u0433\u043e\u0440\u043e\u0434\u0430 \u043c\u043e\u0436\u0435\u0442 \u0438\u043c\u0435\u0442\u044c \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0441\u0443\u0431\u044a\u0435\u043a\u0442\u0430 \u044d\u0442\u043e\u0442 \u0441\u0430\u043c\u044b\u0439 \u0433\u043e\u0440\u043e\u0434.",
-        "52": "\u0414\u043b\u044f \u043d\u0435\u043e\u0440\u0433\u0430\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u043e\u0431\u044a\u0435\u043a\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043d\u0435 \u0431\u044b\u043b\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u044b \u0447\u0435\u043b\u043e\u0432\u0435\u043a\u043e\u043c, \u0430 \u0432\u043e\u0437\u043d\u0438\u043a\u043b\u0438 \u0432 \u043f\u0440\u0438\u0440\u043e\u0434\u0435. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043a\u0430\u043c\u043d\u0438."
+        "52": "\u0414\u043b\u044f \u043d\u0435\u043e\u0440\u0433\u0430\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u043e\u0431\u044a\u0435\u043a\u0442\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043d\u0435 \u0431\u044b\u043b\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u044b \u0447\u0435\u043b\u043e\u0432\u0435\u043a\u043e\u043c, \u0430 \u0432\u043e\u0437\u043d\u0438\u043a\u043b\u0438 \u0432 \u043f\u0440\u0438\u0440\u043e\u0434\u0435. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043a\u0430\u043c\u043d\u0438.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/ru/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "\u0421\u0433\u0435\u043d\u0435\u0440\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u0438\u043d\u0432\u0435\u043d\u0442\u0430\u0440\u043d\u044b\u0439 \u043d\u043e\u043c\u0435\u0440",
         "transfer_invno_suggestion": "\u041f\u0440\u0435\u0434\u043b\u043e\u0436\u0435\u043d\u0438\u0435 \u043e \u043f\u0435\u0440\u0435\u043d\u043e\u0441\u0435 \u0438\u043d\u0432\u0435\u043d\u0442\u0430\u0440\u043d\u043e\u0433\u043e \u043d\u043e\u043c\u0435\u0440\u0430",
         "scan_inventory_number": "\u0421\u043a\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u0438\u043d\u0432\u0435\u043d\u0442\u0430\u0440\u043d\u043e\u0433\u043e \u043d\u043e\u043c\u0435\u0440\u0430",
-        "main_measurement_types": "\u041e\u0441\u043d\u043e\u0432\u043d\u044b\u0435 \u0442\u0438\u043f\u044b"
+        "main_measurement_types": "\u041e\u0441\u043d\u043e\u0432\u043d\u044b\u0435 \u0442\u0438\u043f\u044b",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/ru/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "\u041e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u0435 \u0442\u0435\u0433\u043e\u0432, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u0443\u0442 \u0431\u044b\u0442\u044c \u0441\u0432\u044f\u0437\u0430\u043d\u044b \u0441 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u0430\u043c\u0438, \u043f\u043e \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440\u0443",
         "limit_tags_for_materials_by_id_explica": "\u0421\u043e\u0433\u043b\u0430\u0441\u043d\u043e \u0432\u0435\u043d\u0433\u0435\u0440\u0441\u043a\u043e\u043c\u0443 \u0437\u0430\u043a\u043e\u043d\u043e\u0434\u0430\u0442\u0435\u043b\u044c\u0441\u0442\u0432\u0443, \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043a\u043e\u043b\u043b\u0435\u043a\u0446\u0438\u044f\u043c\u0438 \u0434\u043e\u043b\u0436\u043d\u044b \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0442\u044c \u043c\u0443\u0437\u0435\u044f\u043c \u0432\u044b\u0431\u0438\u0440\u0430\u0442\u044c \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u044b \u0438\u0437 \u0441\u043f\u0438\u0441\u043a\u0430 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0439, \u0445\u0430\u0440\u0430\u043a\u0442\u0435\u0440\u043d\u044b\u0445 \u0434\u043b\u044f \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0433\u043e \u043c\u0443\u0437\u0435\u044f. musdb \u043e\u0431\u044b\u0447\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u0441 \u043e\u0431\u0449\u0438\u043c\u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u0438\u0440\u0443\u0435\u043c\u044b\u043c\u0438 \u0441\u043b\u043e\u0432\u0430\u0440\u044f\u043c\u0438 - \u044d\u0442\u043e \u043e\u0434\u043d\u043e \u0438\u0437 \u0435\u0433\u043e \u0433\u043b\u0430\u0432\u043d\u044b\u0445 \u0434\u043e\u0441\u0442\u043e\u0438\u043d\u0441\u0442\u0432.\r\n\u0427\u0442\u043e\u0431\u044b \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u043e\u0432\u0430\u0442\u044c \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f\u043c \u0432\u044b\u0448\u0435\u0443\u043f\u043e\u043c\u044f\u043d\u0443\u0442\u043e\u0433\u043e \u0437\u0430\u043a\u043e\u043d\u0430, \u043c\u0443\u0437\u0435\u0438 \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u043e \u043f\u043e\u043b\u0435 \u0432\u0432\u043e\u0434\u0430 \u0434\u043b\u044f \u0432\u0432\u043e\u0434\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440\u043e\u0432 \u0442\u0435\u0433\u043e\u0432, \u0432\u043a\u043b\u044e\u0447\u0435\u043d\u043d\u044b\u0445 \u0432 \u0431\u0435\u043b\u044b\u0439 \u0441\u043f\u0438\u0441\u043e\u043a \u0434\u043b\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u043e\u0432, \u0432 \u0432\u0438\u0434\u0435 \u0441\u043f\u0438\u0441\u043a\u0430, \u0440\u0430\u0437\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0437\u0430\u043f\u044f\u0442\u044b\u043c\u0438. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \"1,21,521\".",
         "limit_tags_for_techniques_by_id": "\u041e\u0433\u0440\u0430\u043d\u0438\u0447\u044c\u0442\u0435 \u0442\u0435\u0433\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043c\u043e\u0433\u0443\u0442 \u0431\u044b\u0442\u044c \u0441\u0432\u044f\u0437\u0430\u043d\u044b \u043a\u0430\u043a \u0442\u0435\u0445\u043d\u0438\u043a\u0438, \u043f\u043e \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440\u0443",
-        "limit_tags_for_techniques_by_id_explica": "\u0421\u043e\u0433\u043b\u0430\u0441\u043d\u043e \u0432\u0435\u043d\u0433\u0435\u0440\u0441\u043a\u043e\u043c\u0443 \u0437\u0430\u043a\u043e\u043d\u043e\u0434\u0430\u0442\u0435\u043b\u044c\u0441\u0442\u0432\u0443, \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043a\u043e\u043b\u043b\u0435\u043a\u0446\u0438\u044f\u043c\u0438 \u0434\u043e\u043b\u0436\u043d\u044b \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0442\u044c \u043c\u0443\u0437\u0435\u044f\u043c \u0432\u044b\u0431\u0438\u0440\u0430\u0442\u044c \u0442\u0435\u0445\u043d\u0438\u043a\u0438 \u0438\u0437 \u0441\u043f\u0438\u0441\u043a\u0430 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0439, \u0445\u0430\u0440\u0430\u043a\u0442\u0435\u0440\u043d\u043e\u0433\u043e \u0434\u043b\u044f \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0433\u043e \u043c\u0443\u0437\u0435\u044f. musdb \u043e\u0431\u044b\u0447\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u0441 \u043e\u0431\u0449\u0438\u043c\u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u0438\u0440\u0443\u0435\u043c\u044b\u043c\u0438 \u0441\u043b\u043e\u0432\u0430\u0440\u044f\u043c\u0438 - \u044d\u0442\u043e \u043e\u0434\u043d\u0430 \u0438\u0437 \u0435\u0433\u043e \u0441\u0430\u043c\u044b\u0445 \u0441\u0438\u043b\u044c\u043d\u044b\u0445 \u0441\u0442\u043e\u0440\u043e\u043d.\r\n\u0427\u0442\u043e\u0431\u044b \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u043e\u0432\u0430\u0442\u044c \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f\u043c, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044b\u043c \u0432\u044b\u0448\u0435\u0443\u043f\u043e\u043c\u044f\u043d\u0443\u0442\u044b\u043c \u0437\u0430\u043a\u043e\u043d\u043e\u043c, \u043c\u0443\u0437\u0435\u0438 \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u043e \u043f\u043e\u043b\u0435 \u0432\u0432\u043e\u0434\u0430 \u0434\u043b\u044f \u0432\u0432\u043e\u0434\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440\u043e\u0432 \u0442\u0435\u0433\u043e\u0432, \u0432\u043a\u043b\u044e\u0447\u0435\u043d\u043d\u044b\u0445 \u0432 \u0431\u0435\u043b\u044b\u0439 \u0441\u043f\u0438\u0441\u043e\u043a \u0434\u043b\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0442\u0435\u0445\u043d\u0438\u043a, \u0432 \u0432\u0438\u0434\u0435 \u0441\u043f\u0438\u0441\u043a\u0430, \u0440\u0430\u0437\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0437\u0430\u043f\u044f\u0442\u044b\u043c\u0438. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \"1,21,521\"."
+        "limit_tags_for_techniques_by_id_explica": "\u0421\u043e\u0433\u043b\u0430\u0441\u043d\u043e \u0432\u0435\u043d\u0433\u0435\u0440\u0441\u043a\u043e\u043c\u0443 \u0437\u0430\u043a\u043e\u043d\u043e\u0434\u0430\u0442\u0435\u043b\u044c\u0441\u0442\u0432\u0443, \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043a\u043e\u043b\u043b\u0435\u043a\u0446\u0438\u044f\u043c\u0438 \u0434\u043e\u043b\u0436\u043d\u044b \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0442\u044c \u043c\u0443\u0437\u0435\u044f\u043c \u0432\u044b\u0431\u0438\u0440\u0430\u0442\u044c \u0442\u0435\u0445\u043d\u0438\u043a\u0438 \u0438\u0437 \u0441\u043f\u0438\u0441\u043a\u0430 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0439, \u0445\u0430\u0440\u0430\u043a\u0442\u0435\u0440\u043d\u043e\u0433\u043e \u0434\u043b\u044f \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0433\u043e \u043c\u0443\u0437\u0435\u044f. musdb \u043e\u0431\u044b\u0447\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u0441 \u043e\u0431\u0449\u0438\u043c\u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u0438\u0440\u0443\u0435\u043c\u044b\u043c\u0438 \u0441\u043b\u043e\u0432\u0430\u0440\u044f\u043c\u0438 - \u044d\u0442\u043e \u043e\u0434\u043d\u0430 \u0438\u0437 \u0435\u0433\u043e \u0441\u0430\u043c\u044b\u0445 \u0441\u0438\u043b\u044c\u043d\u044b\u0445 \u0441\u0442\u043e\u0440\u043e\u043d.\r\n\u0427\u0442\u043e\u0431\u044b \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u043e\u0432\u0430\u0442\u044c \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f\u043c, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044b\u043c \u0432\u044b\u0448\u0435\u0443\u043f\u043e\u043c\u044f\u043d\u0443\u0442\u044b\u043c \u0437\u0430\u043a\u043e\u043d\u043e\u043c, \u043c\u0443\u0437\u0435\u0438 \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u043e \u043f\u043e\u043b\u0435 \u0432\u0432\u043e\u0434\u0430 \u0434\u043b\u044f \u0432\u0432\u043e\u0434\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440\u043e\u0432 \u0442\u0435\u0433\u043e\u0432, \u0432\u043a\u043b\u044e\u0447\u0435\u043d\u043d\u044b\u0445 \u0432 \u0431\u0435\u043b\u044b\u0439 \u0441\u043f\u0438\u0441\u043e\u043a \u0434\u043b\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0442\u0435\u0445\u043d\u0438\u043a, \u0432 \u0432\u0438\u0434\u0435 \u0441\u043f\u0438\u0441\u043a\u0430, \u0440\u0430\u0437\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0437\u0430\u043f\u044f\u0442\u044b\u043c\u0438. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \"1,21,521\".",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/ru/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "\u0414\u043e\u0441\u0442\u0443\u043f \u043a \u043e\u0442\u0447\u0451\u0442\u0430\u043c",
         "disable_adding_to_vocabs": "\u041e\u0442\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c \u0432\u043d\u0435\u0441\u0435\u043d\u0438\u044f \u043e\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u0439 \u0432 \u0441\u043b\u043e\u0432\u0430\u0440\u044c",
         "disable_adding_to_vocabs_explica": "\u0415\u0441\u043b\u0438 \u044d\u0442\u0430 \u043e\u043f\u0446\u0438\u044f \u0432\u043a\u043b\u044e\u0447\u0435\u043d\u0430, \u044d\u0442\u043e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u043d\u0435 \u0441\u043c\u043e\u0436\u0435\u0442 \u0431\u043e\u043b\u044c\u0448\u0435 \u0432\u043d\u043e\u0441\u0438\u0442\u044c \u043d\u043e\u0432\u044b\u0435 \u0437\u0430\u043f\u0438\u0441\u0438 \u0432 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u0438\u0440\u0443\u0435\u043c\u044b\u0435 \u0441\u043b\u043e\u0432\u0430\u0440\u0438. \u042d\u0442\u043e \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0442\u044c \u043f\u043e\u043b\u0435\u0437\u043d\u043e \u0434\u043b\u044f \u0442\u043e\u0433\u043e, \u0447\u0442\u043e\u0431\u044b \u043e\u0441\u0442\u0430\u043d\u043e\u0432\u0438\u0442\u044c \u043a\u043e\u043b\u043b\u0435\u0433, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u043f\u043e\u0441\u0442\u043e\u044f\u043d\u043d\u043e \u0432\u0432\u043e\u0434\u044f\u0442 \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u0435 \/ \u043d\u0435\u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u0446\u0438\u0440\u0443\u0435\u043c\u044b\u0435 \/ \u043f\u0440\u043e\u0442\u0438\u0432\u043e\u0440\u0435\u0447\u0430\u0449\u0438\u0435 \u043f\u0440\u0430\u0432\u0438\u043b\u0430\u043c \u0441\u043b\u043e\u0432\u0430\u0440\u043d\u044b\u0435 \u0441\u0442\u0430\u0442\u044c\u0438.\r\n",
-        "remove_remember_me_tokens": "\u0423\u0434\u0430\u043b\u0438\u0442\u044c \u0432\u0441\u0435 \u0437\u0430\u043f\u043e\u043c\u043d\u0435\u043d\u043d\u044b\u0435 \u0432\u0445\u043e\u0434\u044b \u0432 \u0441\u0438\u0441\u0442\u0435\u043c\u0443"
+        "remove_remember_me_tokens": "\u0423\u0434\u0430\u043b\u0438\u0442\u044c \u0432\u0441\u0435 \u0437\u0430\u043f\u043e\u043c\u043d\u0435\u043d\u043d\u044b\u0435 \u0432\u0445\u043e\u0434\u044b \u0432 \u0441\u0438\u0441\u0442\u0435\u043c\u0443",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/ta/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/ta/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/ta/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/ta/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/ta/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/te/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/te/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/te/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",

backend/te/settings.json

@@ -113,6 +113,21 @@
         "limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
         "limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
         "limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
-        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
+        "limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
+        "object_citation_guide": "Object Citation guide",
+        "explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
+        "object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
+        "hide_duplicate_fields": "Hide duplicate fields",
+        "explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
+        "hide_free_text_object_location": "Hide free text fields for object location",
+        "hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
+        "hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
+        "hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
+        "hide_free_text_object_loans": "Hide free text fields for objects' loans",
+        "hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
+        "hide_free_text_object_entry": "Hide free text fields for object entry",
+        "hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together).",
+        "enforce_custom_object_page": "Enforce custom object page",
+        "explica_enforce_custom_object_page": "Requires all users of the current institution to use the custom object editing page. This means, that access to the regular, tab-based page layout is disabled."
     }
 }

backend/te/user.json

@@ -165,6 +165,8 @@
         "access_to_statements": "Access to statements",
         "disable_adding_to_vocabs": "Disable adding to vocabs",
         "disable_adding_to_vocabs_explica": "If enabled, this user account cannot be used anymore to enter new entries to the controlled vocabularies. This may be useful to stop colleagues who repeatedly enter wrong \/ unidentifiable \/ rule-contradicting vocabulary entries.",
-        "remove_remember_me_tokens": "Remove all remembered logins"
+        "remove_remember_me_tokens": "Remove all remembered logins",
+        "disallow_publishing_objects": "Disallow publishing objects",
+        "disallow_publishing_objects_explica": "Disallows the user from publishing any objects. This may be used to prevent users from publishing low quality object data."
     }
 }

backend/tl/basis.json

@@ -302,6 +302,10 @@
         "all": "All",
         "content": "Content",
         "unit": "Unit",
-        "versioning": "Versioning"
+        "versioning": "Versioning",
+        "autogenerate": "Autogenerate",
+        "suggestions": "Suggestions",
+        "generated_by": "Generated by",
+        "formulate_automatically": "Formulate automatically"
     }
 }

backend/tl/eventtype_explica.json

@@ -49,6 +49,11 @@
         "49": "Here you can note down when the object was given away and who did so.",
         "50": "Here you can note down when the object was inherited to somebody.",
         "51": "Mainly used for written works. Describes the central subject of the object. E.g. the founding document of a city may have that same city as its subject.",
-        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones."
+        "52": "For inorganic objects that were not created by humans but emerged in nature. E.g. stones.",
+        "53": "If an object consists of different materials, the production background of these can be described here.",
+        "54": "To be used if the object is a text that prominently features the place hereby referenced.",
+        "55": "To be used if the object is a text that prominently features the time hereby referenced.",
+        "56": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown.",
+        "57": "To be used if an transfer in ownership is recorded, but the exact type (buying\/selling; gift) is unknown."
     }
 }

backend/tl/object_addendum.json

@@ -366,7 +366,20 @@
         "generate_inventory_number": "Generate inventory number",
         "transfer_invno_suggestion": "Transfer inventory number suggestion",
         "scan_inventory_number": "Scan inventory number",
-        "main_measurement_types": "Basic types"
+        "main_measurement_types": "Basic types",
+        "can_be_published": "Can be published",
+        "generating_description_take_time": "Generating description. This may take some seconds. Time: ",
+        "click_to_select_suggestion": "Click to read a full suggestion. Click again to select it. Afterwards, you can make further edits.",
+        "display_prompt": "Display prompt",
+        "redact_ai_generated_desc": "Redact AI-generated object description",
+        "suggest_desc_by_ai_explica": "Use other metadata to request large language models to formulate object descriptions. ",
+        "custom_object_page": "Custom object page",
+        "toggle_custom_object_page_explica": "Toggle on \/ off the custom object editing page. The custom object editing page drops the regular, tab-based interface for fully customizable widget-based view.",
+        "caching_suggestions_for_object_descriptions": "Caching suggestions for object descriptions",
+        "pregenerate_suggestions_for_object_descriptions": "Pre-generate suggestions for object descriptions",
+        "generating_description_requires_tag_event": "Please mind: Generating an object description requires at least one tag and one event.",
+        "disposal_recipient": "Disposal recipient",
+        "disposal_recipient_explica": "Recipient of the object upon disposal. This may be a museum the object was handed over to, a company handling the disposal, etc."
     },
     "ortart": [
         "",