JP2004334529A - Information processing system, information processing apparatus, information processing method, storage medium, and program - Google Patents

Abstract

An object of the present invention is to perform unified management of a group of content files processed by different applications and stored in a predetermined storage location in a predetermined structure.
A plurality of content file groups (501, 503) including content files (DSC.0001.JPG, DSC.0002.JPG,...) Stored in different storage locations (folders AppA, AppB). Means for classifying each content file for each of the content file groups (501, 503) based on the attribute of each content file; an identifier indicating each of the classified groups; Means for generating files (502, 504) in which the identifiers of the content files classified into the respective groups and information on the storage location of the content files are associated with the generated files (502, 504) For generating a file (col-p.xml) Equipped with a.
[Selection diagram] FIG.

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an information processing method and apparatus for managing a data file group such as an image file.
[0002]
[Prior art]
A group of data such as image data and audio data photographed by an imaging device typified by a digital camera (hereinafter, a general multimedia content file such as an image file, an audio file, and a moving image file is described as a “content file”. Is generally recorded in a specific format by a specific file management method on a removable storage medium mounted in the apparatus. In a digital camera, an image file is generally generated in an image format defined by standards such as Exif and Tiff, and is often recorded after being compressed by a standard called JPEG. In addition, recording on a removable storage medium (removable medium) attached to a digital camera is generally performed in a structure defined by DCF (Design Rule for Camera File System) (for example, Patent Documents 1 and 2). .
[0003]
The content group recorded in this manner is input to an information processing device such as a personal computer (PC) via a removable medium or a digital camera or the like via a cable such as a USB and recognized. The recognized content group is generally used via application software (hereinafter, also referred to as an application) for displaying an album or the like. In such application software, the recognized content group is often copied to a storage (storage device) of a PC and then processed. Examples of the copying method include a case where the directory structure of the DCF described above is directly copied to a directory designated by an application or a user, a case where the directory structure is converted into a structure unique to the application, and the like. In any case, the content group is generally copied and managed in different locations with different structures depending on the application.
[0004]
[Patent Document 1]
JP-A-2002-142185
[Patent Document 2]
JP 2001-283188 A
[0005]
[Problems to be solved by the invention]
With such an application-specific management method, there is no problem when only the application is used on a PC, but it is desirable to integrate and manage different content groups handled by different applications on a single PC, for example. When a request occurs (for example, when a group of images taken on the same day is desired to be the same group), this cannot be done, or even if done, the user will have to perform a complicated operation. In particular, in the future, it is expected that individuals will have more than one digital camera, so if you use different applications for each digital camera, you want to manage the content group in a unified manner In such a case, such a problem occurs.
[0006]
SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and utilizes a content file by uniformly managing a group of content files processed by different applications and stored in a predetermined storage location in a predetermined structure. The purpose is to improve the convenience in doing so.
[0007]
[Means for Solving the Problems]
In order to achieve the above object, an information processing apparatus according to the present invention has the following configuration. That is,
An information processing apparatus that manages a plurality of content file groups including at least one content file stored in different storage locations,
Classification means for classifying each content file based on an attribute of each content file in the content file group for each content file group stored in the different storage location,
A first collection file containing at least an identifier indicating each of the classified groups, an identifier of a content file classified into each of the groups, and information on a storage location of the content file is stored in the different storage location. First generating means for generating for each of the generated content files,
A second generation unit that generates a second collection file for associating the plurality of first collection files generated for each of the content file groups.
[0008]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0009]
[First Embodiment]
[System configuration]
FIG. 1 is a diagram showing a configuration of the information processing apparatus according to the first embodiment of the present invention. Reference numeral 0101 denotes a card reader unit such as a memory card. Reference numeral 0102 denotes a storage unit such as a hard disk drive. Reference numeral 0103 denotes a display unit such as a monitor. Reference numeral 0104 denotes an interface unit for connecting a USB or an IEEE 1394 cable.
[0010]
Reference numeral 0105 denotes a processing unit, which indicates an arithmetic device such as a CPU. Each processing program and application software in each flowchart described below are recorded in advance in the storage unit 0102, the ROM 0107, or the RAM 0106, and the processing unit 0105 reads out the contents to an appropriate area of the RAM 0106 and executes the contents. Variables in each processing program are stored in an appropriate area in the RAM 0106. Alternatively, it may be stored in the ROM 0107 as a constant depending on the situation. Reference numeral 0109 denotes a data bus, and data transmission / reception between the units is performed through this bus.
[0011]
[Description of recording structure of content group]
FIG. 2 is a diagram showing an example of a recording state of a content file group according to the DCF standard described above.
[0012]
In the DCF standard, a DOS FAT file system compatible with a file system widely distributed in personal computers is adopted, and a directory named DCIM is located immediately below the root directory 0200 as shown in FIG. 0201 exists, and each subdirectory is arranged therebelow. The name of each subdirectory is composed of eight characters, the first three characters of which are composed of numbers from 100 to 999, and the remaining five characters are given free characters within the range of the DCF standard. In the example of FIG. 2, according to this naming rule, the directory name is represented by 0202. Each of the subdirectories contains a content file. As a content file naming rule, the first four characters of a file name composed of eight characters are assigned a free character string within the range of the DCF standard, and the last four characters are assigned serial numbers from 0001 to 9999. In this example, according to this naming rule, the content file name is represented by a series of files 2033.
[0013]
[Explanation of the file format structure of each content]
FIG. 3 is a diagram illustrating the concept of the data format of a still image file (a), a moving image file (b), and an audio file (c) recorded according to the DCF standard. The still image file 0300a stores, for example, recording date and time information 0301a, model name information 0302a, shooting scene information 0303a, and a thumbnail image 0304a as image attribute information (metadata) together with the main image data 0305a.
[0014]
The moving image file 0300b stores, for example, recording date information 0301b as moving image attribute information (metadata) together with the moving image data 0302b.
[0015]
The audio file 0300c includes, as audio attribute information (metadata), together with the audio data 0304c, for example, the recording date / time information 0301c in the first attribute information area, the recording time 0301c ′ in the second attribute information area, and the model name. Information 0302c and the like are stored.
[0016]
[Description of collection file]
FIG. 4 is a definition information DTD (Document Type Definition) that defines a description method of a list (hereinafter referred to as a collection) of a content group in an XML format generated by the information processing apparatus according to the first embodiment of the present invention. It is a figure showing an example of.
[0017]
The details of the syntax rules of XML and DTD are described in the XML recommendation (http://www.w3.org/TR/REC-xml).
[0018]
The definition information DTD0400 for the collection file includes a COLLECTION element 0401, a GROUP element 0402, an IMG element 0403, a MOV element 0404, an AUD element 0405, and a METADATA element 0406.
[0019]
A COLLECTION element 0401 stores the entire collection file set and functions as a Root element of the collection file. This element may have zero or more GROUP elements (0402) or IMG (0403) elements or MOV elements (0404) or AUD elements (0405) as child elements following zero or more METADATA elements (0406). it can. This element can have an ID attribute 0401a, a COLLECTION_ID attribute 0401b, a NAME attribute 0401c, a CREATE_DATE attribute 0401d, and a MODIFY_DATE attribute 0401e. Here, the ID attribute (0401a) represents a unique element identifier within the collection file, and the COLLECTION_ID attribute (0401b) represents a unique collection identifier within at least the use range of the information processing apparatus. The NAME attribute (0401c) indicates the name of the collection file, the CREATE_DATE attribute (0401d), and the MODIFY_DATE attribute (0401e) indicate the date and time of creation and update of the collection file, respectively.
[0020]
The GROUP element 0402 stores an arbitrary set for classifying a collection file, and can configure a hierarchical structure of the GROUP element. This element may have zero or more GROUP elements (0402) or IMG (0403) elements or MOV elements (0404) or AUD elements (0405) as child elements following zero or more METADATA elements (0406). it can. Also, this element can have an ID attribute 0402a, a COLLECTION_ID attribute 0402b, and a NAME attribute 0402c. Here, the ID attribute (0402a) represents a unique element identifier in the collection file, and the COLLECTION_ID attribute (0402b) represents a classification identifier unique at least within the use range of the information processing apparatus. The NAME attribute (0402c) represents the name of the classification information.
[0021]
The IMG element 0403 stores information of a still image file (for example, a JPEG image). This element can have zero or more METADATA elements (0406) as child elements. This element can have an ID attribute 0403a, a CONTENT_ID attribute 0403b, an SRC attribute 0403c, a TYPE attribute 0403d, and an ALT attribute 0403e. Here, the ID attribute (0403a) represents a unique element identifier in the collection file, and the CONTENT_ID attribute (0403b) represents a data file identifier unique at least within the use range of the information processing apparatus. The SRC attribute (0403c) is a link reference to the target still image file, and the TYPE attribute (0403d) represents the MIME type of the still image file referenced by the SRC attribute. The ALT attribute (0403e) is a simplified display character string, and is used, for example, when a still image file referenced by the SRC attribute cannot be reproduced.
[0022]
The MOV element 0404 stores information on a moving image file (for example, an MPEG moving image). This element can have zero or more METADATA elements (0406) as child elements. This element can have an ID attribute 0404a, a CONTENT_ID attribute 0404b, an SRC attribute 0404c, a TYPE attribute 0404d, and an ALT attribute 0404e. Here, the ID attribute (0404a) represents a unique element identifier within the collection file, and the CONTENT_ID attribute (0404b) represents a data file identifier unique within at least the use range of the information processing apparatus. The SRC attribute (0404c) is a link reference to the target moving image file, and the TYPE attribute (0404d) indicates the MIME type of the moving image file referred to by the SRC attribute. The ALT attribute (0404e) is a simplified display character string, and is used, for example, when the moving image file referenced by the SRC attribute cannot be reproduced.
[0023]
The AUD element 0405 stores information of an audio file (for example, MPEG audio). This element can have zero or more METADATA elements (0406) as child elements. This element can have an ID attribute 0405a, a CONTENT_ID attribute 0405b, an SRC attribute 0405c, a TYPE attribute 0405d, and an ALT attribute 0405e. Here, the ID attribute (0405a) represents a unique element identifier in the collection file, and the CONTENT_ID attribute (0405b) represents a data file identifier unique at least within the use range of the information processing apparatus. The SRC attribute (0405c) is a link reference to the target audio file, and the TYPE attribute (0405d) represents the MIME type of the audio file referenced by the SRC attribute. The ALT attribute (0405e) is a simplified display character string, and is used, for example, when the audio file referenced by the SRC attribute cannot be reproduced.
[0024]
The METADATA element 0406 stores attribute information (metadata) of the still image, moving image, and audio file. This element has no child element restrictions. This element can also have an ID attribute 0406a. Here, the ID attribute (0406a) represents a unique element identifier within the collection file.
[0025]
The link reference is a URI (Uniform Resource Identifiers) standardized as an RFC (Request For Comments) in the Internet Engineering Task Force (IETF), and is defined in RFC2396 and RFC2732.
[0026]
In addition, the MIME (Multipurpose Internet Mail Extensions) type is described in a format defined in RFC2045 and RFC2046,
Type / Subtype
Is described. The type includes, for example, image, audio, video, and the like, and represents that the data is classified into still image data, audio data, and moving image data.
[0027]
[Description of processing in information processing apparatus]
As an example of processing in the information processing apparatus according to the present embodiment, a case where two pieces of application software A and B exist on the information processing apparatus will be described below. More specifically, when the content files are copied from the removable media to the storage unit 0102 of the information processing apparatus by the application software A and B, the information processing apparatus creates a collection file according to the DTD rule. The case of managing the content file group will be described in detail.
[0028]
FIG. 5 is a diagram showing a state where each application has copied a content group from a removable medium. First, when the application A copies a content group recorded in a DCF structure on a removable medium in a structure indicated by 0501, a process of creating a collection file 0502 described in XML in the information processing apparatus is shown in a flowchart of FIG. This will be described with reference to FIG.
[0029]
First, a directory path of a copy destination, in this case, C: \ AppA, is substituted for a variable Dir (step S0601), and a content file group recorded according to the DCF structure in the removable medium is copied under the directory (step S0602). . Here, the structure of the DCIM folder and its subdirectories, which is the structure of the DCF, is copied as it is, but it is needless to say that the structure may be copied after being converted to a structure unique to the application.
[0030]
Next, the number of copied content file groups is counted and assigned to a variable n (step S0603). Then, each content file is read in such a manner that the counter i is repeated from 0 to n-1 (step S0605), and the file name and path are substituted into FileList (i) (step S0606). And creates a unique ID value (step S0607) and substitutes it for the variable ContentID (i). Here, a 128-bit character string called UUID (Universally Unique Identifier) defined by OSF (Open Software Foundation) is used, but other IDs may be used.
[0031]
Next, the file type of the content file is determined (step S0608) and assigned to the variable FileType (i), and the attribute information (metadata) of the content file previously described with reference to FIG. 3 is read and assigned to the variable Metadata (i). (Step S0609). Here, date information is acquired as metadata, and grouping (classification) is performed using the date information. However, grouping may be performed by combining metadata other than date information or a plurality of metadata.
[0032]
In this example, since grouping is performed for each date, if the read metadata is in a format indicated by date and time as indicated by 0701 in FIG. 7, it is processed into data including only the date as indicated by 0702, and the variable AttVal (Step S0610). It is determined whether AttVal exists in the GroupList (step S0611). If it does exist, the process proceeds to step S0614. If it does not exist, the process proceeds to step S0612. AttVal is added as a group name to the GroupList, and further, for each group. An ID value unique to the information processing apparatus is created and assigned to Collection_ID (AttVal) (step S0613). Further, FileList (i) classified as a group of the AttVal value is added to GroupList (AttVal) (step S0614). Then, a unique ID value is created in the child collection file and assigned to ID (i) (step S0615).
[0033]
After performing these processes for all the content files (“Yes” in step S0616), a collection file (first collection file) to which a unique Collection_ID of the information processing device is added based on the value assigned to each variable , (Hereinafter referred to as “child collection file”) (step S0618, step S0619). The written child collection file is as shown in FIG. 8, and the col-a. xml.
[0034]
A similar process is performed for a content file group on a removable medium managed by the application B. The copied content file group is stored in the storage location indicated by 0503 in FIG. 5, and the created collection file is stored in col-b. xml, and the contents are as shown in FIG.
[0035]
By the processing described above, each application can use the content file group that is grouped using XML, but is not associated with the content file group managed by another application. Next, a collection file (second collection file, hereinafter referred to as “parent collection file”) for making the association is created. This can be created as an XML file composed of the same DTD definition as each child collection file created first. The flowchart is shown in FIG.
[0036]
First, the file path of each previously created child collection file is substituted for Path (i) (step S1002). Here, since the parent collection file is created in the root directory of the same drive on the storage, Path (i) is “./ProgramFiles/AppA/MISC/col-a.xml” for application A, and “ ./ProgramFiles/AppB/MISC/col-b.xml ".
[0037]
Next, a character string as the name of each child collection is substituted for GroupName (i) (step S1003). Here, “AppA” is used for application A and “AppB” is used for application B. However, the name may be input by the user or another name may be assigned by the information processing apparatus.
[0038]
The above process is repeated for all the child collection files (steps S1004 and S1007), and after the repetition is completed (“Yes” in step S1004), an ID unique to the information processing device is created for the child collection file and assigned to the variable CollectionID. (Step S1005). Finally, a parent collection file reflecting the value of each variable is written (step S1006). The contents of the parent collection file written out in this example are as shown in FIG. 11, and the file name is col-p. xml.
[0039]
Creating this parent collection file allows each child collection file managed by a different application to be associated.
[0040]
Next, a procedure for reconstructing a plurality of child collection file groups as one flat collection file (hereinafter, referred to as a flat collection file) as needed will be described with reference to FIG.
[0041]
First, a parent collection file is read (step S1201), and each child collection file linked by the SRC attribute of the GROUP element is read one by one using a counter as a variable i (step S1203). In this example, there are two linked child collection files, but it goes without saying that the same processing can be performed even if the number is three or more.
[0042]
The file name and path are substituted for the variable Collection (i), and the IMG, MOV, and AUD elements in the read (child) collection file are sequentially selected with the counter as j (step S1206).
[0043]
Subsequently, the element name and the attribute value group are assigned to a variable Element (i, j). However, since the ID attribute guarantees uniqueness only in each child collection file, it is generally necessary to change the ID attribute when performing composition. For this reason, a process of leaving the ID attribute portion blank here is performed (step S1207).
[0044]
Furthermore, the linked content file itself is read (step S1208), metadata is read from the read content file, and the metadata is substituted for Metadata (i, j) (step S1209).
[0045]
As in the case of creating the child collection file, the value of Metadata (i, j) is processed as necessary, and the processed value is substituted for the variable AttVal to obtain a group name (step S1210). If the AttVal does not exist in the GroupList, the AttVal is added to the GroupList (AttVal) (step S1212), and the information processing device unique ID value of the group is created and assigned to the Collection_ID (AttVal) (step S1213). Next, an ID value unique to the flat collection file is created and stored in the ID attribute value portion of Element (i, j) which has been left blank (step S1214). Further, Element (i, j) classified as a group of the AttVal value is added to GroupList (AttVal) (step S1215). This is repeated for all the elements of each child collection file (steps S1216 to S1219).
[0046]
Finally, a unique ID value is created for the entire flat collection file (step S1220), and the flat collection file is written out based on the values stored in the variables (step S1221).
[0047]
The completed XML flat collection file is col-f. xml is recorded in the root directory of the same drive in the storage. The contents are as shown in FIG. xml, col-b. However, it can be seen that the content files created separately on the same date are managed in the same group.
[0048]
When this flat collection file is used, for example, display and printing reflecting a logical grouping in the flat collection created by using an application such as a Web browser having a function corresponding to the standard defined by W3C called XSLT. And so on.
[0049]
As is clear from the above description, according to the present embodiment, when performing grouping according to attributes for a group of content files stored in a predetermined storage location in a predetermined structure by a predetermined application, a child collection file is generated. By managing the content files, the convenience in using the content file can be improved.
[0050]
In addition, even for multiple content files processed by different applications, it is possible to improve the convenience of using content files by generating and managing parent collection files that associate each child collection file. It becomes.
[0051]
Furthermore, by generating a flat collection file using a parent collection file and a child collection file, it is possible to manage a plurality of content files processed by different applications in a unified manner. Can be further improved.
[0052]
[Second embodiment]
In the first embodiment described above, in the creation of the flat collection file shown in FIG. 12, each content file referred to by each child collection file is referred to and its metadata is referred to. Grouping at the time of creating a collection file and grouping at the time of creating a flat collection file are performed according to the same criterion, and the criterion is determined by any one of the first child collection files (name attribute value of GROUP element in this example). Is used as a key, a flat collection file can be created without referring to each child content file.
[0053]
Furthermore, when the first child collection file is created, the necessary metadata is described in the METADATA element of the child collection file, so that each child collection file can be referred to without referring to the content file again later. A flat collection file can be created.
[0054]
Specifically, for example, col-a. xml instead of col-a2. xml, a metadata element having an appropriate namespace (here, the photographing date and photographer) is included in each of the IMG, AUD, and MOV elements, and col-b. xml is created in a similar form, and the col-f.xml shown in FIG. xml or a flat collection file grouped by the same shooting date as in the case of col-f2. xml, it is possible to create a flat collection file or the like that has been grouped by the photographer.
[0055]
[Third Embodiment]
In the first and second embodiments, the case where each content file and each of the child collection file, the parent collection file, and the flat collection file exist in the same storage unit has been described. These devices can communicate with each other, such as an HTTP protocol over the Internet protocol (the HTTP protocol is standardized as RFC (Request For Comments) 2068 in the IETF (Internet Engineering Task Force)). Even if it is arranged on a network having means, it is possible to realize the processing described in the first embodiment or the second embodiment on the network. Needless to say.
[0056]
FIG. 16 shows an example. In this example, 1601, 1602, 1603, and 1604 are devices on the network 1600 and have names (addresses) 1601-d, 1602-d, 1603-d, and 1604-d that are identified on the Internet. .
[0057]
Each device has a processing function group such as a CPU shown in FIG. 1 and a processing function such as an HTTP protocol. Reference numerals 1601, 1602, and 1604 denote an information processing apparatus exemplifying a PC server, and reference numeral 1603 denotes an imaging apparatus exemplifying a digital camera equipped with an equivalent information processing apparatus.
[0058]
Col-a. Illustrated in the first embodiment. A child collection file similar to xml is created as 1602-x in the storage under the processing in the device 1602.
[0059]
Further, a content file group referred to by the device 1602 at the time of creation is stored in a storage of another device 1601 with a directory structure similar to DCF with each file name of 1601-c, and is stored by using a means such as HTTP. Files are referenced. In this example, the file name col-a3. FIG. 17 shows the child collection file 1602-x created as xml.
[0060]
Further, the col-b. A child collection file similar to xml is created as 1603-x in the storage under the processing in the device 1603. The content file group referred to at the time of creation is stored in the storage of the same device 1603 with the same directory structure as in the first embodiment. Reference numeral 1603-c denotes each file name.
[0061]
The device 1604 creates a parent collection 1604-x1 and a flat collection 1604-x2. At the time of creation, each child collection or content file is referred to using means such as HTTP. 18 and 19 show examples of the parent collection 1604-x1 and the flat collection 1604-x2 created in this example.
[0062]
[Other embodiments]
The present invention can be applied to a system including a plurality of devices (for example, a host computer, an interface device, a reader, a printer, etc.), but may be a device including one device (for example, a copying machine, a facsimile machine, etc.). May be applied.
[0063]
Further, an object of the present invention is to provide a storage medium storing a program code of software for realizing the functions of the above-described embodiments to a system or an apparatus, and a computer (or CPU or MPU) of the system or apparatus to store the storage medium. It is needless to say that the present invention is also achieved by reading and executing the program code stored in the.
[0064]
In this case, the program code itself read from the storage medium realizes the function of the above-described embodiment, and the storage medium storing the program code constitutes the present invention.
[0065]
As a storage medium for supplying the program code, for example, a floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, magnetic tape, nonvolatile memory card, ROM, or the like is used. be able to.
[0066]
When the computer executes the readout program code, not only the functions of the above-described embodiments are realized, but also an OS (Operating System) running on the computer based on the instruction of the program code. It goes without saying that a part or all of the actual processing is performed and the functions of the above-described embodiments are realized by the processing.
[0067]
Further, after the program code read from the storage medium is written into a memory provided on a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that a CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing, and the processing realizes the functions of the above-described embodiments.
[0068]
【The invention's effect】
As described above, according to the present invention, by conveniently managing a group of content files processed by different applications and stored in a predetermined storage location in a predetermined structure, the convenience in using the content files can be improved. It is possible to improve the performance.
[Brief description of the drawings]
FIG. 1 is a diagram illustrating a configuration of an information processing apparatus according to a first embodiment of the present invention.
FIG. 2 is a diagram showing an example of a recording state of a content file group according to the DCF standard.
FIG. 3 is a diagram illustrating the concept of the data format of a still image file, a moving image file, and an audio file recorded according to the DCF standard.
FIG. 4 is a diagram illustrating an example of a DTD (Document Type Definition) that defines a method of describing a collection and a description file in an XML format, which is processed by the information processing apparatus according to the first embodiment of the present invention.
FIG. 5 is a diagram showing a state where each application has copied a content file group from a removable medium.
FIG. 6 is a flowchart illustrating a flow of a child collection file creation process in the information processing apparatus according to the first embodiment of the present invention.
FIG. 7 is a diagram illustrating a form before and after conversion of a metadata value.
FIG. 8 is a diagram showing an example of the contents of a written child collection file.
FIG. 9 is a diagram showing an example of the contents of a written child collection file.
FIG. 10 is a flowchart illustrating a flow of a parent collection file creation process in the information processing apparatus according to the first embodiment of the present invention.
FIG. 11 is a diagram showing an example of the contents of a written parent collection file.
FIG. 12 is a flowchart illustrating a flow of a flat collection file creation process in the information processing apparatus according to the first embodiment of the present invention.
FIG. 13 is a diagram showing an example of the contents of a written flat collection file.
FIG. 14 is a diagram illustrating an example of the contents of a flat collection file including a written metadata part.
FIG. 15 is a diagram showing an example of the content of a written flat collection file.
FIG. 16 is a diagram showing a positional relationship of a group of content files in a network including an information processing device according to a third embodiment of the present invention.
FIG. 17 is a diagram showing an example of the contents of a written child collection file.
FIG. 18 is a diagram showing an example of the contents of a written parent collection file.
FIG. 19 is a diagram showing an example of the contents of a written flat collection file.
[Explanation of symbols]
0101: Card reader section
0102: Storage unit
0103: Display section
0104: Interface section
0105: Processing unit
0106: RAM
0107: ROM
0108: Input unit
0109: Data bus
0200, 0201, 0202: Directory in DCF file structure
[0203] Content file group in DCF file structure
0300a: Still image file
0300b: Video file
0300c: Audio file
0301a, 0301b, 0301c, 0301c ': Recording date and time information
0302a, 0302c: Model name information
# 302b: Video data
0303a: shooting scene information
0304a: Thumbnail image data
0304a: Main image data
0304c: Voice data

Claims (17)

An information processing apparatus that manages a plurality of content file groups including at least one content file stored in different storage locations,
Classifying means for classifying each content file based on an attribute of each content file in the content file group for each of the content file groups stored in the different storage locations,
A first collection file containing at least an identifier indicating each of the classified groups, an identifier of a content file classified into each of the groups, and information on a storage location of the content file is stored in the different storage location. First generating means for generating for each of the generated content files,
An information processing apparatus comprising: a second generation unit configured to generate a second collection file for associating the plurality of first collection files generated for each of the content file groups. The second collection file includes at least an identifier of a first collection file generated for each content file group and information on a storage location of each of the first collection files. The information processing device according to claim 1. Collection file reading means for reading all the first collection files whose storage locations are described in the second collection file;
Re-classifying means for re-classifying all content files whose identifiers are described in the read first collection file in accordance with the attributes of the content files;
A third collection file for generating a third collection file in which at least an identifier indicating each of the reclassified groups, an identifier of a content file reclassified into each of the groups, and information on a storage location of the content file are described; The information processing apparatus according to claim 2, further comprising a generation unit. The re-classification means,
On the basis of information on the storage location of the content file, acquiring information on attributes described in the content file by reading the content file, and performing re-classification using the information on the acquired attribute. The information processing apparatus according to claim 3, wherein: The re-classification means,
The information processing apparatus according to claim 3, wherein re-classification is performed based on an identifier indicating each of the groups described in the first collection file. The method according to claim 1, wherein the first collection file further describes an identifier for uniquely identifying the content file and an identifier for uniquely identifying the first collection file. 2. The information processing device according to 1. The information processing apparatus according to claim 1, wherein the plurality of content file groups are stored in the different storage locations by a plurality of different applications. An information processing method for managing a plurality of content file groups including at least one content file stored in different storage locations,
A classification step of classifying each content file based on an attribute of each content file in the content file group for each of the content file groups stored in the different storage locations;
A first collection file containing at least an identifier indicating each of the classified groups, an identifier of a content file classified into each of the groups, and information on a storage location of the content file is stored in the different storage location. A first generation step of generating for each of the generated content files,
A second generation step of generating a second collection file for associating the plurality of first collection files generated for each of the content file groups. The second collection file includes at least an identifier of a first collection file generated for each content file group and information on a storage location of each of the first collection files. An information processing method according to claim 8. A collection file reading step of reading all the first collection files whose storage locations are described in the second collection file;
A re-classification step of re-classifying all the content files whose identifiers are described in the read first collection file in accordance with an attribute of the content file;
A third collection file for generating a third collection file in which at least an identifier indicating each of the reclassified groups, an identifier of a content file reclassified into each of the groups, and information on a storage location of the content file are described; The information processing method according to claim 9, further comprising a generating step. The reclassification step,
On the basis of information on the storage location of the content file, acquiring information on attributes described in the content file by reading the content file, and performing re-classification using the information on the acquired attribute. The information processing method according to claim 10, wherein The reclassification step,
The information processing method according to claim 10, wherein re-classification is performed based on an identifier indicating each of the groups described in the first collection file. The method according to claim 1, wherein the first collection file further describes an identifier for uniquely identifying the content file and an identifier for uniquely identifying the first collection file. 9. The information processing method according to item 8. 9. The information processing method according to claim 8, wherein the plurality of content file groups are stored in the different storage locations by a plurality of different applications. A storage medium storing a control program for causing a computer to implement the information processing method according to any one of claims 8 to 14. A control program for causing a computer to implement the information processing method according to any one of claims 8 to 14. An information processing system that manages a plurality of content file groups including at least one content file stored in different storage locations,
Classifying means for classifying each content file based on an attribute of each content file in the content file group for each of the content file groups stored in the different storage locations,
A first collection file containing at least an identifier indicating each of the classified groups, an identifier of a content file classified into each of the groups, and information on a storage location of the content file is stored in the different storage location. First generating means for generating for each of the generated content files,
An information processing system comprising: a second generation unit configured to generate a second collection file for associating a plurality of the first collection files generated for each of the content file groups.

Images