alexbfree
commented
3 years ago This somewhat overlaps with hestiaAI/hestialabs-experiences#366 . The difference is this is about structure as opposed to data, and is about proactively detecting what is shareable and suggesting users share it vs relying on explicit user action.
hestiaAI/hestialabs-experiences#366 is higher priority, but it would still be nice to automatically gather some info.
Perhaps one thing that needs to be done here is that "Structure Only" becomes a sharing option within the consent form (see hestiaAI/digipower-data-experiences#86)
Action for @pdehaye and @alexbfree : Refine requirements here.
pdehaye
[Low Priority] Do not do this ticket until tickets hestiaAI/digipower-data-experiences#36 to hestiaAI/digipower-data-experiences#54 are complete.
We should update the base functionality of ALL digipower experiences with the following feature: 1) Each time a new zipfile is uploaded, extract filename + structural information (directory structure, filenames within zip) and store this structural info in session. 2) For each JSON file, CSV file [Stretch goal: also HTML, XML, KML], extract structural information (data types and tree shape ONLY, no actual text values or fieldnames) and store this structural info in session. 3) Create a button ("Share the structure of my data") at the end of the list of experiences.
When you click that button, it shows a screen summarising all the structural summary information that has been gathered
A message at the top should say
"To aid the development of future experiences, we would like to invite you to share information about the structure of your data with Hestia.AI. Please review the information below, mask any data you do not want to share, and press "Share Structure Information" when done
title to say: "Structural Information Gathered So Far"
Then there should be a list of saved structure data. After each directory, a "Mask Directory Name" and "Mask All Filenames in This Directory" button. After each filename, a "Mask Filename" button. These mask buttons visibly hide the text string, replacing it with just "" or some data type indicator. Masking should permanently modify the cache in browser so they never have to mask that same item again (except if captured anew after clear).
At the bottom of the page, a "Share Structure Information" button should share the data (respecting any mask settings) with Hestia in a similar way to the sharing of experience data (but no need for encryption this time).
There should be an email notification generated.
Upon share, once sending is known to be successful, the cached data should be cleared.