Shulou(Shulou.com)06/02 Report--

Most people do not understand the knowledge points of this article "what is the design method of metadata for web automation platform development?", so the editor summarizes the following contents, detailed contents, clear steps, and has a certain reference value. I hope you can get something after reading this article. Let's take a look at this article "what is the design method of web automation platform development metadata?"

Design of metadata

My design for this part of the metadata is to keep it simple, first give a summary of the information, and then the details can be seen through other entrances.

For example, for the database, system, rack location information, these can be obtained from the brother department through the way of API. It can be used as a reference for information.

In the design and planning of a lot of metadata, if there is a formed system in the early stage, it is not good to directly discard it and get rid of the revolution. It is still necessary to absorb the existing experience and gradually precipitate. Things always do not start completely from scratch, but when designing, we still need to avoid over-design.

For example, the following summary information, combined, will find that there is a problem with some of the metadata information. And the master-slave data is also some people, this through the previous way is not visible.

Data dictionary

In the part of the data dictionary, I didn't pay attention to it at first, but after I wrote it to a certain extent, I found that there were still many ways in it, so I added the content of this part.

Because some data dictionary information has iterative relationship, the current display is only the record of iterative relationship, and visualization needs to be further strengthened. For example, the effect is obviously better when viewing it in the following way. This is also where we spend some time preparing for improvement these days. If you want to make a table similar to the following, the hierarchical relationship will be very clear.

Menu permissions for the user

At present, the dynamic menu is used, and I have considered a further step in this granularity, that is, a page has the function of adding, deleting, modifying and querying, and we can do fine-grained permission division, which can not be done by the existing permission, and that can only be achieved at the table level, and we hope to be finer. In this way, the permissions of the menu can be more detailed, if some of the business is open to business students, read-only access is sufficient.

Control granularity of permissions

If the granularity of permissions is more detailed, we still need to do some verification. For example, we have servers in the direction of MySQL and Redis, and the metadata is all in the same entry. If I don't want to see the server information of Redis, I can control it in a way similar to roles or groups. In this way, all I can see on the same page is the information of MySQL. If the permission is large enough, I will see more.

Backup check

Development specification design document

I have also precipitated some ideas in this respect, and I am going to write a version to unify some styles and design ideas.

The above is the content of this article on "what is the design method of metadata for web automation platform development". I believe we all have a certain understanding. I hope the content shared by the editor will be helpful to you. If you want to know more about the relevant knowledge, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.