My Space List: API adjustments needed for sorting/filtering and additional data needed

[dgutride]

This is an issue to roll up all of the others that have been entered around this and provide a higher level overview of what is needed. Only the my spaces page is impacted - all spaces is still under discussion as to whether or not it will be in the product long term.

Design: https://redhat.invisionapp.com/share/DQDSL22JA#/screens/261389228

API needs:
Filtering/searching/sorting
The page needs to be able to support sorting and filtering either client or server side. Although paging is supported now, we can't sort or filter this way because only the paged entries would be impacted instead of the entire list. This is a must have for GA on the columns we agree to include (some are still at risk like activity and private).

Sorting columns: Activity, Name
Filtering: Activity, Collaborator, Name, Owner, Private

Existing issues:

• API: /search/spaces to support sort and filter: API: /search/spaces to support sort and filter #1629
• API: /namedspaces/{userName} to support all spaces: (closed) API: /namedspaces/{userName} to support all spaces #1628

Additional data needed:
The space list includes additional data that is not available today:

1. User relationship to the space - owner, collaborator, none - must have for GA so user can take appropriate actions if any (leave space for collaborator, delete space for owner)
2. Activity - algorithm still to be determined, need to discuss if this is priority
3. Private - is this required for GA?

Existing issues:

• Need API to show where users is a collaborator: Need API to know which spaces a user is a collaborator #1630
• Need API to show activity: Need API to show activity #1631
• Need API to show private spaces: Need API to show private spaces #1632
• API: /namedspaces/{userName} to support sort and filter: API: /namedspaces/{userName} to support sort and filter #1627

@joshuawilson @catrobson @dlabrecq @aslakknutsen

[joshuawilson]

After talking with @qodfathr he confirmed that the things we already support can be implemented. Whereas things like private spaces don't exist and we will not be adding it.

[catrobson]

@joshuawilson can you expand on this a little bit for what exactly you expect this means?

• Does this mean that we will not show a list of both owner and collaborator spaces? This felt like MVP need to me.
• Does this mean we will not support any sort of filtering on the page?
• Does this mean we will not support any sort of sorting on the page?

Activity and Private spaces not being included for GA is reasonable to me.

[qodfathr]

If we have an API which can provide the necessary data, we will use it.
If we don't have an API, the API should be considered to be a stretch goal for H.
So, "will we show a list of both owner and collaborator" will have the same answer as "do we have an API which provides list of Spaces and, either in the API itself or easily on the front end, that list can be classified between owner and collaborator."

Filtering strikes me as a front-end capability (assuming the returned data is of a reasonable size), so the hope is that the Patternfly gadgets used essentially provide this capability for free.

Note that "data is of a reasonable size" implies that the API is only returning Spaces directly associated to the user (either as owner or collaborator) and does not include every Space in the system, across all users. That would require filtering to be done in the backend. If that capability is not currently in the backend, it's a stretch goal to add it.

The same approach should apply to sorting: reasonable sized data returned, front-end operation, already a part of the Patternfly.

Does that help? We are definitely in "make hard decisions and cut stuff" mode right now.