JP2008033783A - Data management device, data management method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that when a piece of content data is deleted, a content data relation thereof is also deleted, or the content data relation is reconstructed. <P>SOLUTION: The device comprises; a content data relation definition means for defining a relation between content data; a content data deletion means for deleting a certain piece of content data; a content data relation following means following the content data relations including the deleted content data; and a metadata display means displaying metadata of content data including the deleted content data. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a content data management apparatus and content data management method and program for managing relationships between content data.

  Conventionally, when content data management is performed using, for example, a link relationship, if the content data is deleted, the link relationship between the content data is also deleted or the link relationship between the remaining content data is newly reconstructed. It was broken. In addition, by not deleting unnecessary content data, the relationship between the content data is maintained, and restructuring is prevented.

  Specifically, a case where content data A and content data B hold a content data relationship 1 and content data B and content data C hold a content data relationship 2 is taken as an example. When the content data B is deleted, the content data relationship 1 and the content data relationship 2 related to the content data B are deleted at the same time, or the content data relationship 3 is reconstructed between the content data A and the content data C Was done.

Further, it is disclosed that when content data is deleted in content data management that manages the relationship between content data, the related content data is deleted (see, for example, Patent Documents 1 and 2). .
Japanese Patent Laid-Open No. 62-121578 Japanese Patent Laid-Open No. 08-161215

  However, if the relationship between the content data is deleted at the same time, there is a problem that the relationship between the remaining content data cannot be traced. If the link relationship between the remaining content data is newly reconstructed, it is possible to trace the relationship between the remaining content data. However, the relationship has been newly reconstructed, and information on what relationship and position the content data has been so far will disappear.

  In the above specific example, when the content data relationship 1 and the content data relationship 2 that have associated the content data B with other content data are deleted in response to the deletion of the content data B, the relationship between the content data A and the content data C is established. I will not have it.

  If the content data relationship 3 is reconstructed between the content data A and the content data C simultaneously with the deletion of the content data B, information that the content data C was created from the content data A through the content data B is lost. End up.

  With the technique that does not delete even unnecessary content data, it has been difficult to effectively use the storage area by reducing the use area of the storage by deleting the content data, especially in an embedded device in which the storage area is limited and difficult to expand.

  Accordingly, an object of the present invention is to provide a data management device, a data management method, and a program that enable the provision of information on deleted content data by tracing the relationship between the content data remaining even after the content data is deleted. And

  In order to solve the above problems, a data management method according to the present invention comprises the following arrangement. That is, in a management method for managing content data including binary data and metadata using a holding unit, a display control step of reading the content data from the holding unit and displaying the content data on a display unit, and a display of the displayed content data A deletion instruction step for instructing deletion; and a deletion step for deleting binary data included in the content data in accordance with the deletion instruction.

  In order to solve the above problems, a data management apparatus according to the present invention comprises the following arrangement. That is, holding means for managing content data including binary data and metadata, display control means for reading out and displaying the content data from the holding means, and deletion instruction means for instructing deletion of the displayed content data; Deletion means for deleting binary data included in the content data in response to the deletion instruction.

  In order to solve the above problems, a program according to the present invention comprises the following arrangement. That is, in a program for reading and executing a management method for managing content data including binary data and metadata using a holding unit by a computer, a display control procedure for reading the content data from the holding unit and displaying the content data on the display unit; A deletion instruction procedure for instructing deletion of the displayed content data, and a deletion procedure for deleting binary data included in the content data in accordance with the deletion instruction.

  According to the present invention, metadata necessary for knowing the relationship with the remaining content data even if certain content data is deleted is left. It is possible to trace the relationship of the remaining content data using the metadata, and the storage area can be effectively used by deleting unnecessary binary data.

<Embodiment 1>
One embodiment of the present invention will be described with reference to the drawings.

  First, the configuration of a computer apparatus that constitutes the apparatus of the present embodiment will be described with reference to the configuration diagram of FIG. Each apparatus may be realized by a single information processing apparatus, or may be realized by distributing each function to a plurality of information processing apparatuses as necessary. When configured by a plurality of devices, they are connected by a local area network (LAN) or the like so that they can communicate with each other.

  The content data management device (100) in FIG. 1 is a device that manages a plurality of content data. In the content data management apparatus (100), the content data relationship definition unit (101) defines the relationship between content data. The content data deletion unit (102) deletes content data. The content data relationship tracing unit (103) tracks content data based on the content data relationship. A metadata display unit (104) displays metadata of content data.

  FIG. 2 is a block diagram showing a schematic configuration of an apparatus according to a preferred embodiment of the present invention. In FIG. 2, a CPU 201 is a central processing unit, and controls each device connected to the CPU device based on a control program stored in the ROM 202 and the storage device 203. A ROM 202 is a Read Only Memory, and holds various control programs and data. The RAM 204 is a random access memory, and includes a work area of the CPU 201, a data save area during error processing, a control program load area, and the like. The storage device 203 stores various control programs and various data. The network interface 205 can communicate with other information devices and the like via the network 206. The CPU bus 207 includes an address bus, a data bus, and a control bus. The provision of the control program to the CPU 201 can be performed from the ROM 202 and the storage device 203 or can be performed from another information device or the like via the network 206.

Hereinafter, specific description will be given with reference to the drawings.
FIG. 3 shows the relationship between content data and content data managed by the content data management apparatus (100), and the content data relationship represents a derivation relationship.

  FIG. 3 shows content data 301 with ID 001, content data 302 with ID 002, content data 303 with ID 003, and content data 304 with ID 004. The content data relationship 305 is defined from the content data 301 to the content data 302 in FIG. 3 by the content data relationship definition unit (101). The content data relationship 306 is similarly defined from the content data 302 to the content data 303 in FIG. 3, and the content data relationship 307 is similarly defined from the content data 302 to the content data 304 in FIG.

  Specifically, the content data relationship in FIG. 3 represents a derivation relationship. That is, the content data relationship indicates that the content data 302 is created from the content data 301 by format conversion or resolution conversion, and the content data 303 and the content data 303 are created from the content data 302. Further, the content data 301 includes the name, type, resolution, creation date, and main body data (binary data of the content data 301) as metadata. Similarly, the content data 302 includes the name, type, resolution, compression rate, creation date, notes, development parameters, and main body data (binary data of the content data 302) as metadata. The content data 303 and the content data 304 include the name, type, resolution, compression rate, creation date, note, and body data (binary data of the content data 302 and the content data 303) as metadata.

  When a deletion operation is performed on the content data 302 in FIG. 3, the main body data of the content data 302 is deleted by the content data deletion unit (102). At this time, the relationship data 305 to the content data 302, the relationship data 306 from the content data 302, and the relationship data 307 are not deleted. Also, the metadata of the content data 302 is not deleted.

  In the case where the content data having the derivation relationship is traced by the content data relationship tracer (103) after the above-described main data deletion operation for the content data 302 in FIG.

  Using the relation data 305 from the content data 301, it is possible to trace to the content data 302 from which the main body data has been deleted. This is because the metadata of the content data 302 remains. Further, the content data 302 can be traced to the content data 303 using the relational data 306, and the content data 302 can be traced to the content data 304 using the relational data 307. Conversely, the relation data can be used to trace from the content data 304 to the content data 302 and from the content data 302 to the content data 301.

  In FIG. 3, after content data 302 is deleted, the content data relationship tracing unit (103) traces the content data having a derivation relationship, and at the same time, the metadata display unit (104) can display the metadata of the content data. . Using the relational data 305 from the content data 301, trace to the content data 302 in which the main body data is deleted but the metadata remains, and the metadata display unit (104) displays the metadata for the content data 302. .

  In the content data deletion unit (102), the main body data is deleted when the content data 302 is deleted, but the metadata remains. Therefore, it is possible to display the name, type, resolution, compression rate, creation date, notes, and development parameters of the content data 302. Since the main data of the content data 302 has been deleted and does not exist, “Deleted” is displayed.

<Embodiment 2>
In the second embodiment, a case where a workflow relationship is represented by a content data relationship will be described with reference to the drawings.

  FIG. 4 shows the relationship between content data and content data managed by the content data management apparatus (100), and the content data relationship represents a workflow relationship.

  4 shows content data 401 with ID 1, content data 402 with ID 2, content data 403 with ID 3, content data 404 with ID 4, content data 405 with ID 5, content data with ID 6 406 is shown.

  A content data relationship 407 is defined from the content data 401 to the content data 402 in FIG. 4 by the content data relationship definition unit (101). Similarly, a content data relationship 408 is defined from content data 402 to content data 403 in FIG. Similarly, content data relation 409 is defined from content data 403 to content data 404 in FIG. Similarly, a content data relationship 410 is defined from content data 404 to content data 405 in FIG. Similarly, a content data relationship 411 is defined from content data 405 to content data 406 in FIG.

  The content data relationship in FIG. 4 specifically represents a workflow relationship. That is, the content data 401 becomes the content data 402 in the next process according to the workflow. Similarly, content data 402 becomes content data 403 in the next process according to the workflow, and the workflow continues to content data 406.

  Specifically, the content data 401 to the content data 406 hold the creation date, creator, post, comment, status, and body data (binary data of the content data 401 to the content data 406) as metadata. The content data 401 holds content data such as an approval document drafted by the creator Yamada as main data, and holds metadata such as creator = “Yamada” and status = “draft”. The content data 402 holds content data such as an approval document in which a comment is added to the approval document of the content data 401 as main data, and creator = “Suzuki”, comment = “effect unknown”, status = “return” And other metadata. The content data 403 holds content data such as a finalized approval document as main data, and holds metadata such as creator = “Suzuki”, status = “re-draft”. The content data 404 holds content data obtained by stamping Suzuki's electronic seal stamp on the decision document of the content data 403 as main data, and holds metadata such as creator = “Suzuki”, status = “approval”. The content data 405 holds content data obtained by impressing Sato's electronic seal stamp on the decision document of the content data 404 as main data, and holds metadata such as creator = “Sato”, status = “approved”, and the like. . The content data 406 holds content data obtained by stamping Tanaka's electronic seal stamp in the decision document of the content data 405 as main data, and holds metadata such as creator = “Tanaka”, status = “approval”, and the like. .

  When a deletion operation is performed on the content data 404 in FIG. 4, the content data deletion unit (102) deletes the main data of the content data 404. At this time, the relationship data 409 to the content data 404 and the relationship data 410 from the content data 404 are not deleted. Also, the metadata of the content data 404 is not deleted.

  In the case where the content data 404 in FIG. 4 is followed by the content data in the workflow relationship by the content data relationship tracking unit (103) after the above-described deletion operation, it is as follows.

  The relationship data 409 is used from the content data 403 to trace to the content data 404 from which the main body data has been deleted, and the content data 404 is traced to the content data 405 using the relationship data 410. Similarly, using the relational data, the content data 405 can be traced to the content data 404, and the content data 404 can be traced to the content data 403.

  After the above deletion operation on the content data 403 in FIG. 4, the content data metadata can be displayed on the metadata display unit (104) at the same time as the content data relationship tracing unit (103) traces the content data in the workflow relationship. Using the relation data 409 from the content data 403, the content data 404 from which the main body data has been deleted is traced, and the metadata is displayed on the content data 404 by the metadata display unit (104).

  The content data deletion unit (102) deletes the main body data in response to a content data 404 deletion instruction. Therefore, since the main body data has been deleted and does not exist, it is also preferable to display “deleted”.

<Embodiment 3>
In the third embodiment, a case where a version relationship is represented by a content data relationship will be described with reference to the drawings.

  The content data management device (100) in FIG. 7 is a device that manages a plurality of content data.

  In the content data management apparatus (100), the content data relationship definition unit (101) defines the relationship between content data. The content data deletion unit (102) deletes content data. In the content data relationship tracing (103), the content data is traced based on the content data relationship. A metadata display unit (104) displays metadata of content data. A content data browsing history management unit (701) manages browsing history of content data.

  FIG. 5 shows the relationship between content data and content data managed by the content data management apparatus (100), and the version relationship is represented by the content data relationship.

  FIG. 5 shows content data 501 with ID 01, content data 502 with ID 02, content data 503 with ID 03, and content data 504 with ID 04. A content data relationship 505 is defined from the content data 501 to the content data 502 by the content data relationship definition unit (101). Similarly, a content data relationship 506 is defined from the content data 502 to the content data 503, and a content data relationship 507 is defined similarly from the content data 503 to the content data 504.

  Specifically, the content data relationship in FIG. 5 represents a version relationship. That is, the content data 502 indicates that the content data 502 is created as the next version of the content data 501. Further, the content data 501 to the content data 504 hold the document name, version, creation date, creator, and main body data (binary data of the content data 501 to the content data 504) as metadata. In the content data 501, when the content data 501 is browsed, a browsing history record is created as a browsing history 508 by the content data browsing history management unit (701). In the content data 502, when the content data 502 is browsed, a browsing history record is created as a browsing history 509 by the content data browsing history management unit (701). Since the content data 503 has never been browsed, there is no data in which the content data 503 is recorded as a browsing history. In the content data 504, when the content data 504 is browsed, a browsing history record is created as a browsing history 510 by the content data browsing history management unit (701).

  When a deletion operation is performed on the content data 503 in FIG. 5, the content data 503 is deleted by the content data deletion unit (102).

  A specific processing flow of the deletion process will be described with reference to FIG. In step S601 in FIG. 6, the main body data of the content data to be deleted is deleted. When the content data 503 is processed as a deletion target, the main data of the content data 503 is deleted. Next, in step S602 in FIG. 6, it is determined whether or not the deletion target content data has a browsing history. If there is a browsing history, the processing in FIG. 6 ends. When there is no browsing history, it progresses to step S603 in FIG. If the content data 503 is to be deleted, there is no browsing history, and the process advances to step S603. In step S603 in FIG. 6, the metadata of the content data to be deleted is deleted.

  At this time, the deletion of the relation data 506 to the content data 503 and the relation data 507 from the content data 503 is not performed, as in the first and second embodiments.

  When the content data 503 in FIG. 5 is followed by version data by the content data relationship tracing unit (103) after the above-described deletion operation, it is as follows.

  The content data 501 is used to trace the content data 502 using the relation data 505, and the content data 502 is traced to the content data 503 using the relation data 506. Although the metadata of the content data 503 has been deleted, the ID remains and can be traced. Next, the content data 503 is traced to the content data 504 using the relational data 507. Conversely, similarly, it is possible to trace from the content data 504 to the content data 501 using the relational data.

<Embodiment 4>
Although the embodiments of the present invention have been described in detail above, the present invention may be applied to a system constituted by a plurality of devices or may be applied to an apparatus constituted by one device.

  The present invention can also be achieved by supplying a program that realizes the functions of the above-described embodiments directly or remotely to a system or apparatus, and the system or apparatus reads and executes the supplied program code. The Accordingly, the program code itself installed in the computer in order to realize the functional processing of the present invention by the computer is also included in the technical scope of the present invention.

  In this case, the program may be in any form as long as it has a program function, such as an object code, a program executed by an interpreter, or script data supplied to the OS.

  Examples of the recording medium for supplying the program include a floppy (registered trademark) disk, a hard disk, an optical disk (CD, DVD), a magneto-optical disk, a magnetic tape, a nonvolatile memory card, and a ROM.

  Further, the functions of the above-described embodiments are realized by the computer executing the read program. In addition, based on the instructions of the program, an OS or the like running on the computer performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.

  Further, the program read from the recording 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. Then, based on the instructions of the program, the CPU or the like provided in the function expansion board or function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are also realized by the processing.

Configuration of content data management apparatus according to an embodiment of the present invention The block diagram of the apparatus in one Embodiment of this invention The chart which shows content data and content data relation in one embodiment of the present invention The chart which shows content data and content data relation in one embodiment of the present invention The chart which shows a document and document relation in one embodiment of the present invention The figure which shows a processing flow in one Embodiment of this invention. Configuration of content data management apparatus according to an embodiment of the present invention

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Content data management apparatus 101 Content data relation definition part 102 Content data deletion part 103 Content data relation trace part 104 Metadata display part 701 Content data browsing history management part

Claims (7)

In a management method for managing content data including binary data and metadata using holding means,
A display control step of reading the content data from the holding unit and displaying the content data on the display unit;
A deletion instruction step for instructing deletion of the displayed content data;
In accordance with the deletion instruction, a deletion step of deleting binary data included in the content data;
A content data management method comprising:   The content data management method according to claim 1, further comprising a relationship defining step for defining a relationship between the content data.   3. The content data management method according to claim 2, wherein the display control means causes the display means to display the second content data related to the first content data using the relation.   4. The content data management method according to claim 1, wherein, in the display control step, when the binary data of the content data does not exist, metadata is displayed on the display means. A storage step of storing the browsing history of the content data in a holding unit;
2. The data management method according to claim 1, wherein, in the deletion step, the browsing history is referred to and the binary data and the metadata are deleted if the content data is not browsed. Holding means for managing content data including binary data and metadata;
Display control means for reading out and displaying the content data from the holding means;
A deletion instruction means for instructing deletion of the displayed content data;
In accordance with the delete instruction, delete means for deleting binary data included in the content data;
A content data management apparatus comprising: In a program for reading and executing by a computer a management method for managing content data including binary data and metadata using a holding unit,
A display control procedure for reading the content data from the holding unit and displaying the content data on the display unit;
A deletion instruction procedure for instructing deletion of the displayed content data;
In accordance with the deletion instruction, a deletion procedure for deleting binary data included in the content data;
A program that causes a computer to execute.

Images