Content Manager 11.00

Icon

This release has reached its end of support. We strongly advise that you update to a more current release.

For more information on updating or upgrading, please contact your sales representative.

Skip to end of metadata
Go to start of metadata

Content Flow Model

The diagram below illustrates the process that moves Content from your Content Manager to its final destination, your Player. An explanation of the terms found in the table, and more specific explanation of the types of Media follow the diagram. 

 

ItemDescription
TemplateThe layout of a page(s) in which a user can change media assets or fill in the text via a simple form.
Message

Filled-in templates that can be added to your content library.

MediaMedia is an object like an image, video, scalascript, html5 widget, etc that can be placed directly into a Playlist.
ContentContent is all of the above items, but only Messages and Media can be assigned to a Playlist.
PlaylistCollection of Content with specification around how it should be played. At the most basic level, it will define the sequence of those items, and the length each item appears. Within a playlist, there may be item specific scheduling. Also, Playlist can reference and nest other Playlists within them.
ScheduleThe main form of controlling when a Playlist is shown. A schedule contains one or many Playlists.
FrameSubset of a Channel, and each frame has one or many Schedules assigned to it.
ChannelWhat the Player is assigned to listen to. A Channel can be broken down into Frames (or is defined as one full frame). This channel frameset defines the screen real estate into smaller sub-chunks, each with its own content stream.
PlayerA playback device is called the Player. A Player is "tuned" to a Channel in Content Manager.

Security Model

Security settings determine what can be done by Users. An explanation of the terms found in the diagram follow below. 

 

ItemDescription
UsersThese are the accounts with logins. They are the People who access the system. A user can be mapped to workgroups and roles.
PermissionsPermissions are granular security access settings in the system. A permission defines access to functional features within the software.
RolesRoles are groupings of permissions that are assigned to Users.
WorkgroupsUsers are mapped to workgroups. Workgroups are "teams" of people that work together.
ContentA list of media accessible by the User's Workgroup.
System FeaturesA group of users within a role, have permission to interact with the system in a certain way, across the content they have access to.
  • No labels