-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy path70-add-on-packages.Rmd
32 lines (21 loc) · 1.71 KB
/
70-add-on-packages.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
# (PART) Related tools {-}
# Add-on packages {#add-on-packages}
There are a growing number of packages that provide the Disco Engine user with additional functionality:
## `discoappend`
`discoappend` allows you to output additional data (beyond just IDs) based on your disco engine definitions. For an introduction with examples, check [the official README](https://github.com/cwolfsonseeley/discoappend#discoappend).
## `discovcr`
`discovcr` allows you to browse data related to your discovery engine definition and select just the IDs you want to keep. This can be particularly useful when using text-search widgets such as `fund_text_contains`, where you may want to review the individual allocations you captured in your original search and remove any that were false matches (for example, a search for funds related to "diversity" brings in a number of biology research funds related to bio-diversity).
For a detailed introduction to using `discovcr`, read the "vignette" that includes examples and instructions by typing:
```{r, eval = FALSE}
vignette("vcr-intro", package = "discovcr")
```
## `discoscape`
The `discoscape` package serves as a bridge between the Discovery Engine and DonorScape. The `donorscape_report` function outputs data in the format required by the DonorScape screening service, so that you can discover and/or define a population using the Discovery Engine, and then immediately run that population through a DonorScape without much hassle in between.
As with any package, you can load it up by using the `library` function:
```{r, eval = FALSE}
library(discoscape)
```
The main function is called `donorscape_report`, and you can learn more about it by typing:
```{r, eval = FALSE}
?donorscape_report
```