You are here

C

Glossary terms starting with the letter C.

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

CachingContentStore
The CachingContentStore (CCS) class adds caching to any ContentStore implementation. Wrapping a slow ContentStore in a CachingContentStore improves access speed in many use cases. Example use cases include document storage using a XAM appliance or cloud-based storage, such as Amazon's S3.
CAS
See Central Authentication Service.
catalog
Digital Asset Management term. Cataloguing is the process of adding metadata to digital assets (for example, images and video). A catalog comprises the digital assets (i.e. the assets that include descriptive metadata) stored in a repository.
category
A category in Alfresco allows you to organize your content to help you retrieve the content you are looking for. You classify your content items in Alfresco with categories. The categories are organized into related groups to form a hierarchy. You can link a content item to more than one category.
CDN
See Content Delivery Network.
Central Authentication Service
The Central Authentication Service (CAS) is an authentication system that enables enterprise single sign-on to web sites.
CIFS
Microsoft Common Internet File System (CIFS) is a network file system for sharing files across the Internet.
<classpathRoot>
The <classpathRoot> is the default directory whose contents are automatically added to the start of your application server's classpath. The location of this directory varies depending on your application server.
CMIS
See Content Management Interoperability Services.
codec
Digital Asset Management term. A codec is a program that can encode and decode digital data (audio or video). H.264/MPEG-4 AVC is a codec. FFmpeg supports many common codecs.
composite action
A composite action is a collection of actions that are combined in a designated order to make one unit of work. If any action within the composite fails, then no other actions within this composite are completed. The unit of work can be any size that you determine.
condition
A condition is a test applied to an action used to determine whether the action can be performed.
<configRoot>
The <configRoot> directory is where the default configuration files are stored. Where possible, you should not edit these files but you can edit the overrides in the <extension> directory. For example, for Tomcat, <configRoot> is: <TOMCAT_HOME>/webapps/alfresco/WEB-INF/.
<configRootShare>
The <configRootShare> directory is where the default configuration files for Share are stored. Where possible, you should not edit these files but you can edit the Share override files in the <web-extension> directory. For example, for Tomcat, <configRootShare> is <TOMCAT_HOME>/webapps/share/WEB-INF.
content
Files or documents made of two main elements: the content itself and information about the content (metadata). For example, documents, video, audio, images, XML, and HTML.
content aspect
See aspect.
Content Delivery Network
A Content Delivery (or Distribution) Network (CDN) delivers contents to users using servers and data centers provided by the CDN operator. Examples are Amazon CloudFront and Brightcove Zencoder.
Content Management Interoperability Services
The Content Management Interoperability Services (CMIS) standard defines a domain model and Web Services and Restful AtomPub bindings that can be used by applications to work with one or more Content Management repositories/systems.

The CMIS interface is designed to be layered on top of existing Content Management systems and their existing programmatic interfaces. It is not intended to prescribe how specific features should be implemented within those CM systems, not to exhaustively expose all of the CM system's capabilities through the CMIS interfaces. Rather, it is intended to define a generic/universal set of capabilities provided by a CM system and a set of services for working with those capabilities.

Source: http://docs.oasis-open.org/cmis/CMIS/v1.0/cmis-spec-v1.0.html

Alfresco fully implements both the CMIS 1.0 and 1.1 standards to allow your application to manage content and metadata in an Alfresco repository or in Alfresco in the cloud.

content model
A content model is a collection of related content types and aspects.
content store
A content store provides low-level access to stored binaries ensuring that, for every write, a new binary storage location is made available. By default, Alfresco is configured with two file content stores: the File Content Store and Deleted Content Store.
content type
Content can be categorized as a type and can be one type at any one time. The type describes the fundamental structure of the content.
cURL
cURL is a command-line tool for getting or sending files using URL syntax. Libcurl is the equivalent library. cURL uses libcurl, which supports most common internet protocols.