Opened 18 years ago

Closed 12 years ago

Last modified 12 years ago

#160 closed enhancement (wontfix)

List pages should be able to list subset of items

Reported by: Nicklas Nordborg Owned by: Nicklas Nordborg
Priority: major Milestone:
Component: web Version:
Keywords: Cc:


For example, the page that lists users should be able to list users that are members of a group or role. The role list page should be able to list the roles of a user. The extracts list page should be able to list extracts from a specific sample, and so on...

For almost every list page, it is possible to think of some other item that can be seen as the "parent" item.

Change History (7)

comment:1 by Johan Enell, 18 years ago

Owner: changed from Johan Enell to Nicklas Nordborg

comment:2 by Jari Häkkinen, 18 years ago

Milestone: BASE 2.0+

comment:3 by Nicklas Nordborg, 14 years ago

Status: newassigned

I'll have a go at this. My idea is that tables should use Ajax to update themselves. This means that we can have multiple tables on a single page and they all work independently of each other. It requires a lot of code re-structuring in places were we need this. I'll use the Users list page as a test-bed when implementing a framework. Users also appear as members on the group view page. Don't know if this will go into BASE 2.16 or later. I guess it depends on how much work it is.

comment:4 by Nicklas Nordborg, 14 years ago

Milestone: BASE 2.x+BASE 3.0
Status: assignednew

It was fairly easy to get the basic functionality, but there are some issues, mostly with on-load scripts that doesn't not run when the table is loaded with Ajax. This causes some features to fail:

  • The "Columns" dialog doesn't work.
  • The function that hides too long string (#1186) doesn't work.
  • Multi-option filter (#1011) doesn't work.
  • Filter on enumeration-type annotations (#965) doesn't work.

My feeling is that fixing this would intrude too much on the current functionality and we would risk breaking things that doesn't use the Ajax loading. It would be better to postpone this to BASE 3 where we can re-design the entire web client.

comment:5 by Nicklas Nordborg, 13 years ago

Milestone: BASE Future ReleaseBASE 3.1
Priority: minormajor

comment:6 by Nicklas Nordborg, 12 years ago

Resolution: wontfix
Status: newclosed

I have decided to not fix this. Looking at the lists that are mentioned in the description of this ticket they are no longer simple lists of a single item type. For example, on the sample view page, the child list contains mixed samples+extracts. The role/user/group pages have similar type of mixed lists. In other cases, for example the experiment page, the lists (experimental factors and raw bioassays) include additional columns that are normally not available in the main list. The 'Experimental factors' list show the 'Used values' from the raw bioassays. The 'Raw bioassays' list show the experimental factor values for each raw bioassay.

So, if we wan't filtering, sorting, paging, etc. in those lists, it is probably easier and quicker to implement that directly in the desired lists instead of trying a generic reusable approach.

comment:7 by Nicklas Nordborg, 12 years ago

Milestone: BASE 3.1
Note: See TracTickets for help on using tickets.