Approval in backend

backend/ar/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/ar/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/ar/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/cs/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Automaticky generovat",
         "generated_by": "Vygenerov\u00e1no u\u017eivatelem",
         "formulate_automatically": "Automaticky formulovat",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/cs/object_addendum.json

@@ -380,7 +380,8 @@
         "generating_description_requires_tag_event": "Upozorn\u011bn\u00ed: Generov\u00e1n\u00ed popisu objektu vy\u017eaduje alespo\u0148 jeden tag a jednu ud\u00e1lost.",
         "disposal_recipient": "P\u0159\u00edjemce likvidace",
         "disposal_recipient_explica": "P\u0159\u00edjemce p\u0159edm\u011btu p\u0159i jeho likvidaci. M\u016f\u017ee se jednat o muzeum, kter\u00e9mu byl p\u0159edm\u011bt p\u0159ed\u00e1n, spole\u010dnost, kter\u00e1 se zab\u00fdv\u00e1 likvidac\u00ed atd.",
-        "prepend_current_object_description": "P\u0159idat na za\u010d\u00e1tek aktu\u00e1ln\u00ed popis objektu"
+        "prepend_current_object_description": "P\u0159idat na za\u010d\u00e1tek aktu\u00e1ln\u00ed popis objektu",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/cs/settings.json

@@ -128,6 +128,16 @@
         "hide_free_text_object_entry": "Skr\u00fdt voln\u00e1 textov\u00e1 pole pro zad\u00e1v\u00e1n\u00ed objekt\u016f",
         "hide_free_text_object_entry_explica": "Na kart\u011b administrace str\u00e1nek objekt\u016f jsou k dispozici r\u016fzn\u00e1 voln\u00e1 textov\u00e1 pole pro popis vstupu objektu do muzea: p\u0159edchoz\u00ed vlastn\u00edk, typ vstupu atd. Alternativn\u011b je mo\u017en\u00e9 objekt propojit s procesem akvizice. Prost\u0159ednictv\u00edm akvizic\u00ed se p\u0159edchoz\u00ed majitel\u00e9 zad\u00e1vaj\u00ed prost\u0159ednictv\u00edm adres\u00e1\u0159e \/ modulu kontakt\u016f. Jejich kontaktn\u00ed \u00fadaje se tak mohou zobrazit na str\u00e1nce objektu, pokud jsou k dispozici. Voln\u00e1 textov\u00e1 pole maj\u00ed nav\u00edc logick\u00fd nedostatek v tom, \u017ee jejich popis pouze jednotliv\u00fdch objekt\u016f br\u00e1n\u00ed popisu p\u0159esn\u00fdch cen pro v\u00edce objekt\u016f, kter\u00e9 byly zakoupeny b\u011bhem hromadn\u00e9 transakce. V p\u0159\u00edpad\u011b v\u00fdb\u011bru akvizic\u00ed se cena zad\u00e1v\u00e1 pouze pro v\u0161echny objekty dohromady (proto\u017ee byla zaplacena pouze jednou za v\u0161echny dohromady).",
         "enforce_custom_object_page": "Vynutit str\u00e1nku vlastn\u00edho objektu",
-        "explica_enforce_custom_object_page": "Vy\u017eaduje, aby v\u0161ichni u\u017eivatel\u00e9 aktu\u00e1ln\u00ed instituce pou\u017e\u00edvali vlastn\u00ed str\u00e1nku pro \u00fapravu objekt\u016f. To znamen\u00e1, \u017ee p\u0159\u00edstup k b\u011b\u017en\u00e9mu rozvr\u017een\u00ed str\u00e1nky s kartami je zak\u00e1z\u00e1n."
+        "explica_enforce_custom_object_page": "Vy\u017eaduje, aby v\u0161ichni u\u017eivatel\u00e9 aktu\u00e1ln\u00ed instituce pou\u017e\u00edvali vlastn\u00ed str\u00e1nku pro \u00fapravu objekt\u016f. To znamen\u00e1, \u017ee p\u0159\u00edstup k b\u011b\u017en\u00e9mu rozvr\u017een\u00ed str\u00e1nky s kartami je zak\u00e1z\u00e1n.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/de/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Vorschl\u00e4ge",
         "generated_by": "Generiert von",
         "formulate_automatically": "Automatisch formulieren",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Hat \u00dcbergeordnetes",
+        "public": "\u00d6ffentlich"
     }
 }

backend/de/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Bestehende Beschreibung voranstellen"
+        "prepend_current_object_description": "Bestehende Beschreibung voranstellen",
+        "additional_numbers": "Weitere Nummern"
     },
     "ortart": [
         "",

backend/de/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Freitextfeld f\u00fcr alternative Inventarnummer verstecken",
+        "hide_freetext_alternative_invno_explica": "Auf dem Reiter \"Verwaltung\" der Objektbearbeitungsseite findet sich ein Feld f\u00fcr die Erfassung alter Inventarnummern. Dieses Feld ist kein Wiederholfeld. Alternative Inventarnummern k\u00f6nnen ebenfalls als zus\u00e4tzliche Nummer auf dem Reiter \"Zusatz\" erfasst werden. Hierbei handelt es sich um ein wiederholbares Feld, das eine deutlich fein-granularere Erfassung erm\u00f6glicht.",
+        "category": "Kategorie",
+        "validation_pattern": "Validierungs-Muster",
+        "explanation": "Erkl\u00e4rung",
+        "alt_no_category_explica": "Name der Kategorie",
+        "alt_invno_validation_pattern_explica": "Leer lassen f\u00fcr nicht-Verwendung. HTML5-Pattern zur Frontend-seitigen Eingabevalidierung.",
+        "alt_no_explanation_explica": "Ver\u00f6ffentlichbare Erkl\u00e4rung \/ Notiz.",
+        "alt_no_schemas": "Schemata f\u00fcr weitere Nummern",
+        "timed_sending_reports": "Regelm\u00e4\u00dfiges Versenden von Reporten"
     }
 }

backend/dsb/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/dsb/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/dsb/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/en/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/en/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/en/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/es/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/es/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/es/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/fr/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/fr/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/fr/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/hi/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/hi/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/hi/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/hsb/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/hsb/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/hsb/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/hu/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/hu/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/hu/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/id/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/id/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/id/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/it/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/it/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/it/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/iw/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/iw/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/iw/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/kn/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/kn/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/kn/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/nl/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/nl/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/nl/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/pl/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/pl/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/pl/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/pt/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/pt/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/pt/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/ro/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/ro/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/ro/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/ru/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/ru/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/ru/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/ta/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/ta/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/ta/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/te/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/te/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/te/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/tl/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/tl/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/tl/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/tr/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/tr/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/tr/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/uk/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "\u041f\u0440\u043e\u043f\u043e\u0437\u0438\u0446\u0456\u0457",
         "generated_by": "\u0417\u0433\u0435\u043d\u0435\u0440\u043e\u0432\u0430\u043d\u043e",
         "formulate_automatically": "\u0421\u0444\u043e\u0440\u043c\u0443\u043b\u044e\u0432\u0430\u0442\u0438 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0447\u043d\u043e",
-        "name": "\u041d\u0430\u0437\u0432\u0430"
+        "name": "\u041d\u0430\u0437\u0432\u0430",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/uk/object_addendum.json

@@ -380,7 +380,8 @@
         "generating_description_requires_tag_event": "\u0417\u0432\u0435\u0440\u043d\u0456\u0442\u044c \u0443\u0432\u0430\u0433\u0443: \u0434\u043b\u044f \u0441\u0442\u0432\u043e\u0440\u0435\u043d\u043d\u044f \u043e\u043f\u0438\u0441\u0443 \u043e\u0431'\u0454\u043a\u0442\u0430 \u043f\u043e\u0442\u0440\u0456\u0431\u0435\u043d \u0449\u043e\u043d\u0430\u0439\u043c\u0435\u043d\u0448\u0435 \u043e\u0434\u0438\u043d \u0442\u0435\u0433 \u0456 \u043e\u0434\u043d\u0430 \u043f\u043e\u0434\u0456\u044f.",
         "disposal_recipient": "\u041e\u0434\u0435\u0440\u0436\u0443\u0432\u0430\u0447 \u043f\u0456\u0434 \u0447\u0430\u0441 \u0432\u0438\u0431\u0443\u0442\u0442\u044f \u043e\u0431'\u0454\u043a\u0442\u0430",
         "disposal_recipient_explica": "\u041e\u0434\u0435\u0440\u0436\u0443\u0432\u0430\u0447 \u043e\u0431'\u0454\u043a\u0442\u0430 \u043f\u0456\u0434 \u0447\u0430\u0441 \u0432\u0438\u0431\u0443\u0442\u0442\u044f. \u0426\u0435 \u043c\u043e\u0436\u0435 \u0431\u0443\u0442\u0438 \u043c\u0443\u0437\u0435\u0439, \u044f\u043a\u043e\u043c\u0443 \u043f\u0435\u0440\u0435\u0434\u0430\u043d\u043e \u043e\u0431'\u0454\u043a\u0442, \u043a\u043e\u043c\u043f\u0430\u043d\u0456\u044f, \u0449\u043e \u0437\u0430\u0439\u043c\u0430\u0454\u0442\u044c\u0441\u044f \u0443\u0442\u0438\u043b\u0456\u0437\u0430\u0446\u0456\u0454\u044e, \u0442\u043e\u0449\u043e.",
-        "prepend_current_object_description": "\u041f\u0456\u0434\u0433\u043e\u0442\u0443\u0432\u0430\u0442\u0438 \u043f\u043e\u0442\u043e\u0447\u043d\u0438\u0439 \u043e\u043f\u0438\u0441 \u043e\u0431'\u0454\u043a\u0442\u0430"
+        "prepend_current_object_description": "\u041f\u0456\u0434\u0433\u043e\u0442\u0443\u0432\u0430\u0442\u0438 \u043f\u043e\u0442\u043e\u0447\u043d\u0438\u0439 \u043e\u043f\u0438\u0441 \u043e\u0431'\u0454\u043a\u0442\u0430",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/uk/settings.json

@@ -128,6 +128,16 @@
         "hide_free_text_object_entry": "\u041f\u0440\u0438\u0445\u043e\u0432\u0430\u0442\u0438 \u043f\u043e\u043b\u044f \u0437 \u0432\u0456\u043b\u044c\u043d\u0438\u043c \u0442\u0435\u043a\u0441\u0442\u043e\u043c \u0434\u043b\u044f \u0432\u0432\u0435\u0434\u0435\u043d\u043d\u044f \u043e\u0431\u2019\u0454\u043a\u0442\u0430",
         "hide_free_text_object_entry_explica": "\u041d\u0430 \u0432\u043a\u043b\u0430\u0434\u0446\u0456 \u0430\u0434\u043c\u0456\u043d\u0456\u0441\u0442\u0440\u0430\u0446\u0456\u0457 \u0441\u0442\u043e\u0440\u0456\u043d\u043e\u043a \u043e\u0431\u2019\u0454\u043a\u0442\u0456\u0432 \u0454 \u0440\u0456\u0437\u043d\u0456 \u043f\u043e\u043b\u044f \u0437 \u0432\u0456\u043b\u044c\u043d\u0438\u043c \u0442\u0435\u043a\u0441\u0442\u043e\u043c \u0434\u043b\u044f \u043e\u043f\u0438\u0441\u0443 \u043d\u0430\u0434\u0445\u043e\u0434\u0436\u0435\u043d\u043d\u044f \u043e\u0431\u2019\u0454\u043a\u0442\u0430 \u0434\u043e \u043c\u0443\u0437\u0435\u044e: \u043f\u043e\u043f\u0435\u0440\u0435\u0434\u043d\u0456\u0439 \u0432\u043b\u0430\u0441\u043d\u0438\u043a, \u0442\u0438\u043f \u043d\u0430\u0434\u0445\u043e\u0434\u0436\u0435\u043d\u043d\u044f \u0442\u043e\u0449\u043e. \u0410\u043b\u044c\u0442\u0435\u0440\u043d\u0430\u0442\u0438\u0432\u043e\u044e \u0454 \u043f\u0440\u0438\u0432\u2019\u044f\u0437\u043a\u0430 \u043e\u0431\u2019\u0454\u043a\u0442\u0430 \u0434\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0443 \u043f\u0440\u0438\u0434\u0431\u0430\u043d\u043d\u044f. \u0427\u0435\u0440\u0435\u0437 \u043f\u0440\u043e\u0446\u0435\u0441\u0438 \u043f\u0440\u0438\u0434\u0431\u0430\u043d\u043d\u044f \u043f\u043e\u043f\u0435\u0440\u0435\u0434\u043d\u0456 \u0432\u043b\u0430\u0441\u043d\u0438\u043a\u0438 \u0432\u0432\u043e\u0434\u044f\u0442\u044c\u0441\u044f \u0447\u0435\u0440\u0435\u0437 \u043c\u043e\u0434\u0443\u043b\u044c \u0430\u0434\u0440\u0435\u0441\u043d\u043e\u0457 \u043a\u043d\u0438\u0433\u0438 \/ \u043a\u043e\u043d\u0442\u0430\u043a\u0442\u0456\u0432. \u0422\u0430\u043a\u0438\u043c \u0447\u0438\u043d\u043e\u043c, \u0457\u0445\u043d\u0456 \u043a\u043e\u043d\u0442\u0430\u043a\u0442\u043d\u0456 \u0434\u0430\u043d\u0456 \u043c\u043e\u0436\u0443\u0442\u044c \u0432\u0456\u0434\u043e\u0431\u0440\u0430\u0436\u0430\u0442\u0438\u0441\u044f \u043d\u0430 \u0441\u0442\u043e\u0440\u0456\u043d\u0446\u0456 \u043e\u0431\u2019\u0454\u043a\u0442\u0430, \u044f\u043a\u0449\u043e \u0432\u043e\u043d\u0438 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u0456.\r\n\r\n\u041a\u0440\u0456\u043c \u0442\u043e\u0433\u043e, \u043f\u043e\u043b\u044f \u0437 \u0432\u0456\u043b\u044c\u043d\u0438\u043c \u0442\u0435\u043a\u0441\u0442\u043e\u043c \u043c\u0430\u044e\u0442\u044c \u043b\u043e\u0433\u0456\u0447\u043d\u0438\u0439 \u043d\u0435\u0434\u043e\u043b\u0456\u043a: \u0457\u0445\u043d\u0456\u0439 \u043e\u043f\u0438\u0441 \u0441\u0442\u043e\u0441\u0443\u0454\u0442\u044c\u0441\u044f \u043b\u0438\u0448\u0435 \u043e\u043a\u0440\u0435\u043c\u0438\u0445 \u043e\u0431\u2019\u0454\u043a\u0442\u0456\u0432, \u0449\u043e \u0443\u043d\u0435\u043c\u043e\u0436\u043b\u0438\u0432\u043b\u044e\u0454 \u0442\u043e\u0447\u043d\u0435 \u0437\u0430\u0437\u043d\u0430\u0447\u0435\u043d\u043d\u044f \u0446\u0456\u043d \u0434\u043b\u044f \u043a\u0456\u043b\u044c\u043a\u043e\u0445 \u043e\u0431\u2019\u0454\u043a\u0442\u0456\u0432, \u043f\u0440\u0438\u0434\u0431\u0430\u043d\u0438\u0445 \u0443 \u0440\u0430\u043c\u043a\u0430\u0445 \u043e\u0434\u043d\u0456\u0454\u0457 \u043c\u0430\u0441\u043e\u0432\u043e\u0457 \u0442\u0440\u0430\u043d\u0437\u0430\u043a\u0446\u0456\u0457. \u042f\u043a\u0449\u043e \u0432\u0438\u043a\u043e\u0440\u0438\u0441\u0442\u043e\u0432\u0443\u0454\u0442\u044c\u0441\u044f \u043c\u043e\u0434\u0443\u043b\u044c \u043f\u0440\u0438\u0434\u0431\u0430\u043d\u044c, \u0446\u0456\u043d\u0430 \u0432\u0432\u043e\u0434\u0438\u0442\u044c\u0441\u044f \u043b\u0438\u0448\u0435 \u043e\u0434\u0438\u043d \u0440\u0430\u0437 \u0434\u043b\u044f \u0432\u0441\u0456\u0445 \u043e\u0431\u2019\u0454\u043a\u0442\u0456\u0432 \u0440\u0430\u0437\u043e\u043c (\u043e\u0441\u043a\u0456\u043b\u044c\u043a\u0438 \u043e\u043f\u043b\u0430\u0442\u0430 \u0437\u0434\u0456\u0439\u0441\u043d\u044e\u0432\u0430\u043b\u0430\u0441\u044f \u043b\u0438\u0448\u0435 \u043e\u0434\u0438\u043d \u0440\u0430\u0437 \u0437\u0430 \u0432\u0441\u0456 \u043e\u0431\u2019\u0454\u043a\u0442\u0438).",
         "enforce_custom_object_page": "\u041f\u0440\u0438\u043c\u0443\u0441\u043e\u0432\u0435 \u0432\u0438\u043a\u043e\u0440\u0438\u0441\u0442\u0430\u043d\u043d\u044f \u0456\u043d\u0434\u0438\u0432\u0456\u0434\u0443\u0430\u043b\u044c\u043d\u043e\u0457 \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0438 \u043e\u0431'\u0454\u043a\u0442\u0430",
-        "explica_enforce_custom_object_page": "\u0423\u0441\u0456 \u043a\u043e\u0440\u0438\u0441\u0442\u0443\u0432\u0430\u0447\u0456 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u0438 \u043c\u0430\u044e\u0442\u044c \u0432\u0438\u043a\u043e\u0440\u0438\u0441\u0442\u043e\u0432\u0443\u0432\u0430\u0442\u0438 \u0456\u043d\u0434\u0438\u0432\u0456\u0434\u0443\u0430\u043b\u044c\u043d\u0443 \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0443 \u0440\u0435\u0434\u0430\u0433\u0443\u0432\u0430\u043d\u043d\u044f. \u0414\u043e\u0441\u0442\u0443\u043f \u0434\u043e \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u043d\u043e\u0433\u043e \u0432\u0438\u0433\u043b\u044f\u0434\u0443 \u0437 \u0432\u043a\u043b\u0430\u0434\u043a\u0430\u043c\u0438 \u0432\u0438\u043c\u0438\u043a\u0430\u0454\u0442\u044c\u0441\u044f."
+        "explica_enforce_custom_object_page": "\u0423\u0441\u0456 \u043a\u043e\u0440\u0438\u0441\u0442\u0443\u0432\u0430\u0447\u0456 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u0438 \u043c\u0430\u044e\u0442\u044c \u0432\u0438\u043a\u043e\u0440\u0438\u0441\u0442\u043e\u0432\u0443\u0432\u0430\u0442\u0438 \u0456\u043d\u0434\u0438\u0432\u0456\u0434\u0443\u0430\u043b\u044c\u043d\u0443 \u0441\u0442\u043e\u0440\u0456\u043d\u043a\u0443 \u0440\u0435\u0434\u0430\u0433\u0443\u0432\u0430\u043d\u043d\u044f. \u0414\u043e\u0441\u0442\u0443\u043f \u0434\u043e \u0441\u0442\u0430\u043d\u0434\u0430\u0440\u0442\u043d\u043e\u0433\u043e \u0432\u0438\u0433\u043b\u044f\u0434\u0443 \u0437 \u0432\u043a\u043b\u0430\u0434\u043a\u0430\u043c\u0438 \u0432\u0438\u043c\u0438\u043a\u0430\u0454\u0442\u044c\u0441\u044f.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }

backend/zh/basis.json

@@ -307,6 +307,8 @@
         "suggestions": "Suggestions",
         "generated_by": "Generated by",
         "formulate_automatically": "Formulate automatically",
-        "name": "Name"
+        "name": "Name",
+        "has_superordinate": "Has superordinate",
+        "public": "Public"
     }
 }

backend/zh/object_addendum.json

@@ -380,7 +380,8 @@
         "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.",
-        "prepend_current_object_description": "Prepend current object description"
+        "prepend_current_object_description": "Prepend current object description",
+        "additional_numbers": "Additional numbers"
     },
     "ortart": [
         "",

backend/zh/settings.json

@@ -128,6 +128,16 @@
         "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."
+        "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.",
+        "hide_freetext_alternative_invno": "Hide freetext field for alternative inventory numbers",
+        "hide_freetext_alternative_invno_explica": "On the \"administration\" tab, one can register alternative inventory numbers using a non-repeatable free text field. A later development allows registering additional numbers of any type using a more fine-grained, repeatable field on the \"addendum\" tab of object pages. If the latter option is used, the former may be hidden.",
+        "category": "Category",
+        "validation_pattern": "Validation pattern",
+        "explanation": "Explanation",
+        "alt_no_category_explica": "Name of the category",
+        "alt_invno_validation_pattern_explica": "Leave empty if not applicable. Will be used as an HTML5 input validation pattern.",
+        "alt_no_explanation_explica": "Publishable explanation or note about the schema.",
+        "alt_no_schemas": "Schemas for additional numbers",
+        "timed_sending_reports": "Regular sending of reports"
     }
 }