Cloud Connected

Thoughts and Ideas from the Gitana Development Team



Bulk Import

Jun 12

Why is there a need for Bulk Import for existing content into a CMS? Content is extremely valuable and expensive to recreate. It’s too valuable to lose and recreating it manually can be a daunting prospect. Your existing content is an important concern at the start of any CMS project – how to migrate content and the related costs is a very important consideration.

If there is content that does need to be imported into the CMS then you will need to have a robust repeatable automated process such that:

  1. content can be reused
  2. the quality of the content is maintained
  3. and additional migration costs are not incurred.

The need for Bulk Import

  1. One-time “bulk import”, eg. Initial Content Import. Quite often you’ll have a lot of your content in a digital format at the beginning of your project, and, depending on how much there is, this content can be time consuming to enter.

  2. “Incremental Import” scenarios. Regular updates from external systems: it would be nice if all content was ‘happily’ in one internal system and only managed in one place. Unfortunately this ideal world doesn’t always exist: typically, CMS initiatives are in phases – one project at a time, or 3rd party content, eg. external product updates. This means that at times some content is managed externally and will need to be imported or updated at regular intervals.

The Cloud CMS solution:

Cloud CMS provides a command line tool (https://www.cloudcms.com/documentation/api/content-services/bulk-import) that you can use to bulk import data into your content repository branches. This allows you to migrate existing data into Cloud CMS within a single transaction – everything goes in or nothing goes in (transactional).

This process is intended to support one-time “bulk import” scenarios as well as “incremental load” scenarios.

The bulk import mechanism allows you to programmatically enter your pre-existing content, saving time and reducing the errors that can happen when doing repetitive content entry.

Features:

  • Bulk import does suggest large numbers of records to be imported. We have tested the Cloud CMS Bulk Import process with hundreds of thousands of records. It worked well and fairly quickly. If you have a large content import then please contact us to discuss or assist.
  • Transactional: if one record fails to import then will rollback
  • As long as the content in the import file has a structured format then it can be imported
  • Can import into related content types
  • Can define and create the Content Type in the import
  • If a content record exists in Cloud CMS, will overwrite the content record in Cloud CMS

Any questions?

I hope this article encourages you to further explore the many features of Cloud CMS. If you have a question, or cannot find a feature you are looking for, or have a suggestion - please Contact Us.