The entry-type Resource
CUE Live requires
an additional publication resource called entry-type
.
It is an XML resource that defines the field structure of different
CUE Live
entry types in the same way as the content-type
resource defines the field structure of content types. It is in fact
very similar to the content-type
resource, and uses
the same elements and namespaces. It is, however, generally simpler than
a content-type
resource since entries have simpler
structures than content items.
For a description of the standard content-type
resource format, see the
Escenic Content Engine
Resource Reference. When you are creating an
entry-type
resource rather than a
content-type
resource, then you need to take the
following factors into account:
-
Each
content-type
element defines a CUE Live entry type, not a content type. -
The
panel
element is required bycontent-type
resource syntax, but has no meaning in CUE Live. You should therefore create just onepanel
in eachcontent-type
element as a container for all itsfield
elements. -
Summary and relation-related elements such as
summary
,relation-type
,relation-type-group
have no meaning in CUE Live and are ignored if present. -
The following field types are not supported by CUE Live and will be ignored if present:
collection complex schedule
-
Some
field
elements may contain special CUE Live elements belonging to thehttp://xmlns.escenic.com/2015/live-center
namespace. For details see Special CUE Live Elements. -
The
entry-type
resource may also containparameter
elements for special purposes. For details see entry-type Parameters.