3 Tips Successful Ektron Drupal Conversion
•Descargar como PPTX, PDF•
0 recomendaciones•763 vistas
With its recent acquisition, many Ektron CMS users are making the switch to Drupal because of the many advantages the platform has to offer. There are several important things that are helpful to know, however, as you make the switch from Ektron to Drupal. Whether you are doing a redesign and only migrating content, or replatforming an existing site, knowing the ins and outs of Ektron will help your project go more smoothly. Join us in this upcoming tech talk to learn: Best practices for content migration from Ektron to Drupal using XLIFF How get the most out of Ektron templates when converting your design to Drupal What you can do to preserve an environment similar to Ektron’s eSync for your new Drupal site
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (10)
Destacado
Destacado (20)
Similar a 3 Tips Successful Ektron Drupal Conversion
Similar a 3 Tips Successful Ektron Drupal Conversion (20)
Más de Acquia
Más de Acquia (20)
Último
Último (20)
3 Tips Successful Ektron Drupal Conversion
- 1. 1 ©2017 Acquia Inc. — Confidential and Proprietary Greg Kihlström, CEO, Carousel30 @carousel30 Brian Browning, SVP, Ameex Technologies Inc. 3 Tips to a Successful Ektron to Drupal Conversion
- 2. 2 ©2017 Acquia Inc. — Confidential and Proprietary Introduction – Since January 2015 when Ektron and Episerver were combined into a single company and CMS platform, many organizations have been making the choice to move their website to a different platform – Drupal has been a natural fit given its extensive feature set, flexibility, and open source community
- 3. 3 ©2017 Acquia Inc. — Confidential and Proprietary Introduction Content strategy is an important part of an website migration: – What content will be rewritten? – What content will be reorganized? – What content will be migrated?
- 4. 4 ©2017 Acquia Inc. — Confidential and Proprietary Content Migration – Definition of Content Migration – Manual Migration – Ektron XLIFF File Migration – Custom ETL Migration
- 5. 5 ©2017 Acquia Inc. — Confidential and Proprietary What is content migration? – Always a major part of any website conversion or migration – Can require multiple approaches depending on the complexity of your needs – Structured and unstructured content require different approaches – As-is migration – Examples: Press releases, existing documents
- 6. 6 ©2017 Acquia Inc. — Confidential and Proprietary Methods of content migration 1. Manual migration – Simplest technically speaking, but can be the most time-consuming 2. Exporting an XLIFF (XML) file 3. A custom ETL process – Most complex of the three, requiring custom coding
- 7. 7 ©2017 Acquia Inc. — Confidential and Proprietary Method 1: Manual Migration
- 8. 8 ©2017 Acquia Inc. — Confidential and Proprietary Manual Content Migration – Easiest method, but most time-consuming – Difficulty ranges depending on the amount of: – Existing HTML/CSS styles – Requirement to restyle new content (vs. having more structured data fields) – Can range from 4-8 pages/hour to more for more complicated content
- 9. 9 ©2017 Acquia Inc. — Confidential and Proprietary Manual Content Migration – Stay organized: – Track all existing URLs in a spreadsheet to use as a “map” – For new content: – Create “content outlines” that allow you to create fields for each type of structured data – Think of it as a map of your content types in a Word doc that’s easy for content writers to use
- 10. 10 ©2017 Acquia Inc. — Confidential and Proprietary Manual Content Migration – Make sure Drupal is set up correctly: – Match Drupal to your content outlines – Clearly define what types of content will receive which styles if manual styling (H1 tags, etc.) is required – Try to limit manual migration where possible
- 11. 11 ©2017 Acquia Inc. — Confidential and Proprietary Method 2: XLIFF File Migration
- 12. 12 ©2017 Acquia Inc. — Confidential and Proprietary XLIFF File Migration – XLIFF – Ektron’s localization feature to get the content we need. – XLIFF: XML Localisation Interchange File Format) – Files are available through the language export feature, Available even if the site is in a single language
- 13. 13 ©2017 Acquia Inc. — Confidential and Proprietary XLIFF File Migration – XLIFF files include all content, menus and taxonomy. – The trick is understanding the files and what to do with them. – While it doesn’t include everything, it does include: – Published status – Page URL – Meta Information – Page Title – Page Text Content
- 14. 14 ©2017 Acquia Inc. — Confidential and Proprietary XLIFF File Migration – For several reasons, the format will not tell you where the page exists in the site structure – We recommended exporting in logical groups. – Think in terms of creating sets of XLIFF files that are of the same content type, or in the same section. – We will call these “migration sets.”
- 15. 15 ©2017 Acquia Inc. — Confidential and Proprietary XLIFF File Migration – Before we explore the concept of migration sets a little bit further, let’s take a look at some of the <body> information of an XLIFF file:
- 16. 16 ©2017 Acquia Inc. — Confidential and Proprietary XLIFF File Migration – Similar to the previous code snippet, you can see a properly XML-formatted document that, in this case shows the meta information.
- 17. 17 ©2017 Acquia Inc. — Confidential and Proprietary XLIFF File Migration Migration Sets – Import individual sets of XLIFF files – Modify content types to include “migration set” field
- 18. 18 ©2017 Acquia Inc. — Confidential and Proprietary XLIFF File Migration – Display migration data while viewing page as admin
- 19. 19 ©2017 Acquia Inc. — Confidential and Proprietary XLIFF File Migration – Editing a page can show even more detail to an administrator/content editor:
- 20. 20 ©2017 Acquia Inc. — Confidential and Proprietary Method 3: Custom ETL Migration
- 21. 21 ©2017 Acquia Inc. — Confidential and Proprietary Custom Automated ETL Migration – The third method of content migration is the most complex of the three – Offers a single, comprehensive solution that matches all needs – The customer automated approach uses technology to conduct an ETL process: – Extract – Transform – Load
- 22. 22 ©2017 Acquia Inc. — Confidential and Proprietary Custom Automated ETL Migration – How Does It Work? – Scripts extract content from the source database – Moves content to the Transform database – Once in the Transform database, content is: – Scrubbed, or parsed, to remove things like inline styles or broken HTML – Styles are applied as appropriate – Crosslinks are updated
- 23. 23 ©2017 Acquia Inc. — Confidential and Proprietary Custom Automated ETL Migration – The role of Data Mapping – Because content lives in different locations from the old site to the new, we must map content locations from the old to the new – Content is mapped, along with assets (files, media, etc) – Source and Destination URLs are generated and mapped – Taxonomies, Menus and other Related Content is mapped – Load into the Destination Site Database – Use the Drupal API to automate the loading of the transformed content – Assigns content through modules as needed
- 24. 24 ©2017 Acquia Inc. — Confidential and Proprietary Custom Automated ETL Migration – Exception Handling – It often takes multiple runs of the content migration scripts to complete the entire process – Why? Most source content isn’t consistent – As successive runs of the migration scripts are conducted, content that doesn’t follow normal rules is identified – Migration scripts are updated to accommodate variations in source content – We term this approach the “Multiple Pass Method”
- 25. 25 ©2017 Acquia Inc. — Confidential and Proprietary Custom Automated ETL Migration – Benefits of the Multiple Pass Method – Once the scripts have been developed, and exceptions handled, the same script can be run over and over – Baseline migration moves 100% of all content – Delta migration(s) move the 10% - 25% of content that changes during testing, training and related activities prior to launch – Using this approach, we can avoid lengthy content freezes – No need to force authors to stop editing content since we can simply run the same scripts to migrate updated content – This is especially important when considering specialized content, like user-generated or social content
- 26. 26 ©2017 Acquia Inc. — Confidential and Proprietary Conclusion
- 27. 27 ©2017 Acquia Inc. — Confidential and Proprietary Recap – Almost any content migration will require more than a single method – Each method has its own benefits and cases where it works best – Planning ahead will save time and missteps – Document the steps required and make sure to prepare plenty of specific direction that may be required for manual formatting of content
- 28. 28 ©2017 Acquia Inc. — Confidential and Proprietary Questions?
- 29. 29 ©2017 Acquia Inc. — Confidential and Proprietary Thank You
Notas del editor
- Acquia's official PPT template begins here. This is the standard presentation title slide.
- This is the standard content slide.
- This is the standard content slide.
- This is the alternate content slide.
- An important consideration to keep in mind is that most sites have a combination of structured and unstructured content. Structured content follows a similar, familiar pattern, like a press release or a product page in an e-commerce catalog. These kinds of content items lend themselves very well to automation because they follow a predictable pattern. Unstructured content typically takes the form of basic web page content authored in HTML, for the most part. Many customer web sites contain content of both types – in these cases, it is extremely important to develop a comprehensive plan to address each kind of unique content structure. Even if you plan on rewriting major pages of your site, there are many types of content which generally do not get modified or rewritten when converting or migrating a site, such as blog posts press releases, and supporting content or documents. In these cases, you need a good way to get content “as is” into your new system.
- There are a few different ways to approach this, including the following: Let’s discuss each so you can see which approach(es) make the most sense for you. In many cases you will most likely want to use different methods for different types of content.
- This is the alternate content slide.
- The first method we’ll discuss is by far the easiest technically, though in most cases (for anything but small websites), is time-prohibitive to use as the sole method. While it is often true that even if you automate most of your content migration, you are going to need to manually migrate at least some of it. Manual content migration is very much what the term implies: a team of humans, copying and pasting content, reformatting styles, moving images and files and re-linking content pages to one another. It’s tedious, but necessary, work and is best done by people with basic levels of HTML and CSS skill, as oftentimes, part of the migration requires removing <FONT> tags and replacing them with CSS styles. Experienced manual content migrators can average as much as 4-8 pages of primarily text content per hour if the pages are relatively simple to construct and the amount of linking is at a minimum. More complex pages can take longer to complete.
- While every organization may have a slightly different way of approaching a manual content migration, the best approach by far is the most organized one. We suggest creating a map of some kind from existing URLs in a spreadsheet to track progress and ensure that any structural changes needed will be accounted for. For instance, if the old “our team” page used to live in the “about” section, but now will live in a new section when migrated, a spreadsheet can be used to track things like this. For brand new content that will be manually entered, it is often helpful to create a “content outline” or a document that maps each field in the Drupal content type to the text/image content provided.
- This goes for all of the migration methods we’ll discuss: it’s imperative that the new Drupal CMS and its corresponding content types are set up correctly from the start before you begin manual content migration. Especially when multiple team members are involved, it’s important to clearly outline where and how content will be entered. Make sure to articulate when various header tags (H1, H2, etc.) will need to be manually formatted vs. handled within the CMS. Finally, you should be careful about how much manual content entry you are requiring during your website migration from Ektron to Drupal. Next, we’ll explore 2 methods that automate content entry and speed up conversion of large sites.
- This is the alternate content slide.
- The second method of content migration we’ll discuss utilizes Ektron’s localization feature to get the content we need. Using the XLIFF (XML Localisation Interchange File Format) files available through the language export feature, you are able to access and export the current content of your site, even if you only have content in a single language and do not technically have a multilingual site. Through a little manipulation, this makes the content migration process relatively straightforward, especially into a CMS like Drupal.
- This is the standard content slide.
- This is the standard content slide.
- As you can see, this is pretty standard XML formatting, which helps legibility. Also, each content area (Title, HTML, Teaser) are clearly labeled to make it easy to understand how to best map the content to an area in your Drupal CMS. This helps in identifying where the pages should go.
- When importing the sets of XLIFF files, you will then migrate each in a distinct set so that you can separate content types, sections or use other methods to categorize the imported content.
- We’ve also made it easy to see the origin of each imported page by adding an admin-only view that shows the migration source when viewing each page while logged in (Figure 2). This even includes the original Ektron ID.
- Note also that we added a “QA Status” field to each content type which also made our review process much easier, especially when review is spread over a large team.
- This is the alternate content slide.
- The third method of content migration is the most complex of the three, because it will involve writing the most custom code. The customer automated approach uses technology to conduct an Extract, Transform and Load (ETL) process.
- A series of scripts is developed by programmers to extract content from the source database and temporarily move it to a database, sometimes referred to as a Transform database. It’s not usually possible to simply pull content out of the old CMS and directly insert it into the new CMS for a number of reasons. First, most content must be scrubbed, or parsed, to remove things like inline styles or malformed HTML. In some cases, HTML and other DTDs are enforced against the Transform database to ensure that the HTML that will be loaded into the new site is properly structured and will render correctly.
- In addition, the structure of the information of the source web site often won’t match the same structure in the new site – this is especially the case in redesign projects that include content migration. To accommodate this need, the ETL scripts follow a data mapping process that maps source content into the destination location. This mapping is taken into consideration before it can be loaded into the new CMS. With the Transform steps completed, the next step is to load the content using the Drupal API where the scripts take the re-formatted HTML code and automatically loads it into the CMS in the appropriate location.
- While automated methods are incredibly valuable as they are able to quickly complete the physical movement of the content, it often takes multiple runs of the content migration scripts to complete the entire process. One of the main reasons for this is that source content is rarely the same across the site and oftentimes, content that can be easily migrated from one section of the site has different problems when you go to migrate other sections of the site. For example, the first run of the migration scripts may work with a 75% - 80% accuracy state, but inevitably, there will be a number of exception rules that must be included into the core automation scripts. These exceptions essentially address the one-off sections or pages that contain different rules for how they are migrated.
- There are benefits to this multiple pass approach, however. Chief among them is the fact that once major exceptions have been identified and mitigated, the same script can be used to perform a master migration that contains the bulk of the content for the site. To avoid lengthy content freezes, the same script can be run again, this time only picking up newly changed or authored content, effectively delivering a delta content migration, reducing downtime and allowing for fast-changing content to be included in the automated approach. This is especially important when considering specialized content, like user-generated or social content that can’t have any kind of real downtime.
- This is the alternate content slide.
- This is the alternate content slide.
- This is the standard presentation ending slide.