IMPORTANT ANNOUNCEMENT

These forums were permanently set to read-only mode on July 20, 2022. From that day onwards, no new posting or comment is allowed on the site, but the historical content remains intact and searchable.

A new location for posting questions about PlanetPress Suite is now available:

OL Learn - PlanetPress Classic (opens in new tab)

Topic Options
#45984 - 12/24/13 05:21 AM Document Metadata stored with Capture Documents
Anees Offline
OL Newbie

Registered: 07/14/13
Posts: 22
Loc: Kuwait
It would be very helpful if the document metadata created at the time of "Create Capture Fields" is stored and made available in the PGC Input process along with "Get Capture Document".

With this, we will be able to use the original metadata for routing the PDF output in to Document Management Systems (Like SharePoint) instead of having to re-create it or use an external metadata file management option (Save & Load) which tends to be expensive on the storage (1 MB Per .meta file).

The whole point of using capture with Anoto Digital Pen is to enable paper to digital transition. This feature would add endless value to the objective.

Top
#45987 - 12/24/13 07:44 AM Re: Document Metadata stored with Capture Documents [Re: Anees]
Philippe F. Offline
OL Expert

Registered: 09/06/00
Posts: 1984
Loc: Objectif Lune, Montreal, Qc
Anees,

I'm not sure how "storing the document's metadata" could be any less expensive on storage than using the Save/Load options... which store the document's metadata!

Could you expand on your idea?
_________________________
Technical Product Manager
I don't want to achieve immortality through my work; I want to achieve immortality through not dying - Woody Allen

Top
#45988 - 12/24/13 07:53 AM Re: Document Metadata stored with Capture Documents [Re: Anees]
Philippe F. Offline
OL Expert

Registered: 09/06/00
Posts: 1984
Loc: Objectif Lune, Montreal, Qc
Anees,

Sorry, I just read your thread in another Forum which expands on this. I think I understand what you mean.

Note that the metadata used to generate the original document should not be used along with the PDF retrieved with the Get Capture Document task: they may not match at all!
The original metadata was created from the original data stream, which could be TXT, CSV, XML, etc. That original data stream could have generated several physical pages for each Data Page in the data. It would be very risky for PlanetPress Capture to assume that the original metadata is a one-to-one match with the PDF generated from the Get Capture Document. Actually, in most cases, it won't match.

That's why the option has to be implemented manually (like you did) if you know for sure that the original metadata and the resulting PDF will match.
_________________________
Technical Product Manager
I don't want to achieve immortality through my work; I want to achieve immortality through not dying - Woody Allen

Top
#45994 - 12/24/13 10:38 AM Re: Document Metadata stored with Capture Documents [Re: Philippe F.]
Anees Offline
OL Newbie

Registered: 07/14/13
Posts: 22
Loc: Kuwait
Hello Philippe,
Thanks for your response. I fully agree with you in the event of a bulk print transaction where a single job could consist of multiple documents. My use for PlanetPress is on an adhoc level with each job being 1 document.

Perhaps I should explain the use case. I am using PP to receive print files (.dat) from ADP Autoline (also known as kerridge) which is a automotive distribution management system. Each file could be printed and/or sent to SharePoint as PDF with metadata.

Every job submitted by Autoline is an individual document and the metadata remains the same Pre and Post PGC. As a matter of fact, some data received in .dat is not required to be printed as they are only needed for creating document metadata for storing in SharePoint. In this case, I am forced to print those data points so that they are present on the document and PDF for me to read again using regionline from PDF to create the metadata.

I must admit that the current workaround employed is functioning pretty well. The only short side is the need for extensive documentation required and the frustration of explaining the workaround which is quiet complex to the team. crazy

I still hope OL will consider this a request with a certain type of users and add it to your future releases. I will be happy to elaborate or send you samples of my PP Watch configuration for your evaluation.

Top