Situation: We use the paged-directory endpoint to list files and folders. While it does return the permissions (own/write/read) it does not return a list of all user-permissions, including those for the anonymous user. If the anonymous user has (at a minimum) read access (in general we have been referring to this as being "public"), then the file can be viewed in IGB through dav-anon. Because we don't know if a file is "public" from the paged-directory endpoint, we cannot easily change the status of the View in IGB buttons to visually indicate to the user whether a file is public and therefore viewable in IGB (we would need to make an API call to the user-permissions endpoint for every single file/folder, which would be very slow).

There is a pseudo-workaround that is enabled by using the search endpoint. Searching for a file or folder will return a list of user-permissions, including those for anonymous. However, the search is recursive, so it is not possible to list just the contents at a single directory level, it will also list all files/folders within any folders. So if the search is conducted on the Community data folder, several million results are returned. There also seems to be a lag in time for when the search results are updated. For example, if I change a files user permission, that change will be instantly reflected in the user-permissions endpoint, but not in the search endpoint (it is unclear how long it takes).

An additional note: The user-permissions endpoint cannot be used on shared or community data as it requires own permissions, and will throw an error if a non-owner hits the endpoint. We had discussed using the search endpoint to circumvent this, but the lag in time for user-permissions may be an issue.

Task: Through conversations with the CyVerse team, they have tentatively agreed to adding user-permissions to the paged-directory endpoint, or to add an isAnonymous/isPublic flag. We do not have a timeline as to when these changes will be made.

Once the changes have been made by CyVerse, test the various endpoints to make sure they are working correctly, add to the comments which approach CyVerse used to implement the changes, update the Terrain API documentation in the Google Drive, and then close this issue.