Assigned to me to investigate what backend sorting changes will be necessary.

Notes on changes that will be necessary for this:

Archived Items

In table, not sortable

• Name (with firstSeedURL + x URLs fallback)
• Pages crawled

Sortable, not in table

• Last Analysis Run

Workflows

In table, not sortable

• Name (with firstSeedURL + x URLs fallback)
• Schedule (also condensed with Name)
• Total size

Sortable, not in table

• Crawl Start URL
• Date created

Collections

In table, not sortable

• Number of archived items
• Total pages

Archived Items tab on the Collections page

Notes

• Same thing as Archived Items table but doesn't have sorting in-place currently

Pages list in the Quality Assurance tab of the Archived Item Detail page

Sortable, not in table

• Recently Approved? (maybe just needs rename, or make sorting by date more apparent? - maybe should just be Approval)
• Most Comments (just Comments in table, existing backend filter is just for has comments or not, not sortable by number of comments)

Notes

• Title and URL collapsed into one column in current view

Crawls tab on the Crawl Workflow Detail page

In table, not sortable

• Duration
• Pages crawled
• createdBy

Org Settings members list

Notes

• Not currently using a backend endpoint, just getting this as part of org response
• Likely need a new /orgs/oid/users endpoint to support sorting

Btrix queue exclusion table

Notes

• Does this need to be sortable? I think these might be fetched from redis currently rather than stored in database

Generally we don't seem to be using many pages of exclusions so I'm not too worried about that table not being sortable. If it's easy to do, great to have for consistency, otherwise seems like low priority to me.

Pull out high priority items into sub-issues and then unschedule this main issue.