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
2023-12-12 14:23:06 +00:00
committed by md translation bot
parent a3b25375c1
commit 57432626d7
19 changed files with 133 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
backend/ar/settings.json
View File

@ -107,6 +107,12 @@
"nextcloud_base_url": "Nextcloud integration: base URL",
"explica_nextcloud_base_url": "musdb can be integrated with an institution's Nextcloud instance. To do so, the base URL (https:\/\/cloud.example.com) needs to be entered here. If that has been done, each user of the institution can enter their username and an app password (available using the user security settings in Nextcloud) in their personal settings. Subsequently, musdb will indicate if one has access to folders with additional data for an entry - e.g. a loan or an exhibition. For this to work, folder names need to include the entity's reference number (displayed in the sidebar).",
"custom_report_templates_explanation": "Here you can upload templates for reports and overviews. At the respecitve places (page of an object, object overview, \u2026) these template might be used to autogenerate the reports and overviews with the relevant information. Placeholders mark the space where the respective information is filled in when the report is generated. A list of the placeholders available for a given type of report can be accessed by clicking one of the buttons below. The templates need to be uploaded in a plain text format (e.g. html, csv, txt, \u2026).",
"custom_report_templates_object_loop_explanation": "Where a given type of report concerns multiple objects, the section for representing object information has to be encapsulted with the marker {object_loop}."
"custom_report_templates_object_loop_explanation": "Where a given type of report concerns multiple objects, the section for representing object information has to be encapsulted with the marker {object_loop}.",
"limit_tags_for_object_types_by_id": "Limit tags that can be linked as object types by ID",
"limit_tags_for_object_types_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose object types 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 object types in a comma-separated list. E.g. \"1,21,521\"",
"limit_tags_for_materials_by_id": "Limit tags that can be linked as materials by ID",
"limit_tags_for_materials_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose materials from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as materials in a comma-separated list. E.g. \"1,21,521\"",
"limit_tags_for_techniques_by_id": "Limit tags that can be linked as techniques by ID",
"limit_tags_for_techniques_by_id_explica": "According to Hungarian law, collection management systems should allow museums to choose techniques from a *museum-specific* list of values. musdb generally works with shared controlled vocabularies - in fact, that is one of it's greatest stengths.\r\nTo still meet the requirements set by the law mentioned above, museums can use this input field to enter the IDs of tags whitelisted for use as techniques in a comma-separated list. E.g. \"1,21,521\""
}
}