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

Approval in quality-web

Browse Source
This commit is contained in:
Joshua Ramon Enslin 2023-10-06 15:14:11 +00:00 committed by md translation bot
parent 64195dc86f
commit 8976b2ef30
5 changed files with 30 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
quality-web/de/quality_web.json
View File

@ -38,6 +38,11 @@
"currently_offline_msg": "Sie sind derzeit offline. Die Auswertung der Daten geschieht auf dem Server. Bitte stellen Sie sicher, dass ihre Internetverbindung stabil ist und probieren es dann erneut.",
"filesize_too_big": "Die Datei ist zu gro\u00df! Die maximale erlaubte Gr\u00f6\u00dfe eines Uploads ist [placeholder] Byte.",
"quality_assessment_tools": "Werkzeuge zur Daten-Qualit\u00e4tskontrolle",
"api": "API"
"api": "API",
"outlook": "Aussicht",
"faq_q_why_is_my_cms_not_supported": "Warum werden Exporte aus meinem Sammlungsmanagementsystem nicht unterst\u00fctzt?",
"faq_a_why_is_my_cms_not_supported": "Wie im Bereich \"Technischer Hintergrund\" beschrieben, gibt es nicht bei jeder Software \u00fcber Museumsgrenzen hinweg konsistente Ausgabe- und Exportformate. museum-digital:qa kann allerdings nur solche (und die g\u00e4ngigen Austauschstandards, etwa LIDO) unterst\u00fctzen.\r\n\r\nOft liegt das Fehlen von konsistenten Ausgabe- und Exportformaten an der Anpassbarkeit der zugrundeliegenden Datenbank - ist diese bis auf die einzelnen Felder auf das Museum zugeschnitten, m\u00fcssen die Exporte ebenso auf das Museum zugeschnitten werden.\r\n\r\nGibt es allerdings ein konsistentes Ausgabeformat, das hier noch nicht ber\u00fccksichtigt wird, oder unterst\u00fctzt die Software prim\u00e4r ein standardisiertes Austauschformat, das hier noch nicht ber\u00fccksichtigt wird, w\u00fcrden wir uns freuen, auch dieses in Zukunft zu unterst\u00fctzen. Eine gro\u00dfe Hilfe w\u00e4re dabei eine Mail an quality@museum-digital.de, idealerweise zusammen mit einigen exemplarischen Exportdaten.",
"faq_q_birth_death_dates_via_vocabs": "Lebensdaten sind in meinen Objektmetadaten nicht verzeichnet, aber es liegen Normdatenverkn\u00fcpfungen vor. Funktionieren die Checks trotzdem?",
"faq_a_birth_death_dates_via_vocabs": "Ja. Beim Auslesen der Daten mit bestehenden Normdatenbez\u00fcgen werden zus\u00e4tzliche Informationen zu den Akteuren - wie etwa Lebensdaten - aus den kontrollierten Vokabularen von museum-digital bezogen, so es dort bereits einen Datensatz f\u00fcr denselben Akteur gibt."
}
}

7
quality-web/en/quality_web.json
View File

@ -38,6 +38,11 @@
"currently_offline_msg": "You are currently offline. Evaluation happens on the server. Please try to reconnect your network first.",
"filesize_too_big": "The file is too big! The maximum allowed size of uploaded files is [placeholder] byte.",
"quality_assessment_tools": "Quality assessment tools",
"api": "API"
"api": "API",
"outlook": "Outlook",
"faq_q_why_is_my_cms_not_supported": "Why are exports from my CMS not supported?",
"faq_a_why_is_my_cms_not_supported": "As described in the section \"technical background\", not every collection management system offers export formats uniform across the different institutions using it. Besides the general open standards for museum-digital:qa can however only reasonably support those export formats that are not specific to a single institution.\r\n\r\nThe lack of a consistent export format often stems from the customizability of the underlying database structure as opposed to a superficial customizability of the interface - where the database structure is fully customized towards the use case of a museum, custom exports need to be written as well - which in turn means additional cost and effort.\r\n\r\nIf your software however supports a uniform export format across institutions, which is not yet usable with museum-digital:qa, we would be most interested in supporting it in the future as well. In such cases, please send a mail - ideally along with some sample exports - to quality@museum-digital.de.",
"faq_q_birth_death_dates_via_vocabs": "Birth and death dates of related actors are not covered by our object metadata, but we do link them to norm data repositories. Will the plausibility checks still work?",
"faq_a_birth_death_dates_via_vocabs": "Yes. museum-digital:qa will also check references to norm data repositories against museum-digital's controlled vocabularies to gather additional data - such as birth and death dates - if any such references are supplied."
}
}

7
quality-web/hu/quality_web.json
View File

@ -38,6 +38,11 @@
"currently_offline_msg": "You are currently offline. Evaluation happens on the server. Please try to reconnect your network first.",
"filesize_too_big": "The file is too big! The maximum allowed size of uploaded files is [placeholder] byte.",
"quality_assessment_tools": "Quality assessment tools",
"api": "API"
"api": "API",
"outlook": "Outlook",
"faq_q_why_is_my_cms_not_supported": "Why are exports from my CMS not supported?",
"faq_a_why_is_my_cms_not_supported": "As described in the section \"technical background\", not every collection management system offers export formats uniform across the different institutions using it. Besides the general open standards for museum-digital:qa can however only reasonably support those export formats that are not specific to a single institution.\r\n\r\nThe lack of a consistent export format often stems from the customizability of the underlying database structure as opposed to a superficial customizability of the interface - where the database structure is fully customized towards the use case of a museum, custom exports need to be written as well - which in turn means additional cost and effort.\r\n\r\nIf your software however supports a uniform export format across institutions, which is not yet usable with museum-digital:qa, we would be most interested in supporting it in the future as well. In such cases, please send a mail - ideally along with some sample exports - to quality@museum-digital.de.",
"faq_q_birth_death_dates_via_vocabs": "Birth and death dates of related actors are not covered by our object metadata, but we do link them to norm data repositories. Will the plausibility checks still work?",
"faq_a_birth_death_dates_via_vocabs": "Yes. museum-digital:qa will also check references to norm data repositories against museum-digital's controlled vocabularies to gather additional data - such as birth and death dates - if any such references are supplied."
}
}

7
quality-web/ru/quality_web.json
View File

@ -38,6 +38,11 @@
"currently_offline_msg": "You are currently offline. Evaluation happens on the server. Please try to reconnect your network first.",
"filesize_too_big": "The file is too big! The maximum allowed size of uploaded files is [placeholder] byte.",
"quality_assessment_tools": "Quality assessment tools",
"api": "API"
"api": "API",
"outlook": "Outlook",
"faq_q_why_is_my_cms_not_supported": "Why are exports from my CMS not supported?",
"faq_a_why_is_my_cms_not_supported": "As described in the section \"technical background\", not every collection management system offers export formats uniform across the different institutions using it. Besides the general open standards for museum-digital:qa can however only reasonably support those export formats that are not specific to a single institution.\r\n\r\nThe lack of a consistent export format often stems from the customizability of the underlying database structure as opposed to a superficial customizability of the interface - where the database structure is fully customized towards the use case of a museum, custom exports need to be written as well - which in turn means additional cost and effort.\r\n\r\nIf your software however supports a uniform export format across institutions, which is not yet usable with museum-digital:qa, we would be most interested in supporting it in the future as well. In such cases, please send a mail - ideally along with some sample exports - to quality@museum-digital.de.",
"faq_q_birth_death_dates_via_vocabs": "Birth and death dates of related actors are not covered by our object metadata, but we do link them to norm data repositories. Will the plausibility checks still work?",
"faq_a_birth_death_dates_via_vocabs": "Yes. museum-digital:qa will also check references to norm data repositories against museum-digital's controlled vocabularies to gather additional data - such as birth and death dates - if any such references are supplied."
}
}

7
quality-web/uk/quality_web.json
View File

@ -38,6 +38,11 @@
"currently_offline_msg": "You are currently offline. Evaluation happens on the server. Please try to reconnect your network first.",
"filesize_too_big": "The file is too big! The maximum allowed size of uploaded files is [placeholder] byte.",
"quality_assessment_tools": "Quality assessment tools",
"api": "API"
"api": "API",
"outlook": "Outlook",
"faq_q_why_is_my_cms_not_supported": "Why are exports from my CMS not supported?",
"faq_a_why_is_my_cms_not_supported": "As described in the section \"technical background\", not every collection management system offers export formats uniform across the different institutions using it. Besides the general open standards for museum-digital:qa can however only reasonably support those export formats that are not specific to a single institution.\r\n\r\nThe lack of a consistent export format often stems from the customizability of the underlying database structure as opposed to a superficial customizability of the interface - where the database structure is fully customized towards the use case of a museum, custom exports need to be written as well - which in turn means additional cost and effort.\r\n\r\nIf your software however supports a uniform export format across institutions, which is not yet usable with museum-digital:qa, we would be most interested in supporting it in the future as well. In such cases, please send a mail - ideally along with some sample exports - to quality@museum-digital.de.",
"faq_q_birth_death_dates_via_vocabs": "Birth and death dates of related actors are not covered by our object metadata, but we do link them to norm data repositories. Will the plausibility checks still work?",
"faq_a_birth_death_dates_via_vocabs": "Yes. museum-digital:qa will also check references to norm data repositories against museum-digital's controlled vocabularies to gather additional data - such as birth and death dates - if any such references are supplied."
}
}