The Rest to Excel library is a good candidate to use the scriptDB to store its library data for both Excel and GAS. However, since I will be using the scriptDB for many things, I wanted to first formalize how I was going to approach data siloing, since that could get tiresome in the future.
I'm using a couple of new classes - cScriptDbSilo and cScriptDbSiloItem to automate that. Here's a test example that uses 2 differentt scriptDb - a local one, and the one associated with the mcpher shared library. ScriptDB also makes a useful lockBox.
That gives this result
Using a Silo manager like this enforces some standardization on how you partition data in this 'tableless' database. You can have as many silos as you want, each identified by some unique key.
If the default scriptDb you want to use is not the one associated with the mcpher library, then you can change it by an initial call like this
or later by changing the xDb property
You are only able to delete data that you created. Items are written with a time stamp and the user who wrote it. Deleting checks that the user ID matches before allowing deletion. I'll also be updating this shortly to restrict shared library to read only.
You can use the mcpher library mentioned in Creating a Google Apps Script Library to access this and to see the code. A snapshot of the code is in this gist and reproduced below.
The code is in the mcpher library. See here for how to incorporate it into your project.