Native windows does not support tagging PDFs as best I can tell. I had the properties window open with a PDF in focus and I was able to tag the PDF, a bit of a surprise but a nice surprise. I was also able to do a Tags:tagname search, all the better.
However I had issues tagging subsequent PDFs. An error panel appears. Not sure that the image uploaded correctly so the message says An error occurred setting metadata filename . The property set specified does not exist on the object. (1170)
Was I accidentally able to tag a couple hundred PDFs or is it supposed to work and there is a bug or something about the PDF causing the error? Thanks.
Adding tags not modifying. Can't really say if it is dependent on a file per se. As I said it worked fine for a couple hundred PDFs doing a mass change. But it failed in a mass change and a single PDF change for a couple. Not sure I could tell the difference, they are all PDFs.
But which tags? Author? Publisher? The actual "tags" tag?
You may need to narrow it down in that case, as it could be something specific to the files involved, if it's working for hundreds of files but failing for some others.
PDF metadata can also involve 3rd party PropertyHandler shell extensions as well, so the issue may be in one of those rather than in Opus itself. Which PDF software do you have installed?
It's possible, since different software presumably produced the PDFs from different actions.
You'll need to narrow down which files it does/doesn't happen to in order to understand what's going on. If you can find a file that always fails and send us a copy of it, we can see if the same is true on our machines, which may tell us whether it's something Opus is doing or something another involved component is doing.
Another factor is anti spyware software which can sometimes arbitrarily block read and/or write access to some documents and not others, based on their contents or whatever other factors it uses to decide they are personal documents. Whitelisting Opus in any software like that is worth a try. If you're using Defender, see the FAQs for guidance (and note that it has two separate whitelists for different parts of it.)
Here's a clue. I am using BoxCryptor to encrypt OneDrive Contents. For the file with issues I CAN adjust the Tags on the PDF file in the native OneDrive lister for the folder but not in the logical BoxCryptor lister. Same folder just some BoxCryptor magic to view the contents locally. I see the tag on the file in lister for the BoxCryptor when I go to that lister but I cannot change it.
Doesn't explain why tagging works for most files and not a few in the BoxCryptor lister though. Workaround would be to modifying tags for problematic PDFs in the native folder lister and the bulk in the BC lister. A bit of a PITA. Enough for now. Thanks.
Creating my own tags via the tag field. Stmt and FY20 for example.
BoxCryptor in the loop for sure. Though why some PDFs work and others don’t has me wondering about some level of metadata as well. It’s not like they all fail.
I am seeing the same behaviour on my system. Most PDFs are taggable but a few are not. My guess is that it depends on what software created the PDF. The attached screen grab shows what happens when attempting to apply a tag to one of the problem PDFs. In my case it has nothing to do with BoxCryptor or Onedrive.
Thanks for that feedback and confirmation. I moved on to putting a tags on the end of file name encased in []'s, [Tagname] for example. Making Tagname reasonably unique and limiting the inventory is key.
Maybe quicker than tag maintenance but tends to shrink the number of tags one might use, which is probably a good thing. Windows indexing enables a very quick search. FWIW.
That PDF appears to be malformed and doesn't have a "trailer" structure at the end. (Although it has something that looks like one, without the word "trailer" at the start like there should be.)
Some ways to repair PDF files with that issue are discussed here:
