Ticket #98 (new Defect)

Opened 9 years ago

Last modified 5 years ago

Aggregated/truncated display of large result sets

Reported by: jri Owned by:
Priority: Major Milestone:
Component: DeepaMehta Standard Distribution Version: 4.0.3
Keywords: Cc:
Complexity: 3 Area: GUI
Module: deepamehta-webclient

Description

The first step could be to truncate result lists (in the content panel) to lets say 150 entries.

The old DM2 had 2 threshold levels:
1) on the canvas never more than 7 topics are revealed at once.
2) the content panel never lists more than 150 topics.
From my experience the first one has not proven useful. Currently in DM4 its up to the user to reveal topics one by one. So she must not hide all the auto-revealed topics she's not intereted in.

Change History

comment:1 Changed 9 years ago by JuergeN

I would suggest the following for the content panel:

  1. Sort associations by type and give it headlines
  2. display 7 or less straight away. (I thought that was the result of scientific research about how our brain works?)
  3. if more then seven, show a list box (in alphanumeric order) and with a dynamic relaod of every so and so many items.

comment:2 Changed 9 years ago by Jörg Richter

Core: limit search results (#98).

Extend Core API by "maxResultSize" argument.
Not yet functional.

See ticket 98.

comment:3 Changed 9 years ago by Jörg Richter

Core: limit search results (#98).

Now functional.
Search result limit is set to 100 items.

See ticket 98.

comment:4 Changed 9 years ago by Jörg Richter

Core: limit search results (#98).

Extend Core API by "maxResultSize" argument.
Not yet functional.

See ticket 98.

comment:5 Changed 9 years ago by Jörg Richter

Core: limit search results (#98).

Now functional.
Search result limit is set to 100 items.

See ticket 98.

comment:6 Changed 9 years ago by Jörg Richter

comment:7 Changed 9 years ago by Malte

  • Milestone Release 4.1 deleted

comment:8 Changed 6 years ago by Malte

Though the maxResultSize argument is still present in the requests, the argument does not seem to have an effect on queries (e.g. "By Type"-Searches). Furthermore, the issue with this latest approach was, what if there are more than 100 / 150 entries, how can the user browse those (e.g. via a "By Type"-Search)?

comment:9 Changed 5 years ago by jri

Since at least DM 4.3 (possibly earlier) the maxResultSize paramter is not supported anymore by the Core API. It will possibly be removed in the next DM release.

ticket:741#comment:2
ticket:741#comment:4

Note: See TracTickets for help on using tickets.