Need more integration between information designer, library administration and analysis interfaces. Merged

Issue:

Working with data sources/information links in context of tracing dependencies is highly inconvenient and functionality is split between several completely different places that cannot be even be opened at once. (You have to navigate both in information designer and library administration tool separately, one by one)

Typical use case to illustrate:

User has some analysis not working due to underlying data source being broken or no sufficient permissions for the data source, and Spotfire engineer needs to trace the problem.

This type of request involves using:

• library administration tool (for permissions checks, required_by, depends_on dependency search)

• information designer(to see columns, data source and information links internals)

• analysis data table properties (to identify information link)

All required functionality is spread across different interface places. We have literally to open multiple client instances to be able to see both information designer and library administration tool in the same time to do the job.

Proposal:

• It should be at least a hyperlink-like connection between library administration interface and information designer for the library elements so they will play well together. For example, a context menu in library administration interface that will open library item in information designer for editing fast. And, a context menu in information designer that will open a folder in library administration interface where the certain library item is located, so you could see library permissions fast.

• It should be possible to open both information designer and library administration in the same tame.

• It it should be possible to trace actual analysis dependencies, including data source, from the analysis interface itself.

• Context menu in library administration tool for creating required_by and depends_on searches automatically could be handy too for tracing dependencies.

• Error message should be more clear than just "data table not available", it should tell the actual reason - if database is unreachable, or user does not have sufficient privileges on the particular library item (data source, information link or information model elements)

• Data sources list in information designer should have filter search instead of just scrolling hundreds of them in a small window.