This is kind of an old issue but let's do it this time.
The difficulty is that getting all the data about the outline at once is pretty slow in terms of query and also very demanding in terms of UI. I think this is because when we fetch some nodes we fetch all the details (topics, authors, with their respective labels, but also location, notes, colophons, etc.) for all the nodes.
Instead let's do something along the lines of what's on the legacy website:
first get the structure of the outline by getting the nodes with their associated labels and part types (that's not too much data for the query or the UI)
when the user clicks opens a node to see the details, then we trigger a query that gets the information to display
@eroux If I understood correctly, we would shift waiting time from page load to the click of expand all. This is a very good idea. Just remember the spinner.
This is kind of an old issue but let's do it this time.
The difficulty is that getting all the data about the outline at once is pretty slow in terms of query and also very demanding in terms of UI. I think this is because when we fetch some nodes we fetch all the details (topics, authors, with their respective labels, but also location, notes, colophons, etc.) for all the nodes.
Instead let's do something along the lines of what's on the legacy website:
https://legacy.tbrc.org/#!rid=W22084
where we could:
what do you think @roopeux @berger-n ?