Hello,
I upgraded to 3.9.5 this morning, and it seems like when I merge documents, the file naming behavior for the merged file has changed. Now, it seems to discard all numbers that are shared between filenames, turning for example “226-E45-29-Letters1” and “226-E45-29-Letters2” into “E45-29-Letters.” Or a bunch of files named “045-01-Scan-XXX” suddenly are just “Scan.”
Because I am rearranging scanned documents, and I have a specific order in mind, this new behavior adds a step and the risk for errors. Is there a way to set this function to only edit the end of the filename string? I downloaded the new manual and don’t see reference to this in the text or release notes.
Thank you.
That’s true as the revised behaviour is preferable for usual and especially numbered document names but obviously not an improvement in your case. We’ll have a look at it.
I appreciate it. I developed my filename system and workflow based on DT’s behavior, so it was jarring. In the meantime, my hack has been to copy the filename of the first file in a series before I merged, paste it in, and then using batch process once I merged everything in the folder.
To add a detail for anyone who finds this as a search, I set up the groups in my database to emulate the structure of the archives I am drawing from. But I don’t take this down to the folder level, and instead rely on the filename to differentiate folders. I do also encode collection, entry/series, and box numbers just in case things get orphaned. This has saved my butt several times. Also, when you have files in a structure that is inherited from its creator (fonds), order is valuable because you can glean insights into the filer’s mind, based on how documents are filed next to each other.
The next release will revise the naming again and handle both your case and numbered document names.
1 Like