Comma Separated Value (CSV)

Note:  No authentication connection is needed to set up CSV connectors, as it reads from the local filesystem. CSV cannot be used as an output connector nor a Content Service Connection.

Discovery Connection

Discovery makes mapping to and from your sources easier for data migration and ensures the data gets connected to the right fields. Discovery requires an Authentication Connection

  1. Select Schema Instance from the Navigation Menu or the Dashboard under Discovery

  2. Select the new connection button

  3. Enter a name for your Discovery Connection

  4. Select your connection type from the drop down

  5. Click save on the Create Connection form

  6. In the edit connection page fill out any addition fields and click save

Guide to Discovery Connections

Viewing the discovery schema instances will show you a table of all available Discovery Instances, this table can be sorted by Name, Type, and Collection.

Discovery Instance Fields

  • Name: Instance Name

  • Ignore Types: List of types to ignore, not used for CSV

  • CSV File Path: Full path to the CSV File.

  • CSV Type: If blank, the type on the fields will be csv file name with periods replaced with '_'

Field

Description

Name

Instance Name

Ignore Types

List of types to ignore, not used for CSV

CSV File Path

Full path to the CSV File

CSV Type

If blank, the type on the fields will be csv file name with periods replaced with '_'

Integration Connection

Every job requires an integration connection for both the source repository connection and the output connection. Also known as input an output connections. Their job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. . In repo mode, it will retrieve list items and all of their relevant metadata from a list or library on the specified site. In output mode, the connection will write content and assign the mapped content type (from type mappings), or simply leave the new list item as a Document. Click here for more information on setting up an integration connection.

  1. Select integration and click on the new connection button.

  2. Enter the name and description of your connection.

  3. Select the connection type from the drop down list.

  4. Click Save on the Create Connection form.

  5. Click Save on the Edit Connection page.

There are no fields to configure in an integration connection.

Guide toIntegration connections

The CSV (Comma Separated Values ) connection is an integration connector that can merge metadata stored in a csv file with external binaries from a filesystem. The binaries are optional depending on configuration.

Integration Connection Fields

  • Connection Name: This is a unique name given to the connector instance upon creation.

  • Description: A description of the connector to help identify it better.

Field

Description

Connection Name

This is a unique name given to the connector instance upon creation.

Description

A description of the connector to help identify it better.

Job Configuration

A 3Sixty Job is the process of moving or syncing content (including versions, ACL's, metadata) from one CMS (content management system) to another. Add tasks to your job to have better control over how your data gets migrated. Click here for details on how to set up an integration job.

Guide to Integration jobs

  1. Select List Jobs under integration on the navigation menu or the dashboard

  2. Click the create job button

  3. In the New Job form

    1. Name the job

    2. Select Simple Migration from the job type drop down

    3. Select the Repository Connection

    4. Select the Output connection

    5. Select your Content Service Connection

      (Only required if you will be using Federation)

    6. Click Save to open the Edit Job page

    7. Fill in the configurations for the Repo and Output Configuration tabs

  4. Click save to save your new integration job

  1. Select Run and Monitor Jobs under Integration in the navigation menu

  2. Click the play button next to the job you want to run

  3. Click the refresh button to view your completed job status

    (Larger jobs will take longer to run)

Repository Specification

Also known as an input connection. It's job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. When using this connector as a source repository filling out the following configuration fields will tell 3Sixty how to locate the files you want migrated.

All of these fields will appear in a Job Specification where the CSV connector is the repository.

CSV File Info

  • CSV File Path: Path to the CSV file

  • CSV Type: CSV Type. Will be prepended to all properties. If blank, the type will be the (filename)_csv

  • Separator Character: The character that separates each field value, also called a delimiter. Default is comma (,)

  • Escape Character: The value used to escape values such as slashes and quotes. Default is backslash (\)

  • Quote Character: The character used to denote fields. Default is double quotes (")

  • Document Type: Sets the base type for the migrated files to either documents or folders

  • Maximum number of rows: Including the header. Set to 0 or leave blank to read the entire csv

  • Check For Timestamp: Check if the created and modified dates are a 10 or 13 digit timestamp. Convert them to the configured format if present.

  • Fail on Missing Content: If including content, fail a document if the supplied file path from the row does not lead to the file content

Field

Description

CSV File Path

Path to the CSV file

CSV Type

CSV Type. Will be prepended to all properties. If blank, the type will be the (filename)_csv

Separator Character

The character that separates each field value, also called a delimiter. Default is comma (,)

Escape Character

The value used to escape values such as slashes and quotes. Default is backslash (\)

Quote Character

The character used to denote fields. Default is double quotes (")

Document Type

Sets the base type for the migrated files to either documents or folders

Maximum number of rows

Including the header. Set to 0 or leave blank to read the entire csv

Check For Timestamp

Check if the created and modified dates are a 10 or 13 digit timestamp. Convert them to the configured format if present.

Fail on Missing Content

If including content, fail a document if the supplied file path from the row does not lead to the file content

File Field Mapping

  • Path Field: The header under which file paths are stored

  • Path Includes Files: If checked, 3Sixty will extract the filename from the value found in the Path Field. Only checked if Path Field is populated

  • File Field: The header under which file names are stored

  • Id Field: Field which contains the source document Id. If blank, the id will be (csvfilepath):(row)

  • Created Date Field: The field that stores the date the file was created

  • File Length Field: The field that stores the file length

  • Modified Date Field: The field that stores the date the file was modified

  • Path to Files: If set, the connector will prepend this to the file path and search for a file at that location. Include Binaries must also be checked

Field

Description

Path Field

The header under which file paths are stored

Path Includes Files

If checked, 3Sixty will extract the filename from the value found in the Path Field. Only checked if Path Field is populated

File Field

The header under which file names are stored

Id Field

Field which contains the source document Id. If blank, the id will be (csvfilepath):(row)

Created Date Field

The field that stores the date the file was created

File Length Field

The field that stores the file length

Modified Date Field

The field that stores the date the file was modified

Path to Files

If set, the connector will prepend this to the file path and search for a file at that location. Include Binaries must also be checked

Mapping

3Sixty Mapping gives you the ability to map your content types and metadata from one system to another.

There are two places in 3Sixty where you can set up mappings:

  • At the top of the mapping tab you can select from saved mappings

  • Creating a unique mapping based on your connectors.

Guide to 3Sixty Mapping

Tasks

Job tasks also known as processors provide a processing pipeline for documents and metadata. Post processors can also be added as a task to run after the files are processed.

Click here for a list of all the tasks you can add to your integration job.

  1. Click on the task tab in your integration job.

  2. Find the task you want to create in the drop down. Tasks are grouped by type. You can also search for the task by name.

  3. Select the create task button

  4. Fill out the configuration fields. Some tasks do not require configuration.

  5. Click Done to save the task to your job.

Looking to integrate with CSV data? We can help.