We have an upcoming project to move ~600,000 Laserfiche documents into Box (box.com). Has anyone done this - mass-transferred documents and metadata to Box? Any suggestions or tips to make this process as efficient as possible?
Thanks,
Geoff
We have an upcoming project to move ~600,000 Laserfiche documents into Box (box.com). Has anyone done this - mass-transferred documents and metadata to Box? Any suggestions or tips to make this process as efficient as possible?
Thanks,
Geoff
Just a final follow-up...
I ended up using the SDK to write an app to do the export. As we were working through the requirements I started getting requests like this:
"Can we update the document name to include some of the metadata?"
"Can we reformat the multi-value field metadata during the export?"
"Can we store the reformatted metadata in a DB so we can use it during the Box import?"
That sort of export functionality is only possible if you have full control over the process, so the SDK/custom app route was the answer for us.
I've recently completed a large data export project and there a couple of methods to go about this. The easiest solution is to export as a briefcase . It will all depend on how you are going to go about reassociating the metadata with each file in Box.
Thanks for the briefcase idea. Having a problem getting 7-Zip to open the tar file within the .gz with a renamed briefcase file exported using LF Client 10.1.1.254. Does that method still work?
I wasn't able to get 7z to work either. Winzip worked for me
Thanks, I'll give that a try.
OK, got the briefcase to open. One of the requirements for the document move is to have all docs end up as searchable PDFs in Box. I notice when I export TIFFs using the briefcase, they stay TIFFs, vs exporting using the client Export functionality, which automatically turns the TIFFs into searchable PDFs. Obviously I don't get metadata using the Export button, so it looks like neither method gives me exactly what I need. Would the SDK allow me to export all docs as searchable PDFs with metadata (in whatever form I choose to write it) to match the doc?
In that case, export the files as PDFS. Then have the columns as metadata in the client and export as 'list contents'. This will give you a csv file containing the metadata for each file.
OK, thanks. I'll take a look at processing the export that way.
Just a final follow-up...
I ended up using the SDK to write an app to do the export. As we were working through the requirements I started getting requests like this:
"Can we update the document name to include some of the metadata?"
"Can we reformat the multi-value field metadata during the export?"
"Can we store the reformatted metadata in a DB so we can use it during the Box import?"
That sort of export functionality is only possible if you have full control over the process, so the SDK/custom app route was the answer for us.