## mto:Transfer mto:Transfer |

## Description

Represent a single transfer task, which could have multiple transfer elements

This class emits notifications about changes, and can be tracked through the `GraphUpdated` DBus signal.

## Class hierarchy

        rdfs:Resource
        ╰── nie:InformationElement
            ╰── mto:Transfer
                ├── mto:UploadTransfer
                ├── mto:DownloadTransfer
                ╰── mto:SyncTransfer

## Properties

### The `“mto:transferPrivacyLevel”` property

    “mto:transferPrivacyLevel”          xsd:string

It will contain an string with the privacy level in the service. The exact string and its interpretation is service specific

Number of possible elements per resource (Cardinality): Unlimited

### The `“mto:agent”` property

    “mto:agent”          nfo:Software

The application processing the transfer - e.g. Upload Engine etc

Number of possible elements per resource (Cardinality): 1

### The `“mto:starter”` property

    “mto:starter”          nfo:Software

The application that actually triggered the transfer - e.g. Gallery, Content Manager etc

Number of possible elements per resource (Cardinality): 1

### The `“mto:account”` property

    “mto:account”          xsd:string

A reference to the account to which the web upload is to be done. This should at least contain information about the account and the service which is being used. For instance, Google/YouTube or Google/Picassa

Number of possible elements per resource (Cardinality): 1

### The `“mto:transferList”` property

    “mto:transferList”          mto:TransferElement

A list of transfer elements

Number of possible elements per resource (Cardinality): Unlimited

### The `“mto:created”` property

    “mto:created”          xsd:dateTime

The date and time when the transfer was created

Number of possible elements per resource (Cardinality): 1

### The `“mto:method”` property

    “mto:method”          mto:TransferMethod

The method of transfer - Bluetooth, Web upload etc

Number of possible elements per resource (Cardinality): 1

### The `“mto:transferState”` property

    “mto:transferState”          mto:State

Captures the state of the transfer. This is derived from the cumulative states of the transfer elements of this transfer. Applications are responsible to keep it up-to-date

Number of possible elements per resource (Cardinality): 1

## See also

The upstream documentation for the MTO ontology.