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

Question

Question

How to count the number of pages

asked on April 27, 2017 Show version history

Hi,

 

I'm looking at ways to count the number of pages added to each volume or folder within our LF repository in a given month.  It would be great if this could be run in WF and set to a schedule so it doesn't need to be manually run each month. 

Any ideas how I could achieve this?  Would also be great to pull the file name, and meta data and page count for each new document added in the month.

 

Thanks,

Anthony 

0 0

Replies

replied on April 27, 2017 Show version history

Create a monthly scheduled workflow with a custom sql query, email yourself the results.

SELECT SUM(pagecount) as pages
  FROM [Your_Repository].[dbo].[toc]
  where created>@monthago

 

1 0
replied on April 27, 2017

Was so simple! My bad!

Great job

0 0
replied on April 28, 2017

Hi,

Thanks for that.  

How would I pull the volume name and meta data (with number of keystrokes) for each newly created document that month?

 

So my email would have:

 

Volume Name: XYZ

New Pages: 1234

Number of Keystrokes: 1234

 

Anthony

 

0 0
replied on April 28, 2017

SQL isn't my strong point, there is probably a more elegant way to do this.

I would run the query once for each volume, see updated query below, and return those tokens in the email.

SELECT SUM(pagecount) as pages
  FROM [Your_Repository].[dbo].[toc]
  where created>@datetoken and vol_id=@volumeidtoken

As for keystrokes, I am not sure what that means to you.

0 0
replied on April 28, 2017

Thanks for this.

I have been looking at this and can't see where I can repeat through each volume in my LF repository?  I have looked through WF and can't see it.  Where is VOLUMEID pulled from within WF?

 

I still need to look at counting the Keystrokes from the meta data... any suggestions?

Anthony

0 0
replied on April 28, 2017

I steered you wrong with volume ids because your rollover volumes will have unique IDs.  I'm still trying to think of how best to do the query to get volume names.

I still don't understand what you're looking for "keystrokes?"  Is that total number of characters in the metadata for all the documents created in the last month?

0 0
replied on April 28, 2017 Show version history

You'd want to go off the Audit Trail database rather than the repository one since you only care about what changed within a given time frame. Querying against the toc table would give you all documents added in that time but not pages added to existing documents.

You can query against the all_events view in Audit Trail. The event types are documented.

Like Eric says, it's not clear to me either what you mean by keystrokes? If it's the total number of characters, then would you expect to count picking values from list as one "keystroke" or the full length of the value? Same thing with pressing the space bar in a date field to get today's value.

And out of curiosity, why does the number of keystrokes matter?

1 0
replied on April 28, 2017

Hi,

 

Does it matter that we don't have the Audit Trail module?  

Our department charges teams 'per keystroke' for having us catalogue and index scanned files being added into their volume.

So a file with metadata:

Name: John Smith (10 Keystrokes)

Date: 01/01/2017 (10 Keystrokes)

Would have a total of 20 keystrokes (including spaces)

 

We scan using a different software provider, and use Auto Import to import images into LF, so List and Dates are all entered manually (so are counted as full not single keystrokes).

Hope this makes sense.

Anthony

0 0
replied on April 28, 2017

The repository's SQL database reflects the current state, not how it got there. Audit Trail is the historical data of what happened over a given period of time.

So, for example, you can tell there is a document created in, say, January and it has 5 pages in the repository, but you need Audit Trail to see if the pages were all added at creation time or over the last 4 months.

Now, if you don't modify documents to add pages after their initial creation, you can get the page count from the repository. But if you need to know how many pages were added to existing documents, then you would need Audit Trail or you might end up double-counting some of them if you only look at the repository.

Similarly, for field data, if it gets set once and never modified, you can get the keystroke count from the repository. But if fields get added in multiple sessions, you'd need Audit Trail to figure out which value you should be counting for what month.

0 0
replied on April 28, 2017

Hi Miruna,

Thanks for your reply.  Most of our documents are added once and don't then get added to over time, however, saying that, I'm sure there would be one time that a page is added to a document at some point - but I will have to work round that.

Are you able to assist with the correct method in which I can get this information pulled using WF (running at the end of each month)?  

Let's say that all documents are created and never added to (which is more likely than not), with their metadata being created at the same time, so going off the Repository Database seems the likely way forward. 

How would I loop through each volume (and roll over volume) and list the total created document/pages added in a given month along with the total keystrokes for each document in this range and then add that information to an email?

Anthony

0 0
replied on April 27, 2017 Show version history

Hi Anthony,

 

I dont know how to do using workflow, but I can give you my solution to know how many document or folder you have in each volume.

 

Under Laserfiche Client, select "Search" on your left panel, then select "Custom Search" and check "Name" and "In the volume".

 

Then, select your "volume", check "Folder" then click "search".

 

 

At the end of your "search" you will have the result's number (in my volume I have 37 folders)

 

 

You can do same with "document".

0 0
replied on December 31, 2017

Hi,

I have been looking into Audit Trail Starter.  Am I correct in believing that I will be able to track the page counts of new documents being added to my repository (either by LF scanning or Import Agent) regardless whether the document was newly created or just updated?

I currently get page counts from the Repository database, but as you are aware, it only returns documents which were created and does not show number of pages which were “added” to a document.

Does audit trail track pages additions via Inport Agent, or do they have to be added by LF scanning?

Thanks,

Anthony 

0 0
replied on January 3, 2018

Audit Trail tracks all page creation, regardless of where they came from.

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

Sign in to reply to this post.