The present invention relates generally to detecting duplicate photographs to conserve storage space.
The computer-stored files representing digital photographs imaged by a digital camera can be transferred to a user's computer to facilitate a number of advantages, including not only archiving but also viewing, printing, editing, and grouping the photographs into albums. As used herein, “user computer” encompasses not only personal computers and the like but also dedicated computerized storage devices such as the so-called “digital shoebox.”
Apart from the advantages afforded by transferring digital photographs to a user computer and apart from the mode in which the transfer is effected, as recognized herein it is possible for a person to unintentionally transfer the same photograph twice into the storage of the computer. Specifically, as recognized herein redundant copies of the same photo can be stored on a computer when a memory card, flash drive, or other typically camera-compatible memory is engaged with the computer to transfer photos thereto, since the memory card may then be subsequently reengaged with the camera, more pictures taken, and then the memory card reengaged with the computer in an effort to archive the new photos with the old photos still on the memory card and, thus, potentially redundantly copied back onto the computer as part of, e.g., an automatic archive function. Such redundant copying wastes storage space.
A method for storing, onto a first computer storage, digital photo files on a second computer storage includes, for at least one photo file (and preferably for all photo files) sought to be stored, accessing metadata of the file. The method compares the metadata or a hash thereof with data in a data structure representing photo files that have been previously stored onto the first computer storage to determine whether to store the photo file onto the first computer storage.
In a preferred implementation of this aspect a hash of metadata is compared to data in the data structure, and the data structure is a hash table. The hash can be a hash of file name, file size, and predetermined EXIF data. In any case, if the hash of metadata associated with the photo file sought to be stored matches a value in the hash table, the photo file is not copied onto the first computer storage. In contrast, if the hash of metadata associated with the photo file sought to be stored does not match a value in the hash table, the photo file is copied onto the first computer storage and the hash of metadata associated with the photo file sought to be stored is added to the hash table.
Non-limiting EXIF data can include camera model name and/or shooting date/time and/or shooting mode and/or photo effect and/or shutter speed and/or aperture value and/or light metering and/or exposure compensation and/or ISO speed and/or lens type and/or focal length and/or whether zoom was used and/or IS mode and/or image size and/or image quality and/or and whether a flash was used and if so what type.
In another aspect, an apparatus for storing digital photo files includes a first computer storage, and a processor accessing a second computer storage to compare hash values of metadata associated with photo files on the second computer storage with values in a hash table. The processor determines whether to store each photo file onto the first computer storage at least partially based on the comparison.
In still another aspect, a computer readable medium bears instructions that can be executed by a computer processor to compare hashes of metadata of digital photographs against values in a hash table representing previously stored photographs on an archive data store to ensure that only previously unstored photos are copied onto the archive data store.
The details of the present invention, both as to its structure and operation, can best be understood in reference to the accompanying drawings, in which like reference numerals refer to like parts, and in which:
Referring initially to
Additionally, the user computer 12 can include a local internal or external data store 22 such as but not limited to hard disk drive, optical disk drive, alone or in combination with solid state memory, etc. Digital photographs may be stored in the local data store 22. Also, the computer 12 may be engageable with a removable memory 24 such as but not limited a Sony Memory Stick® that may also bear digital photographs taken by a camera 26 with which the removable memory 24 can be engaged. A user computer processor 28 can execute logic stored in local memory to execute various steps described further below.
The camera 26 typically stores a digital photograph in file form, appending metadata to the file known as “Exchangeable Image File” (EXIF) data. In one non-limiting implementation, the EXIF data may include but may not be limited to file name, camera model name, shooting date/time, shooting mode, photo effect, shutter speed, aperture value, light metering, exposure compensation, ISO speed, lens type, focal length, whether zoom was used, IS mode, image size, image quality, and whether a flash was used and if so what type. Additional metadata that can be appended to a photo file either by the camera 26 or by the processor 28 can include the file size.
Completing the description of
Now turning to
The do loop proceeds to block 42 to obtain metadata of the file. In one non-limiting implementation, the data obtained is file name, file size, and other (or all of the above) EXIF data. In a particularly preferred implementation the file name, size, and other EXIF data are hashed.
Decision diamond 44 indicates that the metadata obtained at block 42 is compared to metadata in a table that is accessible to the processor 28 and that contains metadata of photo files that have already been stored on the local data store 22. When a hash is used, the table stores hash values, and at decision diamond 44 the processor 28 simply compares the hash obtained at block 42 with the values in the hash table. If no match is found, at block 46 the hash that was obtained at block 42 is added to the table and the photograph file is stored on the local data store 22. On the other hand, if the metadata of the photo file under test matches data in the table (e.g., if the hash from block 42 matches a hash in the table), the process flows from decision diamond 44 to block 48 wherein the photo file is not stored and, if desired, a message is returned to the user to the effect that “this photograph has already been stored.” Further, if desired the process can erase redundant photo files from the removable memory 24.
While the particular SYSTEM AND METHOD FOR AUTOMATIC DETECTION OF DUPLICATE DIGITAL PHOTOS is herein shown and described in detail, it is to be understood that the subject matter which is encompassed by the present invention is limited only by the claims.
Number | Name | Date | Kind |
---|---|---|---|
5644765 | Shimura et al. | Jul 1997 | A |
5796428 | Matsumoto et al. | Aug 1998 | A |
5805215 | Mizoguchi | Sep 1998 | A |
6163622 | Abdel-Mottaleb et al. | Dec 2000 | A |
6400853 | Shiiyama | Jun 2002 | B1 |
6445818 | Kim et al. | Sep 2002 | B1 |
6584221 | Moghaddam et al. | Jun 2003 | B1 |
6961463 | Loui et al. | Nov 2005 | B1 |
7421128 | Venkatesan et al. | Sep 2008 | B2 |
20020114522 | Seeber | Aug 2002 | A1 |
20020194197 | Flank | Dec 2002 | A1 |
20030200229 | Cazier | Oct 2003 | A1 |
20050036692 | Iida et al. | Feb 2005 | A1 |
20050104976 | Currans | May 2005 | A1 |
20060155757 | Williams et al. | Jul 2006 | A1 |
Entry |
---|
Web page http://www.digicamhelp.com/camera-features/advanced-settings/ec/ Note: Publication date is not published. |
Number | Date | Country | |
---|---|---|---|
20080091725 A1 | Apr 2008 | US |