CN115129404A

CN115129404A - Information processing method and device based on task

Info

Publication number: CN115129404A
Application number: CN202110322528.0A
Authority: CN
Inventors: 潘昱昊; 赵立悦
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2021-03-25
Filing date: 2021-03-25
Publication date: 2022-09-30

Abstract

The embodiment of the application provides an information processing method based on tasks. In one example, a client may retrieve at least one task associated with a first user and having a tag. The tag is an additional attribute of the at least one task, and the tag can be shared within a preset range determined by the authority of the tag. After the at least one task is obtained, information corresponding to each task in the at least one task can be presented on a first page displayed by the client. Therefore, by the aid of the scheme, the first user can check the information of at least one task related to the first user on the first page without respectively opening the pages corresponding to the labels, operation of the user is simple, and efficiency of checking the tasks related to the user is improved.

Description

Information processing method and device based on task

Technical Field

The present application relates to the field of information processing, and in particular, to a task-based information processing method.

Background

Currently, some applications may provide task creation functionality. In one example, a tag may also be added to a task. In practical application, for a certain user, if the user participates in a plurality of projects completed by cooperation of a plurality of persons, the user has a need for viewing a task related to a certain project and a need for centralized viewing and management of tasks related to the user. If the user needs to check the tasks related to the user, the user needs to open the pages of the tags of the tasks respectively so as to check the tasks. The user operation is complicated and the efficiency is low.

Therefore, a solution to the above problems is urgently needed.

Disclosure of Invention

The technical problem to be solved by the application is how to improve the efficiency of checking the tasks related to the user by the user, and the task-based information processing method is provided.

In a first aspect, an embodiment of the present application provides a method for processing information based on a task, where the method includes:

the method comprises the steps of obtaining at least one task which is related to a first user and is provided with a label, wherein the label is an additional attribute of the at least one task, and the label is shared within a preset range determined by the authority of the label;

displaying information corresponding to each task in the at least one task on a first page, wherein the first page is as follows: a page displayed on a client that logs into the account of the first user.

Optionally, the task related to the first user includes any one or more of the following:

the creator is a task of the first user, the performer is a task of the first user, and a task of interest to the first user.

Optionally, the at least one task includes a first task, and the information of the first task includes any one or more of the following:

a tag possessed by the first task, a creator of the first task, an executor of the first task, an expiration date of the first task, a status of the first task, and summary information of the first task.

Optionally, information corresponding to each task in the at least one task is displayed in the first page in a form of a list, the information of one task corresponds to one record in the list, and a header of the list is used to indicate content included in the information of each task.

Optionally, the method further includes:

and in response to the task information selection operation triggered by the first user aiming at the head of the list, determining the content included in the information of each task displayed on the first page.

Optionally, the information of each task in the at least one task is arranged in the following sequence: the expiration dates of each task in the at least one task are in a near-to-far order.

Optionally, the method further includes:

and in response to a position moving operation triggered by a first user for a first task in the at least one task, modifying the display position of the first task in the first page.

Optionally, the method further includes:

responding to task screening operation triggered by the first user, and acquiring screening conditions of at least one dimension;

determining tasks meeting the screening condition from the at least one task;

and displaying the information of the task obtained by screening.

Optionally, the at least one dimension includes:

tags, creator, performer, expiration date, and status.

Optionally, the at least one task includes: a first task provided with a first tag, the method further comprising:

creating the first task in response to task creation operation triggered by a user in an overview page of the first tag, wherein the overview page of the first tag is used for displaying information of each information field with the first tag in a partitioned mode; or,

and creating the first task in response to a task creating operation triggered by a user in a page corresponding to the task information field of the first tag, wherein the page corresponding to the task information field is used for displaying information of the task with the first tag.

responding to a tag adding operation triggered by a user in a page corresponding to a first task, and acquiring a first tag corresponding to the tag adding operation;

and storing the association relationship between the first task and the first label.

and in response to a tag canceling operation triggered by a user in a page corresponding to the task information domain of the first tag, deleting the association relationship between the first task and the first tag, wherein after the association relationship between the first task and the first tag is deleted, the first task is not included in the overview page of the first tag and the page corresponding to the task information domain.

In a second aspect, an embodiment of the present application provides an information processing method, where the method includes:

responding to an information adding operation which is triggered by a user and aims at a first information domain, and displaying a first information adding page, wherein the first information adding page comprises identifiers of a plurality of information domains, and the plurality of information domains comprise the first information domain and a second information domain;

responding to selection operation triggered by the user aiming at the identifier of the second information domain, and displaying candidate information corresponding to the second information domain, wherein the second information domain is different from the first information domain;

and generating the association relation between the at least one piece of information and the first label in response to the selection operation triggered by the user for at least one piece of candidate information.

Optionally, the responding to the information adding operation triggered by the user and aiming at the first information domain includes:

responding to an information adding operation, triggered by the user in an overview page of a first label, aiming at the first information field, wherein the overview page of the first label is used for displaying information of each information field with the first label in a sub-region mode.

Optionally, in response to the first information adding page presented by the information adding operation for the first information domain, the candidate information corresponding to the first information domain is also presented by default.

Optionally, the method further includes:

and displaying the at least one piece of information in a page of the first label corresponding to the second information field.

Optionally, the method further includes:

responding to an information adding operation aiming at a first information domain triggered by the user in an overview page of a first label, and displaying a second information adding page, wherein the overview page of the first label is used for displaying information of each information domain with the first label in a regional mode;

acquiring first information which is added in the second information adding page by the user and corresponds to the first information domain;

and generating an incidence relation between the first information and the first label.

Optionally, the method further includes:

displaying the first information in the overview page, and,

and displaying the first information in a page of the first label corresponding to the first information domain.

Optionally, the method further includes:

and responding to collaborator editing operation triggered by the user in the overview page, acquiring information of the edited collaborators, and generating the corresponding relation between the edited collaborators and the first tag.

Optionally, the collaborator modifies operations, including:

adding operation by the collaborators, or deleting operation by the collaborators, or modifying operation by the collaborators; wherein the collaborator modification operation is to modify the first collaborator to the second collaborator.

Optionally, each information field having the information quantity of the first tab is displayed in the overview page of the first tab, and each information field includes the first information field; the method further comprises the following steps:

and responding to preset operation triggered by the user aiming at the information quantity corresponding to the first information domain, and displaying a page corresponding to the first information domain of the first label, wherein the page corresponding to the first information domain comprises an information abstract of the information corresponding to the first information domain and provided with the first label.

Optionally, the method further includes:

responding to a preset operation triggered by the user aiming at second information in the overview page of the first label, and jumping to a page comprising the second information; or,

responding to preset operation triggered by the user aiming at second information in the overview page, and displaying the second information, wherein the user has the viewing permission of the second information;

and the overview page of the first label is used for displaying the information of each information domain with the first label in a partitioned mode.

Optionally, the second information is an instant messaging message, and the method further includes:

and presenting the context information of the second information.

Optionally, the method further includes:

and responding to a preset operation triggered by the user in a page comprising the second information, and displaying the overview page.

Optionally, the second information is a group, and the displaying the second information includes:

and displaying an instant conversation interface corresponding to the group in a first area in the overview page.

Optionally, the method further includes:

receiving instant session messages input by the user in the first area, wherein the user is a user included in the group;

and displaying the instant session message in the instant session interface.

Alternatively to this, the first and second parts may,

the first information field is any one of the following items: tasks, cloud documents, messages, schedules, and groups;

the second information field is any one of the following items: tasks, cloud documents, messages, schedules, and groups.

In a third aspect, an embodiment of the present application provides a task-based information processing apparatus, where the apparatus includes:

the system comprises a first acquisition unit, a second acquisition unit and a third acquisition unit, wherein the first acquisition unit is used for acquiring at least one task which is related to a first user and is provided with a label, the label is an additional attribute of the at least one task, and the label is shared within a preset range determined by the authority of the label;

a first display unit, configured to display information corresponding to each task in the at least one task on a first page, where the first page is: a page displayed on a client that logs into the account of the first user.

Optionally, the at least one task includes a first task, and the information of the first task includes any one or more of the following items:

Optionally, information corresponding to each task in the at least one task is displayed in the first page in a list form, the information of one task corresponds to one record in the list, and a header of the list is used to indicate content included in the information of each task.

Optionally, the apparatus further comprises:

a first determining unit, configured to determine, in response to a task information selection operation triggered by the first user with respect to the header, content included in the information of each task displayed on the first page.

Optionally, the apparatus further comprises:

and the modifying unit is used for modifying the display position of the first task in the first page in response to the position moving operation triggered by the first user aiming at the first task in the at least one task.

Optionally, the apparatus further comprises:

the second acquisition unit is used for responding to task screening operation triggered by the first user and acquiring screening conditions of at least one dimension;

a second determining unit, configured to determine, from the at least one task, a task that meets the screening condition;

and the second display unit is used for displaying the information of the tasks obtained by screening.

Optionally, the at least one dimension includes:

tags, creator, performer, expiration date, and status.

Optionally, the at least one task includes: -a first task provided with a first label, the apparatus further comprising a creating unit for:

and creating the first task in response to task creating operation triggered by a user in a page corresponding to the task information field of the first label, wherein the page corresponding to the task information field is used for displaying information of the task with the first label.

Optionally, the at least one task includes: a first task provided with a first tag, the apparatus further comprising:

a third obtaining unit, configured to obtain, in response to a tag addition operation triggered by a user in a page corresponding to a first task, a first tag corresponding to the tag addition operation;

and the storage unit is used for storing the association relationship between the first task and the first label.

and the deleting unit is used for responding to a tag canceling operation triggered by a user in a page corresponding to the task information domain of the first tag, deleting the association relation between the first task and the first tag, and after the association relation between the first task and the first tag is deleted, excluding the first task from the overview page of the first tag and the page corresponding to the task information domain.

In a fourth aspect, an embodiment of the present application provides an information processing apparatus, including:

the information adding device comprises a first display unit, a second display unit and a display unit, wherein the first display unit is used for responding to information adding operation which is triggered by a user and aims at a first information domain, and displaying a first information adding page, the first information adding page comprises identifiers of a plurality of information domains, and the plurality of information domains comprise the first information domain and a second information domain;

a second display unit, configured to display candidate information corresponding to a second information domain in response to a selection operation triggered by the user with respect to an identifier of the second information domain, where the second information domain is different from the first information domain;

a first generating unit, configured to generate an association relationship between at least one piece of information and the first tag in response to a selection operation triggered by the user for the at least one piece of candidate information.

Optionally, the responding to the user-triggered information adding operation for the first information domain includes:

responding to an information adding operation aiming at a first information field triggered by the user in an overview page of the first label, wherein the overview page of the first label is used for displaying information of each information field with the first label in a sub-area mode.

Optionally, the apparatus further comprises:

and the third display unit is used for displaying the at least one piece of information in a page corresponding to the second information field of the first label.

Optionally, the apparatus further comprises:

the fourth display unit is used for responding to information adding operation, triggered by the user, aiming at the first information field in the overview page of the first label, and displaying a second information adding page, wherein the overview page of the first label is used for displaying information of each information field with the first label in a subarea mode;

a first obtaining unit, configured to obtain first information corresponding to the first information domain, which is added in the second information adding page by the user;

and the second generating unit is used for generating the association relation between the first information and the first label.

Optionally, the apparatus further comprises:

a fifth display unit for displaying the first information in the overview page, and,

a sixth display unit, configured to display the first information in a page of the first tag corresponding to the first information field.

Optionally, the apparatus further comprises:

a second obtaining unit, configured to obtain information of the edited collaborators in response to collaborator editing operation triggered by the user in the overview page, and generate a corresponding relationship between the edited collaborators and the first tag.

Optionally, the collaborator modifies operations, including:

Optionally, each information field having the information quantity of the first tab is displayed in the overview page of the first tab, and each information field includes the first information field; the device further comprises:

a seventh display unit, configured to display, in response to a preset operation triggered by the user for an information amount corresponding to the first information domain, a page of the first tag corresponding to the first information domain, where the page corresponding to the first information domain includes an information summary of the information corresponding to the first information domain and that includes the first tag.

Optionally, the apparatus further comprises:

the jumping unit is used for responding to preset operation triggered by the user aiming at second information in the overview page of the first label and jumping to a page comprising the second information; or,

the eighth display unit is used for responding to preset operation triggered by the user aiming at second information in the overview page and displaying the second information, wherein the user has the viewing permission of the second information;

the overview page of the first tag is used for displaying the information of each information domain with the first tag in a regional mode.

Optionally, the second information is an instant messaging message, and the apparatus further includes:

and the presenting unit is used for presenting the context information of the second information.

Optionally, the apparatus further comprises:

a ninth display unit, configured to display the overview page in response to a preset operation triggered by the user in a page including the second information.

Optionally, the second information is a group, and the eighth display unit is configured to:

Optionally, the apparatus further comprises:

a receiving unit, configured to receive an instant session message input by the user in the first area, where the user is a user included in the group;

a tenth display unit, configured to display the instant session message in the instant session interface.

Optionally, the method may be characterized in that,

In a fifth aspect, an embodiment of the present application provides an apparatus, which includes a processor and a memory;

the processor is configured to execute instructions stored in the memory to cause the apparatus to perform the method of any one of the above first aspects or the above second aspect.

In a sixth aspect, embodiments of the present application provide a computer-readable storage medium, including instructions that instruct a device to perform the method of any one of the above first aspects or the above second aspects.

In a seventh aspect, the present application provides a computer program product, which when run on a computer, causes the computer to execute the method of any one of the above first aspects or the above second aspects.

Compared with the prior art, the embodiment of the application has the following advantages:

The embodiment of the application provides an information processing method. In one example, a user may trigger an information addition operation for a first information domain. After the user triggers the information adding operation, the client may respond to the operation and display a first information adding page. The first information adding page comprises a plurality of information domain identifications, and the plurality of information domains comprise the first information domain and the second information domain. At this time, the user may perform a selection operation triggered by the identifier of the second information field, and the client may display candidate information corresponding to the second information field in response to the selection operation triggered by the user by the identifier of the second information field. The second information field referred to herein is different from the first information field. Further, the user may perform a selection operation triggered by the user for at least one of the candidate information, and the client may generate the association relationship between the at least one information and the first tag in response to the selection operation triggered by the user for the at least one of the candidate information. Therefore, according to the scheme, even if the user triggers the information adding operation aiming at the first information field in the overview page of the first label, the information of the second information field with the first label can be added.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art without creative efforts.

Fig. 1 is a schematic flowchart of a task-based information processing method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a first page provided in the embodiment of the present application;

fig. 3 is a schematic flowchart of an information processing method according to an embodiment of the present application;

FIG. 4a is a schematic diagram of an overview page of a first tab provided in an embodiment of the present application;

fig. 4b is a schematic diagram of an information adding page provided in the embodiment of the present application;

fig. 4c is a schematic diagram of another information adding page provided in the embodiment of the present application;

FIG. 5 is a schematic structural diagram of a task-based information processing apparatus according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an information processing apparatus according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The inventor of the present application finds, through research, that there may be many tasks related to a certain user, and if the user needs to view the tasks related to the user, the user needs to open the associated pages of the tags of the tasks to view the tasks. For example, there are 3 tasks associated with user a, with tag 1, tag 2, and tag 3 for each of the three tasks. User a needs to open the page corresponding to tab 1 to view task 1, user a needs to open the page corresponding to tab 2 to view task 2, and user a needs to open the page corresponding to tab 3 to view task 3. The user operation is complicated and the efficiency is low.

In order to solve the above problem, embodiments of the present application provide a method and an apparatus for task-based information processing.

Various non-limiting embodiments of the present application are described in detail below with reference to the accompanying drawings.

Exemplary method

Referring to fig. 1, the figure is a schematic flowchart of a task-based information processing method according to an embodiment of the present application.

The method provided by the embodiment of the application can be executed by a client, and in the embodiment of the application, a target application program can be installed on the client. The first user mentioned in the embodiment of the present application refers to a user corresponding to an account for logging in the target application program on the client.

The "#" in the drawings of the embodiments of the present application is a tag identifier, and of course, the tag identifier is not limited to "#" and may be other symbols.

The following method shown in fig. 1 and method shown in fig. 3 may be combined and referred to one another without conflict.

All drawings in the embodiments of the present application, such as fig. 2, fig. 4a, fig. 4b, and fig. 4c, are only shown for convenience of understanding contents related to the embodiments of the present application, and do not constitute a limitation to the embodiments of the present application. Other contents may also be included in the pages shown in fig. 2, fig. 4a, fig. 4b, and fig. 4c, and embodiments of the present application are not particularly limited.

In this embodiment, the method shown in fig. 1 may include the following steps, for example: S101-S102.

S101: the method comprises the steps of obtaining at least one task which is related to a first user and is provided with a label, wherein the label is an additional attribute of the at least one task, and the label is shared within a preset range determined by the authority of the label.

In the embodiment of the present application, the task related to the first user may include three cases. The first case is a task created by the first user, i.e. a task for which the creator is the first user. The second case is where the first user is a task of the performer. For example, created by the second user and specifying a task to be performed by an executor including the first user. As another example, the task is created by the first user itself and specifies the task performed by the first user. The third case is a task that the first user is interested in. For example, a first user is a project supervisor who focuses on tasks related to the project to learn the progress of execution of the project.

It should be noted that, in the embodiment of the present application, the tag is not a tag that can only be used locally at the client of the first user, but is a tag that can be shared within a certain range. Specifically, the sharing range of the tag may be determined by the authority of the tag. Taking the first tag as an example, the sharing property of the tag will be described.

In one example, the rights of the first tag may include usage rights. The usage right refers to a right to add a first tag to an information unit. Specifically, the user having the right to use the first tag may add the first tag to the information unit on the corresponding client. The usage right of the first tag may be set by an owner of the first tag, and the owner of the first tag may designate a user having the usage right of the first tag.

In yet another example, the permissions of the first label include viewing permissions. The viewing right refers to a right to view the associated information of the first tag. Specifically, the method comprises the following steps: and displaying the associated information of the first label on the client of the user with the viewing authority of the first label. In other words, the user having the viewing right of the first tag can view the related information of the first tag at the corresponding client.

In some embodiments, it is contemplated that the information units themselves also possess viewing rights. For a first user with the viewing right of the first tag, the associated information of the first tag presented on the client of the first user may be information that the first user has the viewing right. In other words, the associated information of the first tag presented on the client of the first user does not include the information that the first user does not have the viewing right. Therefore, the information safety can be effectively protected, and information leakage caused by the fact that the first user checks the information which does not have the checking authority is avoided. In one example, for a first information unit with viewing permission of a first user, if the first information unit has a first tag, the first tag and the first information unit may be presented in association on a client of the first user. In this way, the first user can determine the specific content of the first information unit according to the first label and the first information unit presented in association, and determine that the first information unit has the first label.

S102: displaying information corresponding to each task in the at least one task on a first page, wherein the first page is as follows: a page displayed on a client that logs into the account of the first user.

After the at least one task is obtained, the client may display information corresponding to each task in the at least one task on a first page displayed by the client. Therefore, the first user can check the information of at least one task related to the first user on the first page without respectively opening the pages corresponding to the labels, the user operation is simple, and the efficiency of checking the tasks related to the first user by the user is improved.

The information about the at least one task is exemplified by a first task of the at least one task. The information of the first task refers to information related to the first task. The information of the first task includes, but is not limited to, any one or more of the following:

Wherein: the state of the first task may include: completed or incomplete; the summary information of the first task may be, for example, a subject of the first task, or may be, for example, a keyword in a task description of the first task.

In some embodiments, the information corresponding to each task in the at least one task may be displayed in a list form on the first page. When displayed in the first page in a list form, information of one task may correspond to one record in the list, where content specifically included in the information of each task is indicated by a header of the list.

For example, the header of the list includes: tags, creator, performer, expiration date, status, and summary information. The information of each task in the at least one task includes: the label that each task possesses, the creator of each task, the executor of each task, the deadline of each task, the state of each task and the summary information of each task. As an example, the executor of each task may be a user name of the executor of each task, or an account avatar of the executor of each task, which is not specifically limited in the embodiment of the present application. Correspondingly, the creator of each task may be a user name of the creator of each task, or an account avatar of the creator of each task, which is not specifically limited in the embodiment of the present application.

It should be noted that the content specifically included in the header of the list may be customized by the first user. In other words, the first user may autonomously select the content specifically included in the information of each of the at least one task displayed in the first page.

In one example, the first user may trigger a task information selection operation with respect to the header, and after the first user triggers the task information selection operation, the client may determine, in response to the task information selection operation, content included in the information of each task displayed on the first page. In some embodiments, the header may include by default: tags, creator, performer, expiration date, status, and summary information. The first user may trigger a cancel operation for one or more of the tag, creator, executor, expiration date, status, and summary information, thereby deleting a portion of the information from the header. For example, if the first user clicks "creator" in the header and further triggers a control for deleting the "creator", the header of the list does not include "creator", and accordingly, the creator of each task in the at least one task is not displayed in the first page.

In some embodiments, it is contemplated that a task has an expiration date, and the closer the expiration date is to the current date, the less time remaining for completing the task. In one example, when the information of each task of the at least one task is displayed in the first page, the information of each task may be sorted in a certain order. Specifically, the method comprises the following steps: the information of each task in the at least one task is arranged in the sequence: the expiration dates of each task in the at least one task are in a near-to-far order. Therefore, the first user can intuitively determine the task with the closer example deadline according to the content displayed on the first page, and the work progress is reasonably arranged so as to avoid missing the deadline of the task.

In some embodiments, it is contemplated that, for tasks associated with the first user, while the expiration dates of some tasks are farther from the current date, these tasks may be of significant interest to, or of greater urgency to, the first user. In this case, if the tasks are sorted according to the expiration dates, the sorting positions of the tasks may be relatively backward, which is not favorable for the first user to visually check the information of the tasks. In view of this, in one implementation manner of the embodiment of the present application, the first user may adjust the display position of some or all of the at least one task. Taking the first task as an example, the first user may trigger a location movement operation for the first task, for example, dragging the first task to a target location. After the first user triggers a position moving operation for the first task, the client can modify the display position of the first task in the first page in response to the position moving operation. After the display position of the first task in the first page is modified, if the user accesses the page used for presenting the information of the task related to the user next time, the display position of the first task in the page displayed by the client is the modified position, so that the user can visually check the information of the first task.

As for the first page, it can be understood with reference to fig. 2, and fig. 2 is a schematic diagram of a first page provided in an embodiment of the present application.

As shown in fig. 2, information of a plurality of tasks related to the first user is displayed in the first page, the information of the plurality of tasks is presented in a list form, and the information of one task corresponds to one record in the list. And arranged according to the order of the deadline of each task from near to far. The header of the list includes: summary information, creator, performer, status, tags, and expiration date.

In one example, the first user may drag the task corresponding to "test 3" to a position before the task corresponding to "test 1" to change the display position of the task corresponding to "test 3" in the first page.

In one example, consider that there are more tasks associated with the first user, some of which may be of greater interest to the first user. Thus, in one example, the target application may also support task screening functionality. Specifically, the method comprises the following steps: the first user may trigger a task screening operation in the first page. After the first user triggers the task screening operation, the client may obtain a screening condition of at least one dimension in response to the task screening operation, determine a task meeting the screening condition from the at least one task, and further display information of the task obtained by screening.

In one example, a task filtering control may be included in the first page, and after the first user triggers the task filtering control (e.g., clicks the task filtering control), a client may display a task filtering page in which the first user may edit a filtering condition of at least one dimension. Then, the client can obtain the screening condition of the at least one dimension.

It should be noted that at least one dimension mentioned herein may be one or more of a label, a creator, an executor, an expiration date, and a status. For example, the first user may set the filtering condition to: completed and the actor is user a. As another example, the first user may set the filtering condition as: incomplete, and date by date before date by year by month. For another example, the first user may set the filtering condition to: # A. Not to be taken as an exhaustive list.

It should be noted that, for the first task with the first tag in the at least one task, it may be created by the user in advance. Next, specific implementations of creating the first task and tagging the first task are described.

In the embodiment of the application, if the first tag is created first, the user may trigger the task creation operation in the relevant page of the first tag, so as to create the first task with the first tag.

In one example, a task creation operation may be triggered in the overview page of the first tab. After the user triggers a task creation operation, the client may create the first task in response to the task creation operation. Specifically, after the user triggers a task creation operation, the client may display a task creation page, and obtain task information input by the user in the task creation page, thereby creating the first task. The user mentioned here may be the aforementioned first user, or may be a second user different from the first user, and is not limited here. It is to be understood that if the user mentioned herein is the aforementioned first user, the first user is a creator of the first task.

As for the overview page of the first tab, it should be noted that the overview page of the first tab is a page displayed in each information area of the first tab in a divided information area. Wherein, the information fields include but are not limited to: one or more of a task, a cloud document, a message, a calendar, and a group. Specifically, the method comprises the following steps: and on the client of the first user, the overview page of the first label is used for displaying the information of each information field which has the first label and the viewing permission of the first user. The overview page may include a plurality of display regions, and one display region is used to display information of one of the information fields. The information field in the embodiment of the present application is used for providing a certain type of information. Wherein one information field may correspond to one service provider.

In yet another example, a task creation operation may be triggered in a page corresponding to the task information field of the first tab. After the user triggers a task creation operation, the client may create the first task in response to the task creation operation. Specifically, after the user triggers a task creation operation, the client may display a task creation page, and obtain task information input by the user in the task creation page, thereby creating the first task. The user mentioned here may be the aforementioned first user, or may be a second user different from the first user, and is not limited here. It is to be understood that if the user mentioned herein is the aforementioned first user, the first user is a creator of the first task.

Regarding the page corresponding to the task information field of the first tab, it should be noted that the page corresponding to the task information field of the first tab is used for displaying information of the task having the first tab. Specifically, the method comprises the following steps: and on the client of the first user, the page corresponding to the task information domain of the first label is used for displaying the information of the task which has the first label and the viewing permission of the first user.

In this embodiment of the present application, if a first task is created first, a user may trigger a tag addition operation in a page corresponding to the first task, so as to add the first tag to the first task. The user mentioned here may be the aforementioned first user, or may be a second user different from the first user, and is not limited here.

In an example, after the user triggers a tag adding operation in a page corresponding to a first task, the client may respond to the tag adding operation, obtain the first tag corresponding to the tag adding operation, and further save an association relationship between the first task and the first tag, thereby achieving an objective of adding the first tag to the first task. Specifically, the method comprises the following steps:

in one implementation: after the user triggers a tag addition operation in a page corresponding to the first task, the client may display a character input area in response to the tag addition operation. The user may then enter characters in the character entry area. The user may enter at least a portion of the characters included in the first label in the character entry area. Correspondingly, after the client acquires the characters input by the user, the client can provide corresponding label candidate items for the user according to the characters input by the user, and display the label candidate items, so that the user can select the first label based on the label candidate items. After the user selects the first tag, that is, the user triggers a selection operation for the first tag in the tag candidate items, for example, clicks the first tag, the client may obtain the first tag, and further store the association relationship between the first task and the first tag.

In yet another implementation: after the user triggers a tag adding operation in a page corresponding to a first task, the client may display at least one tag candidate item in response to the tag adding operation, after the at least one tag candidate item is displayed, the user may trigger a selecting operation for one of the at least one tag candidate item, and if the user triggers a selecting operation for the first tag of the at least one tag candidate item, for example, clicks the first tag, the client may acquire the first tag and further save an association relationship between the first task and the first tag.

It should be noted that, considering that a tag may have a usage right, only when a user has the usage right of a certain tag, the user can add the tag to information. Therefore, in an example, the at least one tag candidate may be a candidate for which the user has a usage right.

As described above, the page corresponding to the task information field of the first tab is used to display the information of the task having the first tab. In one example, it is contemplated that the tags it possesses may change over time for a task. For example, task A is originally associated with project 1 and project 2, but as the projects progress, task A is no longer associated with project 1. At this point, task a is no longer eligible to have a tag (e.g., the first tag) corresponding to correlation 1.

In view of this situation, in this embodiment of the present application, the user may trigger a tag canceling operation in a page corresponding to the task information field of the first tag, and accordingly, the client may respond to the tag canceling operation to delete the association relationship between the first task and the first tag. It can be understood that after the association relationship between the first task and the first tab is deleted, the overview page of the first tab no longer presents the information of the first task, and correspondingly, the information of the first task is no longer presented in the page corresponding to the task information field of the first tab.

It can be understood that, if the first task only has one tag, after the association relationship between the first task and the first tag is deleted, if the first page is refreshed, the refreshed first page does not include information of the first task any more. If the first task includes other tags besides the first tag, after the association relationship between the first task and the first tag is deleted, if the first page is refreshed, the refreshed first page may include information of the first task, but only the tag of the first task, and no longer includes the first tag.

The embodiment of the application also provides an information processing method, which is described in the following with reference to the accompanying drawings.

Referring to fig. 3, the figure is a schematic flowchart of an information processing method according to an embodiment of the present application.

Similar to the task-based information processing method shown in fig. 1, the information processing method shown in fig. 3 may also be executed by the client. The schedule creation method shown in fig. 3 may include, for example, the following S201-S203.

S201: responding to an information adding operation which is triggered by a user and aims at a first information domain, and displaying a first information adding page, wherein the first information adding page comprises a plurality of information domain identifications, and the plurality of information domains comprise the first information domain and a second information domain.

In the embodiment of the application, the user can trigger the information adding operation aiming at the first information field on the page displayed by the client. For example, a page displayed by the client may include a first control for triggering an information addition operation for a first information field. The user may trigger an information addition operation for the first information field, for example, by clicking on the first control.

In one example, the user may trigger an information add operation for a first information field in the overview page of the first tab. Regarding the overview page of the first tab, reference may be made to the above relevant description section, and the description is not repeated here.

In this embodiment of the application, after the user triggers the information adding operation for the first information domain, the client may display a first information adding page in response to the information adding operation. The first information adding page may include identifiers of a plurality of information fields, where the plurality of information fields include at least a first information field and a second information field.

Wherein: the first information field and the second information field may be different information fields. The first information field may be one of a task, a cloud document, a message, a schedule, and a group, and the second information field may be one of a task, a cloud document, a message, a schedule, and a group. For example, the first information domain is a schedule, and the second information domain is a cloud document; for another example, the first information domain is a task, and the second information domain is a cloud document; etc., not to be construed as an exhaustive list.

In one example, in a first information adding page presented by the client in response to the information adding operation for the first information domain, in addition to the identifications of the plurality of information domains, at least one candidate information corresponding to the first information domain is presented by default, so that the first user triggers a selection operation on one or more candidate information of the at least one candidate information corresponding to the first information domain, thereby achieving the purpose of adding one or more information corresponding to the first information domain. It should be noted that, in an example, at least one candidate message corresponding to the first message field is a message having a view right for the user.

S202: and responding to the selection operation triggered by the user aiming at the identification of the second information domain, and displaying the candidate information of the corresponding second information domain, wherein the second information domain is different from the first information domain.

S203: and generating the association relation between the at least one piece of information and the first label in response to the selection operation triggered by the user for at least one piece of candidate information.

In this embodiment of the application, the first information adding page includes an identifier of a second information domain, and if the user wishes to add information corresponding to the second information domain, the user may perform a selection operation triggered by the identifier of the second information domain. After the selection operation triggered by the user for the identification of the second information domain, the client may display candidate information corresponding to the second information domain to the selection operation triggered in response to the user for the identification of the second information domain. In an example, the candidate information corresponding to the second information field is information that has a viewing right for the user.

Then, the user may trigger a selection operation for at least one of the candidate information of the second information domain, so that the client may generate the corresponding relationship between the at least one information and the first tag in response to the selection operation triggered by the user for at least one of the candidate information of the second information domain. This is done for the purpose of adding at least one information corresponding to the second information field.

Therefore, according to the scheme, even if the user triggers the information adding operation aiming at the first information field, the information of the second information field with the first label can be added. In this way, the page displayed by the client, for example, the overview page of the first tab, may include the first control without including a control for triggering an information addition operation for each information field, so that the number of controls included in the page displayed by the client may be reduced, and the layout of the page displayed by the client is simpler.

The method shown in fig. 3 will now be described with reference to fig. 4a to 4c, taking an overview page in which the page displayed by the client is the first tab as an example. Fig. 4a is a schematic view of an overview page of a first tab provided in an embodiment of the present application, fig. 4b is a schematic view of an information adding page provided in the embodiment of the present application, and fig. 4c is a schematic view of another information adding page provided in the embodiment of the present application.

As shown in fig. 4a, the overview page of the first tab "M" includes information of each information field having the first tab. The first information field may be a schedule, and the user may trigger an information adding operation for the schedule by "add immediately" through a control shown in fig. 4 a. After the user triggers the information adding operation for the schedule, the client may display an information adding page shown in fig. 4b, where the information adding page includes the identifier of each information domain (i.e., the name of each information domain shown in fig. 4 b) and the information candidate of the corresponding schedule: schedule a to schedule E. The user's identification of the second information field, e.g., "cloud document", triggers a selection operation, e.g., after the user clicks "cloud document" of fig. 4b, the client may display the information addition page shown in fig. 4 c. The information adding page shown in fig. 4c includes information candidates of a corresponding cloud document: cloud document 1 to cloud document 5. If the user triggers a selection operation for the cloud document 1, the client may generate a corresponding relationship between the tag M and the cloud document 1.

It should be noted that, after executing the above S201-S203, the client may further display the at least one piece of information in a page of the first tab corresponding to the second information field. And the page of the first label corresponding to the second information domain is used for presenting the information which is provided with the first label and corresponds to the second information domain. For example, if the second information field is a cloud document, the page of the first tag corresponding to the second information field is used for presenting the cloud document with the first tag. In one example, on a client of a first user, a page of the first label corresponding to the second information field is used for presenting information which has the first label, corresponds to the second information field and has a view right for the first user.

In one example, the user may also trigger an information adding operation for the first information field in the overview page of the first tab, thereby achieving the purpose of adding information corresponding to the first information field with the first tab. Specifically, the method comprises the following steps:

after the user triggers an information adding operation for a first information field in the overview page of the first tag, the client may display a second information adding page in response to the information adding operation. The second information adding page may include, for example, an editing area for editing information corresponding to the first information field. After the second information adding page is displayed, the user can edit the information corresponding to the first information field in the editing area in the second information adding page. For example, the user may edit the first information in an editing area in the second information adding page. In this way, the client can obtain the first information and further generate the corresponding relationship between the first information and the first label.

After the client generates the corresponding relationship between the first information and the first tab, the client may further display the first information in an overview page of the first tab. For example, the first information may be displayed in a display area corresponding to the first information field in the overview page. In addition, the client may further display the first information in a page of the first tab corresponding to the first information field. The page of the first label corresponding to the first information domain is used for presenting the information which is provided with the first label and corresponds to the first information domain. In one example, if the user is the owner of the first tab, the user may also trigger a collaborator editing operation in the summary page of the first tab to edit collaborators on the first tab. The collaborators of the first label refer to users with the viewing right of the first label. And if the user has the viewing permission of the first label, the user has the permission to view the associated information of the first label. The information related to the first tag is information of each information field having the first tag.

In this embodiment, after the user triggers the collaborator editing operation, the client may obtain information of the edited collaborator in response to the collaborator editing operation, and generate the corresponding relationship between the edited collaborator and the first tag.

The collaborator editing operations referred to herein may include three operations, a collaborator add operation, a collaborator delete operation, and a collaborator modify operation, respectively. Wherein the collaborator adding operation is used for adding a new collaborator on the basis of the original collaborator; the collaborator deleting operation is used for deleting part or all of the original collaborators; the collaborator modification operations are used to modify some or all of the original collaborators, such as modifying a first collaborator to a second collaborator.

It should be noted that, the collaborator editing operation triggered by the user in the overview page may be implemented in various ways when it is implemented specifically. In one example, a collaborator editing control may be included in the overview page, and after the user triggers the control, the client displays a collaborator editing page in which the user may trigger one or more of a collaborator add operation, a collaborator delete operation, and a collaborator modify operation. In yet another example, multiple controls may be included in the overview page, adding controls for collaborators, deleting controls for collaborators, and modifying controls for collaborators, respectively. The user can trigger the operation of adding the collaborators through the collaborator adding control, the user can trigger the operation of deleting the collaborators through the collaborator deleting control, and the user can trigger the operation of modifying the collaborators through the collaborator modifying control.

As described above, the overview page of the first tab is a page displayed in which the information of each information field having the first tab is divided into regions. In one example, in the overview page of the first tab, the number of information having the first tab in each information field is displayed. As can be understood with reference to fig. 4a, fig. 4a shows that the number of tasks corresponding to the task information field is 3, the number of cloud documents corresponding to the cloud document information field is 5, the number of messages corresponding to the message information field is 1, the number of groups corresponding to the group information field is 1, and the number of schedules corresponding to the schedule information field is 1.

Considering that the overview page may have limited content that can be presented, for a first one of the various information fields, the overview page may not be able to display the various information in its entirety. The user can conveniently view the specific information in the first information domain. If the user wishes to view the specific information in the first information domain, a preset operation triggered by the information amount corresponding to the first information domain may be performed, for example, the information amount corresponding to the first information domain is clicked. In this way, the client may respond to a preset operation triggered by the user for the information amount corresponding to the first information domain, and display a page of the first tag corresponding to the first information domain, so that the user can view specific information of the first information domain.

In one example, if a user wishes to view certain information in the overview page, such as second information, the user may trigger a preset operation for the second information in the overview page, such as clicking on an information summary of the second information displayed in the overview page, to achieve the viewing of the second information.

In some embodiments, after the preset operation triggered by the user for the second information in the overview page, the client may jump to a page including the second information in response to the preset operation triggered by the user for the second information in the overview page. In this way, the user can view the second information. For example, if the second information is a group, the client may jump to a page where the group is located. For another example, if the second information is a message, the client may jump to an instant session page where the message is located. For another example, if the second information is a schedule, the client may jump to a page where the schedule is located.

In still other embodiments, after the preset operation triggered by the user for the second information in the overview page, the client may display the second information in response to the preset operation triggered by the user for the second information in the overview page. The second information mentioned here refers to information that the user has viewing rights. As an example, the second information may be displayed in a browser. As one example, the second information may be displayed in a first region (e.g., a sidebar) in the overview page. The second information is not specifically limited in the embodiment of the present application, and the second information may be any one of a task, a cloud document, a message, a schedule, and a group. In an example, if the second information is an instant messaging message, after a preset operation triggered by the user with respect to the second information in the overview page, the client may display context information of the second information in addition to the second information itself, so that the user can view the second information and the context information of the second information.

It should be noted that, when the second information is a group, for example, summary information (e.g., a name) of the group may be displayed when the second information is displayed in the first area of the overview page in a concrete implementation. In another example, an instant conversation interface corresponding to the group may be displayed in the first area.

If the client displays the instant session interface corresponding to the group in the first area of the overview page, when the user is a user in the group, the user can perform an instant communication session in the first area without jumping to the instant session interface where the group is located. Specifically, the user may input an instant session message in the first area, and after receiving the instant session message input by the user, the client may display the instant session message in the instant session interface. In addition, if other users in the group publish the instant session messages in the group, the client can also display the instant session messages published by other users in the first area.

In some embodiments, after a preset operation triggered by the user for the second information in the overview page, the client jumps to a page including the second information. In order to enable the page displayed by the client to be quickly switched from the page including the second information to the overview page, the user may further perform a preset operation triggered in the page including the second information, and accordingly, the client may display the overview page in response to the preset operation triggered by the user in the page including the second information. Therefore, the page displayed by the client side is quickly switched to the overview page. In an example, the page including the second information may further include a second control, and the preset operation triggered by the user in the page including the second information may be, for example, clicking the second control.

Exemplary device

Based on the methods provided by the above embodiments, the embodiments of the present application also provide corresponding apparatuses, which are described below with reference to the accompanying drawings.

Referring to fig. 5, a schematic structural diagram of a task-based information processing apparatus according to an embodiment of the present application is shown. The apparatus 500 may specifically include, for example: a first acquisition unit 501 and a first display unit 502.

A first obtaining unit 501, configured to obtain at least one task related to a first user and having a tag, where the tag is an additional attribute of the at least one task, and the tag is shared within a preset range determined by an authority of the tag;

a first display unit 502, configured to display information corresponding to each task in the at least one task on a first page, where the first page is: a page displayed on a client that logs into the account of the first user.

Optionally, the task related to the first user includes any one or more of:

Optionally, the apparatus further comprises:

Optionally, the at least one dimension includes:

tags, creator, performer, expiration date, and status.

Optionally, the at least one task includes: the apparatus further comprises a creating unit for:

responding to task creating operation triggered by a user in an overview page of the first label, and creating the first task, wherein the overview page of the first label is used for displaying information of each information field with the first label in a partitioned manner; or,

With regard to specific implementation of functions corresponding to the respective units of the apparatus 500, reference may be made to the above description part of the method shown in fig. 1, and a description thereof is not repeated here.

Referring to fig. 6, a schematic structural diagram of an information processing apparatus according to an embodiment of the present application is shown. The apparatus 600 may specifically include, for example: a first display unit 601, a second display unit 602, and a first generation unit 603.

A first display unit 601, configured to display a first information adding page in response to an information adding operation for a first information domain triggered by a user, where the first information adding page includes identifiers of multiple information domains, and the multiple information domains include the first information domain and a second information domain;

a second display unit 602, configured to display candidate information corresponding to a second information domain in response to a selection operation triggered by the user with respect to the identifier of the second information domain, where the second information domain is different from the first information domain;

a first generating unit 603, configured to generate an association relationship between at least one piece of information and the first tag in response to a selection operation triggered by the user for at least one piece of candidate information.

Optionally, in response to the first information addition page displayed by the information addition operation for the first information domain, the candidate information corresponding to the first information domain is also displayed by default.

Optionally, the apparatus further comprises:

and the third display unit is used for displaying the at least one piece of information in a page corresponding to the second information domain of the first label.

Optionally, the apparatus further comprises:

and the sixth display unit is used for displaying the first information in a page of the first label corresponding to the first information domain.

Optionally, the apparatus further comprises:

and the second acquisition unit is used for responding to collaborator editing operation triggered by the user in the overview page, acquiring information of the edited collaborators and generating the corresponding relation between the edited collaborators and the first label.

Optionally, the collaborator modifies operations, including:

Optionally, the apparatus further comprises:

the skipping unit is used for responding to preset operation triggered by the user aiming at second information in the overview page of the first label and skipping to a page comprising the second information; or,

Optionally, the apparatus further comprises:

Alternatively to this, the first and second parts may,

the second information field is any one of the following items: tasks, cloud documents, messages, calendars, and groups.

With regard to specific implementation of functions corresponding to the respective units of the apparatus 600, reference may be made to the above description part of the method shown in fig. 3, and a description thereof is not repeated here.

An embodiment of the present application further provides an apparatus, which includes a processor and a memory; the processor is configured to execute the instructions stored in the memory to cause the apparatus to perform the methods provided by the above method embodiments.

The embodiment of the application also provides a computer-readable storage medium which comprises instructions for instructing equipment to execute the method provided by the method embodiment.

The application embodiments also provide a computer program product, which when run on a computer causes the computer to perform the method provided by the above method embodiments.

Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice in the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the attached claims

The above description is only a preferred embodiment 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 protection scope of the present application.

Claims

1. A method for task-based information processing, the method comprising:

the method comprises the steps of obtaining at least one task which is related to a first user and is provided with a label, wherein the label is an additional attribute of the at least one task, and the label is shared in a preset range determined by the authority of the label;

2. The method of claim 1, wherein the task associated with the first user comprises any one or more of:

3. The method of claim 1, wherein the at least one task comprises a first task, and wherein the information of the first task comprises any one or more of the following:

4. The method according to any one of claims 1 to 3, wherein information corresponding to each task in the at least one task is displayed in the first page in a list form, the information of one task corresponds to one record in the list, and a header of the list is used for indicating content included in the information of each task.

5. The method of claim 4, further comprising:

6. The method according to any one of claims 1 to 5, wherein the information of each task of the at least one task is arranged in the following order: the expiration dates of each task in the at least one task are in a near-to-far order.

7. The method according to any one of claims 1-6, further comprising:

8. The method according to any one of claims 1-7, further comprising:

determining tasks meeting the screening condition from the at least one task;

and displaying the information of the task obtained by screening.

9. The method of claim 8, wherein the at least one dimension comprises:

tags, creator, performer, expiration date, and status.

10. The method of claim 1, wherein the at least one task comprises: a first task provided with a first tag, the method further comprising:

11. The method of claim 1, wherein the at least one task comprises: a first task provided with a first tag, the method further comprising:

12. The method of claim 10, wherein the at least one task comprises: a first task provided with a first tag, the method further comprising:

13. An information processing method, characterized in that the method comprises:

14. The method of claim 13, wherein the responding to the user-triggered information addition operation for the first information field comprises:

15. The method according to claim 13, wherein in the first information adding page presented in response to the information adding operation for the first information field, the candidate information corresponding to the first information field is also presented by default.

16. The method of claim 13, further comprising:

17. The method of claim 13, further comprising:

18. The method of claim 17, further comprising:

displaying the first information in the overview page, and,

19. The method of claim 13, further comprising:

20. The method of claim 19, wherein the collaborator modifies operations comprising:

21. The method of claim 13, wherein the overview page of the first tab displays therein a respective field of information, including the amount of information of the first tab; the method further comprises the following steps:

22. The method of claim 13, further comprising:

23. The method of claim 22, wherein the second message is an instant messaging message, the method further comprising:

and presenting the context information of the second information.

24. The method of claim 22, further comprising:

25. The method of claim 22, wherein the second information is a group, and wherein displaying the second information comprises:

26. The method of claim 25, further comprising:

and displaying the instant session message in the instant session interface.

27. The method of any one of claims 13 to 26,

28. A task-based information processing apparatus, characterized in that the apparatus comprises:

29. An information processing apparatus characterized in that the apparatus comprises:

the second display unit is used for responding to selection operation triggered by the user aiming at the identification of the second information domain, and displaying candidate information corresponding to the second information domain, wherein the second information domain is different from the first information domain;

30. An apparatus, comprising a processor and a memory;

the processor is to execute instructions stored in the memory to cause the device to perform the method of any of claims 1 to 27.

31. A computer-readable storage medium comprising instructions that direct a device to perform the method of any of claims 1-27.

32. A computer program product, characterized in that it causes a computer to carry out the method according to any one of claims 1 to 27 when said computer program product is run on the computer.