You are viewing limited content. For full access, please sign in.

Question

Question

What Is The Best Way To Migrate Fields and Docs To Data Warehouse

Laserfiche
Updated March 25, 2015
asked on March 19, 2015

We need to migrate 5 fields and the documents to our data warehouse. What would be the best way to do this? Our current Laserfiche version is   9.0.2.728 using SQL server 2005, and our data warehouse is also SQL server.  We store the document key value i.e.  534522  in the database that is linked to the documents and want to retain that relationship when moved to the data warehouse.
 

0 0

Replies

replied on March 24, 2015

The direct DB integration, while possible, is not recommended for a variety of reasons.  The biggest reason is that the DB can and does have Schema changes with upgrades and this can break a direct DB integration.  Other reasons are related to security, caching, and sustainablity.

1 0
replied on March 23, 2015

Hello Gary,

 

I have a few questions before I can make any solid recommendations:

 

  • In what format do you need to import the data?  
  • Do you need to store the 6 values in one row in the database (Fields 1-5, and document key)?  
  • By document key, do you mean the Laserfiche assigned Entry ID, or some other document identifier that you have set up?

 

It sounds like this is definitely something that we can help you set up using our automation tool, Laserfiche Workflow, but before I can provide any instructions or suggestions, I'll need to better understand the process to make sure that we're covering all bases.  Feel free to respond to the questions above and leave any other information you feel may help us accurately assist you with setting up this new automated process!

0 0
View 2 previous replies
replied on March 24, 2015

Thank you for the reply. Below are answers to your questions.

  • In what format do you need to import the data?    CSV  format for the fields so it easily inserts into the database.  If we can only get one we could parse the field.
  • Do you need to store the 6 values in one row in the database (Fields 1-5, and document key)?  Yes- That would be great
  • By document key, do you mean the Laserfiche assigned Entry ID, or some other document identifier that you have set up? Yes -  That is in addition to the Laserfiche ID.  We have an case number associated to the documents and data that ties them together.

 

We don't have Workflow. Is there any other way to automate this using scripts in SQL maybe, or VB or bat? 

Once we get the initial load of data we will processes the data  once a week.

0 0
replied on March 24, 2015

Thanks, Gary!  I may have jumped the gun assuming that you had Workflow, as it comes standard with our latest offerings, Laserfiche Avante and Laserfiche Rio.  This is certainly a tougher task to crack without access to the power of automation that Workflow provides.

 

If you are familiar with SQL queries, I do believe that accomplishing this task should be possible using the metadata stored in the repository's database.  Please keep in mind that making any modifications to the Laserfiche database is a risky proposition.  If you're simply querying the database, you should be fine, but please take extra precaution to ensure that the database remains unmodified.

 

Database queries are not exactly in my wheelhouse, but after a small bit of research, I found this page on StackExchange that may be useful to you.  

 

Good luck!

 

0 0
replied on March 25, 2015

Using SQL will work for us thanks for the Link.  We understand that we would only read from the table.  Can you tell us what tables in laserfiche the data is stored in its hard to tell where the user data is stored and the keys. If we get the tables we can figure out the keys if you don’t have time to tell us.

 

Thanks a lot for your help…

0 0
replied on March 25, 2015

Hey Gary,

 

I'd check out the dbo.propval table in the repository's database.  This table contains the tocid (or entry ID), the prop_id (which relates to the table dbo.propdef table for reference), and the values within the field.  I'd check the propdef table to find the prop_id's (or fields) that you want to pull, and use a lookup to grab each of the values listed for Entry ID and metadata entries.

 

Hopefully this makes sense!  Just let me know if you'd like any more explanation!

0 0
replied on March 25, 2015

Thanks. I will try this.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...