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

Question

Question

How find documents not under version control

Search and Retrieval
Updated February 8, 2019
asked on February 6, 2019

Hello,

I recently discovered some user folders were not under version control.  I wanted to get an idea of how many documents this may affect.  Is there any way to search for documents without version control enabled?  Meaning I want to find documents that have no version data - the ones where you see the option to start tracking versions.

My goal is to eventually place everything under version control.  My worry is that just generically applying the settings at the root level will bog our system done for too long for what may be only a few documents.  Thanks in advance!

 

0 0

Answer

SELECTED ANSWER
replied on February 8, 2019

I don't see there being an appreciable load on the Laserfiche or database servers. You probably won't even notice unless you are specifically looking at the Workflow subscriber. 50k entries isn't really that much in terms of bulk operations. However, in my experience, sometimes operations on large numbers of documents can cause the client to lock up. It'll be fine, but it'll look like it's unresponsive during some parts of the process.

The next-level solution is to write an SDK script. You'll still have the same load, but you can build in error handling, retry, and progress tracking to your hearts content. I wouldn't go there unless you experience issues with the client.

1 0

Replies

replied on February 7, 2019

I spent some time playing around with the Version search, and it makes it easy to find documents that have version history, but it doesn't seem to be a way to convince it to do the opposite.

You can run the following query against your repository database to find all of the documents that do not have a version history associated with them.

SELECT toc.tocid AS Tocid
FROM toc
WHERE ((
    SELECT COUNT(*)
    FROM vhist_toc
    WHERE vhist_toc.tocid = toc.tocid
    )) = 0

 

0 0
replied on February 7, 2019

Could you do something like setting up your search criteria, and then add the following to the custom search syntax box:

 

* - {LFVER:modified<"2/8/2019 12:00:00 AM"}

 

where the date is tomorrow?

0 0
replied on February 7, 2019 • Show version history

When I tested that, it seems to return results that don't have a version associated with them, but it also excludes documents that don't have a version.

It's a good thought, though.

One of the reasons why this is going to be difficult from the client is because until you enable versioning, the fields you'd want to look at simply don't exist in the database.

Maybe somebody will come along and prove me wrong. :D

0 0
replied on February 7, 2019

Came here to say the same, Devin.  In general, is there any advice on implementing version control (clicking the button on the root folder) when you will be initiating that on what is probably more than 50,000 entries?  Would this be better done from the server? off-hours?  Thanks for the help, everyone!

0 0
SELECTED ANSWER
replied on February 8, 2019

I don't see there being an appreciable load on the Laserfiche or database servers. You probably won't even notice unless you are specifically looking at the Workflow subscriber. 50k entries isn't really that much in terms of bulk operations. However, in my experience, sometimes operations on large numbers of documents can cause the client to lock up. It'll be fine, but it'll look like it's unresponsive during some parts of the process.

The next-level solution is to write an SDK script. You'll still have the same load, but you can build in error handling, retry, and progress tracking to your hearts content. I wouldn't go there unless you experience issues with the client.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...