Approval in backend

backend/ar/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/cs/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/de/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "Im Falle von museum-digital ist die zwingende erste Frage, welche Daten wie genutzt werden sollen. Die \u00f6ffentlichen APIs von museum-digitals Portalen bieten Lesezugriff auf die \u00fcber die Portale ver\u00f6ffentlichten Datens\u00e4tze. Diese Schnittstellen folgen der Logik der menschenlesbaren HTML-Seiten und sind gezielt einfach und ohne Authentifizierung zu nutzen. Reicht also ein lesender Zugriff auf publizierte Daten-Best\u00e4nde, dann sollten diese genutzt werden.",
         "apis_explica_md_musdb": "M\u00f6chte man auch unver\u00f6ffentlichte Daten auslesen oder allgemein schreibend auf die bei museum-digital \/ \u00fcber musdb gespeicherten Datenbest\u00e4nde einwirken, so sind die \u00f6ffentlichen Schnittstellen ungeeignet. In diesem Fall werden die Schnittstellen von musdb ben\u00f6tigt. Um diese zu Nutzen ist ein daf\u00fcr gezielt eingerichteter Bot-Benutzeraccount n\u00f6tig, dessen Bereichtigungen exakt auf die geplante Anwendung zugeschnitten werden k\u00f6nnen. Mit diesem Benutzeraccount k\u00f6nnen sich nun externe Programme authentifizieren und - eingeschr\u00e4nkt durch die Rechteverwaltung - potentiell jede Action vornehmen, die auch menschliche Nutzende in musdb durchf\u00fchren k\u00f6nnen.",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-kompatible Dokumentation von museum-digitals \u00f6ffentlichen APIs (Lesezugriff, nur f\u00fcr ver\u00f6ffentlichte Daten)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-kompatible Dokumentation von musdbs API (lesend und schreibend)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-kompatible Dokumentation von musdbs API (lesend und schreibend)",
+        "weekday": "Wochentag"
     }
 }

backend/dsb/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/en/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/es/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/fr/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/hi/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/hsb/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/hu/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/id/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/it/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/iw/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/kn/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/nl/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/pl/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/pt/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/ro/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/ru/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/ta/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/te/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/tl/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/tr/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/uk/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }

backend/zh/basis.json

@@ -432,6 +432,7 @@
         "apis_explica_md": "In museum-digital's case, it is of utmost importance to first consider what data is to be processed. museum-digital's portals provide read-only APIs for all the data an institution has published via museum-digital. These APIs closely track the human-readable HTML pages in their logic and way of access - in fact, almost every API has an exactly corresponding HTML page that displays the same data - and are built to be simple to use.",
         "apis_explica_md_musdb": "If you need to process unpublished data or want to automatically change your database contents, this can be done using musdb's API. To use musdb's API, one needs to set up a dedicated bot account, whose permissions can be restricted in a fine-grained way to those needed for the bot's task. Using the bot account's user name and authentication token, the external programm can then access the much more fine-grained controls of musdb's API to potentially perform any action a human user could in musdb (again, limited to the permissions the institution has granted the bot account).",
         "apis_openapi_compatible_docs_frontend": "OpenAPI-compatible documentation of museum-digital's public APIs (read-only, published data only)",
-        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)"
+        "apis_openapi_compatible_docs_musdb": "OpenAPI-compatible documentation of musdb's API (read and write)",
+        "weekday": "Weekday"
     }
 }