Working With Content Folders and Files 8-5
■
Properties: Displays a dialog that provides information about the selected folder
or project in the integration hierarchy. For more information, see Section 8.11.1,
Viewing and Modifying Properties of Folders or Files.
■
Advanced Properties Oracle Content DB servers only: Displays a window that
displays the properties about the selected folder in the integration hierarchy. For more information, see
Section 8.11.3, Viewing and Modifying Advanced Properties of Folders or Files.
■
Sharing Oracle Content DB servers only: Displays a window where you can set
the properties for sharing the selected folders; in other words, who has access to the folder and who can create content in it. For more information, see
Section 8.11.4, Viewing and Modifying Sharing Properties of Folders or Files.
8.2 About Content Files
Content files are files stored and managed on a content server. You work with content files in the integration hierarchy of a content server in much the same way as you do
with other, local files on your computer. You can copy and paste files, drag and drop files, right-click files to open context menus, and so on. In addition, you can perform a
number of content management tasks on the files on the server. Depending on the server type and setup, you may check files out of the server, check them in, make them
available for offline use, view content information, and so on.
The following sections provide more information about content files:
■
Section 8.2.1, Content File Versioning
■
Section 8.2.2, Content File Metadata
■
Section 8.2.3, Local Caching of Content Files
■
Section 8.2.4, Content Management Actions on Files
■
Section 8.2.5, Content File Status
■
Section 8.2.6, Content File Context Menus
8.2.1 Content File Versioning
Oracle Content Server Oracle Content Server can store multiple files of the same name as separate content
items. However, in the integration of Oracle Content Server with Windows Explorer and e-mail applications, file names in content folders need to be unique in the same
way that a folder in Windows cannot contain two files of the same name. Because of this requirement, when you add a file to a content folder that already contains a file of
the same name, it is automatically checked in as a new revision of the existing file on the server. For example, if process.doc is in a folder on the server and you add a second
process.doc file to that same folder, then the second file becomes a new revision of the first file even though they may be completely different documents. If process.doc is in
a folder and you add process2.doc or process.xls to that folder, then they remain separate content items because they have different file names.
The file name that is displayed in the Name column in Windows Explorer or your e-mail application and in the Name field of the Content Properties dialog is the same
as the original file name in the content server repository. When you rename content through the Windows Explorer integration, the original file name also changes to
reflect the new name.
8-6 Oracle Fusion Middleware Users Guide for Desktop Integration Suite
If Oracle Content Server is set up to automatically generate content IDs, then the content IDs follow the established numbering convention. If this option is not enabled,
checking in a new content item through Windows Explorer or an e-mail client generates a unique sequential content or message ID.
Oracle Content Database Servers When you add a file to a content folder on an Oracle Content Database server that
already contains a file of the same name, then it depends on the folder settings how this is handled. If automatic versioning is enabled for the folder, the file is checked in
as a new revision of the existing file on the server. If manual versioning is enabled, then the existing file is simply overwritten in other words, the content folder behaves
exactly like standard Windows folders on your local computer.
Other WebDAV Servers When you add a file to a content folder on a WebDAV server that already contains a
file of the same name, then it depends on the server settings how this is handled. Unless the WebDAV server has special versioning features, the existing file is simply
overwritten with the new file in other words, the content folder behaves exactly like standard Windows folders on your local computer.
8.2.2 Content File Metadata