Approval in backend
This commit is contained in:
md translation bot
parent
03568ef004
commit
4ade6bf484
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -114,8 +114,18 @@
|
||||
"limit_tags_for_materials_by_id_explica": "Nach ungarischem Gesetz m\u00fcssen Sammlungsmanagementsysteme den Museen erlauben Materialarten aus einer \"museumsspezifischen\" Liste von Werten auszuw\u00e4hlen. musdb arbeitet im Allgemeinen mit gemeinsam genutzten kontrollierten (statt museumsspezifischen) Vokabularen - was ja eine seiner gr\u00f6\u00dften St\u00e4rken ist.\r\nUm dennoch den Erfordernissen des genannten Gesetzes gerecht zu werden, k\u00f6nnen Museen dieses Eingabelfeld nutzen um IDs einzutragen, f\u00fcr Begriffe, die als Materialart erlaubt sind. Beispielsweise \"1,21,521\"",
|
||||
"limit_tags_for_techniques_by_id": "Begrenze die Schlagworte, die als Technik verwendet werden d\u00fcrfen durch Angabe von IDs",
|
||||
"limit_tags_for_techniques_by_id_explica": "Nach ungarischem Gesetz m\u00fcssen Sammlungsmanagementsysteme den Museen erlauben Techniken aus einer \"museumsspezifischen\" Liste von Werten auszuw\u00e4hlen. musdb arbeitet im Allgemeinen mit gemeinsam genutzten kontrollierten (statt museumsspezifischen) Vokabularen - was ja eine seiner gr\u00f6\u00dften St\u00e4rken ist.\r\nUm dennoch den Erfordernissen des genannten Gesetzes gerecht zu werden, k\u00f6nnen Museen dieses Eingabelfeld nutzen um IDs einzutragen, f\u00fcr Begriffe, die als Technik erlaubt sind. Beispielsweise \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide": "Hinweise zum Zitieren von Objekten",
|
||||
"explica_object_citation_guide": "Ist dieses Feld nicht leer, wird sein Inhalt als zus\u00e4tzliche Notiz im \"Zitieren\"-Overlay der \u00f6ffentlichen Objektseiten angezeigt. So kann festgehalten werden, wie die Objekte selbst (im Gegensatz zum Datensatz) zitiert werden sollten.",
|
||||
"object_citation_guide_text": "Hinweise und Vorschl\u00e4ge zum Zitieren von Objekten, die Nutzern auf \u00f6ffentlichen Objektseiten angezeigt werden sollen.",
|
||||
"hide_duplicate_fields": "Doppelte Felder verstecken",
|
||||
"explica_hide_duplicate_fields": "Mit den Jahren sind f\u00fcr einige Aufgaben konkurrienrende Felder in musdb implementiert worden - einmal als Freitextfeld, einmal als Verkn\u00fcpfung mit einem dedizierten Datentyp. Z.B. lassen sich Standorte \u00fcber Freitextfelder auf dem Reiter \"Verbleib\" der Objektseite eintragen. Oder direkt daneben als Bezug auf das R\u00e4ume-Modul. Letzterre Option bietet verbessertes Logging, deutlich bessere Suchoptionen, etc. Die neueren Verkn\u00fcpfungsoptionen sind daher f\u00fcr ein effektives Arbeiten in musdb unbedingt zu bevorzugen.\r\n\r\nUm Verwirrung ob der doppelten Felder zu reduzieren, lassen sich die \u00e4lteren Freitextfelder hier verstecken.",
|
||||
"hide_free_text_object_location": "Freitextfelder f\u00fcr Standort von Objekten verstecken",
|
||||
"hide_free_text_object_location_explica": "Versteckt die Freitextfelder f\u00fcr den Standort eines Objektes. Stattdessen kann der Standort \u00fcber Verkn\u00fcpfungen zu R\u00e4umen festgehalten werden. Auf diese Weise erh\u00e4lt man verbesserte Suchm\u00f6glichkeiten, ein detailliertes Log der Standortverschiebungen, sowie die M\u00f6glichkeit, die Objektdaten mit Sensordaten f\u00fcr die Klimamessung zusammenzuf\u00fchren.",
|
||||
"hide_free_text_object_exhibitions": "Freitextfelder f\u00fcr Ausstellungen von Objekten verstecken",
|
||||
"hide_free_text_object_exhibitions_explica": "Ausstellungen k\u00f6nnen mit Objekten entweder \u00fcber das Freitextfeld auf dem Reiter \"Verbleib\" oder \u00fcber den eigenen Reiter \"Ausstellung\" verkn\u00fcpft werden. Werden sie \u00fcber den eigenen Reiter mit Ausstellungen aus dem Ausstellungsmodul verkn\u00fcpft, ergeben sich verbesserte Suchm\u00f6glichkeiten (z.B.: \"Objekte, die gerade ausgestellt sind\").",
|
||||
"hide_free_text_object_loans": "Freitextfelder f\u00fcr Leihverkehre von Objekten verstecken",
|
||||
"hide_free_text_object_loans_explica": "Leihvorg\u00e4nge k\u00f6nnen mit Objekten entweder \u00fcber das Freitextfeld auf dem Reiter \"Verbleib\" oder \u00fcber den eigenen Reiter \"Leihverkehr\" verkn\u00fcpft werden. Werden sie \u00fcber den eigenen Reiter mit Leihverkehren aus dem Leihverkehrsmodul verkn\u00fcpft, ergeben sich verbesserte Suchm\u00f6glichkeiten (z.B.: \"Objekte, die gerade verliehen sind\").",
|
||||
"hide_free_text_object_entry": "Freitextfelder f\u00fcr Zugang von Objekten verstecken",
|
||||
"hide_free_text_object_entry_explica": "Auf dem Reiter \"Verwaltung\" der Objektbearbeitungsseite finden sich eine Reihe von Freitextfeldern, mit denen sich der Zugang eines Objekets erfassen l\u00e4sst: Vorbesitzer, Art des Zugangs, etc. Alternativ dazu kann das Objekt mit einem Erwerbungsvorgang verkn\u00fcpft werden. Geschieht Letzteres, k\u00f6nnen \u00fcber das Kontakt-Modul z.B. die Kontaktdaten des Vorbesitzers als Vorschau eingebunden werden.\r\nDes Weiteren entsteht bei der blo\u00dfen Erfassung \u00fcber Freitextfelder ggfs. ein logisches Problem im Falle von Konvolutank\u00e4ufen. Hier ist kein eindeutiger Ankaufspreis pro Objekt ermittelbar, da mehrere Objekte zusammen gekauft wurden. Auch das l\u00e4sst sich nur \u00fcber das Erwerbungsmodul sinnvoll abbilden."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "A magyar rendeletek szerint a gy\u0171jtem\u00e9nykezel\u0151 rendszereknek lehet\u0151v\u00e9 kell tenni\u00fck, hogy a m\u00fazeumok saj\u00e1t kulcssz\u00f3list\u00e1b\u00f3l v\u00e1laszthassanak. A musdb \u00e1ltal\u00e1ban megosztott, kontroll\u00e1lt sz\u00f3k\u00e9szletekkel dolgozik \u2013 val\u00f3j\u00e1ban ez az egyik legnagyobb er\u0151ss\u00e9ge.\r\n\r\nAhhoz azonban, hogy megfeleljen a fent eml\u00edtett k\u00f6vetelm\u00e9nynek, a m\u00fazeumok haszn\u00e1lhatj\u00e1k ezt a mez\u0151t annak \u00e9rdek\u00e9ben, hogy egy vessz\u0151vel elv\u00e1lasztott list\u00e1ban feh\u00e9rlist\u00e1zz\u00e1k a kulcsszavaknak az azonos\u00edt\u00f3it (ID) P\u00e9ld\u00e1ul: \u201e1,21,521\u201d.",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "\u0421\u043e\u0433\u043b\u0430\u0441\u043d\u043e \u0432\u0435\u043d\u0433\u0435\u0440\u0441\u043a\u043e\u043c\u0443 \u0437\u0430\u043a\u043e\u043d\u043e\u0434\u0430\u0442\u0435\u043b\u044c\u0441\u0442\u0432\u0443, \u0441\u0438\u0441\u0442\u0435\u043c\u044b \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u043a\u043e\u043b\u043b\u0435\u043a\u0446\u0438\u044f\u043c\u0438 \u0434\u043e\u043b\u0436\u043d\u044b \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0442\u044c \u043c\u0443\u0437\u0435\u044f\u043c \u0432\u044b\u0431\u0438\u0440\u0430\u0442\u044c \u0442\u0435\u0445\u043d\u0438\u043a\u0438 \u0438\u0437 \u0441\u043f\u0438\u0441\u043a\u0430 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0439, \u0445\u0430\u0440\u0430\u043a\u0442\u0435\u0440\u043d\u043e\u0433\u043e \u0434\u043b\u044f \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0433\u043e \u043c\u0443\u0437\u0435\u044f. musdb \u043e\u0431\u044b\u0447\u043d\u043e \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u0441 \u043e\u0431\u0449\u0438\u043c\u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u0438\u0440\u0443\u0435\u043c\u044b\u043c\u0438 \u0441\u043b\u043e\u0432\u0430\u0440\u044f\u043c\u0438 - \u044d\u0442\u043e \u043e\u0434\u043d\u0430 \u0438\u0437 \u0435\u0433\u043e \u0441\u0430\u043c\u044b\u0445 \u0441\u0438\u043b\u044c\u043d\u044b\u0445 \u0441\u0442\u043e\u0440\u043e\u043d.\r\n\u0427\u0442\u043e\u0431\u044b \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u043e\u0432\u0430\u0442\u044c \u0442\u0440\u0435\u0431\u043e\u0432\u0430\u043d\u0438\u044f\u043c, \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u043d\u044b\u043c \u0432\u044b\u0448\u0435\u0443\u043f\u043e\u043c\u044f\u043d\u0443\u0442\u044b\u043c \u0437\u0430\u043a\u043e\u043d\u043e\u043c, \u043c\u0443\u0437\u0435\u0438 \u043c\u043e\u0433\u0443\u0442 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c \u044d\u0442\u043e \u043f\u043e\u043b\u0435 \u0432\u0432\u043e\u0434\u0430 \u0434\u043b\u044f \u0432\u0432\u043e\u0434\u0430 \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440\u043e\u0432 \u0442\u0435\u0433\u043e\u0432, \u0432\u043a\u043b\u044e\u0447\u0435\u043d\u043d\u044b\u0445 \u0432 \u0431\u0435\u043b\u044b\u0439 \u0441\u043f\u0438\u0441\u043e\u043a \u0434\u043b\u044f \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f \u0432 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435 \u0442\u0435\u0445\u043d\u0438\u043a, \u0432 \u0432\u0438\u0434\u0435 \u0441\u043f\u0438\u0441\u043a\u0430, \u0440\u0430\u0437\u0434\u0435\u043b\u0435\u043d\u043d\u043e\u0433\u043e \u0437\u0430\u043f\u044f\u0442\u044b\u043c\u0438. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \"1,21,521\".",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "\u0417\u0433\u0456\u0434\u043d\u043e \u0437 \u0443\u0433\u043e\u0440\u0441\u044c\u043a\u0438\u043c \u0437\u0430\u043a\u043e\u043d\u043e\u0434\u0430\u0432\u0441\u0442\u0432\u043e\u043c, \u0441\u0438\u0441\u0442\u0435\u043c\u0438 \u0443\u043f\u0440\u0430\u0432\u043b\u0456\u043d\u043d\u044f \u043a\u043e\u043b\u0435\u043a\u0446\u0456\u044f\u043c\u0438 \u043f\u043e\u0432\u0438\u043d\u043d\u0456 \u0434\u043e\u0437\u0432\u043e\u043b\u044f\u0442\u0438 \u043c\u0443\u0437\u0435\u044f\u043c \u043e\u0431\u0438\u0440\u0430\u0442\u0438 \u043c\u0435\u0442\u043e\u0434\u0438 \u0437 \u043f\u0435\u0440\u0435\u043b\u0456\u043a\u0443 \u0446\u0456\u043d\u043d\u043e\u0441\u0442\u0435\u0439, \u0441\u043f\u0435\u0446\u0438\u0444\u0456\u0447\u043d\u043e\u0433\u043e \u0434\u043b\u044f \u043a\u043e\u0436\u043d\u043e\u0433\u043e \u043c\u0443\u0437\u0435\u044e. musdb \u0437\u0430\u0437\u0432\u0438\u0447\u0430\u0439 \u043f\u0440\u0430\u0446\u044e\u0454 \u0437\u0456 \u0441\u043f\u0456\u043b\u044c\u043d\u0438\u043c\u0438 \u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u043e\u0432\u0430\u043d\u0438\u043c\u0438 \u0441\u043b\u043e\u0432\u043d\u0438\u043a\u0430\u043c\u0438 - \u0432\u043b\u0430\u0441\u043d\u0435, \u0446\u0435 \u043e\u0434\u043d\u0430 \u0437 \u043d\u0430\u0439\u0431\u0456\u043b\u044c\u0448\u0438\u0445 \u0441\u043a\u043b\u0430\u0434\u043e\u0432\u0438\u0445 \u0439\u043e\u0433\u043e \u0440\u043e\u0431\u043e\u0442\u0438.\r\n\u0429\u043e\u0431 \u0432\u0456\u0434\u043f\u043e\u0432\u0456\u0434\u0430\u0442\u0438 \u0432\u0438\u043c\u043e\u0433\u0430\u043c, \u0432\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u043c \u0432\u0438\u0449\u0435\u0437\u0433\u0430\u0434\u0430\u043d\u0438\u043c \u0437\u0430\u043a\u043e\u043d\u043e\u043c, \u043c\u0443\u0437\u0435\u0457 \u043c\u043e\u0436\u0443\u0442\u044c \u0432\u0438\u043a\u043e\u0440\u0438\u0441\u0442\u043e\u0432\u0443\u0432\u0430\u0442\u0438 \u0446\u0435 \u043f\u043e\u043b\u0435 \u0434\u043b\u044f \u0432\u0432\u0435\u0434\u0435\u043d\u043d\u044f \u0456\u0434\u0435\u043d\u0442\u0438\u0444\u0456\u043a\u0430\u0442\u043e\u0440\u0456\u0432 \u0442\u0435\u0433\u0456\u0432, \u0432\u043d\u0435\u0441\u0435\u043d\u0438\u0445 \u0434\u043e \u0431\u0456\u043b\u043e\u0433\u043e \u0441\u043f\u0438\u0441\u043a\u0443 \u0434\u043b\u044f \u0432\u0438\u043a\u043e\u0440\u0438\u0441\u0442\u0430\u043d\u043d\u044f \u0432 \u044f\u043a\u043e\u0441\u0442\u0456 \u043c\u0435\u0442\u043e\u0434\u0456\u0432, \u0443 \u0432\u0438\u0433\u043b\u044f\u0434\u0456 \u0441\u043f\u0438\u0441\u043a\u0443, \u0440\u043e\u0437\u0434\u0456\u043b\u0435\u043d\u043e\u0433\u043e \u043a\u043e\u043c\u0430\u043c\u0438. \u041d\u0430\u043f\u0440\u0438\u043a\u043b\u0430\u0434, \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
@ -116,6 +116,16 @@
|
||||
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\"",
|
||||
"object_citation_guide": "Object Citation guide",
|
||||
"explica_object_citation_guide": "If this field is not empty, an additional note will appear in the citation overlay of published object pages, displaying the text here, describing how your institution prefers objects (rather than the object data \/ page) to be cited.",
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects"
|
||||
"object_citation_guide_text": "Guidance and citation recommendation shown to users aiming to cite objects",
|
||||
"hide_duplicate_fields": "Hide duplicate fields",
|
||||
"explica_hide_duplicate_fields": "As musdb has grown over the years, some fields have been implemented twice - once as a free text field, one as a structured field linking to a dedicated module of musdb. To reduce confusion and enforce the use of the more advanced version, you can choose to hide the free text fields in the regular (non-customized) object editing page.",
|
||||
"hide_free_text_object_location": "Hide free text fields for object location",
|
||||
"hide_free_text_object_location_explica": "Hide the free text fields for an object's location (current location, general location). You can link the object to spaces using the respective location fields just next to the free text fields instead to get a more detailed log, improved searchability, as well as eventually the option to check sensor data for improved handling of the object's condition using links.",
|
||||
"hide_free_text_object_exhibitions": "Hide free text fields for object exhibitions",
|
||||
"hide_free_text_object_exhibitions_explica": "Exhibitions can be linked to objects in a structured way. If you link objects to exhibitions rather than simply listing them in the free text field, you will have improved search options (including the search for objects currently on display in an exhibition).",
|
||||
"hide_free_text_object_loans": "Hide free text fields for objects' loans",
|
||||
"hide_free_text_object_loans_explica": "Loans can be listed for objects using either a free text field or links to loan entries via the dedicated loan tab of the object page. Linking to loans allows advanced search options (e.g. searching for objects currently on loan).",
|
||||
"hide_free_text_object_entry": "Hide free text fields for object entry",
|
||||
"hide_free_text_object_entry_explica": "On the administration tab of object pages, there are different free text fields to describe the object's entry to the museum: previous owner, entry type, etc. Alternative to those, one can link the object to an acquisition process. Via acquisitions, previous owners are entered through the address book \/ contacts module. Thus, their contact details can be displayed on the object page, if available. Additionally, the free text fields have a logical shortcoming in that their description of only single objects prevents the description of accurate prices for multiple objects that were bought in during a bulk transaction. In case acquisitions are chosen, a price is only entered for all of the objects together (as it was paid only once for all of them together)."
|
||||
}
|
||||
}
|
||||
Loading…
x
Reference in New Issue
Block a user