"Owned Groups" checkbox

The current "My groups" checkbox uses the API's user_id filter, listing all groups the user is the owner of or a member (in the future, the owner is supposed to be in the members list as well). There is no API filter for being just the owner of a group at the moment.

To add a checkbox that lists the groups owned by the user, we need to either

1. add the filter to the API (same for member?), increasing the number of query arguments, including all future user-roles
   1. {'member': 'USERID1'}, {'owner': 'USERID1'}, ({'manager': 'USERID1'}, etc.), {'user_id': 'USERID1'}
   2. {'member': [{'user_id': 'USERID1', 'role': 'owner'}, {'user_id': 'USERID2', 'role': 'reviewer'}]} (connector AND or OR?)
   3. {user_id: 'USERID1', role: 'owner'} (simpler but less specific, role doesn't make sense on its own)
2. keep querying for user_id but filter in the GUI, keeping the filtering work for the API higher than necessary.

@mscheidg Not a high priority but I wanted to write it down before the vacation. What is the philosophy for the new GUI, which end should filter what?

I tend towards 1.2, which has the downside that the GET /groups endpoint could not mirror this anymore, so either we drop some feature support there or have to use something like POST /groups/??? for querying instead. (POST /groups is currently used for creating groups.)

I think this should always be done in the backend. The whole routing+filter+table pattern should exactly work the same for uploads and groups (and other things), which requires that its always [search parameters -> route request -> backend -> table]. Don't introduce a filter on the client. This makes pagination, etc. a nightmare. The same for the backend, the backend should always offload all filters to the database (i.e. mongodb).

changed the description

changed the description

closed

reopened

mentioned in issue nomad-FAIR#2238