Understanding file timestamps
The File Fabric does not store any files and it works with remote copies of data that it has indexed. It uses UTC as an independent time format to display information about files. This means that times for files are shown as UTC times and UTC is used to enable the File Fabric to understand whether a file needs to be updated or versioned.
1 File modified times
Hovering over the time field or looking at the file info pane in the File Fabric Web Browser shows 4 different times:
- SME Created (if SaaS) Storage Created (if on-premises) - This is the time the file was added to the File Fabric in UTC format
- SME Modified (if SaaS) Storage Modified (if on-premises) - The last modified time for the file in UTC format
- Local Desktop Time- The local modified time for the file, converted to UTC format (for the browser this will be based on the browser locale settings)
- Remote Cloud Time - The modified timestamp that was received from a files metadata, converted to UTC, from a mapped storage provider.
2 Uploading files from the web
If files are uploaded from the web File Manager then original modified timestamps are preserved except for the Safari browser which will use the timestamp of when the files was uploaded for the modified time as it is not possible from the Safari to obtain the modified time on upload.
3 Uploading files from the desktop
Files that are uploaded from a Mac, Windows or Linux Drive client, or via sync should have the timestamps fully preserved, but converted to UTC (with local time also being shown in browser and on desktop).
4 Uploading files over protocol adaptors
If files are uploaded over a SME CloudDav or CloudFTP protocol adaptor then timestamp preservation depends on the client tool used and whether it issues the command to change the file timestamp.