Skip to main content

Import Custom Database Data with Content Intake in DocuShare 8.1

Updated
Audience:  DocuShare administrators

Import Custom Database Data with Content Intake in DocuShare 8.1

Overview

New in DocuShare 8.1: DocuShare adds reusable Transformation Profiles for mapping incoming CSV columns to columns in an existing Custom Database table, plus automated ingestion that can monitor directories and process files. These capabilities help keep lookup data synchronized without manually uploading each file.

The Custom Database table must exist before you configure a profile. For table setup and manual CSV updates, see Create and Manage Custom Database Tables in DocuShare.

Before You Begin

  • Confirm that the destination Custom Database table exists and that its columns have the required data types.
  • Prepare a sample CSV and identify how each source column maps to a destination column.
  • Confirm that Content Intake is available and that you can configure its sockets and Transformation Profiles.
  • Decide how incoming rows should be applied. DocuShare 8.1 release information lists append, update-or-append, and replace-all strategies.

Configure a Transformation Profile

1. Open Admin > Services and Components > Content Intake > Transformation Profiles.

2. Create a profile for the destination Custom Database table.

3. Map incoming CSV source columns to their corresponding destination table columns.

4. Select the appropriate data-loading strategy exposed by your profile configuration and save the profile. The 8.1 release notes list append, update-or-append, and replace-all strategies.

Use a test file first to confirm that the source headers, mapped columns, and row values produce the expected table data.

Connect the Profile to Automated Ingestion

1. Open Admin > Services and Components > Content Intake > Configuration.

2. Configure or edit a Content Intake socket to watch the directory where incoming CSV files will be placed.

3. Associate the socket with the Transformation Profile, then save the configuration.

4. Place a test CSV in the watched directory and review the processing notifications, reporting, or optional results files available for audit and troubleshooting.

CSV is the supported format for automated ingestion. JSON can be included inside CSV fields when populating ItemsTable properties; this does not make a standalone JSON file an ingestion input.

Choose a Loading Strategy Carefully

  • Append adds incoming rows to the table.
  • Update-or-append updates matching data or adds new rows, according to the configured mapping behavior.
  • Replace-all removes the existing table rows and loads the incoming data in their place.

Use replace-all only when the incoming file is intended to be the complete new contents of the table. Keep a recoverable copy of the source data before running a replacement.

Troubleshooting

  • If no rows are imported, confirm the socket's watched directory, profile association, and CSV file format.
  • If values appear in the wrong columns, review the source-to-destination mappings and test with a small CSV.
  • If processing fails, review the Content Intake processing status and available results or logs. Correct the input or mapping before resubmitting the file.