JP2005050018A - Document file management device and data structure - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To operate a system related to a PUI paper document and a workflow management system by making them associated to each other. <P>SOLUTION: A document file related to a process is managed by an object-oriented model having a document file management class for managing the document file related to the process, a correction data extraction class for extracting correction data, and a document file update class for updating the document file related to the process. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a document file management apparatus and a data structure.
[0002]
[Prior art]
In recent years, several proposals have been made regarding PUI (Paper User Interaction) paper documents printed with a document ID (for example, URL (Uniform Resource Locators)) indicating the location of the original electronic document. (For example, refer to Patent Document 1).
[0003]
In addition, workflow management systems that manage and automate the flow of documents and information passed between persons in charge, in order to facilitate the work when multiple persons in charge work over the network in recent years, are well known. (See, for example, Non-Patent Documents 1 to 3.)
[0004]
[Patent Document 1]
JP 2003-067363 A.
[0005]
[Non-Patent Document 1]
“Standards”, [online], [Search July 3, 2003], <http: // www. wfmc. org / standards / standards. htm>
[0006]
[Non-Patent Document 2]
“Workflow Management Coalition TheWorkflow Reference Model”, [online], [July 3, 2003 search], <http: // www. wfmc. org / standards / docs / tc003v11. pdf>
[0007]
[Non-Patent Document 3]
“Workflow Management Coalition Termination & Glossary” [online], [searched July 3, 2003], <http: // www. wfmc. org / standards / docs / TC-1011_term_glossary_v3. pdf>
[0008]
[Problems to be solved by the invention]
However, the conventional system related to the PUI paper document has a problem that the retouched data related to rewriting and the attribute information related to the attributes of the rewritten data are not managed in association with the original PUI paper document.
[0009]
For this reason, there has been a problem that a workflow management system in which a plurality of persons in charge of workflow make a plurality of additions to the same document cannot be operated in association with the system related to the PUI paper document.
[0010]
SUMMARY An advantage of some aspects of the invention is that a system related to a PUI paper document and a workflow management system are operated in association with each other.
[0011]
[Means for Solving the Problems]
In order to solve the above problem, the present invention provides a document file management class for managing a document file related to a process, an added data extraction class for extracting additional data, and a document file update class for updating a document file related to a process. A document file related to a process is managed by an object-oriented model including:
[0012]
According to the present invention, a system related to a PUI paper document and a workflow management system can be operated in association with each other.
[0013]
The document file management class corresponds to, for example, a PUI document file management class described later. The retouching data extraction class corresponds to, for example, a retouching image extraction class to be described later. The document file update class corresponds to, for example, a PUI document file update class described later.
[0014]
In order to solve the above problem, the present invention may have a data structure.
[0015]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0016]
FIG. 1 is a conceptual diagram (part 1) of a PUI-workflow system according to an embodiment of the present invention.
[0017]
As shown in FIG. 1, a PUI-workflow system includes a PUI document management server 1, a workflow server 2, at least one MFP (Multi Function Printer) 4, and at least one connected via a network. The above client PC 5 is included.
[0018]
In the system shown in FIG. 1, the PUI paper document to which the PUI document ID for identifying the original PUI document file and the PUI user ID for identifying the user are added is circulated to the next examiner / approver.
[0019]
From the PUI paper document image information read by the MFP 4, for example, the PUI document management server 1 separates new writing information such as comments, signatures, and seals. Here, the PUI document management server 1 extracts new difference information by extracting the difference between the image information of the PUI paper document read by the MFP 4 and the addition information of the original electronic document plus the previous examination / approver. Isolate.
[0020]
For example, the PUI document management server 1 manages the retouching information as a PUI document file associated with the original electronic document together with the PUI user ID for identifying the retouching user, the PUI document ID, and the retouching ID for identifying the retouching information. Is done.
[0021]
By circulating the PUI paper document as shown in FIG. 1 and performing the examination and approval, it is possible to avoid the trouble of printing the PUI paper document many times compared to the method described later. Further, the added information is digitized every time it is examined and approved, and is managed by the PUI document management server 1 or the like, so that even if the PUI paper document is lost during circulation, there is little trouble.
[0022]
Note that the PUI document management server 1, the workflow server 2, and the MFP 4 may be separate devices or may be mounted in the same device. The same applies to the following.
[0023]
Although not shown in FIG. 1, an authentication server or the like may be connected to the PUI-workflow system and used for user authentication or the like.
[0024]
Hereinafter, another example of examination / approval using the PUI-workflow system will be described with reference to FIG. FIG. 2 is a conceptual diagram (part 2) of the PUI-workflow system according to the embodiment of the present invention.
[0025]
The PUI-workflow system shown in FIG. 2 is similar to FIG. 1 in that the PUI document management server 1, the workflow server 2, at least one MFP 4 and at least one client connected via a network. PC5.
[0026]
In the system shown in FIG. 2, the PUI paper document to which the PUI document ID for identifying the original PUI document file and the PUI user ID for identifying the user are added is read by the MFP 4, and then the next review / approver Is output as a new PUI paper document from the MFP 4 based on the request from the user.
[0027]
As described above, for the PUI paper document image information read by the MFP 4, for example, the PUI document management server 1 separates new writing information such as comments, signatures, and seals. Here, the PUI document management server 1 extracts new difference information by extracting the difference between the image information of the PUI paper document read by the MFP 4 and the addition information of the original electronic document plus the previous examination / approver. Isolate.
[0028]
For example, the PUI document management server 1 manages the retouching information as a PUI document file associated with the original electronic document together with the PUI user ID for identifying the retouching user, the PUI document ID, and the retouching ID for identifying the retouching information. Is done.
[0029]
Compared with the method shown in FIG. 1, the method shown in FIG. 2 does not circulate the PUI paper document, but prints and outputs the PUI paper document from the MFP 4 connected via the network for review / approval. Therefore, although the workflow is based on a paper document, there is little loss of circulation time and a workflow over a remote location can be realized.
[0030]
Hereinafter, another example of examination / approval using the PUI-workflow system will be described with reference to FIG. FIG. 3 is a conceptual diagram (part 3) of the PUI-workflow system according to the embodiment of the present invention.
[0031]
Similar to FIGS. 1 and 2, the PUI-workflow system shown in FIG. 3 includes a PUI document management server 1, a workflow server 2, at least one MFP 4 and at least one connected via a network. The above client PC 5 is included.
[0032]
In the system shown in FIG. 3, the PUI document document to which the PUI document ID for identifying the original PUI document file and the PUI user ID for identifying the user are added is read by the MFP 4, and then the next review / approver If the next reviewer / approver is in a remote location, the MFP 4 scans it and then creates a new PUI paper document based on the request from the next reviewer / approver. It may be printed out from the MFP 4.
[0033]
As described above, for the PUI paper document image information read by the MFP 4, for example, the PUI document management server 1 separates new writing information such as comments, signatures, and seals. Here, the PUI document management server 1 extracts new difference information by extracting the difference between the image information of the PUI paper document read by the MFP 4 and the addition information of the original electronic document plus the previous examination / approver. Isolate.
[0034]
For example, the PUI document management server 1 manages the retouching information as a PUI document file associated with the original electronic document together with the PUI user ID for identifying the retouching user, the PUI document ID, and the retouching ID for identifying the retouching information. Is done.
[0035]
By taking the method shown in Fig. 3, in the same establishment, the paper document itself is circulated and examined / approved. If examination / approval is required in other establishments, the PUI paper document is It can be read by the MFP 4, printed out from the MFP 4 of another office connected via the network, and requested for examination / approval.
[0036]
It should be noted that a user who conducts examination / approval receives an email requesting examination / approval from the workflow server 2 or the like at the client PC 5 and then prints out a PUI paper document printed from the MFP 4 or a PUI paper document received from another user. May be added to the MFP and read into the MFP, or the client PC 5 or the like may be used to perform electronic stamping or the like on the display of the client PC 5 so as to be reviewed and approved.
[0037]
Hereinafter, the hardware configuration of the PUI document management server 1 will be described with reference to FIG. FIG. 4 is a hardware configuration diagram of an example of the PUI document management server.
[0038]
As shown in FIG. 4, the hardware configuration of the PUI document management server 1 includes an input device 11, a display device 12, a drive device 13, a recording medium 14, a ROM ( It comprises a Read Only Memory (RAM) 15, a RAM (Random Access Memory) 16, a CPU (Central Processing Unit) 17, an interface device 18, and an HDD (Hard Disk Drive) 19.
[0039]
The input device 11 includes a keyboard and a mouse operated by a user of the PUI document management server 1 and is used to input various operation signals to the PUI document management server 1.
[0040]
The display device 12 includes a display used by the user of the PUI document management server 1 and displays various types of information.
[0041]
The interface device 18 is an interface that connects the PUI document management server 1 to a network or the like.
[0042]
A server program or the like of the PUI document management server 1 that performs processing related to a PUI-workflow system to be described later is provided to the PUI document management server 1 by a recording medium 14 such as a CD-ROM, or downloaded through a network. The recording medium 14 is set in the drive device 13, and the server program and the like are installed in the ROM 15 from the recording medium 14 via the drive device 13.
[0043]
The ROM 15 stores data, the server program, and the like. The RAM 16 reads and stores the server program and the like from the ROM 15 when the PUI document management server 1 is activated. The CPU 17 executes processing according to the server program read and stored in the RAM 16.
[0044]
The HDD 19 stores data and files.
[0045]
The hardware configuration of the client PC 5, the workflow server 2, the authentication server, the PUI server and the document management server, which will be described later, is the same as the hardware configuration of the PUI document management server 1 shown in FIG.
[0046]
Hereinafter, an example of a functional configuration and a hardware configuration of the MFP 4 will be described with reference to FIGS. 5 and 6.
[0047]
FIG. 5 is a block diagram showing a functional configuration of the MFP.
[0048]
In FIG. 5, the MFP 4 includes a plotter 1201, a scanner 1202, a hardware resource 1203 such as a facsimile, and the like, a software group 1210 including a platform 1220 and an application 1230, and an MFP activation unit 1240. Yes.
[0049]
The MFP activation unit 1240 is executed first when the MFP 4 is turned on, and activates the platform 1220 and the application 1230.
[0050]
The platform 1220 interprets a processing request from the application 1230 and generates a hardware resource acquisition request as described below, manages one or a plurality of hardware resources, and acquires from the control service 1250. It has a system resource manager (SRM (System Resource Manager) 1223) that arbitrates requests, and an OS 1221.
[0051]
The control service 1250 is formed by a plurality of service modules. Specifically, the system control service (SCS) 1222, the engine control service (ECS) 1224, the memory control service (MCS) 1225, and the OCS (Opera) There is a Control Service (2261), an FCS (FAX Control Service) 1227, an NCS (Network Control Service) 1228, and an IMH (Imaging Memory Handler) 1229. The platform 1220 has an application program interface that can receive a processing request from the application using a predefined function.
[0052]
The OS 1221 is an operating system such as UNIX (registered trademark), and executes the software of the platform 1220 and the application 1230 in parallel as processes. By using open source UNIX (registered trademark), the safety of the program can be ensured, the network can be supported, and the source code can be easily obtained. Furthermore, OS and TCP / IP royalties are unnecessary, and outsourcing is easy.
[0053]
The SRM1223 controls the system and manages resources together with the SCS1222, and includes an engine unit such as a scanner and a plotter, a memory, an HDD file, a host I / O (Centronics I / F, a network I / F, an IEEE1394 I / F, RS232CI / F, etc.) arbitration is performed according to a request from a higher layer using hardware resources, and execution control is performed.
[0054]
Specifically, the SRM 1223 determines whether the requested hardware resource is available and exists (whether it is not used by another request). If the requested hardware resource is available, the requested hardware resource is determined. Tell the upper layer that is available. Also, hardware resource usage scheduling may be performed in response to a request from an upper layer, and the requested contents (for example, paper conveyance and image forming operation by the printer engine, memory allocation, file generation, etc.) may be directly executed. .
[0055]
The SCS 1222 includes application management (function 1), operation unit control (function 2), system screen display (job list screen, counter display screen, etc.) (function 3), LED display (function 4), resource management (function 5), A plurality of functions such as interrupt application control (function 6) are performed. Specifically, in application management (function 1), processing for registering an application and notifying other applications of the information is performed. In the operation unit control (function 2), exclusive control of the operation unit use right of the application is performed. In the system screen display (function 3), a warning screen corresponding to the state of the engine unit is displayed according to the request content from the application having the operation unit usage right. In LED display (function 4), display control of system LEDs such as warning LEDs and application keys is performed. Resource management (function 5) provides services for exclusive control of engine resources (scanners, staples, etc.) that must be excluded when an application (ECS) executes a job. In the interrupt application control (function 6), control and service for preferential operation of a specific application are performed.
[0056]
The ECS 1224 controls engine units such as the plotter 1201, the scanner 1202, and other hardware resources 1203, and performs image reading and printing operations, status notification, jam recovery, and the like.
[0057]
The MCS 1225 performs memory control. Specifically, the MCS 1225 acquires and releases an image memory, uses a hard disk device (HDD), compresses and decompresses image data, and the like.
[0058]
The OCS 1226 is a module that controls an operation panel serving as information transmission means between the operator and the main body control, and provides a process for notifying the main body control of an operator's key operation event and a library function for each application to construct a GUI. Processing, processing for managing the constructed GUI information for each application, display reflection processing on the operation panel, and the like are performed.
[0059]
FCS 1227 performs facsimile transmission / reception using the PSTN / ISDN network from each application layer of the system controller, registration / quotation of various facsimile data managed by BKM (backup SRAM), facsimile reading, facsimile reception printing, and fusion transmission / reception. API (Application Program Interface) 1205 is provided.
[0060]
The NCS 1228 is a module group for providing a service that can be commonly used for applications that require network I / O. The NCS 1228 distributes data received by each protocol from the network side to each application, and distributes data from the application. Mediating when sending to the network side.
[0061]
The IMH 1229 maps image data from a virtual memory area (user virtual space) to a physical memory. In response to process activation, a system call is performed to map a virtual memory area for the process, or to perform processing such as releasing the mapped virtual memory area at the end of the process.
[0062]
The application 1230 includes a printer application 1211 that is a printer application having a page description language (PDL), PCL, and postscript (PS), a copy application 1212 that is a copy application, and a fax application 1213 that is a facsimile application. , A scanner application 1214 that is a scanner application, and a PUI application 1215 that is a PUI application. Since each application 1211 to 1215 can execute an operation by using each process on the platform 1220, a screen display control program for performing screen control, key operation control, job generation, and the like is the main component. Note that a new application can also be installed via the network via the network connected by the NCS 1228. Each application can be added or deleted for each application.
[0063]
The PUI application 1215, for example, from the read PUI paper document, the PUI document ID and / or the PUI user ID and / or the MFP-ID for identifying the MFP 4 and / or the retouching ID for identifying the retouching information (hereinafter simply referred to as the PUI). And also provided to the PUI document management server 1 or the like, or the PUI document file acquired from the PUI document management server 1 or the like and the PUI mark are combined.
[0064]
Note that functions such as the PUI document management server 1 and / or the workflow server 2 may be installed in the MFP 4. In such a configuration, an application that provides each function is installed in the application 1230. Further, as described later, the MFP 4 does not have a special application such as the PUI application 1215 and transmits the read PUI paper document to the PUI document management server 1 or the like to acquire the PUI mark in the PUI document management server 1 or A PUI mark may be combined with a document file.
[0065]
The MFP 4 performs centralized processing on the platform 1220 for processing commonly required by each application.
[0066]
FIG. 6 is a block diagram illustrating a hardware configuration of the MFP.
[0067]
As shown in FIG. 6, the MFP 4 includes an operation panel 1310, a FAX control unit (FCU) 1530, an engine unit 1350 (to which a scanner 1202 and the like are connected), a plotter 1201, and an ASIC 1301 of the controller 1300 connected to the PCI (Peripheral Component Interconnect). ) Connected by a bus 1309 or the like.
[0068]
The controller 1300 connects the ASIC 1301 to the MEM-C 1302, HDD (Hard Disk Drive) 1303, and the like, and connects the ASIC 1301 and the CPU 1304 via the NB 1305 of the CPU chipset. Thus, the reason for connecting via the NB 1305 is that the interface of the CPU 1304 itself is not disclosed.
[0069]
Here, the ASIC 1301 and the NB 1305 are not connected via the PCI, but are connected via the AGP 1308. The reason for the connection via the AGP 1308 is that the MFP 4 is connected by a low-speed PCI because of the execution control of a plurality of processes forming the platform 1220 and the application 1230 shown in FIG. This is because the performance deteriorates.
[0070]
The CPU 1304 performs overall control of the MFP 4. Specifically, the SCS 1222, SRM 1223, ECS 1224, MCS 1225, OCS 1226, FCS 1227, and NCS 1228 that form the platform 1220 on the OS 1221 are started and executed as processes, respectively. The printer application 1211, the copy application 1212, the fax application 1213, the scanner application 1214, and the PUI application 1215 forming the application 1230 are activated and executed.
[0071]
The NB 1305 is a bridge for connecting the CPU 1304, the MEM-P 1306, the SB 1307, the NIC (Network Interface Card) 1341, the USB (Universal Serial Bus) 1330, the IEEE 13941340, the Centronics 1342, and the ASIC 1301.
[0072]
The MEM-P 1306 is a system memory used as a drawing memory or the like of the MFP 4, and the SB 1307 is a bridge for connecting the NB 1305 to the ROMPCI device and peripheral devices. The MEM-C 1302 is a local memory used as an image buffer for copying and a code buffer, and the ASIC 1301 is an IC for image processing applications having hardware elements for image processing.
[0073]
The HDD 1303 is a storage that stores image data, programs, font data, forms, and documents. The operation panel 1310 receives input operations from the operator and displays them for the operator. It is an operation part which performs.
[0074]
The ASIC 1301 is provided with a RAM interface for connecting the MEM-C 1302 and a hard disk interface for connecting the HDD 1303. When inputting / outputting image data to / from these storage units, the input / output destination is Switching to a RAM interface or a hard disk interface.
[0075]
The AGP 1308 is a bus interface for a graphics accelerator card that has been proposed to speed up graphics processing, and makes the graphics accelerator card faster by directly accessing the system memory with high throughput.
[0076]
Hereinafter, an example of the PUI mark added to the PUI paper document will be described with reference to FIG. FIG. 7 is a diagram for explaining an example of the PUI mark.
[0077]
As shown in FIG. 7, the PUI paper document includes a document-specific code (PUI document ID) for identifying the original PUI document file, a user-specific code (PUI user ID) for identifying the user, and the PUI paper document. A code unique to the MFP 4 (MFP-ID) for identifying the MFP 4 that has permitted and / or performed reading and / or printing, and a page number are added.
[0078]
Note that, for example, YYYYYY / ZZZZZZ shown in FIG. 7 may be used as the user ID in association with the PUI user ID and the MFP-ID. By doing so, it is possible to designate a user who can read and / or print a PUI paper document in a predetermined MFP 4.
[0079]
Further, by adding a page number, it is possible to determine which page is the same even in the same PUI document file.
[0080]
Although not shown in FIG. 7, the PUI mark may include a rewriting ID for identifying rewriting information.
[0081]
Hereinafter, an example of the structure of the PUI document file will be described with reference to FIG. FIG. 8 is a diagram (part 1) for explaining the structure of the PUI document file.
[0082]
As shown in FIG. 8, the PUI document file is composed of a document property and an original image, and a writing property and a writing image are added each time writing information is added.
[0083]
The document properties include a document ID (PUI document ID), a title, a creator (PUI user ID), a creation date, and an access right for the PUI document file. Further, the writing property includes a document ID (PUI document ID), a writing ID, a parent writing ID, a writing person (PUI user ID), and a writing date of the writing target document.
[0084]
For example, the first retouched image shown in FIG. 8 includes the first examiner's retouched data, and the second rewritten image includes the second examiner's retouched data.
[0085]
Hereinafter, another example of the structure of the PUI document file will be described with reference to FIG. FIG. 9 is a diagram (part 2) for explaining the structure of the PUI document file.
[0086]
The structure of the PUI document file shown in FIG. 9 is a structure in which original image data exists for each page, compared to the structure of the PUI document file described in FIG. Further, the structure of the PUI document file shown in FIG. 9 is a structure in which a retouched image with respect to the original image for each page exists.
[0087]
For simplification of explanation, FIG. 9 shows only two pages in the structure of the PUI document file, but this does not limit the implementation of the present invention.
[0088]
Hereinafter, another example of the structure of the PUI document file will be described with reference to FIG. FIG. 10 is a diagram (No. 3) for explaining the structure of the PUI document file.
[0089]
The structure of the PUI document file shown in FIG. 10 is a structure having data related to the original application file, for example, the data of the text file itself that created the original, compared to the structure of the PUI document file described in FIG. ing.
[0090]
As shown in FIG. 10, by including data related to the original application file in the PUI document file, the original application file is extracted from the PUI document file and used by using a predetermined application that handles the PUI document file. be able to.
[0091]
Hereinafter, another example of the structure of the PUI document file will be described with reference to FIG. FIG. 11 is a diagram (No. 4) for explaining the structure of the PUI document file.
[0092]
The structure of the PUI document file shown in FIG. 11 includes an original application, for example, a program such as a Java (registered trademark) applet, as compared with the structure of the PUI document file described in FIG.
[0093]
By including the original application in the PUI document file, it is possible to launch and use the original application using a predetermined application that handles the PUI document file.
[0094]
Hereinafter, an example of contraction of the PUI document file will be described with reference to FIG. FIG. 12 is a diagram for explaining an example of contraction of a PUI document file.
[0095]
As shown in FIG. 3, the PUI document management server 1 or the MFP 4 reflects the retouched image in the original image as shown in FIG. 12, for example, when it becomes necessary to circulate the PUI document file in another office or the like. The reduced PUI document file is transmitted to the MFP 4 or the like of another office as an original.
[0096]
By transmitting the reduced PUI document file as a new original to another office or the like, the PUI document file can be transmitted without imposing a load on the network. It should be noted that the rewritten property before the contraction may be reflected on the document property before the contraction to obtain a new document property.
[0097]
As shown in FIGS. 8 to 12, the PUI document file may be stored and / or managed in the PUI document file management unit 25 described later in the form of a compound document, or stored in a database table. And / or may be managed. In the following, an example of storing and / or managing the original and / or additional information of a PUI document file in a table will be described with reference to FIGS.
[0098]
FIG. 13 is a diagram for explaining an example of a table related to the original PUI document file.
[0099]
As shown in FIG. 13A, the PUI document property table includes a document ID, a title, a creation date, a creator, an access right, and a file name as items.
[0100]
The document ID stores, for example, a PUI document ID that identifies the PUI document file. Note that a document ID corresponding to the PUI document ID may be stored. The title stores the title of the PUI document file. The creation date stores the creation date when the PUI document file is created. In the creator, the PUI user ID of the creator who created the PUI document file is stored. In FIG. 13, the name of the creator is stored as it is for the sake of simplicity. The access right stores the PUI user ID of the user who has permitted access to the PUI document file. In FIG. 13, a user name and the like are simply stored for simplification of description. The file name stores the file name of the PUI document file.
[0101]
Further, as shown in FIG. 13B, the PUI document original image table includes a document ID, a page number, and a file name as items.
[0102]
The document ID stores, for example, a PUI document ID that identifies the PUI document file. Note that a document ID corresponding to the PUI document ID may be stored. The page number stores the page number of the PUI document file. The file name stores the file name of the PUI document file associated with the page number.
[0103]
FIG. 14 is a diagram for explaining an example of a table related to the writing information.
[0104]
As shown in FIG. 14A, the PUI retouching property table includes a document ID, a rewriting ID, a parent rewriting ID, a rewriting date, and a rewriter as items.
[0105]
The document ID stores, for example, a PUI document ID that identifies the PUI document file. Note that a document ID corresponding to the PUI document ID may be stored. In the writing ID, an identifier for identifying the writing information is stored. The parent rewriting ID stores identification information for identifying parent rewriting information. The date when the retouching information is extracted is stored as the retouching date. The writer stores the PUI user ID of the writer who performed the writing. In FIG. 14, the name of the author is stored as it is for the sake of simplicity.
[0106]
By including the document ID, the writing ID, and the parent writing ID in the PUI writing property table, the relationship between the writing information can be expressed as shown in FIG. FIG. 15 is a diagram for explaining the relationship between the writing information. For example, FIG. 15 shows that the rewriting information identified by the rewriting IDA3 is rewriting to the rewriting information identified by the rewriting IDA2.
[0107]
Further, as shown in FIG. 14B, the PUI retouching image table includes a document ID, a retouching ID, a page number, and a file name as items.
[0108]
The document ID stores, for example, a PUI document ID that identifies the PUI document file. Note that a document ID corresponding to the PUI document ID may be stored. In the writing ID, an identifier for identifying the writing information is stored. The page number stores the page number of the PUI document file. The file name stores the file name of the PUI document file associated with the page number.
[0109]
Hereinafter, another example of the table relating to the PUI document file will be described with reference to FIG. FIG. 16 is a diagram for explaining another example of the table relating to the PUI document file.
[0110]
As shown in FIG. 16, the PUI document table includes a document ID, a title, a creation date, a creator, an access right, and a URL as items.
[0111]
The document ID stores, for example, a PUI document ID that identifies the PUI document file. Note that a document ID corresponding to the PUI document ID may be stored. The title stores the title of the PUI document file. The creation date stores the creation date when the PUI document file is created. In the creator, the PUI user ID of the creator who created the PUI document file is stored. In FIG. 16, the name of the creator is stored as it is for the sake of simplicity. The access right stores the PUI user ID of the user who has permitted access to the PUI document file. In FIG. 16, the user name and the like are simply stored for the sake of simplicity. In the URL, a URL indicating the location of the PUI document file is stored.
[0112]
As shown in FIG. 16, the PUI document file can be stored and / or managed in one table without being divided into the property table and the original image table.
[0113]
As described with reference to FIGS. 8 to 16, the original data related to the PUI paper document, for example, the original image and the document property, the additional data related to the writing, and the attribute information related to the attribute of the additional data are associated with each other. By managing the PUI paper document, the system related to the PUI paper document and the workflow management system in which a plurality of workflow staff members add a plurality of times to the same document can be operated in association with each other.
[0114]
Hereinafter, an example of the external representation of the PUI document file will be described with reference to FIG. FIG. 17 is a diagram for explaining an example of an external representation of a PUI document file.
[0115]
As will be described later, for example, the PUI document management server 1 has only the PUI document file management unit 25 that manages the PUI document file, and the MFP 4 updates the retouched image extraction unit 24 that extracts the retouched image and the PUI document file. When the PUI document file update unit 23 that performs the above and the like is included, the PUI document management server 1 transmits the PUI document file to the MFP 4 with an input / output data structure as shown in FIG. 17 based on a request from the MFP 4 or the like. Conversely, the PUI document file having the input / output data structure as shown in FIG. 17 transmitted from the MFP 4 or the like is received, stored and / or managed.
[0116]
For example, data and / or information related to the original PUI document file is embedded in a tag of <original></original> shown in FIG. For example, image data relating to the original PUI document file encoded in base 64 is embedded in a tag of <image></image> in a tag of <original></original>. Also, attribute information relating to the original PUI document file is embedded in a tag of <propList></propList> in a tag of <original></original>. For example, a document ID (PUI document ID) is embedded in a tag of <docId></docId>. Also, the title of the PUI document file is embedded in the <title></title> tag. The <date></date> tag is embedded with the creation date when the PUI document file was created.
[0117]
Further, the added rewriting information described in FIG. 8 and the like is embedded in the tag <layer></layer> shown in FIG. For example, the <image></image> tag in the <layer></layer> tag embeds base 64 encoded retouched image data (retouched image data). Also, attribute information related to the retouched image data is embedded in the <propList></propList> tag in the <layer></layer> tag. For example, in the tag <layerId></layerId>, a rewriting ID for identifying the retouched image data is embedded. In addition, the date on which the writing information is extracted is embedded in the tag of <date></date>.
[0118]
By sending and receiving a PUI document file with an input / output data structure as shown in FIG. 17, it is possible to provide a system related to a PUI that is compatible with the workflow system.
[0119]
Hereinafter, a relationship diagram between classes representing the PUI-workflow system will be described with reference to FIG. FIG. 18 is a relationship diagram between classes representing the PUI-workflow system.
[0120]
As shown in FIG. 18, the class representing the PUI-workflow system includes an image input class, an ID detection class, a PUI document file update class, a retouched image extraction class, and a PUI document file management class.
[0121]
The image input class is a class that defines reading (input) of a PUI paper document to which additional information is added. The ID detection class is a class that defines ID detection. Examples of the ID include a PUI document ID, a PUI user ID, an MFP-ID, and a writing ID. The PUI document file update class is a class that defines the update of the PUI document file. The retouched image extraction class is a class that defines extraction of a retouched image. The PUI document file management class is a class that defines management of the PUI document file.
[0122]
Hereinafter, an example of a method possessed by each class will be described with reference to FIG. FIG. 19 is a diagram for explaining an example of a method.
[0123]
As shown in FIG. 19A, the ID detection class has an addImage method. The addImage method is called with the image data read in the image input class and the user name (PUI user ID) input by the user using the operation panel 1310 of the MFP 4 as arguments, and the PUI document ID included in the image data. Or a PUI user ID, and if included, a writing ID or the like is detected, and the detected ID is returned as a return value.
[0124]
Also, as shown in FIG. 19B, the PUI document file update class has an update method. The update method is called by using the PUI document ID and / or retouching ID detected in the addImage method, the image data, and the user name as arguments, and using the PUI document ID and / or the retouching ID as arguments, as shown in FIG. Call the getFile method of the PUI document file management class shown in (D). The getFile method acquires a corresponding PUI document file managed in the PUI document file management class based on the PUI document ID and / or the additional ID, and returns it as a return value. Note that the user name in the argument of the update method may be the PUI user ID detected in the addImage method.
[0125]
The update method uses the image data passed as the argument and the image data created based on the PUI document file acquired as the return value of the getFile method as arguments, and the retouched image extraction class shown in FIG. The extract method is called. The extract method extracts the difference between the two image data passed as the argument, sets the difference between the image data as a retouched image, and returns it as a return value. The update method uses the image data passed as the argument as the targetImageData shown in FIG. 19C, and the image data created based on the PUI document file acquired as the return value of the getFile method. The extract method is called as the originalImageData shown in (C).
[0126]
The update method adds the retouched image acquired as the return value of the extract method to the PUI document file acquired as the return value of the getFile method, for example, as shown in FIG. In addition, the update method adds the PUI user ID and the writing ID passed as arguments to the PUI document file as a writing property of the writing image.
[0127]
Further, the update method is a PUI document file shown in FIG. 19D with the PUI document file to which the retouched image and the retouching property are added, the retouching ID, and the PUI document ID passed as an argument as arguments. Call the putFile method of the management class.
[0128]
The putFile method associates the PUI document file, the writing ID, and the PUI document ID together based on the given argument and saves them in the PUI document file management class.
[0129]
Hereinafter, an example of a functional configuration of the PUI-workflow system will be described with reference to FIG. FIG. 20 is a diagram for explaining an example of a functional configuration of the PUI-workflow system.
[0130]
As illustrated in FIG. 20, the PUI-workflow system includes an image input unit 21, an ID detection unit 22, a PUI document file update unit 23, a retouched image extraction unit 24, and a PUI document file management unit 25. .
[0131]
The image input unit 21 reads a PUI paper document to which additional information is added. The ID detection unit 22 detects and acquires PUI marks such as a PUI document ID, a PUI user ID, and a writing ID from the image data read by the image input unit 21. The PUI document file update unit 23 acquires the corresponding PUI document file from the PUI document file management unit 25 based on the acquired PUI document ID and / or additional ID detected by the ID detection unit 22, and the latest PUI document. Image data of the file is created and transferred to the added image extraction unit 24 together with the image data read by the image input unit 21.
[0132]
The retouched image extraction unit 24 extracts the difference between the two passed image data, generates retouched image data, and passes it to the PUI document file update unit 23. The PUI document file update unit 23 adds the retouched image data acquired from the retouched image extraction unit 24 to the end of the PUI document file acquired from the PUI document file management unit 25, and the retouch property corresponding to the retouched image data, The PUI document file managed by the PUI document file management unit 25 is updated.
[0133]
Note that the contraction described in FIG. 12 may be performed by the PUI document file update unit 23, or although not illustrated, a contraction unit or the like may be provided and performed by the contraction unit. .
[0134]
Hereinafter, the functional configuration of each apparatus constituting the PUI-workflow system will be described with reference to FIGS.
[0135]
FIG. 21 is a diagram (No. 1) for describing a functional configuration of each device configuring the PUI-workflow system.
[0136]
The configuration shown in FIG. 21 is a configuration in which the MPF 4 has all the functional configurations described in FIG. In the case of the configuration shown in FIG. 21, the PUI document management server 1 or the like is not necessary in the PUI-workflow system described with reference to FIGS. 1 to 3. For example, the PUI document file is managed in each MFP 4.
[0137]
Hereinafter, another example of the functional configuration of each device constituting the PUI-workflow system will be described with reference to FIG. FIG. 22 is a diagram (No. 2) for describing a functional configuration of each device configuring the PUI-workflow system.
[0138]
The MFP 4 shown in FIG. 22 includes an image input unit 21, an ID detection unit 22, a PUI document file update unit 23, and a retouched image extraction unit 24. The PUI document management server 1 shown in FIG. 22 includes a PUI document file management unit 25.
[0139]
The configuration illustrated in FIG. 22 is configured such that the PUI document file management unit 25 is included in the PUI document management server 1 as compared to the configuration illustrated in FIG. With the configuration as shown in FIG. 22, the PUI document file can be centrally managed in the PUI document management server 1.
[0140]
Hereinafter, another example of the functional configuration of each device constituting the PUI-workflow system will be described with reference to FIG. FIG. 23 is a diagram (No. 3) for describing a functional configuration of each device that configures the PUI-workflow system.
[0141]
The MFP 4 shown in FIG. 23 includes an image input unit 21 and an ID detection unit 22. The PUI document management server 1 shown in FIG. 23 includes a PUI document file update unit 23, a retouched image extraction unit 24, and a PUI document file management unit 25.
[0142]
The configuration shown in FIG. 23 is a configuration in which the PUI document file update unit 23 and the retouched image extraction unit 24 are included in the PUI document management server 1 as compared to the configuration shown in FIG. With the configuration as shown in FIG. 23, main processing relating to the PUI document file such as extraction of a retouched image and update of the PUI document file can be performed collectively in the PUI document management server 1.
[0143]
Hereinafter, another example of the functional configuration of each device configuring the PUI-workflow system will be described with reference to FIG. FIG. 24 is a diagram (No. 4) for describing a functional configuration of each device included in the PUI-workflow system.
[0144]
The MFP 4 shown in FIG. 24 includes an image input unit 21 and an ID detection unit 22. The PUI server shown in FIG. 24 includes a PUI document file update unit 23 and a retouched image extraction unit 24. The document management server shown in FIG. 24 includes a PUI document file management unit 25.
[0145]
The configuration shown in FIG. 24 divides the PUI document management server 1 into a PUI server and a document management server, compared to the configuration shown in FIG. With the configuration shown in FIG. 24, the management of the PUI document file is left to the document management server, and processing related to the PUI document file, such as extraction of a retouched image and update of the PUI document file, is efficiently performed in the PUI server. Can be done.
[0146]
Hereinafter, another example of the functional configuration of each device configuring the PUI-workflow system will be described with reference to FIG. FIG. 25 is a diagram (No. 5) for explaining a functional configuration of each device included in the PUI-workflow system.
[0147]
The MFP 4 shown in FIG. 25 includes an image input unit 21. 25 includes an ID detection unit 22, a PUI document file update unit 23, a retouched image extraction unit 24, and a PUI document file management unit 25.
[0148]
The configuration shown in FIG. 25 is a configuration in which the PUI document management server 1 has the ID detection unit 22 as compared to the configuration shown in FIG. With the configuration shown in FIG. 25, the MFP 4 transmits the read data and / or information to the PUI document management server 1 to detect the PUI mark, extract the added image, update the PUI document file, and update the PUI. All processes related to PUI, such as management of document files, can be performed in the PUI document management server 1.
[0149]
Hereinafter, an example of processing according to the PUI-workflow system will be described with reference to FIG. FIG. 26 is a flowchart for explaining an example of processing according to the PUI-workflow system.
[0150]
In step S10, the image input unit 21 reads a paper document. Progressing to step S11 following step S10, the image input unit 21 acquires user information such as a user name input by the user, for example.
[0151]
Progressing to step S12 following step S11, the ID detection unit 22 determines whether or not a PUI mark is included in the image data related to the paper document read in step S10. If the ID detection unit 22 determines that the PUI mark is included (YES in step S12), the process proceeds to step S15. If the ID detection unit 22 determines that the PUI mark is not included (NO in step S12), the process proceeds to step S13.
[0152]
For example, the ID detection unit 22 reads information added at a predetermined position of the image data related to the paper document read in step S10, and determines whether the information is a PUI mark, thereby reading it in step S10. It is determined whether the PUI mark is included in the image data related to the paper document.
[0153]
In step S13, the user information acquired in step S11 is added to the image data related to the paper document read in step S10 by the PUI document file update unit 23 or the PUI document file creation unit that creates the PUI document file (not shown). Etc. are added to create a new PUI document file.
[0154]
Progressing to step S14 following step S13, the PUI document file update unit 23 or the PUI document file registration unit that registers the PUI document file (not shown) manages the PUI document file created in step S13 as PUI document file management. Register in the unit 25.
[0155]
On the other hand, in step S15, the PUI document file update unit 23 or the authentication unit (not shown), based on the user information acquired in step S11 and / or the PUI user ID included in the PUI mark read in step S12, For example, it is determined whether the corresponding user has an access right to access the corresponding PUI document file.
[0156]
If the PUI document file update unit 23 or the authentication unit determines that the user has an access right to access the corresponding PUI document file (YES in step S15), the process proceeds to step S16 to access the corresponding PUI document file. If it is determined that there is no access right (NO in step S15), the process is terminated.
[0157]
For example, the PUI document file update unit 23 or the authentication unit includes the user information acquired in step S11 and / or the PUI user ID included in the PUI mark read in step S12, and the PUI document included in the PUI mark read in step S12. An access right confirmation request including an ID or the like is made to the PUI document file management unit 25, and for example, the user corresponding to the user information and / or the PUI user ID is accessed to the PUI document file corresponding to the PUI document ID. The confirmation result as to whether or not there is an access right to be acquired is acquired from the PUI document file management unit 25. The PUI document file updating unit 23 or the authentication unit determines whether the user has an access right to access the PUI document file based on the confirmation result.
[0158]
In step S <b> 16, the PUI document file update unit 23 acquires a corresponding PUI document file from the PUI document file management unit 25 based on the PUI document ID and the like included in the PUI mark read in step S <b> 12.
[0159]
Progressing to step S17 following step S16, the retouched image extraction unit 24 calculates the difference between the image data related to the paper document read in step S10 and the image data related to the PUI document file acquired in step S16, Extract image data.
[0160]
Progressing to step S18 following step S17, the PUI document file updating unit 23 adds the retouched image data extracted in step S17 and the retouching property corresponding to the retouched image data to the PUI document file acquired in step S16. The PUI document file is updated, and the newly updated PUI document file is stored in the PUI document file management unit 25. The writing properties include a writing ID for identifying the writing image data, a PUI user ID of the user who performed the writing, and the like.
[0161]
The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to such specific embodiments, and various modifications can be made within the scope of the gist of the present invention described in the claims.・ Change is possible.
[0162]
【The invention's effect】
As described above, according to the present invention, the system relating to the PUI paper document and the workflow management system can be operated in association with each other.
[0163]
[Brief description of the drawings]
FIG. 1 is a conceptual diagram (part 1) of a PUI-workflow system according to an embodiment of the present invention.
FIG. 2 is a conceptual diagram (part 2) of the PUI-workflow system according to the embodiment of the present invention.
FIG. 3 is a conceptual diagram (part 3) of the PUI-workflow system according to the embodiment of the present invention.
FIG. 4 is a hardware configuration diagram of an example of a PUI document management server.
FIG. 5 is a block diagram illustrating a functional configuration of the MFP.
FIG. 6 is a block diagram illustrating a hardware configuration of the MFP.
FIG. 7 is a diagram for explaining an example of a PUI mark.
FIG. 8 is a diagram (part 1) for explaining the structure of a PUI document file;
FIG. 9 is a diagram (No. 2) for explaining the structure of a PUI document file;
FIG. 10 is a diagram (No. 3) for explaining the structure of a PUI document file;
FIG. 11 is a diagram (No. 4) for explaining the structure of a PUI document file;
FIG. 12 is a diagram for explaining an example of contraction of a PUI document file.
FIG. 13 is a diagram for explaining an example of a table related to an original PUI document file.
FIG. 14 is a diagram for describing an example of a table related to writing information.
FIG. 15 is a diagram for explaining a relationship between writing information.
FIG. 16 is a diagram for explaining another example of a table related to a PUI document file.
FIG. 17 is a diagram for explaining an example of an external representation of a PUI document file.
FIG. 18 is a relationship diagram between classes representing a PUI-workflow system.
FIG. 19 is a diagram for explaining an example of a method.
FIG. 20 is a diagram for explaining an example of a functional configuration of a PUI-workflow system.
FIG. 21 is a diagram (No. 1) for describing a functional configuration of each device that configures the PUI-workflow system;
FIG. 22 is a diagram (No. 2) for describing a functional configuration of each device that configures the PUI-workflow system;
FIG. 23 is a diagram (No. 3) for describing a functional configuration of each device that configures the PUI-workflow system;
FIG. 24 is a diagram (No. 4) for describing a functional configuration of each device that configures the PUI-workflow system;
FIG. 25 is a diagram (No. 5) for explaining a functional configuration of each device included in the PUI-workflow system;
FIG. 26 is a flowchart for explaining an example of processing according to the PUI-workflow system;
[Explanation of symbols]
1 PUI document management server
2 Workflow server
4 MFP (Multi Function Printer)
5 Client PC
21 Image input section
22 ID detector
23 PUI document file update section
24 Retouched image extraction unit
25 PUI document file management department

Claims (16)

A document file management class for managing document files related to the process;
A retouching data extraction class that extracts retouching data;
A document file management apparatus for managing a document file related to a process using an object-oriented model having a document file update class for updating the document file related to the process. The document file management apparatus according to claim 1, wherein the document file update class and the additional data extraction class are related to each other. 3. The document file management apparatus according to claim 1, wherein the document file update class and the document file management class are related to each other. 4. The document file management apparatus according to claim 1, further comprising an identification information detection class for detecting identification information. 5. The document file management apparatus according to claim 4, wherein the identification information detection class and the document file update class are related to each other. 6. The document file management apparatus according to claim 1, further comprising a document reading class for reading a document. The document file management apparatus according to claim 6, wherein the document reading class and the identification information detection class are related to each other. 8. The document according to claim 4, wherein the identification information detection class has an identification information detection method for detecting identification information included in the data based on data passed as an argument. File management device. The document according to any one of claims 1 to 8, wherein the retouched data extraction class has a difference extraction method for extracting a difference between the two data based on the two data passed as arguments. File management device. The document file update class is based on the data related to the document file to which the additional data passed as an argument is added and the document identification information related to the document file and / or the additional identification information related to the additional data. The document file management apparatus according to claim 1, further comprising a document file update method for updating a document file. The document file management class has a document file acquisition method for acquiring a corresponding document file based on document identification information related to the document file passed as an argument and / or additional identification information related to the additional data. The document file management apparatus according to claim 1, wherein the document file management apparatus is a document file management apparatus. The document file management class stores the updated document file based on the updated document file passed as an argument and the document identification information related to the document file and / or the additional identification information related to the additional data. The document file management apparatus according to claim 1, further comprising: a document file storage method for performing the process. A data structure related to input / output of a document file related to a process,
Original data relating to the original of the document file;
Original attribute information related to the original data;
A data structure comprising: retouched data relating to retouching added in the steps constituting the process. 14. The data structure according to claim 13, further comprising additional attribute information related to the additional data. 15. The data structure according to claim 13, wherein the data structure is described in a meta language and / or a markup language. 16. The data structure according to claim 13, wherein the data structure is described in XML.

Images