TERMINALFOUR's Neil O'Neill discusses how T4 Site Manager comes with a number of tools to automatically migrate content, what migration approach is best for you, the steps involved in content migration and the systems we have migrated from.
2. ⢠TERMINALFOUR Site Manager comes with a number of
tools to approach automated migration.
⢠Even with automated migration, some manual
migration will be required for content not handled by
the import tools.
⢠TERMINALFOUR endeavour to migrate at a minimum of
80% of the existing content.
⢠In some cases, custom tools are required to handle
specific site and content structures.
t44u.2013
2
3. Manual
Auto
⢠The amount of content to be migrated <1500
⢠Is content well structured & marked-up correctly?
⢠Complexity of the original web site
⢠Is it coming from another CMS (e.g. Red Dot) ?
⢠Is the HTML source consistent?
⢠Can we access an XML extract
⢠Structured Data: Use Web Objects / Data Objects
/Content Syncer / Web Services integration features
Integration ⢠Live code in pages
⢠Combination of three options above?
t44u.2013
3
4. 1. Access Web Site
6. Manual updates
5. Test / QA
2. Analyse the Data
4. Run the
Migration
t44u.2013
3. Configure the
Migration Tool
4
5. STEP 1 :
Copy of the website
STEP 2 :
STEP 3 :
Analysis of the
website
Configure the
Migration Tool
The content in
HTML, XML, or a
Database dump.
How to determine
the Site Structure?
Media files including
images, linked
documents, videos,
flash movies etc.
Is there multi-lingual
content to be
migrated?
Map the elements
from the existing
pages layouts to the
new content
templates
What is the
structure of the
content (pages)?
t44u.2013
5
6. STEP 4 :
Running the
Migration
Defined XML format &
Defined Structure for
Content
STEP 5 :
STEP 6 :
Test/QA
Manual Update
A link checker is run on
the published website
to determine if there
are any broken links or
missing content.
some manual updates
required in order to fix
issues
Site Structure
Assets.
Two types of manual
review are required
t44u.2013
6
7. 1. How much data is to be migrated i.e. pages, sites by TERMINALFOUR?
2. Will the content be exported from the existing CMS in order to migrate it or will
the published site be used? i.e. what format will the website be provided in.
3. Is the website structure the same or different in the new system? If different a
mapping will be required between the old and the new structure.
4. Is there a one to one mapping from the old page layouts to the new page
layouts?
5. Is there multi-lingual content to be migrated?
6. Will there be content that is not currently in the existing site to be migrated? If
so, what format will this be in?
7. Is there mirrored content (same source content appearing in multiple locations
on the site) within the website that needs to be handled during the migration?
This includes portions of pages.
8. Are the pages well structured with markers to identify different components of
the page?
t44u.2013
7
8. â
â
â
â
â
â
â
â
â
â
â
â
â
t44u.2013
Serena Collage (University of St. Thomas, University of Liverpool)
InterWoven TeamSites (Southern States Coop)
Documentum (Missouri State technical College)
Open Text RedDot (University of the Arts London)
Vignette (OECD)
Microsoft CMS (UNAIDS)
BroadVision (Aer Lingus)
HannonHill Cascade Server
Percussion (NUIG)
SunGard LuminisCMS (University of Huddersfield)
Active Networks IronPoint CMS (University of Fraser Valley, LMU)
DreamWeaver HTML pages (VCU)
Squiz (RMIT Australia, University of Stirling)
8
9. Case Study: Weitz & Luxenberg
⢠A targeted list of page IDâs within a data source to be
migrated in bulk from existing custom CMS.
⢠Create Hierarchy Builder to build parent and child structure
within Site Manager from data source (MS EXCEL).
⢠HTML code being migrated to be âcleanedâ using specified
non-required HTML tags.
⢠Link Resolver to recurse imported HTML code and check for
links that can be resolved â continual checking.
⢠Automatic Static/Regex URL Redirect
t44u.2013
9
10. Case Study: W&L - Database to Database Migration Proposal
Client Produce table of
WebPageID, Level, Section
Name, ContentHTML,
OriginalURL, TemplateID,
MetaDescrip, MetaKeywords
1
2
Table is imported into the
Content Syncer using predefined fields
Content Syncer
W&L
DB
3
Content is imported
into Site Manager
using template /
column mapping
6
5
New section/page information
is used to resolve the links
using a new function to match
previous IDâs with new SM IDâs
Link Resolver
SM
DB
HTML
Cleaner
The HTML is cleaned in
the SM DB without
resolved links
4
11. Case Study: W&L â Data Source
Data Source can be Excel,
SQL or MySQL
Fields need to follow
exact naming convention
t44u.2013
11
12. Case Study: W&L â External Content Syncer Handler
Setup Connection
to Data Source
t44u.2013
12
13. Case Study: W&L â Content Syncer
Ensure Site Creator
Plugin set & test you
can query Database
t44u.2013
13
14. Case Study: W&L â Content Hierarchy Built & Imported
⢠Example ât44uâ
shows section
created and
hierarchy &
content created
t44u.2013
14
15. Case Study: W&L â HTML Cleaner
⢠Current interface available now within Site Manager
Specify Section to clean and upload properties file
t44u.2013
15
16. Case Study: W&L â HTML Cleaner - Options
⢠Remove tags only:
Parse the HTML using Jsoup, extract the content
enclosed by them and write it out, minus the tags that
are to be removed.
⢠Remove attributes only:
Only defined attribute in the tag to be removed. The tag
itself will remain within the content.
⢠Remove tags and content:
Parse the html, find the relevant tag and pull it and the
enclosed content out of the file.
t44u.2013
16
17. Case Study: W&L â HTML Cleaner â Properties File
⢠Sample Properties file to keep listed tags
and remove everything else
t44u.2013
17
18. Case Study: W&L â URL Redirect
Original URL captured
from import & used to
create Static or Regex
URL Rewrite
t44u.2013
18
19. Case Study: W&L â URL Redirect
Example ISS Static URL
Rewrite Mapping
t44u.2013
19
20. Case Study: W&L â URL Redirect â The Future âV8â
Beta Screen Grab for
V8 â URL Redirect
t44u.2013
20