6.11   Allow duplicate files in library

Normally EagleFiler will prevent you from importing a file if a file with the same contents (in the data fork) is already in the library. You can check this option if you prefer to import every file, even duplicates. In order for duplicate detection to work, your files’ checksums must be up-to-date. For more information, please read about the Verify and Update Checksum commands.

When you import via Scan for New Files, EagleFiler does not check for duplicates. This is because you have specifically put the files in EagleFiler’s library folder.

To remove duplicates after the files are already in the library, see the Remove Duplicate Files script.

Duplicate URLs

Archived Web pages with the same source URL will generally contain different data, so EagleFiler will not treat them as duplicates. However, there is a script for removing duplicates by URL if that’s what you want to do.

Duplicate E-mail Messages

• EagleFiler checks for duplicates at the file level. Thus, when you import a mailbox file containing a bunch of e-mail messages, EagleFiler checks for a duplicate mailbox but does not check the individual messages within that mailbox file for duplicates.
• When importing the selected messages from an e-mail client (using the capture key), EagleFiler automatically skips duplicate messages within the same mailbox. See also: Handling Duplicate Messages in Apple Mail.
• To prevent importing all duplicate e-mail messages, you can import them as individual .eml files. See the Importing Mail section.
• To remove duplicate e-mail messages from a mailbox, after importing, see the Remove Duplicate Messages script.