Many metadata fields exist in Assets Server and many of them store very similar data. This can make it confusing sometimes to know exactly which field to use when searching for files.
In this article we highlight some of these metadata fields.
Fields that store date and time information
The following are examples of metadata fields that store date or date/time information.
| Name | Description |
|---|---|
|
Checked In Internal name: assetFileModified |
Date and time when the file was checked-in or when a file in a Collection was modified. |
|
Creation date Internal name: created |
The embedded date and time when the file was created (not available for all assets). Example: EXIF DateTimeOriginal: the date and time when a photo was taken as recorded by the camera with which the photo was taken. |
|
Enterprise created Internal name: sceCreated |
The date when the asset was created in Studio Server. |
|
Enterprise modified Internal name: sceModified |
The date when the asset was modified in Studio Server. |
|
File Creation Date Internal name: fileCreated |
Date and time when the asset was created on the file system. It is only read when manually importing the asset and cannot be read through Java or the exiftool (perl). When empty, the value of File Modified Date (fileModified) is used. |
|
File Modified Date Internal name: fileModified |
Date and time when the asset was modified on the file system. Note: The usefulness of this field is questionable. For example if the asset was imported through the Web Service this will be the lastModified date of the temp file created for the Web Service attachment on the server, which is not a realistic time stamp. |
|
Imported in Assets Internal name: assetCreated |
Date and time when the asset was created in Assets Server by importing it. |
|
IPTC creation date Internal name: iptcCreated |
The embedded creation date read from IPTC or XMP-photoshop (not available for all assets). |
|
Modified date Internal name: modified |
The embedded date when the asset was modified (not available for all assets). |
|
Modified in Assets Internal name: assetModified |
Date and time when the file was modified in some way in Assets Server. This includes Collections and files in Collections. |
|
XMP creation date Internal name: xmpCreated |
The embedded creation date read from XMP (not available in all assets). |
Fields that store file location information
Various metadata fields store information about the location where an asset is stored in the folder structure of Assets Server. Knowing how to use these fields is useful when searching, filtering or sorting assets.
This can best be shown by using an example. Consider the following path to an asset:
/Main Zone/sub folder A/sub folder B/someasset.txt
| Name | Description | Result |
|---|---|---|
|
Path Internal name: assetPath |
Stores the full path to the asset: folders and file name. | /Main Zone/sub folder A/sub folder B/someasset.txt |
|
File name Internal name: filename |
Stores the full file name including the extension. | someasset.txt |
|
Name Internal name: name |
The name of the asset. For virtual assets such as a Collection, the extension is left out |
someasset.txt |
|
Directory Internal name: folderPath |
Stores the folder part of the Path (assetPath) field, excluding the trailing slash and the file name. | /Main Zone/sub folder A/sub folder B |
|
Ancestor paths Internal name: ancestorPaths |
This special field stores all 'ancestor' folder paths of the full path. | /Main Zone/sub folder A/sub folder B /Main Zone/sub folder A /Main Zone |
|
Tokenized path Internal name: assetPathTokenized |
Stores the tokenized version of the full asset path. | Main Zone sub folder A B someasset txt |
|
Some useful search examples:
ancestorPaths:"/Main Zone/sub folder A"
folderPath:"/Main Zone/sub folder A" |
Fields that store file type information
| Name | Description |
|---|---|
|
Type Internal name: assetType |
The extension of the file (.txt, .jpeg, .pdf and so on). When the file extension is not mapped as an asset type, 'unknown' is used. |
|
Extension Internal name: extension |
The actual extension of the file (txt, jpeg, pdf and so on) |
|
Kind Internal name: assetDomain |
The 'kind' of file. Possible values:
|
|
File type Internal name: fileType |
The file type as reported by the exiftool (JPEG, TXT, PDF and so on). |
|
MIME type Internal name: mimeType |
The MIME type: a method of classifying file types. It consists of a type and a subtype, divided by a slash (image/jpeg, application/pdf, video/quicktime, application/msword and so on). |
Comments
0 comments
Please sign in to leave a comment.