diff --git a/backend/ar/basis.json b/backend/ar/basis.json
index 047caa84..569a0fc6 100644
--- a/backend/ar/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/cs/basis.json b/backend/cs/basis.json
index c21c5452..19e9e993 100644
--- a/backend/cs/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/de/basis.json b/backend/de/basis.json
index ceb53f5f..b1f0e4e1 100644
--- a/backend/de/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/dsb/basis.json b/backend/dsb/basis.json
index c330ce03..5d6e23b5 100644
--- a/backend/dsb/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/en/basis.json b/backend/en/basis.json
index 1ee8fd89..5acf33c3 100644
--- a/backend/en/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/es/basis.json b/backend/es/basis.json
index 2808511f..e6f646c5 100644
--- a/backend/es/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/fr/basis.json b/backend/fr/basis.json
index ef9740b9..f9ee3381 100644
--- a/backend/fr/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/hi/basis.json b/backend/hi/basis.json
index 1ee8fd89..5acf33c3 100644
--- a/backend/hi/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/hsb/basis.json b/backend/hsb/basis.json
index c330ce03..5d6e23b5 100644
--- a/backend/hsb/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/hu/basis.json b/backend/hu/basis.json
index bf0d0f44..75cf038a 100644
--- a/backend/hu/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/id/basis.json b/backend/id/basis.json
index 30550d19..caf3d82c 100644
--- a/backend/id/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/it/basis.json b/backend/it/basis.json
index 2808511f..e6f646c5 100644
--- a/backend/it/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/iw/basis.json b/backend/iw/basis.json
index d8d20d37..66224211 100644
--- a/backend/iw/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/kn/basis.json b/backend/kn/basis.json
index 1ee8fd89..5acf33c3 100644
--- a/backend/kn/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/nl/basis.json b/backend/nl/basis.json
index 2808511f..e6f646c5 100644
--- a/backend/nl/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/pl/basis.json b/backend/pl/basis.json
index 2cdd491a..acc86a12 100644
--- a/backend/pl/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/pt/basis.json b/backend/pt/basis.json
index d2cd8789..771836f3 100644
--- a/backend/pt/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/ro/basis.json b/backend/ro/basis.json
index 1ee8fd89..5acf33c3 100644
--- a/backend/ro/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/ru/basis.json b/backend/ru/basis.json
index bc67e789..2935f564 100644
--- a/backend/ru/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/ta/basis.json b/backend/ta/basis.json
index 1ee8fd89..5acf33c3 100644
--- a/backend/ta/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/te/basis.json b/backend/te/basis.json
index 1ee8fd89..5acf33c3 100644
--- a/backend/te/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/tl/basis.json b/backend/tl/basis.json
index 2808511f..e6f646c5 100644
--- a/backend/tl/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/tr/basis.json b/backend/tr/basis.json
index 4823689b..e491343e 100644
--- a/backend/tr/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/uk/basis.json b/backend/uk/basis.json
index 33711aa0..3704b8f4 100644
--- a/backend/uk/basis.json
+++ b/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"
     }
 }
\ No newline at end of file
diff --git a/backend/zh/basis.json b/backend/zh/basis.json
index 1ee8fd89..5acf33c3 100644
--- a/backend/zh/basis.json
+++ b/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"
     }
 }
\ No newline at end of file