The CoreMedia WebDAV support exports the content of the CoreMedia repository into the file system of your
computer; or, to be more exact, the part of the CoreMedia repository on which you have at least read rights. For
each folder of the CoreMedia repository you will find a folder in the file system with the same name. The export
of CoreMedia content items is a bit more complicated. In general, you define in webdav.properties
which
properties of which content types you want to export. You can do so in two different ways depending on the
number of properties you want to export:
export as files
export as folders
You can configure the mapping of content items to files or folders in the webdav.properties
file. See
Section 5.6, “Reference of webdav.properties” for a description of all properties.
Export as files
If you only want to export one property of a specific content type, you are better off exporting the items
as files. You will get one file in the file system for each corresponding content items, where the file has the same
name as the content item. The exported item is located in a directory structure that is equal to the CoreMedia
folder structure. By default, no file extensions are appended to the exported file. You can configure the WebDAV
Server to append a file type extension to all content items that are exported as file. The extension is
automatically derived from the MIME type of the exported field and must be configured in the file
mime.properties
. If no extension can be derived, the extension .bin
is used.
If you have more than one field in your content type, which you want to edit via WebDAV, you have to export the content item as folders.
Export as folders
If you want to export more than one property of a content item, you can export it as folders. In this case, you will
get for each exported content a folder with the name of the content item. This folder contains one file for every
exported property, where the file has the localized name of the property with a file extension that is
automatically derived from the MIME type of the exported field and must be configured in the file
mime.properties
.
This export is more flexible than the export as files but it might be more confusing for users because you have WebDAV folders for CoreMedia folders as well as for content items.
Creating content items
When you create a new file with your WebDAV client, the WebDAV server has to determine the content type of the
content it should create in the CoreMedia repository. This is done via a mapping between a part of the name of
the file or folder (such as the extension) and the content type to create (see
Section 5.6, “Reference of webdav.properties”). So, if you have registered ".doc" as an extension for CoreMedia items
of type CMWord
and you create a new Word document "NewText.doc" in a WebDAV folder, then the WebDAV server
will create a content item of type CMWord
named "NewText" in the CoreMedia repository. You can use WebDAV to
rename the content item after its creation, which of course does not change the type of an already created item.
The configured extension mapping is only used for the creation of content items.
When you use the folder mapping for content items and want to create a new content that uses folder mapping, you have to create a new Folder with a name that ends with the registered text. The task is a bit more complicated because Windows creates a "New Folder" first before you can specify the name of the folder. This leads to the creation of a CoreMedia folder with the same name. If you immediately rename the still empty folder to a name with an extension that is mapped to a content type, then the empty CoreMedia folder is deleted and a document of the wanted type is created instead. The WebDAV server will automatically create empty files for all exported properties of the new document.
You can also configure the catch-all extension *
for one content type to create content items of that
type for all names which do not match another configured extension. Note, that if you configure such an
extension for a content type which uses the folder mapping, you will not be able to create CoreMedia folders
with WebDAV.