CN107870805B - Information processing method and device of task system - Google Patents
Information processing method and device of task system Download PDFInfo
- Publication number
- CN107870805B CN107870805B CN201610847093.0A CN201610847093A CN107870805B CN 107870805 B CN107870805 B CN 107870805B CN 201610847093 A CN201610847093 A CN 201610847093A CN 107870805 B CN107870805 B CN 107870805B
- Authority
- CN
- China
- Prior art keywords
- task
- user
- node
- record
- screening
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/461—Saving or restoring of program or task context
-
- 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
Abstract
The application provides an information processing method of a task system, which comprises the following steps: responding to the access operation of a user to the task page, and acquiring page data of the task page; acquiring a record of task screening items of a user from a background server, determining the task screening items selected by the user last time, and screening out task names corresponding to the task screening items selected by the user last time from a plurality of task names; displaying a task page, wherein the task page comprises the screened task name, and setting the determined task screening item selected by the user last time to be in a selected state; responding to the selection operation of a user on task screening items in a task page, and sending the information of the selected task screening items to a background server; and the background server maintains a record of the task screening items for the user according to the received information of the selected task screening items. The application also provides a corresponding browser and a server. By adopting the technical scheme, the task checking efficiency can be improved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to an information processing method and apparatus for a task system.
Background
At present, some task systems are implemented based on the internet, and a user can access task data provided by a background task management module through terminal equipment (handheld equipment, a PC, and the like) and further browse relevant information (such as task names, task description information, parameter configuration, and the like) of tasks in the task system.
The user can browse various task names in the task page firstly, and can enter a page of a task corresponding to the task name by clicking or touching the task name displayed in the task page, wherein various description information and parameters of the task are displayed.
Disclosure of Invention
The application provides an information processing method of a task system, which is applied to a front-end browser and comprises the following steps: responding to an access operation of a user on a task page, and acquiring page data of the task page, wherein the page data comprises a plurality of task screening items to be displayed and a plurality of task names; acquiring a record of the task screening items of the user from a background server, determining the task screening items selected by the user last time according to the record, and screening out task names corresponding to the task screening items selected by the user last time from the plurality of task names; displaying the task page, wherein the task page comprises the plurality of task screening items and the screened task names, and setting the determined task screening item selected by the user last time to be in a selected state; responding to the selection operation of the user on the task screening items in the task page, sending the information of the selected task screening items to the background server, screening task names corresponding to the selected task screening items from the task names, and displaying the screened task names in the task page; and the background server maintains a record of the task screening items for the user according to the received information of the selected task screening items.
The application also provides an information processing method of the task system, which is applied to a background server and comprises the following steps: receiving information aiming at a task screening item of a user from a front-end browser; the front-end browser responds to the selection operation of the user on the task screening items in the task page and sends the information of the selected task screening items to the background server; creating or updating a record of the task screening items of the user in a database according to the received information of the task screening items of the user; receiving a task screening item query request of the front-end browser for the user; according to the received task screening item query request, acquiring a record of the task screening item of the user from the database and sending the record to the front-end browser, so that the front-end browser determines the task screening item selected by the user last time according to the record, screens out a task name corresponding to the task screening item selected by the user last time from a plurality of task names to be displayed, displays the plurality of task screening items and the screened task name in the task page, and sets the determined task screening item selected by the user last time to be in a selected state.
The present application further provides a front-end browser, including: the system comprises a user interface module, a page data module, a record processing module, a screening module and a display module; the user interface module responds to an access operation of a user on a task page, triggers the page data module to acquire page data of the task page, wherein the page data comprises a plurality of task screening options and a plurality of task names to be displayed, and triggers the record processing module to acquire records of the task screening options of the user from a background server; the screening module determines the task screening item selected by the user last time according to the record of the task screening item acquired by the record acquisition module, and screens out the task name corresponding to the task screening item selected by the user last time from the plurality of task names; the user interface module is further used for responding to the selection operation of the user on the task screening items in the task page, triggering the record processing module to send the information of the selected task screening items to the background server, and triggering the screening module to screen out task names corresponding to the selected task screening items from the task names; the background server maintains a record of the task screening items for the user according to the received information of the selected task screening items; the display module displays the task page according to the screening result of the screening module, wherein the task page comprises the plurality of task screening items and the screened task names, and when the user interface module responds to the access operation of the user, the display module further sets the task screening item which is determined by the screening module and is selected by the user last time to be in a selected state.
The present application further provides a backend server, including: the system comprises a transceiver module, a record processing module and an inquiry module; the receiving and sending module receives information of task screening options aiming at a user from a front-end browser; the front-end browser sends information of the selected task screening items in response to the user's selection operation on the task screening items in the task page; the record processing module is used for creating or updating a record of the task screening items of the user in a database according to the received information of the task screening items of the user; the receiving and sending module receives a task screening item query request of the front-end browser for the user; the query module acquires a record of the task screening items of the user from the database according to the received task screening item query request and sends the record to the front-end browser, so that the front-end browser determines the task screening items selected by the user last time according to the record, screens out task names corresponding to the task screening items selected by the user last time from a plurality of task names to be displayed, displays the task screening items and the screened task names in the task page, and sets the determined task screening items selected by the user last time to be in a selected state.
By adopting the method, the browser and the server provided by the application, the state of the task screening item operated by the user last time can be restored in the task page of the task system, so that the efficiency of the user for searching the task can be improved, and the display effect of the task information can be improved.
Drawings
In order to more clearly illustrate the technical solutions in the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only examples of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive effort. Wherein the content of the first and second substances,
FIG. 1 is a system architecture diagram to which the present application relates;
FIG. 2 is a schematic flow chart of a method according to an example of the present application;
FIGS. 3A-3C are schematic diagrams of an embodiment of the present application;
FIGS. 4A-4B are schematic diagrams of an embodiment of the present application;
FIG. 5 is a schematic flow chart of a method according to an example of the present application;
FIG. 6 is a block diagram of a front-end browser according to an embodiment of the present application;
FIG. 7 is a block diagram of a backend server according to an embodiment of the present application; and
FIG. 8 is a block diagram of a computing device in one example of the present application.
Detailed Description
The technical solutions in the present application will be described clearly and completely with reference to the accompanying drawings, and it is obvious that the described examples are some, but not all examples of the present application. All other examples, which can be obtained by a person skilled in the art without making any inventive step based on the examples in this application, are within the scope of protection of this application.
Fig. 1 is a system architecture diagram applied to the technical solution of the present application. As shown in fig. 1, the system architecture includes: a data warehouse 101 (such as a Tencent data warehouse TDW), a task management module 102, a data server 103 (such as an Internet data center IDC server) and a terminal device 104, which realize information interaction through a network 105. The data warehouse 101 maintains various data in the network, and can analyze and calculate mass data. For various data analysis and calculation, the task management module 102 establishes and manages a large number of tasks, each of which represents a multi-step computer-implemented process for performing a calculation and statistics. The user can upload various data to the data repository 101 and obtain various data analysis/calculation results from the data repository 101 by using the data server 103 and the terminal device 104 through the network 105, and can also create various tasks in the task management module 102 and browse various task information in the task management module 102. The network 105 may be the internet, and the terminal device 104 may be installed with a front-end browser, through which task information in the task management module 102 can be accessed and displayed in a page. The task management module 102 may be located at a web server. The data server 103 may serve as a background server for the terminal device 104, and perform corresponding background processing based on instructions and data from the terminal device 104.
The application provides an information processing method of a task system, which can be applied to a front-end browser in a terminal device 104. Here, the terminal device 104 may be various computing devices, such as: a PC, a mobile phone, a palm computer, a tablet computer, a notebook computer, etc.
As shown in fig. 2, the method comprises the following steps:
step 201: responding to the access operation of a user to a task page, and acquiring page data of the task page, wherein the page data comprises a plurality of task screening items to be displayed and a plurality of task names; acquiring a record of the task screening items of the user from a background server, determining the task screening items selected by the user last time according to the record, and screening out task names corresponding to the task screening items selected by the user last time from the plurality of task names (namely, the task screening items selected when a task page is accessed last time); and displaying the task page, wherein the task page comprises the plurality of task screening items and screened task names, and setting the determined task screening item selected by the user last time to be in a selected state.
That is to say, the front-end browser can restore the selection operation of the user on the task screening item when the user accesses the task page last time according to the record of the task screening item maintained by the background server, automatically complete the screening of the task name, and restore the display state of the task page to the state when the user accesses the task page last time.
Here, when the user wants to browse the task page, the user clicks or inputs a link address of the task page (for example, inputs a URL, or clicks the URL or clicks a control bound to the URL), and then sends an access operation, and in response to the access operation, the front-end browser pulls corresponding page data from the task management module 102 through the link address of the task page, and then displays the task page.
Step 202: responding to the selection operation of the user on the task screening items in the task page, sending the information of the selected task screening items to a background server, screening out task names corresponding to the selected task screening items from a plurality of task names, and displaying the screened task names in the task page. And the background server maintains the record of the task screening items for the user according to the received information of the selected task screening items. Here, the backend server may be the data server 103.
Here, each time the user performs a selection operation on a task screening item, the front-end browser sends information of the selected task screening item to the background server, and the background server updates a record of the task screening item of the user to ensure that the recorded information of the task screening item is the information of the task screening item selected by the user last time.
By adopting the above example, each time the user browses the task page of the task system, the front-end browser can automatically restore the display state (including the selected task screening item and the screened task name) when the user accesses the task page last time, and the user can perform further screening on the basis, so that the operation efficiency of the user can be improved, the operation times of the user can be reduced, and the performance of the task system can be improved.
In some examples, when the record of the task screening item of the user is not obtained from the background server, the front-end browser displays the task page, wherein the task page comprises the plurality of task screening items to be displayed and the plurality of task names. That is, in this case, it is described that the user has not selected the task screening item, so the background server has no record of the task screening item of the user, and at this time, the front-end browser fully displays all the task screening items and the task names.
The implementation of an example of the above method is described below with reference to fig. 3A-3C.
FIG. 3A illustrates task filters in a task page, which fall into several categories: master principal, output type, and tag. Of these, three screening items (aleche, TDW, and aaa) are selected by the user.
When the user selects the three filter items, the front-end browser may record the selected three filter items as javascript's data objects, as shown in fig. 3B. In FIG. 3B, the names and categories of the three filter items are recorded (as shown in the box). Then, the front-end browser can encode the data object into a JSON character string form to facilitate storage and transmission of data, where the character string converted from the data object is:
{"query_condition":[{"key":"identity","value":"aleche"},{"key":"out_type","value":"tdw"},{"key":"tag","value":"aaa"},{"key":"flag","value":"normal"}]}
the front-end browser transmits the JSON character string to the background server through an HTTP protocol.
The background server stores the received JSON character string in a database, forms a corresponding relation with a user name, stores the JSON character string as a record of a task screening item of the user, only keeps the latest JSON character string of the user, and updates the record of the user when a new JSON character string comes. As shown in fig. 3C, the backend server maintains records of task filters of three users in the database, and each user name corresponds to a record of the last filter.
When the user leaves the task page (for example, logs out or enters other pages) and then accesses the task page again, the front-end browser can restore the last operating state of the user in the task page through the following processing.
The front-end browser may request the backend server to query a record of the task screening item of the user according to a user identifier (e.g., a login name) obtained when the user logs in. Specifically, the front-end browser sends a task filter item query request for the user to the backend server through an HTTP protocol, where the request may carry an identifier (e.g., a login name) of the user. And the background server searches the record of the corresponding task screening item in the database through the identification of the user and returns the record to the front-end browser. For example: the task screening item record in the form of the JSON character string can be obtained by inquiring the record shown in the figure 3C according to the user login name 'aleche':
{"query_condition":[{"key":"identity","value":"aleche"},{"key":"out_type","value":"tdw"},{"key":"tag","value":"aaa"},{"key":"flag","value":"normal"}]}
the front-end browser can parse the obtained JSON string into data objects, as shown in fig. 3B. Then, the front-end browser may determine the task screening item selected by the user last time by parsing the data object, and may further restore the selected state of the task screening item on the task page (as shown in fig. 3A) and the screened task name. For example: in the data object shown in fig. 3B, the value of "owner" of the keyword identity record is aleche, and based on this record, the task screening item "aleche" belonging to "owner" on the interface of the task page may be set to the selected state. Similarly, the task screening item "TDW" belonging to the "output type" is set to the selected state, and the task screening item "aaa" belonging to the "tag" is set to the selected state.
In some examples, each task corresponding to each task name in the task page is divided according to the service to which the task belongs, and each task name and each service name are displayed in a tree structure (which may be referred to as a service tree), in the tree structure, each node represents one task or one service and is displayed as one task name or one service name, and a link between any two nodes represents an affiliation between two services represented by the two nodes or an affiliation between tasks and services represented by the two nodes.
As shown in fig. 4A, the respective service names and task names are displayed in a task page in a tree structure. Wherein each task is divided into a plurality of services according to the service to which the task belongs. Each service is divided into two levels, a plurality of second-level services are arranged under the first-level service, and each task is divided under each second-level service. Specifically, FIG. 4B illustrates an interface diagram showing task names in a tree structure. The node 401 is a primary service name, the node 402 is a secondary service name, and the node 403 is a task name.
In the above example, the names of the tasks are displayed in a tree structure, and the services of each level to which the tasks belong can be presented, and the dependency relationship between the tasks and the services is clear at a glance, so that the user can conveniently search the tasks, and the display space can be saved.
In some examples, the front-end browser may further perform the following: in response to the expansion operation of a user on a first node in the tree structure, showing sub-nodes of the first node and links among the sub-nodes; and hiding the sub nodes of the second node and the links among the sub nodes in the tree structure in response to the user's collapsing operation on the second node. The task related information display mode based on the tree structure enables the display mode to be very flexible, a user can further conveniently search tasks, and the display space is more effectively utilized.
In some examples, the displaying of the screened task name in the task page in step 202 may include, based on a task related information displaying manner of a tree structure: determining a third node needing to be expanded and/or a fourth node needing to be retracted in the tree structure according to each node corresponding to the screened task name; exposing the third node, children of the third node, and links therebetween, and/or hiding children of the fourth node and links therebetween. Here, the third node and the fourth node may be one or more, and their child nodes may be one or more. Furthermore, the father node of the third node can be shown as the direct father node, and can also further comprise the indirect father node.
Based on the above tree-structured task-related information display manner, the front-end browser can record the operation on the tree structure in the background server, and then can restore the operation state of the user on the tree structure last time. In some examples, the front-end browser may further perform the following:
1. responding to the expansion operation of a user on a first node in the tree structure, and sending the expansion operation information of the first node to a background server; and/or responding to the retraction operation of the user on the second node in the tree structure, and sending the retraction operation information of the second node to the background server. And the background server maintains a record of the node state for the user according to the received expansion operation information of the first node and/or the received retraction operation information of the second node. Depending on implementation, only records of the expanded state of the nodes (e.g., only records of the information of the expanded nodes), only records of the collapsed state of the nodes (e.g., only records of the information of the collapsed nodes), or records of both the expanded and collapsed states of the nodes (e.g., simultaneously records of the information of the expanded and collapsed nodes) may be maintained.
2. And responding to the access operation of the user to the task page, acquiring the node state record of the user from a background server, and determining the node which is expanded and/or packed by the user last time according to the node state record, wherein the node which is expanded last time, each child node, the parent node and the link among the nodes are displayed, and each child node of the node which is packed last time and the link among the child nodes are hidden.
In some examples, further, when the record of the node state of the user is not obtained from the background server, the front-end browser displays the task page, wherein the task page includes preset default displayed nodes (all nodes or part of nodes in the tree structure can be displayed by default, or a root node can be displayed by default), so that the expanded/contracted state of the nodes in the tree structure is restored to the state of the user when the user operates last time. According to different implementations, this situation may account for different operating situations of the user: 1. if the record of the node state maintained by the background server only comprises the information of the retracted node, the user does not execute the retraction operation; 2. if the record of the node state maintained by the background server only comprises the information of the expanded node, the expansion operation is not executed by the user; 3. if the record of the node state maintained by the background server comprises the information of the nodes which are unfolded and folded, the user is not performed the unfolding and folding operation. In any case, the tree structure in the task page can be restored to the state of the last operation of the user.
One specific example is given below. In this example, the traffic is divided in levels and tasks are divided under the traffic as leaf nodes of a tree structure. Therefore, when the user performs the expansion or contraction operation, the user operates the node representing the service or the sub-service.
When a user executes a packing operation on a node in the tree structure, a front-end browser acquires information (such as an identifier ID of a corresponding service or a sub-service) of the packed node, and records the information of the node as a data object (javascript) as follows:
here, bs1, bs3, bs4, and bs7 are identifiers of four nodes, respectively, and indicate that the four nodes are in the collapsed state. These four nodes also correspond to four services, respectively, and may be referred to as service nodes.
Then, the front-end browser encodes the data objects into a JSON character string form so as to facilitate the storage and transmission of data, and the converted JSON character string is as follows: { [ 'bs 1', 'bs 3', 'bs 4', 'bs 7' ] }. The front-end browser transmits the JSON character string to the background server through an HTTP protocol.
The background server stores the received JSON character string as a record of the node state of the user in a database, and forms a corresponding relation with the user identifier of the user, as shown in the following table 1:
| user identification | Nodal state (packed node) |
| aleche | {[‘bs1’,’bs3’,‘bs4’,‘bs7’]} |
| wekizhang | {[‘bs2’,‘bs9’,‘bs31’,‘bs33’]} |
| jasskaluo | {[‘bs10’,‘bs22’]} |
TABLE 1
Like the records of the task screening options, when a new JSON character string representing the node state comes, the background server updates the record of the user and only keeps a latest record. As shown in table 1, the backend server maintains records of node states of three users in the database, and each user name corresponds to a record of node state.
When the user leaves the task page (for example, logs out or enters other pages) and then accesses the task page again, the front-end browser can restore the last operating state of the user on the tree structure in the task page through the following processing.
The front-end browser can request the background server to query the record of the node state of the user according to the user identification (such as login name) acquired when the user logs in. Specifically, the front-end browser sends a node status query request for the user to the backend server through the HTTP protocol, where the request may carry an identifier (e.g., a login name) of the user. And the background server searches the record of the corresponding task screening item in the database through the identification of the user and returns the record to the front-end browser. For example: according to the record shown in the user login name 'aleche' lookup table 1, the record of the node state in the form of the JSON character string can be obtained: { [ 'bs 1', 'bs 3', 'bs 4', 'bs 7' ] }. The front-end browser can parse the JSON string into data objects:
the front-end browser can determine that the collapsed nodes in the tree structure include the four nodes identified as bs1, bs3, bs4, and bs7 by parsing the data object.
Correspondingly, the embodiment of the application also provides an information processing method of the task system, which is applied to the background server. As shown in fig. 5, the method includes the steps of:
step 501: receiving information aiming at a task screening item of a user from a front-end browser; the front-end browser responds to the selection operation of the user on the task screening items in the task page and sends the information of the selected task screening items to the background server.
Step 502: and creating or updating a record of the task screening items of the user in a database according to the received information of the task screening items of the user. Here, if there is no record of the user's task screen in the database, a record is created for the user, and if there is a record of the user's task screen, the existing record is updated.
Step 503: and receiving a task screening item query request of the front-end browser for the user.
Step 504: according to the received task screening item query request, acquiring a record of the task screening item of the user from the database and sending the record to the front-end browser, so that the front-end browser determines the task screening item selected by the user last time according to the record, screens out a task name corresponding to the task screening item selected by the user last time from a plurality of task names to be displayed, displays the plurality of task screening items and the screened task name in the task page, and sets the determined task screening item selected by the user last time to be in a selected state.
In some examples, the front-end browser displays each task name in a tree structure, each task corresponding to each task name in a task page is divided according to the service to which the task name belongs, and each task name and each service name are displayed in the tree structure, each node represents one task or one service, and a link between any two nodes represents an affiliation between two services represented by the two nodes or an affiliation between the tasks and services represented by the two nodes. Therefore, the front-end browser can send the operation information of the user on the nodes in the tree structure to the background server for storage.
In these examples, the backend server further performs the following:
1. and receiving expansion operation information from a first node of the front-end browser and/or receiving retraction operation information from a second node of the front-end browser. And creating or updating a record of the node state of the user in the database according to the received expansion operation information of the first node and/or the received retraction operation information of the second node. Here, if there is no record of the node status of the user in the database, a record is created for the user, and if there is a record of the node status of the user, the existing record is updated.
2. And receiving a query request aiming at the node state of the user from the front-end browser. And according to the query request of the node state, acquiring the record of the node state of the user from the database and sending the record to the front-end browser, so that the front-end browser determines the node which is expanded and/or packed last time by the user according to the record of the node state, and further displays the node which is expanded last time, each sub-node of the node and the link between the sub-nodes, and/or hides each sub-node of the node which is packed last time and the link between the sub-nodes.
The data formats of the various records of the user, which are maintained in the database by the background server, and the interaction mode between the background server and the front-end browser have been described above, and are not described herein again.
Based on the foregoing example, the present application further provides a front-end browser. As shown in fig. 6, this front-end browser 600 includes: a user interface module 601, a page data module 602, a record processing module 603, a filtering module 604, and a presentation module 605.
The user interface module 601, in response to an access operation of a user on a task page, triggers the page data module 602 to obtain page data of the task page, where the page data includes a plurality of task screening items and a plurality of task names to be displayed, and triggers the record processing module 603 to obtain a record of the task screening items of the user from a background server.
The screening module 604 determines the task screening item selected by the user last time according to the record of the task screening item acquired by the record acquisition module 603, and screens out a task name corresponding to the task screening item selected by the user last time from the plurality of task names.
The user interface module 601 is further configured to, in response to a selection operation of the user on the task screening item in the task page, trigger the record processing module 603 to send information of the selected task screening item to the background server, and trigger the screening module 604 to screen a task name corresponding to the selected task screening item from the plurality of task names; and the background server maintains a record of the task screening items for the user according to the received information of the selected task screening items.
A display module 605, configured to display the task page according to the filtering result of the filtering module 604, where the task page includes the plurality of task filtering items and the filtered task names, and when the user interface module 601 responds to the access operation of the user, set the task filtering item, which is selected by the user last time and is determined by the further filtering module 604, to be in a selected state.
In some examples, when the record processing module 603 does not obtain the record of the task screening items of the user from the background server, the presentation module 605 presents the task page, which includes the plurality of task screening items and the plurality of task names.
In some examples, each task corresponding to each task name in the task page is divided according to the service to which the task belongs, and each task name and each service name are displayed in a tree structure, in the tree structure, each node represents one task or one service and is displayed as one task name or one service name, and a link between any two nodes represents an affiliation between two services represented by the two nodes or an affiliation between the tasks and the services represented by the two nodes. The user interface module 601 is further used for triggering the display module 605 to display the sub-nodes of the first node and the links among the sub-nodes in the first node in response to the expansion operation of the user on the first node in the tree structure; further in response to the user's collapsing operation on the second node in the tree structure, triggering a presentation module 605 to hide the sub-nodes of the second node and the links therebetween; the record processing module 603 is also triggered to send the deployment operation information of the first node and/or the retraction operation information of the second node to the background server; and the background server maintains a record of the node state for the user according to the received expansion operation information of the first node and/or the received retraction operation information of the second node. The user interface module 601, in response to the access operation of the user on the task page, further triggers the record processing module 603 to obtain the record of the node status of the user from the background server. The screening module 604 determines the node that is expanded and/or collapsed last time by the user according to the record of the node state acquired by the record processing module 603. A showing module 605, which shows the last expanded node, its sub-nodes and the links between them and/or hides the sub-nodes of the last packed node and the links between them.
The application also provides a background server. As shown in fig. 7, the background server 700 includes: a transceiver module 701, a record processing module 702 and an inquiry module 703.
A transceiver module 701, which receives information of task screening options for a user from a front-end browser; the front-end browser sends information of the selected task screening items in response to the user's selection operation of the task screening items in the task page.
The record processing module 702 creates or updates a record of the task screening item of the user in a database according to the received information of the task screening item of the user.
The transceiver module 701 receives a task screening item query request of the front-end browser for the user.
The query module 703 is configured to obtain, according to the received task screening query request, a record of the task screening item of the user from the database and send the record to the front-end browser through the transceiver module 701, so that the front-end browser determines, according to the record, the task screening item selected by the user last time, screens, from the multiple task names to be displayed, a task name corresponding to the task screening item selected by the user last time, displays, in the task page, the multiple task screening items and the screened task name, and sets the determined task screening item selected by the user last time in a selected state.
In some examples, each task corresponding to each task name in the task page is divided according to the service to which the task belongs, and each task name and each service name are displayed in a tree structure, in the tree structure, each node represents one task or one service, and a link between any two nodes represents an affiliation between two services represented by the two nodes or an affiliation between the tasks and the services represented by the two nodes. The transceiver module 701 further receives the deployment operation information from the first node of the front-end browser and/or receives the retraction operation information from the second node of the front-end browser. The record processing module 702 further creates or updates a record of the node state of the user in the database according to the received expansion operation information of the first node and/or the received retraction operation information of the second node. The transceiver module 701 receives a query request for the node status of the user from the front-end browser. The query module 703 acquires the record of the node state of the user from the database according to the query request of the node state and sends the record to the front-end browser through the transceiver module 701, so that the front-end browser determines the node that is expanded and/or packed last time by the user according to the record of the node state, and further displays the node expanded last time, each sub-node thereof, and links therebetween, and/or hides each sub-node of the node packed last time and links therebetween.
The specific implementation principle of the functions of the above modules has been described in the foregoing, and is not described herein again.
In addition, the browser, the backend server and the modules in the browser, the backend server and the modules in the browser, the backend server and. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
In one embodiment, the browser and the backend server described above may be run on various computing devices and loaded into memory of the computing device.
Fig. 8 is a block diagram showing a computing device on which the front-end browser or the back-end server is located. As shown in fig. 8, the computing device includes one or more processors (CPUs) 802, a communication module 804, a memory 806, a user interface 810, and a communication bus 808 for interconnecting these components.
The processor 802 may receive and transmit data via the communication module 804 to enable network communications and/or local communications.
User interface 810 includes one or more output devices 812 including one or more speakers and/or one or more visual displays. The user interface 810 also includes one or more input devices 814, including, for example, a keyboard, a mouse, a voice command input unit or microphone, a touch screen display, a touch sensitive tablet, a gesture capture camera or other input buttons or controls, and the like.
The memory 806 may be high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; or non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.
The memory 806 stores a set of instructions executable by the processor 802, including at least:
Applications 818, may include applications for a front-end browser. In some examples, the front-end browser includes a program that enables the process flow in the examples described above. In some examples, the front-end browser can include the modules 601-605 shown in FIG. 6, and each of the modules 601-605 can store machine-executable instructions. The processor 802 can implement the functions of the modules 601-605 by executing the machine-executable instructions of the modules 601-605 in the memory 806.
Optionally, applications 818 may include backend server applications. In some examples, the backend server includes a program that enables the process flows in the examples described above. In some examples, the backend server may include each of the modules 701-703 shown in FIG. 7, and each of the modules 701-703 may store machine-executable instructions. The processor 802 can implement the functions of the modules 701-703 by executing the machine-executable instructions of the modules 701-703 in the memory 806.
In addition, each example of the present application can be realized by a data processing program executed by a data processing apparatus such as a computer. It is clear that a data processing program constitutes the present application. Further, the data processing program, which is generally stored in one storage medium, is executed by directly reading the program out of the storage medium or by installing or copying the program into a storage device (such as a hard disk and/or a memory) of the data processing device. Such a storage medium therefore also constitutes the present application. The storage medium may use any type of recording means, such as a paper storage medium (e.g., paper tape, etc.), a magnetic storage medium (e.g., a flexible disk, a hard disk, a flash memory, etc.), an optical storage medium (e.g., a CD-ROM, etc.), a magneto-optical storage medium (e.g., an MO, etc.), and the like.
The present application thus also provides a non-volatile storage medium having stored therein a data processing program for executing any one of the examples of the method of the present application.
The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the scope of the present application.
Claims (15)
1. An information processing method of a task system is applied to a front-end browser, and the method comprises the following steps:
responding to an access operation of a user on a task page, acquiring page data of the task page, wherein the page data comprises a plurality of task screening items to be displayed and a plurality of task names, and each task is established for carrying out data analysis and calculation on massive data and represents a multi-step computer execution process for completing calculation or statistical result of a certain data; acquiring a record of task screening items of the user from a background server, determining the task screening items selected when the user accesses a task page last time according to the record, and screening out task names corresponding to the task screening items selected last time by the user from the plurality of task names; when the user selects a task screening item in the task page, the front-end browser sends the information of the selected task screening item to the background server so that the background server updates the record of the task screening item corresponding to the user; displaying the task page, wherein the task page comprises the plurality of task screening items and screened task names, and setting the determined task screening item selected by the user last time to be in a selected state;
responding to the selection operation of the user on the task screening items in the task page, sending the information of the selected task screening items to the background server, screening task names corresponding to the selected task screening items from the task names, and displaying the screened task names in the task page.
2. The method of claim 1, further comprising: and when the record of the task screening items of the user is not obtained from the background server, displaying the task page, wherein the task page comprises the plurality of task screening items and the plurality of task names.
3. The method according to claim 1, wherein each task corresponding to each task name in the task page is divided according to the service to which the task belongs, and each task name and each service name are displayed in a tree structure, each node represents one task or one service and is displayed as one task name or one service name in the tree structure, and a link between any two nodes represents an affiliation between two services represented by the two nodes or an affiliation between tasks and services represented by the two nodes.
4. The method of claim 3, further comprising:
in response to the expansion operation of the user on a first node in the tree structure, showing sub-nodes of the first node and links among the sub-nodes;
hiding the sub-nodes of the second node and the links between the sub-nodes in response to the user's collapsing operation on the second node in the tree structure.
5. The method of claim 4, wherein presenting the screened task name in the task page comprises:
determining a third node needing to be expanded and/or a fourth node needing to be retracted in the tree structure according to each node corresponding to the screened task name;
and displaying the third node, the sub-nodes of the third node and the links among the sub-nodes, and/or hiding the sub-nodes of the fourth node and the links among the sub-nodes.
6. The method of claim 4, wherein the method further comprises:
responding to the expansion operation of the user on the first node in the tree structure, and sending the expansion operation information of the first node to the background server; and/or responding to the retraction operation of the user on the second node in the tree structure, and sending retraction operation information of the second node to the background server;
the background server maintains a record of the node state for the user according to the received expansion operation information of the first node and/or the received retraction operation information of the second node;
and responding to the access operation of the user to the task page, acquiring a record of the node state of the user from the background server, and determining the node which is expanded and/or packed last time by the user according to the record of the node state, wherein the node which is expanded last time, each sub-node thereof and the link between the nodes are shown, and/or each sub-node which hides the node which is packed last time and the link between the sub-nodes are shown.
7. An information processing method of a task system is applied to a background server, and the method comprises the following steps:
receiving information aiming at a task screening item of a user from a front-end browser; when the user selects a task screening item in a task page, the front-end browser responds to the selection operation of the user and sends information of the selected task screening item to the background server, wherein each task is established for carrying out data analysis and calculation on mass data and represents a multi-step computer execution process for completing calculation or statistical result of a certain data;
creating or updating a record of the task screening items of the user in a database according to the received information of the task screening items of the user;
receiving a task screening item query request of the front-end browser for the user;
according to the received task screening item query request, acquiring a record of the task screening item of the user from the database and sending the record to the front-end browser, so that the front-end browser determines the task screening item selected when the user accesses a task page last time according to the record, screens out a task name corresponding to the task screening item selected last time by the user from a plurality of task names to be displayed, displays the task screening items and the screened task names in the task page, and sets the determined task screening item selected last time by the user to be in a selected state.
8. The method according to claim 7, wherein each task corresponding to each task name in the task page is divided according to the service to which the task corresponds, and each task name and each service name are displayed in a tree structure, wherein each node represents one task or one service, and a link between any two nodes represents an affiliation between two services represented by the two nodes or an affiliation between tasks and services represented by the two nodes;
receiving expansion operation information from a first node of the front-end browser and/or receiving retraction operation information from a second node of the front-end browser;
creating or updating a record of the node state of the user in the database according to the received expansion operation information of the first node and/or the received retraction operation information of the second node;
receiving a query request aiming at the node state of the user from the front-end browser;
and according to the query request of the node state, acquiring the record of the node state of the user from the database and sending the record to the front-end browser, so that the front-end browser determines the node which is expanded and/or packed last time by the user according to the record of the node state, and then displays the node which is expanded last time, each sub-node of the node and the link between the sub-nodes, and/or hides each sub-node of the node which is packed last time and the link between the sub-nodes.
9. A front-end browser, comprising: the system comprises a user interface module, a page data module, a record processing module, a screening module and a display module; wherein the content of the first and second substances,
the user interface module responds to an access operation of a user on a task page, and triggers the page data module to acquire page data of the task page, wherein the page data comprises a plurality of task screening items and a plurality of task names to be displayed, each task is established for carrying out data analysis and calculation on mass data and represents a multi-step computer execution process for completing calculation or statistical result of a certain data; the record processing module is also triggered to acquire the record of the task screening items of the user from a background server;
the screening module determines the task screening item selected by the user when the user accesses a task page last time according to the record of the task screening item acquired by the record processing module, and screens out the task name corresponding to the task screening item selected by the user last time from the plurality of task names, wherein each time the user selects and operates the task screening item in the task page, the front-end browser sends the information of the selected task screening item to the background server so that the background server updates the record of the task screening item corresponding to the user;
the user interface module is further used for responding to the selection operation of the user on the task screening items in the task page, triggering the record processing module to send the information of the selected task screening items to the background server, and triggering the screening module to screen out task names corresponding to the selected task screening items from the task names;
the display module displays the task page according to the screening result of the screening module, wherein the task page comprises the plurality of task screening items and the screened task names, and when the user interface module responds to the access operation of the user, the display module further sets the task screening item selected by the user last time and determined by the screening module to be in a selected state.
10. The browser of claim 9,
when the record processing module does not obtain the record of the task screening items of the user from the background server, the display module displays the task page, wherein the task page comprises the plurality of task screening items and the plurality of task names.
11. The browser according to claim 9, wherein each task corresponding to each task name in the task page is divided according to the service to which the task corresponds, and each task name and each service name are displayed in a tree structure, in the tree structure, each node represents one task or one service and is displayed as one task name or one service name, and a link between any two nodes represents an affiliation between two services represented by the two nodes or an affiliation between tasks and services represented by the two nodes;
the user interface module is further used for responding to the expansion operation of the user on the first node in the tree structure, and triggering the display module to display the sub-nodes of the first node and the links among the sub-nodes; further responding to the user's retraction operation on a second node in the tree structure, triggering the presentation module to hide sub-nodes of the second node and links among the sub-nodes; the record processing module is also triggered to send the expansion operation information of the first node and/or the retraction operation information of the second node to the background server; the background server maintains a record of the node state for the user according to the received expansion operation information of the first node and/or the received retraction operation information of the second node;
the user interface module is used for responding to the access operation of the user to the task page and further triggering the record processing module to acquire the record of the node state of the user from the background server;
the screening module is used for determining the nodes which are expanded and/or collected by the user last time according to the records of the node states acquired by the record processing module;
and the display module displays the nodes expanded last time, the sub-nodes and the links among the nodes expanded last time and/or hides the sub-nodes and the links among the sub-nodes of the nodes contracted last time.
12. A backend server, comprising: the system comprises a transceiver module, a record processing module and an inquiry module; wherein the content of the first and second substances,
the receiving and sending module receives information aiming at a task screening item of a user from a front-end browser; when the user selects a task screening item in a task page, the front-end browser sends information of the selected task screening item to the background server in response to the selection operation of the user, wherein each task is established for carrying out data analysis and calculation on mass data and represents a multi-step computer execution process for completing calculation or statistical result of a certain data;
the record processing module is used for creating or updating a record of the task screening items of the user in a database according to the received information of the task screening items of the user;
the receiving and sending module receives a task screening item query request of the front-end browser for the user;
the query module acquires a record of the task screening items of the user from the database according to the received task screening item query request, and sends the record to the front-end browser through the transceiver module, so that the front-end browser determines the task screening items selected by the user last time according to the record, screens out task names corresponding to the task screening items selected by the user last time from a plurality of task names to be displayed, displays the task screening items and the screened task names in the task page, and sets the determined task screening items selected by the user last time to be in a selected state.
13. The background server of claim 12, wherein each task corresponding to each task name in the task page is divided according to the service to which the task corresponds, and each task name and each service name are displayed in a tree structure, in the tree structure, each node represents one task or one service, and a link between any two nodes represents an affiliation between two services represented by the two nodes or an affiliation between tasks and services represented by the two nodes;
the transceiver module is further used for receiving expansion operation information from a first node of the front-end browser and/or receiving retraction operation information from a second node of the front-end browser;
the record processing module is further configured to create or update a record of the node state of the user in the database according to the received expansion operation information of the first node and/or the received retraction operation information of the second node;
the transceiver module receives a query request aiming at the node state of the user from the front-end browser;
the query module acquires the record of the node state of the user from the database according to the query request of the node state and sends the record to the front-end browser through the transceiver module, so that the front-end browser determines the node which is expanded and/or packed last time by the user according to the record of the node state, and then displays the node which is expanded last time, each sub-node of the node and the link between the nodes, and/or hides each sub-node of the node which is packed last time and the link between the sub-nodes.
14. A computing device comprising a processor and a memory; the memory stores a data processing program which, when executed by the processor, causes the processor to perform the steps of the method of any one of claims 1 to 8.
15. A non-volatile storage medium having a data processing program stored thereon, wherein the data processing program, when executed by a processor, implements the steps of the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610847093.0A CN107870805B (en) | 2016-09-23 | 2016-09-23 | Information processing method and device of task system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610847093.0A CN107870805B (en) | 2016-09-23 | 2016-09-23 | Information processing method and device of task system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107870805A CN107870805A (en) | 2018-04-03 |
| CN107870805B true CN107870805B (en) | 2021-06-25 |
Family
ID=61751692
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610847093.0A Active CN107870805B (en) | 2016-09-23 | 2016-09-23 | Information processing method and device of task system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107870805B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110704735B (en) * | 2019-09-24 | 2022-01-28 | 贝壳技术有限公司 | Front-end implementation method and device of list page |
| CN114860126B (en) * | 2022-05-25 | 2024-04-05 | 北京字跳网络技术有限公司 | Collaborative task processing method, device, equipment and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981820A (en) * | 2011-09-29 | 2013-03-20 | 微软公司 | Automatic lifecycle management for pages on a mobile application |
| CN104991778A (en) * | 2015-07-15 | 2015-10-21 | 北京京东尚科信息技术有限公司 | Filtering method and apparatus based on tree structure |
| CN105335404A (en) * | 2014-07-29 | 2016-02-17 | 北京奇虎科技有限公司 | Page information loading method and device |
| CN105574755A (en) * | 2015-12-22 | 2016-05-11 | 北京奇虎科技有限公司 | Method and device of providing front-end service |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8037093B2 (en) * | 2006-09-12 | 2011-10-11 | Facebook, Inc. | Feeding updates to landing pages of users of an online social network from external sources |
-
2016
- 2016-09-23 CN CN201610847093.0A patent/CN107870805B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981820A (en) * | 2011-09-29 | 2013-03-20 | 微软公司 | Automatic lifecycle management for pages on a mobile application |
| CN105335404A (en) * | 2014-07-29 | 2016-02-17 | 北京奇虎科技有限公司 | Page information loading method and device |
| CN104991778A (en) * | 2015-07-15 | 2015-10-21 | 北京京东尚科信息技术有限公司 | Filtering method and apparatus based on tree structure |
| CN105574755A (en) * | 2015-12-22 | 2016-05-11 | 北京奇虎科技有限公司 | Method and device of providing front-end service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107870805A (en) | 2018-04-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11348294B2 (en) | Systems and methods for updating a third party visualization in response to a query | |
| CN105431844B (en) | Third party for search system searches for application | |
| CN110309264B (en) | Method and device for acquiring geographic product data based on knowledge graph | |
| US8312125B1 (en) | System and method for bulk web domain generation and management | |
| CN101488151B (en) | System and method for gathering website contents | |
| US20110136542A1 (en) | Method and apparatus for suggesting information resources based on context and preferences | |
| JP2017157192A (en) | Method of matching between image and content item based on key word | |
| Baumgarten et al. | User-driven navigation pattern discovery from internet data | |
| CN104899220A (en) | Application program recommendation method and system | |
| JP6363682B2 (en) | Method for selecting an image that matches content based on the metadata of the image and content | |
| US11477263B2 (en) | Identifying un-deployed features of an application | |
| CN104899306B (en) | Information processing method, information display method and device | |
| US20150227566A1 (en) | Content Display Device, Content Display System, Data Structure, Content Display Method, and Content Display Program | |
| CN103246699A (en) | Method and device for data access control based on browser | |
| KR102024998B1 (en) | Extracting similar group elements | |
| KR20190058141A (en) | Method for generating data extracted from document and apparatus thereof | |
| CN104809173A (en) | Search result processing method and device | |
| CN107870805B (en) | Information processing method and device of task system | |
| Spitz et al. | Topexnet: entity-centric network topic exploration in news streams | |
| WO2023082645A1 (en) | Information processing method and apparatus, and device and storage medium | |
| CN105095404A (en) | Method and apparatus for processing and recommending webpage information | |
| CN115470489A (en) | Detection model training method, detection method, device and computer readable medium | |
| JP2016521889A (en) | Cross model filtering | |
| CN110209885B (en) | Graph query method and system | |
| US20090024560A1 (en) | Method and apparatus for having access to web page |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |