Skip to content

Latest commit

 

History

History
52 lines (44 loc) · 1.69 KB

README.md

File metadata and controls

52 lines (44 loc) · 1.69 KB

datafinisher_webapp

Web front-end for modifying DataFinisher files. Here is a demo.

Quick Start

First, clone this repo along with its dependency. In bash or some similar command shell:

git clone [email protected]:bokov/datafinisher_webapp
cd datafinisher_webapp
git checkout integration
git submodule update --init --recursive
R

Then, in an R session...

# install dependencies
install.packages(c('reticulate','readr','shiny','dplyr','devtools'
                    ,'shinyjs','shinyalert'))
devtools::install_github("harveyl888/queryBuilder")

# assuming you are still in the top-level project directory...
shiny::runApp('dfshiny')

The hard part is not DataFinisher, really. The hard part is deploying DataBuilder and figuring out how to configure it to create those .db files for you.

Here is what passes for an API at this stage...

These are all the calls that Shiny currently makes to DFMeta attributes:

py$dfmeta$data$dialect$delimiter;
py$dfmeta$inhead;

These are all the calls that Shiny currently makes to to four distinct DFMeta methods, getStatIDs, makeNameUnq, useDesignedRule, and getColIDs.

py$dfmeta$getStatIDs();
py$dfmeta$makeNameUnq(newname,'rulename',maxlen=int(12))
py$dfmeta$userDesignedRule(newrule,rulename,as.list(input$customSelCols));

py$dfmeta$getColIDs(ids='divIDchosen');
py$dfmeta$getColIDs(ids='incolid');
py$dfmeta$getColIDs(asdicts=T,ids='incolid'
                    ,childids=c('rulename','addbid')
                    ,childtype='rules');

No calls are being made to any Python object that isn't part of a DFMeta object