JP2005010950A - File management apparatus, file management method, program, and recording medium - Google Patents

Abstract

An unintended movement of a content file can be detected while leaving a form in which a content file group can be used by another software.
A content list file 101 for managing a logical structure 107 of a content file group is created based on the copied content file groups 102 to 105, and each of the content file groups 102 to 105 is created based on registration information on the content list file 101. The movement of the content files 102 to 105 is detected.
[Selection] Figure 1

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a file management apparatus, a file management method, a program, and a recording medium for managing the logical structure of a content file group copied to a recording medium in an information processing apparatus.
[0002]
[Prior art]
Conventionally, as shown in FIG. 11, in an imaging apparatus 110 typified by a digital camera, a data group such as captured image data and audio data (hereinafter referred to as general multimedia content files such as image files, audio files, and moving image files). (Referred to as “content files”) is typically recorded in a specific format on a removable storage medium 112 in the device by a specific file management method.
[0003]
An image file in a digital camera is generally an image format defined by a standard such as Exif or Tiff, and when compressed, it is often performed according to a standard called JPEG. Recording on removable media is generally performed with a structure defined by DCF (Design rule for Camera File System).
[0004]
In the DCF standard, a DOS FAT file system often used in a personal computer is adopted, and as shown in FIG. 12, a directory 1202 named DCIM exists immediately below the root directory 1201 and below that. Each subdirectory is located. The name of each subdirectory is composed of 8 characters, the first 3 characters are composed of numbers from 100 to 999, and the remaining 5 characters are given free characters within the DCF standard. In this example, directory names represented by 1203 and 1204 follow the naming convention. Each subdirectory contains an image file. As the image file name rule, the first four characters of a file name consisting of eight characters are assigned a free character string within the range of the DCF standard, and the second four characters are assigned serial numbers from 0001 to 9999. In this example, image file names represented by 1205, 1206, 1207, and 1208 follow the naming convention. In addition, content files such as audio and moving images other than image files are not regarded as image files defined by the DCF standard, but are allowed to be placed in the same subdirectory.
[0005]
The recorded image file generally has a structure as shown in FIG. The entire format starts with an SOI represented by 1301 and ends with an EOI represented by 1302. The inside of the format is not only the compressed image data represented by 1308 and 1309 and its related tables, but also the attached information recording unit represented by 1303. Various data can often be recorded as metadata. For example, in addition to a marker such as 1304, an identification code, and a header, a part capable of recording the manufacturer and user's unique information indicated by 1305, a date and time recording part indicated by 1306, and a thumbnail image indicated by 1307 are recorded. It is often possible.
[0006]
As an example, the recorded content group is recognized by the processing device 111 such as a PC via the removable storage medium 112 itself in FIG. 11 or from a digital camera or the like via the cable 114 such as USB. Is done. The recognized content group is generally copied to the storage device 113 in the processing device and can be used by software for displaying an album or the like.
[0007]
In the usage form as described above, several forms in which the software manages content groups are conceivable. The following two forms will be mentioned as typical ones.
(1) One is a method in which a content group is taken into software at the time of copying and managed by a software-specific management method. In this case, the original content group is integrated with software-specific management data and is generally managed as one content file.
[0008]
(2) The other is a content file group such as DCF illustrated in FIG. 12 and its directory structure as a copy source, in the copy destination storage as illustrated in FIG. 14, within the dotted line in FIG. As shown in (1407), it is placed in the same or different directory structure, the content file group itself is not changed, and it is represented by a language called HTML defined by a consortium such as the World Wide Web Consortium. This is a method for creating and displaying a content group in a file created by software by a method such as hyperlink.
[0009]
In general, in the example of FIG. 14, the HTML file 1401 is placed in an appropriate position in the file system or on the network, here in the root directory in the same file system, and a DCF structure directory DCIM indicated by 1409 is directly below the root. It is arranged as a directory. The content of such an HTML file is, for example, as shown in FIG. In general, software such as this example is created by software, and an application typified by a Web browser displays a content file group.
[0010]
[Problems to be solved by the invention]
However, in the method (1), content groups are generally combined into one file by a method unique to the software. As a result, the content can be accessed only by a specific software-specific management method. In that case, modification or deletion of the content group is performed through the software. This has the advantage that unintentional movement of content does not occur, but has the disadvantage of making it difficult to reuse the content group with other software.
[0011]
Further, the method (2) has an advantage that the content group can be used separately by another application. On the other hand, the following problems occur.
When a user who does not understand the structure represented by a beginner moves a content file or changes a file name that is not originally intended, for example, from 1403 to 1406 in FIG. 14, the underline in FIG. In some cases, the target content cannot be managed due to a broken link in the portion indicated by the section 1504.
Furthermore, since HTML is a format that generally includes information on layout and document structure, it is difficult to accurately manage the logical structure of content groups, such as grouping, with a processing program or the like. For example, in the example of FIG. 15, three TR elements are included in the TABLE element as indicated by 1501, 1502, and 1503. The TR elements 1501 and 1502 should logically correspond to the grouping of albums, and 1503 represents a link button to another album, but the HTML structure equates the three parties, It becomes difficult to create a page that can accurately reflect the logical structure and to edit it with an application or the like.
[0012]
Therefore, an object of the present invention is to make it possible to detect an unintended movement of a content file while leaving a form in which the content file group can be used by another software.
[0013]
[Means for Solving the Problems]
In order to achieve such an object, a file management apparatus according to the present invention includes a copy unit that copies a content file group into a recording medium, and a logical structure of the content file group based on the copied content file group. Content list file creation means for creating a content list file for management, and movement detection means for detecting movement of each content file based on registration information on the content list file.
[0014]
Also, the file management method of the present invention is a file management method for managing the logical structure of a content file group copied to a recording medium in an information processing apparatus, wherein the content list file creation means includes the copied content A content list file for managing the logical structure of the content file group is created based on the file group, and the movement detecting means detects the movement of each content file based on the registration information on the content list file. It is characterized by doing.
[0015]
A program according to the present invention causes a computer to execute the file management method. Furthermore, the computer-readable recording medium of the present invention is characterized in that the program is recorded.
[0016]
DETAILED DESCRIPTION OF THE INVENTION
DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments to which the invention is applied will be described in detail with reference to the accompanying drawings.
<First Embodiment>
FIG. 2 is a system configuration diagram of the file management apparatus according to the first embodiment of the present invention.
Reference numeral 201 denotes a card reader unit such as a memory card. Reference numeral 202 in FIG. 11 denotes a storage device such as a hard disk drive. Reference numeral 203 denotes a display unit such as a monitor. Reference numeral 204 denotes an interface such as USB or IEEE1394. Reference numeral 205 denotes a processing unit, which indicates an arithmetic device such as a CPU. Each processing program shown in each flowchart described below is recorded in advance in the storage unit 202 or the ROM 207, and the processing unit 205 reads and executes the contents as appropriate. Variables in each processing program are stored in the RAM 206. Alternatively, it may be stored in the ROM 207 as a constant depending on the situation. Reference numeral 209 denotes a data bus, and data transmission / reception between the respective units is performed through this bus.
[0017]
FIG. 3 is a diagram showing a content list file created in the present embodiment.
It is illustrated as a file for managing the content group shown in the example of FIG. In order to reflect the logical structure of the content group, the content file is described using a language called XML defined by the World Wide Web Consortium.
[0018]
As shown in FIG. 1, an XML content list file 101 that manages a content file group that is a set of content files 102, 103, 104, and 105 serving as contents is an appropriate position in the file system or on the network, here the same. The situation is described as an example in which the directory is arranged in the root directory in the file system and the directory DCIM having the DCF structure is arranged as a directory directly under the root.
[0019]
In FIG. 3, the entire content list is bundled with an element called COLLECTION immediately below the XML declaration on the first line, and an ID corresponding to the COLLECTION is assigned as an attribute. For example, even when another content list exists, a unique COLLECTION_ID is assigned to each COLLECTION.
[0020]
Further, a GROUP element for grouping corresponding to the directory structure may exist immediately below the COLLECTION, and it can link a link to each content file existing in the corresponding directory. In this example, only image files are targeted, but audio, video files, and the like may be targeted.
[0021]
The GROUP element has a NAME attribute, and in this example, has a directory name as the value of the NAME attribute. The grouping corresponding to the directory structure is merely an example. Actually, the grouping need not be limited to the directory structure, and content files under various directories may be grouped under different free names, or appropriate In order to represent grouping, a GROUP element may be nested, and an element representing content may be arranged immediately below the COLLECTION element without using the GROUP element.
[0022]
An actual content file is associated with an element representing the content, for example, an element named IMG if it is an image file, and the physical path of the actual file is described by the SRC attribute of the element. Further, in this example, an explanation for the content is described by an ALT attribute, and an ID attribute that is unique in the XML (here, in COLLECTION) is given. The application software uses the XML content list according to the rules as in this example, manages the content file group, and performs display editing.
[0023]
FIG. 4 is a flowchart showing the steps of the process for creating the content list as described above.
In S401, first, all content groups are copied from the digital camera to the storage unit 202 via the removable medium or cable via the card reader unit 201 or the cable I / F unit 204 in FIG.
[0024]
The copied content group has the same directory structure as the copy source or is recorded in the storage unit in a new directory structure. In this example, as shown in a dotted line (107) in FIG. 1, it has the same directory structure as the copy source.
[0025]
In the process of S402, pre-processing for creating an XML content list is performed. Specifically, as shown in S501 of FIG. 5, a unique value is assigned to the variable CollectionID for each XML content list created by the system. Various creation methods can be considered for a unique value, but here, as an example, an example of a value obtained by separating a 16-byte numeric value with a hyphen in the form of UUID (Universally Unique IDentifier) adopted by some operating systems , "AAAAAAAAA-0000-1111-BBBB-AAAAAAAAAAAAA" is entered.
[0026]
In the process of S502, the system date and time is substituted into the variable CreateDate. Here, the value “2002-04-10-T11: 27: 04” is entered in a format compliant with the international standard ISO8601.
[0027]
When the preprocessing for creating the XML content list is completed, in S403, the number of directories existing directly under DCIM is counted, and the value is substituted into a variable DirNum. (Here, the directory under DCIM is not nested because it is an example of copying the directory structure in the DCF format as it is.)
[0028]
In step S404, 0 is substituted for the counter variable i, and the directory names directly under DCIM are read in order. The directory name read first is substituted into variable DirName (i) in S405.
[0029]
Subsequently, in S406, the number of files in the directory DirName (i) is read, and the value is substituted into a variable FileNum.
[0030]
Subsequently, 0 is substituted into the counter variable j in S407, and then the file names below DirName (i) are read in order.
[0031]
Subsequently, in S408, the file name is substituted into the variable FileName (i, j), and in S409, the directory path from the location where the content list XML file is scheduled to be placed, here the location of the root directory, is read. Assign it to PathName (i, j). For example, if the file 102 in FIG. 1 is a directory and the files are read in the order shown, FileName (0,0) = “IMG — 0001.JPG”, PathName (0,0) = “/ DCIM / 100ABCDE / IMG — 0001.JPG "
[0032]
In step S410, the process proceeds to processing for describing metadata in the content file. This processing flow is shown in FIG.
In S601 of FIG. 6, the system assigns an ID value to the content for which the value of the current variable PathName (i, j) is the target, and substitutes it for the variable ContentID (i, j).
[0033]
Next, in step S602, the corresponding content file is read into the RAM 206, and in step S603, a value obtained by concatenating the variable CollectionID and the variable ContentID (i, j) is recorded at a predetermined metadata designation location of the corresponding content file. For example, if the file has a structure as shown in FIG. 13, the value is recorded in the manufacturer / user information recording unit 1305 or the value is recorded immediately after the EOI portion 1302.
[0034]
Next, in step S604, the value of the variable CreateDate is appropriately converted and recorded in the portion where the corresponding content file change date is recorded as necessary. For example, in the case of a file having the format described in FIG. 13, the date / time recording unit 1306 converts the CreateDate value into a format corresponding to the file, for example, “2002: 04: 10 11:27:04”. Record.
[0035]
Further, the modification date and time in the file system is set as the value of CreateDate on the content list file. For example, if a file system capable of defining similar information such as a DOS FAT file system or compatible file system used in DCF is used, a bit field of update date / time in the DOS FAT system in the corresponding content file Is appropriately converted from the value of CreateDate. For example, in the case of the DOS FAT file system, the update date bit field is “0101100010001010” (YYYYYYMMMMDDDD, Y is a relative value from 1980), the update time field is “1011011011000010” (hhhhhhmmmmssss, second is Actual half value is entered). However, since the creation date in the file system is used for another purpose, the change is not forced if the processing system does not want to change it. After the data in the file is converted to the above, the file is overwritten and saved.
[0036]
Returning to FIG. 4, in S411, it is determined whether or not the counter variable j has reached the number obtained by subtracting 1 from FileNum, which is the number of files in the directory. If not reached yet, 1 is added to the counter variable j in the process of S413, and the process returns to S408.
[0037]
If j = FileNum−1, it is checked in step S412 if the counter variable i has already reached the number obtained by subtracting 1 from the number of directories DirNum directly under DCIM. If not reached yet, 1 is added to i in S414, and the process returns to S405.
[0038]
When i reaches DirNum-1, the process proceeds to the XML content list writing process in S415. Specifically, a COLLECTION element and its attributes are created based on the information of the variables CollectionID and CreateDate, a GROUP element is created based on the information of DirName (i), PathName (i, j), ContentID (i, j ), An IMG element is created based on the information of FileName (i, j). In this example, the completed XML content list is as shown in FIG. 3, and the Contents. Saved with the file name xml.
[0039]
Eventually, the content group is in a state where “COLLECTION_ID attribute value + IMG element ID attribute value” is recorded as metadata in each content file. The state is schematically drawn in the frames in 102, 103, 104, and 105 in FIG.
[0040]
The copied content file can be used by an application in the processing device 111 such as a PC in FIG. For example, when an application having a function corresponding to XSLT is operating, the content file can be displayed as a target of a link destination of the XML content list created earlier.
[0041]
Next, a description will be given of checking whether or not an unintended content file movement has occurred in the content group created by the above-described means, and search processing in the case where it has occurred.
[0042]
FIG. 7 is a flowchart describing a process for checking that an unintended movement of a content file has occurred by a user.
First, in the processing of S701, the XML content list file recorded in 101 in FIG. 1 is read into the RAM. Next, the value of the COLLECTION_ID attribute of the COLLECTION element in the corresponding XML content list file is substituted into the variable CollectionID, and the CREATE_DATE attribute value is substituted into the variable CreateDate.
[0043]
Further, the IMG elements in the XML content list file are read in order. In the processing of S704 and S705, the SRC attribute value of the corresponding IMG element is substituted for the variable ContentPath, and the ID attribute value of the corresponding IMG element is substituted for the variable ContentID.
[0044]
Next, in the process of S706, it is confirmed whether or not the file actually exists on the path of the value of ContentPath previously assigned. If it is confirmed, the same processing is performed from S703 for the IMG element to be read next. If the existence of the file has not been confirmed, it is assumed that the user has moved the file unintentionally, and the content file search process is performed in S707. I do.
[0045]
In the example of FIG. 1, a state in which the user has mistakenly moved the file 103 to the position 106 under the directory XXX is schematically illustrated. In such a state, when the IMG element 301 in FIG. 3 in this process is confirmed as the corresponding IMG element, it can be seen that the existence of the file does not exist at the location specified in the content list.
[0046]
The flow of content file search processing is shown in FIG.
First, in the processing of S802, the last string character string distinguished by the delimiter representing the directory of the variable ContentPath substituted previously is substituted into the variable FileName. For example, when the value of ContentPath is “DCIM / 100AABCDE / IMG — 0001.JPG”, the delimiter is a slash and the FileName value is “IMG — 0001.JPG”.
[0047]
Next, in the process of S803, a file whose FileName is the same as the file name is searched from the entire storage. If one or more files are found as a result of the search (S804), metadata is checked for each of them (S805).
[0048]
If the file is not found, or if the file is different as a result of the metadata check, the value of the variable CreateDate appropriately changed to the format of the file system in step S806 is the file change date and time. Search all storage for files that are the same.
[0049]
If one or more files are found as a result of the search (S807), metadata is checked for each of them (S808). If the file is not found, or if the file is different as a result of the metadata check, the metadata is checked for all the files in the storage in S809 and S810. As a result, when the file is not found, the user is notified that there is no file in the corresponding storage, and the process returns to S708 in FIG.
[0050]
FIG. 9 shows a flow of processing for checking each file metadata in S805, S808, and S810 in FIG.
In step S902, each content file as a search result is read into the RAM. Next, in the process of S903, the value of the metadata recorded in the metadata designation location of the corresponding content is substituted into the variable CollectionContentID.
[0051]
In the processing of S904, it is confirmed whether or not the value of CollectionContentID is the same value as that obtained by concatenating the CollectionID and ContentID previously substituted from the XML file. For example, if the value of CollectionContentID is "AAAAAAAAA-0000-1111-BBBB-AAAAAAAAAAAA cano001", and the value of CollectionID is "AAAAAAAAA-0000A11A-AAAAAAAA01, Data is considered a match.
[0052]
If the data matches, you have found the file. In that case, the discovery process is performed in the process of S906. For example, (1) the content file name, (2) the current location on the file system, and (3) the location with the SRC attribute value on the XML content list are displayed to the user, and the user selects The position of the content file on the file system is moved or copied to the position described in (3). Or conversely, the value of (3) may be changed to the position of (2). These processes may be automatically executed by the initial setting of the system.
[0053]
In the example of movement from 103 to 106 in FIG. 1, the content file itself may be returned to the position of 106 to 103, or the SRC attribute of the corresponding IMG element in the XML content path is set to XXX / IMG_0002. It is also possible to perform processing for changing to the current position, such as JPG. This may be selected by the user each time, or may be automatically processed by a predetermined option. When the discovery-time process ends, the process returns to S708 in FIG. 7, and confirmation is similarly performed for another IMG element.
[0054]
If the data does not match in S904, the process returns to S902 until all files are confirmed, and the next search result content file is similarly confirmed. When all the files are finished and there is no file whose data matches, the process returns to the process next to the process that called the process of FIG. For example, when called from S805, the process returns to S806.
[0055]
<Second Embodiment>
Next, a second embodiment of the present invention will be described. The system configuration of the file management apparatus according to the present embodiment is the same as the system configuration of the file management apparatus according to the first embodiment shown in FIG. As the second embodiment of the present invention, instead of the combination of COLLECTION_ID and CONTENT_ID, the file path itself in which the file exists can be used as metadata embedded in the content file.
[0056]
In the content list file used in the first embodiment, since this file path is also described as the SRC attribute of each IMG file, this information is similarly used as the file ID and recorded in the metadata designated location in S603. By using the variable substitution value from the metadata designation location in S903 and the metadata and ID check in S904, it is possible to obtain the same effect as in the first embodiment. FIG. 10 schematically shows a state where the file path is embedded.
[0057]
According to the first and second embodiments, the form in which the content group can be used by other software is left, the logical structure of the album is reflected in the hyperlink, and management by the software is facilitated and is not intended. Appropriate corrections can be made when content files are moved. In the present invention, a magnetic disk or a semiconductor memory can be applied as the storage medium in the above embodiment.
[0058]
Another object of the present invention is to supply a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus, and the computer (or CPU or MPU) of the system or apparatus stores the storage medium. Needless to say, this can also be achieved by reading and executing the program code stored in.
[0059]
In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing the program code constitute the present invention.
[0060]
As a storage medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.
[0061]
Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (basic system or operating system) running on the computer based on the instruction of the program code. Needless to say, a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.
[0062]
Further, after the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function is determined based on the instruction of the program code. It goes without saying that the CPU or the like provided in the expansion board or function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.
[0063]
【The invention's effect】
According to the present invention, a content list file for managing the logical structure of a content file group is created, and the movement of each content file can be detected based on registration information on the content list file. It is possible to detect an unintended movement of a content file while leaving the group in a form that can be used by another software.
[Brief description of the drawings]
FIG. 1 is a diagram showing an example of a file management state of a content group on a storage.
FIG. 2 is a diagram showing a system configuration of a file management apparatus according to an embodiment of the present invention.
FIG. 3 is a diagram showing an example of a completed form of a content list created by XML.
FIG. 4 is a flowchart showing processing for creating a content list and adding metadata to the content.
FIG. 5 is a flowchart showing pre-processing for creating a content list.
FIG. 6 is a flowchart showing a process for describing metadata in a content file.
FIG. 7 is a flowchart showing a process for checking that an unintended movement of a content file has occurred by a user.
FIG. 8 is a flowchart showing content file search processing;
FIG. 9 is a flowchart showing processing for checking each file metadata.
FIG. 10 is a diagram showing an example in which a file path is embedded as an ID in the file management state of the content group on the storage.
FIG. 11 is a diagram schematically illustrating a connection configuration of a processing device such as a digital camera and a PC, media, and a cable.
FIG. 12 is a diagram schematically showing a recording format structure of a digital camera.
FIG. 13 is a diagram schematically showing a content recording format such as an image file.
FIG. 14 is a diagram schematically showing a structure in which an image file group is managed by HTML.
FIG. 15 is a diagram showing an example of an HTML document displaying an image file group.
[Explanation of symbols]
101 XML content list file
102-106 content file
107 Directory structure
201 Card reader unit
202 Storage unit
203 display
204 Cable I / F section
205 processor
206 RAM
207 ROM
208 Input section
209 Data bus
301 IMG element in XML content list file
110 Digital camera
111 PC
112 Storage media
113 Storage device
114 cable
1301 Compressed data start position
1302 Compressed data end position
1303 Attached information recording part
1304 Marker, identification code, header, etc. recording section
1305 Manufacturer, user information recording unit
1306 Date and time recording section
1307 Thumbnail image recording unit
1308 Various tables for compression, each header information recording unit
1309 Compressed image data recording unit

Claims (15)

A copy means for copying the content file group into the recording medium;
Content list file creation means for creating a content list file for managing the logical structure of the content file group based on the copied content file group;
A file management apparatus comprising movement detection means for detecting movement of each content file based on registration information on the content list file. The content list file includes information indicating an initial recording position of the content files in the recording medium, and the movement detection unit checks the recording positions of the content files in the recording medium, thereby The file management apparatus according to claim 1, wherein movement of the file is detected. 3. The file management according to claim 1, further comprising: search means for searching for a content file whose movement is detected from the recording medium when movement of the content file is detected by the movement detection means. apparatus. 4. The file management according to claim 3, wherein the search unit searches the content medium whose movement is detected by the movement detection unit based on registration information on the content list file from the recording medium. apparatus. The content list file includes first identification information of each content file, and the search unit searches the recording medium for a content file corresponding to the first identification information. Item 5. The file management device according to Item 4. Identification information giving means for giving second identification information to each content file based on registration information in the content list file;
The apparatus further comprises confirmation means for confirming the validity of the content file searched by the search means by comparing the second identification information of each content file with the registration information in the content list file. The file management device according to claim 3, wherein the file management device is a file management device. Identification information giving means for giving second identification information to each content file;
Time information giving means for giving time information indicating the time when the second identification information is given by the identification information giving means to each of the content files;
Time information registration means for registering the time information with respect to the content list file;
The said search means searches the content file to which the same time information as the said time information in the said content list file was provided from the said recording medium, The any one of Claims 3-5 characterized by the above-mentioned. File management device. Further comprising confirmation means for confirming the validity of the content file retrieved by the retrieval means;
The identification information providing unit provides second identification information for each content file based on registration information in the content list file, and the confirmation unit includes the second identification information of each content file, 8. The file management apparatus according to claim 7, wherein validity of the content file searched by the search means is confirmed by comparing with registration information in the content list file. 9. The processing apparatus according to claim 6, further comprising a processing unit for matching the content file whose validity is confirmed by the confirmation unit with the management content of the logical structure in the content list file. The file management device described in 1. The file management apparatus according to claim 1, wherein the recording medium is a storage medium. The file management apparatus according to claim 10, wherein the storage medium is a magnetic disk. 11. The file management apparatus according to claim 10, wherein the storage medium is a semiconductor memory. A file management method for managing a logical structure of a content file group copied to a recording medium in an information processing apparatus,
Content list file creation means creates a content list file for managing the logical structure of the content file group based on the copied content file group,
A file management method, wherein the movement detection means detects movement of each content file based on registration information on the content list file. A program for causing a computer to execute the file management method according to claim 13. The computer-readable recording medium which recorded the program of Claim 14.

Images