A schedule creation method and device

Abstract

The present application discloses a schedule creation method, which can be executed by a client. A user can trigger a schedule adding operation in the associated page of a first tag displayed on the client, and the client can display a schedule adding page in response to the schedule adding operation, and the schedule adding page includes a first tag. Among them, the associated page of the first tag is used to present the associated information of the first tag. After the schedule adding page is displayed, the user can enter the schedule information in the schedule adding page, and the client can generate a schedule with the first tag. It can be seen that, using this solution, after the user triggers the schedule adding operation in the associated page of the first tag, the first tag will be automatically brought into the schedule adding page, and further, a schedule including the first tag can be generated. There is no need for the user to first create a schedule and then add a tag to the schedule, thereby reducing the cumbersomeness of creating a schedule with a tag.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a schedule creation method and device. Background Art

[0002] In some scenarios, you need to create a schedule with a tag. For example, for a project, you can add a tag to the schedule related to the project. The project participants can use the tag to locate the schedule related to the project, so that the project participants can arrange their work schedules reasonably. However, the current method of creating a schedule with a tag is cumbersome for users to operate.

[0003] Therefore, a solution is urgently needed to solve the above problems. Summary of the invention

[0004] The technical problem to be solved by the present application is that the current method of creating a schedule with a label is relatively cumbersome for the user to operate, and a method and device for creating a schedule are provided.

[0005] In a first aspect, an embodiment of the present application provides a schedule creation method, the method comprising:

[0006] In response to a schedule adding operation triggered by a user in an associated page of a first tag, displaying a schedule adding page, wherein the schedule adding page includes the first tag, and an associated page of the first tag is used to present associated information of the first tag;

[0007] The schedule information input by the user in the schedule adding page is acquired, and a schedule having the first tag is generated.

[0008] Optionally, the method further includes:

[0009] In response to a tag editing operation triggered by the user in the schedule adding page, acquiring a second tag indicated by the tag editing operation;

[0010] The generating of the schedule having the first label includes:

[0011] A schedule including the first label and the second label is generated.

[0012] Optionally, the user triggers the tag editing operation through a tag adding control.

[0013] Optionally, in response to a tag editing operation triggered by the user in the schedule adding page, obtaining a second tag includes:

[0014] In response to a tag editing operation triggered by the user in the schedule adding page, displaying at least one tag candidate item, wherein the at least one tag candidate item includes the second tag;

[0015] In response to a selection operation triggered by the user on the second tag in the at least one tag candidate item, the second tag is acquired.

[0016] Optionally, in response to a tag editing operation triggered by the user in the schedule adding page, obtaining a second tag includes:

[0017] In response to a tag editing operation triggered by the user in the schedule adding page, characters input by the user are acquired, and the second tag is acquired according to the characters input by the user.

[0018] Optionally, the method further includes:

[0019] In the schedule page corresponding to the second tag, summary information of the schedule is displayed. The schedule page corresponding to the second tag is used to display summary information of the schedule with the second tag.

[0020] Optionally, the schedule adding page also includes: participants of the schedule, and the participants of the schedule are users who have the viewing permission of the first tag.

[0021] Optionally, the acquiring the schedule information input by the user in the schedule adding page includes:

[0022] The participants of the schedule input by the user in the schedule adding page are obtained.

[0023] Optionally, the method further includes:

[0024] If the participants of the schedule entered by the user in the schedule adding page do not have the permission of the first tag before the schedule with the first tag is generated, the participants of the schedule are granted the permission of the first tag in response to the generation of the schedule with the first tag.

[0025] Optionally, the first tag is shared among users who have permission to use the first tag.

[0026] Optionally, the permission of the first tag includes usage permission, and a user who has the usage permission of the first tag has the permission to add the first tag to the information unit on the corresponding client.

[0027] Optionally, the permission of the first tag includes viewing permission, and the associated information of the first tag is displayed on the client of the user who has the viewing permission of the first tag.

[0028] Optionally, the method further includes:

[0029] In response to the first user having the permission to view the first tag, the first tag and a first information unit are associated and presented on the client of the first user, wherein the first information unit is an information unit that the first user has the permission to view.

[0030] Optionally, the associated page of the first tag includes:

[0031] The overview page of the first tab, or the page corresponding to the schedule information field of the first tab; wherein:

[0032] The overview page is a page that displays information in summary form in each information field having the first tag; or, the page corresponding to the schedule information field is used to display information of the schedule having the first tag.

[0033] Optionally, the information corresponding to each information domain is presented in different regions in the overview page.

[0034] In a second aspect, an embodiment of the present application provides a schedule creation method, the method comprising:

[0035] In response to a schedule adding operation triggered by a user in an associated page of a first tag, displaying a schedule adding page, wherein the schedule adding page includes the first tag, and an associated page of the first tag is used to present associated information of the first tag;

[0036] In response to a tag editing operation triggered by the user in the schedule adding page, modifying the first tag to a second tag;

[0037] The schedule information input by the user in the schedule adding page is acquired, and a schedule having the second tag is generated.

[0038] Optionally, in response to a tag editing operation triggered by the user in the schedule adding page, modifying the first tag to a second tag includes:

[0039] In response to a tag editing operation triggered by the user in the schedule adding page, displaying at least one tag candidate item, wherein the at least one tag candidate item includes the second tag;

[0040] In response to a selection operation triggered by the user on the second tag in the at least one tag candidate item, the first tag is modified to a second tag.

[0041] Optionally, in response to a tag editing operation triggered by the user in the schedule adding page, modifying the first tag to a second tag includes:

[0042] In response to a tag editing operation triggered by the user in the schedule adding page, characters input by the user are acquired, the second tag is acquired according to the characters input by the user, and the first tag is modified to the second tag.

[0043] Optionally, the method further includes:

[0044] In the schedule page corresponding to the second tag, summary information of the schedule is displayed. The schedule page corresponding to the second tag is used to display summary information of the schedule with the second tag.

[0045] In a third aspect, an embodiment of the present application provides a schedule creation device, the device comprising:

[0046] A display unit, configured to display a schedule adding page in response to a schedule adding operation triggered by a user in a page associated with a first tag, wherein the schedule adding page includes the first tag, and the page associated with the first tag is configured to present associated information of the first tag;

[0047] A first acquisition unit, configured to acquire schedule information input by the user in the schedule adding page;

[0048] A generating unit is used to generate a schedule having the first tag.

[0049] Optionally, the device further comprises:

[0050] A second acquisition unit, configured to, in response to a tag editing operation triggered by the user in the schedule adding page, acquire a second tag indicated by the tag editing operation;

[0051] The generating unit is used for:

[0052] A schedule including the first label and the second label is generated.

[0053] Optionally, the user triggers the tag editing operation through a tag adding control.

[0054] Optionally, the second acquiring unit is used to:

[0055] In response to a tag editing operation triggered by the user in the schedule adding page, displaying at least one tag candidate item, wherein the at least one tag candidate item includes the second tag;

[0056] In response to a selection operation triggered by the user on the second tag in the at least one tag candidate item, the second tag is acquired.

[0057] Optionally, the second acquiring unit is used to:

[0058] In response to a tag editing operation triggered by the user in the schedule adding page, characters input by the user are acquired, and the second tag is acquired according to the characters input by the user.

[0059] Optionally, the device further comprises:

[0060] The first display unit is used to display summary information of the schedule in the schedule page corresponding to the second tag, and the schedule page corresponding to the second tag is used to display summary information of the schedule with the second tag.

[0061] Optionally, the schedule adding page also includes: participants of the schedule, and the participants of the schedule are users who have the viewing permission of the first tag.

[0062] Optionally, the first acquiring unit is used to:

[0063] The participants of the schedule input by the user in the schedule adding page are obtained.

[0064] Optionally, the device further comprises:

[0065] The permission setting unit is used to: if the participants of the schedule entered by the user in the schedule adding page do not have the permission of the first tag before the schedule with the first tag is generated, then in response to the generation of the schedule with the first tag, grant the participants of the schedule the permission of the first tag.

[0066] Optionally, the first tag is shared among users who have permission to use the first tag.

[0067] Optionally, the permission of the first tag includes usage permission, and a user who has the usage permission of the first tag has the permission to add the first tag to the information unit on the corresponding client.

[0068] Optionally, the permission of the first tag includes viewing permission, and the associated information of the first tag is displayed on the client of the user who has the viewing permission of the first tag.

[0069] Optionally, the device further comprises:

[0070] The second display unit is used to present the first tag and the first information unit in association on the client of the first user in response to the first user having the viewing permission of the first tag, wherein the first information unit is an information unit that the first user has the viewing permission.

[0071] Optionally, the associated page of the first tag includes:

[0072] The overview page of the first tab, or the page corresponding to the schedule information field of the first tab; wherein:

[0073] The overview page is a page that displays information in summary form in each information field having the first tag; or, the page corresponding to the schedule information field is used to display information of the schedule having the first tag.

[0074] Optionally, the information corresponding to each information domain is presented in different regions in the overview page.

[0075] In a fourth aspect, an embodiment of the present application provides a schedule creation device, the device comprising:

[0076] A first display unit, configured to display a schedule adding page in response to a schedule adding operation triggered by a user in a first tag's associated page, wherein the schedule adding page includes the first tag, and the first tag's associated page is configured to present associated information of the first tag;

[0077] a modifying unit, configured to modify the first tag to a second tag in response to a tag editing operation triggered by the user in the schedule adding page;

[0078] An acquiring unit, configured to acquire schedule information input by the user in the schedule adding page;

[0079] A generating unit is used to generate a schedule having the second tag.

[0080] Optionally, the modification unit is used to:

[0081] In response to a tag editing operation triggered by the user in the schedule adding page, displaying at least one tag candidate item, wherein the at least one tag candidate item includes the second tag;

[0082] In response to a selection operation triggered by the user on the second tag in the at least one tag candidate item, the first tag is modified to a second tag.

[0083] Optionally, the modification unit is used to:

[0084] In response to a tag editing operation triggered by the user in the schedule adding page, characters input by the user are acquired, the second tag is acquired according to the characters input by the user, and the first tag is modified to the second tag.

[0085] Optionally, the device further comprises:

[0086] The second display unit is used to display the summary information of the schedule in the schedule page corresponding to the second tag. The schedule page corresponding to the second tag is used to display the summary information of the schedule with the second tag.

[0087] In a fifth aspect, an embodiment of the present application provides a device, the device comprising a processor and a memory;

[0088] The processor is used to execute instructions stored in the memory so that the device executes any one of the first aspects or the method described in the second aspect.

[0089] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising instructions, wherein the instructions instruct a device to execute any one of the methods described in the first aspect or the second aspect above.

[0090] In a seventh aspect, an embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute any one of the methods described in the first aspect or the second aspect.

[0091] Compared with the prior art, the embodiments of the present application have the following advantages:

[0092] An embodiment of the present application provides a schedule creation method. A user can trigger a schedule adding operation in the associated page of the first tag displayed on the client, and the client can display a schedule adding page in response to the schedule adding operation, and the schedule adding page includes the first tag. Among them, the associated page of the first tag is used to present the associated information of the first tag. After the schedule adding page is displayed, the user can enter the schedule information in the schedule adding page, and the client can obtain the schedule information and further generate a schedule with the first tag based on the schedule information. It can be seen that, using this solution, after the user triggers the schedule adding operation in the associated page of the first tag, the first tag will be automatically brought into the schedule adding page, and further, a schedule including the first tag can be generated. There is no need for the user to first create a schedule and then add a tag to the schedule, thereby reducing the cumbersomeness of creating a schedule with a tag.

[0093] The embodiment of the present application provides a schedule creation method. A user can trigger a schedule adding operation in the associated page of the first tag displayed by the client, and the client can respond to the schedule adding operation and display the schedule adding page, which includes the first tag. Among them, the associated page of the first tag is used to present the associated information of the first tag. After the schedule adding page is displayed, the user can trigger a tag editing operation in the schedule adding page to modify the first tag in the schedule adding page to the second tag. Then, the user can enter the schedule information in the schedule adding page, and the client can obtain the schedule information and further generate a schedule with the second tag based on the schedule information. It can be seen that, using this scheme, when the user wants to create a schedule with a second tag, even if the page displayed by the client is the associated page of the first tag, the user does not need to switch the page displayed by the client to the associated page of the second tag. The user can create a schedule with the second tag in the associated page of the first tag, thereby improving the operational flexibility of creating a schedule with a tag. BRIEF DESCRIPTION OF THE DRAWINGS

[0094] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0095] Figure 1 A schematic diagram of a schedule creation method provided in an embodiment of the present application;

[0096] Figure 2 A schematic diagram of a schedule adding page provided in an embodiment of the present application;

[0097] Figure 3 A flowchart of another schedule creation method provided in an embodiment of the present application;

[0098] Figure 4 A schematic diagram of the structure of a schedule creation device provided in an embodiment of the present application;

[0099] Figure 5 A schematic diagram of the structure of another schedule creation device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0100] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0101] After research, the inventor of the present application found that in some scenarios, it is necessary to create a schedule with a label. For example, for a certain project, a label can be added to the schedule related to the project. In one example, the project participants related to the schedule can be given permission to use the label, and the project participants related to the schedule can be given access rights to the schedule. In this way, the project participants related to the schedule can locate the schedule through the label, so as to arrange the work schedule reasonably.

[0102] However, the current method of creating a schedule with a label is relatively cumbersome for the user to operate. As an example, first, a schedule needs to be created, and then a corresponding label is added to the schedule.

[0103] In order to solve the above problems, the embodiments of the present application provide a schedule creation method and device.

[0104] Various non-limiting implementations of the present application are described in detail below in conjunction with the accompanying drawings.

[0105] Exemplary Methods

[0106] See also Figure 1 , which is a flow chart of a schedule creation method provided in an embodiment of the present application.

[0107] The method provided in the embodiment of the present application can be executed by a client or a server. In the embodiment of the present application, the target application can be installed on the client, and the server can be the server corresponding to the target application. The user mentioned in the embodiment of the present application refers to the user corresponding to the account that logs in to the target application on the client.

[0108] In the following description of the embodiments of the present application, the method is executed by a client as an example.

[0109] The “#” in the drawings of the embodiments of the present application is a tag identifier. Of course, the tag identifier is not limited to “#”, but can also be other symbols.

[0110] In the absence of conflict, the following Figure 1 The method shown and Figure 3The methods shown can be combined and referenced with each other.

[0111] All the drawings in the embodiments of this application, such as Figure 2 , which is only shown to facilitate understanding of the contents related to the embodiments of the present application and does not constitute a limitation on the embodiments of the present application. Figure 2 The page shown may also include other content, which is not specifically limited in the embodiment of the present application.

[0112] In this embodiment, Figure 1 The method shown may include, for example, the following steps: S101 - S102 .

[0113] S101: In response to a schedule adding operation triggered by a user in an associated page of a first tag, displaying a schedule adding page, wherein the schedule adding page includes the first tag, and the associated page of the first tag is used to present associated information of the first tag.

[0114] In an embodiment of the present application, the associated information of the first tag refers to information that has an associated relationship with the first tag. The information mentioned here includes, but is not limited to, one or more of tasks, schedules, messages, cloud documents, and groups. Among them, tasks, schedules, messages, cloud documents, and groups can each correspond to an information domain, specifically: tasks can correspond to task information domains, schedules can correspond to schedule information domains, messages can correspond to message information domains, cloud documents can correspond to cloud document information domains, and groups can correspond to group information domains. The information domain in an embodiment of the present application is used to provide a certain type of information. In some application scenarios, an information domain can correspond to a service provider.

[0115] In one implementation of the embodiment of the present application, the associated page of the first tag may be an overview page of the first tag, and the overview page of the first tag is a page that summarizes and displays the information of each information domain having the first tag. In one example, the overview page of the first tag may include information of each information domain having the first tag, for example, one or more of information in the task information domain, information in the schedule information domain, information in the message information domain, information in the cloud document information domain, and information in the group information domain. In some embodiments, to facilitate users to view the information included in the overview page, the information corresponding to each information domain is presented in different areas in the overview page. For example, in the overview page, the task information domain, the schedule information domain, the message information domain, the cloud document information domain, and the group information domain each correspond to a display area for displaying information corresponding to themselves. That is: the display area corresponding to the task information domain is used to display the information of the task with the first label; the display area corresponding to the schedule information domain is used to display the information of the schedule with the first label; the display area corresponding to the message information domain is used to display the information of the message with the first label; the display area corresponding to the cloud document information domain is used to display the information of the cloud document with the first label; the display area corresponding to the group information domain is used to display the information of the group with the first label.

[0116] In another implementation of the embodiment of the present application, the associated page of the first tag may be a page corresponding to the schedule information field of the first tag, and the page corresponding to the schedule information field of the first tag is used to display information of the schedule with the first tag. The page corresponding to the schedule information field may also be referred to as a "schedule page".

[0117] In one example, the associated page of the first tag displayed on the client of the user presents content that the user has the permission to view.

[0118] In one implementation of the embodiment of the present application, the associated page of the first tag may include a first control, and the function corresponding to the first control is a schedule adding function. The user may trigger the schedule adding operation through the first control. After the user triggers the schedule adding operation, the client may display the schedule adding page, and the first tag may be automatically brought into the schedule adding page.

[0119] In one example, when S101 is implemented, the client may first call a schedule application programming interface (API), and pass the first tag as a parameter to a schedule application through the schedule API, thereby obtaining the schedule adding page including the first tag. The schedule application is a software module for creating a schedule.

[0120] S102: Acquire schedule information input by the user in the schedule adding page, and generate a schedule with the first tag.

[0121] After the schedule adding page is displayed, the user can enter schedule information in the schedule adding page, for example, enter the schedule subject, the start time and end time of the schedule, and the corresponding meeting room and other detailed information.

[0122] After the user enters schedule information in the schedule adding page, the client can obtain the schedule information entered by the user, and further generate a schedule with the first tag based on the obtained schedule information. It can be understood that the generated schedule includes the schedule information obtained by the client.

[0123] From the above description, we can see that using Figure 1 In the schedule creation method shown, after the user triggers the schedule adding operation in the associated page of the first tag, the first tag is automatically brought into the schedule adding page, and further, a schedule including the first tag can be generated. The user does not need to create a schedule first and then add the first tag to the schedule, thereby reducing the tediousness of creating a schedule with a tag.

[0124] In one example, after creating a schedule with the first tag, summary information of the schedule can be presented in the schedule page of the first tag. The summary information of the schedule mentioned here can be, for example, the subject of the schedule, or keywords in the subject of the schedule, which is not limited here. The schedule page corresponding to the first tag is used to display summary information of the schedule with the second tag. In some embodiments, the schedule page corresponding to the first tag displayed on the client can display summary information of the schedule that the user has permission to view.

[0125] In one example, multiple tags can be added to a schedule. In this case, the user can also trigger a tag editing operation in the schedule adding page. For example, the schedule adding page includes a tag adding control, and the user can trigger the tag editing operation through the tag adding control. After the user triggers the tag editing operation, the client can obtain the second tag indicated by the tag editing operation. Accordingly, the schedule generated by the client can include a second tag in addition to the aforementioned first tag.

[0126] It is understandable that if the schedule also has a second tag, the schedule page of the second tag can present summary information of the schedule. The schedule page corresponding to the second tag is used to display summary information of the schedule with the second tag. In some embodiments, the schedule page corresponding to the second tag displayed on the client can display summary information of the schedule that the user has the right to view.

[0127] In the embodiment of the present application, "acquiring a second tag in response to a tag editing operation triggered by the user in the schedule adding page" may be implemented in a variety of ways. Two possible implementations are described below.

[0128] The first implementation method:

[0129] After the user triggers a tag editing operation in the schedule adding page, the client may display at least one tag candidate item in response to the tag editing operation. After displaying the at least one tag candidate item, the user may trigger a selection operation for one of the at least one tag candidate items. If the user triggers a selection operation for the second tag in the at least one tag candidate item, such as clicking on the second tag, the client may obtain the second tag.

[0130] It should be noted that, considering that tags may have usage permissions, only when a user has usage permissions for a tag can the user add the tag to the information. Therefore, in one example, the at least one tag candidate may be a candidate for which the user has usage permissions.

[0131] The second implementation method:

[0132] After the user triggers the tag editing operation in the schedule adding page, the client can display a character input area in response to the tag editing operation. Then, the user can enter characters in the character input area. The user can enter at least a portion of the characters included in the second tag in the character input area. Accordingly, after the client obtains the characters entered by the user, it can provide the user with corresponding tag candidates based on the characters entered by the user, and display the tag candidates so that the user can select the second tag based on the tag candidates. After the user selects the second tag, that is, the user triggers a selection operation for the second tag in the tag candidates, such as clicking on the second tag, the client can obtain the second tag.

[0133] In some embodiments, it is considered that the schedule generally has corresponding participants. The first tag itself may also have a certain identification meaning, for example, related to a certain project. Correspondingly, the first tag also has certain collaborators. The so-called collaborators of the first tag refer to users with the first tag authority. For example, it is a user with the first tag viewing authority. Among them, the user with the first tag viewing authority has the authority to view the associated information of the first tag. Since the schedule has the first tag, in some scenarios, it can be assumed that the collaborators of the first tag can also be participants of the schedule at the same time. Therefore, in one example, the aforementioned schedule adding page can also include participants of the schedule, and the participants of the schedule are users with the authority of the first tag. In other words, the collaborators of the first tag can be automatically brought into the schedule adding page. In this way, the user does not need to manually enter the participants of the schedule, thereby improving the efficiency of creating the schedule.

[0134] In some other embodiments, the participants of the schedule may also be specified by the user. In this case, the user may input the participants of the schedule in the schedule adding page.

[0135] It should be noted that the participants of the schedule input by the user may include collaborators of the first tag, or other users other than the collaborators of the first tag. In some application scenarios, if the participants of the schedule input by the user include other users other than the collaborators of the first tag, then after the schedule with the first tag is generated, the other users other than the collaborators of the first tag among the participants of the schedule may be converted into collaborators of the first tag. In other words, after the schedule with the first tag is generated, the client may grant the participants of the schedule the permission of the first tag in response to the generation of the schedule with the first tag. Specifically: the user who originally does not have the permission of the first tag among the participants of the schedule may be granted the permission of the first tag. The permission of the first tag mentioned here may be the permission to view the first tag. The so-called permission to view the first tag refers to the permission to view the associated information of the first tag, for example, the permission to indicate whether the client used by the user can display the first tag and at least a part of the information with the first tag in an associated manner. The associated information of the first tag mentioned here refers to the information with the first tag.

[0136] For example, the user inputs that the participants of the schedule include user A and user B, where user B is not a collaborator of the first label. After the schedule is generated, user B can be granted the viewing permission of the first label, so that user B becomes a collaborator of the first label. In this way, the user does not need to first modify user B to be a collaborator of the first label, and then set user B as a participant of the schedule. The user can directly set user B as a participant of the schedule, which is flexible in operation and simplifies user operation to improve user experience. Furthermore, in the scenario where the first label corresponds to a multi-person collaborative project, for user B who has the viewing permission of the schedule, even if the member does not currently have the viewing permission of the first label, for example, the user B is a new user who joins the project. In this way, user B can also be quickly set as a participant of the schedule, and user B can be automatically set as a collaborator of the first label, without the need to additionally set user B as a collaborator of the first label. The operation is flexible and the user experience is high.

[0137] Regarding the schedule adding page, now combined with Figure 2 Provide explanation. Figure 2 A schematic diagram of a schedule adding page provided in an embodiment of the present application.

[0138] like Figure 2 As shown, #A represents the first label, Add tags "Add controls to the tag. The participants of the tag, as described above, can be collaborators of the first tag or user input, for example, in Figure 2In the area indicating "participants", "***" is used to indicate that. For other contents in the tag details, such as the corresponding conference room, schedule reminder method, etc., you can Figure 2 In the area indicating "Schedule Details", "*****" is used to indicate it. After the user enters schedule information on the schedule adding page, he can click Figure 2 The "Save" control shown is used to generate the schedule including the first label.

[0139] It should be noted that, in the embodiment of the present application, the first tag is not a tag that can only be used locally in the client of the user, but a tag that can be shared within a certain range. Specifically, the sharing range of the first tag can be determined by the authority of the first tag.

[0140] In one example, the permission of the first tag may include usage permission. The so-called usage permission refers to the permission to add the first tag to the information unit. Specifically, users with the permission to use the first tag can add the first tag to the information unit on their corresponding clients. The permission to use the first tag can be set by the owner of the first tag, and the owner of the first tag can specify users with the permission to use the first tag.

[0141] In another example, the permission of the first tag includes viewing permission. The so-called viewing permission refers to the permission to view the associated information of the first tag. Specifically: the associated information of the first tag is displayed on the client of the user who has the viewing permission of the first tag. In other words, the user who has the viewing permission of the first tag can view the associated information of the first tag on his corresponding client. The viewing permission of the first tag can be set by the owner of the first tag, and the owner of the first tag can specify the user who has the viewing permission of the first tag.

[0142] In some embodiments, it is considered that the information unit itself also has viewing permissions. Then, for the first user who has viewing permissions for 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 viewing permissions for. In other words, the associated information of the first tag presented on the client of the first user does not include information that the first user does not have viewing permissions for. In this way, information security can be effectively protected to prevent the first user from viewing information that he does not have viewing permissions for and causing information leakage. In one example, for the first information unit that the first user has viewing permissions for, if the first information unit has a first tag, the first tag and the first information unit can be presented in association on the client of the first user. In this way, the first user can determine the specific content of the first information unit based on the first tag and the first information unit presented in association, and determine that the first information unit has the first tag.

[0143] The embodiment of the present application also provides a schedule creation method, which is described below in conjunction with the accompanying drawings.

[0144] See also Figure 3 , which is a flow chart of another schedule creation method provided in an embodiment of the present application.

[0145] and Figure 1 The schedule creation method shown is similar. Figure 3 The schedule creation method shown can also be executed by the client or the server. In the following description of the embodiment of the present application, the method is executed by the client as an example for explanation.

[0146] Figure 3 The schedule creation method shown may include, for example, the following S201 - S203 .

[0147] S201: In response to a schedule adding operation triggered by a user in an associated page of a first tag, displaying a schedule adding page, wherein the schedule adding page includes the first tag, and an associated page of the first tag is used to present associated information of the first tag.

[0148] Regarding S201, please refer to the above description of S101, and no repeated description is given here.

[0149] S202: In response to a tag editing operation triggered by the user in the schedule adding page, modify the first tag to a second tag.

[0150] In an embodiment of the present application, it is considered that when the page displayed on the client is an associated page of the first tag, the user may also have the need to create a schedule with a second tag. Therefore, in one example, the user can trigger a schedule adding operation in the associated page of the first tag, and then the client can display a schedule adding page, which includes the first tag. In addition, the first tag can be modified. Specifically: the user can modify the first tag to the second tag by triggering a tag editing operation.

[0151] There are multiple implementation methods for S202. Two possible implementation methods are described below.

[0152] The first implementation method:

[0153] After the user triggers a tag editing operation in the schedule adding page, the client may display at least one tag candidate item in response to the tag editing operation. After displaying the at least one tag candidate item, the user may trigger a selection operation for one of the at least one tag candidate items. If the user triggers a selection operation for the second tag in the at least one tag candidate item, such as clicking on the second tag, the client may modify the first tag to the second tag.

[0154] It should be noted that, considering that tags may have usage permissions, only when a user has usage permissions for a tag can the user add the tag to the information. Therefore, in one example, the at least one tag candidate may be a candidate for which the user has usage permissions.

[0155] The second implementation method:

[0156] After the user triggers the tag editing operation in the schedule adding page, the client can display a character input area in response to the tag editing operation. Then, the user can enter characters in the character input area. The user can enter at least a portion of the characters included in the second tag in the character input area. Accordingly, after the client obtains the characters entered by the user, it can provide the user with corresponding tag candidates based on the characters entered by the user, and display the tag candidates so that the user can select the second tag based on the tag candidates. After the user selects the second tag, that is, the user triggers a selection operation for the second tag in the tag candidates, such as clicking on the second tag, the client can modify the first tag to the second tag.

[0157] S203: Acquire the schedule information input by the user in the schedule adding page, and generate a schedule with the second tag.

[0158] After the schedule adding page is displayed, the user can not only trigger the tag editing operation, but also enter schedule information in the schedule adding page, for example, enter the schedule subject, the start time and end time of the schedule, and the corresponding meeting room and other detailed information.

[0159] After the user enters schedule information in the schedule adding page, the client can obtain the schedule information entered by the user, and further generate a schedule with the second tag based on the obtained schedule information. It can be understood that the generated schedule includes the schedule information obtained by the client.

[0160] In one example, after a schedule with the second label is created, summary information of the schedule may be presented on the schedule page of the second label.

[0161] From the above description, we can see that using Figure 3 In the schedule creation method shown, when a user wants to create a schedule with a second tag, even if the page displayed by the client is the associated page of the first tag, the user does not need to switch the page displayed by the client to the associated page of the second tag, but can directly create a schedule with the second tag in the associated page of the first tag, thereby improving the operational flexibility of creating schedules with tags.

[0162] Exemplary Devices

[0163] Based on the method provided in the above embodiment, the embodiment of the present application further provides a device, which is described below in conjunction with the accompanying drawings.

[0164] See also Figure 4 , which is a schematic diagram of the structure of a schedule creation device provided in an embodiment of the present application. The device 400 may specifically include: a display unit 401, a first acquisition unit 402 and a generation unit 403.

[0165] The display unit 401 is used to display a schedule adding page in response to a schedule adding operation triggered by a user in a first tag's associated page, wherein the schedule adding page includes the first tag, and the first tag's associated page is used to present associated information of the first tag;

[0166] A first acquisition unit 402 is used to acquire the schedule information input by the user in the schedule adding page;

[0167] The generating unit 403 is configured to generate a schedule having the first tag.

[0168] Optionally, the device further comprises:

[0169] A second acquisition unit, configured to, in response to a tag editing operation triggered by the user in the schedule adding page, acquire a second tag indicated by the tag editing operation;

[0170] The generating unit 403 is used for:

[0171] A schedule including the first label and the second label is generated.

[0172] Optionally, the user triggers the tag editing operation through a tag adding control.

[0173] Optionally, the second acquiring unit is used to:

[0174] In response to a tag editing operation triggered by the user in the schedule adding page, displaying at least one tag candidate item, wherein the at least one tag candidate item includes the second tag;

[0175] In response to a selection operation triggered by the user on the second tag in the at least one tag candidate item, the second tag is acquired.

[0176] Optionally, the second acquiring unit is used to:

[0177] In response to a tag editing operation triggered by the user in the schedule adding page, characters input by the user are acquired, and the second tag is acquired according to the characters input by the user.

[0178] Optionally, the device further comprises:

[0179] The first display unit is used to display summary information of the schedule in the schedule page corresponding to the second tag, and the schedule page corresponding to the second tag is used to display summary information of the schedule with the second tag.

[0180] Optionally, the schedule adding page also includes: participants of the schedule, and the participants of the schedule are users who have the viewing permission of the first tag.

[0181] Optionally, the first acquiring unit 402 is configured to:

[0182] The participants of the schedule input by the user in the schedule adding page are obtained.

[0183] Optionally, the device further comprises:

[0184] The permission setting unit is used to: if the participants of the schedule entered by the user in the schedule adding page do not have the permission of the first tag before the schedule with the first tag is generated, then in response to the generation of the schedule with the first tag, grant the participants of the schedule the permission of the first tag.

[0185] Optionally, the first tag is shared among users who have permission to use the first tag.

[0186] Optionally, the permission of the first tag includes usage permission, and a user who has the usage permission of the first tag has the permission to add the first tag to the information unit on the corresponding client.

[0187] Optionally, the permission of the first tag includes viewing permission, and the associated information of the first tag is displayed on the client of the user who has the viewing permission of the first tag.

[0188] Optionally, the device further comprises:

[0189] The second display unit is used to present the first tag and a first information unit in association on a client of the first user in response to the first user having the viewing permission of the first tag, wherein the first information unit is an information unit that the first user has the viewing permission.

[0190] Optionally, the associated page of the first tag includes:

[0191] The overview page of the first tab, or the page corresponding to the schedule information field of the first tab; wherein:

[0192] The overview page is a page that displays information in summary form in each information field having the first tag; or, the page corresponding to the schedule information field is used to display information of the schedule having the first tag.

[0193] Optionally, the information corresponding to each information domain is presented in different regions in the overview page.

[0194] Since the device 400 is provided with the above method embodiment Figure 1 The corresponding method and the corresponding device, and the specific implementation of each unit of the device 400 are the same as those in the above method embodiment. Figure 1 The method shown is of the same concept, therefore, for the specific implementation of each unit of the device 400, reference may be made to the relevant description part of the above method embodiment, which will not be repeated here.

[0195] See also Figure 5 , which is a schematic diagram of the structure of another schedule creation device provided in an embodiment of the present application. The device 500 may specifically include: a first display unit 501, a modification unit 502, an acquisition unit 503 and a generation unit 504.

[0196] A first display unit 501 is used to display a schedule adding page in response to a schedule adding operation triggered by a user in a first tag's associated page, wherein the schedule adding page includes the first tag, and the first tag's associated page is used to present associated information of the first tag;

[0197] A modifying unit 502, configured to modify the first tag to a second tag in response to a tag editing operation triggered by the user in the schedule adding page;

[0198] The acquisition unit 503 is used to acquire the schedule information input by the user in the schedule adding page;

[0199] The generating unit 504 is configured to generate a schedule having the second tag.

[0200] Optionally, the modifying unit 502 is used to:

[0201] In response to a tag editing operation triggered by the user in the schedule adding page, displaying at least one tag candidate item, wherein the at least one tag candidate item includes the second tag;

[0202] In response to a selection operation triggered by the user on the second tag in the at least one tag candidate item, the first tag is modified to a second tag.

[0203] Optionally, the modifying unit 502 is used to:

[0204] In response to a tag editing operation triggered by the user in the schedule adding page, characters input by the user are acquired, the second tag is acquired according to the characters input by the user, and the first tag is modified to the second tag.

[0205] Optionally, the device further comprises:

[0206] The second display unit is used to display the summary information of the schedule in the schedule page corresponding to the second tag. The schedule page corresponding to the second tag is used to display the summary information of the schedule with the second tag.

[0207] Since the device 500 is provided with the above method embodiment Figure 3 The corresponding method and the corresponding device, and the specific implementation of each unit of the device 500 are the same as those in the above method embodiment. Figure 3 The method shown is of the same concept, therefore, for the specific implementation of each unit of the device 500, reference may be made to the relevant description part of the above method embodiment, which will not be repeated here.

[0208] An embodiment of the present application also provides a device, which includes a processor and a memory; the processor is used to execute instructions stored in the memory, so that the device executes the method provided by the above method embodiment.

[0209] An embodiment of the present application also provides a computer-readable storage medium, including instructions, wherein the instructions instruct a device to execute the method provided in the above method embodiment.

[0210] The application embodiment also provides a computer program product, which, when executed on a computer, enables the computer to execute the method provided in the above method embodiment.

[0211] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0212] It should be understood that the present application is not limited to the precise structures 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 present application is limited only by the appended claims.

[0213] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A schedule creation method, characterized in that: The method comprises: In response to a schedule adding operation triggered by a user in an associated page of a first tag, displaying a schedule adding page, wherein the schedule adding page includes the first tag, and an associated page of the first tag is used to present associated information of the first tag; Acquire the schedule information entered by the user in the schedule adding page; In response to a tag editing operation triggered by the user in the schedule adding page, acquiring a second tag indicated by the tag editing operation; A schedule including the first label and the second label is generated.

2. The method according to claim 1, characterized in that The user triggers the tag editing operation through a tag adding control.

3. The method according to claim 1 or 2, characterized in that: In response to a tag editing operation triggered by the user in the schedule adding page, obtaining a second tag includes: In response to a tag editing operation triggered by the user in the schedule adding page, displaying at least one tag candidate item, wherein the at least one tag candidate item includes the second tag; In response to a selection operation triggered by the user on the second tag in the at least one tag candidate item, the second tag is acquired.

4. The method according to claim 1 or 2, characterized in that: In response to a tag editing operation triggered by the user in the schedule adding page, obtaining a second tag includes: In response to a tag editing operation triggered by the user in the schedule adding page, characters input by the user are acquired, and the second tag is acquired according to the characters input by the user.

5. The method according to claim 1, characterized in that: The method further comprises: In the schedule page corresponding to the second tag, summary information of the schedule is displayed. The schedule page corresponding to the second tag is used to display summary information of the schedule with the second tag.

6. The method according to claim 1, characterized in that The schedule adding page also includes: participants of the schedule, and the participants of the schedule are users who have the viewing authority of the first tag.

7. The method according to claim 1, characterized in that The acquiring of the schedule information input by the user in the schedule adding page includes: The participants of the schedule input by the user in the schedule adding page are obtained.

8. The method according to claim 7, characterized in that The method further comprises: If the participants of the schedule entered by the user in the schedule adding page do not have the permission of the first tag before the schedule with the first tag is generated, the participants of the schedule are granted the permission of the first tag in response to the generation of the schedule with the first tag.

9. The method according to claim 1, characterized in that: The first tag is shared among users who have permission for the first tag.

10. The method according to claim 9, characterized in that The authority of the first tag includes usage authority. A user who has the usage authority of the first tag has the authority to add the first tag to the information unit on the corresponding client.

11. The method according to claim 9, characterized in that The permission of the first tag includes viewing permission, and the associated information of the first tag is displayed on the client of the user who has the viewing permission of the first tag.

12. The method according to claim 11, characterized in that The method further comprises: In response to the first user having the permission to view the first tag, the first tag and a first information unit are associated and presented on the client of the first user, wherein the first information unit is an information unit that the first user has the permission to view.

13. The method according to claim 1, characterized in that The associated page of the first tag includes: The overview page of the first tab, or the page corresponding to the schedule information field of the first tab; wherein: The overview page is a page that displays information in summary form in each information field having the first tag; or, the page corresponding to the schedule information field is used to display information of the schedule having the first tag.

14. The method according to claim 13, characterized in that The information corresponding to each information domain is presented in different regions in the overview page.

15. A schedule creation method, characterized in that: The method comprises: In response to a schedule adding operation triggered by a user in an associated page of a first tag, displaying a schedule adding page, wherein the schedule adding page includes the first tag, and an associated page of the first tag is used to present associated information of the first tag; In response to a tag editing operation triggered by the user in the schedule adding page, modifying the first tag to a second tag; The schedule information input by the user in the schedule adding page is acquired, and a schedule having the second tag is generated.

16. The method according to claim 15, characterized in that In response to a tag editing operation triggered by the user in the schedule adding page, modifying the first tag to a second tag includes: In response to a tag editing operation triggered by the user in the schedule adding page, displaying at least one tag candidate item, wherein the at least one tag candidate item includes the second tag; In response to a selection operation triggered by the user on the second tag in the at least one tag candidate item, the first tag is modified to a second tag.

17. The method according to claim 16, characterized in that In response to a tag editing operation triggered by the user in the schedule adding page, modifying the first tag to a second tag includes: In response to a tag editing operation triggered by the user in the schedule adding page, characters input by the user are acquired, the second tag is acquired according to the characters input by the user, and the first tag is modified to the second tag.

18. The method according to any one of claims 15 to 17, characterized in that: The method further comprises: In the schedule page corresponding to the second tag, summary information of the schedule is displayed. The schedule page corresponding to the second tag is used to display summary information of the schedule with the second tag.

19. A schedule creation device, characterized in that: The device comprises: A display unit, configured to display a schedule adding page in response to a schedule adding operation triggered by a user in a page associated with a first tag, wherein the schedule adding page includes the first tag, and the page associated with the first tag is configured to present associated information of the first tag; A first acquisition unit, configured to acquire schedule information input by the user in the schedule adding page; A second acquisition unit, configured to, in response to a tag editing operation triggered by the user in the schedule adding page, acquire a second tag indicated by the tag editing operation; A generating unit is used to generate a schedule having the first label and the second label.

20. A schedule creation device, characterized in that: The device comprises: A first display unit, configured to display a schedule adding page in response to a schedule adding operation triggered by a user in a page associated with a first tag, wherein the schedule adding page includes the first tag, and the page associated with the first tag is configured to present associated information of the first tag; a modifying unit, configured to modify the first tag to a second tag in response to a tag editing operation triggered by the user in the schedule adding page; An acquiring unit, configured to acquire schedule information input by the user in the schedule adding page; A generating unit is used to generate a schedule having the second tag.

21. A device, characterized in that The device comprises a processor and a memory; The processor is configured to execute instructions stored in the memory, so that the device performs the method according to any one of claims 1 to 18.

22. A computer-readable storage medium, characterized in that: The method comprises instructions for instructing a device to execute the method according to any one of claims 1 to 18.

23. A computer program product, characterized in that When the computer program product is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 18.

Images