You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would make sense to import a set of common functions/"API" around the TAGSExplorer spreadsheets. So the first step is presumably making a commitment somehow to a library function that grabs data from the spreadsheet, and maybe normalises/defines column headings we are going to use?
At the moment I am using gsqAPI() which is buried in examples files.
[Ultimately, I guess we should work towards a TAGSExplorer library in its own right (though I have no idea at, how to create one of these!]
The text was updated successfully, but these errors were encountered:
Would make sense to have a library approach for core functions. Column heading are reasonably stable (although I might sneak in to_user). Issue might be if people try these out on older versions of TAGS where column names/order were different. It's a shame the spreadsheet query language doesn't support queries using column names. I need to start describing what scripts do in the heading
It would make sense to import a set of common functions/"API" around the TAGSExplorer spreadsheets. So the first step is presumably making a commitment somehow to a library function that grabs data from the spreadsheet, and maybe normalises/defines column headings we are going to use?
At the moment I am using gsqAPI() which is buried in examples files.
[Ultimately, I guess we should work towards a TAGSExplorer library in its own right (though I have no idea at, how to create one of these!]
The text was updated successfully, but these errors were encountered: