CN115525370A

CN115525370A - View management method and device, electronic equipment and storage medium

Info

Publication number: CN115525370A
Application number: CN202210541735.XA
Authority: CN
Inventors: 林诗鸿; 刘大畅; 唐伟豪
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2022-05-17
Filing date: 2022-05-17
Publication date: 2022-12-27
Also published as: WO2023222043A1

Abstract

The embodiment of the disclosure provides a view management method and device, electronic equipment and a storage medium. When the trigger view processing control is detected, displaying a view management list; the view management list comprises view associated information of at least one created view which is managed currently; taking the created view corresponding to the view related information triggered in the view management list as a view to be managed, and performing management operation on the view to be managed based on the operation authority information corresponding to the view to be managed; and updating the view to be managed based on the view corresponding to the management operation. The technical scheme provided by the embodiment of the disclosure can efficiently and conveniently manage the view.

Description

View management method and device, electronic equipment and storage medium

Technical Field

The present disclosure relates to image processing technologies, and in particular, to a method and an apparatus for view management, an electronic device, and a storage medium.

Background

At present, displaying project requirement information in a view mode becomes a very common data management mode at present. In the prior art, the views for displaying the project requirement information are generated and managed individually, and the view information to be viewed needs to be manually input when the view needs to be viewed each time, so that the display and management operations of the view can be completed. However, manual input is inefficient, time consuming and labor intensive; the single management mode has poor management convenience.

Disclosure of Invention

The disclosure provides a view management method, a view management device, an electronic device and a storage medium, so as to realize efficient and convenient view management.

In a first aspect, an embodiment of the present disclosure provides a view management method, including:

when the trigger view processing control is detected, displaying a view management list; the view management list comprises view associated information of at least one created view which is managed currently;

taking the created view corresponding to the view related information triggered in the view management list as a view to be managed, and performing management operation on the view to be managed based on the operation authority information corresponding to the view to be managed;

and updating the view to be managed based on the view corresponding to the management operation.

In a second aspect, an embodiment of the present disclosure further provides a view management apparatus, where the apparatus includes:

the view management list display module is used for displaying a view management list when the trigger view processing control is detected; wherein the view management list comprises view associated information of at least one created view which is currently managed;

a view to be managed operation module, configured to use the created view corresponding to the view association information triggered in the view management list as a view to be managed, and perform a management operation on the view to be managed based on operation permission information corresponding to the view to be managed;

and the view to be managed updating module is used for updating the view to be managed based on the view corresponding to the management operation completed.

In a third aspect, an embodiment of the present disclosure further provides an electronic device, where the electronic device includes:

one or more processors;

a storage device to store one or more programs,

when executed by the one or more processors, cause the one or more processors to implement a view management method as in any of the embodiments of the present disclosure.

In a fourth aspect, the disclosed embodiments also provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the view management method according to any one of the disclosed embodiments.

According to the technical scheme of the embodiment of the disclosure, when the triggering view processing control is detected, a view management list is displayed, and the view management list comprises the view associated information of at least one created view which is managed currently, so that the created view is managed uniformly; and the created view corresponding to the view association information triggered in the view management list is used as the view to be managed, the view to be managed is managed through the operation authority information corresponding to the view to be managed, the safety of the operation on the view to be managed is improved, and the view to be managed is updated based on the view corresponding to the management operation completion. The embodiment of the disclosure solves the problems of labor and time waste in the prior art, and can efficiently and conveniently manage the view.

Drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and components are not necessarily drawn to scale.

Fig. 1 is a schematic flowchart of a view management method according to an embodiment of the disclosure;

FIG. 2 is a schematic diagram of a display interface provided by an embodiment of the present disclosure;

FIG. 3 is a schematic diagram illustrating operations of a sharing operation according to an embodiment of the present disclosure;

FIG. 4 is an operational schematic diagram of a batch operation provided by an embodiment of the present disclosure;

FIG. 5 is a schematic flow chart diagram illustrating another method for view management according to an embodiment of the present disclosure;

FIG. 6 is an operational diagram of a sort operation provided by an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a view management apparatus according to an embodiment of the disclosure;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "including" and variations thereof as used herein is intended to be open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.

It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.

The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.

Before the technical solution is introduced, an application scenario may be exemplarily described. Based on the technical scheme, application software or a display page, such as an H5 page, can be developed so as to realize the function of uniformly managing the view by the application software or the display page. The technical scheme can also be integrated in a project management platform or system and is used for managing project views generated by project data in the project platform or system. For example, a platform user wants to view and edit requirement data and planning and scheduling information of related projects, and can quickly and efficiently operate the view based on the scheme of the embodiment, so that the user management is facilitated.

Fig. 1 is a flowchart illustrating a view management method provided by an embodiment of the present disclosure, where the embodiment of the present disclosure is applicable to a situation where a built view is managed in a unified manner, and the method may be executed by a view management apparatus, where the apparatus may be implemented in a form of software and/or hardware, and optionally, implemented by an electronic device, where the electronic device may be a mobile terminal, a PC end, a server, or the like.

As shown in fig. 1, the view management method includes:

and S110, when the trigger view processing control is detected, displaying a view management list.

The view management list comprises view associated information of at least one created view which is managed currently, the created view can contain at least one item of information of project requirement information, project attribute information and project plan information, and the view associated information comprises information of contents such as view names, view identifiers and view descriptions of the created view.

In this embodiment, the view processing control is a control that starts a function of displaying the view management list when being triggered, for example, the view processing control may be a key including a "view processing control" character, and the key may be rectangular, circular, star-shaped, or the like; the view processing control can also be an icon containing animation information of the view processing action, and the icon which vividly shows the view processing control is displayed on the display interface of the project management platform or system so as to start the function based on the triggering operation.

In particular implementations, the triggering operation for the view processing control may take a variety of forms. Illustratively, the triggering operation of the view processing control can be realized in at least one of a voice control mode, an external device control mode, a touch screen control mode and a gesture control mode. For example, the external device may include a mouse, and when the view processing control is displayed in the form of a rectangular button, it may be determined that the view processing control is triggered when a click operation of the mouse on the rectangular control is detected; or, when the recognized voice instruction is received, the view processing control can be triggered; or detecting that the touchable screen is clicked and the clicking position is on the key position displayed by the view processing control, and determining that the view processing control is triggered.

In this embodiment, the view processing control includes at least one processing type control, such as a "all-required view processing control", "uncompleted required view processing control", or "completed required view processing control", and a view management list of a corresponding type may be displayed according to the type of the triggered view processing control detected; if the "incomplete requirement view processing control" is triggered, a list of incomplete requirement views may be correspondingly presented, where the list includes only constructed views of each incomplete requirement.

In specific implementation, the display mode of the view management list may be displaying at a default position of the current display interface or displaying according to a preset designated position, for example, the default position may include positions of the left side, the right side, the top, the bottom, and the like of the current display interface, so as to avoid blocking other display information in the display interface; in addition, the project management user can input the position information of the designated position in advance through the external output device so as to display the view management list according to the designated position, for example, the position information can be the coordinate data of the display position, or the user can perform selection operation on the current display interface through a mouse and other devices and use the detected selected area information as the position information. Further, the display form of the view management list may include a scrolling cycle display, a folding hidden display, a full expansion display, etc., and those skilled in the art may determine the display form of the view management list according to the actual application requirements.

In this embodiment, in order to visually and clearly display the view management list, a specific display mode for displaying the view management list includes: popping up a window including a view management list; and expanding and displaying the view management list which is displayed in a folded mode in the display interface.

Specifically, a window containing a view management list displayed in a folded manner can be displayed in the display interface, and when the view processing control is detected to be triggered, the window can be directly popped up; in order to completely and specifically show each piece of information in the view management list, the view management list of the folded display can be unfolded and displayed. Further, a folding control is deployed in the window, and is used for folding or unfolding the view management list when being triggered. The folding control can be represented by a triangle, an arrow, a circle or a rectangular box. The method can be triggered by clicking operation, and the view management list is updated to a display state opposite to the current state based on the triggering operation; and if the information is displayed in the unfolding state at present, folding and displaying the information in the view management list after the folding control is triggered.

Taking fig. 2 as an example for detailed description, the view management list in fig. 2 is displayed on the left navigation bar of the display interface and is controlled by a folding control "

"switching control between the collapsed state and the expanded state is performed for each view in the view management list. Illustratively, when a view management list is first displayed, expansion may be employedDisplaying the state, namely displaying all the views contained in the view management list in a complete way; before displaying, it may be determined whether the number of views included in the view management list is greater than a preset number of views, and if so, it is described that the number of views included in the view management list is large and all views cannot be displayed simultaneously. And if the number of the views is less than or equal to the preset number of the views, the views can be directly unfolded and displayed. It should be noted that the number of the preset views may be determined according to display parameters such as a display font size and a display interval set on the display interface.

As shown in fig. 2, the display interface may further include a search control, for example, if a need, a defect, or a work item instance in the current view needs to be searched, the search key may be clicked to input a related keyword, the searched keyword is highlighted, and the need, defect, or work item instance including the keyword is displayed.

In this embodiment, the view association information includes at least one indicator item, where the at least one indicator item includes at least one of view name information, creator identifier, creation time, browsing right, and collaborator; the created view includes at least one of a system view, a fixed view, and a conditional view.

The creator identifier can be the code number of a user creating the view, the collaborators comprise participants involved in the created view, and the browsing permission is the permission for viewing the content in the corresponding created view; illustratively, the browsing right includes a full browsing right and a partial browsing right, for example, when the user has the full browsing right, the user can browse all contents in the corresponding view, and when the user has only the partial browsing right, only the browseable partial contents in the corresponding view are displayed, that is, only partial contents in which the user participates are involved, so as to improve confidentiality and security of the view contents.

In the present embodiment, the created views are different in configuration and may be divided into at least one of a system view, a fixed view, and a conditional view. The system view is a template view created by an administrator; opening operation authority or browsing authority for the administrator. After a view processing control used for displaying the system view is triggered, view association information of each template view included in the system view can be displayed on a display interface; the view related information of each template view can be arranged in a navigation bar on the left side of the display interface, and the arrangement sequence of the displayed view related information of each template view can be adjusted, the view related information can be changed and the like based on the operation of an administrator.

The created view can also comprise a view which is created after the view is fixed and at least one configuration item is selected from the requirement list of the item fixation; the configuration items comprise links of other views, data links and at least one of various requirement items in project association data; through the linkage of the views, the fixed view can be directly associated with other views, so that the fixed view can be quickly switched to other views; and acquiring data corresponding to the data link in the fixed view through the data link. For example, each configuration item can be displayed by adopting a fixed view in a requirement review or version iteration requirement scene.

In a specific implementation, the displayed content in the fixed view can be updated based on the configuration item selected from the requirement list of the item fixation, for example, when it is detected that the selected configuration item in the requirement list is not the same as the configuration item displayed in the current fixed view, the different configuration item is correspondingly added or deleted in the current fixed view, and the current fixed view is updated based on the addition or deletion result.

The created view may further include a conditional view, which is a view generated after determining view participation data based on a preset filtering condition. In a specific implementation, the filtering condition may be input in advance, for example, an input box may be directly displayed in the display interface, so that the user may input the filtering condition; the set screening conditions can be imported into a project management platform or system in a mode of importing screening condition texts; or, when the screening condition input control is detected to be triggered, popping up an editing interface to facilitate the user to input the screening condition; further, when a control associated with the filtering condition input operation is triggered, a filtering condition edit page is popped up to perform the filtering condition edit. Further, based on a preset screening condition, screening data satisfying the screening condition may be determined in the project management database as view participation data, and the view participation data may be used as constituent content to constitute a conditional view.

Further, the screening relationship of the screening condition includes types of belonging, including, equal to, empty, and in the interval. Wherein, the type of the data belongs to the single-selection scene, such as A belongs to A, B, but C does not belong to A, B; in the multiple choice scenario, for example, A, D belongs to A, B, C, D, but D, E does not belong to A, B, C. The inclusion type is in a multi-scene application, such as A, B, C includes A, B, but A, C does not include A, B.

As shown in fig. 2, a display frame of a view type may be set in a top navigation bar of a display interface, and the display frame may be a display frame capable of inputting, that is, any one of a system view, a fixed view and a conditional view is input in the display frame in a direct input manner; or, a hidden selection control is arranged in an adjacent area of the display frame, when the hidden selection control is triggered, options corresponding to the system view, the fixed view and the conditional view are correspondingly displayed, the currently selected view type is determined based on the selection operation, the selected view type is displayed in the display frame, and a view management list corresponding to the type and corresponding view associated information are correspondingly displayed.

Further, default views may also be preset for presentation when the system view, fixed view, and conditional view are not set. For example, when the view management method provided by this embodiment is applied to a project management system, the default view may include at least one of all requirements, ongoing requirements, completed requirements, and a terminated requirement pool. All the requirements of the current control can be displayed by clicking all the requirements, and the termination requirement is not contained; clicking the on-going requirement, and displaying the on-going requirement; the completed demand can show that the demand state is the finished demand; and terminating the demand pool, and entering the termination demand pool by default after the demand is terminated. In addition, the default view may also show a defect view, such as showing all defects, pending defects, user reported defects, and user committed defects.

And S120, taking the created view corresponding to the view related information triggered in the view management list as a view to be managed, and performing management operation on the view to be managed based on the operation authority information corresponding to the view to be managed.

The operation authority information comprises at least one operation authority of sequencing, sharing, collecting, deleting, modifying and exporting of the views to be managed, and different users have different operation authorities for different views to be managed.

In a specific implementation, when it is detected that each view association control corresponding to the view management list is triggered, which indicates that management operation needs to be performed on view association information corresponding to the view association control at present, the created view corresponding to the triggered view association information may be determined as a view to be managed. For example, the view association control may be a textbox button on which the view association information is displayed, and when it is detected that the textbox button is clicked, it is determined that the corresponding view association control is triggered; the view association control can also be triggered by means of a voice instruction, and when the voice instruction of 'starting the A-view association information' is detected, the corresponding A-view association information can be determined to be triggered.

In this embodiment, before performing a management operation on a view to be managed, operation permission information corresponding to the view to be managed may be determined, and a specific implementation manner may be: determining user login information of a current login system, acquiring user operation authority information corresponding to the user login information, determining operation authority information corresponding to the view to be managed based on the corresponding relation between the pre-stored user operation authority information and each view, and managing the view to be managed according to the operation authority information. The user login information comprises at least one of an authorized login address, a login user code number or a user identification of the login user.

Specifically, when user operation authority information corresponding to user login information is acquired, the operation authority information corresponding to the user can be determined through pre-stored authority ranges of the users; the operation authority information corresponding to the user can also be determined by determining the user type and/or the user operation level corresponding to the user login information; exemplarily, when the user login information reflects that the currently logged-in user is an administrator, the administrator can be given the maximum operation authority, and any operation can be performed on any view; when the user login information reflects that the currently logged-in user is a project participant, the operation authority of project participation system can be given as the authority of browsing the participated project, so that the information safety is improved; the operation levels can be preset for various login users, different operation levels have different operation authorities, the higher the operation level is, the higher the operation authority of the user is, and the user operation authority information corresponding to the user login information is determined according to the user operation level corresponding to the user login information.

In specific implementation, when a view to be managed is managed, whether the triggered current management operation is in the range of the determined operation authority information needs to be detected; if yes, operating the view to be managed according to the triggered current management operation; if not, prompting information of 'no operation authority, operation after the authority can be opened' is prompted so as to prompt the user to open the corresponding authority; and if the same operation without the operation authority is detected to be triggered by the same user for a preset number of times, generating alarm information and sending the alarm information to the management terminal to prompt that the current operation has risks.

In this embodiment, the management operation on the view to be managed includes at least one of a view sharing operation, a view collecting operation, and a batch operation. Optionally, when the management operation is a view sharing operation, based on the operation permission information corresponding to the view to be managed, the management operation on the view to be managed is specifically implemented in the following manner: when the sharing operation of the view to be managed is detected, and the operation authority information comprises the sharing authority, the view link of the view to be managed is shared to at least one user to be shared, so that the view to be managed is obtained based on the view link.

The view link can be a storage path of the view to be managed in the current project management system.

In specific implementation, the display interface includes a sharing control, when the sharing control is triggered, the management operation is a sharing operation, in order to ensure operation safety, it is required to verify whether operation authority information corresponding to a view to be managed includes sharing authority, if yes, it is indicated that the view to be managed can be shared, after the sharing control is triggered, a view link of the view to be managed is provided, and a user is prompted to input information of the user to be shared, such as information of a code number, a login name and the like of the user to be shared, so as to obtain information of the user to be shared, and the view link is shared to the user to be shared based on the information of the user to be shared.

For example, the user to be shared may be one or more users designated by the current login user, or all users belonging to a certain project group, and when all users in the project group need to be shared, information such as a project group number and a project group name is input; when the user needs to share the user or users, the information such as the code number, the login name and the like of the user to be shared can be directly input.

The sharing operation is generally applicable to sharing the review forecasting mode through a shared project view chain when the project is reviewed. In order to show the implementation situation of the sharing view more clearly, referring to fig. 3, a sharing control is arranged in a top navigation bar of a display interface, when it is detected that a click operation occurs at a position where the sharing control of the display interface belongs, it can be confirmed that the sharing control is triggered, a sharing information input window can be popped up, as shown in fig. 3, an address of the sharing link, a copy control and an information input control of a user to be shared are displayed in the sharing information input window, by triggering the copy control, a storage address link of the view to be managed can be acquired, an identifier of the user to be shared is input at an input position corresponding to the user to be shared, and a link a is sent to the user to be shared corresponding to the input identifier.

Optionally, when the management operation is a favorite view operation, based on the operation permission information corresponding to the view to be managed, the management operation on the view to be managed is specifically implemented in the following manner: and if the operation authority information comprises the collection authority, collecting the view to be managed or canceling the collection of the view to be managed.

The collection authority comprises a collection view authority and a collection view canceling authority. Specifically, if the operation authority information includes the collection authority of the view to be managed, when the management operation is the operation of collecting the view to be managed, the view to be managed can be added to the collected list, and the collected view is subjected to collection marking in the view management list, wherein the collection marking can be at least one marking mode of highlighting, thickening, underlining and special symbol marking on the information of the collected view to be managed; when the management operation is a cancel favorite view to be managed operation, the view to be managed can be removed from the collected list, and the favorite mark of the view to be managed can be canceled in the view management list. Further, when the management operation is collection or collection of the view to be managed is cancelled and the collection authority information does not include the collection authority, prompt information can be generated, and a user is prompted to have no collection authority temporarily through modes such as voice broadcasting and text display, so that the operation cannot be carried out.

For example, to describe the specific manner of the collection operation in detail, as shown in fig. 3, a collection control is disposed in a top navigation bar of the display interface, and the collection operation or the cancel of the collection operation on the view currently displayed in the view display area can be implemented by clicking the collection control.

When the view to be managed is a view which is not collected and collection operation is required, clicking a collection control in a display interface; for example, the view displayed in the view display area is the content of the view B, and the view B is taken as the view to be managed which needs to be collected, the collection control is clicked, the clicked collection control and the collection control before being clicked are displayed in a distinguishing manner, if the collection control before being clicked is displayed without shadow, the shadow is added to the collection control after being clicked; and the collection control before clicking is surrounded and displayed by a dotted line frame, and the collection control after clicking is surrounded and displayed by a solid line frame. When the view "view B" to be managed is collected, the associated information of the view B may be marked in the view management list containing the view B, for example, the mark "o" may be color-filled to be "●" to display that the view is collected.

When the view to be managed is a collected view and the management operation is a collection canceling operation, the collection canceling operation of the view can be realized by the following modes: 1. the collection control can be clicked again to enable the collection control to be in an uncollected state, and then the collection of the view in the view display area is cancelled; 2. the identification control before the view to be managed can be clicked in the view management list where the view to be managed is located to cancel the collection operation and enable the identification control to be in an uncollected state; as in fig. 3, the identification control before "view a" is "o", i.e., in an unpopulated state, and the identification control before "view B" is "●", in a populated state; 3. and clicking the identification control in front of the collected view to be managed in the collected view list to cancel the collection.

Optionally, when the management operation is a batch operation, based on the operation permission information corresponding to the view to be managed, the management operation on the view to be managed is specifically implemented in the following manner: and if the operation authority information comprises view batch operation, performing batch management operation on at least one view to be managed.

The view batch operation comprises at least one of batch upgrading, batch deleting, batch modifying, batch exporting and dragging. The view to be managed comprises at least one data item, and the batch operation can be an operation on the at least one view to be managed and also an operation on the at least one data item in the view to be managed; the batch upgrading can be used for upgrading the selected at least one view to be managed into a preset view template; the batch deletion can be used for deleting the selected at least one view to be managed from the view management list or deleting data items contained in the view to be managed in batches; the batch modification can be used for modifying at least one item of association information, view parameters, view content and contained data items of the selected at least one view to be managed; the batch export can be used for exporting the selected at least one view to be managed or the data items in the view to be managed to a preset address; the dragging is used for sorting the selected at least one view to be managed in the view management list in a replacement mode, and can also be used for replacing the arrangement sequence of any requirements in the view to be managed.

In this embodiment, the display interface is respectively provided with an upgrade control, a delete control, a modification control, and a export control, and when the corresponding control is triggered, at least one selected view to be managed is upgraded, deleted, modified, or exported. For batch upgrading operation, in order to prevent upgrading misoperation, when the upgrading control is detected to be triggered, popup prompt can be performed to remind the user of operating content again, and corresponding operation is performed on the selected view to be managed until confirmation operation sent by the user through the input device is obtained.

And for batch deletion operation, when the view fails, the view is wrongly established, and the requirement establishment in the view to be managed is wrong, the deletion operation can be carried out, the operation path can be at least one view to be managed or the data item in at least one view to be managed is selected, and then the deletion control is clicked to delete the selected view to be managed or the data item.

Aiming at batch modification operation, the method is mainly applied to scenes of carrying out batch value modification or replacement on fields of the same type, and if the priority of at least one item of data item in the view to be managed is increased in batches, the data item needing to be increased in priority can be selected, and the corresponding priority value is modified in batches.

For batch export operation, the method is mainly applied to a scene of exporting at least one data item in a view to be managed or a view to be managed to a local storage. The derived views or data items may be stored in tabular form, image form, or text form.

The specific implementation manner may be that the view to be managed or the data items are selected, the view to be managed or the data items are moved from the initial position to the target position, and the view management category or the ordering of each data item in the view to be managed is updated based on the moved ordering. For drag operations, only one view or data item may be dragged at a time; when a plurality of views or data items need to be dragged, in order to improve convenience, whether the target positions of the views or data items needing to be dragged are consistent or not can be determined, if the positions are the same, the views or data items needing to be dragged can be selected, and meanwhile, the selected content is dragged to the target position; and if not, selecting the views or the data items with the same target position in batch, and dragging to the target position.

Exemplarily, as shown in fig. 4, an upgrade control, a delete control, an export control, and a modification control are arranged on the top navigation bar of the display interface; each view in the view management list corresponds to a selected box, the selected box can be clicked to realize the selection operation of the view, and all the selected boxes can be selected or some of the selected boxes can be selected; and marking an X mark in a check box corresponding to the selected view so as to be continuously distinguished from the unselected view. When the number of the selected views exceeds the preset number, the display state of each view can be labeled, for example, each selected view is labeled in a highlighting mode. Furthermore, the selected view can be used as a view to be managed, and corresponding operation of the view to be managed is realized by clicking any one of the upgrading control, the deleting control, the exporting control or the modifying control. Furthermore, when all the views in the view management list need to be selected, all the views can be used as views to be managed by clicking the full-selection control below the view management list.

And S130, updating the view to be managed based on the view corresponding to the management operation.

In this embodiment, the management operation may include at least one of browsing, sharing, sorting, modifying, deleting, and exporting, and for the browsing operation, the display content and the display mode of the view to be managed are not changed after the operation, but the operations such as sharing, sorting, modifying, deleting, and exporting change the display content and/or the display mode of the view to be managed. Therefore, when the management operation is finished, whether the display contents and/or the display modes of the view to be managed before the operation and the view to be managed after the operation are consistent or not can be detected, and if the display contents and/or the display modes are consistent, the state of the view to be managed before the operation is kept; if not, the view to be managed after the management operation is saved as a new view to replace the view to be managed before the operation, so as to finish the updating operation of the view to be managed.

Specifically, before updating the view to be managed, whether it is detected whether the control of "saving the current view" is triggered can be determined, and if so, the view to be managed is updated based on the current corresponding view, so as to avoid view errors caused by misoperation of the user on the view to be managed; if not, query information can be displayed on the interface according to a preset time interval, the query information can be popped up to the display interface in a dialog box mode to show a text of 'whether the view needs to be updated', when the 'update determining' control is triggered, the view to be processed can be updated, and when the 'update not temporarily' control is triggered, the view to be managed does not need to be updated.

Furthermore, a preset number of views to be managed before updating can be stored, and when a user operates wrongly or wants to view historical views, the views to be managed before updating are displayed again, so that the convenience of user operation is improved. Or, each view to be managed before updating in the preset time period can be stored, so that the user can manage and check each historical view to be managed in the preset time period.

Fig. 5 is a flowchart illustrating a view management method according to an embodiment of the disclosure; on the basis of the previous embodiment, when the trigger view creation control is detected, drawing a target view; and when the trigger of the sequencing control in the view to be managed is detected, sequencing the data in the view to be managed. The technical scheme of the embodiment can be referred to for the specific implementation mode. The technical terms that are the same as or corresponding to the above embodiments are not repeated herein.

As shown in fig. 5, the method specifically includes the following steps:

s210, when the trigger view processing control is detected, displaying a view management list; and the view management list comprises the view associated information of at least one created view which is currently managed.

S220, taking the created view corresponding to the view related information triggered in the view management list as a view to be managed, and performing management operation on the view to be managed based on the operation authority information corresponding to the view to be managed.

And S230, updating the view to be managed based on the view corresponding to the management operation.

And S240, when the condition that the view creation control is triggered is detected, obtaining view name information in the view name editing control.

The view creation control is used for creating a new view, the view name editing control is used for inputting name information of a view to be created, and the view name information comprises an identifier and/or a name of the view to be created, such as 'a view required in the current week', 'a view completed in the current week', and 'a view not completed in the current week'.

It should be noted that, the user can customize the requirement list or the display condition according to the actual use preference, so as to create the view based on the actual requirement. In a specific implementation, after the view creation control is triggered, a view name editing page containing the view name editing control can be popped up. The view name editing control can comprise at least one control of an input box, a selection key, a scroll bar and a pull-down menu, and the view name editing control can be triggered to acquire information by selecting preset name information, actively inputting information and the like. By obtaining the content input in the view editing control, the view name information can be obtained.

And S250, acquiring at least one screening condition and/or at least one configuration item selected from the requirement list, and determining the view drawing participation data.

The requirement list comprises at least one configuration item, and the configuration item comprises at least one of links of other views, data links and project associated data; the screening condition is used for screening configuration items in the requirement list so as to draw the participation data by taking the screened configuration items as views.

In this embodiment, when the view drawing participation data is determined by the screening condition, the screening condition may include at least one of time screening information, progress screening information, and participation user screening information, and if the screening condition may be set to "project data completed within the first time period", data satisfying the screening condition may be used as the view drawing participation data. When the view drawing participation data is determined through the selected configuration items, whether each configuration item of the requirement list is selected or not can be detected, and the data corresponding to the selected configuration item is determined as the view drawing participation data.

And S260, drawing the target view according to the selected view display form, the view name information and the view drawing participation data.

Wherein the view display form comprises at least one of a list view, a bar chart, a pie chart, a line chart, a graph, a three-dimensional view and a Gantt chart. The list view can clearly show all detailed information, such as service lines, priority, responsible persons or nodes in progress, and the like. Gantt charts are a type of bar chart showing the progression of items, progress, and other time-related system progress and internal relationships over time. The progress of a requirement, a node subtask or a single version iteration can be visually displayed through a Gantt chart. Specifically, the gantt chart supports step size settings, supporting particle presentation at different times, such as monthly, bi-monthly, semi-annual, and yearly.

In this embodiment, an alternative view display form may be displayed in advance, the display form may be a hidden folding display or an unfolding display, and when it is detected that a control corresponding to the alternative view display form is triggered, the triggered alternative view display form may be determined as a target view display form, view drawing participation data is displayed in an interface according to the target view display form, and view name information is correspondingly displayed, so as to generate a target view.

And S270, when the trigger view determination control is detected, taking the target view as the created view, and updating the view association information of the target view to the view management list.

Wherein the view determination control is used for confirming whether the generated target view is determined as the created view and updating the view management list. In particular implementation, in order to prevent misoperation, a view determination control may be set, and after the view determination control is triggered, the target view is taken as the created view.

Further, in order to facilitate searching for the target view, the view management information of the target view may be updated into the view management list. For example, the view association information corresponding to the target view may be added to the view management list according to the view creation time sequence.

Specifically, the view type of the created view may also be set, for example, when the currently displayed created view is set to be the system view, the displayed created view may be set to be the system view by the user when the system view switch control is turned on; and providing a control for collecting the system view for the control member, collecting the system view through the control, and setting the system view in a collected view list by default. Furthermore, the sizes of the rows and columns of the created view can be set, such as compact, moderate, high, ultrahigh and self-defined table height types in the view; similarly, the line width can be set to be compact, moderate, high, ultrahigh and self-defined; a save operation may be performed for the set line size, after which the created view may be opened again for display in accordance with the saved line size.

In particular implementations, while displaying the created view, an "open on New tab" option may be provided on the display interface, which, when selected, restarts a new page while displaying the created view.

In this embodiment, the method further includes: setting browsing permission and operation permission information for the created view, determining the external visibility of the created view based on the browsing permission, and performing management operation on the created view based on the operation permission information; view links corresponding to the created views are generated to retrieve the created views based on the view links.

In order to better manage the view and improve the safety, the created view can be set with browsing authority and operation authority information. The operation authority information comprises at least one operation authority of sequencing, sharing, collecting, deleting, modifying, exporting and upgrading of views to be managed, and different users have different operation authorities for different views to be managed.

In specific implementation, different browsing permissions and operation permission information can be set for the created view according to different role types of the operation users. For example, when the view management method provided by this embodiment is applied to a project management system, the operation permissions of various role types may be set in a setting panel by clicking an "edit" control. The operation authority can be divided into the following cases: 1. disclosure rights, all accesses this can modify view settings; 2. non-public rights, only the creator or collaborator may modify the view settings; 3. the collaborators can modify the view display conditions, and can synchronously apply to all view access after the change is stored; 4. in the fixed view, collaborators may add or remove requirement lists in the fixed view.

Exemplarily, for an operation user with a role type of view creator, the browsing permission can be set to allow browsing, and the operation permission can be at least one operation of sequencing, sharing, collecting, deleting, modifying, exporting and upgrading the view; for an operation user with a collaborator role type, the browsing permission can be set to allow browsing, and the operation permission can not be any one of sequencing, sharing, collecting, deleting, modifying, exporting and upgrading; and for the role type of an illegal user, namely an unregistered user, setting the browsing authority as not allowing browsing and the operation authority as not allowing any operation.

Further, in order to facilitate the user to quickly and conveniently acquire the view, a view link may be generated based on the view association information of the created view, the view link may be displayed to a corresponding position of the created view of the view management list, and the corresponding created view may be directly accessed through the view link.

And S280, when the sequencing control in the view to be managed is detected to be triggered, determining an index item corresponding to the sequencing control, sequencing the data in the view to be managed according to the index item, and updating the view to be managed.

And the index item is a list head and/or a line head in the view to be managed. The list head comprises at least one item of creation time, view data volume, creation user, task responsible person and priority; the row header includes a view identification. The sorting processing comprises ascending processing and descending processing, and the sorting control comprises an ascending sorting control and a descending sorting control.

In specific implementation, determining an implementation manner of the indicator item corresponding to the sorting control may include: when a sorting control triggering the view to be managed is detected, popping up a sorting selection window, determining a selected index item in the sorting selection window, and sorting the data in the view to be managed according to the selected index item; or establishing corresponding sorting sub-controls for each list head item contained in the row list head and/or the list head, determining the list head item corresponding to the triggered sorting sub-control after detecting that the sorting sub-control is triggered, sorting the data in the view to be managed according to the list head item, and updating the view to be managed according to the sorting result.

Illustratively, as shown in fig. 6, the list header includes contents such as a name, a creating user, and a creating time, and the row header includes view association information; a "↓" control and a "↓" control are arranged in a table of each item in the head of the list and used for representing ascending sorting; determining a sequencing sequence by clicking the ascending and descending sequence control; and determining the index items corresponding to the clicking operation, and sequencing the determined index items according to the determined sequencing order to obtain the view to be managed according with the sequencing order.

In this embodiment, when it is detected that a grouping control in the view to be managed is triggered, grouping information corresponding to the grouping control is determined, data in the view to be managed is grouped and processed according to the grouping information, and the view to be managed is updated. Specifically, grouping items can be configured through the editing page, grouping information is generated based on the configured grouping items, and data in the view to be managed is grouped, so that the data is clearly and hierarchically displayed. Illustratively, three levels of grouping may be supported.

Furthermore, the view can be provided with controls for node circulation, state circulation and the like, when the node circulation control is triggered, the information of the circulation node can be acquired based on the node circulation control, and node circulation can be performed quickly in the view to be managed. The state flow comprises the state flow among the defects, the iterations and the version views, and the defects, the iterations and the version views are quickly switched through the state flow control.

In the embodiment of the disclosure, the visual image creating control creates a target view, and sets the browsing authority and the operation authority of the created view so as to improve the safety of the view operation; and the established view which is required to be operated can be quickly and conveniently searched and obtained through the established view link. In addition, the data in the view to be managed can be sorted according to the index items, and the diversified requirements of the user can be better met.

Fig. 7 is a schematic structural diagram of a view management apparatus according to an embodiment of the present disclosure, which is capable of executing a view management method according to any embodiment of the present disclosure, and has functional modules and beneficial effects corresponding to the execution method. As shown in fig. 7, the apparatus includes: a view management list display module 310, a view to be managed operation module 320, and a view to be managed update module 330.

A view management list display module 310, configured to display a view management list when detecting that the view processing control is triggered; the view management list comprises view associated information of at least one created view which is managed currently;

a view to be managed operation module 320, configured to use the created view corresponding to the view association information triggered in the view management list as a view to be managed, and perform a management operation on the view to be managed based on the operation permission information corresponding to the view to be managed;

a view to be managed updating module 330, configured to update the view to be managed based on the view corresponding to the management operation completed.

On the basis of the above technical solutions, the apparatus further includes:

the view name information acquisition module is used for acquiring view name information in the view name editing control when the view creation control is detected to be triggered;

the view drawing participation data determining module is used for acquiring at least one screening condition and/or at least one configuration item selected from the requirement list and determining view drawing participation data;

the target view drawing module is used for drawing a target view according to the selected view display form, the view name information and the view drawing participation data;

the view management list updating module is used for taking the target view as the created view and updating the view related information of the target view to the view management list when a trigger view determination control is detected;

wherein the view presentation form comprises at least one of a list view, a bar graph, a pie graph, a line graph, a three-dimensional view and a gantt chart.

On the basis of the above technical solutions, the apparatus further includes:

the management operation module is used for setting browsing authority and operation authority information for the created view, determining the external visibility of the created view based on the browsing authority, and performing management operation on the created view based on the operation authority information;

a view link generation module for generating a view link corresponding to the created view to acquire the created view based on the view link.

On the basis of the above technical solutions, the view management list display module 310 includes:

a window pop-up unit for popping up a window including a view management list;

and the list expansion unit is used for expanding and displaying the view management list which is folded and displayed in the display interface.

On the basis of the above technical solutions, the view association information includes at least one indicator item, where the at least one indicator item includes at least one of view name information, creator identification, creation time, browsing authority, and collaborator; the created view includes at least one of a system view, a fixed view, and a conditional view.

On the basis of the technical schemes, the system view is a template view created by an administrator;

the fixed view is a view created after at least one configuration item is selected from a requirement list of item fixation; the configuration items comprise at least one of links of other views, data links and each requirement item in project association data;

the conditional view is a view generated after determining view participation data based on preset screening conditions.

On the basis of the above technical solutions, the view to be managed operation module 320 includes:

the view sharing unit is used for sharing the view link of the view to be managed to at least one user to be shared when the sharing operation of the view to be managed is detected and the operation authority information comprises a sharing authority, so that the view to be managed is obtained based on the view link.

and the view collection unit is used for collecting the view to be managed or canceling the collection of the view to be managed if the collection authority is included in the operation authority information.

the view batch management unit is used for carrying out batch management operation on at least one view to be managed if the operation authority information comprises view batch operation;

the view batch operation comprises at least one of batch upgrading, batch deleting, batch modifying, batch exporting and dragging.

On the basis of the above technical solutions, the apparatus further includes:

the index item determining module is used for determining an index item corresponding to a sequencing control when the sequencing control in the view to be managed is triggered;

the view data sorting module is used for sorting the data in the view to be managed according to the index items and updating the view to be managed;

and the index item is a list head and/or a line head in the view to be managed.

The view management device provided by the embodiment of the disclosure can execute the view management method provided by any embodiment of the disclosure, and has corresponding functional modules and beneficial effects of the execution method.

It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only used for distinguishing one functional unit from another, and are not used for limiting the protection scope of the embodiments of the present disclosure.

Fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. Referring now to fig. 8, a schematic diagram of an electronic device (e.g., the terminal device or the server in fig. 8) 400 suitable for implementing embodiments of the present disclosure is shown. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 8, electronic device 400 may include a processing device (e.g., central processing unit, graphics processor, etc.) 401 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 402 or a program loaded from a storage device 408 into a Random Access Memory (RAM) 403. In the RAM 403, various programs and data necessary for the operation of the electronic apparatus 400 are also stored. The processing device 401, the ROM402, and the RAM 403 are connected to each other via a bus 404. An editing/output (I/O) interface 405 is also connected to bus 404.

Generally, the following devices may be connected to the I/O interface 405: input devices 406 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 407 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage devices 408 including, for example, magnetic tape, hard disk, etc.; and a communication device 409. The communication means 409 may allow the electronic device 400 to communicate wirelessly or by wire with other devices to exchange data. While fig. 8 illustrates an electronic device 400 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication device 409, or from the storage device 408, or from the ROM 402. The computer program, when executed by the processing device 401, performs the above-described functions defined in the methods of the embodiments of the present disclosure.

The electronic device provided by the embodiment of the present disclosure and the view management method provided by the above embodiment belong to the same inventive concept, and technical details that are not described in detail in the embodiment can be referred to the above embodiment, and the embodiment has the same beneficial effects as the above embodiment.

The disclosed embodiments provide a computer storage medium having stored thereon a computer program that, when executed by a processor, implements the view management method provided by the above-described embodiments.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.

The computer readable medium may be embodied in the electronic device; or may be separate and not incorporated into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to:

the computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: when the trigger view processing control is detected, displaying a view management list; the view management list comprises view associated information of at least one created view which is managed currently; taking the created view corresponding to the view related information triggered in the view management list as a view to be managed, and performing management operation on the view to be managed based on the operation authority information corresponding to the view to be managed; and updating the view to be managed based on the view corresponding to the management operation.

Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems on a chip (SOCs), complex Programmable Logic Devices (CPLDs), and the like.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

According to one or more embodiments of the present disclosure, [ example one ] there is provided a view management method, including:

when the trigger view processing control is detected, displaying a view management list; wherein the view management list comprises view associated information of at least one created view which is currently managed;

According to one or more embodiments of the present disclosure [ example two ] there is provided a view management method, comprising:

when the trigger view creation control is detected, obtaining view name information in a view name editing control;

acquiring at least one screening condition and/or at least one configuration item selected from a requirement list, and determining view drawing participation data;

drawing a target view according to the selected view display form, the view name information and the view drawing participation data;

when a trigger view determination control is detected, taking the target view as the created view, and updating the view association information of the target view to the view management list;

According to one or more embodiments of the present disclosure, [ example three ] there is provided a view management method, comprising:

setting browsing authority and operation authority information for the created view, determining the external visibility of the created view based on the browsing authority, and performing management operation on the created view based on the operation authority information;

generating a view link corresponding to the created view to retrieve the created view based on the view link.

According to one or more embodiments of the present disclosure, [ example four ] there is provided a view management method, comprising:

popping up a window including a view management list;

and expanding and displaying the view management list which is displayed in a folding manner in the display interface.

According to one or more embodiments of the present disclosure, [ example five ] there is provided a view management method comprising:

the view association information comprises at least one index item, and the at least one index item comprises at least one of view name information, creator identification, creation time, browsing permission and collaborators; the created view includes at least one of a system view, a fixed view, and a conditional view.

According to one or more embodiments of the present disclosure, [ example six ] there is provided a view management method comprising:

the system view is a template view created by an administrator;

the fixed view is a view created after at least one configuration item is selected from a requirement list of item fixation; the configuration items comprise at least one of links of other views, data links and requirement items in project association data;

According to one or more embodiments of the present disclosure, [ example seven ] there is provided a view management method comprising:

when the sharing operation of the view to be managed is detected, and the operation authority information comprises sharing authority, sharing the view link of the view to be managed to at least one user to be shared, so as to obtain the view to be managed based on the view link.

According to one or more embodiments of the present disclosure, [ example eight ] there is provided a view management method, comprising:

and if the operation authority information comprises a collection authority, collecting the view to be managed or canceling to collect the view to be managed.

According to one or more embodiments of the present disclosure, [ example nine ] there is provided a view management method, comprising:

if the operation authority information comprises view batch operation, performing batch management operation on at least one view to be managed;

According to one or more embodiments of the present disclosure, [ example ten ] there is provided a view management method comprising:

when the sequencing control in the view to be managed is detected to be triggered, determining an index item corresponding to the sequencing control;

sorting the data in the view to be managed according to the index items, and updating the view to be managed;

and the index item is a list head and/or a line head in the view to be managed.

According to one or more embodiments of the present disclosure, [ example eleven ] there is provided an example view management apparatus, further comprising:

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method for view management, comprising:

2. The method of claim 1, further comprising:

3. The method of claim 2, further comprising:

4. The method of claim 1, wherein displaying the view management list comprises:

popping up a window including a view management list;

5. The method according to claim 1, wherein the view association information includes at least one index item, and the at least one index item includes at least one of view name information, creator identification, creation time, browsing right and collaborator; the created view includes at least one of a system view, a fixed view, and a conditional view.

6. The method of claim 5, wherein the system view is a template view created by an administrator;

7. The method according to claim 1, wherein the performing management operation on the view to be managed based on the operation authority information corresponding to the view to be managed comprises:

when the sharing operation of the view to be managed is detected and the operation authority information comprises sharing authority, sharing the view link of the view to be managed to at least one user to be shared so as to obtain the view to be managed based on the view link.

8. The method according to claim 1, wherein the performing management operation on the view to be managed based on the operation authority information corresponding to the view to be managed comprises:

9. The method according to claim 1, wherein the performing management operation on the view to be managed based on the operation authority information corresponding to the view to be managed comprises:

10. The method of claim 1, further comprising:

and the index item is a list head and/or a line head in the view to be managed.

11. A view management apparatus, comprising:

12. An electronic device, characterized in that the electronic device comprises:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the view management method of any of claims 1-10.

13. A storage medium containing computer-executable instructions for performing the view management method of any of claims 1-10 when executed by a computer processor.