CMIS4DAM Use Cases
System. An entity that complies with the DAM standard. This is more general than the CMIS notion of a repository. A DAM-compliant system need not be a repository. It could, for example, be a web server that supplies content from CMIS repositories or other DAM-compliant systems. It might be better to call this actor a Server.
Application. An entity that manages or uses assets. Unlike a system, an application need not be DAM-compliant.
Federation. A system that federates multiple autonomous DAM-compliant systems that may be unaware that they are being federated.
The use cases are arranged in categories of use case for convenience and to relate them with the CMIS4DAM-specific use cases.
Metadata access and integration. There is no corresponding CMIS use case. CMIS4DAM addresses metadata interoperability and disambiguation.
Metadata interoperability. While virtually all digital asset managers support XMP, there are many other metadata standards. Expression, representation, serialization of that metadata.
Metadata disambiguation. Different vocabs expressing the same data points: IPTC as Dublin Core, or any domain-specific fields that are not part of any metadata standard.
System-to-System. In this use case, systems interact with each other. The CMIS use case is Repository-to-Repository (R2R).
- One system manages assets that are stored in other systems.
- Publishing assets from one system to another system.
Application-to-System. This is an asymmetric interaction. The CMIS use case is Application-to-Repository (A2R). The CMIS use case includes A and B for documents.
Collaboration systems. The ICOM TC has developed a detailed object model for interoperation between collaborative systems. The ICOM object model is, in principle, expressible as a CMIS profile although this has not yet been specified.
Desktop systems. Various applications could use a CMIS-compliant repository for managing their documents. This would also be possible for DAM-compliant systems.
Asynchronous access. Assets may be accessed asynchronously. In particular, an asset might not exist yet, could be ordered, and the requesting application would be notified (via server push) when the asset is available. The first version of CMIS4DAM will only specify pull coding (polling).
Rendition technical information. The technical properties of a rendition will be specified by metadata. This requires the metadata use case.
Federated Systems. A system that federates multiple autonomous DAM-compliant systems that may be unaware that they are being federated. Federation enables you to find assets, but doesn't allow editing.
Federated Search. A single query of a single node may be used to search multiple repositories. CMIS4DAM does not specify how different metadata standards would be mapped to enable federated queries.
Federation instead of migration. A legacy repository would be federated with a new repository. Old content remains on the legacy repository until it becomes outdated or is migrated. All new content is on the new repository.
System Integration. For example, between WCM and DAM, between PIM and DAM, between media management and media delivery.