Get rid of fokus.local_deploy_path
:
export_qstnr/_all()
's param local_deploy_path
to path
/output
or the like which defaults to the relative path output/
.deploy
param and its functionality (and instead directly deploy from the fokus_reports
' output dir to Netlify).Somehow, including multiple asciicasts in the same Rmd doesn't work properly (the second asciicast's <asciinema-player>
custom HTML tag is missing in the
resulting HTML; both via asciicast's knitr engine as well as embedding the generated asciicast htmlwidget via asciicast::asciinema_player()
), thus the
second asciicast containing an intentionally triggered error in the raw qstnr had to be removed.
-> Investigate the actual cause of the inclusion failure (and report/fix upstream)!
The removed vignette part is:
```` If some mistake that breaks questionnaire generation is present in the raw questionnaire, like a syntax error in embedded R code for example, an error is thrown and the progress output stops, allowing to easily locate the source position of the mistake:
{r, echo = FALSE}
fs::path_package("asciicasts/gen_qstnr_tibble-failed.json",
package = "fokus") %>%
asciicast::read_cast() %>%
# playback speed is not stored in the asciicast itself, so has to be set here
asciicast::asciinema_player(speed = 0.75)
As one can see from the output above, the error occurred when processing key variable_label
, and from further above we can see that the key belongs to
the item first_name
which in turn is defined under branch path 00_cantonal_statistical_office.002_to_polling_agency
.
````
For some reason, documenting the internal data objects raw_qstnr
, raw_qstnrs_suppl
and qstnr_item_keys
in the usual way (documenting the object name
sentinel, e.g. "raw_qstnr"
) fails with the error
Error: 'raw_qstnr' is not an exported object from 'namespace:fokus'
while the other internal data objects can be documented fine that way (e.g. all_ballot_dates
)... seems to be related to @keywords internal
and the Rd's
autogenerated \usage
section and \docType
tags...
add who
vaue for ehemals erwerbstätige Online-Respondenten
whose filter equals the nichterwerbstätige Online-Respondenten
conditions plus
former_employment_situation %in% 1:4
and use that for
former_employment_level
former_occupational_sector
former_company_size
former_company_sector
Ask Uwe whether easyvote booklet actually covers cantonal proposals. If not, the distinction between
cantonal_proposals_information_source_easyvote_booklet
and federal_proposals_information_source_easyvote_booklet
doesn't make sense and we could merge
the variable with information_source_easyvote_booklet
(which currently refers to the election booklet only).
Clean-ups:
who
keyConsider introducing a mechanism to define truly hierarchical first-item question intros on table lvl above item
lvl. But maybe not worth the effort? Wait
until we conduct an online survey by ourselves to get better understanding of actual requirements!
add var latent_expertise_proposals
that combines expertise on cantonal and federal proposals
Port the FOKUS questionnaire to qstnr!
Supplemental date-specific TOML questionnaire files:
mode = "majority"
defined under table cantonal.aargau.election.majoritarian.1
(seems bollocks)Consider relying on external package for frequency tables and other summary statistics. A good (but a bit aged) overview of available packages is found here
Export CSV data in CSV on the Web (CSVW) format using package csvw once it supports writing CSVW.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.