KorAPConnection() creates a connection to a KorAP server for corpus queries.
This is your starting point for all corpus analysis tasks.
KorAPConnection() object that can be used e.g. with corpusQuery()
URL of the web user interface of the KorAP server instance you want to access.
Defaults to the environment variable KORAP_URL if set and to the IDS Mannheim KorAP main instance
to query DeReKo, otherwise. In order to access the KorAP instance at the German
National Library (DNB) to query the contemporary fiction corpus DeLiKo@DNB,
for example, set KorAPUrl to https://korap.dnb.de/.
which version of KorAP's API you want to connect to. Defaults to "v1.0".
URL of the KorAP web service. If not provided, it will be constructed from KorAPUrl and apiVersion.
OAuth2 access token. For queries on corpus parts with restricted access (e.g. textual queries on IPR protected data), you need to authorize your application with an access token. You can obtain an access token in the OAuth settings of your KorAP web interface.
More details are explained in the authorization section of the RKorAPClient Readme on GitHub.
To use authorization based on an access token in subsequent queries, initialize your KorAP connection with:
kco <- KorAPConnection(accessToken="<access token>")
In order to make the API
token persistent for the currently used KorAPUrl (you can have one
token per KorAPUrl / KorAP server instance), use:
persistAccessToken(kco)
This will store it in your keyring using the
keyring::keyring-package. Subsequent KorAPConnection() calls will
then automatically retrieve the token from your keying. To stop using a
persisted token, call clearAccessToken(kco). Please note that for
DeReKo, authorized queries will behave differently inside and outside the
IDS, because of the special license situation. This concerns also cached
results which do not take into account from where a request was issued. If
you experience problems or unexpected results, please try kco <- KorAPConnection(cache=FALSE) or use
clearCache() to clear the cache completely.
An alternative to using an access token is to use a browser-based oauth2 workflow
to obtain an access token. This can be done with the auth() method.
OAuth2 client object.
OAuth2 scope. Defaults to "search match_info".
logical that indicates if authorization is supported/necessary for the current KorAP instance. Automatically set during initialization.
user agent string. Defaults to "R-KorAP-Client".
timeout in seconds for API requests (this does not influence server internal timeouts). Defaults to 240 seconds.
logical that decides whether following operations will default to be verbose. Defaults to FALSE.
logical that decides if API calls are cached locally. You can clear
the cache with clearCache(). Defaults to TRUE.
# Connect to KorAP
kcon <- KorAPConnection()# Search for a term
query <- corpusQuery(kcon, "Ameisenplage")
# Get all results
results <- fetchAll(query)
For access to restricted corpora, authorize your connection:
kcon <- KorAPConnection() |> auth()
Use KorAPConnection() to connect, then corpusQuery() to search, and
fetchAll() to retrieve results. For authorized access to restricted corpora,
use auth() or provide an accessToken.
The KorAPConnection object contains various configuration slots for advanced users: KorAPUrl (server URL), apiVersion, accessToken (OAuth2 token), timeout (request timeout), verbose (logging), cache (local caching), and other technical parameters. Most users can ignore these implementation details.
Other initialization functions:
auth,KorAPConnection-method,
clearAccessToken,KorAPConnection-method,
persistAccessToken,KorAPConnection-method