When copying content, the system performs the following actions in order to copy over, match up, and publish.

• Article content – all article content managed directly through the article manager is copied over to the target site
  • Kicker
  • Headline
  • Sub-headline
  • Author (see below)
  • Teaser
  • Body (body 1, body 2, etc)
  • Keywords
  • Image (see below)
  • Go live date and time/Pull data and time
  • Indexable
  • Allow Talkback
  • Publication, volume, issue, publication number, original publication date fields
  • Taxonomy (see below)
  • Friendly URL
  • Browser Title
  • Meta description and keywords
  • Canonical tag editor (NEW)
  • Associated media files (see below)
• Media – Images and video associated to the article using the article manager will be copied to the target website.
  • Images in the article body must use a full path (not a relative path – e.g. <src url=”/ext/resources/images/bob.jpg” />) when copied over or the image will display as a broken image on the target site.
  • Associated images (main image, article media tool images) will be copied over and will display correctly.
  • Video associated through the media view in the article manager (Editorial >> Article Manager >> Edit >> Media) will be copied over.
• Taxonomy – all taxonomy is matched on internal names assigned on both the source and target websites by an ePublishing developer. We assume that this process or creating internal names will happen when the target website is ready for launch and internal names will only be periodically updated. Updating internal names can be done by an ePublishing project manager or developer when needed. If the system cannot find a match on an internal name, then the taxonomy will not be copied over or associated to the article on the target website.
  • Site Placement
  • Classification taxonomy
  • Topic taxonomy
• Authors – All author associations with the article on the source site will be copied to the target site. We will match on the email address associated with the author. This is the only reliable, unique field available for matching.
  • If the author on the source site has an email address that matches an author on the target site, we will update the author details on the target site with the author data from the source website. This way, updates to author details will be propagated to target sites when articles they are associated with are copied over.
  • If no email address is set for the author on the source site or the target site, we have nothing to match on. The author will be created on the target site even if an author with the same name already exists.
  • Multiple author associations to articles will be preserved.
• NOT COPIED – the following data and associations will not be copied to the target site.
  • Related content listed in the “Related” view of the article manager.
  • Inline images (as explained above)
  • Product associations
  • View counts/
  • Comments
  • Tracked changes
• Legacy ID Field use – the system will use the article’s Legacy ID field on the target website to contain a unique string that will identify where the article was copied from. This field is not editable.
• Canonical tagging on target – A new canonical tag manager field will be added to the article admin tools on the SEO page. This will allow insertion/editing/deletion of a canonical tag on any website. Note the following:
  • By default, a canonical tag will be automatically created and inserted on the target website pointing back to the parent website.
  • If the article on the source website already has a canonical tag set then we will copy over the canonical tag to the target website to preserve correct canonicalization.
  • If an editor does not want the target website to have a canonical tag pointing back to the source or needs to update the canonical tag, they can log into the source website and edit the tag within the article manager SEO view.