About uploading folders, About media files with no file extension, Response pane and window – Apple Final Cut Server User Manual
Page 196: P. 196)
196
About Uploading Folders
When you manually upload a folder containing media files to the Final Cut Server
catalog, you are given two options for how Final Cut Server should treat the folder:
 Upload the folder as a bundle. This means the folder and all of its contents are treated
as a single asset, and you do not have access to the individual assets within the folder.
 Upload the folder’s contents as individual assets. This means that each of the media
files within the folder are uploaded as individual assets, and the fact that they were
all in a folder when uploaded is not tracked.
If you choose to upload the folder and its contents as a bundle onto a device that has
an automation, such as a scan response, configured to watch for new media files, the
folder’s media files can end up being added to the Final Cut Server catalog as
individual assets.
This means that you could potentially create a situation, either intentionally or
unintentionally, where you can upload a folder as a bundle but still be able to work
with the bundle’s individual assets. If you do not want the individual media files to be
added to the catalog, be sure to upload the bundle to a device that is not automatically
being scanned for new assets.
About Media Files with No File Extension
In some cases, Final Cut Server automations can correctly recognize, upload, and
process media files that do not have a file extension. To ensure that all files upload and
are processed correctly, be sure all media files have an extension. This is especially true
if the files are being uploaded to an FTP device.
Files without file extensions that are not correctly recognized will upload and be added
to the Final Cut Server catalog as assets, but they will not have thumbnail or proxy files
generated for them.
Response Pane and Window
The Response pane contains the settings for creating a wide variety of preconfigured
actions. These responses are what the watchers, subscriptions, and schedules use when
they detect that an action needs to be performed. Responses are configured separately
from watchers, subscriptions, and schedules because the same response may be
required in several situations.