When having a lost of assets (> 100k) the main listing produces a query that can not be tuned from the database,
in PostgreSQL a simplified version is:
The 3 clauses are not selective at all and the best plan is a seq scan on all table which give a very bad response time, also sorting title requires too much memory and may use a temporary file.
A GIN index on ancestors.ancestors does not help because we are looking for the root of all assets.
A BTREE index on dublincore.title is not used preventing cursor or limit usage.
Thomas mentioned that we may try to run the query only after something is selected in the filter