I'm not sure if this will be possible without changes to the Agave API, or implementing our own "shared" system and maintaining a database around it.
An API call to: https://agave.iplantc.org/files/v2/listings/shared does not return the shared folder, but instead returns the community folder. This may be useful, except that all folders/files within this directory are labelled as READ (many are actually private), which would make it impossible for us to parse the folders and only show what the user has access to.
The "shared" folder in the Discovery Environment seems to be created by putting all of the usernames that have shared data with the user in one folder. However, using a listings API call (https://agave.iplantc.org/files/v2/listings) returns thousands of usernames, all of which are labelled as READ (which is again inaccurate). Making an API call directly against the user (suppose nfreese shared a file with nowlanf - https://agave.iplantc.org/files/v2/listings/nfreese) will display the shared data/folder. Oddly, all files/folders show up, even those that are private, and again are all labelled with READ access.
I can't see any easy way to use the current API calls to create a shared folder for the user. We could allow users to share files/folders, but then we would need to have a database containing what has/has not been shared (this also runs into the similar issue we have with public/private permission disparities between Agave and the Discovery Environment).
Task
Major
I'm not sure if this will be possible without changes to the Agave API, or implementing our own "shared" system and maintaining a database around it.
An API call to: https://agave.iplantc.org/files/v2/listings/shared does not return the shared folder, but instead returns the community folder. This may be useful, except that all folders/files within this directory are labelled as READ (many are actually private), which would make it impossible for us to parse the folders and only show what the user has access to.
The "shared" folder in the Discovery Environment seems to be created by putting all of the usernames that have shared data with the user in one folder. However, using a listings API call (https://agave.iplantc.org/files/v2/listings) returns thousands of usernames, all of which are labelled as READ (which is again inaccurate). Making an API call directly against the user (suppose nfreese shared a file with nowlanf - https://agave.iplantc.org/files/v2/listings/nfreese) will display the shared data/folder. Oddly, all files/folders show up, even those that are private, and again are all labelled with READ access.
I can't see any easy way to use the current API calls to create a shared folder for the user. We could allow users to share files/folders, but then we would need to have a database containing what has/has not been shared (this also runs into the similar issue we have with public/private permission disparities between Agave and the Discovery Environment).