museum-digital/translation-json
36
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Approval in backend

Browse Source
This commit is contained in:
Joshua Ramon Enslin
2025-03-28 15:28:17 +00:00
committed by md translation bot
parent 03568ef004
commit 4ade6bf484
23 changed files with 255 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
backend/en/settings.json
View File

@ -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)."
}
}