Approval.

de/quality_web.php

@@ -4,7 +4,7 @@ $quality_web = array (
   'puqi' => 'Publikations-Qualitäts-Index (PuQI)',
   'plausi' => 'Plausibilitäts-Check',
   'plausi_legal' => 'Plausibilitäts-Check für Rechteangaben von Objektabbildungen',
-  'puqi_explica' => 'Der Publikations-Qualitäts-Index (PuQI) misst die Vollständigkeit und The publication quality index measures the completeness and suitability of an object record\'s publishable information. For example, feedback is given on the availability of an object title and a tags. Objects\' descriptions are checked for their length; and linked images\' license status is evaluated. Based on these evaluations, a quantitative score is provided to be able to roughly measure the completeness and quality of an object record for publication.',
+  'puqi_explica' => 'Der Publikations-Qualitäts-Index (PuQI) misst die Vollständigkeit und Eignung veröffentlichbarer Informationen eines Objektdatensatzes. Zum Beispiel werden das Vorhandensein eines Objekttitels und von Schlagworten geprüft. Die Objektbeschreibungen werden auf ihre Länge geprüft, und auch der Lizenzstatus der verlinkten Bilder wird evaluiert. Auf der Grundlage dieser Bewertungen wird eine  quantitative Einschätzung ermittelt, um die Vollständigkeit und Qualität eines Objektdatensatzes für die Veröffentlichung grob zu messen.',
   'plausi_explica' => 'Im Rahmen dieses Checks werden die mit einem Objekt verknüpften Ereignisse (Herstellung, Benutzung, etc.) auf ihre logische Kohärenz geprüft. Hierzu werden die angegebenen Lebensdaten und Zeiten genutzt. Zum Beispiel kann ein Fahrrad, das 1950 hergestellt wurde, nicht 1870 genutzt worden sein. Genauso ist es unwahrscheinlich, dass eine 1920 aufgenommene Fotografie Ice-T (geboren 1958) zeigt.',
   'plausi_explica_2' => 'Wurde eine solche logische Inkonsistenz zwischen den verschiedenen Ereignissen der Objektgeschichte gefunden, wird eine Warnung zurückgegeben.',
   'plausi_legal_explica' => 'Dieser Check versucht offensichtliche Probleme bei den Rechte- und Lizenzangaben von Objektabbildungen (etwa Objektfotos) zu identifizieren. Hierzu werden die Lebensdaten der verknüpften Schaffenden ausgewertet - entweder wie mitgegeben oder auf Basis von ggfs. mitgelieferten Bezügen zu kontrollierten Vokabularen und Normdatenrepositorien wie zur Library of Congress, Wikidata oder  der Gemeinsamen Normdatei der Deutschen Nationalbibliothek:',
@@ -26,7 +26,7 @@ Genauso wird eine Warnung zurückgegeben, wenn eine nicht restriktive Lizenz ver
   'select_import_format' => 'Ein Import-Format auswählen',
   'upload_a_file' => 'Eine Datei hochladen',
   'select_file_for_upload' => 'Datei zum Hochladen auswählen',
-  'alt_paste_text' => 'Oder einen Objekt-Datensatz als Text einfügen',
+  'alt_paste_text' => 'Einen Objekt-Datensatz als Text einfügen',
   'text' => 'Text',
   'submit' => 'Abschicken',
   'news' => 'Neuigkeiten',
@@ -43,4 +43,55 @@ Mit museum-digital:qa werden diese Werkzeuge auch über die Grenzen von museum-d
   'tech_background_hl' => 'Technischer Hintergrund',
   'faq' => 'FAQ',
   'tech_background_summary' => 'museum-digital:qa nutzt die Komponenten des Import-Tools von museum-digital nach, die zum Auslesen verschiedener Eingabeformate und zur einheitlichen Ansprache der Daten verwendet werden. So unterstützt es neben gängigen Austauschformaten auch die softwarespezifischen Exportformate verschiedener Sammlungsmanagementsysteme und bietet eine Plattform zur Weiterverarbeitung von Museumsdaten aus verschiedensten Quellen. Die so eingelesenen Daten werden in der Folge auf ihre Vollständigkeit und Konsistenz geprüft.',
+  '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ß! 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.',
+  'outlook_text' => 'museum-digital:qa bietet eine Plattform, um Museumsdaten aus verschiedensten Quellen einfach ansprechen und weiterverarbeiten zu können - spezifisch, um sie Tests zur Überprüfung der Datenqualität zu unterziehen. Durch die strikte Trennung der Komponenten - dem Auslesen der Daten einerseits, den Checks andererseits und schließlich der Kommunkation zwischen den eben genannten -   ist es leicht um weitere Tools erweiterbar.
+
+Mit einer OpenAPI-Definition für die Programmierschnittstelle können die durch museum-digital:qa verfügbar gemachten Tools einfach durch Softwareanbieter und Forschende nachgenutzt werden.',
+  'tech_background_text' => 'museum-digital:qa nimmt Daten aus gängigen und konsistent vorliegenden Eingabeformaten entgegen, bringt diese in ein internes, einheitliches Format, um diese schließlich hinsichtlich ihrer Vollständigkeit und Plausibilität auszuwerten. Eingabeformate können einerseits die Ausgabe- und Exportformate von verschiedenen Sammlungsmanagementsystemen, so diese für alle das Programm nutzenden Museen gleich geformt sind, oder die gängigen Austauschformate für Objektdaten sein. 
+
+Die üblichen Sammlungsmanagementsysteme haben verschiedene Ansätze, um mit spezifischen Anpassungen der Datenbank an einzelne Museen umzugehen. Während museum-digital:musdb gezielt keine vom Museum selbst definierten Felder zulässt, um eine konsistente Datenbankgestaltung über Institutionsgrenzen hinweg zu ermöglichen, und so einerseits eine Vielzahl von Auswertungsfunktionen, die auf die Feldauswahl zugeschnitten sind anbieten zu können, und andererseits Export- und Suchfunktionen über mehrere Museen hinweg zu ermöglichen, sind andere Sammlungsmanagementsysteme auch intern deutlich stärker auf die sie nutzenden Museen zugeschnitten. Diese Anpassbarkeit kann entweder auf Ebene der Benutzeroberfläche oder direkt auf der Ebene der Datenbankstruktur vorliegen. Ist auch die Datenbankstruktur anpassbar, heißt das gleichzeitig, dass die Exporte aus derselben Software je nach Museum sehr unterschiedlich geformt sein können. Wo nur die Benutzeroberfläche angepasst wird, gibt es oft softwarespezifische Standard-Exportformate, die über Museumsgrenzen hinweg konsistent geformt, gut gewartet und ggfs. vollständiger als andere Exportoptionen sind (und somit etwa für eine Migration der Daten besonders gut geeignet sind).
+
+Um den Austausch von Daten über Institutions- und Softwaregrenzen hinweg zu vereinfachen, haben sich verschiedene offene (Austausch-)Standards etabliert. Der für Museen sicherlich wichtigste ist dabei LIDO, in angrenzenden Bereichen werden etwa EAD (v.a. Archive) und MODS (v.a. Bibliotheken) verwendet. Diese Standards sind in den meisten Fällen für den Austausch veröffentlichbarer Daten gedacht, decken also in den seltensten Fällen alle lokal vorhandenen Datenfelder ab. Offene Standards sind andererseits in vielen Sammlungsmanagement-Lösungen implementiert. Mit dem 2023 veröffentlichten EODEM sind im Museumsbereich erste Schritte zu erkennen, auch primär interne Daten standardisiert austauschbar zu machen.
+
+Zum Zwecke des Importierens von Daten (sei es zur Migration der Daten für die Inventarisierung oder zur Veröffentlichung) bietet museum-digital ein Import-Tool, das neben den gängigen Austauschformaten auch einige software-spezifische Formate beherrscht (einerseits, weil nicht alle Sammlungsmanagementsysteme die gängigen Austauschformate "von Haus aus" unterstützen, anderseits, weil diese wie oben besprochen oft vollständiger sind). Dieses Import-Tool besteht seinerseits aus drei Komponenten: 1) grundlegenden, für die Museumarbeit relevanten Datentypen (etwa Objekt, Schlagwort, Leihverkehr), 2) Funktionen zum Auslesen von Daten aus den erwähnten Formaten und die Überführung der Eingabedaten in die eben genannten Datentypen, und 3) einem Modul zum tatsächlichen Überführen der Daten in die Datenbank.
+
+Die Importer-Module zur Definition der Datentypen und zum Auslesen der Daten aus verschiedenen Eingabeformaten werden in museum-digital:qa nachgenutzt. So kann museum-digital:qa mit wenigen Anpassungen alle Importformate, die auch der Importer von museum-digital unterstützt, unterstützen (bei museumsspezifischen Importformaten lohnt es sich allerdings nicht, diese Anpassungen zu unternehmen). Ohne relevanten eigenen Code für das Auslesen der eingehenden Daten bleibt museum-digital:qa somit zudem sehr wartungsarm. Umgekehrt bedeutet die Nachnutzung des Auslese-Teils des Importers auch, dass alle Daten, die mit museum-digital:qa auf ihre Qualität überprüft werden können, ohne weitere Anpassungen in museum-digital importiert werden können.
+
+Die eingelesenen Daten liegen in der Folge in einer strukturierten Form vor und können verhältnismäßig einfach weiter verarbeitet werden, indem sie - leicht umformuliert - an die Funktionen zur Überprüfung der Datenqualität weitergegeben werden. Diese Funktionen wurden im Zuge der Arbeit an museum-digital:qa aus museum-digital:musdb in eine eigene Open-Source-Bibliothek ausgelagert.',
+  'go_back' => 'Zurück',
+  'paste_as_text' => 'Als Text einfügen',
+  'licensed_under' => 'Dieses Werk ist lizensiert nach',
+  'reload_application' => 'Anwendung neu laden',
+  'more' => 'Weiteres',
+  'select_check' => 'Bitte wählen Sie die Art der auszuführenden Prüfung',
+  'minimaldatensatz_p1' => 'Die AG Minimaldatensatz hat es sich zum Ziel gesetzt, eine Auswahl von Informationseinheiten zu definieren, die für eine sinnvolle Publikation von Objektdaten zwingend notwendig oder zumindest dringend empfohlen sind. Dabei zielen die Empfehlungen der AG besonders auf die Publikation der Daten in der Deutschen Digitalen Bibliothek (DDB) ab - sie können aber auch darüber hinaus als eine sinnvoller Mindest-Ausgangswert genutzt werden.',
+  'minimaldatensatz_p2' => 'Weil der Kontext der AG Minimaldatensatz spezifisch deutsch ist, sind auch die Rückgabewerte der Prüfung vorerst nur auf Deutsch verfügbar.',
+  'see_also' => 'Siehe auch',
+  'log' => 'Zeitleiste',
+  'launch' => 'Launch',
+  'thanks' => 'Danksagung',
+  'count_new_to_vocabs' => 'Zähler für erwartbar neue Vokabular-Einträge bei museum-digital',
+  'count_new_to_vocabs_short' => 'Zähle unbekannte Vokabulareinträge',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality verbindet die Möglichkeiten des Importtools von museum-digital, verschiedene Formate auszulesen und weiterverarbeitbar zu machen mit verschiedenen Checks. Das heißt auch, dass alle Objektdaten, die mit museum-digital:quality geprüft werden können, gleichzeitig auch ohne größere Probleme zu museum-digital importiert werden könnten.
+
+Ein tatsächlicher Import der Daten bedeutet aber immer auch einen Import der dazugehörigen Vokabulardaten - Akteure, Orte, Zeiten und Schlagworte - in die kontrollierten Vokabulare von museum-digital. Diese müssen im Nachhinein bereinigt und angereichert werden. Mithilfe dieses "Checks" lässt sich die Anzahl der im Falle eines Imports neu importierten Vokabulareinträge ermitteln.',
+  'samples' => 'Beispielhafte Auszüge',
+  'select_activity' => 'Was soll mit den Daten geschehen?',
+  'evaluate' => 'Auswerten',
+  'convert_to_xml' => 'Konvertieren (XML)',
+  'select_conversion_target_format' => 'In welches Format soll konvertiert werden?',
+  'other_features' => 'Weitere Features',
+  'convert_to_xml_explica' => 'museum-digital:qa kann die ursprünglich für XML-Exporte aus musdb geschriebenen XSL-Transformationen nutzen, um hochgeladene Daten in die dort unterstützten Austauschformate zu konvertieren. Hierzu gehört, neben dem etablierten Austauschstandard LIDO, EODEM - ein neues (2023) LIDO-Profil das den Standard um Informationen spezifisch für den Austausch von Objektdaten im Rahmen von Leihverkehren ergänzt.',
 );

en/quality_web.php

@@ -42,4 +42,55 @@ museum-digital:qa allows the (re-)use of these tools by users and software beyon
   'tech_background_hl' => 'Technical background',
   'faq' => 'Frequently Asked Questions',
   'tech_background_summary' => 'museum-digital:qa resuses those components of museum-digital\'s improt tool, which cover the tasks of parsing different input formats and converting them into a uniform format for simple processing. It thus supports reading both well-established open standards for data exchange in the cultural heritage sector as well as the specific export formats of a number of collection management systems to establish a platform for the processing of museum data from a variety of sources. The data thus read are then checked for their completeness and coherence.',
+  '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',
+  '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.',
+  'outlook_text' => 'museum-digital:qa offers a platform to parse and process museum data from a multitude of sources - specifically, to check them for their quality. The strictly modularization of components - the parsing of the data on one hand, the checks themselves on the other, and finally the communication between these two - makes it simple to integrate further tools and checks.
+
+Using the API, specified using the OpenAPI format, researchers and software vendors can easily reuse the tools made accessible through museum-digital:qa.',
+  'tech_background_text' => 'museum-digital:qa accepts data from common and consistent input formats, converts them into an internal, uniform format, and finally evaluates them with regard to their completeness and plausibility. Input formats may either be the software-specific export formats of various collection management systems, if these are formed in the same way across all museums using the same application, or the common open standards for the exchange of museum object data. 
+
+Different collection management systems have different approaches to dealing with the task of customization. While museum-digital:musdb purposefully does not allow museums to freely define fields in order to ensure a consistent database design across institutional boundaries, and thus to be able to offer a variety of evaluation functions tailored to the shared set of data fields on the one hand, and to enable export and search functions across multiple museums on the other hand, other collection management systems allow customization up to the level of defining a fully custom database structure. This customizability may either work on the user interface level or directly at level of the underlying database. If the database structure is also customizable, this simultaneously means that exports from the same software can come in a variety of formats similarly custom to the given museum. Where only the user interface is customizable, there are often software-specific export formats that are consistent across museum boundaries, well maintained, and possibly more complete than other export options (and thus particularly well suited for data migration, for example).
+
+In order to simplify the exchange of data across institutional and software boundaries, various open standards have been developed. The single one most relevant for museums is certainly LIDO; in related areas, EAD (mainly archives) and MODS (mainly libraries) are used. In most cases, these standards are intended for the exchange of publishable data. They thus rarely cover all locally available data fields. Open standards, on the other hand, are implemented in many collection management solutions. With the EODEM published in 2023, early steps towards fascilitating the exchange of primarily internal data have begun to be taken.
+
+For the purpose of importing data (be it for data migration or simply for publication), museum-digital offers an import tool that - in addition to the common exchange formats - also supports some software-specific formats (on the one hand, because not all collection management systems support the common exchange formats "out of the box", on the other hand, because these are often more complete, as discussed above). This import tool, in turn, consists of three components: 1) basic data types relevant to museum work (such as object, keyword, loan), 2) functions for reading data from the aforementioned formats and transferring the input data into the data types just mentioned, and 3) a module for actually transferring the data into the database.
+
+The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
+
+The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
+  'paste_as_text' => 'Paste in plain text',
+  'licensed_under' => 'This work is licensed under',
+  'reload_application' => 'Reload application',
+  'more' => 'More',
+  'select_check' => 'Please select the type of check(s) to run',
+  'minimaldatensatz_p1' => 'The Working Group Minimaldatensatz ("Minimum Viable Object Record") sets out to define a set of basic object information required or highly recommended for a worthwhile publication of objects. Its recommendations are primarily aimed at publishing in the German Digital Library (DDB), but can serve as a sane guideline in other contexts as well.',
+  'minimaldatensatz_p2' => 'As the context of this check is specifically German, the return values of the check are thus far available only in German.',
+  'see_also' => 'See also',
+  'log' => 'Log',
+  'launch' => 'Launch',
+  'thanks' => 'Thanks',
+  'count_new_to_vocabs' => 'Counters for new vocabulary entries at museum-digital',
+  'count_new_to_vocabs_short' => 'Count: new vocabulary entries',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality strings together the parsing of input data of different formats from museum-digital\'s import tool with different checks. That also means that all data that can be checked using museum-digital:quality could be imported to museum-digital as well.
+
+Actually importing the data however regularly also entails adding missing entries to museum-digital\'s controlled vocabularies for actors, places, times, and tags, which need to be cleaned and enriched in the aftermath of the import. Using this check, the number of such newly added entries can be counted.',
+  'samples' => 'Samples',
+  'select_activity' => 'What would you like to do with the data?',
+  'evaluate' => 'Evaluate',
+  'convert_to_xml' => 'Convert to XML',
+  'select_conversion_target_format' => 'Select the target format for conversion',
+  'other_features' => 'Other features',
+  'convert_to_xml_explica' => 'museum-digital:qa can leverage the XSL transformations written for musdb to convert any imported data to those XML formats musdb can export to. Next to the well-established exchange standard LIDO this includes EODEM, a recent extension to LIDO meant to simplify data exchange for registrars specifically in the case of loans between museums.',
 );

hu/quality_web.php

@@ -1,24 +1,28 @@
 <?PHP
 declare(strict_types = 1);
 $quality_web = array (
-  'puqi' => 'Publication Quality Index (PuQI)',
-  'plausi' => 'Plausibility Check',
-  'plausi_legal' => 'Plausibility Check for License Status of Images / Representations',
-  'puqi_explica' => 'The publication quality index measures the completeness and suitability of an object record\'s publishable information. For example, feedback is given on the availability of an object title and a tags. Objects\' descriptions are checked for their length; and linked images\' license status is evaluated. Based on these evaluations, a quantitative score is provided to be able to roughly measure the completeness and quality of an object record for publication.',
-  'plausi_explica' => 'During this check, the objects\' events (production, usage, etc.) are checked for their logical coherence based on the provided times and actors. For example, a bike that has been produced in 1950 cannot have been used in 1870. Similarly, a photograph showing Ice-T (born 1958) cannot have been taken in 1920.',
-  'plausi_explica_2' => 'If such a logical inconsistency between or different events in the object\'s history is detected, a warning will be provided.',
-  'plausi_legal_explica' => 'This check aims to identify and warn about obvious issues concerning the licensing status of an object\'s representations (mainly images). To do so, the life dates of the recorded creators are identified - either directly taken from the provided inputs or via references to central authority files and repositories like the Library of Congress Subject Headings, Wikidata or the Gemeinsame Normdatei of the German National Library. ',
-  'plausi_legal_explica_2' => 'The check is based on the assumption that images of museum objects are meant to be documenting - meaning that in many jurisdictions (such as the EU) no copyright protection is extended to the images themselves. It is thus likely, that images of objects older than 100 years after the death of their creator are in the public domain (here, we are using the maximum number of years by which any country extends copyright protection to a work). If a license status indicating otherwise is provided, a warning will be returned. Similarly, a warning will be displayed if images of objects created by creators who are still alive or have died only within the last 50 years (as per the Berne Convention) have been set under a non-restrictive license. These checks are of course only a rough approximation - laws are complicated and diverse, and so is object data. In sum, it is hoped however, that they cover issues appearing regularly, while not producing too many falsely positive warnings.',
-  'citation' => 'Citation',
-  'puqi_score' => 'PuQI Score',
-  'results' => 'Results',
+  'puqi' => 'Publikációs minőségi index (PuQI)',
+  'plausi' => 'Plauzabilitás ellenőrzés',
+  'plausi_legal' => 'A képek / ábrázolások licenc státuszának plauzibilitási ellenőrzése',
+  'puqi_explica' => 'A publlikációs minőségi index (Publication Quality Index - PuQI) egy rekord publikálható információinak teljességét és megfelelőségét méri. Például visszajelzést ad a tárgy megnevezésének és kulcsszavainak elérhetőségéről. A tárgyak leírásának hosszát ellenőrzi; és értékeli a képek licencstátuszát. Ezen értékelések alapján egy mennyiségi pontszámot ad meg annak érdekében, hogy nagyjából mérni tudjuk egy műtárgy metaadatainak a teljességét a minőségi közzétételhez.',
+  'plausi_explica' => 'Ellenőrzés során a tárgyak eseményeit (készítés, felhasználás stb.) vizsgáljuk logikai összefüggésük szempontjából a megadott időpontok és szereplők alapján. Például egy 1950-ben gyártott kerékpár nem lehetett használatban 1870-ben. Hasonlóképpen, egy fénykép, amelyen Ice-T (született 1958) szerepel, nem készülhetett 1920-ban.',
+  'plausi_explica_2' => 'Ha a tárgynál hasonló logikai ellentmondás vagy eltérés kerül felismerésre az egyes események között, figyelmeztetés jelenik meg.',
+  'plausi_legal_explica' => 'Az ellenőrzés célja, hogy a tárgyhoz feltöltött képek licencelési állapotával kapcsolatos nyilvánvaló problémákat azonosítsa és jelezze. Ennek érdekében a rögzített alkotók életrajzi adatait határozza meg – akár közvetlenül a megadott adatokból, olyan központi adatbázisokra hivatkozva, mint például a Library of Congress Subject Headings, a Wikidata vagy a Német Nemzeti Könyvtár Gemeinsame Normdatei rendszere.',
+  'plausi_legal_explica_2' => 'Az ellenőrzés azon a feltételezésen alapul, hogy a múzeumi tárgyakról készült képek dokumentációs célt szolgálnak – vagyis sok joghatóságban (például az EU-ban) maguk a képek nem részesülnek szerzői jogi védelemben. Ennek megfelelően valószínűsíthető, hogy azoknak a tárgyaknak a képei, amelyek alkotója több mint 100 éve elhunyt, közkincsnek minősülnek (itt a leghosszabb időtartamot vesszük figyelembe, amelyet bármely ország egy mű szerzői jogi védelmére alkalmaz). Ha ettől eltérő licencstátusz szerepel, figyelmeztetés jelenik meg.
+
+Hasonlóképpen, figyelmeztetés jelenik meg akkor is, ha olyan alkotók által létrehozott tárgyakról készült képeket, akik még élnek, vagy az elmúlt 50 évben hunytak el (a Berni Egyezmény alapján), nem korlátozó licenccel láttak el.
+
+Ezek az ellenőrzések természetesen csak egy durva közelítést adnak – a jogszabályok bonyolultak és sokfélék, ahogyan az objektumadatok is. Összességében azonban remélhető, hogy segítenek az ismétlődő problémák felismerésében, miközben nem generálnak túl sok téves figyelmeztetést.',
+  'citation' => 'Hivatkzoás',
+  'puqi_score' => 'PuQI érték',
+  'results' => 'Találatok',
   'objects_identified' => '[placeholder_for_count] objects identified',
   'check_passed' => 'Check passed',
-  'warning' => 'Warning',
-  'status' => 'Status',
-  'plausibility_warnings' => 'Plausibility Check: Warnings',
+  'warning' => 'Figyelmeztetés',
+  'status' => 'Státusz',
+  'plausibility_warnings' => 'Plauzabilitás: Figyelmeztetések',
   'plausibility_warnings_licenses' => 'Plausibility Check for Image Licenses: Warnings',
-  'puqi_notices' => 'PuQI Messages',
+  'puqi_notices' => 'PuQI üzenetek',
   'types_of_evaluations' => 'Types of Evaluations',
   'see' => 'See',
   'step' => 'Step',
@@ -26,7 +30,7 @@ $quality_web = array (
   'upload_a_file' => 'Upload a file',
   'select_file_for_upload' => 'Select a file for upload',
   'alt_paste_text' => 'Or Paste the Object Record in Plain Text',
-  'text' => 'Text',
+  'text' => 'Szöveg',
   'submit' => 'Submit',
   'news' => 'News',
   'click_read_more' => 'Click to read more',
@@ -42,4 +46,55 @@ museum-digital:qa allows the (re-)use of these tools by users and software beyon
   'tech_background_hl' => 'Technical background',
   'faq' => 'Frequently Asked Questions',
   'tech_background_summary' => 'museum-digital:qa resuses those components of museum-digital\'s improt tool, which cover the tasks of parsing different input formats and converting them into a uniform format for simple processing. It thus supports reading both well-established open standards for data exchange in the cultural heritage sector as well as the specific export formats of a number of collection management systems to establish a platform for the processing of museum data from a variety of sources. The data thus read are then checked for their completeness and coherence.',
+  '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',
+  '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.',
+  'outlook_text' => 'museum-digital:qa offers a platform to parse and process museum data from a multitude of sources - specifically, to check them for their quality. The strictly modularization of components - the parsing of the data on one hand, the checks themselves on the other, and finally the communication between these two - makes it simple to integrate further tools and checks.
+
+Using the API, specified using the OpenAPI format, researchers and software vendors can easily reuse the tools made accessible through museum-digital:qa.',
+  'tech_background_text' => 'museum-digital:qa accepts data from common and consistent input formats, converts them into an internal, uniform format, and finally evaluates them with regard to their completeness and plausibility. Input formats may either be the software-specific export formats of various collection management systems, if these are formed in the same way across all museums using the same application, or the common open standards for the exchange of museum object data. 
+
+Different collection management systems have different approaches to dealing with the task of customization. While museum-digital:musdb purposefully does not allow museums to freely define fields in order to ensure a consistent database design across institutional boundaries, and thus to be able to offer a variety of evaluation functions tailored to the shared set of data fields on the one hand, and to enable export and search functions across multiple museums on the other hand, other collection management systems allow customization up to the level of defining a fully custom database structure. This customizability may either work on the user interface level or directly at level of the underlying database. If the database structure is also customizable, this simultaneously means that exports from the same software can come in a variety of formats similarly custom to the given museum. Where only the user interface is customizable, there are often software-specific export formats that are consistent across museum boundaries, well maintained, and possibly more complete than other export options (and thus particularly well suited for data migration, for example).
+
+In order to simplify the exchange of data across institutional and software boundaries, various open standards have been developed. The single one most relevant for museums is certainly LIDO; in related areas, EAD (mainly archives) and MODS (mainly libraries) are used. In most cases, these standards are intended for the exchange of publishable data. They thus rarely cover all locally available data fields. Open standards, on the other hand, are implemented in many collection management solutions. With the EODEM published in 2023, early steps towards fascilitating the exchange of primarily internal data have begun to be taken.
+
+For the purpose of importing data (be it for data migration or simply for publication), museum-digital offers an import tool that - in addition to the common exchange formats - also supports some software-specific formats (on the one hand, because not all collection management systems support the common exchange formats "out of the box", on the other hand, because these are often more complete, as discussed above). This import tool, in turn, consists of three components: 1) basic data types relevant to museum work (such as object, keyword, loan), 2) functions for reading data from the aforementioned formats and transferring the input data into the data types just mentioned, and 3) a module for actually transferring the data into the database.
+
+The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
+
+The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
+  'paste_as_text' => 'Paste in plain text',
+  'licensed_under' => 'This work is licensed under',
+  'reload_application' => 'Reload application',
+  'more' => 'More',
+  'select_check' => 'Please select the type of check(s) to run',
+  'minimaldatensatz_p1' => 'The Working Group Minimaldatensatz ("Minimum Viable Object Record") sets out to define a set of basic object information required or highly recommended for a worthwhile publication of objects. Its recommendations are primarily aimed at publishing in the German Digital Library (DDB), but can serve as a sane guideline in other contexts as well.',
+  'minimaldatensatz_p2' => 'As the context of this check is specifically German, the return values of the check are thus far available only in German.',
+  'see_also' => 'See also',
+  'log' => 'Log',
+  'launch' => 'Launch',
+  'thanks' => 'Thanks',
+  'count_new_to_vocabs' => 'Counters for new vocabulary entries at museum-digital',
+  'count_new_to_vocabs_short' => 'Count: new vocabulary entries',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality strings together the parsing of input data of different formats from museum-digital\'s import tool with different checks. That also means that all data that can be checked using museum-digital:quality could be imported to museum-digital as well.
+
+Actually importing the data however regularly also entails adding missing entries to museum-digital\'s controlled vocabularies for actors, places, times, and tags, which need to be cleaned and enriched in the aftermath of the import. Using this check, the number of such newly added entries can be counted.',
+  'samples' => 'Samples',
+  'select_activity' => 'What would you like to do with the data?',
+  'evaluate' => 'Evaluate',
+  'convert_to_xml' => 'Convert to XML',
+  'select_conversion_target_format' => 'Select the target format for conversion',
+  'other_features' => 'Other features',
+  'convert_to_xml_explica' => 'museum-digital:qa can leverage the XSL transformations written for musdb to convert any imported data to those XML formats musdb can export to. Next to the well-established exchange standard LIDO this includes EODEM, a recent extension to LIDO meant to simplify data exchange for registrars specifically in the case of loans between museums.',
 );

kn/quality_web.php

@@ -0,0 +1,96 @@
+<?PHP
+declare(strict_types = 1);
+$quality_web = array (
+  'puqi' => 'Publication Quality Index (PuQI)',
+  'plausi' => 'Plausibility Check',
+  'plausi_legal' => 'Plausibility Check for License Status of Images / Representations',
+  'puqi_explica' => 'The publication quality index measures the completeness and suitability of an object record\'s publishable information. For example, feedback is given on the availability of an object title and a tags. Objects\' descriptions are checked for their length; and linked images\' license status is evaluated. Based on these evaluations, a quantitative score is provided to be able to roughly measure the completeness and quality of an object record for publication.',
+  'plausi_explica' => 'During this check, the objects\' events (production, usage, etc.) are checked for their logical coherence based on the provided times and actors. For example, a bike that has been produced in 1950 cannot have been used in 1870. Similarly, a photograph showing Ice-T (born 1958) cannot have been taken in 1920.',
+  'plausi_explica_2' => 'If such a logical inconsistency between or different events in the object\'s history is detected, a warning will be provided.',
+  'plausi_legal_explica' => 'This check aims to identify and warn about obvious issues concerning the licensing status of an object\'s representations (mainly images). To do so, the life dates of the recorded creators are identified - either directly taken from the provided inputs or via references to central authority files and repositories like the Library of Congress Subject Headings, Wikidata or the Gemeinsame Normdatei of the German National Library. ',
+  'plausi_legal_explica_2' => 'The check is based on the assumption that images of museum objects are meant to be documenting - meaning that in many jurisdictions (such as the EU) no copyright protection is extended to the images themselves. It is thus likely, that images of objects older than 100 years after the death of their creator are in the public domain (here, we are using the maximum number of years by which any country extends copyright protection to a work). If a license status indicating otherwise is provided, a warning will be returned. Similarly, a warning will be displayed if images of objects created by creators who are still alive or have died only within the last 50 years (as per the Berne Convention) have been set under a non-restrictive license. These checks are of course only a rough approximation - laws are complicated and diverse, and so is object data. In sum, it is hoped however, that they cover issues appearing regularly, while not producing too many falsely positive warnings.',
+  'citation' => 'Citation',
+  'puqi_score' => 'PuQI Score',
+  'results' => 'Results',
+  'objects_identified' => '[placeholder_for_count] objects identified',
+  'check_passed' => 'Check passed',
+  'warning' => 'Warning',
+  'status' => 'Status',
+  'plausibility_warnings' => 'Plausibility Check: Warnings',
+  'plausibility_warnings_licenses' => 'Plausibility Check for Image Licenses: Warnings',
+  'puqi_notices' => 'PuQI Messages',
+  'types_of_evaluations' => 'Types of Evaluations',
+  'see' => 'See',
+  'step' => 'Step',
+  'select_import_format' => 'Select an import format',
+  'upload_a_file' => 'Upload a file',
+  'select_file_for_upload' => 'Select a file for upload',
+  'alt_paste_text' => 'Or Paste the Object Record in Plain Text',
+  'text' => 'Text',
+  'submit' => 'Submit',
+  'news' => 'News',
+  'click_read_more' => 'Click to read more',
+  'try_it_out' => 'Try it out',
+  'intro_text' => 'Since the 1980s, more and more museums have started managing their object data digitally. Where inventory cards oftentimes only covered the most rudimentary information systematically, digital record-keeping allows for a much more detailled description of the objects without any of the space limitations inherent to the medium of the inventory card. Detailed information that had often only been written down unsystematically in catalogues or research articles can now be stored and searched digitally alongside the rudimentary object data in a database. Simultaneously, an increasing number of museums has started to publish their collections in publicly accessible databases, often in collaboration with other museums, which have entirely different collections.
+
+A coverage of the collections that is at the same time systematic and detailled has thus only really been possible due to digitization. The increasingly close link between inventorization and publication of the object data on the other hand makes data quality more relevant than ever.
+
+museum-digital has helped museums and related institutions in collaboratively managing and publishing their collections online since 2009. In this context, a number of tools were written to measure and improve the quality of collection data.
+
+museum-digital:qa allows the (re-)use of these tools by users and software beyond museum-digital. They may be used directly via a web interface or via an API, which also allows for the simple embedding of the quality assessment tools into other collection management systems, which often do not feature comparable tools as of yet.',
+  'summary' => 'Summary',
+  'tech_background_hl' => 'Technical background',
+  'faq' => 'Frequently Asked Questions',
+  'tech_background_summary' => 'museum-digital:qa resuses those components of museum-digital\'s improt tool, which cover the tasks of parsing different input formats and converting them into a uniform format for simple processing. It thus supports reading both well-established open standards for data exchange in the cultural heritage sector as well as the specific export formats of a number of collection management systems to establish a platform for the processing of museum data from a variety of sources. The data thus read are then checked for their completeness and coherence.',
+  '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',
+  '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.',
+  'outlook_text' => 'museum-digital:qa offers a platform to parse and process museum data from a multitude of sources - specifically, to check them for their quality. The strictly modularization of components - the parsing of the data on one hand, the checks themselves on the other, and finally the communication between these two - makes it simple to integrate further tools and checks.
+
+Using the API, specified using the OpenAPI format, researchers and software vendors can easily reuse the tools made accessible through museum-digital:qa.',
+  'tech_background_text' => 'museum-digital:qa accepts data from common and consistent input formats, converts them into an internal, uniform format, and finally evaluates them with regard to their completeness and plausibility. Input formats may either be the software-specific export formats of various collection management systems, if these are formed in the same way across all museums using the same application, or the common open standards for the exchange of museum object data. 
+
+Different collection management systems have different approaches to dealing with the task of customization. While museum-digital:musdb purposefully does not allow museums to freely define fields in order to ensure a consistent database design across institutional boundaries, and thus to be able to offer a variety of evaluation functions tailored to the shared set of data fields on the one hand, and to enable export and search functions across multiple museums on the other hand, other collection management systems allow customization up to the level of defining a fully custom database structure. This customizability may either work on the user interface level or directly at level of the underlying database. If the database structure is also customizable, this simultaneously means that exports from the same software can come in a variety of formats similarly custom to the given museum. Where only the user interface is customizable, there are often software-specific export formats that are consistent across museum boundaries, well maintained, and possibly more complete than other export options (and thus particularly well suited for data migration, for example).
+
+In order to simplify the exchange of data across institutional and software boundaries, various open standards have been developed. The single one most relevant for museums is certainly LIDO; in related areas, EAD (mainly archives) and MODS (mainly libraries) are used. In most cases, these standards are intended for the exchange of publishable data. They thus rarely cover all locally available data fields. Open standards, on the other hand, are implemented in many collection management solutions. With the EODEM published in 2023, early steps towards fascilitating the exchange of primarily internal data have begun to be taken.
+
+For the purpose of importing data (be it for data migration or simply for publication), museum-digital offers an import tool that - in addition to the common exchange formats - also supports some software-specific formats (on the one hand, because not all collection management systems support the common exchange formats "out of the box", on the other hand, because these are often more complete, as discussed above). This import tool, in turn, consists of three components: 1) basic data types relevant to museum work (such as object, keyword, loan), 2) functions for reading data from the aforementioned formats and transferring the input data into the data types just mentioned, and 3) a module for actually transferring the data into the database.
+
+The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
+
+The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
+  'paste_as_text' => 'Paste in plain text',
+  'licensed_under' => 'This work is licensed under',
+  'reload_application' => 'Reload application',
+  'more' => 'More',
+  'select_check' => 'Please select the type of check(s) to run',
+  'minimaldatensatz_p1' => 'The Working Group Minimaldatensatz ("Minimum Viable Object Record") sets out to define a set of basic object information required or highly recommended for a worthwhile publication of objects. Its recommendations are primarily aimed at publishing in the German Digital Library (DDB), but can serve as a sane guideline in other contexts as well.',
+  'minimaldatensatz_p2' => 'As the context of this check is specifically German, the return values of the check are thus far available only in German.',
+  'see_also' => 'See also',
+  'log' => 'Log',
+  'launch' => 'Launch',
+  'thanks' => 'Thanks',
+  'count_new_to_vocabs' => 'Counters for new vocabulary entries at museum-digital',
+  'count_new_to_vocabs_short' => 'Count: new vocabulary entries',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality strings together the parsing of input data of different formats from museum-digital\'s import tool with different checks. That also means that all data that can be checked using museum-digital:quality could be imported to museum-digital as well.
+
+Actually importing the data however regularly also entails adding missing entries to museum-digital\'s controlled vocabularies for actors, places, times, and tags, which need to be cleaned and enriched in the aftermath of the import. Using this check, the number of such newly added entries can be counted.',
+  'samples' => 'Samples',
+  'select_activity' => 'What would you like to do with the data?',
+  'evaluate' => 'Evaluate',
+  'convert_to_xml' => 'Convert to XML',
+  'select_conversion_target_format' => 'Select the target format for conversion',
+  'other_features' => 'Other features',
+  'convert_to_xml_explica' => 'museum-digital:qa can leverage the XSL transformations written for musdb to convert any imported data to those XML formats musdb can export to. Next to the well-established exchange standard LIDO this includes EODEM, a recent extension to LIDO meant to simplify data exchange for registrars specifically in the case of loans between museums.',
+);

ro/quality_web.php

@@ -0,0 +1,96 @@
+<?PHP
+declare(strict_types = 1);
+$quality_web = array (
+  'puqi' => 'Publication Quality Index (PuQI)',
+  'plausi' => 'Plausibility Check',
+  'plausi_legal' => 'Plausibility Check for License Status of Images / Representations',
+  'puqi_explica' => 'The publication quality index measures the completeness and suitability of an object record\'s publishable information. For example, feedback is given on the availability of an object title and a tags. Objects\' descriptions are checked for their length; and linked images\' license status is evaluated. Based on these evaluations, a quantitative score is provided to be able to roughly measure the completeness and quality of an object record for publication.',
+  'plausi_explica' => 'During this check, the objects\' events (production, usage, etc.) are checked for their logical coherence based on the provided times and actors. For example, a bike that has been produced in 1950 cannot have been used in 1870. Similarly, a photograph showing Ice-T (born 1958) cannot have been taken in 1920.',
+  'plausi_explica_2' => 'If such a logical inconsistency between or different events in the object\'s history is detected, a warning will be provided.',
+  'plausi_legal_explica' => 'This check aims to identify and warn about obvious issues concerning the licensing status of an object\'s representations (mainly images). To do so, the life dates of the recorded creators are identified - either directly taken from the provided inputs or via references to central authority files and repositories like the Library of Congress Subject Headings, Wikidata or the Gemeinsame Normdatei of the German National Library. ',
+  'plausi_legal_explica_2' => 'The check is based on the assumption that images of museum objects are meant to be documenting - meaning that in many jurisdictions (such as the EU) no copyright protection is extended to the images themselves. It is thus likely, that images of objects older than 100 years after the death of their creator are in the public domain (here, we are using the maximum number of years by which any country extends copyright protection to a work). If a license status indicating otherwise is provided, a warning will be returned. Similarly, a warning will be displayed if images of objects created by creators who are still alive or have died only within the last 50 years (as per the Berne Convention) have been set under a non-restrictive license. These checks are of course only a rough approximation - laws are complicated and diverse, and so is object data. In sum, it is hoped however, that they cover issues appearing regularly, while not producing too many falsely positive warnings.',
+  'citation' => 'Citation',
+  'puqi_score' => 'PuQI Score',
+  'results' => 'Results',
+  'objects_identified' => '[placeholder_for_count] objects identified',
+  'check_passed' => 'Check passed',
+  'warning' => 'Warning',
+  'status' => 'Status',
+  'plausibility_warnings' => 'Plausibility Check: Warnings',
+  'plausibility_warnings_licenses' => 'Plausibility Check for Image Licenses: Warnings',
+  'puqi_notices' => 'PuQI Messages',
+  'types_of_evaluations' => 'Types of Evaluations',
+  'see' => 'See',
+  'step' => 'Step',
+  'select_import_format' => 'Select an import format',
+  'upload_a_file' => 'Upload a file',
+  'select_file_for_upload' => 'Select a file for upload',
+  'alt_paste_text' => 'Or Paste the Object Record in Plain Text',
+  'text' => 'Text',
+  'submit' => 'Submit',
+  'news' => 'News',
+  'click_read_more' => 'Click to read more',
+  'try_it_out' => 'Try it out',
+  'intro_text' => 'Since the 1980s, more and more museums have started managing their object data digitally. Where inventory cards oftentimes only covered the most rudimentary information systematically, digital record-keeping allows for a much more detailled description of the objects without any of the space limitations inherent to the medium of the inventory card. Detailed information that had often only been written down unsystematically in catalogues or research articles can now be stored and searched digitally alongside the rudimentary object data in a database. Simultaneously, an increasing number of museums has started to publish their collections in publicly accessible databases, often in collaboration with other museums, which have entirely different collections.
+
+A coverage of the collections that is at the same time systematic and detailled has thus only really been possible due to digitization. The increasingly close link between inventorization and publication of the object data on the other hand makes data quality more relevant than ever.
+
+museum-digital has helped museums and related institutions in collaboratively managing and publishing their collections online since 2009. In this context, a number of tools were written to measure and improve the quality of collection data.
+
+museum-digital:qa allows the (re-)use of these tools by users and software beyond museum-digital. They may be used directly via a web interface or via an API, which also allows for the simple embedding of the quality assessment tools into other collection management systems, which often do not feature comparable tools as of yet.',
+  'summary' => 'Summary',
+  'tech_background_hl' => 'Technical background',
+  'faq' => 'Frequently Asked Questions',
+  'tech_background_summary' => 'museum-digital:qa resuses those components of museum-digital\'s improt tool, which cover the tasks of parsing different input formats and converting them into a uniform format for simple processing. It thus supports reading both well-established open standards for data exchange in the cultural heritage sector as well as the specific export formats of a number of collection management systems to establish a platform for the processing of museum data from a variety of sources. The data thus read are then checked for their completeness and coherence.',
+  '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',
+  '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.',
+  'outlook_text' => 'museum-digital:qa offers a platform to parse and process museum data from a multitude of sources - specifically, to check them for their quality. The strictly modularization of components - the parsing of the data on one hand, the checks themselves on the other, and finally the communication between these two - makes it simple to integrate further tools and checks.
+
+Using the API, specified using the OpenAPI format, researchers and software vendors can easily reuse the tools made accessible through museum-digital:qa.',
+  'tech_background_text' => 'museum-digital:qa accepts data from common and consistent input formats, converts them into an internal, uniform format, and finally evaluates them with regard to their completeness and plausibility. Input formats may either be the software-specific export formats of various collection management systems, if these are formed in the same way across all museums using the same application, or the common open standards for the exchange of museum object data. 
+
+Different collection management systems have different approaches to dealing with the task of customization. While museum-digital:musdb purposefully does not allow museums to freely define fields in order to ensure a consistent database design across institutional boundaries, and thus to be able to offer a variety of evaluation functions tailored to the shared set of data fields on the one hand, and to enable export and search functions across multiple museums on the other hand, other collection management systems allow customization up to the level of defining a fully custom database structure. This customizability may either work on the user interface level or directly at level of the underlying database. If the database structure is also customizable, this simultaneously means that exports from the same software can come in a variety of formats similarly custom to the given museum. Where only the user interface is customizable, there are often software-specific export formats that are consistent across museum boundaries, well maintained, and possibly more complete than other export options (and thus particularly well suited for data migration, for example).
+
+In order to simplify the exchange of data across institutional and software boundaries, various open standards have been developed. The single one most relevant for museums is certainly LIDO; in related areas, EAD (mainly archives) and MODS (mainly libraries) are used. In most cases, these standards are intended for the exchange of publishable data. They thus rarely cover all locally available data fields. Open standards, on the other hand, are implemented in many collection management solutions. With the EODEM published in 2023, early steps towards fascilitating the exchange of primarily internal data have begun to be taken.
+
+For the purpose of importing data (be it for data migration or simply for publication), museum-digital offers an import tool that - in addition to the common exchange formats - also supports some software-specific formats (on the one hand, because not all collection management systems support the common exchange formats "out of the box", on the other hand, because these are often more complete, as discussed above). This import tool, in turn, consists of three components: 1) basic data types relevant to museum work (such as object, keyword, loan), 2) functions for reading data from the aforementioned formats and transferring the input data into the data types just mentioned, and 3) a module for actually transferring the data into the database.
+
+The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
+
+The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
+  'paste_as_text' => 'Paste in plain text',
+  'licensed_under' => 'This work is licensed under',
+  'reload_application' => 'Reload application',
+  'more' => 'More',
+  'select_check' => 'Please select the type of check(s) to run',
+  'minimaldatensatz_p1' => 'The Working Group Minimaldatensatz ("Minimum Viable Object Record") sets out to define a set of basic object information required or highly recommended for a worthwhile publication of objects. Its recommendations are primarily aimed at publishing in the German Digital Library (DDB), but can serve as a sane guideline in other contexts as well.',
+  'minimaldatensatz_p2' => 'As the context of this check is specifically German, the return values of the check are thus far available only in German.',
+  'see_also' => 'See also',
+  'log' => 'Log',
+  'launch' => 'Launch',
+  'thanks' => 'Thanks',
+  'count_new_to_vocabs' => 'Counters for new vocabulary entries at museum-digital',
+  'count_new_to_vocabs_short' => 'Count: new vocabulary entries',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality strings together the parsing of input data of different formats from museum-digital\'s import tool with different checks. That also means that all data that can be checked using museum-digital:quality could be imported to museum-digital as well.
+
+Actually importing the data however regularly also entails adding missing entries to museum-digital\'s controlled vocabularies for actors, places, times, and tags, which need to be cleaned and enriched in the aftermath of the import. Using this check, the number of such newly added entries can be counted.',
+  'samples' => 'Samples',
+  'select_activity' => 'What would you like to do with the data?',
+  'evaluate' => 'Evaluate',
+  'convert_to_xml' => 'Convert to XML',
+  'select_conversion_target_format' => 'Select the target format for conversion',
+  'other_features' => 'Other features',
+  'convert_to_xml_explica' => 'museum-digital:qa can leverage the XSL transformations written for musdb to convert any imported data to those XML formats musdb can export to. Next to the well-established exchange standard LIDO this includes EODEM, a recent extension to LIDO meant to simplify data exchange for registrars specifically in the case of loans between museums.',
+);

ru/quality_web.php

@@ -1,45 +1,97 @@
 <?PHP
 declare(strict_types = 1);
 $quality_web = array (
-  'puqi' => 'Publication Quality Index (PuQI)',
-  'plausi' => 'Plausibility Check',
-  'plausi_legal' => 'Plausibility Check for License Status of Images / Representations',
-  'puqi_explica' => 'The publication quality index measures the completeness and suitability of an object record\'s publishable information. For example, feedback is given on the availability of an object title and a tags. Objects\' descriptions are checked for their length; and linked images\' license status is evaluated. Based on these evaluations, a quantitative score is provided to be able to roughly measure the completeness and quality of an object record for publication.',
-  'plausi_explica' => 'During this check, the objects\' events (production, usage, etc.) are checked for their logical coherence based on the provided times and actors. For example, a bike that has been produced in 1950 cannot have been used in 1870. Similarly, a photograph showing Ice-T (born 1958) cannot have been taken in 1920.',
-  'plausi_explica_2' => 'If such a logical inconsistency between or different events in the object\'s history is detected, a warning will be provided.',
-  'plausi_legal_explica' => 'This check aims to identify and warn about obvious issues concerning the licensing status of an object\'s representations (mainly images). To do so, the life dates of the recorded creators are identified - either directly taken from the provided inputs or via references to central authority files and repositories like the Library of Congress Subject Headings, Wikidata or the Gemeinsame Normdatei of the German National Library. ',
-  'plausi_legal_explica_2' => 'The check is based on the assumption that images of museum objects are meant to be documenting - meaning that in many jurisdictions (such as the EU) no copyright protection is extended to the images themselves. It is thus likely, that images of objects older than 100 years after the death of their creator are in the public domain (here, we are using the maximum number of years by which any country extends copyright protection to a work). If a license status indicating otherwise is provided, a warning will be returned. Similarly, a warning will be displayed if images of objects created by creators who are still alive or have died only within the last 50 years (as per the Berne Convention) have been set under a non-restrictive license. These checks are of course only a rough approximation - laws are complicated and diverse, and so is object data. In sum, it is hoped however, that they cover issues appearing regularly, while not producing too many falsely positive warnings.',
-  'citation' => 'Citation',
-  'puqi_score' => 'PuQI Score',
-  'results' => 'Results',
-  'objects_identified' => '[placeholder_for_count] objects identified',
-  'check_passed' => 'Check passed',
-  'warning' => 'Warning',
-  'status' => 'Status',
-  'plausibility_warnings' => 'Plausibility Check: Warnings',
-  'plausibility_warnings_licenses' => 'Plausibility Check for Image Licenses: Warnings',
-  'puqi_notices' => 'PuQI Messages',
-  'types_of_evaluations' => 'Types of Evaluations',
-  'see' => 'See',
-  'step' => 'Step',
-  'select_import_format' => 'Select an import format',
-  'upload_a_file' => 'Upload a file',
-  'select_file_for_upload' => 'Select a file for upload',
-  'alt_paste_text' => 'Or Paste the Object Record in Plain Text',
-  'text' => 'Text',
-  'submit' => 'Submit',
-  'news' => 'News',
-  'click_read_more' => 'Click to read more',
-  'try_it_out' => 'Try it out',
-  'intro_text' => 'Since the 1980s, more and more museums have started managing their object data digitally. Where inventory cards oftentimes only covered the most rudimentary information systematically, digital record-keeping allows for a much more detailled description of the objects without any of the space limitations inherent to the medium of the inventory card. Detailed information that had often only been written down unsystematically in catalogues or research articles can now be stored and searched digitally alongside the rudimentary object data in a database. Simultaneously, an increasing number of museums has started to publish their collections in publicly accessible databases, often in collaboration with other museums, which have entirely different collections.
+  'puqi' => 'Индекс качества публикаций (PuQI)',
+  'plausi' => 'Проверка на правдоподобность',
+  'plausi_legal' => 'Проверка правдоподобности лицензионного статуса изображений/представлений',
+  'puqi_explica' => 'Индекс качества публикации измеряет полноту и пригодность информации об объекте для публикации. Например, оценивается наличие названия объекта и тегов. Проверяется длина описаний объектов; оценивается лицензионный статус связанных изображений. На основе этих оценок выставляется количественный балл, позволяющий приблизительно оценить полноту и качество записи объекта для публикации.',
+  'plausi_explica' => 'В ходе этой проверки события объектов (производство, использование и т. д.) проверяются на логическую связность на основе предоставленных времен и действующих лиц. Например, велосипед, произведенный в 1950 году, не мог быть использован в 1870 году. Аналогично, фотография, на которой изображен Айс-Ти (1958 года рождения), не может быть сделана в 1920 году.',
+  'plausi_explica_2' => 'Если будет обнаружено логическое несоответствие между событиями или разными событиями в истории объекта, будет выдано предупреждение.',
+  'plausi_legal_explica' => 'Эта проверка направлена на выявление и предупреждение очевидных проблем, связанных с лицензионным статусом репрезентаций объекта (в основном изображений). Для этого определяются даты жизни записанных создателей - либо непосредственно из предоставленных данных, либо через ссылки на центральные авторитетные файлы и хранилища, такие как Предметные рубрики Библиотеки Конгресса США, Викиданные или Gemeinsame Normdatei Немецкой национальной библиотеки. ',
+  'plausi_legal_explica_2' => 'Проверка основана на предположении, что изображения музейных предметов предназначены для документирования - это означает, что во многих юрисдикциях (например, в ЕС) на сами изображения не распространяется защита авторских прав. Поэтому вполне вероятно, что изображения объектов старше 100 лет после смерти их создателя являются общественным достоянием (здесь мы используем максимальное количество лет, на которое любая страна распространяет защиту авторских прав на произведение). Если указан статус лицензии, указывающий на обратное, будет выдано предупреждение. Аналогично, предупреждение будет выдано, если изображения объектов, созданных авторами, которые еще живы или умерли только в течение последних 50 лет (согласно Бернской конвенции), были установлены под неограничительной лицензией. Конечно, эти проверки являются лишь грубым приближением - законы сложны и разнообразны, как и данные об объектах. В целом можно надеяться, что они охватывают вопросы, возникающие регулярно, и при этом не дают слишком много ложноположительных предупреждений.',
+  'citation' => 'Цитата',
+  'puqi_score' => 'Показатель PuQI',
+  'results' => 'Результаты',
+  'objects_identified' => '[placeholder_for_count] идентифицированных объектов',
+  'check_passed' => 'Проверка пройдена',
+  'warning' => 'Предупреждение',
+  'status' => 'Статус',
+  'plausibility_warnings' => 'Проверка правдоподобности: Предупреждения',
+  'plausibility_warnings_licenses' => 'Проверка правдоподобности лицензий на изображения: Предупреждения',
+  'puqi_notices' => 'Сообщения PuQI',
+  'types_of_evaluations' => 'Виды оценок',
+  'see' => 'См.',
+  'step' => 'Шаг',
+  'select_import_format' => 'Выберите формат импорта',
+  'upload_a_file' => 'Загрузить файл',
+  'select_file_for_upload' => 'Выберите файл для загрузки',
+  'alt_paste_text' => 'Или вставьте запись об объекте в виде обычного текста',
+  'text' => 'Текст',
+  'submit' => 'Отправить',
+  'news' => 'Новости',
+  'click_read_more' => 'Нажмите, чтобы узнать больше',
+  'try_it_out' => 'Попробуйте',
+  'intro_text' => 'С 1980-х годов все больше музеев начинают вести учет своих предметов в цифровом формате. Если инвентарные карточки зачастую систематически отражали лишь самую элементарную информацию, то цифровой учет позволяет составить гораздо более подробное описание предметов без каких-либо ограничений по объему, присущих инвентарным карточкам. Подробная информация, которая раньше часто лишь бессистемно записывалась в каталоги или исследовательские статьи, теперь может храниться и искаться в цифровом виде наряду с простейшими данными об объектах в базе данных. Одновременно все большее число музеев начинает публиковать свои коллекции в общедоступных базах данных, часто в сотрудничестве с другими музеями, обладающими совсем другими собраниями.
 
-A coverage of the collections that is at the same time systematic and detailled has thus only really been possible due to digitization. The increasingly close link between inventorization and publication of the object data on the other hand makes data quality more relevant than ever.
+Таким образом, охват собраний, который одновременно является систематическим и подробным, стал возможен только благодаря оцифровке. С другой стороны, все более тесная связь между инвентаризацией и публикацией данных о предметах делает качество данных как никогда актуальным. 
 
-museum-digital has helped museums and related institutions in collaboratively managing and publishing their collections online since 2009. In this context, a number of tools were written to measure and improve the quality of collection data.
+С 2009 года museum-digital помогает музеям и смежным учреждениям совместно управлять своими коллекциями и публиковать их в Интернете. В связи с этим был создан ряд инструментов для измерения и улучшения качества данных о коллекциях. 
 
-museum-digital:qa allows the (re-)use of these tools by users and software beyond museum-digital. They may be used directly via a web interface or via an API, which also allows for the simple embedding of the quality assessment tools into other collection management systems, which often do not feature comparable tools as of yet.',
-  'summary' => 'Summary',
-  'tech_background_hl' => 'Technical background',
-  'faq' => 'Frequently Asked Questions',
-  'tech_background_summary' => 'museum-digital:qa resuses those components of museum-digital\'s improt tool, which cover the tasks of parsing different input formats and converting them into a uniform format for simple processing. It thus supports reading both well-established open standards for data exchange in the cultural heritage sector as well as the specific export formats of a number of collection management systems to establish a platform for the processing of museum data from a variety of sources. The data thus read are then checked for their completeness and coherence.',
+museum-digital:qa позволяет (повторно) использовать эти инструменты пользователями и программным обеспечением за пределами museum-digital. Они могут использоваться непосредственно через веб-интерфейс или через API, что также позволяет легко встраивать инструменты оценки качества в другие системы управления собраниями, которые часто пока не имеют сопоставимых инструментов.',
+  'summary' => 'Резюме',
+  'tech_background_hl' => 'Техническая база',
+  'faq' => 'Часто задаваемые вопросы',
+  'tech_background_summary' => 'museum-digital:qa использует те компоненты инструмента импорта от museum-digital, которые решают задачи разбора различных входных форматов и преобразования их в единый формат для простой обработки. Таким образом, он поддерживает чтение как устоявшихся открытых стандартов обмена данными в секторе культурного наследия, так и специфических экспортных форматов ряда систем управления коллекциями, что позволяет создать платформу для обработки музейных данных из различных источников. Считанные таким образом данные затем проверяются на полноту и согласованность.',
+  'currently_offline_msg' => 'Вы сейчас находитесь в режиме офлайн. Оценка происходит на сервере. Пожалуйста, сначала попробуйте переподключиться к сети.',
+  'filesize_too_big' => 'Файл слишком большой! Максимально допустимый размер загружаемых файлов составляет [placeholder] байт.',
+  'quality_assessment_tools' => 'Инструменты оценки качества',
+  'api' => 'API',
+  'outlook' => 'Перспективы',
+  'faq_q_why_is_my_cms_not_supported' => 'Почему экспорт из моей CMS не поддерживается?',
+  'faq_a_why_is_my_cms_not_supported' => 'Как описано в разделе "Технические предпосылки", не каждая система управления собраниями предлагает форматы экспорта, единые для различных учреждений, использующих ее. Помимо общих открытых стандартов museum-digital:qa может поддерживать только те форматы экспорта, которые не являются специфическими для отдельного учреждения.
+
+Отсутствие единого формата экспорта часто обусловлено настраиваемостью базовой структуры базы данных, а не поверхностной настраиваемостью интерфейса. Если структура базы данных полностью настраивается под нужды музея, то и экспорт нужно писать на заказ, что, в свою очередь, означает дополнительные затраты и усилия.
+
+Если ваше программное обеспечение поддерживает единый для всех учреждений формат экспорта, который пока не может быть использован в museum-digital:qa, мы будем очень заинтересованы в его поддержке в будущем. В таких случаях, пожалуйста, отправьте письмо - в идеале вместе с примерами экспорта - на адрес quality@museum-digital.de.',
+  'faq_q_birth_death_dates_via_vocabs' => 'Даты рождения и смерти связанных между собой действующих лиц не включены в метаданные наших объектов, но мы связываем их с хранилищами нормативных данных. Будут ли по-прежнему работать проверки правдоподобия?',
+  'faq_a_birth_death_dates_via_vocabs' => 'Да. museum-digital:qa также проверит ссылки на нормативные хранилища данных по контролируемым словарям museum-digital, чтобы собрать дополнительные данные - например, даты рождения и смерти, - если такие ссылки будут предоставлены.',
+  'outlook_text' => 'museum-digital:qa предлагает платформу для разбора и обработки музейных данных из множества источников - в частности, для проверки их качества. Строгая модульность компонентов - парсинг данных, с одной стороны, сами проверки, с другой, и, наконец, связь между ними - упрощает интеграцию дополнительных инструментов и проверок.
+
+Используя API, заданный в формате OpenAPI, исследователи и производители программного обеспечения могут легко повторно использовать инструменты, доступные через museum-digital:qa.',
+  'tech_background_text' => 'museum-digital:qa принимает данные из общих и согласованных входных форматов, преобразует их во внутренний унифицированный формат и оценивает на предмет полноты и правдоподобности. В качестве входных форматов могут выступать либо форматы экспорта, специфичные для программного обеспечения различных систем управления коллекциями, если они формируются одинаково во всех музеях, использующих одно и то же приложение, либо общие открытые стандарты обмена данными о музейных предметах. 
+
+Различные системы управления собраниями по-разному подходят к решению задачи кастомизации. В то время как museum-digital:musdb целенаправленно не позволяет музеям свободно определять поля, чтобы обеспечить согласованный дизайн базы данных в пределах институциональных границ и, таким образом, иметь возможность предлагать разнообразные функции оценки, адаптированные к общему набору полей данных, с одной стороны, и обеспечить функции экспорта и поиска в нескольких музеях, с другой стороны, другие системы управления собраниями позволяют настраивать их вплоть до определения полностью индивидуальной структуры базы данных. Такая настройка может осуществляться как на уровне пользовательского интерфейса, так и непосредственно на уровне базовой базы данных. Если структура базы данных также настраивается, это одновременно означает, что экспорт из одного и того же программного обеспечения может осуществляться в различных форматах, аналогичных тем, которые характерны для конкретного музея. Если настраивается только пользовательский интерфейс, то часто существуют специфические для программного обеспечения форматы экспорта, которые согласованы между музеями, хорошо поддерживаются и, возможно, являются более полными, чем другие варианты экспорта (и поэтому особенно хорошо подходят, например, для миграции данных).
+
+Чтобы упростить обмен данными между организациями и программным обеспечением, были разработаны различные открытые стандарты. Наиболее актуальным для музеев, безусловно, является LIDO; в смежных областях используются EAD (в основном архивы) и MODS (в основном библиотеки). В большинстве случаев эти стандарты предназначены для обмена публикуемыми данными. Поэтому они редко охватывают все локально доступные области данных. Открытые стандарты, с другой стороны, реализованы во многих решениях по управлению собраниями. С выходом EODEM в 2023 году начались первые шаги по фасилитации обмена преимущественно внутренними данными.
+
+
+Для импорта данных (будь то миграция данных или просто публикация) museum-digital предлагает инструмент импорта, который, помимо общих форматов обмена, поддерживает также некоторые специфические форматы программного обеспечения (с одной стороны, потому что не все системы управления собраниями поддерживают общие форматы обмена "из коробки", с другой стороны, потому что они часто являются более полными, как говорилось выше). Этот инструмент импорта, в свою очередь, состоит из трех компонентов: 1) основные типы данных, актуальные для музейной работы (такие как объект, ключевое слово, заем), 2) функции для чтения данных из вышеупомянутых форматов и переноса входных данных в только что упомянутые типы данных, и 3) модуль для собственно переноса данных в базу данных.
+
+Модули инструмента импорта для определения типов данных и разбора данных из различных входных форматов повторно используются в museum-digital:qa. Таким образом, museum-digital:qa может поддерживать все форматы импорта, которые также поддерживаются импортером museum-digital, с минимальными дополнительными усилиями (для специфических музейных форматов импорта, однако, нет смысла проводить такую адаптацию). Не имея собственного кода для чтения входящих данных, museum-digital:qa, таким образом, также остается очень малообслуживаемым. Напротив, повторное использование функций разбора импортера также означает, что все данные, которые можно проверить на качество с помощью museum-digital:qa, могут быть импортированы в museum-digital без каких-либо дополнительных настроек.
+
+Исходные данные впоследствии предоставляются в структурированном виде и легко поддаются дальнейшей обработке. Здесь они передаются в слегка адаптированном виде функциям проверки качества данных. По мере написания museum-digital:qa эти функции были перенесены из museum-digital:musdb в отдельную библиотеку, в самостоятельную библиотеку с открытым исходным кодом.',
+  'go_back' => 'Вернуться',
+  'paste_as_text' => 'Вставить обычный текст',
+  'licensed_under' => 'Эта работа лицензирована под',
+  'reload_application' => 'Перезагрузить приложение',
+  'more' => 'Подробнее',
+  'select_check' => 'Пожалуйста, выберите тип проверки (проверок)',
+  'minimaldatensatz_p1' => 'Рабочая группа Minimaldatensatz ("Минимальная жизнеспособная запись об объекте") ставит перед собой задачу определить набор базовой информации об объекте, необходимой или крайне рекомендуемой для достойной публикации объектов. Ее рекомендации в первую очередь направлены на публикацию в Немецкой электронной библиотеке (DDB), но могут служить разумным ориентиром и в других контекстах.',
+  'minimaldatensatz_p2' => 'Поскольку контекст этой проверки специфически немецкий, возвращаемые значения проверки пока доступны только на немецком языке.',
+  'see_also' => 'См. также',
+  'log' => 'Журнал',
+  'launch' => 'Запуск',
+  'thanks' => 'Благодарности',
+  'count_new_to_vocabs' => 'Счётчик новых словарных единиц в museum-digital',
+  'count_new_to_vocabs_short' => 'Счётчик: новые словарные единицы',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality объединяет разбор входных данных различных форматов из инструмента импорта museum-digital с различными проверками. Это также означает, что все данные, которые могут быть проверены с помощью museum-digital:quality, могут быть импортированы в museum-digital.
+
+Однако регулярный импорт данных влечет за собой добавление недостающих записей в контролируемые словари museum-digital для акторов, мест, времени и тегов, которые должны быть очищены и дополнены после импорта. С помощью этой проверки можно подсчитать количество таких вновь добавленных записей.',
+  'samples' => 'Примеры',
+  'select_activity' => 'Что бы вы хотели сделать с этими данными?',
+  'evaluate' => 'Оценить',
+  'convert_to_xml' => 'Конвертировать в XML',
+  'select_conversion_target_format' => 'Выберите целевой формат для преобразования',
+  'other_features' => 'Другие особенности',
+  'convert_to_xml_explica' => 'museum-digital:qa может использовать XSL-преобразования, написанные для musdb, для преобразования любых импортируемых данных в те XML-форматы, в которые musdb может экспортировать. Наряду с хорошо зарекомендовавшим себя стандартом обмена LIDO сюда входит EODEM, недавнее расширение LIDO, призванное упростить обмен данными для регистраторов, в частности, в случае займов между музеями.',
 );

ta/quality_web.php

@@ -0,0 +1,96 @@
+<?PHP
+declare(strict_types = 1);
+$quality_web = array (
+  'puqi' => 'Publication Quality Index (PuQI)',
+  'plausi' => 'Plausibility Check',
+  'plausi_legal' => 'Plausibility Check for License Status of Images / Representations',
+  'puqi_explica' => 'The publication quality index measures the completeness and suitability of an object record\'s publishable information. For example, feedback is given on the availability of an object title and a tags. Objects\' descriptions are checked for their length; and linked images\' license status is evaluated. Based on these evaluations, a quantitative score is provided to be able to roughly measure the completeness and quality of an object record for publication.',
+  'plausi_explica' => 'During this check, the objects\' events (production, usage, etc.) are checked for their logical coherence based on the provided times and actors. For example, a bike that has been produced in 1950 cannot have been used in 1870. Similarly, a photograph showing Ice-T (born 1958) cannot have been taken in 1920.',
+  'plausi_explica_2' => 'If such a logical inconsistency between or different events in the object\'s history is detected, a warning will be provided.',
+  'plausi_legal_explica' => 'This check aims to identify and warn about obvious issues concerning the licensing status of an object\'s representations (mainly images). To do so, the life dates of the recorded creators are identified - either directly taken from the provided inputs or via references to central authority files and repositories like the Library of Congress Subject Headings, Wikidata or the Gemeinsame Normdatei of the German National Library. ',
+  'plausi_legal_explica_2' => 'The check is based on the assumption that images of museum objects are meant to be documenting - meaning that in many jurisdictions (such as the EU) no copyright protection is extended to the images themselves. It is thus likely, that images of objects older than 100 years after the death of their creator are in the public domain (here, we are using the maximum number of years by which any country extends copyright protection to a work). If a license status indicating otherwise is provided, a warning will be returned. Similarly, a warning will be displayed if images of objects created by creators who are still alive or have died only within the last 50 years (as per the Berne Convention) have been set under a non-restrictive license. These checks are of course only a rough approximation - laws are complicated and diverse, and so is object data. In sum, it is hoped however, that they cover issues appearing regularly, while not producing too many falsely positive warnings.',
+  'citation' => 'Citation',
+  'puqi_score' => 'PuQI Score',
+  'results' => 'Results',
+  'objects_identified' => '[placeholder_for_count] objects identified',
+  'check_passed' => 'Check passed',
+  'warning' => 'Warning',
+  'status' => 'Status',
+  'plausibility_warnings' => 'Plausibility Check: Warnings',
+  'plausibility_warnings_licenses' => 'Plausibility Check for Image Licenses: Warnings',
+  'puqi_notices' => 'PuQI Messages',
+  'types_of_evaluations' => 'Types of Evaluations',
+  'see' => 'See',
+  'step' => 'Step',
+  'select_import_format' => 'Select an import format',
+  'upload_a_file' => 'Upload a file',
+  'select_file_for_upload' => 'Select a file for upload',
+  'alt_paste_text' => 'Or Paste the Object Record in Plain Text',
+  'text' => 'Text',
+  'submit' => 'Submit',
+  'news' => 'News',
+  'click_read_more' => 'Click to read more',
+  'try_it_out' => 'Try it out',
+  'intro_text' => 'Since the 1980s, more and more museums have started managing their object data digitally. Where inventory cards oftentimes only covered the most rudimentary information systematically, digital record-keeping allows for a much more detailled description of the objects without any of the space limitations inherent to the medium of the inventory card. Detailed information that had often only been written down unsystematically in catalogues or research articles can now be stored and searched digitally alongside the rudimentary object data in a database. Simultaneously, an increasing number of museums has started to publish their collections in publicly accessible databases, often in collaboration with other museums, which have entirely different collections.
+
+A coverage of the collections that is at the same time systematic and detailled has thus only really been possible due to digitization. The increasingly close link between inventorization and publication of the object data on the other hand makes data quality more relevant than ever.
+
+museum-digital has helped museums and related institutions in collaboratively managing and publishing their collections online since 2009. In this context, a number of tools were written to measure and improve the quality of collection data.
+
+museum-digital:qa allows the (re-)use of these tools by users and software beyond museum-digital. They may be used directly via a web interface or via an API, which also allows for the simple embedding of the quality assessment tools into other collection management systems, which often do not feature comparable tools as of yet.',
+  'summary' => 'Summary',
+  'tech_background_hl' => 'Technical background',
+  'faq' => 'Frequently Asked Questions',
+  'tech_background_summary' => 'museum-digital:qa resuses those components of museum-digital\'s improt tool, which cover the tasks of parsing different input formats and converting them into a uniform format for simple processing. It thus supports reading both well-established open standards for data exchange in the cultural heritage sector as well as the specific export formats of a number of collection management systems to establish a platform for the processing of museum data from a variety of sources. The data thus read are then checked for their completeness and coherence.',
+  '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',
+  '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.',
+  'outlook_text' => 'museum-digital:qa offers a platform to parse and process museum data from a multitude of sources - specifically, to check them for their quality. The strictly modularization of components - the parsing of the data on one hand, the checks themselves on the other, and finally the communication between these two - makes it simple to integrate further tools and checks.
+
+Using the API, specified using the OpenAPI format, researchers and software vendors can easily reuse the tools made accessible through museum-digital:qa.',
+  'tech_background_text' => 'museum-digital:qa accepts data from common and consistent input formats, converts them into an internal, uniform format, and finally evaluates them with regard to their completeness and plausibility. Input formats may either be the software-specific export formats of various collection management systems, if these are formed in the same way across all museums using the same application, or the common open standards for the exchange of museum object data. 
+
+Different collection management systems have different approaches to dealing with the task of customization. While museum-digital:musdb purposefully does not allow museums to freely define fields in order to ensure a consistent database design across institutional boundaries, and thus to be able to offer a variety of evaluation functions tailored to the shared set of data fields on the one hand, and to enable export and search functions across multiple museums on the other hand, other collection management systems allow customization up to the level of defining a fully custom database structure. This customizability may either work on the user interface level or directly at level of the underlying database. If the database structure is also customizable, this simultaneously means that exports from the same software can come in a variety of formats similarly custom to the given museum. Where only the user interface is customizable, there are often software-specific export formats that are consistent across museum boundaries, well maintained, and possibly more complete than other export options (and thus particularly well suited for data migration, for example).
+
+In order to simplify the exchange of data across institutional and software boundaries, various open standards have been developed. The single one most relevant for museums is certainly LIDO; in related areas, EAD (mainly archives) and MODS (mainly libraries) are used. In most cases, these standards are intended for the exchange of publishable data. They thus rarely cover all locally available data fields. Open standards, on the other hand, are implemented in many collection management solutions. With the EODEM published in 2023, early steps towards fascilitating the exchange of primarily internal data have begun to be taken.
+
+For the purpose of importing data (be it for data migration or simply for publication), museum-digital offers an import tool that - in addition to the common exchange formats - also supports some software-specific formats (on the one hand, because not all collection management systems support the common exchange formats "out of the box", on the other hand, because these are often more complete, as discussed above). This import tool, in turn, consists of three components: 1) basic data types relevant to museum work (such as object, keyword, loan), 2) functions for reading data from the aforementioned formats and transferring the input data into the data types just mentioned, and 3) a module for actually transferring the data into the database.
+
+The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
+
+The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
+  'paste_as_text' => 'Paste in plain text',
+  'licensed_under' => 'This work is licensed under',
+  'reload_application' => 'Reload application',
+  'more' => 'More',
+  'select_check' => 'Please select the type of check(s) to run',
+  'minimaldatensatz_p1' => 'The Working Group Minimaldatensatz ("Minimum Viable Object Record") sets out to define a set of basic object information required or highly recommended for a worthwhile publication of objects. Its recommendations are primarily aimed at publishing in the German Digital Library (DDB), but can serve as a sane guideline in other contexts as well.',
+  'minimaldatensatz_p2' => 'As the context of this check is specifically German, the return values of the check are thus far available only in German.',
+  'see_also' => 'See also',
+  'log' => 'Log',
+  'launch' => 'Launch',
+  'thanks' => 'Thanks',
+  'count_new_to_vocabs' => 'Counters for new vocabulary entries at museum-digital',
+  'count_new_to_vocabs_short' => 'Count: new vocabulary entries',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality strings together the parsing of input data of different formats from museum-digital\'s import tool with different checks. That also means that all data that can be checked using museum-digital:quality could be imported to museum-digital as well.
+
+Actually importing the data however regularly also entails adding missing entries to museum-digital\'s controlled vocabularies for actors, places, times, and tags, which need to be cleaned and enriched in the aftermath of the import. Using this check, the number of such newly added entries can be counted.',
+  'samples' => 'Samples',
+  'select_activity' => 'What would you like to do with the data?',
+  'evaluate' => 'Evaluate',
+  'convert_to_xml' => 'Convert to XML',
+  'select_conversion_target_format' => 'Select the target format for conversion',
+  'other_features' => 'Other features',
+  'convert_to_xml_explica' => 'museum-digital:qa can leverage the XSL transformations written for musdb to convert any imported data to those XML formats musdb can export to. Next to the well-established exchange standard LIDO this includes EODEM, a recent extension to LIDO meant to simplify data exchange for registrars specifically in the case of loans between museums.',
+);

te/quality_web.php

@@ -0,0 +1,96 @@
+<?PHP
+declare(strict_types = 1);
+$quality_web = array (
+  'puqi' => 'Publication Quality Index (PuQI)',
+  'plausi' => 'Plausibility Check',
+  'plausi_legal' => 'Plausibility Check for License Status of Images / Representations',
+  'puqi_explica' => 'The publication quality index measures the completeness and suitability of an object record\'s publishable information. For example, feedback is given on the availability of an object title and a tags. Objects\' descriptions are checked for their length; and linked images\' license status is evaluated. Based on these evaluations, a quantitative score is provided to be able to roughly measure the completeness and quality of an object record for publication.',
+  'plausi_explica' => 'During this check, the objects\' events (production, usage, etc.) are checked for their logical coherence based on the provided times and actors. For example, a bike that has been produced in 1950 cannot have been used in 1870. Similarly, a photograph showing Ice-T (born 1958) cannot have been taken in 1920.',
+  'plausi_explica_2' => 'If such a logical inconsistency between or different events in the object\'s history is detected, a warning will be provided.',
+  'plausi_legal_explica' => 'This check aims to identify and warn about obvious issues concerning the licensing status of an object\'s representations (mainly images). To do so, the life dates of the recorded creators are identified - either directly taken from the provided inputs or via references to central authority files and repositories like the Library of Congress Subject Headings, Wikidata or the Gemeinsame Normdatei of the German National Library. ',
+  'plausi_legal_explica_2' => 'The check is based on the assumption that images of museum objects are meant to be documenting - meaning that in many jurisdictions (such as the EU) no copyright protection is extended to the images themselves. It is thus likely, that images of objects older than 100 years after the death of their creator are in the public domain (here, we are using the maximum number of years by which any country extends copyright protection to a work). If a license status indicating otherwise is provided, a warning will be returned. Similarly, a warning will be displayed if images of objects created by creators who are still alive or have died only within the last 50 years (as per the Berne Convention) have been set under a non-restrictive license. These checks are of course only a rough approximation - laws are complicated and diverse, and so is object data. In sum, it is hoped however, that they cover issues appearing regularly, while not producing too many falsely positive warnings.',
+  'citation' => 'Citation',
+  'puqi_score' => 'PuQI Score',
+  'results' => 'Results',
+  'objects_identified' => '[placeholder_for_count] objects identified',
+  'check_passed' => 'Check passed',
+  'warning' => 'Warning',
+  'status' => 'Status',
+  'plausibility_warnings' => 'Plausibility Check: Warnings',
+  'plausibility_warnings_licenses' => 'Plausibility Check for Image Licenses: Warnings',
+  'puqi_notices' => 'PuQI Messages',
+  'types_of_evaluations' => 'Types of Evaluations',
+  'see' => 'See',
+  'step' => 'Step',
+  'select_import_format' => 'Select an import format',
+  'upload_a_file' => 'Upload a file',
+  'select_file_for_upload' => 'Select a file for upload',
+  'alt_paste_text' => 'Or Paste the Object Record in Plain Text',
+  'text' => 'Text',
+  'submit' => 'Submit',
+  'news' => 'News',
+  'click_read_more' => 'Click to read more',
+  'try_it_out' => 'Try it out',
+  'intro_text' => 'Since the 1980s, more and more museums have started managing their object data digitally. Where inventory cards oftentimes only covered the most rudimentary information systematically, digital record-keeping allows for a much more detailled description of the objects without any of the space limitations inherent to the medium of the inventory card. Detailed information that had often only been written down unsystematically in catalogues or research articles can now be stored and searched digitally alongside the rudimentary object data in a database. Simultaneously, an increasing number of museums has started to publish their collections in publicly accessible databases, often in collaboration with other museums, which have entirely different collections.
+
+A coverage of the collections that is at the same time systematic and detailled has thus only really been possible due to digitization. The increasingly close link between inventorization and publication of the object data on the other hand makes data quality more relevant than ever.
+
+museum-digital has helped museums and related institutions in collaboratively managing and publishing their collections online since 2009. In this context, a number of tools were written to measure and improve the quality of collection data.
+
+museum-digital:qa allows the (re-)use of these tools by users and software beyond museum-digital. They may be used directly via a web interface or via an API, which also allows for the simple embedding of the quality assessment tools into other collection management systems, which often do not feature comparable tools as of yet.',
+  'summary' => 'Summary',
+  'tech_background_hl' => 'Technical background',
+  'faq' => 'Frequently Asked Questions',
+  'tech_background_summary' => 'museum-digital:qa resuses those components of museum-digital\'s improt tool, which cover the tasks of parsing different input formats and converting them into a uniform format for simple processing. It thus supports reading both well-established open standards for data exchange in the cultural heritage sector as well as the specific export formats of a number of collection management systems to establish a platform for the processing of museum data from a variety of sources. The data thus read are then checked for their completeness and coherence.',
+  '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',
+  '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.',
+  'outlook_text' => 'museum-digital:qa offers a platform to parse and process museum data from a multitude of sources - specifically, to check them for their quality. The strictly modularization of components - the parsing of the data on one hand, the checks themselves on the other, and finally the communication between these two - makes it simple to integrate further tools and checks.
+
+Using the API, specified using the OpenAPI format, researchers and software vendors can easily reuse the tools made accessible through museum-digital:qa.',
+  'tech_background_text' => 'museum-digital:qa accepts data from common and consistent input formats, converts them into an internal, uniform format, and finally evaluates them with regard to their completeness and plausibility. Input formats may either be the software-specific export formats of various collection management systems, if these are formed in the same way across all museums using the same application, or the common open standards for the exchange of museum object data. 
+
+Different collection management systems have different approaches to dealing with the task of customization. While museum-digital:musdb purposefully does not allow museums to freely define fields in order to ensure a consistent database design across institutional boundaries, and thus to be able to offer a variety of evaluation functions tailored to the shared set of data fields on the one hand, and to enable export and search functions across multiple museums on the other hand, other collection management systems allow customization up to the level of defining a fully custom database structure. This customizability may either work on the user interface level or directly at level of the underlying database. If the database structure is also customizable, this simultaneously means that exports from the same software can come in a variety of formats similarly custom to the given museum. Where only the user interface is customizable, there are often software-specific export formats that are consistent across museum boundaries, well maintained, and possibly more complete than other export options (and thus particularly well suited for data migration, for example).
+
+In order to simplify the exchange of data across institutional and software boundaries, various open standards have been developed. The single one most relevant for museums is certainly LIDO; in related areas, EAD (mainly archives) and MODS (mainly libraries) are used. In most cases, these standards are intended for the exchange of publishable data. They thus rarely cover all locally available data fields. Open standards, on the other hand, are implemented in many collection management solutions. With the EODEM published in 2023, early steps towards fascilitating the exchange of primarily internal data have begun to be taken.
+
+For the purpose of importing data (be it for data migration or simply for publication), museum-digital offers an import tool that - in addition to the common exchange formats - also supports some software-specific formats (on the one hand, because not all collection management systems support the common exchange formats "out of the box", on the other hand, because these are often more complete, as discussed above). This import tool, in turn, consists of three components: 1) basic data types relevant to museum work (such as object, keyword, loan), 2) functions for reading data from the aforementioned formats and transferring the input data into the data types just mentioned, and 3) a module for actually transferring the data into the database.
+
+The import tool\'s modules for defining data types and parsing data from different input formats are reused in museum-digital:qa. Thus, museum-digital:qa can support all import formats that are also supported by the importer of museum-digital with a minimum of additional effor (for museum-specific import formats, however, it is not worthwhile to undertake such adaptations). Without relevant own code for reading the incoming data, museum-digital:qa thus also remains very low-maintenance. Conversely, reusing the parsing functionalities of the importer also means that all data that can be checked for quality using museum-digital:qa can be imported into museum-digital without any further adjustments as well.
+
+The input data are subsequently available in a structured form and can easily be processed further. Here, it is passed on in a slightly adapted form to the functions for checking data quality. As museum-digital:qa was written, these functions were moved from museum-digital:musdb to a separate library into a standalone, open-source library.',
+  'go_back' => 'Go back',
+  'paste_as_text' => 'Paste in plain text',
+  'licensed_under' => 'This work is licensed under',
+  'reload_application' => 'Reload application',
+  'more' => 'More',
+  'select_check' => 'Please select the type of check(s) to run',
+  'minimaldatensatz_p1' => 'The Working Group Minimaldatensatz ("Minimum Viable Object Record") sets out to define a set of basic object information required or highly recommended for a worthwhile publication of objects. Its recommendations are primarily aimed at publishing in the German Digital Library (DDB), but can serve as a sane guideline in other contexts as well.',
+  'minimaldatensatz_p2' => 'As the context of this check is specifically German, the return values of the check are thus far available only in German.',
+  'see_also' => 'See also',
+  'log' => 'Log',
+  'launch' => 'Launch',
+  'thanks' => 'Thanks',
+  'count_new_to_vocabs' => 'Counters for new vocabulary entries at museum-digital',
+  'count_new_to_vocabs_short' => 'Count: new vocabulary entries',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality strings together the parsing of input data of different formats from museum-digital\'s import tool with different checks. That also means that all data that can be checked using museum-digital:quality could be imported to museum-digital as well.
+
+Actually importing the data however regularly also entails adding missing entries to museum-digital\'s controlled vocabularies for actors, places, times, and tags, which need to be cleaned and enriched in the aftermath of the import. Using this check, the number of such newly added entries can be counted.',
+  'samples' => 'Samples',
+  'select_activity' => 'What would you like to do with the data?',
+  'evaluate' => 'Evaluate',
+  'convert_to_xml' => 'Convert to XML',
+  'select_conversion_target_format' => 'Select the target format for conversion',
+  'other_features' => 'Other features',
+  'convert_to_xml_explica' => 'museum-digital:qa can leverage the XSL transformations written for musdb to convert any imported data to those XML formats musdb can export to. Next to the well-established exchange standard LIDO this includes EODEM, a recent extension to LIDO meant to simplify data exchange for registrars specifically in the case of loans between museums.',
+);

uk/quality_web.php

@@ -1,45 +1,96 @@
 <?PHP
 declare(strict_types = 1);
 $quality_web = array (
-  'puqi' => 'Publication Quality Index (PuQI)',
-  'plausi' => 'Plausibility Check',
-  'plausi_legal' => 'Plausibility Check for License Status of Images / Representations',
-  'puqi_explica' => 'The publication quality index measures the completeness and suitability of an object record\'s publishable information. For example, feedback is given on the availability of an object title and a tags. Objects\' descriptions are checked for their length; and linked images\' license status is evaluated. Based on these evaluations, a quantitative score is provided to be able to roughly measure the completeness and quality of an object record for publication.',
-  'plausi_explica' => 'During this check, the objects\' events (production, usage, etc.) are checked for their logical coherence based on the provided times and actors. For example, a bike that has been produced in 1950 cannot have been used in 1870. Similarly, a photograph showing Ice-T (born 1958) cannot have been taken in 1920.',
-  'plausi_explica_2' => 'If such a logical inconsistency between or different events in the object\'s history is detected, a warning will be provided.',
-  'plausi_legal_explica' => 'This check aims to identify and warn about obvious issues concerning the licensing status of an object\'s representations (mainly images). To do so, the life dates of the recorded creators are identified - either directly taken from the provided inputs or via references to central authority files and repositories like the Library of Congress Subject Headings, Wikidata or the Gemeinsame Normdatei of the German National Library. ',
-  'plausi_legal_explica_2' => 'The check is based on the assumption that images of museum objects are meant to be documenting - meaning that in many jurisdictions (such as the EU) no copyright protection is extended to the images themselves. It is thus likely, that images of objects older than 100 years after the death of their creator are in the public domain (here, we are using the maximum number of years by which any country extends copyright protection to a work). If a license status indicating otherwise is provided, a warning will be returned. Similarly, a warning will be displayed if images of objects created by creators who are still alive or have died only within the last 50 years (as per the Berne Convention) have been set under a non-restrictive license. These checks are of course only a rough approximation - laws are complicated and diverse, and so is object data. In sum, it is hoped however, that they cover issues appearing regularly, while not producing too many falsely positive warnings.',
-  'citation' => 'Citation',
-  'puqi_score' => 'PuQI Score',
-  'results' => 'Results',
-  'objects_identified' => '[placeholder_for_count] objects identified',
-  'check_passed' => 'Check passed',
-  'warning' => 'Warning',
-  'status' => 'Status',
-  'plausibility_warnings' => 'Plausibility Check: Warnings',
-  'plausibility_warnings_licenses' => 'Plausibility Check for Image Licenses: Warnings',
-  'puqi_notices' => 'PuQI Messages',
-  'types_of_evaluations' => 'Types of Evaluations',
-  'see' => 'See',
-  'step' => 'Step',
-  'select_import_format' => 'Select an import format',
-  'upload_a_file' => 'Upload a file',
-  'select_file_for_upload' => 'Select a file for upload',
-  'alt_paste_text' => 'Or Paste the Object Record in Plain Text',
-  'text' => 'Text',
-  'submit' => 'Submit',
-  'news' => 'News',
-  'click_read_more' => 'Click to read more',
-  'try_it_out' => 'Try it out',
-  'intro_text' => 'Since the 1980s, more and more museums have started managing their object data digitally. Where inventory cards oftentimes only covered the most rudimentary information systematically, digital record-keeping allows for a much more detailled description of the objects without any of the space limitations inherent to the medium of the inventory card. Detailed information that had often only been written down unsystematically in catalogues or research articles can now be stored and searched digitally alongside the rudimentary object data in a database. Simultaneously, an increasing number of museums has started to publish their collections in publicly accessible databases, often in collaboration with other museums, which have entirely different collections.
+  'puqi' => 'Індекс якості публікацій (PuQI)',
+  'plausi' => 'Перевірка правдоподібності',
+  'plausi_legal' => 'Перевірка достовірності ліцензійного статусу зображень / презентацій',
+  'puqi_explica' => 'Індекс якості публікації вимірює повноту та придатність інформації про об\'єкт для публікації. Наприклад, оцінюється наявність назви об\'єкта та тегів. Описи об\'єктів перевіряються на довжину; оцінюється ліцензійний статус пов\'язаних зображень. На основі цих оцінок виставляється кількісна оцінка, що дозволяє приблизно виміряти повноту і якість запису про об\'єкт для публікації.',
+  'plausi_explica' => 'Під час цієї перевірки події об\'єктів (виробництво, використання тощо) перевіряються на логічну узгодженість на основі наданих даних про час і дійових осіб. Наприклад, велосипед, виготовлений у 1950 році, не може бути використаний у 1870 році. Аналогічно, фотографія, на якій зображений Ice-T (1958 року народження), не могла бути зроблена в 1920 році.',
+  'plausi_explica_2' => 'Якщо буде виявлено таку логічну невідповідність між або різними подіями в історії об\'єкта, буде видано попередження.',
+  'plausi_legal_explica' => 'Ця перевірка має на меті виявити та попередити про очевидні проблеми, пов\'язані з ліцензійним статусом зображень об\'єкта (переважно зображень). Для цього визначаються дати життя авторів зображень - або безпосередньо з наданих матеріалів, або за допомогою посилань на центральні авторитетні файли та репозиторії, такі як Предметні рубрики Бібліотеки Конгресу США, Вікідані або Gemeinsame Normdatei Німецької національної бібліотеки. ',
+  'plausi_legal_explica_2' => 'Перевірка ґрунтується на припущенні, що зображення музейних предметів є документацією, а це означає, що в багатьох юрисдикціях (наприклад, у ЄС) захист авторського права не поширюється на самі зображення. Таким чином, цілком ймовірно, що зображення об\'єктів, старших за 100 років після смерті їхнього творця, є суспільним надбанням (тут ми використовуємо максимальну кількість років, на яку будь-яка країна поширює захист авторського права на твір). Якщо статус ліцензії вказує на протилежне, буде повернуто попередження. Аналогічно, попередження буде показано, якщо зображення об\'єктів, створених авторами, які ще живі або померли протягом останніх 50 років (відповідно до Бернської конвенції), були розміщені на умовах необмеженої ліцензії. Звичайно, ці перевірки є лише грубим наближенням - закони складні та різноманітні, так само як і дані про об\'єкти. В цілому, ми сподіваємося, що вони охоплюють проблеми, які з\'являються регулярно, і при цьому не видають занадто багато хибно позитивних попереджень.',
+  'citation' => 'Цитування',
+  'puqi_score' => 'Оцінка PuQI',
+  'results' => 'Результати',
+  'objects_identified' => '[placeholder_for_count] об\'єктів виявлено',
+  'check_passed' => 'Перевірку пройдено',
+  'warning' => ' Попередження',
+  'status' => 'Статус',
+  'plausibility_warnings' => 'Перевірка правдоподібності: Попередження',
+  'plausibility_warnings_licenses' => 'Перевірка правдоподібності для ліцензій на зображення: Попередження',
+  'puqi_notices' => 'Повідомлення PuQI',
+  'types_of_evaluations' => 'Типи оцінок',
+  'see' => 'Дивіться',
+  'step' => 'Крок',
+  'select_import_format' => 'Виберіть формат імпорту',
+  'upload_a_file' => 'Завантажити файл',
+  'select_file_for_upload' => 'Виберіть файл для завантаження',
+  'alt_paste_text' => 'Або вставте запис про об\'єкт у вигляді простого тексту',
+  'text' => 'Текст',
+  'submit' => 'Надіслати',
+  'news' => 'Новини',
+  'click_read_more' => 'Натисніть, щоб прочитати більше',
+  'try_it_out' => 'Спробуйте',
+  'intro_text' => 'Починаючи з 1980-х років, дедалі більше музеїв почали керувати даними про свої об\'єкти в цифровому форматі. Там, де інвентарні картки часто систематично охоплювали лише найпростішу інформацію, цифрове ведення обліку дозволяє набагато детальніше описувати об\'єкти без жодних обмежень у просторі, притаманних носіям інвентарних карток. Детальна інформація, яка часто лише безсистемно записувалася в каталогах чи наукових статтях, тепер може зберігатися і шукатися в цифровому вигляді разом з первинними даними про об\'єкт у базі даних. Одночасно все більше музеїв почали публікувати свої колекції в загальнодоступних базах даних, часто у співпраці з іншими музеями, які мають зовсім інші колекції.
 
-A coverage of the collections that is at the same time systematic and detailled has thus only really been possible due to digitization. The increasingly close link between inventorization and publication of the object data on the other hand makes data quality more relevant than ever.
+Таким чином, систематичне та детальне висвітлення колекцій стало можливим лише завдяки оцифровуванню. З іншого боку, дедалі тісніший зв\'язок між інвентаризацією та публікацією даних про об\'єкт робить якість даних більш актуальною, ніж будь-коли.
 
-museum-digital has helped museums and related institutions in collaboratively managing and publishing their collections online since 2009. In this context, a number of tools were written to measure and improve the quality of collection data.
+Починаючи з 2009 року, museum-digital допомагає музеям та пов\'язаним з ними установам у спільному управлінні та публікації їхніх колекцій в Інтернеті. У цьому контексті було розроблено низку інструментів для вимірювання та покращення якості колекційних даних.
 
-museum-digital:qa allows the (re-)use of these tools by users and software beyond museum-digital. They may be used directly via a web interface or via an API, which also allows for the simple embedding of the quality assessment tools into other collection management systems, which often do not feature comparable tools as of yet.',
-  'summary' => 'Summary',
-  'tech_background_hl' => 'Technical background',
-  'faq' => 'Frequently Asked Questions',
-  'tech_background_summary' => 'museum-digital:qa resuses those components of museum-digital\'s improt tool, which cover the tasks of parsing different input formats and converting them into a uniform format for simple processing. It thus supports reading both well-established open standards for data exchange in the cultural heritage sector as well as the specific export formats of a number of collection management systems to establish a platform for the processing of museum data from a variety of sources. The data thus read are then checked for their completeness and coherence.',
+museum-digital:qa дозволяє (повторне) використання цих інструментів користувачами та програмним забезпеченням поза межами museum-digital. Їх можна використовувати безпосередньо через веб-інтерфейс або через API, що також дозволяє легко вбудовувати інструменти оцінки якості в інші системи управління колекціями, які часто ще не мають порівнянних інструментів.',
+  'summary' => 'Резюме',
+  'tech_background_hl' => 'Технічна інформація',
+  'faq' => 'Часті запитання',
+  'tech_background_summary' => 'museum-digital:qa повторно використовує ті компоненти інструменту імпорту museum-digital, які охоплюють завдання розбору різних вхідних форматів і перетворення їх в єдиний формат для простого опрацювання. Таким чином, він підтримує зчитування як усталених відкритих стандартів обміну даними в секторі культурної спадщини, так і специфічних експортних форматів низки систем управління колекціями, щоб створити платформу для обробки музейних даних з різних джерел. Зчитані таким чином дані потім перевіряються на повноту та узгодженість.',
+  'currently_offline_msg' => 'Наразі ви перебуваєте в режимі офлайн. Оцінка відбувається на сервері. Будь ласка, спробуйте спочатку підключитися до мережі.',
+  'filesize_too_big' => 'Файл занадто великий! Максимально допустимий розмір завантажених файлів - [placeholder] байт.',
+  'quality_assessment_tools' => 'Інструменти оцінки якості',
+  'api' => 'API',
+  'outlook' => 'Outlook',
+  'faq_q_why_is_my_cms_not_supported' => 'Чому не підтримується експорт з моєї CMS?',
+  'faq_a_why_is_my_cms_not_supported' => 'Як описано в розділі "технічні передумови", не кожна система управління колекціями пропонує формати експорту, однакові для різних установ, що її використовують. Окрім загальних відкритих стандартів для museum-digital:qa, однак, може обґрунтовано підтримувати лише ті формати експорту, які не є специфічними для однієї установи.
+
+Відсутність узгодженого формату експорту часто пов\'язана з кастомізацією базової структури бази даних, а не з поверхневою кастомізацією інтерфейсу - якщо структура бази даних повністю налаштована під конкретний музейний кейс, то кастомізований експорт також має бути написаний, а це, в свою чергу, означає додаткові витрати і зусилля.
+
+Якщо ваше програмне забезпечення підтримує єдиний формат експорту для всіх установ, який ще не можна використовувати з museum-digital:qa, ми були б дуже зацікавлені в його підтримці в майбутньому. У таких випадках, будь ласка, надішліть листа - в ідеалі разом із прикладами експорту - на адресу quality@museum-digital.de.',
+  'faq_q_birth_death_dates_via_vocabs' => 'Дати народження та смерті пов\'язаних акторів не охоплюються нашими метаданими об\'єкта, але ми пов\'язуємо їх зі сховищами нормативних даних. Чи працюватиме перевірка правдоподібності?',
+  'faq_a_birth_death_dates_via_vocabs' => 'Так. museum-digital:qa також перевірятиме посилання на сховища нормативних даних у контрольованих словниках museum-digital, щоб зібрати додаткові дані - такі як дати народження і смерті - якщо такі посилання будуть надані.',
+  'outlook_text' => 'museum-digital:qa пропонує платформу для аналізу та обробки музейних даних з багатьох джерел - зокрема, для перевірки їхньої якості. Сувора модуляризація компонентів - парсинг даних, з одного боку, власне перевірка, з іншого, і, нарешті, комунікація між ними - спрощує інтеграцію подальших інструментів і перевірок.
+
+Використовуючи API, визначений у форматі OpenAPI, дослідники і постачальники програмного забезпечення можуть легко повторно використовувати інструменти, доступні через museum-digital:qa.',
+  'tech_background_text' => 'museum-digital:qa приймає дані з поширених і узгоджених вхідних форматів, перетворює їх у внутрішній, уніфікований формат і, нарешті, оцінює їх на предмет повноти і достовірності. Вхідні формати можуть бути або програмно-специфічними форматами експорту різних систем управління колекціями, якщо вони формуються однаково в усіх музеях, що використовують одну програму, або загальними відкритими стандартами для обміну даними про музейні об\'єкти. 
+
+Різні системи управління колекціями мають різні підходи до вирішення завдання налаштування. У той час як museum-digital:musdb цілеспрямовано не дозволяє музеям вільно визначати поля, щоб забезпечити узгоджену структуру бази даних між інституційними кордонами і, таким чином, мати можливість пропонувати різноманітні функції оцінювання, пристосовані до спільного набору полів даних, з одного боку, і увімкнути функції експорту і пошуку між кількома музеями, з іншого боку, інші системи управління колекціями дозволяють кастомізацію аж до рівня визначення повністю кастомної структури бази даних. Таке налаштування може відбуватися як на рівні інтерфейсу користувача, так і безпосередньо на рівні баз даних. Якщо структура бази даних також налаштовується, це одночасно означає, що експорт з одного і того ж програмного забезпечення може здійснюватися у різних форматах, подібних до тих, що використовуються в даному музеї. Там, де можна налаштувати лише інтерфейс користувача, часто існують специфічні для програмного забезпечення формати експорту, які узгоджуються між музеями, добре підтримуються і, можливо, є більш повними, ніж інші варіанти експорту (а отже, особливо добре підходять, наприклад, для міграції даних).
+
+Для того, щоб спростити обмін даними через інституційні та програмні кордони, було розроблено різні відкриті стандарти. Найбільш актуальним для музеїв є, безумовно, LIDO; у суміжних галузях використовуються EAD (переважно архіви) і MODS (переважно бібліотеки). У більшості випадків ці стандарти призначені для обміну опублікованими даними. Таким чином, вони рідко охоплюють всі доступні на місцевому рівні поля даних. З іншого боку, відкриті стандарти впроваджені в багатьох рішеннях для управління колекціями. З публікацією EODEM у 2023 році почали робитися перші кроки до спрощення обміну переважно внутрішніми даними.
+
+Для імпорту даних (чи то для міграції даних, чи просто для публікації) museum-digital пропонує інструмент імпорту, який - на додаток до загальних форматів обміну - також підтримує деякі програмно-специфічні формати (з одного боку, тому що не всі системи управління колекціями підтримують загальні формати обміну "з коробки", а з іншого боку, тому що вони часто є більш повними, як обговорювалося вище). Цей інструмент імпорту, у свою чергу, складається з трьох компонентів: 1) базові типи даних, релевантні для музейної роботи (такі як об\'єкт, ключове слово, позика), 2) функції для зчитування даних з вищезгаданих форматів і переведення вхідних даних у щойно згадані типи даних, і 3) модуль для власне перенесення даних до бази даних.
+
+Модулі інструменту імпорту для визначення типів даних та аналізу даних з різних вхідних форматів повторно використовуються в museum-digital:qa. Таким чином, museum-digital:qa може підтримувати всі формати імпорту, які також підтримуються імпортером museum-digital, з мінімальними додатковими зусиллями (для специфічних для музею форматів імпорту, однак, не варто здійснювати таку адаптацію). Без відповідного власного коду для зчитування вхідних даних, museum-digital:qa, таким чином, також залишається дуже малообслуговуваним. І навпаки, повторне використання функцій синтаксичного аналізу імпортера також означає, що всі дані, які можна перевірити на якість за допомогою museum-digital:qa, також можна імпортувати до museum-digital без будь-яких подальших коригувань.
+
+Згодом вхідні дані стають доступними у структурованому вигляді і можуть бути легко оброблені далі. Тут вони в дещо адаптованому вигляді передаються функціям для перевірки якості даних. Під час написання museum-digital:qa ці функції було перенесено з museum-digital:musdb в окрему бібліотеку, в окрему бібліотеку з відкритим вихідним кодом.',
+  'go_back' => 'Повернутися',
+  'paste_as_text' => 'Вставити звичайним текстом',
+  'licensed_under' => 'Ця робота ліцензована під',
+  'reload_application' => 'Перезавантажити програму',
+  'more' => 'Більше',
+  'select_check' => 'Будь ласка, виберіть тип перевірки для запуску',
+  'minimaldatensatz_p1' => 'Робоча група Minimaldatensatz ("Мінімальний життєздатний запис про об\'єкт") має на меті визначити набір базової інформації про об\'єкт, необхідної або настійно рекомендованої для повноцінної публікації об\'єктів. Її рекомендації в першу чергу спрямовані на публікацію в Німецькій цифровій бібліотеці (DDB), але можуть слугувати розумним керівництвом і в інших контекстах.',
+  'minimaldatensatz_p2' => 'Оскільки контекст цієї перевірки є специфічно німецьким, значення, що повертаються, поки що доступні лише німецькою мовою.',
+  'see_also' => 'Дивіться також',
+  'log' => 'Журнал',
+  'launch' => 'Запуск',
+  'thanks' => 'Подяка',
+  'count_new_to_vocabs' => 'Кількість нових словникових статей на сайті museum-digital',
+  'count_new_to_vocabs_short' => 'Підрахунок: нові записи в словнику',
+  'count_new_to_vocabs_explica_1' => 'museum-digital:quality об\'єднує синтаксичний аналіз вхідних даних різних форматів з інструменту імпорту museum-digital з різними перевірками. Це також означає, що всі дані, які можна перевірити за допомогою museum-digital:quality, також можна імпортувати до museum-digital.
+
+Насправді, регулярний імпорт даних також тягне за собою додавання відсутніх записів до контрольованих словників museum-digital для акторів, місць, часу і тегів, які потрібно очистити і збагатити після імпорту. За допомогою цієї перевірки можна підрахувати кількість таких нещодавно доданих записів.',
+  'samples' => 'Зразки',
+  'select_activity' => 'Що б ви хотіли зробити з цими даними?',
+  'evaluate' => 'Оцінити',
+  'convert_to_xml' => 'Конвертувати в XML',
+  'select_conversion_target_format' => 'Виберіть цільовий формат для конвертації',
+  'other_features' => 'Інші особливості',
+  'convert_to_xml_explica' => 'museum-digital:qa може використовувати XSL-трансформації, написані для musdb, для перетворення будь-яких імпортованих даних у ті XML-формати, в які musdb може експортувати. Поряд з усталеним стандартом обміну LIDO сюди входить EODEM, нещодавнє розширення до LIDO, призначене для спрощення обміну даними для реєстраторів, особливо у випадку позик між музеями.',
 );