dbFindFields

Given part of the name of a field of interest to the user, this
function returns the full field names used in records that were
previously loaded into a collection
(using ctrLoadQueryIntoDb). Only names of fields that have
a value in the collection can be returned.
Set <code>sample = FALSE</code> to force screening all records in the
collection for field names, see below.
See ctrShowOneTrial to interactively find fields.

A system for querying, retrieving and analyzing
protocol- and results-related information on clinical trials from
four public registers, the 'European Union Clinical Trials Register'
('EUCTR', <https://www.clinicaltrialsregister.eu/>),
'ClinicalTrials.gov' (<https://clinicaltrials.gov/> and also
translating queries the retired classic interface), the
'ISRCTN' (<http://www.isrctn.com/>) and the
'European Union Clinical Trials Information System'
('CTIS', <https://euclinicaltrials.eu/>).
Trial information is downloaded, converted and stored in a database
('PostgreSQL', 'SQLite', 'DuckDB' or 'MongoDB'; via package 'nodbi').
Protocols, statistical analysis plans, informed consent sheets and other
documents in registers associated with trials can also be downloaded.
Other functions implement trial concepts canonically across registers,
identify deduplicated records, easily find and extract variables
(fields) of interest even from complex nested data as used by the
registers, merge variables and update queries.
The package can be used for monitoring, meta- and trend-analysis of
the design and conduct as well as of the results of clinical trials
across registers.

Ralf Herold

ctrdata

Retrieve and Analyze Clinical Trials Data from Public Registers

dbFindFields function

<dl><dt>namepart</dt>
<dd>A character string (can be a regular expression,
including Perl-style) to be searched among all field names (keys)
in the collection, case-insensitive. The default `".*"` lists all fields.</dd>
<dt>con</dt>
<dd>A database connection object, created with
<code>nodbi</code>. See section `1 - Database connection` in
ctrdata.</dd>
<dt>sample</dt>
<dd>If <code>TRUE</code> (default), uses a sample of only 5 trial
records per register to identify fields, to rapidly return a possibly
incomplete set of field names.
If <code>FALSE</code>, uses all trial records in the collection, which will
take more time with more trials but ensures to returns all names of
all fields in the collection.</dd>
<dt>verbose</dt>
<dd>If <code>TRUE</code>, prints additional information
(default <code>FALSE</code>).</dd></dl>

Arguments

Find names of fields in the database collection — dbFindFields

<dl>

<dt>namepart</dt>
<dd>A character string (can be a regular expression,
including Perl-style) to be searched among all field names (keys)
in the collection, case-insensitive. The default `".*"` lists all fields.</dd>


<dt>con</dt>
<dd>A database connection object, created with
<code>nodbi</code>. See section `1 - Database connection` in
ctrdata.</dd>


<dt>sample</dt>
<dd>If <code>TRUE</code> (default), uses a sample of only 5 trial
records per register to identify fields, to rapidly return a possibly
incomplete set of field names.
If <code>FALSE</code>, uses all trial records in the collection, which will
take more time with more trials but ensures to returns all names of
all fields in the collection.</dd>


<dt>verbose</dt>
<dd>If <code>TRUE</code>, prints additional information
(default <code>FALSE</code>).</dd>

</dl>

dbFindFields: Find names of fields in the database collection

Description

Usage

Value

Arguments

Details

Examples