CN118245594A - Method, device, equipment and storage medium for document management - Google Patents

Abstract

According to an embodiment of the present disclosure, a method, apparatus, device and storage medium for document management are provided. The method includes receiving a document screening condition; in response to retrieving one or more documents that meet the document screening condition, displaying a document information set, the document information set including corresponding information of the one or more documents; and in response to detecting a predetermined operation on the document information set, displaying a document entry of the one or more documents in a document directory area. Thus, for document management, it is possible to implement on-demand screening, sorting of documents, and supplementation of directory areas, etc. In this way, users can be helped to achieve efficient document management and use.

Description

Method, device, equipment and storage medium for document management

Technical Field

Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, devices, apparatuses, and computer-readable storage media for document management.

Background technique

With the development of computer technology, the document information is usually organized and displayed through a tree-based directory or manual editing. With the increase in the types and number of documents, it is expected to achieve more efficient management of documents.

Summary of the invention

In a first aspect of the present disclosure, a method for document management is provided. The method includes: receiving a document screening condition; in response to retrieving one or more documents that meet the document screening condition, displaying a document information set, the document information set including corresponding information of the one or more documents; and in response to detecting a predetermined operation on the document information set, displaying a document entry of the one or more documents in a document directory area.

In a second aspect of the present disclosure, a device for document management is provided. The device includes: an input receiving module configured to receive a document screening condition; an information display module configured to display a document information set in response to retrieving one or more documents that meet the document screening condition, the document information set including corresponding information of the one or more documents; and an entry display module configured to display a document entry of one or more documents in a document directory area in response to detecting a predetermined operation on the document information set.

In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the device executes the method of the first aspect.

In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.

It should be understood that the contents described in this content section are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

FIG1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;

2A to 2I are schematic diagrams showing example interfaces for document management according to some embodiments of the present disclosure;

3A to 3B show a flowchart of a process for displaying a document information set according to some embodiments of the present disclosure;

FIG4 illustrates a flow chart of a process for document management according to some embodiments of the present disclosure;

FIG5 shows a block diagram of an apparatus for document management according to some embodiments of the present disclosure; and

FIG6 shows a block diagram of a device capable of implementing various embodiments of the present disclosure.

Detailed ways

It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet the relevant laws and regulations may also be applied to the implementation of the present disclosure.

It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

It should be noted that the titles of any sections/subsections provided herein are not restrictive. Various embodiments are described throughout this article, and any type of embodiment may be included under any section/subsection. In addition, the embodiments described in any section/subsection may be combined in any manner with any other embodiments described in the same section/subsection and/or different sections/subsections.

Herein, unless explicitly stated, executing a step “in response to A” does not mean executing the step immediately after “A” but may include one or more intermediate steps.

In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below. The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

As briefly mentioned above, for the organization of a large amount of document information, the documents are organized by manual editing. On the one hand, the documents can be managed through a group directory tree. However, since the grouping and sorting are manually fixed, operations such as filtering and sorting cannot be performed. On the other hand, the documents can be organized through conventional techniques, for example, filtering, sorting, grouping, etc. However, there is no direct access in the document directory area (for example, the directory on the left), and you can only jump to the corresponding list and open the document content in the list.

None of the above methods can meet the needs in some scenarios. For example, user A joins a project group, and related documents are often sent in the group. When user A looks for documents, he can only browse and search in the group, and cannot put this document list as fixed content in the document directory category commonly used by user A. For another example, user B is recently working on a "knowledge management" requirement. He is very concerned about relevant documents within the organization, so he often uses search to find documents with corresponding keywords, but cannot fix these search results to the document directory category commonly used by user B. For another example, user C joins a "product team" knowledge base, but sees that the documents in the knowledge base are structured, and he cannot access and view the documents in the order they were recently created.

In view of this, an embodiment of the present disclosure proposes an improved solution for document management. According to various embodiments of the present disclosure, a user provides a document filtering condition. If one or more documents satisfying the document filtering condition are retrieved, a document information set including corresponding information of the one or more documents is displayed. Then, if a predetermined operation for the document information set is detected, the document entry of the one or more documents is displayed in the document directory area.

In the embodiments of the present disclosure, users are supported to input document screening conditions according to their own needs, so as to construct the document information set they need. Furthermore, the embodiments of the present disclosure also support displaying the entrance of the corresponding document in the directory area to facilitate user access to the document. Thus, for document management, it is possible to implement on-demand screening, sorting of documents, and supplementation of the directory area, etc. In this way, users can achieve efficient document management and use.

Example Environment

1 shows a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. In the example environment 100, a component execution platform 110 can support the execution of a business component 125. A user 140 can interact with the business component 125 via a client of the component execution platform 110.

In some embodiments, the business component 125 may be downloaded and installed on a terminal device of the user 140. In some embodiments, the business component 125 may also be accessed in other ways, such as through a web page. In the environment 100 of FIG. 1 , in response to the business component 125 being started, the client of the component execution platform 110 may present an interface 150 of the business component 125.

The business component 125 includes, but is not limited to, one or more of the following: a chat business component (also known as an instant messaging business IM component), a document business component, an audio and video conference business component, an email business component, a task business component, a calendar business component, an objective and key result (OKR) business component, and the like. It can be understood that although a single business component is shown in FIG. 1 , in fact, multiple business components can be installed on the terminal device 110. Multiple business components can be integrated on the component operation platform 110, and such a component operation platform 110 can be regarded as a multifunctional collaboration platform. In the case where multiple business components are installed in the terminal device 110, these multiple business components can be integrated on one or more component operation platforms 110. In the component operation platform 110, people can start different business components as needed to complete corresponding information processing, sharing, communication, etc. The business component 125 can provide a content entity 126. The content entity 126 can be a content instance created by the user 140 or other users on the business component 125. For example, depending on the type of the business component 125, the content entity 126 can be unstructured content. For example, documents (e.g., word documents, pdf documents, presentations, spreadsheet documents, etc.), emails, messages (e.g., conversation messages on instant messaging service components), calendars, schedules, tasks, audio, video, images, etc. Content entity 126 may be structured content, such as data tables, forms, etc.

The component operation platform 110 can be deployed locally on the terminal device of each user 140, and/or can be supported by a server-side device. For example, the terminal device of the user 140 can run a client of the component operation platform 110, and the client can support the interaction between the user 140 and the component operation platform 110 provided by the server. In the case where the component operation platform 110 runs locally on the user's terminal device, the user 145 can directly use the terminal device to interact with the local component operation platform 110. In the case where the component operation platform 110 runs on the server-side device, the server-side device can realize the service supply to the client running in the terminal device based on the communication connection with the terminal device. The component operation platform 110 can present a corresponding interface 150 to the user 140 based on the operation of the user 140, so as to output and/or receive information related to the use of the component to the user 140.

The component operation platform 110 can be run on an appropriate electronic device. The electronic device here can be any type of device with computing capabilities, including a terminal device or a server device. The terminal device can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio/video player, a digital camera/camcorder, a positioning device, a television receiver, a radio broadcast receiver, an e-book device, a gaming device or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. The server device can include, for example, a computing system/server, such as a mainframe, an edge computing node, a computing device in a cloud environment, and the like. In some embodiments, the component operation platform 110 can be implemented based on a cloud service.

It should be understood that the structure and functionality of environment 100 are described for exemplary purposes only and does not imply any limitation on the scope of the present disclosure.

Some example embodiments of the present disclosure will continue to be described with reference to the accompanying drawings. It should be understood that the interfaces shown in the accompanying drawings are merely examples, and various interface designs may actually exist. The various graphical elements in the interface may have different arrangements and different visual representations, one or more of which may be omitted or replaced, and one or more other elements may also exist. The embodiments of the present disclosure are not limited in this respect. In addition, hereinafter, the example embodiments will be described mainly with respect to the component runtime platform 110. It should be understood that the actions described with respect to the component runtime platform 110 may be implemented by the client and/or server of the component runtime platform 110. For example, it may be performed by an application, component, or suite (e.g., business component 125) running on a terminal device, or it may be performed by an application, component, or suite in collaboration with its server.

The following will describe an example implementation of the present disclosure for document management with reference to Figures 2A to 2I. Figures 2A to 2I show schematic diagrams of example interfaces 201 to 209 for document management according to some embodiments of the present disclosure. The following will be described in conjunction with Figure 1 for ease of discussion.

In some embodiments, the component operation platform 110 receives document filtering conditions. The triggering operation for receiving the document filtering conditions may be various suitable operations. In some embodiments, if an operation of creating a new document set view is detected in the homepage of the document library, a setting area for the filtering conditions may be displayed for the user to enter the document filtering conditions in the area. First, refer to interfaces 201 to 203 as shown in FIGS. 2A to 2C. In interface 201, the homepage of the document library, such as the homepage of the document component, is presented. The user 140 may click on the "add" control 210 for creating a new document set view to add a new document information set. Such a document information set may also be referred to as a document list. The presented document information set may also be referred to as a list view or a custom view. Subsequently, in interface 202, after the user 140 clicks on the "filter" control 220, the component operation platform 110 presents an area 221 of "setting filtering conditions" for the user to set the document filtering conditions, thereby filtering the documents in the entire document list.

In some embodiments, a document set view can be inserted into a document. For example, if an operation of inserting a document set view is detected in the main body (e.g., text) of a target document, a filter condition setting area can be displayed for the user to set document filter conditions. In this way, information of associated documents can be displayed in one document.

In some embodiments, the document screening condition may include keywords contained in the document. For example, the words included in the corresponding title or main content of the document. As shown in FIG. 2C , the component operation platform 110 may receive keywords input by the user 140 in the input box 231. For example, the keyword input by the user 140 is "document A". The document screening condition may also include the document type. In some examples, the type of the document may include various types, such as a rich content document (which is a document that can contain various contents such as text, tables, forms, images, etc.), a data table, a form, a multidimensional table, a slide, a note, a mind map, a file, and the like. As shown in FIG. 2C , the component operation platform 110 may receive the type of document to be screened selected by the user 140 in the selection box 232. For example, the type selected by the user 140 is "document X". In some embodiments, the document range targeted by the document screening condition may include various types of online documents listed above, such as cloud documents.

The document filtering conditions may also include users associated with the document. In some examples, the users associated with the document included in the filtering conditions may be the creators or modifiers of the document. As shown in FIG2C , the component operation platform 110 may receive the owner of the document to be filtered selected by the user 140 in the selection box 233. For example, the user 140 selects the owner of the document to be filtered as "User A". In some examples, the users associated with the document included in the filtering conditions may be the sharers of the document. As shown in FIG2C , the component operation platform 110 may receive the sharers of the document to be filtered selected by the user 140 in the selection box 234. For example, the user 140 selects the sharer of the document to be filtered as "User B".

The document screening condition may also include a session associated with the document. In some examples, the session associated with the document included in the document screening condition may be a group chat session or a single chat session. As shown in FIG2C , the component operation platform 110 may receive the source session selected by the user 140 in the selection box 235. For example, the source of the document selected by the user 140 to be screened is the document in the “XX group”.

The document screening condition may also include the management category to which the document belongs. In some examples, the management category may be a folder, a knowledge base, etc. to which the document belongs. As shown in FIG2C , the component execution platform 110 may receive the location selected by the user 140 in the selection box 236. For example, the user 140 selects the location of the document to be screened as “folder a”.

In some embodiments, the component operation platform 110 displays a document information set including corresponding information of the one or more documents in response to retrieving one or more documents that meet the document filtering condition. In some examples, the component operation platform 110 presents the document information set after document filtering in real time based on the document filtering condition input by the user 140. For example, if the user 140 filters according to the source of a group, when the group sends a new document, the directory synchronization will update the document.

After the component execution platform 110 receives the document filtering condition input by the user 140, if one or more documents satisfying the document filtering condition are retrieved, a document information set including corresponding information of the one or more documents is displayed. The document information set can be displayed in a newly created document set view or in an inserted document set view. For example, a document set view 248 having a document information set is displayed in the interface 204 as shown in FIG2D.

The document set view 248 showing the document information set may include various information about the document. For example, basic information of the document, such as name, management category, owner, access time, etc., may be displayed. In some embodiments, additional information of the document may also be displayed to provide the user with more information about the document. In some examples, in the "XX group chat session", if the user 140 chooses to set the target document as a top document, the component operation platform 110 will display the top control. As shown in FIG. 2D , the component operation platform 110 displays the top control 243 behind the corresponding title of the target document. If the user 140 collects the target document, the component operation platform 110 will display the collection control. As shown in FIG. 2D , the component operation platform 110 displays the collection control 244 behind the corresponding title of the target document. How the component operation platform 110 displays the document information set in response to retrieving one or more documents that meet the document filtering condition will be described in detail below.

Through the disclosed embodiment, the component operation platform 110 can present the document information set after document screening in real time according to the document screening condition input by the user 140. In some examples, the document information set and the documents involved can share a data source to achieve synchronous update.

In some embodiments, the component execution platform 110 receives a sorting dimension specified by a user, and updates the display order of corresponding information of one or more documents according to the specified sorting dimension.

In some examples, the component operation platform 110 can update the display order of corresponding information of one or more documents according to the sorting dimension for the document information set filtered by the document filtering condition. For example, if the sorting of a certain node is sorted by access time, when accessing a new document, the list will also sort the most recently accessed document to the front according to time.

In some examples, the sorting dimensions specified by the user 140 and received by the component execution platform 110 may be sortable fields such as time (eg, access time, creation time, sharing time, modification time, etc.), name (eg, title name corresponding to the document), etc.

As shown in the interface 205 of FIG. 2E , the component running platform 110 sorts according to the access time 250 specified by the user 140 and the user 140's choice of whether to sort according to the rule 251 of "access time from earliest to latest" or the rule 252 of "access time from latest to earliest".

In some embodiments, the component execution platform 110 displays corresponding document entries of one or more documents in the document directory area in response to detecting a predetermined operation for the document information set. In some embodiments, the entry displayed by the component execution platform 110 in the document directory area includes an information set entry of the document information set and a document entry of the target document.

In some embodiments, the document directory area is independent of the area for receiving document filtering conditions. In the embodiments of the present disclosure, "independent of" means that the document directory area is different from, does not overlap, or is visually separated from the area for receiving document filtering conditions. As shown in the interface 204 of Figure 2D, the component operation platform 110 displays the information set entry 245 of the document information set and the document entry 246 of the target document in the document directory area (e.g., sidebar) 247 in response to detecting a predetermined operation on the document information set. In this example, the document target area 247 is in the sidebar, and the area for receiving document filtering conditions (e.g., control 220) is on the homepage of the document library.

In some embodiments, the component operation platform 110 displays the information set entry of the document information set in the document directory area 247 as the parent node of the document entry. For example, if the document information set includes one or more documents, the information set entry 245 of the document information set can be used as the parent node of the document entry corresponding to the one or more documents. The one or more document corresponding entries are child nodes of the information set entry. When the user 140 clicks on the information set entry 245, the component operation platform 110 will display the child nodes of the document information set (for example, the entry of the document corresponding to the one or more documents included in the document information set).

The information set entry may be an access entry for a document information set. In some examples, if the user 140 clicks on the entry 245 of the document information set in the document directory area 247, the component execution platform 110 will display the document information set in the document set view 248. For example, the document information set includes information of document AA, document A, document AAA, and so on.

In some embodiments, the display format of the document information set is user-selectable. In some examples, if the user 140 clicks the "list" control 241, the component execution platform 110 displays the document information set in the document set view 248 in the form of a list. If the user 140 clicks the "grid" control 242, the component execution platform 110 displays the document information set in the document set view 248 in the form of a view.

The document entry displayed in the document directory area can be an access entry for the document. In some embodiments, the component operation platform 110 will display the target document in response to detecting a trigger of the document entry of the target document in one or more documents. For example, if the user clicks on the document entry 246, the component operation platform 110 will present the document. Thus, it is convenient for the user to access the required document from the directory area.

In some embodiments, the component execution platform 110 updates the display order of the document entries of one or more documents in the document directory area according to the sorting dimension. In some examples, if the component execution platform 110 receives the sorting dimension specified by the user 140, the component execution platform 110 updates the display order of the document entries of one or more documents in the document directory area 247 according to the sorting dimension for the document information set filtered by the document filtering condition.

In some embodiments, the component execution platform 110 displays document entries for one or more documents in the document directory area in response to detecting a predetermined operation on the document information set. The predetermined operation may include a triggering operation of adding a control to a directory associated with the document information set.

As shown in interface 206 of FIG. 2F , if user 140 clicks on a document information set (e.g., “XX document set”), component runtime platform 110 will display a selection card 260 associated with “XX document set”. Selection card 260 includes a directory adding control 261 (e.g., “Add to sidebar”) associated with “XX document set”. User 140 clicks control 261 to add “XX document set” to the sidebar, i.e., the document directory area.

In some examples, the selection card 260 further includes a "rename" control 262, and the user 140 can click the control 262 to rename the "XX document set". The selection card 260 further includes a "delete" control 263, and the user 140 can click the control 263 to delete the "XX document set".

In some embodiments, the predetermined operation may also include a move operation of moving the label of the document information set to the document directory area. For example, the user 140 may add the document information set to the directory area by dragging the label "XX document set" 264 of the document information set.

The present disclosure can display the document entry of one or more documents in the document directory area by receiving a predetermined operation from the user (e.g., adding to the "sidebar" or dragging). The following description is for the added directory in the document directory area, and the user can adjust the position of the added directory by moving the operation (e.g., dragging).

In some embodiments, in response to detecting a move operation on an information set entry, the component execution platform 110 updates the display positions of the information set entry and the document entry in the document directory area according to the end position of the move operation.

In some embodiments, the component operation platform 110 displays the information set entry according to the track of the movement operation in response to detecting the movement operation. At this time, the information set entry displayed by the component operation platform 110 collapses the document entry of one or more documents. If the movement operation from the user ends, the component operation platform 110 expands the corresponding document entry of one or more documents according to the ending position.

For example, when the user 140 drags, the component execution platform 110 collapses the document entry corresponding to one or more documents included in the document information set. After the user 140 drags, the component execution platform 110 expands the document entry corresponding to one or more documents included in the document information set.

In the example interfaces 207 to 209 shown in FIGS. 2G to 2I , the user 140 drags the information set entry 270 of the “XX document set” to the area 280. During the dragging process, the component operation platform collapses the document entry of the documents included in the “XX document set”. After the user 140 drags, the component operation platform 110 expands the document entry corresponding to the multiple documents included in the “XX document set” at the area 290 in the example interface 209.

The present disclosure can provide various document directory structures for different users according to actual scenarios and needs through screening and sorting. The following will describe the operations of adding and deleting documents.

In some embodiments, the component operation platform 110 responds to the addition of documents that meet the document screening conditions by adding a document entry for the added document in the document directory area. In some examples, if the screening conditions include screening according to the source of a certain group, when the group sends a new document that meets the screening conditions, the document information set is synchronously updated to add the information of the document. At this time, the component operation platform 110 adds a document entry corresponding to the added document in the document directory area.

In some embodiments, the component operation platform 110 removes the document entry for the reduced document in the document directory area in response to the reduction of the documents that meet the document screening condition. In some examples, if the screening condition includes screening the documents in a folder, when a document that originally meets the screening condition is removed from the folder, the document information set is synchronously updated to remove the information of the document. At this time, the component operation platform 110 reduces the document entry corresponding to the removed document in the document directory area.

The above describes a solution for document management based on the client side of the component operation platform 110, and efficient management of documents can be achieved through the present disclosure. For ease of understanding, the following will refer to Figures 3A to 3B to describe the process of the component operation platform 110 displaying a document information set in response to retrieving one or more documents that meet the document filtering conditions. For example, after the document directory area is closed or no longer displayed, if the document directory area needs to be displayed again (for example, the user activates the document component), the component operation platform 110 can retrieve the documents that currently meet the document filtering conditions. Then, in the document directory area, the component operation platform 110 can display the corresponding document entries of these documents in order according to the sorting dimension.

3A to 3B are flowcharts of processes 301 to 302 for displaying document information sets according to some embodiments of the present disclosure. Process 301 is an interaction process between a client 310 and a server 350 of a component runtime platform 110. The server 350 includes a backend service 320, a document service 330, and a downstream service 340.

The client 310 sends (361) a directory display request to the backend 320. The backend 320 determines directory configuration information in response to the directory display request of the client 320, and returns (362) the directory configuration information to the client 310. The directory configuration information may include various entries and corresponding positions that need to be displayed in the document directory area.

Subsequently, the client 310 sends (363) a document information access request to the document service 330. For example, a user desires to access a document information set, thereby triggering an information set entry. The document service 330 requests (364) the document information from the downstream service 340. The downstream service 340 determines the document information and provides (365) the document information to the document service 330. How the downstream service determines the document information will be described in detail below with reference to FIG. 3B. Although one downstream service 340 is shown, multiple downstream services 340 may be included, as will be described below.

Continuing with process 301, document service 330 assembles (366) the document information it receives. Document service 330 then returns (367) the assembled document information to client 310. Client 310 can then display the document information, such as document set view 248 shown in FIG. 2D.

The following will describe the process 302 of the downstream service determining document information. The search service 322 as a downstream service receives the document information request 321 from the document service, searches for one or more documents that meet the document screening conditions, and returns them to the document service 330. The document service 330 calls the knowledge base document service 324 and/or the non-knowledge base document service 323 (for example, a folder service) according to the management category to which the one or more documents belong to obtain the document information. That is, if a document in the one or more documents is a file belonging to the knowledge base, the knowledge base document service 324 is called to obtain the corresponding information of the document. If a document in the one or more documents belongs to the non-knowledge base document service 323, the non-knowledge base document service 323 is called to obtain the corresponding information of the document.

The document service 330 obtains the basic information of the document based on the knowledge base document service 324 and the non-knowledge base document service 323, such as the document name, creation time, access time, etc. After that, the document service 330 obtains the additional information 325 to determine the final document information. The acquisition of the additional information 325 can call various appropriate downstream services, such as: metadata service 325-1, folder location service 325-2 (for example, the location of the file to which the document belongs), knowledge base location service 325-3 (for example, the location of the knowledge base to which the document belongs), top service 325-4 (for example, whether the document is top), collection service 325-5 (for example, whether the document is collected), permission service 325-6 (for example, the permissions of the document), dense service 325-7 (for example, whether the document is public or private), thumbnail service 325-8 (for example, the document is displayed in the form of a grid), and icon service 325-9.

In summary, the disclosed embodiments utilize search capabilities to retrieve the document screening conditions configured by the user, assemble the business in the document service (BFF) middle layer, and return the document information set (e.g., list data) required by the user. Furthermore, by storing the directory list and sorting configured by the user in the document directory area, it is possible to achieve real-time retrieval when the user accesses.

Example Process

FIG4 shows a flowchart of a process 400 for document management according to some embodiments of the present disclosure. The process 400 may be implemented at the component execution platform 110, for example, by a server of the business component 125, or by a terminal device of the business component 125, or by a server and a terminal device in coordination. The process 400 is described below with reference to FIG1.

In block 410 , the component execution platform 110 receives document filtering conditions.

In block 420 , in response to retrieving one or more documents satisfying the document screening condition, the component execution platform 110 displays a document information set including corresponding information of the one or more documents.

In block 430 , the component execution platform 110 displays document entries of one or more documents in the document directory area in response to detecting a predetermined operation on the document information set.

In some embodiments, process 400 also includes: receiving user specifications for sorting dimensions; updating the display order of corresponding information of one or more documents based on the specified sorting dimensions; and updating the display order of document entries of one or more documents in the document directory area based on the specified sorting dimensions.

In some embodiments, an information set entry for the document information set is also displayed in the document directory area, and the information set entry is displayed as a parent node of the document entry.

In some embodiments, process 400 further includes: in response to detecting a move operation on the information set entry, updating the display positions of the information set entry and the document entry in the document directory area according to the end position of the move operation.

In some embodiments, updating the display position of the information set entry and the document entry in the document directory area includes: in response to detecting a move operation, displaying the information set entry according to the trajectory of the move operation and collapsing the document entries of one or more documents; and in response to the end of the move operation, expanding the document entries of one or more documents according to the end position.

In some embodiments, process 400 also includes at least one of the following: in response to an increase in documents that meet the document filtering condition, adding a document entry for the added document in the document directory area, or in response to a decrease in documents that meet the document filtering condition, removing the document entry for the reduced document from the document directory area.

In some embodiments, displaying a document entry for one or more documents in a document directory area is in response to detecting a predetermined operation for a document information set, and the predetermined operation includes at least one of the following: a triggering operation to add a control to a directory associated with the document information set, or a moving operation to move a label of the document information set to the document directory area.

In some embodiments, process 400 further includes: in response to detecting a trigger of a document entry of a target document in the one or more documents, presenting the target document.

In some embodiments, the document screening condition includes at least one of the following: keywords contained in the document, document type, a user associated with the document, a session associated with the document, and a management category to which the document belongs.

In some embodiments, receiving document filtering conditions includes: displaying a setting area for the filtering conditions in response to at least one of the following: detecting an operation of creating a new document set view in the home page of the document library, or detecting an operation of inserting a document set view in the body of the target document; and receiving the document filtering conditions via the setting area.

In some embodiments, the document information set is displayed in a newly created document set view or an inserted document set view.

In some embodiments, the document directory area is independent of the area for receiving document filter criteria.

5 shows a schematic structural block diagram of an apparatus 500 for document management according to some embodiments of the present disclosure. The apparatus 500 may be implemented as or included in the component execution platform 110. Each module/component in the apparatus 500 may be implemented by hardware, software, firmware or any combination thereof.

As shown in the figure, the apparatus 500 includes an input receiving module 510 configured to receive document screening conditions.

The apparatus 500 further includes an information set display module 520 configured to display a document information set in response to retrieving one or more documents satisfying the document screening condition, wherein the document information set includes corresponding information of the one or more documents.

The apparatus 500 further includes an input receiving module 530 configured to display document entries for one or more documents in a document directory area in response to detecting a predetermined operation on a document information set.

In some embodiments, the device 500 also includes a designated receiving module configured to receive user specifications for sorting dimensions; update the display order of corresponding information of one or more documents based on the designated sorting dimensions; and update the display order of document entries of one or more documents in the document directory area based on the designated sorting dimensions.

In some embodiments, an information set entry for the document information set is also displayed in the document directory area, and the information set entry is displayed as a parent node of the document entry.

In some embodiments, the device 500 also includes a position update module configured to update the display position of the information set entry and the document entry in the document directory area according to the end position of the move operation in response to detecting a move operation on the information set entry.

In some embodiments, the location update module is also configured to, in response to detecting a moving operation, display the information set entrance according to the trajectory of the moving operation and collapse the document entrance of one or more documents; and in response to the end of the moving operation, expand the document entrance of one or more documents according to the end position.

In some embodiments, the device 500 also includes an entry update module, which is configured to add a document entry for the added document in the document directory area in response to the increase of documents that meet the document filtering conditions, or to remove the document entry for the reduced document from the document directory area in response to the reduction of documents that meet the document filtering conditions.

In some embodiments, displaying document entries for one or more documents in a document directory area is in response to detecting a predetermined operation for a document information set, and the predetermined operation includes at least one of the following: a triggering operation to add a control to a directory associated with the document information set, or a moving operation to move a label of the document information set to the document directory area.

In some embodiments, the apparatus 500 further includes a document display module configured to display a target document in response to detecting a trigger of a document entry of a target document in one or more documents.

In some embodiments, the document screening condition includes at least one of the following: keywords contained in the document, document type, a user associated with the document, a session associated with the document, and a management category to which the document belongs.

In some embodiments, the input receiving module 510 is further configured to: display a setting area for filtering conditions in response to at least one of the following: detecting an operation of creating a new document set view in the homepage of the document library, or detecting an operation of inserting a document set view in the main body of the target document; and receiving document filtering conditions via the setting area.

In some embodiments, the document information set is displayed in a newly created document set view or an inserted document set view.

In some embodiments, the document directory area is independent of the area for receiving document filter criteria.

FIG6 shows a block diagram of an electronic device 600 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 600 shown in FIG6 is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. The electronic device 600 shown in FIG6 may be used to implement the electronic device 110 of FIG1 .

As shown in FIG6 , the electronic device 600 is in the form of a general electronic device. The components of the electronic device 600 may include, but are not limited to, one or more processors or processing units 610, a memory 620, a storage device 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. The processing unit 610 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 620. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 600.

The electronic device 600 typically includes a plurality of computer storage media. Such media may be any accessible media that is accessible to the electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 620 may be a volatile memory (e.g., registers, caches, random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 630 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and/or data and may be accessed within the electronic device 600.

The electronic device 600 may further include additional removable/non-removable, volatile/non-volatile storage media. Although not shown in FIG. 6 , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a “floppy disk”) and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 620 may include a computer program product 625 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.

The communication unit 640 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 600 can be implemented with a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 600 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

The input device 650 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 660 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 600 may also communicate with one or more external devices (not shown) through the communication unit 640 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 600, or communicate with any device that allows the electronic device 600 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input/output (I/O) interface (not shown).

According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

Various aspects of the present disclosure are described herein with reference to the flowcharts and/or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and/or block diagram and the combination of each box in the flowchart and/or block diagram can be implemented by computer-readable program instructions.

These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions/actions specified in one or more boxes in the flowchart and/or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and/or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions/actions specified in one or more boxes in the flowchart and/or block diagram.

Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions/actions specified in one or more boxes in the flowchart and/or block diagram.

The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and/or flow chart, and the combination of the square boxes in the block diagram and/or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the marketplace, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.

Claims (15)

1. A document management method, comprising: Receive document filtering conditions; In response to retrieving one or more documents satisfying the document screening condition, displaying a document information set, the document information set including corresponding information of the one or more documents; and In response to detecting a predetermined operation on the document information set, document entries of the one or more documents are displayed in a document directory area. 2. The method according to claim 1, further comprising: receiving a user specification of a sorting dimension; According to the specified sorting dimension, updating the display order of the corresponding information of the one or more documents; and According to the specified sorting dimension, the display order of the document entries of the one or more documents in the document directory area is updated. 3 . The method according to claim 2 , wherein an information set entry for the document information set is also displayed in the document directory area, and the information set entry is displayed as a parent node of the document entry. 4. The method according to claim 3, further comprising: In response to detecting a move operation on the information set entry, the display positions of the information set entry and the document entry in the document directory area are updated according to the end position of the move operation. 5. The method according to claim 4, wherein updating the placement of the information set entry and the document entry in the document directory area comprises: In response to detecting the moving operation, displaying the information set entry according to a trajectory of the moving operation and retracting the document entries of the one or more documents; and In response to the end of the moving operation, the document entry of the one or more documents is expanded according to the end position. 6. The method according to claim 1, further comprising at least one of the following: In response to the addition of a document satisfying the document screening condition, a document entry for the added document is added in the document directory area, or In response to a reduction in the number of documents satisfying the document screening condition, document entries of the reduced documents are removed from the document directory area. 7. The method according to claim 1, wherein displaying the document entry for the one or more documents in the document directory area is in response to detecting a predetermined operation for the document information set, and the predetermined operation comprises at least one of the following: a trigger action that adds a control to the catalog associated with the document information set, or A move operation is performed to move the tag of the document information set to the document directory area. 8. The method according to claim 1, further comprising: In response to detecting a trigger on a document entry of a target document among the one or more documents, the target document is presented. 9. The method according to claim 1, wherein the document screening condition comprises at least one of the following: Keywords contained in the document, Document type, the user associated with the document, the session associated with the document, The management category to which the document belongs. 10. The method according to claim 1, wherein receiving the document screening condition comprises: In response to at least one of the following, a setting area for filter conditions is displayed: An action to create a new Document Set view is detected on the home page of a document library, or An insertion of a document set view is detected within the body portion of a target document; and The document screening condition is received via the setting area. 11. The method according to claim 10, wherein the document information set is displayed in a newly created document set view or an inserted document set view. 12. The method according to claim 1, wherein the document directory area is independent of an area for receiving the document filtering condition. 13. A device for document management, comprising: An input receiving module configured to receive a document filtering condition; an information set display module, configured to display a document information set in response to retrieving one or more documents satisfying the document screening condition, the document information set including corresponding information of the one or more documents; and The entry display module is configured to display document entries for one or more documents in the document directory area in response to detecting a predetermined operation on the document information set. 14. An electronic device comprising: at least one processing unit; and At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 12 when executed by the at least one processing unit. 15. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 12.