1,126
edits
Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"
Jump to navigation
Jump to search
Migrating From Filenet to Content Manager OnDemand (view source)
Revision as of 11:45, 6 September 2015
, 11:45, 6 September 2015Initial edit on ingestion.
m (New section on ingestion.) |
(Initial edit on ingestion.) |
||
| Line 53: | Line 53: | ||
== Consider how you'll ingest the data == | == Consider how you'll ingest the data == | ||
You'll want to make sure that during the export process that you consider the information you'll need to get the exported data into Content Manager OnDemand. | |||
=== Provide report names === | |||
In order to get specific reports into OnDemand, you need to provide the name of an report (likely as an Application). Make life easier for yourself by including the name of the report in the file names you output. | |||
=== Group reports in chronological order === | |||
Due to the way table segmentation works in OnDemand, you'll want to load the data in chronological order. When you name files, consider including a date field in YYYY-MM-DD format, so it can be sorted numerically at load time. | |||
=== Concatenate Reports === | |||
Concatenating reports together means fewer loads (and less overhead, as each load can represent up to 10k in metadata). It also means you'll get better compression for storage. | |||
== Order of Operations == | == Order of Operations == | ||