Approval in backend

backend/kn/action.json

@@ -125,6 +125,8 @@
         "search_by_collection_inclusive": "Search objects linked to this collection or any of its subordinate collections.",
         "search_by_collection_exclusive": "Search objects linked to exactly this collection (not those linked to any of its subordinates collections).",
         "search_by_space_inclusive": "Search objects linked to this space or any of its subordinate spaces.",
-        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
+        "search_by_space_exclusive": "Search objects linked to exactly this space (not those linked to any of its subordinates spaces).",
+        "data_dissemination": "Data dissemination",
+        "data_dissemination_intro": "Links to the endpoints users can use to access different pools of data of the institution in an automated or machine-readable way."
     }
 }

backend/kn/basis.json

@@ -422,6 +422,16 @@
         "currently_configured": "Currently configured",
         "format": "Format",
         "use_case": "Use case",
-        "hide": "Hide"
+        "hide": "Hide",
+        "api": "API",
+        "apis": "APIs",
+        "data_harvesting": "Data harvesting",
+        "data_harvesting_explica": "Data harvesting describes the automated and regular retrieval of data from a data source. To facilitate a fully automated process, open standards such as OAI-PMH describe standardized interfaces for retrieving large datasets subdivided into smaller batches. The specific data - in museum-digital's case published object data - is then expressed using standards such as LIDO to allow external platforms and the like automatic, regular synchronizations.",
+        "oai_pmh_explica_md": "The OAI-PMH implementation of museum-digital's portals can be used to harvest published object data. It flexibly follows the search logic to further specify the retrieved data set. Below you can find the endpoint used to harvest the data of all published objects of your home institution. Adjusting the URL following the rules of the search logic allows further specification, e.g. to a single collection.",
+        "apis_explica": "Application programming interfaces provide a machine-readable access to the data and functionality of a programm. They thus allow programmers to build external applications on top of them.",
+        "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)"
     }
 }