Egmont Publishing Norway: Highly Efficient Magazine

Primary tabs

Secondary tabs

... (Array, 21 elements)
- body (Array, 16 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 5
 - #title (String, 4 characters ) Body
 - #access (Boolean) TRUE
 - #label_display (String, 6 characters ) hidden
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 4 characters ) body
 - #field_type (String, 17 characters ) text_with_summary
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 9 characters ) dcx_story
 - #object (Object) stdClass
 
 vid (String, 4 characters ) 1466
 
 uid (String, 1 characters ) 0
 
 title (String, 52 characters ) Egmont Publishing Norway: Highly Efficient Maga...
 
 Egmont Publishing Norway: Highly Efficient Magazine
 
 log (String, 0 characters )
 
 status (String, 1 characters ) 1
 
 comment (String, 1 characters ) 2
 
 promote (String, 1 characters ) 1
 
 sticky (String, 1 characters ) 0
 
 nid (String, 4 characters ) 1439
 
 type (String, 9 characters ) dcx_story
 
 language (String, 3 characters ) und
 
 created (String, 10 characters ) 1576149096
 
 changed (String, 10 characters ) 1576149096
 
 tnid (String, 1 characters ) 0
 
 translate (String, 1 characters ) 0
 
 revision_timestamp (String, 10 characters ) 1576149096
 
 revision_uid (String, 1 characters ) 0
 
 body (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 5 elements)
 
 value (String, 5363 characters ) Starting point Egmont Publishing Norway ...
 
 Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partnerThe first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision:
 
 summary (NULL)
 
 format (String, 9 characters ) full_html
 
 safe_value (String, 5372 characters ) Starting point Egmont Publishing Norway...
 
 Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partnerThe first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision:
 
 safe_summary (String, 0 characters )
 
 field_author (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 17 characters ) Steffen Landsberg
 
 format (NULL)
 
 safe_value (String, 17 characters ) Steffen Landsberg
 
 field_highline (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 5 characters ) BMG 2
 
 format (NULL)
 
 safe_value (String, 5 characters ) BMG 2
 
 field_images (Array, 1 element)
 
 und (Array, 2 elements)
 
 0 (Array, 13 elements)
 
 fid (String, 4 characters ) 2290
 
 uid (String, 1 characters ) 0
 
 filename (String, 28 characters ) file78ddjrebv461ch39622u.jpg
 
 uri (String, 37 characters ) public://file78ddjrebv461ch39622u.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 5 characters ) 60835
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 533
 
 1 (Array, 13 elements)
 
 fid (String, 4 characters ) 2291
 
 uid (String, 1 characters ) 0
 
 filename (String, 28 characters ) file74j7xow27w81213ua6a6.jpg
 
 uri (String, 37 characters ) public://file74j7xow27w81213ua6a6.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 4 characters ) 5678
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 800
 
 field_primary_image (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 13 elements)
 
 fid (String, 4 characters ) 2289
 
 uid (String, 1 characters ) 0
 
 filename (String, 27 characters ) file78ddjzdc1ugysygv22v.jpg
 
 uri (String, 36 characters ) public://file78ddjzdc1ugysygv22v.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 5 characters ) 52841
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 520
 
 field_section (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 9 characters ) Lifestyle
 
 format (NULL)
 
 safe_value (String, 9 characters ) Lifestyle
 
 field_sid (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 22 characters ) doc78deeugqtkhy8ez28ns
 
 format (NULL)
 
 safe_value (String, 22 characters ) doc78deeugqtkhy8ez28ns
 
 field_subheadline (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 0 characters )
 
 format (NULL)
 
 safe_value (String, 0 characters )
 
 field_socialshareprivacy (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 1 element)
 
 value (String, 1 characters ) 1
 
 field_shariff (Array, 1 element)
 
 und (Array, 1 element)
 
 0 (Array, 1 element)
 
 value (String, 1 characters ) 1
 
 rdf_mapping (Array, 9 elements)
 
 rdftype (Array, 2 elements)
 
 0 (String, 9 characters ) sioc:Item
 
 1 (String, 13 characters ) foaf:Document
 
 title (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 8 characters ) dc:title
 
 created (Array, 3 elements)
 
 predicates (Array, 2 elements)
 
 0 (String, 7 characters ) dc:date
 
 1 (String, 10 characters ) dc:created
 
 datatype (String, 12 characters ) xsd:dateTime
 
 callback (String, 12 characters ) date_iso8601 | (Callback) date_iso8601();
 
 changed (Array, 3 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 11 characters ) dc:modified
 
 datatype (String, 12 characters ) xsd:dateTime
 
 callback (String, 12 characters ) date_iso8601 | (Callback) date_iso8601();
 
 body (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 15 characters ) content:encoded
 
 uid (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 16 characters ) sioc:has_creator
 
 type (String, 3 characters ) rel
 
 name (Array, 1 element)
 
 predicates (Array, 1 element)
 
 0 (String, 9 characters ) foaf:name
 
 comment_count (Array, 2 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 16 characters ) sioc:num_replies
 
 datatype (String, 11 characters ) xsd:integer
 
 last_activity (Array, 3 elements)
 
 predicates (Array, 1 element)
 
 0 (String, 23 characters ) sioc:last_activity_date
 
 datatype (String, 12 characters ) xsd:dateTime
 
 callback (String, 12 characters ) date_iso8601 | (Callback) date_iso8601();
 
 cid (String, 1 characters ) 0
 
 last_comment_timestamp (String, 10 characters ) 1576149096
 
 last_comment_name (NULL)
 
 last_comment_uid (String, 1 characters ) 0
 
 comment_count (String, 1 characters ) 0
 
 name (String, 0 characters )
 
 picture (String, 1 characters ) 0
 
 data (NULL)
 
 entity_view_prepared (Boolean) TRUE
 - #items (Array, 1 element)
 
 0 (Array, 5 elements)
 
 value (String, 5363 characters ) Starting point Egmont Publishing Norway ...
 
 Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partnerThe first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision:
 
 summary (NULL)
 
 format (String, 9 characters ) full_html
 
 safe_value (String, 5372 characters ) Starting point Egmont Publishing Norway...
 
 Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partnerThe first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision:
 
 safe_summary (String, 0 characters )
 - #formatter (String, 12 characters ) text_default
 - 0 (Array, 1 element)
 
 #markup (String, 5372 characters ) Starting point Egmont Publishing Norway...
 
 Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partnerThe first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision: Starting point Egmont Publishing Norway employs around 150 authors and editors in addition to 300 freelance writers, who create content for its print editions and online features. The systems previously used by the publisher limited its ability to manage a wide selection of content in a structured manner. There was no easy way to exchange content between its print and digital media. In 2017, the growing relevance of its web-based content led Egmont Publishing Norway to look for a solution that would ensure the efficient production of print editions while simultaneously supplying content to its digital channels. The search for the right partner The first step taken by Egmont Publishing Norway was to identify its requirements for the production of print and digital content, so that it could start scouring the market for suitable software solutions. The publisher wasn’t just looking to purchase a product; it wanted to find a reliable partner to help achieve its publishing objectives. After reviewing various offers, the company narrowed its initial selection down to three solutions. Further in-depth workshops followed, before the Content-X solution developed by ppi Media and Digital Collections was eventually chosen in October 2018. There were many crucial factors that led to this decision:
- field_author (Array, 16 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 9
 - #title (String, 3 characters ) von
 - #access (Boolean) TRUE
 - #label_display (String, 6 characters ) inline
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 12 characters ) field_author
 - #field_type (String, 4 characters ) text
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 9 characters ) dcx_story
 - #object (Object) stdClass
 
 ∞ (Recursion)
 - #items (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 17 characters ) Steffen Landsberg
 
 format (NULL)
 
 safe_value (String, 17 characters ) Steffen Landsberg
 - #formatter (String, 12 characters ) text_default
 - 0 (Array, 1 element)
 
 #markup (String, 17 characters ) Steffen Landsberg
- field_images (Array, 17 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 3
 - #title (String, 7 characters ) Gallery
 - #access (Boolean) TRUE
 - #label_display (String, 6 characters ) hidden
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 12 characters ) field_images
 - #field_type (String, 5 characters ) image
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 9 characters ) dcx_story
 - #object (Object) stdClass
 
 ∞ (Recursion)
 - #items (Array, 2 elements)
 
 0 (Array, 13 elements)
 
 fid (String, 4 characters ) 2290
 
 uid (String, 1 characters ) 0
 
 filename (String, 28 characters ) file78ddjrebv461ch39622u.jpg
 
 uri (String, 37 characters ) public://file78ddjrebv461ch39622u.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 5 characters ) 60835
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 533
 
 1 (Array, 13 elements)
 
 fid (String, 4 characters ) 2291
 
 uid (String, 1 characters ) 0
 
 filename (String, 28 characters ) file74j7xow27w81213ua6a6.jpg
 
 uri (String, 37 characters ) public://file74j7xow27w81213ua6a6.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 4 characters ) 5678
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 800
 - #formatter (String, 8 characters ) colorbox
 - 0 (Array, 8 elements)
 
 #theme (String, 24 characters ) colorbox_image_formatter
 
 #item (Array, 13 elements)
 
 fid (String, 4 characters ) 2290
 
 uid (String, 1 characters ) 0
 
 filename (String, 28 characters ) file78ddjrebv461ch39622u.jpg
 
 uri (String, 37 characters ) public://file78ddjrebv461ch39622u.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 5 characters ) 60835
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 533
 
 #entity_type (String, 4 characters ) node
 
 #entity (Object) stdClass
 
 ∞ (Recursion)
 
 #node (Object) stdClass
 
 ∞ (Recursion)
 
 #field (Array, 16 elements)
 
 entity_types (Array, 0 elements)
 
 foreign keys (Array, 1 element)
 
 fid (Array, 2 elements)
 
 table (String, 12 characters ) file_managed
 
 columns (Array, 1 element)
 
 fid (String, 3 characters ) fid
 
 indexes (Array, 1 element)
 
 fid (Array, 1 element)
 
 0 (String, 3 characters ) fid
 
 settings (Array, 2 elements)
 
 default_image (Integer) 0
 
 uri_scheme (String, 6 characters ) public
 
 translatable (String, 1 characters ) 0
 
 storage (Array, 5 elements)
 
 type (String, 17 characters ) field_sql_storage
 
 settings (Array, 0 elements)
 
 module (String, 17 characters ) field_sql_storage
 
 active (String, 1 characters ) 1
 
 details (Array, 1 element)
 
 sql (Array, 2 elements)
 
 FIELD_LOAD_CURRENT (Array, 1 element)
 
 field_data_field_images (Array, 5 elements)
 
 fid (String, 16 characters ) field_images_fid
 
 alt (String, 16 characters ) field_images_alt
 
 title (String, 18 characters ) field_images_title
 
 width (String, 18 characters ) field_images_width
 
 height (String, 19 characters ) field_images_height
 
 FIELD_LOAD_REVISION (Array, 1 element)
 
 field_revision_field_images (Array, 5 elements)
 
 fid (String, 16 characters ) field_images_fid
 
 alt (String, 16 characters ) field_images_alt
 
 title (String, 18 characters ) field_images_title
 
 width (String, 18 characters ) field_images_width
 
 height (String, 19 characters ) field_images_height
 
 id (String, 2 characters ) 11
 
 field_name (String, 12 characters ) field_images
 
 type (String, 5 characters ) image
 
 module (String, 5 characters ) image
 
 active (String, 1 characters ) 1
 
 locked (String, 1 characters ) 0
 
 cardinality (String, 2 characters ) -1
 
 deleted (String, 1 characters ) 0
 
 columns (Array, 5 elements)
 
 fid (Array, 4 elements)
 
 description (String, 54 characters ) The {file_managed}.fid being referenced in this...
 
 The {file_managed}.fid being referenced in this field.
 
 type (String, 3 characters ) int
 
 not null (Boolean) FALSE
 
 unsigned (Boolean) TRUE
 
 alt (Array, 4 elements)
 
 description (String, 56 characters ) Alternative image text, for the image's 'alt' a...
 
 Alternative image text, for the image's 'alt' attribute.
 
 type (String, 7 characters ) varchar
 
 length (Integer) 512
 
 not null (Boolean) FALSE
 
 title (Array, 4 elements)
 
 description (String, 52 characters ) Image title text, for the image's 'title' attri...
 
 Image title text, for the image's 'title' attribute.
 
 type (String, 7 characters ) varchar
 
 length (Integer) 1024
 
 not null (Boolean) FALSE
 
 width (Array, 3 elements)
 
 description (String, 33 characters ) The width of the image in pixels.
 
 type (String, 3 characters ) int
 
 unsigned (Boolean) TRUE
 
 height (Array, 3 elements)
 
 description (String, 34 characters ) The height of the image in pixels.
 
 type (String, 3 characters ) int
 
 unsigned (Boolean) TRUE
 
 bundles (Array, 1 element)
 
 node (Array, 1 element)
 
 0 (String, 9 characters ) dcx_story
 
 #display_settings (Array, 8 elements)
 
 colorbox_node_style (String, 28 characters ) gallery-crop_scale__200x200_
 
 colorbox_node_style_first (String, 0 characters )
 
 colorbox_image_style (String, 28 characters ) gallery-crop_scale__200x200_
 
 colorbox_gallery (String, 4 characters ) post
 
 colorbox_gallery_custom (String, 0 characters )
 
 colorbox_caption (String, 4 characters ) auto
 
 colorbox_caption_custom (String, 0 characters )
 
 colorbox_multivalue_index (NULL)
 
 #delta (Integer) 0
 - 1 (Array, 8 elements)
 
 #theme (String, 24 characters ) colorbox_image_formatter
 
 #item (Array, 13 elements)
 
 fid (String, 4 characters ) 2291
 
 uid (String, 1 characters ) 0
 
 filename (String, 28 characters ) file74j7xow27w81213ua6a6.jpg
 
 uri (String, 37 characters ) public://file74j7xow27w81213ua6a6.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 4 characters ) 5678
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 800
 
 #entity_type (String, 4 characters ) node
 
 #entity (Object) stdClass
 
 ∞ (Recursion)
 
 #node (Object) stdClass
 
 ∞ (Recursion)
 
 #field (Array, 16 elements)
 
 entity_types (Array, 0 elements)
 
 foreign keys (Array, 1 element)
 
 fid (Array, 2 elements)
 
 table (String, 12 characters ) file_managed
 
 columns (Array, 1 element)
 
 fid (String, 3 characters ) fid
 
 indexes (Array, 1 element)
 
 fid (Array, 1 element)
 
 0 (String, 3 characters ) fid
 
 settings (Array, 2 elements)
 
 default_image (Integer) 0
 
 uri_scheme (String, 6 characters ) public
 
 translatable (String, 1 characters ) 0
 
 storage (Array, 5 elements)
 
 type (String, 17 characters ) field_sql_storage
 
 settings (Array, 0 elements)
 
 module (String, 17 characters ) field_sql_storage
 
 active (String, 1 characters ) 1
 
 details (Array, 1 element)
 
 sql (Array, 2 elements)
 
 FIELD_LOAD_CURRENT (Array, 1 element)
 
 field_data_field_images (Array, 5 elements)
 
 fid (String, 16 characters ) field_images_fid
 
 alt (String, 16 characters ) field_images_alt
 
 title (String, 18 characters ) field_images_title
 
 width (String, 18 characters ) field_images_width
 
 height (String, 19 characters ) field_images_height
 
 FIELD_LOAD_REVISION (Array, 1 element)
 
 field_revision_field_images (Array, 5 elements)
 
 fid (String, 16 characters ) field_images_fid
 
 alt (String, 16 characters ) field_images_alt
 
 title (String, 18 characters ) field_images_title
 
 width (String, 18 characters ) field_images_width
 
 height (String, 19 characters ) field_images_height
 
 id (String, 2 characters ) 11
 
 field_name (String, 12 characters ) field_images
 
 type (String, 5 characters ) image
 
 module (String, 5 characters ) image
 
 active (String, 1 characters ) 1
 
 locked (String, 1 characters ) 0
 
 cardinality (String, 2 characters ) -1
 
 deleted (String, 1 characters ) 0
 
 columns (Array, 5 elements)
 
 fid (Array, 4 elements)
 
 description (String, 54 characters ) The {file_managed}.fid being referenced in this...
 
 The {file_managed}.fid being referenced in this field.
 
 type (String, 3 characters ) int
 
 not null (Boolean) FALSE
 
 unsigned (Boolean) TRUE
 
 alt (Array, 4 elements)
 
 description (String, 56 characters ) Alternative image text, for the image's 'alt' a...
 
 Alternative image text, for the image's 'alt' attribute.
 
 type (String, 7 characters ) varchar
 
 length (Integer) 512
 
 not null (Boolean) FALSE
 
 title (Array, 4 elements)
 
 description (String, 52 characters ) Image title text, for the image's 'title' attri...
 
 Image title text, for the image's 'title' attribute.
 
 type (String, 7 characters ) varchar
 
 length (Integer) 1024
 
 not null (Boolean) FALSE
 
 width (Array, 3 elements)
 
 description (String, 33 characters ) The width of the image in pixels.
 
 type (String, 3 characters ) int
 
 unsigned (Boolean) TRUE
 
 height (Array, 3 elements)
 
 description (String, 34 characters ) The height of the image in pixels.
 
 type (String, 3 characters ) int
 
 unsigned (Boolean) TRUE
 
 bundles (Array, 1 element)
 
 node (Array, 1 element)
 
 0 (String, 9 characters ) dcx_story
 
 #display_settings (Array, 8 elements)
 
 colorbox_node_style (String, 28 characters ) gallery-crop_scale__200x200_
 
 colorbox_node_style_first (String, 0 characters )
 
 colorbox_image_style (String, 28 characters ) gallery-crop_scale__200x200_
 
 colorbox_gallery (String, 4 characters ) post
 
 colorbox_gallery_custom (String, 0 characters )
 
 colorbox_caption (String, 4 characters ) auto
 
 colorbox_caption_custom (String, 0 characters )
 
 colorbox_multivalue_index (NULL)
 
 #delta (Integer) 1
- field_primary_image (Array, 16 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 1
 - #title (String, 13 characters ) Primary Image
 - #access (Boolean) TRUE
 - #label_display (String, 6 characters ) hidden
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 19 characters ) field_primary_image
 - #field_type (String, 5 characters ) image
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 9 characters ) dcx_story
 - #object (Object) stdClass
 
 ∞ (Recursion)
 - #items (Array, 1 element)
 
 0 (Array, 13 elements)
 
 fid (String, 4 characters ) 2289
 
 uid (String, 1 characters ) 0
 
 filename (String, 27 characters ) file78ddjzdc1ugysygv22v.jpg
 
 uri (String, 36 characters ) public://file78ddjzdc1ugysygv22v.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 5 characters ) 52841
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 520
 - #formatter (String, 5 characters ) image
 - 0 (Array, 4 elements)
 
 #theme (String, 15 characters ) image_formatter
 
 #item (Array, 13 elements)
 
 fid (String, 4 characters ) 2289
 
 uid (String, 1 characters ) 0
 
 filename (String, 27 characters ) file78ddjzdc1ugysygv22v.jpg
 
 uri (String, 36 characters ) public://file78ddjzdc1ugysygv22v.jpg
 
 filemime (String, 10 characters ) image/jpeg
 
 filesize (String, 5 characters ) 52841
 
 status (String, 1 characters ) 1
 
 timestamp (String, 10 characters ) 1576149096
 
 rdf_mapping (Array, 0 elements)
 
 alt (NULL)
 
 title (String, 0 characters )
 
 width (String, 3 characters ) 800
 
 height (String, 3 characters ) 520
 
 #image_style (String, 27 characters ) news-detail-big__999x412px_
 
 #path (String, 0 characters )
- field_section (Array, 16 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 0
 - #title (String, 7 characters ) Section
 - #access (Boolean) TRUE
 - #label_display (String, 6 characters ) hidden
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 13 characters ) field_section
 - #field_type (String, 4 characters ) text
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 9 characters ) dcx_story
 - #object (Object) stdClass
 
 ∞ (Recursion)
 - #items (Array, 1 element)
 
 0 (Array, 3 elements)
 
 value (String, 9 characters ) Lifestyle
 
 format (NULL)
 
 safe_value (String, 9 characters ) Lifestyle
 - #formatter (String, 12 characters ) text_default
 - 0 (Array, 1 element)
 
 #markup (String, 9 characters ) Lifestyle
- field_shariff (Array, 16 elements)
 - #theme (String, 5 characters ) field
 - #weight (String, 1 characters ) 2
 - #title (String, 7 characters ) Shariff
 - #access (Boolean) TRUE
 - #label_display (String, 5 characters ) above
 - #view_mode (String, 4 characters ) full
 - #language (String, 3 characters ) und
 - #field_name (String, 13 characters ) field_shariff
 - #field_type (String, 7 characters ) shariff
 - #field_translatable (String, 1 characters ) 0
 - #entity_type (String, 4 characters ) node
 - #bundle (String, 9 characters ) dcx_story
 - #object (Object) stdClass
 
 ∞ (Recursion)
 - #items (Array, 1 element)
 
 0 (Array, 1 element)
 
 value (String, 1 characters ) 1
 - #formatter (String, 17 characters ) shariff_formatter
 - 0 (Array, 15 elements)
 
 #theme (String, 7 characters ) shariff
 
 #services (Array, 2 elements)
 
 twitter (String, 7 characters ) twitter
 
 facebook (String, 8 characters ) facebook
 
 #shariff_theme (String, 7 characters ) colored
 
 #orientation (String, 10 characters ) horizontal
 
 #twitter_via (NULL)
 
 #mail_url (NULL)
 
 #mail_subject (NULL)
 
 #mail_body (NULL)
 
 #referrer_track (NULL)
 
 #backend_url (NULL)
 
 #flattr_category (NULL)
 
 #flattr_user (NULL)
 
 #media_url (NULL)
 
 #lang (String, 2 characters ) en
 
 #url (String, 111 characters ) https://support-portal.content-x.de/cx-online4/...
 
 https://support-portal.content-x.de/cx-online4/en/dc-x-story/egmont-publishing-norway-highly-efficient-magazine
- #pre_render (Array, 1 element)
 - 0 (String, 30 characters ) _field_extra_fields_pre_render | (Callback) _field_extra_fields_pre_render();
- #entity_type (String, 4 characters ) node
- #bundle (String, 9 characters ) dcx_story
- title (Array, 14 elements)
 - #theme (String, 5 characters ) field
 - #field_type (String, 2 characters ) ds
 - #skip_edit (Boolean) TRUE
 - #title (String, 8 characters ) Headline
 - #weight (String, 1 characters ) 4
 - #label_display (String, 6 characters ) hidden
 - #field_name (String, 5 characters ) title
 - #bundle (String, 9 characters ) dcx_story
 - #object (Object) stdClass
 
 ∞ (Recursion)
 - #entity_type (String, 4 characters ) node
 - #view_mode (String, 4 characters ) full
 - #access (Boolean) TRUE
 - #items (Array, 1 element)
 
 0 (Array, 1 element)
 
 value (String, 61 characters ) <h2>Egmont Publishing Norway: Highly Efficient ...
 
 <h2>Egmont Publishing Norway: Highly Efficient Magazine </h2>
 - 0 (Array, 1 element)
 
 #markup (String, 61 characters ) <h2>Egmont Publishing Norway: Highly Efficient ...
 
 <h2>Egmont Publishing Norway: Highly Efficient Magazine </h2>
- #attached (Array, 1 element)
 - css (Array, 1 element)
 
 0 (String, 64 characters ) sites/all/modules/ds/layouts/ds_2col_stacked/ds...
 
 sites/all/modules/ds/layouts/ds_2col_stacked/ds_2col_stacked.css
- #groups (Array, 0 elements)
- #fieldgroups (Array, 0 elements)
- #group_children (Array, 0 elements)
- links (Array, 6 elements)
 - #theme (String, 11 characters ) links__node
 - #pre_render (Array, 1 element)
 
 0 (String, 23 characters ) drupal_pre_render_links | (Callback) drupal_pre_render_links();
 - #attributes (Array, 1 element)
 
 class (Array, 2 elements)
 
 0 (String, 5 characters ) links
 
 1 (String, 6 characters ) inline
 - node (Array, 3 elements)
 
 #theme (String, 17 characters ) links__node__node
 
 #links (Array, 0 elements)
 
 #attributes (Array, 1 element)
 
 class (Array, 2 elements)
 
 0 (String, 5 characters ) links
 
 1 (String, 6 characters ) inline
 - comment (Array, 3 elements)
 
 #theme (String, 20 characters ) links__node__comment
 
 #links (Array, 1 element)
 
 comment_forbidden (Array, 2 elements)
 
 title (String, 100 characters ) <a href="/cx-online4/en/user/login?destination=...
 
 <a href="/cx-online4/en/user/login?destination=node/1439%23comment-form">Log in</a> to post comments
 
 html (Boolean) TRUE
 
 #attributes (Array, 1 element)
 
 class (Array, 2 elements)
 
 0 (String, 5 characters ) links
 
 1 (String, 6 characters ) inline
 - statistics (Array, 3 elements)
 
 #theme (String, 23 characters ) links__node__statistics
 
 #links (Array, 1 element)
 
 statistics_counter (Array, 1 element)
 
 title (String, 9 characters ) 409 reads
 
 #attributes (Array, 1 element)
 
 class (Array, 2 elements)
 
 0 (String, 5 characters ) links
 
 1 (String, 6 characters ) inline
- comments (Array, 0 elements)
- submitted_by (Array, 1 element)
 - #markup (String, 111 characters ) PUBLISHED: 12:11 CET...
 
 PUBLISHED: 12:11 CET, 12 December 2019 | UPDATED: 12:11 CET, 12 December 2019
- #view_mode (String, 4 characters ) full
- #theme (String, 4 characters ) node
- #node (Object) stdClass
 - ∞ (Recursion)
- #language (String, 2 characters ) en
Krumo version 0.2.1a
| http://krumo.sourceforge.net

Egmont Publishing Norway: Highly Efficient Magazine

Primary tabs

Secondary tabs

Krumo version 0.2.1a