We have exported data from an old Canon imageWARE system, both the scanned images and a .CSV file containing file paths and index data. How to import the columns from the CSV over to Fields in Laserfiche?
Hi Pat,
For something like this, you could use Excel's marco programming environment with the Laserfiche API. If there's an obvious link between each row of metadata and the related file to import, it's quite a simple task for someone with some basic programming skills.
One information is in Excel, I find it convenient to continue to use Excel for such things like small import runs and mass metadata updates.
-Ben
I realize this topic is a few years old, but I have an easier answer for you. First you need to save the CSV as a TXT, because otherwise laserfiche gets confused and tries to use Excel instead of extracting the text. There may be smarter ways to do that part of this.
Then run this workflow on it, this is a proof of concept, and not a real application.
The sneaky bit is the Pattern Match called Bust Up CSV into Multi Value Token.
It turns every line into a token, then you can apply metadata, send to data base tables, or whatever with a "For Each Value". Here's how I populated metadata fields:
ODBC connection to the csv, then you can use that like a data source query and extract the information from it.
To get started, there is a help page on administrating data sources:
which includes links to more about the query data activity and information on setting up ODBC.
The thing to remember about using the ODBC connection with Workflow is that the connection is single-use and Workflow is multi-threaded... So unless you're using Workflow for a one-time data-transfer, I wouldn't recommend using Workflow for this task. Also, you'll miss a lot of opportunity to log errors, so you'll have to be 100% certain of matching data. The SDK/API method has many benefits over using workflow.
Ben,
You are indeed correct, that is why I hope that with added functionality to the Simple Synchronization Sequence activity, we will be able to ensure 1 workflow is using a connection at a time
Kenneth,
The simple synchronization sequence only impacts locked documents when multiple workflow instances are trying to access the same document concurrently. It has nothing to do with data sources. Like Ben said, the SDK is a better solution here.