Skip to Main Content
Spotfire Ideas Portal

Spotfire Library - TIBCO supported views on Spotfire library metadata

Could TIBCO deliver "native views" (materialized?), developed and maintained by TIBCO that could provide real insights in the Spotfire library? I am aware of this article (https://community.tibco.com/wiki/tibco-spotfire-metadata-queries), but it is not complete enough.

I am thinking on being able to find (list non exhaustive):

  • Orphans building blocks

  • Invalid data sources (with cause, affected information links, reports and so on)

  • Invalid information links (with cause, affected reports and so on)

  • Using joins with information links

  • Using filters and values in information links

  • Other values that can be seen from the GUI within Information Designer

  • Type and count of data tables for each report

  • Which particular packages are using in reports (like an in house developed extension for example - We had recently a case where we wondering which files / users had a particular plugin in their reports, requesting to test a newer version of the plugin)

  • Top report usage (who, when and so on)

  • Scripting content

  • Any other information that could be useful from an administration side

This would ease keeping the library in good shape, find out possible issues (allowing to fix them) before they are noticed on the user side.

Thank you for your consideration.

Kind regards.

  • Attach files
      Drop here to upload
    • Guest
      Reply
      |
      Feb 18, 2023

      The 'TIBCO Spotfire® Metadata Queries' article written by @Julieta Diaz is great, but I have a Postegres server as the backend of my company's Spotfire Library. TIBCO, please consider Metadata views for ALL TIBCO supported Spotfire server types (Postgres, MS SQL, Oracle, etc) for on-prem installations, not just Oracle instance.

    • Guest
      Reply
      |
      Apr 21, 2020

      Thank you Miguel for setting this idea Under Consideration.

    • Admin
      Miguel Diez
      Reply
      |
      Apr 20, 2020

      Thanks Xavier. Those are good use cases. We are looking into improving library search usage and we are going to think on your suggestions.