Hi Jon, first off thanks so much for the new marooned attachments manager (MAM)!
For my core database, somehow I "lost" the links for ~1260 PDFs, they are in my attachments folder and the references are in my database, but the names do not line up (this happened quite some time ago, but I never had time to sit down and manually reattach, I manually reattach when I need to). MAM finds these attachments, which is really helpful as at least I now have a clear quantification of my problem.
Here is an example, the PDF and its database entry (a small change in the way the attachment is named, spaces around the ellipsis …):
So my question is what the optimal way is to automate reattaching these PDFs?
Marooned attachments: best way to reattach?
Re: Marooned attachments: best way to reattach?
If I use the attachment-pane right-click "Reattach..." method, I get to select the attachment, then I get this requestor:
I select add to existing attachment (i.e. it finds it correctly), which then results in a double-attachment (i.e. reattach does not replace the missing attachment, so I then have to manually unattach the broken one):
I select add to existing attachment (i.e. it finds it correctly), which then results in a double-attachment (i.e. reattach does not replace the missing attachment, so I then have to manually unattach the broken one):
Re: Marooned attachments: best way to reattach?
I'll have to take a look at why it doesn't get rid of the orphaned attachment in that case.
You can get rid of it using Global Change -> Remove Orphaned Attachments. This can be applied to one reference, many references, or all references at once. Try this on a Copy of your library first to see how it works.
Jon
Sonny Software
P.S. There is also the Refs -> Get PDF -> Find & Attach Local PDFs. it's not 100%, but it when it works it will save you time. You'd still want to get rid of orphaned attachments when finished.
You can get rid of it using Global Change -> Remove Orphaned Attachments. This can be applied to one reference, many references, or all references at once. Try this on a Copy of your library first to see how it works.
Jon
Sonny Software
P.S. There is also the Refs -> Get PDF -> Find & Attach Local PDFs. it's not 100%, but it when it works it will save you time. You'd still want to get rid of orphaned attachments when finished.
Re: Marooned attachments: best way to reattach?
Thanks Jon. So the recommendation is to make a copy of my database, use the MAM to move the ~1250 marooned attachments to a temp folder, then use "Find & Attach Local PDFs", spot-check what the result is, remove orphans if necessary, then replace the main database with the copy.
Is there a way to generate a "log" of what some of the global actions like Find & Attach Local PDFs do? It would help to validate when we make major changes to our database (manual checking is hard to do when there are thousands of references in the database)...
Is there a way to generate a "log" of what some of the global actions like Find & Attach Local PDFs do? It would help to validate when we make major changes to our database (manual checking is hard to do when there are thousands of references in the database)...
Re: Marooned attachments: best way to reattach?
No, these actions don't generate a log.
Jon
Sonny Software
Jon
Sonny Software
Re: Marooned attachments: best way to reattach?
P.S. I've made a silent update and Reattach should now work as intended.
Re: Marooned attachments: best way to reattach?
Hi Jon, I downloaded the silent update but still get the double attachment when I try to reattach the PDF:
Perhaps this depends on the renaming options. I use a custom format using a {d} t for renaming. Anyway this is fairly minor.
Regarding the log, could this be a feature request for a future version of Bookends, as I think it would be helpful, even if there is no UI, but just a simple text file that can be referenced when making a major change to a database...
Perhaps this depends on the renaming options. I use a custom format using a {d} t for renaming. Anyway this is fairly minor.
Regarding the log, could this be a feature request for a future version of Bookends, as I think it would be helpful, even if there is no UI, but just a simple text file that can be referenced when making a major change to a database...