{"action":"opened","issue":{"url":"https://api.github.com/repos/OpenBEL/openbel-server/issues/25","labels_url":"https://api.github.com/repos/OpenBEL/openbel-server/issues/25/labels{/name}","comments_url":"https://api.github.com/repos/OpenBEL/openbel-server/issues/25/comments","events_url":"https://api.github.com/repos/OpenBEL/openbel-server/issues/25/events","html_url":"https://github.com/OpenBEL/openbel-server/issues/25","id":56698722,"number":25,"title":"Define consistent access to resource collections","user":{"login":"abargnesi","id":149445,"avatar_url":"https://avatars.githubusercontent.com/u/149445?v=3","gravatar_id":"","url":"https://api.github.com/users/abargnesi","html_url":"https://github.com/abargnesi","followers_url":"https://api.github.com/users/abargnesi/followers","following_url":"https://api.github.com/users/abargnesi/following{/other_user}","gists_url":"https://api.github.com/users/abargnesi/gists{/gist_id}","starred_url":"https://api.github.com/users/abargnesi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abargnesi/subscriptions","organizations_url":"https://api.github.com/users/abargnesi/orgs","repos_url":"https://api.github.com/users/abargnesi/repos","events_url":"https://api.github.com/users/abargnesi/events{/privacy}","received_events_url":"https://api.github.com/users/abargnesi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-05T17:07:06Z","updated_at":"2015-02-05T17:07:06Z","closed_at":null,"body":"A discussion with @nbargnesi about accessing the evidence resource collection brought up the following design goals:\n\n- `GET /api/[collection]` streams the full resource collection\n- Paging a resource collection can initially be done through the *start* and *size* query parameters, for example `GET /api/[collection]?start=0&size=500`.\n- Filter a resource collection by one or more *filter* query parameters. The filter query parameter value is defined by a JSON document with *category*, *name*, and *value* fields. For example a text search could be encoded as `{ \"category\": \"text search\", \"name\": \"literal\", \"value\": \"AKT\" }`.\n- Delay server sorting capabilities due to the inability to stream for all use cases. This can be revisited in the future."}}