US11507536B2 - Information processing apparatus and non-transitory computer readable medium for selecting file to be displayed - Google Patents

Information processing apparatus and non-transitory computer readable medium for selecting file to be displayed Download PDF

Info

Publication number
US11507536B2
US11507536B2 US17/011,245 US202017011245A US11507536B2 US 11507536 B2 US11507536 B2 US 11507536B2 US 202017011245 A US202017011245 A US 202017011245A US 11507536 B2 US11507536 B2 US 11507536B2
Authority
US
United States
Prior art keywords
file
job
storage region
displayed
file storage
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US17/011,245
Other languages
English (en)
Other versions
US20210216503A1 (en
Inventor
Junko MURAKAMI
Yasuhiro Ito
Tomoyuki Shimizu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fujifilm Business Innovation Corp
Original Assignee
Fujifilm Business Innovation Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Fujifilm Business Innovation Corp filed Critical Fujifilm Business Innovation Corp
Publication of US20210216503A1 publication Critical patent/US20210216503A1/en
Application granted granted Critical
Publication of US11507536B2 publication Critical patent/US11507536B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482—Interaction with lists of selectable items, e.g. menus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/168—Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/14—Details of searching files based on file metadata
    • G06F16/148—File search processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/172—Caching, prefetching or hoarding of files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/188—Virtual file systems
    • G06F16/192—Implementing virtual folder structures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04812—Interaction techniques based on cursor appearance or behaviour, e.g. being affected by the presence of displayed objects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units

Definitions

  • the present disclosure relates to an information processing apparatus and a non-transitory computer readable medium.
  • job document management is performed as follows. A folder is created for each job and documents are stored in the corresponding folders. Sometimes, multiple folders are created for each job in a hierarchical structure and documents are stored in the corresponding folders, thereby sorting the documents in greater detail.
  • files to be displayed in response to an operation for displaying files are fixed.
  • the first four image files are always displayed.
  • Files to be displayed are not changed in accordance with the status of a job.
  • Non-limiting embodiments of the present disclosure relate to an information processing apparatus and a non-transitory computer readable medium in which, in response to an operation for displaying a display element indicating files stored in a file storage region created for a job, files to be displayed are selected from among the files stored in the file storage region in accordance with the status of the job.
  • aspects of certain non-limiting embodiments of the present disclosure overcome the above disadvantages and/or other disadvantages not described above.
  • aspects of the non-limiting embodiments are not required to overcome the disadvantages described above, and aspects of the non-limiting embodiments of the present disclosure may not overcome any of the disadvantages described above.
  • an information processing apparatus which is able to access a file storage region.
  • the file storage region is formed in accordance with job defining information that defines tasks of a job and a file to be created in each of the tasks.
  • the file storage region is formed for each job or each job and each task.
  • a file related to a job or a task is stored in a corresponding file storage region.
  • the information processing apparatus includes a processor.
  • the processor is configured to: obtain job status information concerning a status of each job for which a file storage region is formed; and select, in response to an operation for displaying a display element indicating files stored in a first file storage region, a file as a subject file to be displayed, from among the files stored in the first file storage region, in accordance with the status of a first job corresponding to the first file storage region, the status of the first job being obtained from the job status information.
  • FIG. 1 is a schematic block diagram illustrating a file management system according to a first exemplary embodiment
  • FIG. 2 illustrates an example of the data structure of job management information in the first exemplary embodiment
  • FIG. 3A schematically illustrates the status of job case 1 in the first exemplary embodiment
  • FIG. 3B illustrates the configuration of folders and documents created in accordance with job case 1 in the first exemplary embodiment
  • FIG. 3C schematically illustrates the status of job case 2 in the first exemplary embodiment
  • FIG. 3D illustrates the configuration of folders and documents created in accordance with job case 2 in the first exemplary embodiment
  • FIG. 4 is a flowchart illustrating display processing according to the first exemplary embodiment
  • FIG. 5 illustrates an example of the display screen of a client personal computer (PC).
  • PC personal computer
  • FIG. 6A schematically illustrates the status of job case 1 in a second exemplary embodiment
  • FIG. 6B illustrates the configuration of folders and documents created in accordance with job case 1 in the second exemplary embodiment
  • FIG. 6C schematically illustrates the status of job case 2 in the second exemplary embodiment
  • FIG. 6D illustrates the configuration of folders and documents created in accordance with job case 2 in the second exemplary embodiment
  • FIG. 7A schematically illustrates the status of job case 1 in a third exemplary embodiment
  • FIG. 7B illustrates the configuration of folders and documents created in accordance with job case 1 in the third exemplary embodiment
  • FIG. 7C schematically illustrates the status of job case 2 in the third exemplary embodiment
  • FIG. 7D illustrates the configuration of folders and documents created in accordance with job case 2 in the third exemplary embodiment
  • FIG. 8 illustrates another example of the display screen of the client PC.
  • FIG. 1 is a schematic block diagram illustrating a file management system according to a first exemplary embodiment.
  • FIG. 1 includes a display control device 1 , a job management server 2 , a database (DB) server 3 , a user management server 4 , and a client personal computer (PC) 5 .
  • Each of the display control device 1 , the job management server 2 , the DB server 3 , and the user management server 4 is a system for providing services concerning files, such as documents, to a user using the client PC 5 .
  • the first exemplary embodiment will be explained, assuming that documents created in certain jobs are handled as files.
  • the file management system in the first exemplary embodiment is implemented by cloud computing, for example.
  • the file management system may be implemented in the configuration other than that by cloud computing, in accordance with the scale or the usage situation of the file management system.
  • a single server may serve as the display control device 1 , the job management server 2 , the DB server 3 , and the user management server 4 .
  • the client PC 5 is implemented by the hardware configuration of a general-purpose PC including a central processing unit (CPU), a read only memory (ROM), a random access memory (RAM), a storage, a communication interface, and a user interface.
  • the client PC 5 refers to a file (document) managed by the DB server 3 via the display control device 1 .
  • a mouse is used as a user input interface.
  • Each of the job management server 2 , the DB server 3 , and the user management server 4 may be implemented by the hardware configuration of a general-purpose server computer. That is, the job management server 2 , the DB server 3 , and the user management server 4 may each include a CPU, a ROM, a RAM, a storage, such as a hard disk drive (HDD), and a communication interface. They may also include a user interface for allowing an administrator, for example, to manage information.
  • a CPU central processing unit
  • ROM read-only memory
  • RAM random access memory
  • storage such as a hard disk drive (HDD)
  • HDD hard disk drive
  • the job management server 2 is a server computer that manages information concerning jobs.
  • the job management server 2 includes a job template DB 21 and a job management information DB 22 .
  • a job template is job defining information that defines tasks of a job and types of files to be created in each task of a job. It is not always necessary to determine the order in which tasks of a job are executed. The first exemplary embodiment will be explained, however, assuming that tasks of a job are executed in chronological order. In the following description, “steps”, which form a procedure of tasks, will be used as tasks.
  • a job case which is used for carrying out a job, is drafted after a job template for this job case is determined.
  • a job case describes the specific content of a job based on a job template selected for this job.
  • the first exemplary embodiment will be discussed, assuming that digital document data (hereinafter simply called a document) is created as a file. Additionally, in the first exemplary embodiment, a folder, which is a storage region for a document, is created for each job case and for each step. A document created in accordance with the progress of a step is stored in a corresponding folder. In the first exemplary embodiment, as shown in FIG.
  • a folder is created for a job case of a certain job (such a folder may also be called a parent folder), and then, folders for individual steps of this job case are created under the parent folder (such folders may also be called child folders).
  • folders for individual steps that is, child folders
  • folders for individual steps may not necessarily be created, and all documents created for a job case may be stored in a parent folder for this job case.
  • Under a child folder another folder may be created, and under this folder, another folder may be created. In this manner, documents may be managed in a hierarchical structure having more levels than those in FIG. 3B .
  • FIG. 2 illustrates an example of the data structure of job management information in the first exemplary embodiment.
  • the status of a job in each drafted job case is managed by job management information.
  • the individual items of information shown in FIG. 2 will be explained.
  • “Job case No.” is identification information concerning a job case.
  • “Template No.” is identification information concerning a template used for this job case.
  • “User” is identification information concerning one or more users engaged in this job case.
  • “Folder name” is the name of the folder positioned on the highest level of the hierarchical structure (that is, the parent folder) of this job case.
  • “Progress” indicates the progress status of this job case.
  • “Completed” is set in “Progress”, and if it has not been completed and is currently in progress, the ongoing step number is set in “Progress”.
  • documents to be created in this job case are managed for each step.
  • “Document name”, “Creator”, and “Approver” are set for each document.
  • “Created” is information indicating the status of the document, that is, information indicating whether the corresponding document has been created.
  • “Approved” is information indicating the status of the document, that is, information indicating whether the corresponding document has been approved. If the document has been created or approved, “Yes” is set, and if the document has not been created or approved, “No” is set.
  • the items of information shown in FIG. 2 are those referred to in the first exemplary embodiment, and the job management information may include other items of information.
  • the job management information is suitably updated in accordance with the status of the job.
  • elements for executing information management such as setting and updating of information, and provision of information are not shown in the job management server 2 .
  • the DB server 3 and the user management server 4 are shown in FIG. 1 .
  • the DB server 3 includes a document repository 31 that stores documents handled in the first exemplary embodiment. As discussed above, a document handled in the first exemplary embodiment is stored in a folder provided for each job case or each step in the document repository 31 .
  • the user management server 4 includes a user information DB 41 for storing user information concerning users engaged in individual job cases.
  • the user information includes identification information and affiliation information concerning each user, such as the department of each user.
  • the display control device 1 refers to information managed by the job management server 2 , the DB server 3 , and the user management server 4 and provides documents to the client PC 5 .
  • the display control device 1 may be implemented by the hardware configuration of a general-purpose server computer or PC. That is, the display control device 1 includes a CPU, a ROM, a RAM, a storage, such as an HDD, and a communication interface.
  • the display control device 1 may include a user interface for executing information management, for example.
  • the display control device 1 includes a user interface (UI) controller 11 , a job management information obtainer 12 , a document selector 13 , and a display information generator 14 . Elements that are not referred to in the first exemplary embodiment are not shown in FIG. 1 .
  • the UI controller 11 includes an operation receiver 111 and a display controller 112 .
  • the operation receiver 111 receives an operation performed by a user on the client PC.
  • the display controller 112 performs control to display documents on the client PC 5 .
  • the job management information obtainer 12 obtains job management information from the job management server 2 .
  • the job management information obtained by the job management information obtainer 12 is job status information concerning the status of a job (job case).
  • the document selector 13 selects documents to be displayed on the screen of the client PC 5 when the user of the client PC 5 has selected a folder with a mouseover operation, such as when the user has set a mouse pointer over a folder displayed on the screen of the client PC 5 with a mouse.
  • the display information generator 14 generates display information including thumbnails of the selected documents.
  • the display controller 112 performs control to display the display information generated by the display information generator 14 on the screen of the client PC 5 .
  • the UI controller 11 , the job management information obtainer 12 , the document selector 13 , and the display information generator 14 are implemented by collaborative work between a computer forming the display control device 1 and a program executed by the CPU of the computer.
  • Programs to be used in the first exemplary embodiment may be provided by a communication medium or as a result of being stored in a computer-readable recording medium, such as a compact disc (CD)-ROM or a universal serial bus (USB) memory.
  • a communication medium such as a compact disc (CD)-ROM or a universal serial bus (USB) memory.
  • CD compact disc
  • USB universal serial bus
  • folders for storing documents to be generated in this job case are created in the document repository 31 .
  • Documents created in individual steps forming this job case are stored in the corresponding folders in the document repository 31 .
  • the user of the client PC 5 When the user of the client PC 5 is trying to create a document in an ongoing step of an ongoing job case, it may wish to check a past document. More specifically, the user may be trying to create a document by checking a past document highly related to the document to be created. In this case, by relying on the user's memory, the user searches for a target document by using a search function. The names of documents created for job cases which are drafted based on the same job template are likely to be similar to each other. For this reason, the user may be required to open and check the documents one by one. It thus takes a lot of time and effort for the user to find the target document. Even if the user has succeeded in finding the folder storing the target document, many documents may be stored in this folder. If it is not possible to display all the thumbnail document images on the screen, the user has to search for the target document by scrolling up and down the screen.
  • thumbnails indicating documents stored in a folder
  • a user performs an operation for displaying a display element (that is, thumbnails) indicating documents stored in a folder
  • documents which are likely to be checked by the user among the documents stored in the selected folder are selected as the subject documents to be displayed in accordance with the status of a job (job case) or a task (step) corresponding to this folder.
  • thumbnails of the selected documents are displayed. That is, when a certain folder is selected with a mouse, instead of displaying all the documents stored in this folder, documents are selectively displayed in accordance with the status of a job case or a step.
  • the documents to be displayed among the documents in this folder are not always the same and are varied in accordance with the status of a job case or a step. This enables the user to easily find a target document and also reduces the display space of document thumbnails.
  • FIG. 3A illustrates the status of job case 1 drafted based on a job template “T001”.
  • FIG. 3A shows that the job template “T001” defines a job process consisting of step 1 through step 4 and that two documents are to be created in each of step 1 through step 4.
  • “completed” is highlighted in gray, which indicates that step 1 through step 4 are all finished and case 1 has been completed.
  • FIG. 3B illustrates the configuration of folders and documents created in accordance with job case 1.
  • the folders of job case 1 are formed in the following hierarchical structure. Under the parent folder of job case 1, child folders corresponding to step 1 through step 4 are created. In the child folder in each step, documents created in a corresponding step are stored. Job case 1 has been completed, and all the documents created in the individual steps are stored in the corresponding folders.
  • FIG. 3C illustrates the status of job case 2 drafted based on the job template “T001”.
  • FIG. 3C shows that, since job case 2 is drafted based on the same template “T001” as for job case 1, the job process consisting of step 1 through step 4 are already defined and that two documents are to be created in each of step 1 through step 4.
  • “step 3” is highlighted in gray, which indicates that step 3 is currently executed.
  • FIG. 3D illustrates the configuration of folders and documents created in accordance with job case 2.
  • the folders of job case 2 are formed in the following hierarchical structure. Under the parent folder of job case 2, child folders corresponding to step 1 through step 4 are created. In the child folder in each step, documents created in a corresponding step are stored. In job case 2, documents in step 1 and step 2, which are completed steps, and document 3-1 in step 3, which is the ongoing step, have been created, but document 3-2 in step 3 and documents in step 4 are not yet created.
  • Display processing in the first exemplary embodiment will be discussed below with reference to the flowchart of FIG. 4 . Display processing will be explained when a job is in the status shown in FIGS. 3A and 3B and when a job is in the status shown in FIGS. 3C and 3D .
  • “user” is the user using the client PC 5 unless otherwise stated.
  • the user first performs a predetermined operation, such as starting a document management application to search for a document to be checked.
  • the operation receiver 111 of the display control device 1 receives this operation.
  • the display controller 112 then performs control to display the hierarchical structure of folders stored in the document repository 31 on the client PC 5 .
  • the user selects a folder storing a target document from among the folders displayed on the client PC 5 . It is assumed that the user has selected the folder with a mouseover operation.
  • the job management information obtainer 12 In response to receiving the user selecting operation by the operation receiver 111 of the display control device 1 , the job management information obtainer 12 identifies the folder selected by the user as a subject folder in step S 101 . Then, in step S 102 , the job management information obtainer 12 checks whether the subject folder is a folder linked with a job case. The job management information indicates the name of the parent folder of each job case. The job management information obtainer 12 can thus easily judge whether the folder selected by the user is a folder linked with a job case. If the selected folder is a folder linked with a job case (YES in step S 102 ), the job management information obtainer 12 checks the progress of the subject job by referring to the job management information. More specifically, the job management information obtainer 12 judges in step S 103 whether the job case has been completed.
  • step S 104 the job management information obtainer 12 searches for an ongoing job case which is being carried out based on the same template as that for job case 1 and identifies which step of this ongoing job case is currently executed. It is assumed that job case 2 shown in FIG. 3C is found as the ongoing job case. The job management information obtainer 12 then obtains the job management information concerning job case 1 and job case 2.
  • step S 105 the document selector 13 refers to the job management information obtained by the job management information obtainer 12 and selects documents to be displayed. That is, in this example, in job case 2, step 3 is currently executed, and the document selector 13 thus selects documents in step 3 of job case 1, which is the selected job case, namely, document 3-1 and document 3-2 surrounded by the long dashed dotted lines in FIG. 3B , from the document repository 31 .
  • document 1-1, document 1-2, document 2-1, . . . , document 4-2 could be displayed.
  • the document selector 13 assumes that the user may wish to check document 3-1 and document 3-2 in step 3, based on the fact that step 3 in job case 2, which is the ongoing job case, is now being executed.
  • the document selector 13 accordingly selects document 3-1 and document 3-2 from among the documents of job case 1.
  • step S 106 the thumbnail generator 141 generates thumbnails of the selected documents.
  • step S 107 the display controller 112 performs control to display display information including the generated thumbnails on the screen of the client PC 5 .
  • job case 1 linked with the folder selected by the user with a mouseover operation has been completed, the status of another job case (that is, job case 2) which is being carried out based on the same job template as job case 1 is checked. Then, the step number of job case 2 which is currently executed is detected, and document 3-1 and document 3-2 in step 3 of job case 1 are selected.
  • step 4 of job case 2 If step 4 of job case 2 is currently executed, the document selector 13 selects document 4-1 and document 4-2 in step 4 of job case 1. In this manner, depending on the status of job case 2 at the time when the user has selected the folder of job case 1 with a mouseover operation, documents to be displayed become different.
  • documents that the user probably wishes to check are selected and displayed from among the documents of the selected folder. This enables the user to easily find a target document from among the displayed documents. Additionally, as a result of selecting and displaying only suitable documents, the space for displaying document thumbnails is reduced.
  • thumbnails of documents are displayed.
  • attribute information for identifying documents such as document names, may be displayed.
  • step S 104 a job case using the same template as that job case 1 (job case 2 in the above-described example) is found. If multiple ongoing job cases using the same template as job case 1 are found, documents in the same step number of job case 1 as the ongoing step of each of the searched job cases may be displayed. Alternatively, documents to be displayed may be narrowed down based on another condition, as will be discussed in another exemplary embodiment. For example, documents to be displayed are restricted to documents whose creator or approver is a user performing a mouseover operation.
  • step S 103 A description will now be given of display processing to be executed when the user selects the folder positioned on the highest level of the hierarchical structure of job case 2, that is, the parent folder of job case 2 (hereinafter simply called the folder of job case 2).
  • the status of job case 2 shown in FIG. 3C shows that job case 2 is currently in progress and step 3 is being executed.
  • the result of step S 103 accordingly becomes NO.
  • the job management information obtainer 12 then proceeds to step S 108 .
  • the job management information obtainer 12 identifies that step 3 is now being executed and then obtains the job management information concerning job case 2.
  • the document selector 13 refers to the obtained job management information and selects at least one of a group of documents created in step 3, which is the ongoing step, and a document created in step 2, which is the step immediately before step 3, from among the documents in the folders of job case 2 (including child folders on the lower levels). If both of the documents in the current step and those in the previous step are selected in the first exemplary embodiment, the document selector 13 selects document 2-1, document 2-2, and document 3-1 surrounded by the long dashed dotted lines in FIG. 3D , from the document repository 31 .
  • step S 106 the thumbnail generator 141 generates thumbnails of the selected documents, as discussed above.
  • step S 107 the display controller 112 performs control to display display information including the generated thumbnails on the screen of the client PC 5 .
  • the display control device 1 assumes that the user wishes to check lately created documents in the selected folder and performs control to display such documents on the client PC 5 .
  • step S 102 If the folder selected by the user is not a folder linked with a job case (the result of step S 102 is NO), documents are specified in accordance with a predetermined rule and are obtained from the document repository 31 in step S 109 .
  • the thumbnail generator 141 generates thumbnails of the obtained documents.
  • step S 107 the display controller 112 performs control to display display information including the generated thumbnails on the screen of the client PC 5 .
  • FIG. 5 illustrates an example of the display screen of the client PC 5 .
  • the folders of job case 1 through job case 4, which are the lower level of the folder “UserA”, are displayed, and the user has set the mouse pointer over the folder of job case 2.
  • the user merely selects the folder of job case 2 with a mouse without opening the folder and can check which documents are stored in the folder (documents selected by the document selector 13 ) in a tooltip or popup window. This helps the user figure out in which folder a target document is included.
  • the configurations of a file management system and job management information are the same as those shown in FIGS. 1 and 2 , and display processing is the same as that shown in FIG. 4 .
  • a user selecting a folder icon with a mouse is identified so that the documents selected in step S 105 or S 108 in FIG. 4 become different from those in the first exemplary embodiment.
  • documents to be displayed become different depending on who has performed the mouseover operation. Processing for selecting and obtaining documents will be explained below with reference to FIGS. 6A through 6D .
  • the progress status of job case 1 and the documents created in the individual steps are the same as those in FIGS. 3A and 3B , while the progress status of job case 2 and the documents created in the individual steps are the same as those in FIGS. 3C and 3D .
  • job case 2 which is an ongoing job case
  • the creator and the approver of each document, and the creation status and the approval status of each document, that is, information indicating whether each document has been created or approved are checked.
  • the user performing a mouseover operation (hereinafter simply called the operating user) is assumed to be a user A represented by identification information “userA”.
  • the operating user can be identified with reference to login information, for example.
  • the job management information indicates that the user A is the creator of all the documents of job case 2.
  • the user A is accordingly the creator of document 3-1 and document 3-2 in the ongoing step 3 of job case 2.
  • the user A has created document 3-1 but has not yet created document 3-2.
  • step 3 of job case 2 the user A has created document 3-1 but has not yet created document 3-2. That is, it can be assumed that the user A wishes to create document 3-2 of job case 2 by referring to document 3-2 of job case 1, which is already created.
  • the document selector 13 thus selects document 3-2 of job case 1, which is the same document type as document 3-2 of job case 2, as indicated by the long dashed dotted lines in FIG. 6B , and obtains document 3-2 of job case 1 from the document repository 31 .
  • the operating user is assumed to be a user B represented by identification information “userB”.
  • the job management information indicates that the user B is the approver of all the documents of job case 2.
  • the user B has not yet approved document 2-1 in step 2, which is the previous step of the current step 3, and document 3-1 and document 3-2 in the current step 3.
  • Document 3-2 has not been created yet, as discussed above. That is, the user B has document 2-1 and document 3-1 to be approved.
  • the user B has selected the folder of job case 1 with a mouseover operation.
  • the current step 3 of job case 2 created based on the same job template “T001” as job case 1 is specified.
  • job case 2 the user B has not yet approved document 2-1 and document 3-1 among the created documents. That is, it can be assumed that the user B wishes to do approval work for document 2-1 and document 3-1 of job case 2 by referring to document 2-1 and document 3-1 of job case 1, which have already been created.
  • the document selector 13 thus selects document 2-1 and document 3-1 of job case 1, which are the same document types as document 2-1 and document 3-1 of job case 2, as indicated by the long dashed double-dotted lines in FIG. 6B , and obtains these documents from the document repository 31 .
  • the document selector 13 selects document 2-1 and document 3-1 that have been created but has not been approved yet and obtains these documents from the document repository 31 .
  • documents to be checked may become different depending on the operating user. That is, the documents to be displayed can be varied depending on the user.
  • the folder of job case 1, which is a completed job case is selected, the ongoing step of an ongoing job case using the same job template as job case 1 (step 3 of job case 2 in the above-described example) is specified, and then, documents in the same step of job case 1 as the specified step are selected as the documents to be displayed.
  • documents to be displayed are selected similarly to the first exemplary embodiment, but a document related to the selected documents is also selected and displayed.
  • FIG. 7A illustrates the progress status of job case 1, while FIG. 7C illustrates the progress status of job case 2.
  • the progress statuses in FIGS. 7A and 7C are the same as those in FIGS. 3A and 3C in the first exemplary embodiment.
  • FIG. 7B shows that, in response to a user having selected the folder of job case 1 with a mouseover operation, the document selector 13 selects document 3-1 and document 3-2 after processing is executed similarly to the first exemplary embodiment.
  • FIG. 7B also shows that the document selector 13 has selected document 1-2 related to at least one of document 3-1 and document 3-2.
  • the degree of relevance between documents is calculated in accordance with a predetermined rule, for example.
  • the degree of relevance between each document of job case 1 and each of document 3-1 and document 3-2 is calculated.
  • the calculated degree of relevance is compared with a predetermined threshold.
  • a document having a degree of relevance greater than or equal to the predetermined threshold (document 1-2 in this example) is selected.
  • the degree of relevance is calculated by using a known technique. For example, if the creator and/or the approver of a document are the same creator and/or the same approver of document 3-1 or 3-2, for example, or if a document includes more words identical to those in document 3-1 or 3-2, for example, the degree of relevance of such a document becomes greater.
  • the degree of relevance may be calculated based on attribute information concerning a document, such as the registration date of the document in the document repository 31 , the updating date of the document, the number of times the document is downloaded or accessed, the number of times the document is output from the document repository 31 , and the relationship between the department of the creator of this document and that of another document. For example, if the creator of one document and that of another document belong to the same department, the degree of relevance becomes greater.
  • the document selector 13 selects a document related to documents created in step 3, which is the ongoing step. If document 3-1 and document 3-2 in step 3 to be displayed are not yet created, as shown in FIG. 7D , the document selector 13 does not select them but still selects a document (document 1-2 in this example) related to document 3-1 and document 3-2 (to-be-created documents). Approaches to selecting relevant documents are similar to those described above.
  • thumbnail generator 141 when a user has selected a folder with a mouseover operation, documents to be displayed are selected and thumbnails of the selected documents are displayed on the screen of the client PC 5 as a display element indicating the documents.
  • the thumbnail generator 141 generates a thumbnail in accordance with the user having performed a mouseover operation or the document selected to be displayed.
  • a thumbnail is generated by reducing the size of the first page of a document, such as the cover page of a document.
  • the thumbnail generator 141 generates a thumbnail from the image of a page related to job steps or a page describing the features of a document.
  • a document selected by the document selector 13 is assumed to be a document A including an order sheet. If the document A is not yet approved and if the operating user is the approver of the document A, the thumbnail generator 141 generates a thumbnail of the document A from the image of the page to be checked by the approver to approve the document A, such as the image of a page showing a list of order goods.
  • step 2 which is subsequent to step 1 in which the document A is created, is currently in progress and if the operating user is the creator of a document in step 2, the thumbnail generator 141 generates a thumbnail of the document A from the image of a page which may be useful for creating a document in step 2, such as the image of the page showing the table of contents of the document A.
  • the document selector 13 has selected document 1-2 as a document related to document 3-1.
  • the thumbnail generator 141 analyzes document 1-2 to specify a page related to document 3-1, and then generates a thumbnail of document 1-2 from the image of the specified page.
  • the thumbnail generator 141 analyzes document 1-2 to specify a page related to document 3-2, and then generates a thumbnail of document 1-2 from the image of the specified page.
  • a relevant page can be specified using a known technology, such as calculating of the word frequency in the document or conducting natural language analysis.
  • a thumbnail is generated from the image of a page describing the general statement or the abstract. If a document is an invoice, a thumbnail is generated from the image of a page indicating the total amount. If a document is a delivery statement, a thumbnail is generated from a page including information concerning a delivery destination.
  • a thumbnail may not necessarily represent the image of the entire page. Only part of a page, such as a portion of a page indicating the total amount of an invoice or a portion of a page including information concerning a delivery destination of a delivery statement, may be used to generate a thumbnail.
  • a display element that is, thumbnails in the above-described exemplary embodiments, indicating files stored in a folder are displayed.
  • the operation for displaying a display element is not restricted to a mouseover operation.
  • FIG. 8 illustrates another example of the display screen of the client PC 5 .
  • the folders of job case 1 through job case 4, which are the lower level of the folder “UserA”, are displayed. Folder icons are formed and displayed so that thumbnails of all or some of the documents stored in each folder are displayed.
  • the thumbnails of the folder of job case 1 and those of job case 2 are displayed by way of example.
  • a user can check which documents (documents selected by the document selector 13 , as described above) are included in a folder without opening the folder or performing a mouseover or click operation, for example. This helps the user figure out in which folder a target document is included. As shown in the example in FIG.
  • the operation for displaying a display element is not limited to an operation intentionally performed by a user to display a display element, such as a mouseover operation. Even without such an intentional operation, documents selected with a function of any of the exemplary embodiments may be displayed. In other words, in response to starting an application, a display element is displayed.
  • an operation for starting an application and an operation for selecting a folder positioned at the highest level that is, an operation for displaying a list of folders
  • folders are displayed, and thus, such an operation may be regarded as an operation for selecting a folder.
  • exemplary embodiments have been discussed by assuming that a parent folder is selected by a mouseover operation.
  • the exemplary embodiments are also applicable to a case in which a child folder corresponding to a step is selected. In this case, processing is executed similarly to that when a parent folder is selected.
  • documents to be displayed are selected from among documents stored in the child folder and those stored in folders on a lower level of the child folder.
  • processor refers to hardware in a broad sense.
  • the processor includes general processors (e.g., CPU: Central Processing Unit), dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Integrated Circuit, FPGA: Field Programmable Gate Array, and programmable logic device).
  • general processors e.g., CPU: Central Processing Unit
  • dedicated processors e.g., GPU: Graphics Processing Unit
  • ASIC Application Integrated Circuit
  • FPGA Field Programmable Gate Array
  • programmable logic device e.g., programmable logic device
  • processor is broad enough to encompass one processor or plural processors in collaboration which are located physically apart from each other but may work cooperatively.
  • the order of operations of the processor is not limited to one described in the embodiments above, and may be changed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Library & Information Science (AREA)
  • User Interface Of Digital Computer (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
US17/011,245 2020-01-15 2020-09-03 Information processing apparatus and non-transitory computer readable medium for selecting file to be displayed Active 2041-01-30 US11507536B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2020004300A JP7396061B2 (ja) 2020-01-15 2020-01-15 情報処理装置及びプログラム
JP2020-004300 2020-01-15
JPJP2020-004300 2020-01-15

Publications (2)

Publication Number Publication Date
US20210216503A1 US20210216503A1 (en) 2021-07-15
US11507536B2 true US11507536B2 (en) 2022-11-22

Family

ID=76763035

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/011,245 Active 2041-01-30 US11507536B2 (en) 2020-01-15 2020-09-03 Information processing apparatus and non-transitory computer readable medium for selecting file to be displayed

Country Status (3)

Country Link
US (1) US11507536B2 (ja)
JP (1) JP7396061B2 (ja)
CN (1) CN113127424A (ja)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007025998A (ja) 2005-07-14 2007-02-01 Canon Inc 情報処理装置及びその制御方法、並びに、コンピュータプログラム及びコンピュータ可読記憶媒体
JP4501731B2 (ja) 2005-03-10 2010-07-14 富士ゼロックス株式会社 画像処理装置
US20110161388A1 (en) * 2009-12-28 2011-06-30 Canon Kabushiki Kaisha Information processing apparatus and method of controlling same
US8712862B2 (en) * 2005-05-09 2014-04-29 Google Inc. System and method for enabling image recognition and searching of remote content on display
US20140365430A1 (en) * 2013-06-11 2014-12-11 Canon Kabushiki Kaisha Information processing apparatus, system, and control method
US20190087416A1 (en) * 2017-09-21 2019-03-21 Fuji Xerox Co., Ltd. Information processing apparatus and non-transitory computer readable medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003281185A (ja) * 2002-03-26 2003-10-03 Hitachi Ltd 情報検索方法および情報検索装置
JP2009211165A (ja) * 2008-02-29 2009-09-17 Fuji Xerox Co Ltd 情報処理装置、書類作成システム及びプログラム
JP2011186851A (ja) * 2010-03-09 2011-09-22 Fuji Xerox Co Ltd 情報処理装置、情報処理システム及びプログラム
JP6412541B2 (ja) * 2016-11-10 2018-10-24 Ｎｅｃパーソナルコンピュータ株式会社 情報処理装置、情報処理方法、およびプログラム

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4501731B2 (ja) 2005-03-10 2010-07-14 富士ゼロックス株式会社 画像処理装置
US8712862B2 (en) * 2005-05-09 2014-04-29 Google Inc. System and method for enabling image recognition and searching of remote content on display
JP2007025998A (ja) 2005-07-14 2007-02-01 Canon Inc 情報処理装置及びその制御方法、並びに、コンピュータプログラム及びコンピュータ可読記憶媒体
US20110161388A1 (en) * 2009-12-28 2011-06-30 Canon Kabushiki Kaisha Information processing apparatus and method of controlling same
US20140365430A1 (en) * 2013-06-11 2014-12-11 Canon Kabushiki Kaisha Information processing apparatus, system, and control method
US20190087416A1 (en) * 2017-09-21 2019-03-21 Fuji Xerox Co., Ltd. Information processing apparatus and non-transitory computer readable medium

Also Published As

Publication number Publication date
US20210216503A1 (en) 2021-07-15
CN113127424A (zh) 2021-07-16
JP7396061B2 (ja) 2023-12-12
JP2021111258A (ja) 2021-08-02

Similar Documents

Publication Publication Date Title
CN107004008B (zh) 使用对不同的数据存储位置的自动化查询的相关文件识别
JP2020501208A (ja) コンテンツ管理システムにおけるプロジェクトの管理
CN111443912B (zh) 基于组件的页面渲染方法、装置、计算机设备和存储介质
US10223698B2 (en) Integrating a web-based CRM system with a PIM client application
US20120124068A1 (en) Document management apparatus and method for controlling same
US20100057770A1 (en) System and method of file management, and recording medium storing file management program
US20230134989A1 (en) System and method for building document relationships and aggregates
JP6262708B2 (ja) 深い検索性を有するオブジェクト化及びハードコピーからオリジナルの電子ファイルを検出するドキュメント検出方法
US11341197B2 (en) Recommendation system based on adjustable virtual indicium
CN115701299A (zh) 组合的本地和服务器上下文菜单
US11423230B2 (en) Process extraction apparatus and non-transitory computer readable medium
JP2006024158A (ja) 分類案内装置
US11507536B2 (en) Information processing apparatus and non-transitory computer readable medium for selecting file to be displayed
US7730100B2 (en) Information processing apparatus, information processing method, and storage medium
US9733800B2 (en) Document management system and document management method
US9984084B2 (en) Information processing apparatus, method for controlling same, and storage medium
US20200104342A1 (en) Content providing system that provides document as reference for editing, content providing method, information processing apparatus, and storage medium
US12061598B2 (en) File management apparatus and non-transitory computer readable medium
US20190012400A1 (en) Information processing apparatus and non-transitory computer readable medium
EP4054166B1 (en) Information processing apparatus, information processing program, and information processing method
US20210089595A1 (en) Information processing apparatus and non-transitory computer readable medium storing program
US20230326225A1 (en) System and method for machine learning document partitioning
EP4435622A1 (en) Information processing system, program, and information processing method
US11704625B2 (en) Knowledge management device, method, and computer program product for a software project
US20230012509A1 (en) Method and apparatus for providing a document editing interface for providing resource information related to a document using a backlink button

Legal Events

Date Code Title Description
AS Assignment

Owner name: FUJI XEROX CO., LTD., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MURAKAMI, JUNKO;ITO, YASUHIRO;SHIMIZU, TOMOYUKI;REEL/FRAME:053685/0564

Effective date: 20200716

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

AS Assignment

Owner name: FUJIFILM BUSINESS INNOVATION CORP., JAPAN

Free format text: CHANGE OF NAME;ASSIGNOR:FUJI XEROX CO., LTD.;REEL/FRAME:056078/0098

Effective date: 20210401

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STCF Information on status: patent grant

Free format text: PATENTED CASE