Browser extension: ignore HTTPheader content-disposition:attachment; for the combinations of MIMEtype&URL you set.
If possible make a difference between files manually opened and those by other files (maybe based on whether a window object is in context)
Say someone saves stuff on a network drive from within Excel, and that is sort of the top of what this person is capable of doing technically (either by skill, time, interest, or what sysadmin allows). The network drive has a webinterface too. Still people keep explaining each other where files are located in the file explorer, instead of sending links you can click. Now you as a web-dataviz person (but without all the access of the busy sysadmins) did interest that person (and other persons doing entry of the same type of data) into some of the dataviz examples you've shown, but doesn't want this to turn into a mail back-and-forth recurring job with a risk of version hell. The 'data entry person' was interested in being able to having it viewable by anybody (who is allowed by login) on any device, also when Excel is not available there. With a dataviz URL that has the dataURL as a parameter, multiple data files can be edited and the moment the dataviz runs it uses the last saved version of the data. Many client-side web visualisation libraries need .csv files, not Excel. "Save as .csv" is no rocket science however. The dataviz (automatically, as it's client-side) can only load the data if the person loading it has viewing rights to the data used. Of course everybody needs to install the browser extension this is about, but people can be pointed there by the then-not-working-dataviz. The structure needed for these datavisualisations, helps people improve their spreadsheets for other purposes too.
#remarks When D3js is used, the dataviz can easily be used in PowerBI and Excel (through E2D3). It could tell people about webDAV and how to install/configure that. Have the extension to install on the webdrive for everybody
Can Office365 serve files, or only 'enhanced' by wrapping them in some webbased viewer?
(possible companion of dataCentricFileExploring)
Also see:
-
tabFS: "apply all the existing tools on your computer that already know how to deal with files -- terminal commands, scripting languages, point-and-click explorers, etc -- and use them to control and communicate with your browser"