Batch to change metatags

[Anonymous]

I plan to use the program in a workflow process. Incomming invoices will be scanned to PDF and has to go through different departments to be approved, inputted in accounting program etc. (try to make a paperless office)

Almost ready to buy as it looks like your program might be able to do this.

Now we have to scan some 400 docs from Jan, Feb and March. Can we make a batch to give these files certain values in column of title, subject, Author and Keywords?
Will renaming the fields (show as) create any problems finding info using other programs?
tks in advance

[RTT]

Now we have to scan some 400 docs from Jan, Feb and March. Can we make a batch to give these files certain values in column of title, subject, Author and Keywords?

For static content (invoice state, invoice ID data, etc) use the EditInfoFields batch tool. With it you can enter the same content to one, or more, of the metadata fields of the batch processed files. If you need more advanced edit operations, export the grid to a .csv file, use an external program to make these advanced editions, MS Excell is good on these tasks, and, when done, import again the .csv file into PDF Explorer and the new information will be entered in the PDFE database and in the PDF files.

Will renaming the fields (show as) create any problems finding info using other programs?

The layout rename option works as a mask and is only used in the PDFE environment, in the PDF files the fields keep the same standard name.
Even so, in the next build 56 I will introduce (already developed) the option to rename the custom fields, in the PDF file itself. This way we can gather and edit other applications custom metadata fields, and maintain compatibility between applications.

[Anonymous]

When exporting to csv file the content of fields creation date and modification date does not seem to be included. (does not show in Excell)

[RTT]

Strange no one mentioned this problem before!! You have found a bug introduced in early build 54, now, thanks to you, fixed.

It is also important that if you latter want to import the .csv you also select for exportation the file system related fields: File Path (this one is really required for latter import task), disk label, disk serial, file size and file date.

[Anonymous]

Do I understand you correctly that when exporting /importing it is important to use Grid "all" and not my personal defined one?

[RTT]

Not exactly. When importing .csv files there is the need to correctly identify the file, so the path and the filename, or the fullpath, fields are really necessary.
The disk serial, volume label and disk type are also other fields useful to make the correct identification of the file source disk, in multiple and removable disk, systems. If these ones are not provided they are gathered by the import tool from the disk corresponding to the drive letter of the provided file path.

If the file is already indexed in the database, all the not provided fields are keep unchanged. For new files, not yet indexed in the database, (PDF Explorer can import .csv files from other cataloguing systems) these not provided fields are filled with default information, for most of them, empty one.

So, you can export your custom grids, but the file path is necessary. If you are using a custom grid layout, with the "Hide invisible fields form the rest of the interface" option active, and the file path field is one of these invisible fields, you have to temporally uncheck this option so you can export that file path field.