What new feature would you like to see implemented?
The following would help users manage a set of several GFTs and linked GSSs
1. A schematic/ visual report showing the linkages between GFTs - showing a
user what GFTs have been merged to create what other GFTs. The (i) GFT
Filename, (ii) ID, (iii) Visibility (Private, etc.) and Reuse settings
(Download permitted or not), and (iv) Reuse Licence, should be visible.
2. A schematic/ visual report showing the linkages between GFTs and the GSSs
that may be updating (synchronising) them using scripts. The GFT Filename and
ID should be visible along with the GSS Filename. The following should be
visible for the GSS:
(i) The docid being used by the GSS script
(ii) Whether the Fusion Tables service is 'on' for Apps Script and in the
Developer Console
(iii) Whether the script being used is 'authenticated'
(iv) The triggers that may be present
How will you use it?
I would use the above feature to more easily manage the multiple GSSs, and GFTs
that it takes to produce the open data 'Chikungunya in the Americas' site at
http://health.caribbeangis.com/chikungunya
--------------------------------------------------------------------------
NOTE: Use this form to suggest new features for Google Fusion Tables
website or API. For BUGS, please e-mail us at googletables-
feedback@google.com.
Your "star" vote on requests in this issue tracker helps the Fusion Tables
team prioritize work on the most useful features.
By submitting this form you agree to the Google Terms of Service
(http://www.google.com/accounts/TOS) and the following additional term:
In addition to the Content license you grant to Google in Section 11 of the
Google Terms of Service, you agree that Google may, at its option, use your
Content to provide support for, or to develop, correct or improve Google's
current or future products and services, without any compensation to you.
Thanks for the suggestion!
--------------------------------------------------------------------------
Original issue reported on code.google.com by vi...@caribbeangis.com on 6 Oct 2014 at 2:39
Original issue reported on code.google.com by
vi...@caribbeangis.comon 6 Oct 2014 at 2:39