I am testing from the UI from a fil query or file entity page:
To test this:
[ ] querying the api as a full member with no program access logged in, can see
-- a file from a FULL release status a single file query or page
-- a file from a ASSOCIATE release status a single file query or page
-- a file from a PUBLIC release status a single file query or page
[ ] querying the api as a associate program member logged in can see:
-- a file from OWN PROGRAM that is actually just from my program that a full member cant see
-- a file from a ASSOCIATE release status a single file query or page
-- a file from a PUBLIC release status a single file query or page
[ ] querying the api as a public member logged in, see only publicly released data
-- a file from a ASSOCIATE release status a single file query or page results in a 403
-- a file from a PUBLIC release status a single file query or page
Similar to https://github.com/icgc-argo/platform-api/issues/364, we need to make sure that individual filters are working correctly (for example from the file-entity page)
Expected Behaviour
I am testing from the UI from a
fil
query orfile entity page
: To test this:[ ] querying the api as a full member with no program access logged in, can see -- a file from a
FULL
release status a single file query or page -- a file from aASSOCIATE
release status a single file query or page -- a file from aPUBLIC
release status a single file query or page[ ] querying the api as a associate program member logged in can see: -- a file from
OWN PROGRAM
that is actually just from my program that a full member cant see -- a file from aASSOCIATE
release status a single file query or page -- a file from aPUBLIC
release status a single file query or page[ ] querying the api as a public member logged in, see
only publicly released data
-- a file from aASSOCIATE
release status a single file query or page results in a 403 -- a file from aPUBLIC
release status a single file query or page