Difference between revisions of "PT Import Content"

From ADF Docs
Jump to: navigation, search
(→‎Getting Started)
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[PT Import Content Installation|Installation]]
+
== Overview ==
−
[[PT Import Content Known Issues and Bugs|Known Issues and Bugs]]
+
The PT Import Content project allows CS Owners to easily import content via the Content Creation API.  The basic controls import subsites and page content into Formatted Text Blocks based on a formatted spread sheet.  Imported content for subsites and pages can also be re-imported and modified.
 +
 
 +
== Process Overview ==
 +
The import process:
 +
# Import Subsite content into the Subsite Mapping Custom Element
 +
# Process the records in the Subsite Mapping Custom Element [create subsites]
 +
# Import Page content into the Page Mapping Custom Element
 +
# Process the records in the Page Mapping Custom Element [create pages]
 +
# Identify documents in imported page content blocks and store in Document Mapping Custom Element.
 +
# Process the records in the Document Mapping Custom Element [upload documents]
 +
# Identify images in imported page content blocks and store in Image Mapping Custom Element.
 +
# Process the records in the Image Mapping Custom Element [upload images]
 +
# Fix Page links
 +
 
 +
== Getting Started ==
 +
Follow the installation steps to setup and configure the application in the new site.
 +
* [[PT Import Content Installation | Installation]]
 +
 
 +
The first step for the import is to identify the content that is being imported to the CommonSpot site.  There are two methods to accomplish this.  The application can be connected to an existing CommonSpot site database or populated to database tables.
 +
 
 +
The following Migration Configuration page will setup the source subsite and page data to be connected to a CommonSpot site database and then imported into the Subsite Mapping and Page Mapping custom elements.
 +
# [[PT_Import_Content_Migration_Confing|Migration Configuration]]
 +
 
 +
For content imports not from an existing CommonSpot site, the data will be imported (if necessary) into a database table and then imported into the Subsite Mapping and Page Mapping custom elements.
 +
Mapping Data:
 +
# [[PT_Import_Content_Subsite_Mapping_Confing|Subsite Mapping Configuration]]
 +
# [[PT_Import_Content_Page_Mapping_Confing|Page Mapping Configuration]]
 +
 
 +
== Process Overview ==
 +
The import process is divided into four main categories: subsites, pages, documents, and images.  These are menu items on the PT Import Content Dashboard page.
 +
 
 +
Each categories import processing works in two steps, mapping and building.  Mapping is the process of identifying the data for subsites, pages, documents, and images that will be imported to the new site.  This data is stored in mapping custom elements that can be modified through the dashboard in CommonSpot.  Once the mapping data is loaded into the mapping custom elements, the build process reads these data records and creates/updates the necessary subsites, pages, documents, or images.
 +
 
 +
The final step is a process to fix links for the import content pages.  This means updating links in imported text blocks that link to an import page, and fixing text blocks document and image links/URLs.  The fix links process dynamically builds the mapping data based on the pages, documents, and images imported. 
 +
 
 +
Outlined below are the steps and instructions for running each categories process to complete the import.
 +
* [[PT_Import_Content_Dashboard_Overview|Dashboard Overview]]
 +
* Subsite
 +
** [[PT_Import_Content_Subsite_Mappings|Mappings]]
 +
** [[PT_Import_Content_Subsite_Build|Build]]
 +
* Page
 +
** [[PT_Import_Content_Page_Mappings|Mappings]]
 +
** [[PT_Import_Content_Page_Build|Build]]
 +
* Documents
 +
** Mappings
 +
** Build
 +
* Images
 +
** Mappings
 +
** Build
 +
* Fix Links
 +
** Processing
 +
 
 +
== Components ==
 +
* [[PT Import Content ImportController | ImportController]]
 +
=== Subsite ===
 +
* [[PT Import Content SubsiteController | SubsiteController]]
 +
* [[PT Import Content SubsiteMapDAO | SubsiteMapDAO]]
 +
* [[PT Import Content SubsiteDAO | SubsiteDAO]]
 +
 
 +
=== Pages ===
 +
* [[PT Import Content PageController | PageController]]
 +
* [[PT Import Content PageMapDAO | PageMapDAO]]
 +
* [[PT Import Content PageDAO | PageDAO]]
 +
 
 +
 
 +
== Troubleshooting ==
 +
 
 +
== [[PT Import Content Known Issues and Bugs | Known Issues/Bugs]] ==
 +
 
 +
== Tasks ==
 +
* Delete pages needs CSSecurity integration
 +
* Delete Page and Subsite Mapping content needs CSSecurity integration
 +
* Update Page Mapping - set NeedsUpdate = 1 (to reprocess content)
 +
* Fix Links Method for PageController.cfc
 +
 
 +
 
 +
=== Reports ===
 +
* Pages Mapped
 +
* Subsites Mapped
 +
* Subsites Created
 +
* Subsites Needed to be Created
 +
* Pages Needed to be Updated
 +
 
 +
[[Category:PT Import Content]]

Latest revision as of 14:46, 27 May 2011

Overview

The PT Import Content project allows CS Owners to easily import content via the Content Creation API. The basic controls import subsites and page content into Formatted Text Blocks based on a formatted spread sheet. Imported content for subsites and pages can also be re-imported and modified.

Process Overview

The import process:

  1. Import Subsite content into the Subsite Mapping Custom Element
  2. Process the records in the Subsite Mapping Custom Element [create subsites]
  3. Import Page content into the Page Mapping Custom Element
  4. Process the records in the Page Mapping Custom Element [create pages]
  5. Identify documents in imported page content blocks and store in Document Mapping Custom Element.
  6. Process the records in the Document Mapping Custom Element [upload documents]
  7. Identify images in imported page content blocks and store in Image Mapping Custom Element.
  8. Process the records in the Image Mapping Custom Element [upload images]
  9. Fix Page links

Getting Started

Follow the installation steps to setup and configure the application in the new site.

The first step for the import is to identify the content that is being imported to the CommonSpot site. There are two methods to accomplish this. The application can be connected to an existing CommonSpot site database or populated to database tables.

The following Migration Configuration page will setup the source subsite and page data to be connected to a CommonSpot site database and then imported into the Subsite Mapping and Page Mapping custom elements.

  1. Migration Configuration

For content imports not from an existing CommonSpot site, the data will be imported (if necessary) into a database table and then imported into the Subsite Mapping and Page Mapping custom elements. Mapping Data:

  1. Subsite Mapping Configuration
  2. Page Mapping Configuration

Process Overview

The import process is divided into four main categories: subsites, pages, documents, and images. These are menu items on the PT Import Content Dashboard page.

Each categories import processing works in two steps, mapping and building. Mapping is the process of identifying the data for subsites, pages, documents, and images that will be imported to the new site. This data is stored in mapping custom elements that can be modified through the dashboard in CommonSpot. Once the mapping data is loaded into the mapping custom elements, the build process reads these data records and creates/updates the necessary subsites, pages, documents, or images.

The final step is a process to fix links for the import content pages. This means updating links in imported text blocks that link to an import page, and fixing text blocks document and image links/URLs. The fix links process dynamically builds the mapping data based on the pages, documents, and images imported.

Outlined below are the steps and instructions for running each categories process to complete the import.

Components

Subsite

Pages


Troubleshooting

Known Issues/Bugs

Tasks

  • Delete pages needs CSSecurity integration
  • Delete Page and Subsite Mapping content needs CSSecurity integration
  • Update Page Mapping - set NeedsUpdate = 1 (to reprocess content)
  • Fix Links Method for PageController.cfc


Reports

  • Pages Mapped
  • Subsites Mapped
  • Subsites Created
  • Subsites Needed to be Created
  • Pages Needed to be Updated
Retrieved from "http://community.paperthin.com/adf-docs/index.php?title=PT_Import_Content&oldid=4778"