Approval in backend
This commit is contained in:
jrenslin authored and 
md translation bot committed
1 parent
2603b7df88
commit
1ef20acc1d
50 files changed
+350
-50
No files matched your search
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -125,6 +125,8 @@
|
||||
"search_by_collection_inclusive": "Suche Objekte die dieser Sammlung oder einer der ihr untergeordneten Sammlungen zugeordnet sind.",
|
||||
"search_by_collection_exclusive": "Suche Objekte, die exakt dieser Sammlung - nicht den ihr untergeordneten Sammlungen - zugewiesen sind.",
|
||||
"search_by_space_inclusive": "Suche Objekte die diesem Raum oder einem der ihm untergeordneten R\u00e4ume zugeordnet sind.",
|
||||
"search_by_space_exclusive": "Suche Objekte, die exakt diesem Raum - nicht den ihr untergeordneten R\u00e4umen - zugewiesen sind."
|
||||
"search_by_space_exclusive": "Suche Objekte, die exakt diesem Raum - nicht den ihr untergeordneten R\u00e4umen - zugewiesen sind.",
|
||||
"data_dissemination": "Datenweitergabe",
|
||||
"data_dissemination_intro": "Links zu den Endpunkten, die genutzt werden k\u00f6nnen, um verschiedene Datenbest\u00e4nde der Institution in maschinenlesbarer Form und potentiell automatisiert abzurufen."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -422,6 +422,16 @@
|
||||
"currently_configured": "Derzeit konfiguriert",
|
||||
"format": "Format",
|
||||
"use_case": "Use case",
|
||||
"hide": "Verstecken"
|
||||
"hide": "Verstecken",
|
||||
"api": "API",
|
||||
"apis": "Programmierschnittstellen",
|
||||
"data_harvesting": "Data harvesting",
|
||||
"data_harvesting_explica": "Data harvesting beschreibt das automatische und regelm\u00e4\u00dfige abrufen von Datensets aus einer Datenquelle. Um einen vollst\u00e4ndig automatisierten Prozess zu erm\u00f6glichen, beschreiben offene Standards wie OAI-PMH standartisierte Schnittstellen um gr\u00f6\u00dfere Datenbest\u00e4nde Schritt f\u00fcr Schritt in kleineren, leichter bearbeitbaren Einheiten abzurufen. Die konkreten einzelnen Eintr\u00e4ge - im Falle von museum-digital die ver\u00f6ffentlichte Objektdatens\u00e4tze - werden dann mithilfe passender offener Standards wie z.B. LIDO beschrieben um etwa externen Plattformen regelm\u00e4\u00dfige und vollst\u00e4ndig automatisierte Datenabgleiche zu erm\u00f6glichen.",
|
||||
"oai_pmh_explica_md": "Die OAI-PMH-Implementation von museum-digitals Portalen kann genutzt werden, um \u00fcber museum-digital ver\u00f6ffentlichte Objektdatens\u00e4tze stapelweise f\u00fcr einen Datenabgleich abzurufen. Sie ist dabei flexibel: Der Suchlogik folgend k\u00f6nnen die Daten einzelner Museen oder z.B. auch einzelner Sammlungen abgerufen werden. Direkt folgend findet sich die URL des OAI-PMH-Endpunktes, den externe Partner nutzen k\u00f6nnen, um einen Datenabgleich aller von einer Institution ver\u00f6ffentlichten Objektdatens\u00e4tze durchzuf\u00fchren.",
|
||||
"apis_explica": "Programmierschnittstellen oder Application Programming Interfaces (APIs) bieten einen stabilen, maschinenlesbaren Zugang zu den Daten und Funktionen einer Anwendung. Programmierende k\u00f6nnen Sie nutzen um darauf aufbauende weitere Funktionalit\u00e4ten oder Anwendungen zu implementieren.",
|
||||
"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.\r\n\r\n\r\nIf 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-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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -125,6 +125,8 @@
|
||||
"search_by_collection_inclusive": "\u0428\u0443\u043a\u0430\u0442\u0438 \u043e\u0431\u2019\u0454\u043a\u0442\u0438, \u043f\u043e\u0432\u2019\u044f\u0437\u0430\u043d\u0456 \u0437 \u0446\u0456\u0454\u044e \u043a\u043e\u043b\u0435\u043a\u0446\u0456\u0454\u044e \u0430\u0431\u043e \u0431\u0443\u0434\u044c-\u044f\u043a\u043e\u044e \u0437 \u0457\u0457 \u043f\u0456\u0434\u043f\u043e\u0440\u044f\u0434\u043a\u043e\u0432\u0430\u043d\u0438\u0445 \u043a\u043e\u043b\u0435\u043a\u0446\u0456\u0439.",
|
||||
"search_by_collection_exclusive": "\u0428\u0443\u043a\u0430\u0442\u0438 \u043e\u0431\u2019\u0454\u043a\u0442\u0438, \u043f\u043e\u0432\u2019\u044f\u0437\u0430\u043d\u0456 \u0441\u0430\u043c\u0435 \u0437 \u0446\u0456\u0454\u044e \u043a\u043e\u043b\u0435\u043a\u0446\u0456\u0454\u044e (\u0431\u0435\u0437 \u043e\u0431\u2019\u0454\u043a\u0442\u0456\u0432, \u043f\u043e\u0432\u2019\u044f\u0437\u0430\u043d\u0438\u0445 \u0456\u0437 \u0457\u0457 \u043f\u0456\u0434\u043f\u043e\u0440\u044f\u0434\u043a\u043e\u0432\u0430\u043d\u0438\u043c\u0438 \u043a\u043e\u043b\u0435\u043a\u0446\u0456\u044f\u043c\u0438).",
|
||||
"search_by_space_inclusive": "\u0428\u0443\u043a\u0430\u0442\u0438 \u043e\u0431\u2019\u0454\u043a\u0442\u0438, \u043f\u043e\u0432\u2019\u044f\u0437\u0430\u043d\u0456 \u0437 \u0446\u0438\u043c \u043f\u0440\u0438\u043c\u0456\u0449\u0435\u043d\u043d\u044f\u043c \u0430\u0431\u043e \u0431\u0443\u0434\u044c-\u044f\u043a\u0438\u043c \u0456\u0437 \u0439\u043e\u0433\u043e \u043f\u0456\u0434\u043f\u043e\u0440\u044f\u0434\u043a\u043e\u0432\u0430\u043d\u0438\u0445 \u043f\u0440\u0438\u043c\u0456\u0449\u0435\u043d\u044c.",
|
||||
"search_by_space_exclusive": "\u0444\u0428\u0443\u043a\u0430\u0442\u0438 \u043e\u0431\u2019\u0454\u043a\u0442\u0438, \u043f\u043e\u0432\u2019\u044f\u0437\u0430\u043d\u0456 \u0441\u0430\u043c\u0435 \u0437 \u0446\u0438\u043c \u043f\u0440\u0438\u043c\u0456\u0449\u0435\u043d\u043d\u044f\u043c (\u0431\u0435\u0437 \u043e\u0431\u2019\u0454\u043a\u0442\u0456\u0432, \u043f\u043e\u0432\u2019\u044f\u0437\u0430\u043d\u0438\u0445 \u0456\u0437 \u0439\u043e\u0433\u043e \u043f\u0456\u0434\u043f\u043e\u0440\u044f\u0434\u043a\u043e\u0432\u0430\u043d\u0438\u043c\u0438 \u043f\u0440\u0438\u043c\u0456\u0449\u0435\u043d\u043d\u044f\u043c\u0438).Search objects linked to exactly this space (not those linked to any of its subordinates spaces)."
|
||||
"search_by_space_exclusive": "\u0444\u0428\u0443\u043a\u0430\u0442\u0438 \u043e\u0431\u2019\u0454\u043a\u0442\u0438, \u043f\u043e\u0432\u2019\u044f\u0437\u0430\u043d\u0456 \u0441\u0430\u043c\u0435 \u0437 \u0446\u0438\u043c \u043f\u0440\u0438\u043c\u0456\u0449\u0435\u043d\u043d\u044f\u043c (\u0431\u0435\u0437 \u043e\u0431\u2019\u0454\u043a\u0442\u0456\u0432, \u043f\u043e\u0432\u2019\u044f\u0437\u0430\u043d\u0438\u0445 \u0456\u0437 \u0439\u043e\u0433\u043e \u043f\u0456\u0434\u043f\u043e\u0440\u044f\u0434\u043a\u043e\u0432\u0430\u043d\u0438\u043c\u0438 \u043f\u0440\u0438\u043c\u0456\u0449\u0435\u043d\u043d\u044f\u043c\u0438).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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
@@ -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."
|
||||
}
|
||||
}
|
||||
+11
-1
@@ -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)"
|
||||
}
|
||||
}
|
||||
Reference in new issue
Block a user