Source: http://www.google.com/patents/US20020055943?ie=ISO-8859-1
Timestamp: 2014-07-12 07:10:46
Document Index: 249249685

Matched Legal Cases: ['art 100', 'art 101', 'art 102', 'art 103', 'art 102', 'art 100', 'art 100', 'art 101', 'art 102', 'art 103', 'art 100', 'art 101', 'art 102', 'art 103', 'art 100', 'art 102', 'art 101', 'art 103', 'art 102', 'art 102', 'art 103', 'art 103', 'art 102']

Patent US20020055943 - Data storage method and device and storage medium therefor - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign in<nobr>Advanced Patent Search</nobr>PatentsThere is provided a binary data storage method and device and a storage medium which, upon duplicating binary data stored in an external storage medium into a data storage device, is capable of generating inside the data storage device a folder having a name which is appropriate for the data without...http://www.google.com/patents/US20020055943?utm_source=gb-gplus-sharePatent US20020055943 - Data storage method and device and storage medium thereforAdvanced Patent SearchPublication numberUS20020055943 A1Publication typeApplicationApplication numberUS 09/983,723Publication dateMay 9, 2002Filing dateOct 25, 2001Priority dateOct 27, 2000Also published asUS7085767Publication number09983723, 983723, US 2002/0055943 A1, US 2002/055943 A1, US 20020055943 A1, US 20020055943A1, US 2002055943 A1, US 2002055943A1, US-A1-20020055943, US-A1-2002055943, US2002/0055943A1, US2002/055943A1, US20020055943 A1, US20020055943A1, US2002055943 A1, US2002055943A1InventorsKiyoshi KusamaOriginal AssigneeKiyoshi KusamaExport CitationBiBTeX, EndNote, RefManReferenced by (7), Classifications (13), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetData storage method and device and storage medium thereforUS 20020055943 A1Abstract There is provided a binary data storage method and device and a storage medium which, upon duplicating binary data stored in an external storage medium into a data storage device, is capable of generating inside the data storage device a folder having a name which is appropriate for the data without the user having to perform manipulations or confirm the content of the data. The existence of still image data inside a memory card is confirmed and the existence of meta data inside the memory card is confirmed, a folder having a name based on the meta data is generated in a HDD inside the binary data storage device, the still image data inside the memory card is read out and the still image data is duplicated into the generated folder, producing the result that when the still image data inside the memory card is duplicated or stored into the binary data storage device a folder having a name which is appropriate for the data is generated inside the binary data storage device without the user having to perform manipulations or confirm the content of the data. Images(17) Claims(41)
What is claimed is: 1. A data storage method for storing binary data stored in an external storage medium into a data storage device, the method comprising: a binary data confirmation step of confirming an existence of the binary data inside the external storage medium; a meta data confirmation step of confirming an existence of meta data inside the external storage medium; a folder generation step of generating inside the data storage device a folder having a name based on the confirmed meta data; a binary data read-out step of reading out the confirmed binary data; and a binary data duplication step of duplicating into the generated folder the binary data which has been read out. 2. A data storage method according to claim 1, wherein in the folder generation step, in a case where the meta data does not exist, a folder is generated with a name selected in order based on a data base which has been prepared in advance. 3. A data storage method according to claim 1, wherein, in the folder generation step, in the case where the meta data does not exist, a folder is generated with a name that is randomly selected based on a data base which has been prepared in advance. 4. A data storage method according to claim 1, wherein, in the folder generation step, a sentence is generated by a combination of the meta data, and a folder is generated with a name of this generated sentence. 5. A data storage method according to claim 1, wherein, in the folder generation step, in the case where the meta data does not exist, the meta data which is used most among the respective meta data attached to each of the binary data is selected, and this meta data is made to be a folder name. 6. A data storage method according to claim 1, wherein, in the folder generation step, in the case where the meta data does not exist, a plurality of meta data which are used most among the respective meta data attached to each of the binary data are selected in order, and these meta data are combined and made to be the folder name. 7. A data storage method according to claim 1, wherein, in the folder generation step, in the case where the meta data does not exist, each meta data attached to the respective binary data are displayed in a list form and a meta data selected from this list is made to be the folder name. 8. A data storage method according to claim 7, wherein the meta data displayed in the list form are displayed according to the number of times in which the meta data are used in order from the greatest. 9. A data storage method according to claim 1, wherein, in the binary data confirmation step, in a case where the binary data is still image data taken by means of a digital camera, confirmation is made as to whether there exists a DCF object file in a DCF file format. 10. A data storage method according to claim 1, wherein, in the binary data confirmation step, every directory of binary data in the external storage medium is searched, whereby confirmation is made as to whether a binary data file supported by the data storage device exists or not. 11. A data storage method according to claim 1, wherein the meta data are written in a data description language. 12. A data storage method according to claim 11, wherein the data description language is any one of: XML, SGML and HTML. 13. A binary data storage device for storing binary data stored in an external storage medium, the device comprising: a binary data confirmation means for confirming an existence of the binary data inside the external storage medium; a meta data confirmation means for confirming an existence of meta data inside the external storage medium; a folder generation means for generating inside the data storage device a folder having a name based on the confirmed meta data; a binary data read-out means for reading out the confirmed binary data; and a binary data duplication means for duplicating into the generated folder the binary data which has been read out. 14. A data storage device according to claim 13, wherein in a case where the meta data does not exist, the folder generation means generates a folder with a name selected in order based on a data base which has been prepared in advance. 15. A binary data storage device according to claim 13, wherein in the case where the meta data does not exist, the folder generation means generates a folder having a name that is randomly selected based on a data base which has been prepared in advance. 16. A binary data storage device according to claim 13, wherein the folder generation means generates a sentence combining the meta data and generates a folder with a name of said generated sentence. 17. A binary data storage device according to claim 13, wherein, in the case where the meta data does not exist, the folder generation means selects the meta data used most among the respective meta data attached to each of the binary data and makes this meta data be a folder name. 18. A binary data storage device according to claim 13, wherein, in the case where the meta data does not exist, the folder generation means selects in order a plurality of meta data which are used most among the respective meta data attached to each of the binary data, and combines these meta data to be the folder name. 19. A binary data storage device according to claim 13, wherein, in the case where the meta data does not exist, the folder generation means displays in a list form the meta data which are attached to the respective binary data, and selected meta data from this list is made to be the folder name. 20. A binary data storage device according to claim 13, wherein the meta data displayed in the list form are displayed the number of times in which the meta data are used in order from the greatest. 21. A binary data storage device according to claim 13, wherein in the case where the binary data is still image data taken by means of a digital camera, the binary data confirmation means confirms whether there exists a DCF object file in a DCF file format. 22. A binary data storage device according to claim 13, wherein the binary data confirmation means searches every directory of binary data in the external storage medium, whereby confirming whether a binary data file supported by the data storage device exists or not. 23. A binary data storage device according to claim 13, wherein the external storage medium is a semiconductor memory, which includes a PC card, a compact flash card, a SmartMedia, a MultiMedia Card, an SD Card and a memory stick. 24. A binary data storage device according to claim 13, wherein the external storage medium is a magnetic memory, which includes a floppy disk and a magnetic card. 25. A binary data storage device according to claim 13, wherein the external storage medium is a disk-type storage medium, which includes an MO, a CD, an RW, a PD, a DVD, a RAM and an MD data. 26. A binary data storage device according to claim 13, wherein the external storage medium is a storage medium, which includes a removable hard disk. 27. A binary data storage device according to claim 13, wherein the binary data is still image data. 28. A binary data storage device according to claim 13, wherein the binary data is voice/music data. 29. A binary data storage device according to claim 13, wherein the binary data is motion image data. 30. A binary data storage device according to claim 13, wherein the meta data is written in a data description language. 31. A binary data storage device according to claim 30, wherein the data description language is any one of: XML, SGML and HTML. 32. A readable storage medium storing a program for executing a method for storing in a data storage device binary data stored in an external storage medium, the program comprising: a binary data confirmation module for confirming an existence of the binary data inside the external storage medium; a meta data confirmation module for confirming an existence of meta data inside the external storage medium; a folder generation module for generating inside the data storage device a folder having a name based on the confirmed meta data; a binary data read-out module for reading out the confirmed binary data; and a binary data duplication module for duplicating into the generated folder the binary data which has been read out. 33. A readable storage medium according to claim 32, wherein in a case where the meta data does not exist, the folder generation module generates a folder having a name selected in order based on a data base which has been prepared in advance. 34. A readable storage medium according to claim 32, wherein in the case where the meta data does not exist, the folder generation module generates a folder having a name that is randomly selected based on a data base which has been prepared in advance. 35. A readable storage medium according to claim 32, wherein the folder generation module generates a sentence combining the meta data and generates a folder having a name of this generated sentence. 36. A readable storage medium according to claim 32, wherein in the case where the meta data does not exist, the folder generation module selects the meta data used most among the respective meta data attached to each of the binary data and makes this meta data be the folder name. 37. A readable storage medium according to claim 32, wherein in the case where the meta data does not exist, the folder generation module selects in order a plurality of meta data which are used most among the respective meta data attached to each of the binary data, and combines these meta data to be the folder name. 38. A readable storage medium according to claim 32, wherein in the case where the meta data does not exist, the folder generation module displays in a list form the meta data which are attached to the respective binary data, and selected meta data from this list is made to be the folder name. 39. A readable storage medium according to claim 32, wherein the meta data displayed in the list form are displayed according to the number of times in which the meta date are used in order from the greatest. 40. A readable storage medium according to claim 32, wherein in the case where the binary data is still image data taken by module of a digital camera, the binary data confirmation module confirms whether there exists a DCF object file in a DCF file format. 41. A readable storage medium according to claim 32, wherein the binary data confirmation module searches every directory of binary data in the external storage medium, whereby confirming whether a binary data file supported by the data storage device exists or not.
BACKGROUND OF THE INVENTION [0001] 1. Field of the Invention [0002] The present invention relates to a data storage method, a device to storage data therein and a storage medium. [0003] 2. Related Background Art [0004] Conventionally, in a digital camera, a digital video camera and other such image input devices, the inputted still image data, motion image data, voice data or other such binary data is either stored in a memory unit (i.e., memory) mounted into the device, or is stored in a detachable medium (i.e., external storage medium) such as a memory card, a PC card or the like. When binary data stored in a medium such as those is to be used, the medium in which the binary data was stored is inserted into a personal computer (PC), or the image input device is connected directly to the PC; the binary data is read out; and the necessary processing is performed with the data. [0005] However, when the binary data described above is read from the medium, the file name of the binary data file has been automatically assigned on the image input device side, and so there was the problem in that it could not be readily understood from the file name alone when and how the data was generated. [0006] In order to deal with this problem, the user generally adopted a method in which a folder having an appropriate folder name was generated on the PC, and duplicated (i.e., copied) all of the binary data into that folder, whereby a folder name which could be easily understood was given to the data. According to this method, in order to generate the name for the folder it was necessary to confirm the content of the data to be copied, and this operation was a burden, so it was not uncommon to copy the data without generating a folder name. SUMMARY OF THE INVENTION [0007] The present invention has been made in view of the above, and therefore an objective of the present invention is to provide a binary data storage method and device and a storage medium which, upon duplicating binary data stored in an external storage medium into a data storage device, are capable of generating inside the data storage device a folder having a name which is appropriate for the data without the user having to perform manipulations or confirm the content of this data. [0008] According to a first aspect of the present invention, there is provided a data storage method for storing into a data storage device binary data that was stored in an external storage medium, the method including: [0009] a binary data confirmation process for confirming the existence of the binary data inside the external storage medium; [0010] a meta data confirmation process for confirming the existence of meta data inside the external storage medium; [0011] a folder generation process for generating inside the data storage device a folder having a name based on the confirmed meta data; [0012] a binary data read-out process for reading out the confirmed binary data; and [0013] a binary data duplication process for duplicating into the generated folder the binary data which has been read out.
BRIEF DESCRIPTION OF THE DRAWINGS [0014]FIG. 1 is a block diagram depicting an outline construction of a binary data storage device according to the First Embodiment of the present invention; [0015]FIG. 2 is an outline diagram depicting an appearance of the binary data storage device of FIG. 1; [0016]FIG. 3 is an outline diagram depicting a directory structure of binary data stored in a memory card shown in FIG. 2; [0017]FIG. 4 is a flow chart depicting a process for duplicating image data from the memory card of FIG. 2 to a storage part; [0018]FIG. 5 is a flow chart of a process for confirming existence of image data, at step S302 depicted in FIG. 4; [0019]FIG. 6 is a flow chart of another process for confirming the existence of image data, at step S302 depicted in FIG. 4; [0020]FIG. 7 is a flow chart of a process for inputting meta data, at step S304 depicted in FIG. 4; [0021]FIG. 8 is an outline diagram of an input screen displayed on a display part, for inputting the meta data in the process for FIG. 7; [0022]FIG. 9 is a flow chart of a process for duplicating image data, at step S303 depicted in FIG. 4; [0023]FIG. 10 is an outline diagram depicting an example description of the meta data stored in the memory card depicted in FIG. 2; [0024]FIG. 11 is an outline diagram depicting results of the image data duplication process at step S303 depicted in FIG. 4; [0025]FIG. 12 is a flow chart of a process for generating a folder name, in the binary data storage device according to the Second Embodiment of the present invention; [0026]FIG. 13 is an outline diagram of a data base necessary for the generation of the folder name in the process depicted in FIG. 12; [0027]FIG. 14 is a diagram depicting a construction of image data inside the memory card; [0028]FIG. 15 a flow chart of a folder name generation process according to the Third Embodiment; [0029]FIG. 16 is a flow chart of a folder name generation process according to the Fourth Embodiment; and [0030]FIG. 17 is an example of a display screen according to the Fourth Embodiment.
DESCRIPTION OF THE PREFERRED EMBODIMENTS [0031] Hereinafter, explanation will be made of embodiments of the present invention, making reference to the drawings. [0032] (First Embodiment) [0033]FIG. 1 is a block diagram depicting an outline construction of a binary data storage device according to First Embodiment of the present invention. [0034] In FIG. 1, a read part 100 is an entity (input) device for reading predetermined kinds of data, and it is for reading image data which has been read by a scanner (not shown), or binary data or meta data which has been stored in a memory card, a PC card, or other such external memory medium. An input part 101 comprises a keyboard, mouse and/or other such pointing device (not shown), and it is for receiving data input made by a user. A storage part 102 is an entity (input) device for storing inputted binary data, for example, and it is mainly comprised of a hard disk (HDD) or other such memory device. A display part 103 either displays the binary data stored in the storage part 102 or displays the image data which has been read by the read part 100, and it is comprised of a CRT, a liquid crystal display, a TV or other such display devices. [0035] A CPU 14 performs control processes necessary for each part of the device, including the above-mentioned read part 100, input part 101, storage part 102 and display part 103. A ROM 105 and RAM 106 are memories for providing memory space and operational space (i.e., temporary memory space) necessary for a given process. Further, a control program for realizing the control process described below and depicted in FIG. 4, is stored in the ROM 105. The read part 100, the input part 101, the storage part 102, the display part 103, the CPU 104, the ROM 105 and the RAM 106 are connected to each other by means of a system bus. [0036] The binary data storage device according to the present embodiment has various constituting elements provided other than the ones mentioned above; however, these are not the focus of the present invention, so their explanations are omitted. [0037]FIG. 2 is an outline diagram depicting an appearance of the binary data storage device of FIG. 1. [0038] In FIG. 2, the binary data storage device has a slot 201 provided to its front surface, and it is possible to insert a memory card 202 into this slot 201. The memory card 202 is an external storage medium for recording/storing image data, for example, which is to be used by an image input device such as a digital camera, a digital video camera, a scanner, or the like. When the memory card 202 is inserted into the slot 201, the binary data stored in the memory card 202 is read out by means of a read part 100 inside the slot 201. Accordingly, the binary data which has thus been read out is stored/saved on an HDD 203 being a storage part 102. Further, this storage device is provided with, as well as the above-mentioned slot 201 and the HDD 203, an input part 101, a display part 103 and a control part which includes a CPU 104, a ROM 105 and a RAM 106 which are not depicted in the drawing. [0039] Next, explanation will be made of a process for the binary data storage device depicted in FIG. 1, being a process for storing into the storage part 102 the image data from the inserted memory card 202, the explanation being made making reference to FIG. 3 and FIG. 4. Note that the binary data being saved in the memory card 202 here is still image data, having captured by means of a digital camera. In this case, the file format stored in the memory card 202 is that of a Design rule for Camera File Device (referred to hereinafter as �DCF file format�), and an example of a directory structure in this DCF file format is illustrated in FIG. 3. [0040]FIG. 3 is an outline diagram depicting a directory structure of binary data stored in a memory card 202 shown in FIG. 2. [0041] In FIG. 3, reference numeral 400 is a root directory in the memory card 202, and a DCF image root directory 401 with a directory name �DCIM� is stored directly under this root directory. Below that there is a DCF directory 402 for storing a DCF object (file). Below this DCF directory 402 there are stored a plural number of DCF objects, namely the binary data, which is the still image data. The illustration in FIG. 3 indicates that there are four sets of still image data, that are DCF objects 403 a to 403 d, being stored. [0042]FIG. 4 is a flow chart depicting a process for duplicating image data from the memory card 202 of FIG. 2 to the storage part 102. [0043] In FIG. 4, the memory card 202 is first inserted into the slot 201 in the binary data storage device (step S301). Next, at step S302, a discrimination is made by means of a discrimination process depicted in FIG. 5 and FIG. 6 described below, as to whether the image data which is the still image data exists inside the memory card 202 or not. When the result of the discrimination in step S302 indicates that the image data does not exist in the memory card 202, the processing of inputting the meta data (step S304) shown in FIG. 7 and FIG. 8 and described below is performed, and the present processing ends. [0044] On the other hand, when the result of the discrimination in step S302 indicates that the image data does exist in the memory card 202, the processing of duplicating the image data (step S303) depicted in FIG. 9 and FIG. 11 is performed, and the present processing ends. [0045] Next, explanation will be made of a processing of confirming the existence of the image data at step S302, which is depicted in FIG. 4, making reference to FIG. 5 and FIG. 6. [0046]FIG. 5 is a flow chart of a processing of confirming existence of image data, at step S302 depicted in FIG. 4. [0047] In FIG. 5, a fixed DCF image root directory 401 in the memory card 202 is first searched, and a discrimination is made as to whether the name �DCIM� of this directory 401 exists or not (step S500). When the results of this discrimination indicate that �DCIM� does not exist, the process advances to step S504 and a judgment of no DCF object, that is, a judgment that the still image data does not exist in the memory card 202 is made and the process returns. On the other hand, when �DCIM� does exist, the DCF directory 402 below the DCF image directory 401 is then searched (step S501). At step S501, just as in step S500, a discrimination is made as to whether the DCF directory 402 exists or not, and in the case where the DCF directory 402 does not exist, the process advances to step S504 and returns. However, in the case where the DCF directory 402 does exist, a discrimination is then made at step S502 as to whether the DCF object exists or not. When the results of this discrimination indicate that the DCF object does not exist, then the process advances to step S504 and returns. However, in the case where the DCF object does exist the process advances to step S503, and a judgment that the DCF object exists, that is, a judgment that the still image data does exist in the memory card 202 is made and the process returns. Note that in the present processing is only a judgment as to whether the DCF object 403, namely the still image data, exists or not, so it is not necessary to determine the number of DCF objects 403 at this stage. [0048] On the other hand, in the case where the file format stored in the memory card 202 is the above-mentioned DCF file format, a plurality of DCF directories 402 may be stored directly under the DCF image root directory 401, and a processing in such a case is depicted in FIG. 6. [0049]FIG. 6 is a flow chart of another processing of confirming the existence of image data, at step S302 depicted FIG. 4. Note that in FIG. 6 the same reference numerals are assigned to the steps which perform the same processes as in FIG. 5, and their explanations are omitted. [0050] In FIG. 6, in the case where the DCF directory and the DCF object are determined at step S501 and at step S502, respectively, not to exist (i.e., NO at step S501 and NO at step S502), then a discrimination is made at step S601 as to whether a subsequent DCF directory exists or not, and when this subsequent directory exists a processing of returning to step S501 is added on. Accordingly, it becomes possible to search all of the plurality of DCF directories 402, and determine whether or not there is a DCF object stored in each DCF directory 402. [0051] Next, explanation will be made of a processing of inputting meta data at step S304 in FIG. 4, making reference to FIG. 7 and FIG. 8. [0052]FIG. 7 is a flow chart of a processing of inputting meta data, at step S304 depicted in FIG. 4. FIG. 8 is an outline diagram of an input screen displayed on a display part 103, for inputting the meta data in the processing of FIG. 7. In FIG. 8, reference numeral 801 is an event to be photographed, 802 is a date and time of photograph, 803 is a location of photograph, and 804 is a photographer. [0053] At step S701 in FIG. 7 the meta data input screen is displayed on the display part 103 as a meta data input processing. The meta data is comprised, generally, of a date, a person who took the image, and other such data, which is to be attached to the image. Next, the meta data input made by the user is received (step S702). The meta data input is performed for each of the items of �Title�, �Date� and the like in FIG. 8 by manipulations of a keyboard and/or mouse, for example. After all of the items have been inputted and the OK button indicated by reference numeral 805 is clicked, the inputted meta data is saved in the root directory 400 of the memory card 202 under the name �cardinfo.xml� (step S703), and the present processing thus ends. The meta data input processing is performed as described above. [0054] Next, explanation will be made of a processing of duplicating the image data at step S303 in FIG. 4, making reference to FIGS. 9 through 11. [0055]FIG. 9 is a flow chart of a processing of duplicating image data, at step S303 depicted in FIG. 4. [0056] At step S901 in FIG. 9 confirmation is made as to whether the meta data exists in the memory card 202 or not, and thus the existence or non-existence is determined. In the present embodiment, the language in which the meta data is described is Extensible Markup Language (XML), and to confirm whether the XML file �cardinfo.xml� exists in the root directory in the memory card 202 or not is sufficient. In the case where the results of this determination indicate that the XML file �cardinfo.xml� did exist, then a judgement is made that there does exist meta data and the process advances to step S902. On the other hand, in the case where the results indicate that the meta data did not exist a judgement is made that there is no meta data, and the process advances to step S903. [0057] At step S902, the �Title� of �cardinfo.xml� is read, and the folder having the same name as the meta data being saved in the �Title� are generated at a predetermined location in the binary data storage device. According to this processing, in the case where there is, for example, the meta data �cardinfo.xml� depicted in FIG. 10, then the folder having the name of �Party� which is written in the �Title� is generated. If a folder with the same name is present in this predetermined location, then numbers are added in sequence to the end of the name of the newly generated folder. Further, in the case where a memory card 202 in which the meta data �Party� is saved is used over and over again, then folders having the names �Party�, �Party-2�, �Party-3�, �Party-4� and so on are generated. The predetermined location where the folder is to be generated may be designated in advance, but it is also possible to designate it as the need arises. [0058] Further, not only is the �Title� (which is �Party�) used from �cardinfo.xml�, but also the �Date� (i.e., �Oct. 10, 2000�), the �Location� (i.e., �Tokyo�), the �Photographer� (i.e., �Kiyoshi Kusama�) and the like are also used to indicate, for example, �a photograph taken of a party in Tokyo by Kiyoshi Kusama on Oct. 11, 2000�, thus indicating �who� took the picture, �when� and �where� as a complete sentence, and generating a folder having that sentence as its name. [0059] Next, the still image data inside the memory card 202 is duplicated in the folder generated at step S902 (step S904), and the process returns. As a result, the still image data 1101 which is present in the memory card 202 indicated in FIG. 11 is duplicated as still image data 1102 in a folder having the name generated at a predetermined location in the binary data storage device (in the present example the name is �Images�.) [0060] On the other hand, when the results of the discrimination made at step S901 indicate that the meta data did not exist, then a folder having the name of �Untitled� is generated in the predetermined location of the binary data storage device. Here, in the same way as in step S902, in the case where a folder having the same name existed in the predetermined location, then a folder is generated with a new number chosen in numerical sequence added to the end of the folder name. Then, at step S904, the still image data is duplicated in the folder with the name �Untitled� which has been generated at the predetermined location in the binary data storage device, and then the process returns. [0061] According to this processing, a folder with a name is automatically generated in the storage part 102 (i.e., in the HDD 203) of the binary data storage device based on the meta data inside the memory card 202, and it becomes possible to duplicate the still image data inside the memory card 202. [0062] According the present embodiment, all of the DCF objects (i.e., the still image data) inside the memory card 202 are copied into the binary data storage device, but when this image data is copied from the memory card 202 it may be automatically deleted from the memory card 202. Further, according to the present embodiment, the information which was used in the meta data is used just as it is to generate the folder name, but it is also possible to use a built-in dictionary function or the like to come up with connotatively or semantically similar words or information to use as the folder name. [0063] According to the present embodiment, explanation has been made of the case in which the format of the file to be stored inside the memory card 202 is the DCF file format; however, even in the case where there is no directory structure having such specific file format it is still possible to perform the above processes. In such a case, the file which is to be recognized as the binary data can be searched from the memory card 202 as, for example, a JPEG file in the case of still image data, or an MPEG file in the case of motion image data. [0064] According to the First Embodiment, the presence of the still image data inside the memory card 202 is confirmed (step S302), and also, the presence of the meta data inside the memory card 202 is confirmed (step S901), the folder having the name based on this meta data is generated in the HDD 203 of the binary data storage device (step S902), the still image data inside the memory card 202 is read out and the still image data is duplicated in the folder which has been generated (step S904); therefore, when the still image data inside the memory card 202 is duplicated (i.e., copied) into or stored in the binary data storage device, the folder having the name being appropriate for that data can be generated inside the binary data storage device without the user performing manipulations or confirming the content of this data. [0065] (Second Embodiment) [0066] It was explained that, in the above-mentioned First Embodiment, a folder having a name based on the meta data inside the memory card 202 is generated in the binary data storage device. Explanation will be made of the generation of the folder name, according to the Second Embodiment, in the case where the image data is present inside the memory card 202 and the meta data does not exist therein, this explanation being made with reference to FIG. 12 and FIG. 13. Note that the binary data storage device in the Second Embodiment has the same construction as in the above-mentioned First Embodiment, so explanation thereof is omitted here. Hereinafter, explanation will be made only of the points which are different from the First Embodiment. [0067]FIG. 12 is a flow chart of a processing of generating a folder name, in the binary data storage device according to the Second Embodiment of the present invention. [0068] According to FIG. 12, in the case where the meta data was not present in the memory card 202 the name of �Untitled� was uniformly given to the folder in the case of First Embodiment, but at step S1201 in the Second Embodiment, a name is selected in order based on a data base (FIG. 13) prepared in advance in the binary data storage device. Next, at step S1202, a folder having this selected name is generated at a predetermined location in the binary data storage device, and at step S1203 the image data inside the memory card 202 is duplicated into the generated folder having this name. [0069] In the present embodiment, the bland and dry folder name �Untitled� which was given in the First Embodiment becomes a specific name, and it thus becomes easy to handle the folder even without having to assign a name to it. Further, in the Second Embodiment the example was given of selecting a folder name in order based on a data base which has been prepared in advance; however, it is also possible to assign appropriate names in a random fashion. [0070] According to the Second Embodiment, when the still image data exists in the memory card 202 but the meta data does not, the folder is generated having the name selected in order based on the data base which has been prepared in advance (step S1201 and step S1202), and the still image data is duplicated into the generated folder (step S1203); therefore, when the still image data inside the memory card 202 is duplicated (i.e., copied) into or stored in the binary data storage device, the folder having the name being appropriate for that data can be generated inside the binary data storage device without the user performing manipulations or confirming the content of this data. [0071] (Third Embodiment) [0072] It was explained that, in the above-mentioned First Embodiment and Second Embodiment, folders are generated in the binary data storage device having names based on the meta data inside the memory card 202 and based on the data base. [0073] Explanation will be made of the generation of the folder name, according to the Third Embodiment, in the case where the still image data is present inside the memory card 202 and the meta data of each set of the still image data is also present therein, this explanation being made with reference to FIG. 14 and FIG. 15. Note that the binary data storage device in the Third Embodiment has the same construction as in the above-mentioned the First Embodiment, so explanation thereof is omitted here. Hereinafter, explanation will be made only of the points which are different from the First Embodiment. [0074]FIG. 14 depicts a construction of the image data inside the memory card 202, and meta data written in XML is attached to each set of image data. In the memory card 202 the Cardinfo.xml meta data is not present. Here, the meta data written in XML may be stored in a JPEG file application marker APP4 or the like inside each of the sets of image data, for example, and it is also possible to save this meta data written in XML as a separate file from the image file. [0075] In the First Embodiment and the Second Embodiment, in the case where the meta data �cardinfo.xml� did not exist, a different name was given to the folder to generate the folder name. FIG. 15 is a flow chart explaining a method of generating a folder name in the case where the meta data of each set of image data does exist. At step S1501, all of the image files inside the DCF folder inside the folder are first confirmed, and the number of pieces of meta data included therein is confirmed. That is, according to the example in FIG. 14, �Kenji�=3, �Opening Ceremony�=1 and �Tug of War�=2. Next, at step S1502, the most common meta data becomes the folder name, and this is generated at a predetermined location. According to the example in FIG. 14, �Kenji� is the most common, so a folder having the name of �Kenji� is generated. If there already exists a folder with the name of �Kenji� in the predetermined location, then folders having the names of �Kenji-2�, �Kenji-3�, and so on are created. It is possible to designate in advance the predetermined location where the folder is to be generated, but it is also possible to designate this location at the time when the need arises. [0076] At the final step, step S1503, all of the images inside the memory card are copied to the generated folder. According to the present embodiment, the meta data attached to each of the images is effectively used and the meta data which is used the most becomes the folder name, which produces the advantage that the content of the folder can be easily imaged based on the folder name. [0077] In the present embodiment, only the common meta data was used for the folder name; however, in the case where more than one meta data have been used exactly the same number of times, all of these meta data may be used to generated the folder name. [0078] In the present embodiment, only the most frequently used meta data was used for the folder name; however, it is also possible to use meta data which is of a superior rank for the folder name. [0079] (Fourth Embodiment) [0080] Explanation was made of methods for completely automatically determining the file name, according to the above-mentioned First, Second and Third Embodiments. Explanation will now be made of an operation for the user to generate the folder name manually, according to the Fourth Embodiment, making reference to FIG. 16 and FIG. 17. Note that the binary data storage device in the Fourth Embodiment has the same construction as in the above-mentioned First Embodiment, so explanation thereof is omitted here. Hereinafter, explanation will be made only of the points which are different from the First Embodiment. [0081] In the Third Embodiment a method was shown of generating a folder in the case where meta data is attached to each image. [0082] In the Fourth Embodiment, too, explanation will be made of a method of generating a folder in the case where the meta data is attached to each of the images, with reference being made to the flow chart of FIG. 16. [0083] At step S1601, the meta data included in the individual images inside the DCF folder are first extracted, each meta data is listed up, and the quantity thereof is counted. At step S1602, the meta data are displayed to the user in order of greatest number thereof. FIG. 17 depicts the display screen at this time. [0084] Reference numeral 1701 is an appellation of a meta data which is a selected candidate to become the folder name, and reference numeral 1702 is the list showing the extracted meta data. Also, reference numeral 1703 is the number or quantity of the meta data, which is arranged in sequence according to greatest number. When the user selects the meta data which the user is interested in from the list 1702 on the screen in FIG. 17 and presses on an �OK� button 1704, and the process advances to step S1603. [0085] At step S1603, the folder of the folder name selected at step S1602 is generated at a predetermined location. In the case where there already exists a folder with the same folder name at that predetermined location, the numerals �2�, �3� and so on are added to the end of the folder name and the folder is thus generated. [0086] At the final step, step S1604, all of the images in the memory card are copied into the generated folder. [0087] According to the present embodiment, it is possible for the user to generate the folder with his or her own intentions reflected in the folder name. [0088] In the above-mentioned First, Second, Third and Fourth Embodiments explanation has already been made of the case in which the binary data stored inside the memory card 202 is still image data; however, it goes without saying that even when voice/music data or motion image data is stored the same processing can be performed. Further, the memory card 202 may be a PC card, a compact flash card, a SmartMedia�, a MultiMedia Card�, an SD Card�, a Memory Stick� or other such semiconductor memory, or a floppy disk, a magnetic card or other such magnetic memory, or an MO, a CD, an RW, a PD, a DVD, a RAM, an MD or other such disk-type storage medium, or may also be a removable hard disk or other such storage medium. [0089] Further, the meta data is, as described above, data description language and in the above-mentioned the First and Second Embodiments XML was used, but another language, such as Standard Generalized Markup Language (SGML) or Hypertext Markup Language (HTML) may also be used. [0090] (Other Embodiments) [0091] A program being stored in the ROM 105 inside the binary data storage device and being for executing a control method for realizing the First Embodiment and the Second Embodiment may be stored in a freely selected removable storage medium and this storage medium may be attached from an external point, producing the result that this program is provided to the CPU 104 and executed. The storage medium for providing this program may be, for example, a floppy disk, a hard disk, an optical disk, an optical magnetic disk, a CD-ROM, a CD-R, a magnetic tape, a non-volatile memory card or the like. Further, in place of the CPU 102 it is possible to realize the above-mentioned embodiments by means of a circuit (not shown) which performs operations similar to these. [0092] The binary data storage device may be a PC, and an Operating System (OS) or the like running on the PC may execute a part or all of the above-mentioned program. Additionally, the program provided by the freely selected, removable storage medium is written into a memory (not shown) which is provided to function extension board (not shown) which has been inserted into the PC, or to a function extension unit (not shown) which is connected to the PC, and after that, the CPU and such (not shown), which are provided to this function extension board or function extension unit, execute a part or all of this program. [0093] As is explained in detail above, according to the present invention, the existence of the binary data inside the external storage medium and the meta data inside the external storage medium is confirmed, the folder having the folder name based on this meta data is generated inside the data storage device and the binary data is duplicated into the generated folder; so therefore, when the binary data inside the external storage medium is duplicated into the data storage device, it is possible to generate a folder name for the duplication of the data without the user having to perform manipulations or confirm the content of this data. [0094] Further, according to the present invention, in the case where the meta data did not exist in the external storage medium, a folder is generated having a name selected in order based on a data base which has been prepared in advance, or having a name which is selected randomly and the binary data is duplicated into the generated folder; so therefore, when the binary data inside the external storage medium is duplicated into the data storage device, it is possible to generate a folder name for the duplication of the data without the user having to perform manipulations or confirm the content of this data. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7522174Jun 24, 2004Apr 21, 2009Canon Kabushiki KaishaImage processing apparatus, image processing method, program for implementing image processing method, and recording medium recording programUS7599960Aug 18, 2004Oct 6, 2009Canon Kabushiki KaishaMetadata processing method, metadata storing method, metadata adding apparatus, control program and recording medium, and contents displaying apparatus and contents imaging apparatusUS7840586 *Jun 30, 2004Nov 23, 2010Nokia CorporationSearching and naming items based on metadataUS20090228831 *Mar 3, 2009Sep 10, 2009Andreas WendkerCustomization of user interface elementsEP1574959A1 *Dec 9, 2003Sep 14, 2005Konica Minolta Holdings, Inc.Data management structure rewriting programEP2432209A1 *Sep 14, 2011Mar 21, 2012Samsung Electronics Co., Ltd.Apparatus and method for managing image data and metadataWO2006003516A1 *Jun 17, 2005Jan 12, 2006Hakala TeroSearching and naming items based on metadata* Cited by examinerClassifications U.S. Classification1/1, 707/E17.01, 707/999.201International ClassificationG06T1/00, G06F12/00, G06F17/30Cooperative ClassificationY10S707/99944, Y10S707/99942, Y10S707/99945, Y10S707/99943, G06F17/30067, H04N2201/3229European ClassificationG06F17/30FLegal EventsDateCodeEventDescriptionJan 2, 2014FPAYFee paymentYear of fee payment: 8Dec 30, 2009FPAYFee paymentYear of fee payment: 4Jan 18, 2002ASAssignmentOwner name: CANON KABUSHIKI KAISHA, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KUSAMA, KIYOSHI;REEL/FRAME:012487/0993Effective date: 20011130RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google