ru_setup | R Documentation |
ruODK
settings.Settings are returned invisibly and additionally printed depending on
get_ru_verbose
.
ru_setup(
svc = NULL,
pid = NULL,
fid = NULL,
url = NULL,
un = NULL,
pw = NULL,
pp = NULL,
tz = NULL,
odkc_version = NULL,
retries = NULL,
verbose = NULL,
test_svc = NULL,
test_pid = NULL,
test_fid = NULL,
test_fid_zip = NULL,
test_fid_att = NULL,
test_fid_gap = NULL,
test_fid_wkt = NULL,
test_url = NULL,
test_un = NULL,
test_pw = NULL,
test_pp = NULL,
test_odkc_version = NULL
)
svc |
(optional, character) The OData service URL of a form.
This parameter will set |
pid |
(optional, character) The ID of an existing project on |
fid |
(optional, character) The alphanumeric ID of an existing form
in |
url |
An ODK Central URL,
e.g. "https://sandbox.central.getodk.org".
This will override the ODK Central base URL from |
un |
An ODK Central username which is the email of a "web user" in the
specified ODK Central instance |
pw |
The password for user |
pp |
The passphrase (optional, character) for an encrypted form. |
tz |
Global default time zone.
|
odkc_version |
The ODK Central version as major/minor version, e.g. 1.1. |
retries |
The number of attempts to retrieve a web resource. This parameter is given to Default: 3. |
verbose |
Global default for
|
test_svc |
(optional, character) The OData service URL of a test form.
This parameter will set |
test_pid |
(optional, character) The numeric ID of an existing project
on |
test_fid |
(optional, character) The alphanumeric ID of an existing form
in |
test_fid_zip |
(optional, character) The alphanumeric ID of an existing
form in |
test_fid_att |
(optional, character) The alphanumeric ID of an existing
form in |
test_fid_gap |
(optional, character) The alphanumeric ID of an existing
form in |
test_fid_wkt |
(optional, character) The alphanumeric ID of an existing
form in |
test_url |
(optional, character) A valid ODK Central URL for testing.
This will override the ODK Central base URL from |
test_un |
(optional, character) A valid ODK Central username (email)
privileged to view the test project(s) at |
test_pw |
(optional, character) The valid ODK Central password for
|
test_pp |
(optional, character) The valid passphrase to decrypt the
data of encrypted project |
test_odkc_version |
The ODK Central test server's version as major/minor version, e.g. 1.1. |
ru_setup
sets ODK Central connection details.
ruODK
's functions default to use the default project ID,
form ID, URL, username, and password unless specified explicitly.
Any parameters not specified will remain unchanged. It is therefore possible
to set up username and password initially with
ru_setup(un="XXX", pw="XXX")
, and switch between forms with
ru_setup(svc="XXX")
, supplying the form's OData service URL.
ODK Central conveniently provides the OData service URL in the form
submission tab, which in turn contains base URL, project ID, and form ID.
ruODK
's automated tests require a valid ODK Central URL, and a
privileged username and password of a "web user" on that ODK Central
instance, as well as an existing project and form.
Other ru_settings:
odata_svc_parse()
,
parse_odkc_version()
,
ru_settings()
,
semver_gt()
,
semver_lt()
,
yell_if_error()
,
yell_if_missing()
# `ruODK` users only need default settings to their ODK Central:
ru_setup(url = "https://my-odkc.com", un = "me@email.com", pw = "...")
# `ruODK` contributors and maintainers need specific ODK Central
# instances to run tests and build vignettes, see contributing guide:
ru_setup(
url = "https://odkcentral.dbca.wa.gov.au",
un = "me@email.com",
pw = "...",
pp = "...",
test_url = "https://sandbox.central.getodk.org",
test_un = "me@email.com",
test_pw = "...",
test_pp = "...",
test_pid = 14,
test_fid = "build_Flora-Quadrat-0-2_1558575936",
test_fid_zip = "build_Spotlighting-0-6_1558333698",
test_fid_att = "build_Flora-Quadrat-0-1_1558330379",
test_fid_gap = "build_Turtle-Track-or-Nest-1-0_1569907666",
test_fid_wkt = "build_Locations_1589344221",
retries = 3,
verbose = TRUE
)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.