我们可以自动迁移到SDL Tridion吗？ [英] Can we automate migrating to SDL Tridion?

问题描述

我们已经完成了从旧CMS到SDL Tridion的网站迁移。我们有成千上万的客户，其中不到五个被迁移。现在，我们需要自动迁移其余数千个客户端，显然我们不能使用手动方法。有没有办法使用它可能提供的任何API针对SDL开发自动化解决方案？如果是，我们在哪里可以找到API的文档？是否有相同的书籍或在线教程？

We are done migrating a website from old CMS to SDL Tridion. We have thousands of clients out of which fewer than five are migrated. Now let's say we need to automate migrating the rest of the thousands clients, obviously we can not use manual effort. Is there a way to develop automated solution against SDL using any APIs it may provide? If yes where can we find documentation for APIs? Any Books or online tutorials for the same?

推荐答案

无论采用哪种CMS，都可以根据如何衡量迁移的复杂性来衡量

Regardless of the CMS, the complexity of a migration can be measured based on how organized is your content in the system you want to migrate from.

我将迁移分为与源和目标有关的3种类型：

I categorize the migration into 3 types related to the Origin and Destination:

• 1-> CMS至CMS


• 2->数据库至CMS


• 3-> WebSite到CMS

如果原始源是数据库或其他CMS，通常会降低复杂度，因为内容是已经结构化。
您必须提取该内容，然后将现有内容与新系统中将具有的结构进行映射

If the original source is a database or another CMS typically the complexity is reduced, as the content is already structured. You have to extract that and map the existing content with the structure that will have in the new system

如果目标是将现有网站迁移到CMS与
在CMS中具有的内容相比，随着内容变得更加混乱，其复杂性也随之增加。
同样，如果网站中的内容结构正确，仍然可以实现自动化，但是大多数情况是旧网站
是手动维护的。
有一些商业工具可以从站点中爬网内容并应用模式来识别通用元素，通用内容，通用元数据，结构
并能够对原始内容进行处理并根据允许的规则应用逻辑来组织内容，但是即使是最好的工具，当源头杂乱无章时，
的工作也很难完成。
另外，我也看到了将最终的html分割成几部分并将其放入CMS的迁移。这是一种简单的方法，但当然是错误的方法，因为
您没有利用CMS

If the goal is migrate an existing website into a CMS the complexity increases as the content is more disorganized that having that in the CMS. Again, if the content in the site is properly structured is still possible to automate that, but most of the cases are old sites maintained manually. There are commercial tools that crawl the content from the sites and apply patterns to identify common elements, common content, common metadata, structure and are able to massage the original content and apply logic based on rules that allows to structure the content, however even the best tool has a hard work to do when the source is disorganized. Also I have seen migrations that cut the final html in pieces and put that in the CMS. That is an easy approach but of course a wrong one, as you are not taking any advantage of the CMS

，并且3种类型与我们迁移的源类型有关

And 3 Types related the source type we migrate from and the source type we want to obtain

• 1->内容到内容


• 2 ->（HTML +内容全部）成（HTML）+（内容）


• 3->（HTML +内容+全部代码）成（HTML）+（内容）+
  （代码）分隔

内容到内容的迁移不太复杂

Content to Content Migration is less complex

第二个选项当然更复杂，因为您必须将要成为模板的内容和HTML分开

Second option is of course more complex, as you have to Separate Content and HTML that will become templates

第三个选项甚至更复杂，就好像您正在提取页面的html（例如，像大多数商业工具一样使用http客户端），
并未捕获页面的逻辑。对于这种情况，您需要在文件级别进行操作

Third option is even more complex, as if you are extracting the html of the page (using an http client for instance as most of the commercial tools do), you are not capturing the logic of the page. For this case you need to work at the file level

在进入迁移之前，请尝试进行非常深入的分析，因为事情可能会变得复杂。
只有您对原始系统和要应用的扎实模式非常了解，才可以在自动化系统中思考

Try to do a very depth analysis before you enter in a migration, as things can turn complex. Only if you have a very good knowledge of the original system and solid patterns to apply you can think in an automation

这篇关于我们可以自动迁移到SDL Tridion吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！