Approval.

This commit is contained in:
2023-10-06 15:33:43 +00:00
committed by md translation bot
parent 3fb8b51998
commit dde939a533
5 changed files with 15 additions and 0 deletions

View File

@ -55,4 +55,7 @@ The lack of a consistent export format often stems from the customizability of t
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.',
);