Link for Code changes:
https://bitbucket.org/nfreese/django-cyversedev/pull-requests/48/change-the-hardcoded-string-to-include-the/diff

Moving to Needs Testing.

There is currently no way to share a folder in the BioViz-CyVerse UI as we need to implement the right-click/3-dot functionality for folders, so this issue is currently blocked for testing by IGBF-1960.

Email from Paul Sarando at CyVerse:

"I think this is a known issue with our data service:

When sharing a file with a user, our service also shares the enclosing
parent folders of that file, in order for that user to be able to
navigate down to the file within the DE's data window (those parent
folders have to be readable to that user in order to display in the
data window for navigation).

I think that folder was automatically shared with anonymous after
sharing its file, so our service decided no action needed to be taken
when attempting to directly share that folder with anonymous.

It seems unsharing first is a good workaround for now. Sorry for the
inconvenience.

Regards,
Paul"

We will need to make two API calls to share a folder with a user or to make the folder public (the behavior is the same for both):
First API call: unshare the folder
Second API call: share the folder

Link for (API) code Changes.
https://bitbucket.org/nfreese/django-cyversedev/pull-requests/57/major-fixes/diff

This issue is currently blocked for testing by IGBF-1960.

I'm moving sharing of folders/files to the backlog. I changed the title of this issue to reflect that the folder will not be shared with user but made public (sharing with anonymous).

Now able to make a folder recursively public.

Closing issue.

Note: Due to how the Terrain API behaves in regard to "public" (shared with anonymous) data, if a single file within a folder is listed as public, then the enclosing folder is also considered public. This is somewhat confusing, as a folder can be listed as public, but not all files contained are public. Currently, user would see that a folder is public, but only a single file contained could be public. To make the folder "completely" public, they would need to remove the public link to the folder, and then make a public link for the folder. Due to Terrain I do not think there is any way to get around this, currently.