The Content UI presents a dynamic folder hierarchy for browsing and uploading content within a bucket. This hierarchy is based on the prefixes stored on the object names (such as folder/subfolder/object.xml). This folder simulation is similar to the listing behavior of other visual clients used with Swarm, such as SwarmFS and S3 Browser. (v7.0)
These folders offer three key benefits:
Prefix Filtering: By parsing object prefixes into hierarchical folders in real time, the Content UI provides users a fast and intuitive way to view and manage content in a bucket, automatically.
Empty Folders: The Content UI allows creation and persistence of new, empty folders ready to receive files. This allows planning and setting up organizing structures ahead of time, to guide content uploaders to use the organization. By having users upload directly to folders, enforce a content architecture and avoid the risk they perform bulk uploads using a malformed prefix.
Recursive Deletes: Even more powerfully, the Content UI allows deleting virtual folders, which recursively deletes objects and subfolders they contain. Users are warned about the impact and are prompted to verify all folder deletes.
The Content UI automatically parses object names into a folder hierarchy when opening a bucket to view the contents.
This is the automatic view of the bucket contents; one folder level at a time is visible. Although S3 includes the folder within the listing, the Content UI does not, so as to match the behavior of file systems.
To walk down the hierarchy of folder levels, click on a folder name in the object listing, which opens that folder level.
To walk up the hierarchy of folder levels, click on a folder name in the breadcrumb trail, which opens that folder level.
To see the full name of a given object, click the name to open the Detail pane:
The ability exists to see the flattened view of bucket contents, without virtual folders.
To see the flattened view, start a Collection (which is a saved Search): 
The Content UI displays virtual folders in two ways - one temporary and one permanent.
Create temporary folders when content is uploaded with a File Name Prefix.
ImportantWith prefixes, naming is important: do not begin with a slash, but always end with a slash: |
The uploaded content appears in the virtual folder because it is synthesized dynamically; the folder no longer appears in the bucket listing if deleting all uploaded contents (including historical versions).
To create a persistent folder even when empty, open a bucket and select +Add > Add Folder.
This action creates a durable placeholder folder preserved in the bucket until it is explicitly deleted.
These folders are virtual and are not full contexts (like domains and buckets) carrying customizable metadata, permissions, and content protection policies. These folders inherit all attributes from the bucket.
The Content UI allows deleting permanent virtual folders in two ways - one recursively and one non-recursively:
The Actions menu provides the option to delete the folder while in the folder view. This delete is a recursive removal of all content, both objects and subfolders.
The Objects count shows how many content-bearing objects are deleted along with the folder.
The recursive delete prompts for verification of deletion of all folder contents.
The ability to delete a persisted folder without deleting or renaming any content for a collection is present in the flattened view.
Deleting the folder from the flattened view removes the folder and preserves the objects it contained, as well as the prefix in the name:
TipThe folder is temporary and appears dynamically because of prefixes on object names if the folder is not visible on a separate line in this view - there is nothing persisted in the cluster to be deleted. |