Approval.

de/quality_web.php

@@ -47,4 +47,13 @@ Mit museum-digital:qa werden diese Werkzeuge auch über die Grenzen von museum-d
   'filesize_too_big' => 'Die Datei ist zu groß! Die maximale erlaubte Größe eines Uploads ist [placeholder] Byte.',
   'quality_assessment_tools' => 'Werkzeuge zur Daten-Qualitätskontrolle',
   'api' => 'API',
+  'outlook' => 'Aussicht',
+  'faq_q_why_is_my_cms_not_supported' => 'Warum werden Exporte aus meinem Sammlungsmanagementsystem nicht unterstützt?',
+  'faq_a_why_is_my_cms_not_supported' => 'Wie im Bereich "Technischer Hintergrund" beschrieben, gibt es nicht bei jeder Software über Museumsgrenzen hinweg konsistente Ausgabe- und Exportformate. museum-digital:qa kann allerdings nur solche (und die gängigen Austauschstandards, etwa LIDO) unterstützen.
+
+Oft 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üssen die Exporte ebenso auf das Museum zugeschnitten werden.
+
+Gibt es allerdings ein konsistentes Ausgabeformat, das hier noch nicht berücksichtigt wird, oder unterstützt die Software primär ein standardisiertes Austauschformat, das hier noch nicht berücksichtigt wird, würden wir uns freuen, auch dieses in Zukunft zu unterstützen. Eine große Hilfe wäre 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üpfungen vor. Funktionieren die Checks trotzdem?',
+  'faq_a_birth_death_dates_via_vocabs' => 'Ja. Beim Auslesen der Daten mit bestehenden Normdatenbezügen werden zusätzliche Informationen zu den Akteuren - wie etwa Lebensdaten - aus den kontrollierten Vokabularen von museum-digital bezogen, so es dort bereits einen Datensatz für denselben Akteur gibt.',
 );

en/quality_web.php

@@ -46,4 +46,13 @@ museum-digital:qa allows the (re-)use of these tools by users and software beyon
   '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',
+  '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.
+
+The 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.
+
+If 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.',
 );

hu/quality_web.php

@@ -46,4 +46,13 @@ museum-digital:qa allows the (re-)use of these tools by users and software beyon
   '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',
+  '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.
+
+The 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.
+
+If 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.',
 );

ru/quality_web.php

@@ -46,4 +46,13 @@ museum-digital:qa allows the (re-)use of these tools by users and software beyon
   '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',
+  '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.
+
+The 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.
+
+If 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.',
 );

uk/quality_web.php

@@ -46,4 +46,13 @@ museum-digital:qa allows the (re-)use of these tools by users and software beyon
   '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',
+  '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.
+
+The 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.
+
+If 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.',
 );