Content Views

The content views page can be accessed via The Content Menu:

Content > Content Views

The content views page forms a part of orcharhino’s content management. (See also: Content Management Guide).

A content view is a named (and versioned) collection of (local) orcharhino repositories. In order to add any repositories to a content view those repositories must first be added to (and synchronized with) orcharhino using the products page. (See also Products).

It is possible to add any number of repositories (of any number of repository types) from any number of products to any given content view. Once any desired repositories have been added to a new content view, it is necessary to publish (a new version) of that content view. This will create a fixed snapshot of the repositories contained in the content view, as they were at the time of publication. (Subsequent synchronizations of the underlying repositories with their remote sources, will not affect such snapshots).

The first publication of a content view, is referred to as “version 1.0” of that content view, and the major version number is iterated for subsequent publications (2.0, 3.0, etc). The publication of newer versions of a content view, is the only way for content views to reflect changes (newer synchronizations) to the underlying repositories contained within.

It is also possible to apply Errata to some published version of a content view. Doing so will create minor versions of the content view (1.1, 1.2, 2.1, etc).

The purpose of such versioning is to create stable software sets for the distribution to hosts. Ultimately each host will be associated with a single content view, such that this view must contain all the repositories needed by the registered hosts. However, it is possible to create composite content views by combining existing content views. (Hosts can then be registered to a composite content view aggregating everything those hosts might need.)

What version of a content view is delivered to some given host registered to the view, depends on the lifecycle environment the host is in. (See also: Lifecycle Environments). The mechanism employed to register hosts with a given view, involves the use of activation keys. (See also: Activation Keys).