Folders Overview Usage Scenarios

6 Managing Folders and WebDAV 6-1 6 Managing Folders and WebDAV This chapter provides information about administering Folders and WebDAV. It covers the following topics: ■ About Folders on page 6-1 ■ About WebDAV on page 6-8 ■ Administering Folders on page 6-11 ■ Administering WebDAV on page 6-20

6.1 About Folders

This section covers the following topics: ■ Folders Overview on page 6-1 ■ Usage Scenarios on page 6-2 ■ Folders Structure on page 6-3 ■ Naming Folders on page 6-4 ■ Folders Component Security on page 6-4 ■ Folder Metadata Inheritance on page 6-5 ■ Trash Bin on page 6-5 ■ Metadata Propagation on page 6-5 ■ Folder Content Item Revisions on page 6-6 ■ Default Metadata Values on page 6-6 ■ Local Folders on page 6-7 ■ Folder Archiving on page 6-8 ■ Folder Searching on page 6-8 ■ URL-Mapped Folders on page 6-8

6.1.1 Folders Overview

Folders is an optional component that is automatically installed with Content Server. When enabled, it provides a hierarchical folder interface to content in Content Server in the form of virtual folders also called hierarchical folders. Virtual folders enable you to create a multi-level folder structure. Figure 6–1 shows virtual folders as viewed from a content server web page. 6-2 Application Administrators Guide for Content Server Figure 6–1 Virtual Folders in Content Server Interface Virtual folders provide the following benefits: ■ Users can find content by drilling down through a familiar folder-type interface. Some of the fields in the My View search results are unavailable or not applicable when browsing through virtual folders. ■ Users can apply default metadata to content items by checking them in through a particular folder. ■ The system administrator can control the default metadata applied to content items by appropriately setting up folders. ■ In turn, the preset default metadata is applied to content items when users check them in through a particular folder set up by the system administrator.

6.1.2 Usage Scenarios

The main usage scenarios for the Folders functionality are as follows: ■ Browsing: Users should be able to browser through folders to find sub-folders, and content items. Users should have a simple mechanism to get additional information about a folder, and to traverse back up the tree structure. Users should be able to view folders containing hundreds of items and sub-folders. In a folder containing a large number of sub-folders, the user should be able to easily view and browse through content items in that folder. Similarly, in a folder containing a large number of content items, a user should be able to easily view and browse through the sub-folders. ■ Creating folders: In any given folder, users should be able to create new folders. Ideally, this process should involve only naming the folder. Additional information, such as folder metadata, default metadata, etc. should be accessible only if needed. ■ Assigning folder metadata: A user should be able to assign metadata to folders. This action should be possible at folder creation time. A user should be able to assign folder metadata on existing folders as well. The process and steps for both should be same. ■ Assigning default metadata for items: A user should be able to specify metadata that should be assigned to content created in or added to a folder. The user should be able to set this metadata at folder creation time or at a later time. In either case, the steps and process for setting metadata should be the same. ■ Assigning a Content Profile to a folder: A user should be able to assign a content profile to a folder. This may be done at folder creation time or later. This will Managing Folders and WebDAV 6-3 determine what metadata fields are available to be set as defaults for content items added to that folder. ■ Creating new content in a folder: A user should be able to browse into a folder and create check-in a new item into it. If the folder specifies default metadata for new content, or a content profile, then the content check-in form should accurately reflect that. ■ Adding existing content to a folder: A user should be able to browse into a folder and add a linkshortcut to an existing content item. That content item may exist in another folder, or may be in the content server and not in any folder. No metadata should be required at that time since the content item already exists in the server. If the destination folder contains items with the same name, the user should be asked to rename the new linkshortcut. ■ Moving an itemfolder from one folder to another: A user should be able to browse to a folder, select one or more sub-folders and content items, and move them into another folder. The user should not be able to move the folderitems into the child of a folder that is selected to be moved. No metadata should be required as these are existing itemsfolders. If the destination folder contains items with names the same as those that are being moved, the user should be asked if those items and folders should be overwritten or not. ■ Copying an itemfolder from one folder to another: A user should be able to browse to a folder, select one or more sub-folders and content items, and copy them to another folder. This action should create new copies of the selected folders and items i.e. not links into the destination folder. Metadata should be copied over and the user should not be prompted to ask for new metadata. If the destination folder contains folders and content items with names same as those being copied, the user should be asked if the destination files and folders should be overwritten or not. ■ Deleting an itemfolder: A user should be able to browse to a folder, select one or more sub-folders and content items, and delete them. The user should be prompted for confirmation of delete action. For items, with multiple revisions, user should be asked for all revisions should be deleted or only the latest revision. The user should have an option to apply their answer to all selected files. ■ Renaming an itemfolder: A user should be able to select a linkshortcut or sub-folder within a folder, and choose to rename it. The rename action should be allowed only on single items. If the new name is same as that of an existing item or folder, the user should be warned and required to change the name to be unique.

6.1.3 Folders Structure