[FEATURE]Service, schema and root table selection

lmichel / TAP-complex-data

JS module helping users to query and browse complex data exposed in a IVOA TAP service

MIT License

5 stars 1 forks source link

[FEATURE]Service, schema and root table selection #36

Open galyfray opened 2 years ago

galyfray commented 2 years ago

Is your feature request related to a problem? Please describe. there is no way to change the root table or to use a different schema in the jsResources demos page

Describe the solution you'd like something like the tree used in the TapHandle page would do the job

lmichel commented 2 years ago

Connecting different TAP Nodes

There are 2 different ways to connect the tool with a TAP node:

From the URL
- https://server/joinwalker?url=https://simbad.tap: will create an TAP node in the data tree.
  - This Node is populated with the TAP service structure (schema, table)
  - The connection to a particular table is triggered by a user action on the data tree
- https://server/joinwalker?url=https://simbad.tap&table=public.basic: will create an TAP node in the data tree.
  - This Node is populated with the TAP service structure (schema, table)
  - The API gets connected with that table as root table.
    1. From the registry search bar
  - The user types keywords in the search bar
  - The list of matching services is displayed
  - The user select the service he/she wants to connect to.
  - This Node is populated with the TAP service structure (schema, table)
  - The connection to a particular table is triggered by a user action on the data tree

lmichel commented 2 years ago

Service Tree Node Behavior

Look and feel

The service tree node keep the same layout as for TapHandle
The capability LEDs will have to be updated
- Just on light: working or not
- Green at starting time
- Red in case of failure
A trash button will be added to each service root node to remove it from the tree
- Don't forget to disconnect first

Double Click on table

As the following actions are a bit heavy, it is better to trigger them with double-clicks: lower risk of mistakes.

Connect to the relevant service if different from the former one
- Update some global variable
- Update some relevant labels helping for the user experience
Connect the API to that table
- Update the map
- Update the query forms
- Run a query on the 10 first columns
Set a mark on the tree telling which tables is currently connected
- More visible for the root table
- Less visible for the others

Simple Click on a table

If the table is connected
- Show up the attribute-handlers as for TapHandle
Else
- Show up an alert

Double Click on service root node

Show up the Schema selector as for TAPHandle

lmichel commented 2 years ago

Once the direct access to a specific table is working (?url=https://simbad.tap&table=public.basic), the URL must be made available to allow users to bookmark any table.

proposal When clicking on thge [i] button on any table node of the data tree, the column selector show up.

The URL could by added to the table description block above the column table. The should use the same layout as for BookMark bottom on the application page head