Spotfire Ideas Portal
As an administrator I would be interested in having an option to build an external database for the Library, this way keeping the actual system database slim and providing options to link multiple libraries and provide multiple storage locations.
e.g: this allows for business departments to have their own library and a shared Library as well.
it can also be convenient to store embedded analysis for example towards a library linked to a public facing Spotfire Server.
(on a sidenote: I recently discovered that we can now link the TDV repository to Spotfire, however I havent completely explored that path)
0
Future Consideration
Hi Gerko,
We have this partially. You can use AWS S3, Azure Blob Storage or Google Cloud Storage as the external storage for the Spotfire library items. By doing that, the Spotfire database is only used for the items metadata.
The new thing would be to have connection to different external storages. What is your use case? Why using different storages? Is it for different groups of users that will not share and see each other´s content? (isolated tenants) Why?
thanks
This would be very helpful, especially if configuration allowed for flexible search.
Just as the TDV Integration ("Data Catalog") supports connection to multiple instances, it would be fantastic if the Spotfire Library also supported connection to multiple databases, that could each be configured with a customizable name. The example of having embedded analyses in a separate database is a good one -- another would be separating personal/project files from departmental dashboards, certified from non-certified, etc.
Related to this (and equal in terms of importance) would be to be able to limit a search query to a specific database through the UI, without having to master specific search syntax.