The behaviour of collection queries via the webservice is confusion and broken.
At present, any request ending /ws/2/collection returns a collection-list element containing the collections for the currently authenticated user, e.g.,
This is confusing, and entirely inconsistent with the behaviour for other entities.
To regain consistency with the behaviour for other entities, it should firstly be possible to lookup a single collection via its id. Thus a request for,
should return something like:
and not simply a complete collection-list as above.
It should also be possible to issue a browse request that does return a collection-list (with data as above). For consistency with other browse requests, I would recommend something like:
Any request for a editor other than the current authenticated username would return an http 401 status. It might also be useful to have a 'magic' user value that would indicate that the currently authenticated user should be used.
Finally, there's currently no way to get the content of the release-list for a collection. Adding inc=releases could be used to cause this information to be returned. Alternatively, and probably preferably as release-list is likely to be large (and thus it would probably be desirable to be able to page through the releases), it should be possible to use a browse request, e.g.: