Home · All Classes · Annotated · Functions

Document System - Content Metadata

Overview
Categories

Overview

In the case of a data stream or a temporary file there is no concept of a meaningful filename visible outside the DocAPI. Generally, client programs only need access to the content, so there will be no request for the filename string. Even though the filename will not be available, a range of important metadata about the Content will be available via the API - this is known as Content metadata.

Content metadata contains important information about a Content item. For example, it:

provides an API for operations on documents
abstracts a list of Content items used for operations
the list of Content items provides a window to the database of all Content objects
provides access to a Qt 4 MVC model view of the list, updated live.

The Document System maintains the following meta-data for the Content Items:

Field	Description/Example
`uiName`	User-visible content name: for example, Us on the beach
`mimeType`	RFC2045 content type: for example, `image/jpeg`
`size`	number of bytes of plain content : mainly for encrypted and/or compressed files, and streams
`drmStatus`	one of: `plain` : files outside any 3rd party rights, for example a users own photos or media files `controlled` : files subject to current rights and able to be rendered within the terms of those rights `unrenderable` : subject to rights, but according to those rights are not able to be rendered, for example, expired interval, file format corrupt or unreadable
`docStatus`	one of: `doc` : user documents, for example, a photo, word document where it is meaningful for the user to see the content as a distinct item separate from the application which created it `dat` : application data, for example a sticky notes files or cached data
`icon`	user-visible `QIcon` data: a Qtopia icon suited to the mime-type, or a downloaded icon
`thumbnail`	cached thumbnail data: allows previewing as appropriate, for example, 32x32 low-bit plane representation of the `jpeg`; may be null
`owner`	program identity as per Safe Execution Environment: allows uninstalls and updates to manage files related to a program
categories	link to or export of category sub-system information: for example in export example Camera:Holiday/Fiji:Req by Doug, the auto-generated category for `Content` generated by the `Camera` application has user custom hierarchical category Fiji within Holiday applied; and has user custom category Req by Doug for files which Doug has requested.

Document System - Content Metadata

Overview

Categories