We use a table as the default presentation on most search pages on hosted portals (occurrence, publishers, datasets, institutions, collections, literature). We need that on the new gbif.org as well
I'm open to changes and most of below features are obvious, but here is a list of what the table currently supports:
site owners can provide a config that defines what columns to show as default, which ordering
site users can customise what columns to show (of those made available by the site owner) - see occurrence search
Horizontal overflow is scrollable
The first columns can be locked in place to ease overview when scroll horizontally, on mobile that disappears due to space constraints
Column headers can be used to open the filters for that column
Table cell values can be used to add filters (can be disabled in config as some site owners do not like it)
Clicking a row can open the record in either a drawer or go to a new page
Pagination
fixed header on vertical scroll to make it easier to know what columns you are looking at
A thing I do not particular like is the fixed height. It is awkward to use in many cases in turns out. I like the idea when I implemented it, but in reality it is a bit awkward to work with. If we can find a different way to have a fixed header, and ideally pagination footer, then that would be great.
We use a table as the default presentation on most search pages on hosted portals (occurrence, publishers, datasets, institutions, collections, literature). We need that on the new gbif.org as well
Examples usages:
I'm open to changes and most of below features are obvious, but here is a list of what the table currently supports:
A thing I do not particular like is the fixed height. It is awkward to use in many cases in turns out. I like the idea when I implemented it, but in reality it is a bit awkward to work with. If we can find a different way to have a fixed header, and ideally pagination footer, then that would be great.