This session creates, updates, and deletes AssetContents in bulk. The data for create and update is provided by the consumer via the form object. OsidForms are requested for each create or update and may not be reused.

Create and update operations differ in their usage. To create an AssetContent, an AssetContentForm is requested using geAssetContentFormsForCreate() specifying the desired assets and record Types or none if no record Types are needed. Each of the returned AssetContentForms will indicate that it is to be used with a create operation and can be used to examine metdata or validate data prior to creation. Once an AssetContentForm is submiited to a create operation, it cannot be reused with another create operation unless the first operation was unsuccessful. Each AssetContentForm corresponds to an attempted transaction.

The AssetContentForms returned from getAssetContentFormsForCreate() may be linked to the originating request through the peer Ids of the AssetContentForm. In the case where there may be duplicates, any AssetContentForm of the same peer Ids may be used for a create operation.

Once a batch of AssetContentForms are submitted for create, a CreateResponse is returned for each AssetContentForm, although the ordering is not defined. Only errors that pertain to the entire create operation are returned from createAssetContents(), errors specific to an individual AssetContentForm are indicated in the corresponding CreateResponse. CreateResponses may be linked to the originating AssetContentForm through the AssetContentForm Id.

For updates, AssetContentForms are requested to the AssetContent Id that is to be updated using getAssetContentFormsForUpdate() where the reference Id in the AssetContentForm may be used to link the request. Similarly, the AssetForm has metadata about the data that can be updated and it can perform validation before submitting the update. The AssetContentForm can only be used once for a successful update and cannot be reused.

Once a batch of AssetContentForms are submitted for update, an UpdateResponse is returned for each AssetContentForm, although the ordering is not defined. Only errors that pertain to the entire update operation are returned from updateAssetContents(), errors specific to an individual AssetContentForm are indicated in the corresponding UpdateResponse. UpdateResponses may be linked to the originating AssetContentForm through the AssetContentForm Id.

The delete operations delete AssetContents in bulk. To unmap an AssetContent from the current Repository, the AssetContentRepositoryAssignmentSession should be used. These delete operations attempt to remove the AssetContent itself thus removing it from all known Repository catalogs. Bulk delete operations return the results in DeleteResponses.