The Beat platform distinguishes between Content and Editorial. This page will give you an introduction to both. Simply put, the difference between the two is:
Content and Editorial are clearly divided in our system architecture. This division of responsibility is also reflected in our database management tools; information about actors, series, and releases belongs to the content section, whilst information about release groups, banners, banner groups, etc. belongs to the editorial section.
The following diagram illustrates the division and provides an overview of the architecture for each section:
graph TD
URL
subgraph Content
R[Release]
S[Series]
A[Actor]
S -- "contains (1:n)" --> R
A -- "author, narrator, translator (n:n)" --> R
end
subgraph Editorial
RG[Release group]
B[Banner]
BG[Banner group]
L[Layout]
LS[Layout section]
RG -- "contains (1:n)" --> R
BG -- "contains (1:n)" --> B
BG -- "generated from (1:1)" --> RG
B -. "links to (1:1)" .-> R
B -. "links to (1:1)" .-> A
B -. "links to (1:1)" .-> S
B -. "links to (1:1)" .-> BG
B -. "links to (1:1)" .-> L
B -. "links to (1:1)" .-> URL
B -. "links to (1:1)" .-> RG
L -- "contains (1:n)" --> LS
LS -- "uses (1:1)" --> BG
LS -. "optionally links to (1:1)" .-> RG
end
<aside> ℹ️ In the edges between nodes above, the cardinality of the link is indicated in parenthesis. The cardinality defines how many entities on one side, link to entities on the other side. You should read the diagram like this:
<aside> 💡 If you are new to Beat’s services, don’t expect to understand this diagram immediately as it takes some time to familiarize yourself with it. Please read through the entire page where the concepts in the diagram are presented, then return and take a moment to study how things are connected. Remember that for any unfamiliar vocabulary, you can always refer to our Glossary.
</aside>
When presenting these entities, we will start from the bottom up, meaning we will start with the most isolated concept and build from there.