Handle hierarchical project > doc > section & url in Edit app (+ read/write Google Sheet)

[bbest]

Transfer:

• from: documents data | marineenergy.app - Google Sheet

  project	doc NAME	ATTACHMENT NAME	url

• to: unique sheets that use drop-downs to get at project_docs, project_doc_sections

• and consume into db with update_ferc_docs() in /scripts/update.R

[cdobbelaere]

Hi @bbest, it looks like I need access to the data | marineenergy.app - Google Sheet - either cdobbelaere@ucsb.edu or cristinadobbelaere@gmail.com should work. Thanks!

[bbest]

Ah whoops, I should've done that already. Ok, just gave you access :)

[cdobbelaere]

No worries, just got it! @bbest

[bbest]

Ok, looks like you got this to work well in Google Sheets but the multiple levels of hierarchy seem too complicated to handle with its data validation:

• projects
  • documents
  • attachments (aka sections)

Ideally, something like Access subdatasheet would be available in Shiny DT::datatable(), eg Access 2016 Tables: Subdatasheets - YouTube @ 8:20:

But here's what we found:

• Extending DT child rows example most promising, hopefully the child table could also be editable
• Child Rows
• javascript - Parent/Child Rows in R shiny Package - Stack Overflow
• R Shiny DT Child Row Selection and Info · Issue #660 · rstudio/DT
• Shiny DT Child Row Selection and Info Issue · Issue #659 · rstudio/DT

[bbest]

This solution seems to work :) Manually edit child row in shiny datatable - Stack Overflow:

See DTedit-subdatasheet/test.R

[bbest]

Hi @cdobbelaere, here also is a more thorough explanation of this NestedData() approach:

• Child tables with DT, editing, exporting | R-bloggers

[cdobbelaere]

Thanks @bbest! Very helpful.

[bbest]

Actually @cdobbelaere, I'm thinking we could handle all of this more simply with selectizeInput(..., create = T) inside a renderUI() and some observe() functions to detect a new list item plus updateSelectizeInput(). See: Shiny - Using selectize input:

# allow creation of new items in the drop-down list
selectizeInput(
  'foo', label = NULL, choices = state.name,
  options = list(create = TRUE)
)

[cdobbelaere]

@bbest - Sounds like a good plan of action - will look into it right now.

Are we thinking that we'd update the project choices (via create = TRUE) for the DTedit ferc docs table as a whole, or would this be for a separate tab with the docs/sections/URLs corresponding to each project?

I was initially using this approach for updating the project choices for the DTedit ferc docs table, but the selectizeInput() and selectize.options didn't seem to be working (they were from the DavidPatShuiFong modularized version of DTedit), similarly to how we were having difficulties adding in checkboxInputs.

[cdobbelaere]

Hi @bbest, exciting news!! I was finally able to get the correct DavidPatShuiFong version of DTedit installed, and we now have checkboxInputs functioning! Now to see if we can get the selectize.options from this particular commit in order.

[cdobbelaere]

Screenshots showing

1. checkboxInput functionality

   

2. ability to create a new project within edit panel

   

[bbest]

We can use update.R's update_ferc_docs() and update the GoogleSheet data | marineenergy.app - Google Sheets with googlesheets4::sheet_write().