Approval in backend

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"
     }
 }