A directory management method, device and equipment

Abstract

The application discloses a catalog management method, device and equipment, the method comprises the following steps: receiving the catalog metadata editing request of a user; according to the catalog metadata editing request, arranging and processing target catalog metadata according to the scene of a cloud platform, generating a catalog list for the scene; and displaying the catalog list of the scene. Through the above method, the application realizes unified management of multi-scene data and catalog arrangement in different scenes.

Description

Technical Field

[0001] This invention relates to the field of cloud platform information management technology, specifically to a directory management method, apparatus, and equipment. Background Technology

[0002] Currently, the storage and management of directory metadata are handled through the backend. However, the management of cloud service products is separated from the platform's directory management, resulting in the lack of correlation between cloud service launch and decommissioning information and the platform's directory. This leads to customers clicking on the directory only to find that the product has been taken offline, resulting in a poor service experience. Furthermore, the cloud platform has complex integration relationships, diverse directory display scenarios, and different directory requirements for different scenarios. Different systems also have directory display needs, but the display styles and data are inconsistent. Summary of the Invention

[0003] In view of the above problems, embodiments of the present invention are proposed to provide a catalog management method, apparatus and device that overcomes or at least partially solves the above problems.

[0004] According to one aspect of the present invention, a directory management method is provided, applied to a directory management system of a cloud platform, the method comprising:

[0005] Receive user requests to edit directory metadata;

[0006] Based on the directory metadata editing request, the target directory metadata is arranged and processed according to the scenario of the cloud platform to generate a directory list oriented towards the scenario;

[0007] Display a directory list of the scenarios described.

[0008] According to another aspect of the present invention, a directory management device is provided, applied to a directory management system of a cloud platform, the device comprising:

[0009] The receiving module is used to receive users' requests to edit directory metadata;

[0010] The processing module is used to organize and process the target directory metadata according to the scenario of the cloud platform based on the directory metadata editing request, generate a directory list for the scenario, and display the directory list for the scenario.

[0011] According to another aspect of the present invention, a computing device is provided, comprising: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other through the communication bus;

[0012] The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the directory management method described above.

[0013] According to another aspect of the present invention, a computer storage medium is provided, the storage medium storing at least one executable instruction that causes a processor to perform an operation corresponding to the directory management method described above.

[0014] According to the solution provided in the above embodiments of the present invention, the directory management method can receive a user's directory metadata editing request; based on the directory metadata editing request, arrange and process the target directory metadata according to the scenario of the cloud platform to generate a directory list for the scenario; and display the directory list for the scenario. This solves the problem of poor service experience caused by the lack of association between cloud service online / offline information and the platform directory, realizes unified management of multi-scenario data and directory arrangement for different scenarios, synchronizes directory management with product management, and realizes the functions of product delisting and online updating of directory data.

[0015] The above description is merely an overview of the technical solutions of the embodiments of the present invention. In order to better understand the technical means of the embodiments of the present invention and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of the present invention more obvious and understandable, specific implementation methods of the embodiments of the present invention are described below. Attached Figure Description

[0016] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0017] Figure 1 A flowchart illustrating a directory management method provided in an embodiment of the present invention is shown;

[0018] Figure 2 A flowchart illustrating the operation of the directory management system in an embodiment of the present invention is shown;

[0019] Figure 3 A schematic diagram of the structure of a directory management device provided in an embodiment of the present invention is shown;

[0020] Figure 4 A schematic diagram of the structure of a computing device provided in an embodiment of the present invention is shown. Detailed Implementation

[0021] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0022] Figure 1 A flowchart illustrating a directory management method provided in an embodiment of the present invention is shown. Figure 1 As shown, the method includes the following steps:

[0023] Step 11: Receive the user's directory metadata editing request;

[0024] Step 12: Based on the directory metadata editing request, the target directory metadata is arranged and processed according to the scenario of the cloud platform to generate a directory list oriented towards the scenario;

[0025] Step 13: Display the directory list of the scenario.

[0026] The scenarios include at least one of the following: portal homepage directory scenario; cloud service product order page directory scenario; cloud service product shopping cart directory scenario; console directory scenario; but are not limited to these scenarios.

[0027] In this embodiment, a preferred user can initiate a directory metadata editing request to the directory management system of the cloud platform through a visual metadata management platform. The directory management system arranges and processes the target directory metadata according to the scenario of the cloud platform, generates a scenario-oriented directory list, and displays the scenario-oriented directory list. This achieves unified management of multi-scenario data, realizes directory arrangement for different scenarios, connects directory management with product management, and enables the functions of product delisting and online updating of directory data. Here, the directory metadata editing request initiated by the user includes at least one of the following: directory metadata addition request, directory metadata deletion request, directory metadata modification request, directory metadata query request, directory metadata publication request, and directory metadata approval request.

[0028] The target directory metadata includes at least one of the following: directory ID (identification code), directory name, directory code, system internal code, directory level, parent directory ID (identification code), directory sorting, directory description, directory badge identifier, directory badge expiration time, listing status, whether billing is enabled, whether public beta is enabled, product URL (Uniform Resource Locator), introduction page URL, order page URL, user agreement URL, price details URL, help center URL, service agreement URL, registration agreement URL, creator, creation time, updater, update time, and whether deletion is enabled.

[0029] The portal homepage directory scenario is used to display all products of the portal information. Specifically, it includes at least one of the following: a product catalog that can be subscribed to, a product catalog that does not require subscription, and a product catalog that allows service activation. It needs to include products in public beta and products that are officially launched.

[0030] The cloud service product subscription page catalog scenario is used to display the catalog of products available for subscription from the full range of products on the portal, and it needs to include products in public beta and products that have been officially launched.

[0031] The shopping cart catalog scenario for cloud service products is used to display selected, orderable products.

[0032] The console directory scenario is used to display a list of all resource product catalogs that can be managed in the resource console of the catalog management system. It needs to include all products in public beta, all products in internal beta, and all products that have been officially launched.

[0033] It should be noted that preferred users can also initiate directory scene data editing requests to the cloud platform's directory management system through the visual metadata management platform.

[0034] In an optional embodiment of the present invention, step 12 includes:

[0035] Step 121: Based on the directory metadata editing request, create a directory metadata list and a scenario list;

[0036] Step 122: Associate the directory metadata list and the scene list to obtain an association table;

[0037] Step 123: Arrange the target directory metadata according to the association table to generate a directory list for the scenario.

[0038] In this embodiment, the cloud platform's directory management system creates a directory metadata list and a scenario list based on the directory metadata editing request, associates the directory metadata list and the scenario list to obtain an association table, and arranges the target directory metadata according to the association table to determine and generate the directory list to be displayed in each scenario.

[0039] In an optional embodiment of the present invention, step 123 includes:

[0040] Step 1231: Arrange the target directory metadata according to the directory metadata arrangement rules corresponding to the association table to generate a directory list for the scenario.

[0041] In this embodiment, the metadata of the target directory can be arranged according to the relationship between internal testing, public testing and official launch, or according to the relationship between listing and delisting, or according to the relationship between deletion and non-deletion. This embodiment is not limited to these.

[0042] In an optional embodiment of the present invention, the directory management method further includes:

[0043] Step 14: Generate common components for the scene based on the directory list of the scene;

[0044] Step 15: Process the data of the third-party system accessing the cloud platform according to the common components of the scenario.

[0045] In this embodiment, the front end of the directory management system obtains the directory list of the scenario by calling the interface, and builds a common component (orderHeader) for different scenarios based on the directory list. It should be noted that different scenarios correspond to different common components. The common components include: a scaffold that encapsulates the display style information and display data information of the directory, and a common scaffold that uses the Hypertext Markup Language (HTML) language to display the style. The common components of different scenarios can be used to process data from third-party systems accessing the cloud platform.

[0046] Optionally, step 15 includes:

[0047] Based on the common components of the scenario, a unified directory display style and / or data display format are adopted to display data from at least two third-party systems connected to the cloud platform.

[0048] In this embodiment, the front end of the directory management system implements scene navigation based on the scene, quickly references the corresponding public components, and displays the data of the third-party system using a unified directory display style and / or data display format. Here, preferably, the unified directory display style is the Vue format, which is a progressive framework used to build user interfaces; preferably, the unified data display format is the format of the directory metadata obtained by calling the API (Application Programming Interface).

[0049] Furthermore, in step 13, when displaying the directory list of the scenarios, the directory list of scenarios can be called through the public scaffolding to update the data, and then the updated directory list of scenarios can be displayed through the public scaffolding; the synchronization and updating of data information across the entire network can also be achieved through the public scaffolding and / or API.

[0050] In an optional embodiment of the present invention, the directory management method may further include:

[0051] Step 16: Obtain the real-time validity status of cloud service products provided in the cloud service product system;

[0052] Step 17: Update the directory metadata according to the real-time validity status of the cloud service product.

[0053] In this embodiment, the directory management system obtains the real-time validity status of cloud service products provided in the cloud service product system. When the status of cloud service products being listed or delisted changes, the real-time validity status synchronization interface is triggered. Preferably, the directory code can be used as an interactive judgment identifier to synchronize the real-time validity status of the directory corresponding to the cloud service product.

[0054] Based on the effective implementation status of cloud service products, the operation of updating the directory metadata is triggered. The directories that are in the unavailable state are deleted from the portal homepage directory scenario and the cloud service product order page directory scenario, and the association relationship of the unavailable directories is canceled in the association table. When the user initiates a directory metadata editing request again, it will be arranged and processed according to the updated directory metadata.

[0055] Figure 2 A flowchart illustrating the operation of the directory management system in an embodiment of the present invention is shown; for example... Figure 2 As shown, in a specific embodiment, the method includes the following steps:

[0056] Users can access the visual metadata management platform within the directory management system and submit requests to edit directory metadata, such as adding, deleting, modifying, searching, publishing, and approving.

[0057] The scenario-based directory manager organizes and processes the target directory metadata according to the scenario of the cloud platform, and generates a scenario-oriented directory list. The scenario-based directory list includes the homepage directory, order page directory, shopping cart directory, and console directory, etc.

[0058] The front-end calls the interface corresponding to the directory list of the scene through the component corresponding to the directory. The component corresponding to the home directory is the public navigation component, the component corresponding to the order page directory is the order navigation component, the component corresponding to the shopping cart directory is the shopping cart component, and the component corresponding to the console directory is the console navigation component. When a third-party system needs to call the interface corresponding to the directory list of the scene, it can call the home directory, order page directory, shopping cart directory, and console directory through the public component. That is, the public component can implement the functions of the public navigation component, order navigation component, shopping cart component, and console navigation component.

[0059] When a product is listed or delisted, the catalog metadata is updated on the product side to reflect the product's real-time validity status, and the catalog metadata is synchronized and displayed simultaneously.

[0060] The solution of this invention receives a user's directory metadata editing request; based on the directory metadata editing request, it arranges and processes the target directory metadata according to the scenario of the cloud platform to generate a directory list for the scenario; and displays the directory list for the scenario. This solves the problem of poor service experience caused by the lack of association between cloud service online / offline information and the platform directory, realizes unified management of multi-scenario data, realizes directory arrangement for different scenarios, connects directory management with product management, and realizes the functions of product delisting and online update of directory data.

[0061] Figure 3 A schematic diagram of the structure of a directory management device provided in an embodiment of the present invention is shown. For example... Figure 3 As shown, the directory management system applied to the cloud platform includes the following components:

[0062] Receiver module 31 is used to receive user requests to edit directory metadata;

[0063] The processing module 32 is used to arrange and process the target directory metadata according to the scenario of the cloud platform based on the directory metadata editing request, generate a directory list for the scenario, and display the directory list for the scenario.

[0064] Optionally, the scenario includes at least one of the following:

[0065] Portal homepage directory scenario;

[0066] The scenario of a cloud service product order page catalog;

[0067] Shopping cart catalog scenario for cloud service products;

[0068] Console directory scenario.

[0069] Optionally, processing module 32 includes:

[0070] The first processing submodule is used to create a directory metadata list and a scene list based on the directory metadata editing request;

[0071] The second processing submodule is used to associate the directory metadata list and the scene list to obtain an association table.

[0072] The third processing submodule is used to organize and process the target directory metadata according to the association table to generate a directory list oriented towards the scenario.

[0073] Optional, the third processing submodule includes:

[0074] The first processing unit is used to arrange the target directory metadata according to the directory metadata arrangement rules corresponding to the association table, and generate a directory list for the scenario.

[0075] Optionally, the processing module 32 is further configured to generate common components of the scenario based on the directory list of the scenario; and process data from third-party systems accessing the cloud platform based on the common components of the scenario.

[0076] Optionally, processing module 32 includes:

[0077] The fourth processing submodule is used to display data from at least two third-party systems connected to the cloud platform, based on the common components of the scenario and using a unified directory display style and / or data display format.

[0078] Optionally, the processing module 32 is also used to obtain the real-time validity status of cloud service products provided in the cloud service product system; and update the directory metadata according to the real-time validity status of the cloud service products.

[0079] It should be noted that this device is the same as the method described above. All implementations in the above method embodiments are applicable to the embodiments of this device and can achieve the same technical effect.

[0080] This invention also provides a directory management system for a cloud platform, including the device described above. All implementation methods in the above embodiments are applicable to the embodiments of this system and can achieve the same technical effect. The processing module can be implemented by a directory editor. The system may further include a scene editor for editing scenes on the cloud platform, such as deleting, modifying, adding, and updating relevant scene information.

[0081] This invention also provides a non-volatile computer storage medium storing at least one executable instruction that can execute the directory management method in any of the above method embodiments.

[0082] Figure 4 The diagram shows a structural schematic of a computing device provided in an embodiment of the present invention. The specific embodiments of the present invention do not limit the specific implementation of the computing device.

[0083] like Figure 4 As shown, the computing device may include a processor, a communications interface, memory, and a communications bus.

[0084] The processor, communication interface, and memory communicate with each other via a communication bus. The communication interface is used to communicate with other network elements, such as clients or other servers. The processor executes programs, specifically the steps described in the above embodiment of the directory management method for computing devices.

[0085] Specifically, the program may include program code, which includes computer operation instructions.

[0086] The processor may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The computing device includes one or more processors, which may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0087] Memory is used to store programs. Memory may include high-speed RAM, and may also include non-volatile memory, such as at least one disk drive.

[0088] Specifically, the program can be used to cause the processor to execute the directory management method in any of the above method embodiments. The specific implementation of each step in the program can be found in the corresponding descriptions of the steps and units in the above directory management method embodiments, and will not be repeated here. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the devices and modules described above can be referred to the corresponding process descriptions in the foregoing method embodiments, and will not be repeated here.

[0089] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used in conjunction with the teachings herein. The required structure for constructing such systems is apparent from the above description. Furthermore, the embodiments of the present invention are not directed to any particular programming language. It should be understood that the embodiments of the present invention described herein can be implemented using various programming languages, and the above description of specific languages ​​is for the purpose of disclosing the best mode of implementation of the embodiments of the present invention.

[0090] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0091] Similarly, it should be understood that, in order to streamline the embodiments of the invention and aid in understanding one or more of the various inventive aspects, features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof in the above description of exemplary embodiments of the invention. However, this disclosure should not be construed as reflecting an intention that the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, as reflected in the following claims, inventive aspects lie in fewer than all features of a single foregoing disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of the invention.

[0092] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiments can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.

[0093] Furthermore, those skilled in the art will understand that although some embodiments herein include certain features included in other embodiments but not others, combinations of features from different embodiments are intended to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[0094] The various component embodiments of the present invention can be implemented in hardware, or as software modules running on one or more processors, or a combination thereof. Those skilled in the art will understand that microprocessors or digital signal processors (DSPs) can be used in practice to implement some or all of the functions of some or all of the components according to the embodiments of the present invention. The embodiments of the present invention can also be implemented as device or apparatus programs (e.g., computer programs and computer program products) for performing part or all of the methods described herein. Such programs implementing the embodiments of the present invention can be stored on a computer-readable medium, or can be in the form of one or more signals. Such signals can be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.

[0095] It should be noted that the above embodiments are illustrative of the present invention and not restrictive of the invention, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. Embodiments of the present invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be construed as limiting the order of execution.

Claims

1. A method for managing a directory, characterized in that, A directory management system applied to a cloud platform, the method comprising: Receive user requests to edit directory metadata; Based on the directory metadata editing request, the target directory metadata is arranged and processed according to the scenario of the cloud platform to generate a directory list oriented towards the scenario; Display a directory list of the described scenarios; Based on the directory list of the scenario, generate common components for the scenario; based on the common components of the scenario, use a unified directory display style and / or data display format to display data from at least two third-party systems connected to the cloud platform; wherein, different scenarios correspond to different common components, and the common components include: a scaffold that encapsulates the directory display style information and the display data information, and a common scaffold that uses the Hypertext Markup Language (HTML) language to display the style.

2. The directory management method according to claim 1, characterized in that, The scenario includes at least one of the following: Portal homepage directory scenario; The scenario of a cloud service product order page catalog; Shopping cart catalog scenario for cloud service products; Console directory scenario.

3. The directory management method according to claim 1, characterized in that, Based on the directory metadata editing request, the target directory metadata is arranged and processed according to the scenario of the cloud platform to generate a directory list oriented towards the scenario, including: Based on the directory metadata editing request, create a directory metadata list and a scenario list; The directory metadata list and the scene list are associated to obtain an association table; The target directory metadata is organized and processed based on the association table to generate a directory list tailored to the scenario.

4. The directory management method according to claim 3, characterized in that, The target directory metadata is organized and processed according to the association table to generate a directory list oriented towards the scenario, including: Based on the directory metadata arrangement rules corresponding to the association table, the target directory metadata is arranged and processed to generate a directory list for the scenario.

5. The directory management method according to claim 1, characterized in that, Also includes: Real-time access to the real-time validity status of cloud service products provided in the cloud service product system; The directory metadata is updated based on the real-time validity status of the cloud service product.

6. A catalog management device, characterized in that, A directory management system applied to a cloud platform, the device comprising: The receiving module is used to receive users' requests to edit directory metadata; The processing module is used to, based on the directory metadata editing request, arrange and process the target directory metadata according to the scenario of the cloud platform, and generate a directory list for the scenario; display the directory list of the scenario; generate common components for the scenario based on the directory list of the scenario; and, based on the common components of the scenario, display data from at least two third-party systems connected to the cloud platform using a unified directory display style and / or data display format; wherein, different scenarios correspond to different common components, and the common components include: a scaffold that encapsulates the directory display style information and the display data information, and a common scaffold that uses the Hypertext Markup Language (HTML) language for display style.

7. A computing device, comprising: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the directory management method as described in any one of claims 1-5.

8. A computer storage medium storing at least one executable instruction that causes a processor to perform an operation corresponding to the directory management method as described in any one of claims 1-5.

Images