CN114443120A - Intelligent embedded point management system and method - Google Patents

Intelligent embedded point management system and method Download PDF

Info

Publication number
CN114443120A
CN114443120A CN202111677808.XA CN202111677808A CN114443120A CN 114443120 A CN114443120 A CN 114443120A CN 202111677808 A CN202111677808 A CN 202111677808A CN 114443120 A CN114443120 A CN 114443120A
Authority
CN
China
Prior art keywords
page
buried point
sub
event
point event
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111677808.XA
Other languages
Chinese (zh)
Inventor
张聪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jinbaobei Network Technology Suzhou Co ltd
Original Assignee
Jinbaobei Network Technology Suzhou Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jinbaobei Network Technology Suzhou Co ltd filed Critical Jinbaobei Network Technology Suzhou Co ltd
Priority to CN202111677808.XA priority Critical patent/CN114443120A/en
Publication of CN114443120A publication Critical patent/CN114443120A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Computational Linguistics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention belongs to the technical field of data acquisition and data analysis, and provides an intelligent embedded point management system and method, which comprises the following steps: when a new version command is received, obtaining version data of a historical page to update the version data of the current page; when a modified page is received, checking whether the metadata of the modified page is the same as the metadata of the current page, and when the metadata of the modified page is different from the metadata of the current page, adding the modified page into the current page; when a buried point modification event is received, if the buried point modification event is different from the buried point modification event of the current page, adding a buried point modification event in the current page; and when the buried point event name is received, constructing a query statement according to the buried point event name, so that the total number of the current day of the corresponding buried point event which is queried is displayed in the buried point event document. By adding the version, the page and changing the new version, the embedded point document is more three-dimensional, the existing data is better analyzed and controlled, and new embedded point requirements are increased.

Description

Intelligent embedded point management system and method
Technical Field
The invention relates to the technical field of data acquisition and data analysis, in particular to an intelligent embedded point management system and method.
Background
A service site refers to a collection of specific behaviors of a class of users when using APP so that an enterprise can better serve the users, for example: the user has clicked a certain button. The burial points are iterated along with the APP version, and the product defines which burial points are needed, and development needs to realize the logics according to documents. Moreover, because version iteration leads to more and more buried points, and a phenomenon of missing errors often occurs during development and implementation, how to reduce the errors in a buried point system becomes a problem to be solved urgently.
Developers hope to see new or modified buried points of a new version compared with an old version, while the product and data analysis and college theory better focuses on which buried points exist in a certain module of a current version, and the current document system on the market cannot simultaneously solve the two pain points.
Disclosure of Invention
The invention provides an intelligent embedded point management method and system, which solve the problems.
The technical scheme provided by the invention is as follows:
an intelligent site-burying management system, comprising:
the new version module is used for acquiring version data of the historical page when a new version instruction is received so as to update the version data of the current page; the version data comprises metadata and a buried point event of a page;
the new modified page module is used for checking whether the metadata of the modified page is the same as the metadata of the current page or not when the modified page is received, and adding the modified page to the current page when the metadata of the modified page is different from the metadata of the current page;
the newly-added modified buried point module is used for receiving a modified buried point event, and if the modified buried point event is different from the buried point event of the current page, newly adding a modified buried point event on the current page;
and the buried point checking module is used for constructing a query statement according to the buried point event name when the buried point event name is received, so that the total number of the current day of the corresponding buried point event which is queried is displayed in the buried point event document.
Further preferably, the method further comprises the following steps:
and the display judging module is used for comparing the version data of the current page with the version data of the historical page when the current page receives a click instruction, and displaying that different target version data exist in the version data of the current page and the version data of the historical page.
Further preferably, the display determination module is further configured to:
the page traversal submodule is used for traversing metadata of each sub-page in the current page, and if the sub-page does not exist in the historical page, the sub-page is a newly added page;
and the buried point traversing submodule is used for traversing the buried point event of the sub-page if the sub-page exists in the historical page.
Further preferably, the buried point traversal submodule is further configured to:
if the buried point event of the sub-page does not appear in the corresponding historical page, the buried point event of the sub-page is a newly added buried point event, and the newly added buried point event is placed into the sub-page;
if the embedded point event of the sub-page occurs in the corresponding historical page and the fields are inconsistent, the embedded point event of the sub-page is a modified embedded point event, and the modified embedded point event is put into the sub-page;
and if the embedded point event of the sub-page appears in the corresponding historical page and the fields are consistent, the embedded point event of the sub-page is not modified, and the embedded point event of the sub-page is skipped.
Further preferably, the method further comprises the following steps:
and the global keyword searching module is used for querying the database according to the version keywords to obtain corresponding version data when the version keywords are received.
Further preferably, the global keyword search module is further configured to:
traversing metadata of each sub-page in the current page, and if the sub-page is matched with the keyword, putting the sub-page into a search result page;
if the sub-page is not matched with the keyword, traversing the buried point event of the sub-page;
if the buried point event of the sub-page is matched with the keyword, the buried point event of the sub-page is placed into the sub-page;
and if the buried point event of the sub-page is not matched with the keyword, skipping the buried point event of the sub-page.
Further preferably, the method further comprises the following steps:
and the page classification and sorting module is used for setting corresponding priority according to the relevance degree of the metadata of each sub-page in the current page when the current page is displayed, and classifying and sorting the sub-pages based on the priority.
Further preferably, the page classification and sorting module is further configured to:
and setting a priority field of a digital type in the metadata of each sub-page, and sequencing and returning the sub-pages according to the priority field when a result is returned.
Further preferably, it comprises:
and the storage module is used for storing the metadata of the current page, the embedded point event of the current page, the metadata of the modified page, the modified embedded point event and the correlation degree data of the sub-page.
An intelligent site burying management method comprises the following steps:
when a new version instruction is received, obtaining version data of a historical page to update the version data of a current page; the version data comprises metadata and a buried point event of a page;
when a modified page is received, checking whether the metadata of the modified page is the same as the metadata of the current page, and when the metadata of the modified page is different from the metadata of the current page, adding the modified page to the current page;
when a modified buried point event is received, if the modified buried point event is different from the buried point event of the current page, adding a modified buried point event in the current page;
and when the buried point event name is received, constructing a query statement according to the buried point event name so that the total number of the current day of the corresponding buried point event which is queried is displayed in the buried point event document.
The intelligent embedded point management method and system provided by the invention at least have the following beneficial effects:
1) and the structured data storage provides possibility for automatic buried point check and big data integration. The version, the page and the new version change three visual angles to enable the buried point document to be more three-dimensional, the existing data can be better analyzed and controlled by the product and the data colleagues, new buried point requirements are added, and development students can more clearly see the requirements of the new version change on the buried points without interference.
2) Global searching is more convenient and useful than traditional document tools.
3) When newly added and modified, the existing data can be compared, the generation of repeated event pages is avoided, and the occurrence of inconsistent event definitions before and after the generation is prevented.
Drawings
The invention is described in further detail below with reference to the following figures and detailed description:
FIG. 1 is a schematic diagram of one embodiment of an intelligent site management system of the present invention;
FIG. 2 is a schematic view of an interface according to the present invention;
FIG. 3 is a schematic diagram of one embodiment of an intelligent site management system of the present invention;
FIG. 4 is a schematic diagram of one embodiment of an intelligent site management system of the present invention;
FIG. 5 is a schematic diagram of one embodiment of an intelligent site management system of the present invention;
FIG. 6 is a schematic diagram of one embodiment of an intelligent site management system of the present invention;
FIG. 7 is a schematic diagram of one embodiment of an intelligent site management method of the present invention;
FIG. 8 is a schematic diagram showing the logic performed by the judgment module in accordance with the present invention;
FIG. 9 is a diagram of the global keyword search module execution logic of the present invention.
Detailed Description
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
For the sake of simplicity, the drawings only schematically show the parts relevant to the present invention, and they do not represent the actual structure as a product. In addition, in order to make the drawings concise and understandable, components having the same structure or function in some of the drawings are only schematically illustrated or only labeled. In this document, "one" means not only "only one" but also a case of "more than one".
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
In this context, it is to be understood that, unless otherwise explicitly stated or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
In addition, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not intended to indicate or imply relative importance.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will be made with reference to the accompanying drawings. It is obvious that the drawings in the following description are only some examples of the invention, and that for a person skilled in the art, other drawings and embodiments can be derived from them without inventive effort.
It should be noted that, in order to better explain the technical solution of the present invention, the following concepts are explained:
version: corresponding to the product iteration versions, each product version should establish a corresponding version of the buried point document, for example: appv5.1. contains multiple pages.
Page: corresponding to APP or H5 page, a page representing some actually existing application function, for example: APP personal center page. The page contains a plurality of buried point events.
A buried point event: the method really needs to be developed and implemented corresponding to certain user behaviors needing to be recorded, such as: the user clicks on a shopping cart button event. The buried point event document comprises an event name, a description, a parameter description and a schematic picture.
The whole system of the invention is a document system which comprises a plurality of functional modules, wherein the product uses the functional modules such as newly-built page editing embedded points, and the development uses the functional modules for checking the new version and comparing the upper version. By the method, the product and data users can better analyze and control the existing data, new embedded point requirements are added, and development users can more clearly see the requirements of the new version for changing the related embedded points without interference.
The invention provides an embodiment of an intelligent embedded point management system, as shown in fig. 1, specifically including:
the new version module 100 is configured to, when a new version instruction is received, obtain version data of a historical page to update the version data of a current page; the version data comprises metadata and a buried point event of the page.
Specifically, since the buried point requirement is also part of the version requirement, iteration is also performed; the buried point is often defined again according to the APP function page or module, for example: the user clicks a button in the center of the person.
Therefore, the new module provided by the embodiment can realize the document viewing from the three new views of the version, the page and the new version.
The embedded point system can be subjected to programmed inspection to reduce errors such as more and more embedded points caused by version iteration, and missing errors frequently occur during development and implementation.
The new version module is used for the new version to inherit the data of the previous version: inheriting the previous version data to generate a same new version, and then adding and changing the current version buried point event by using the following related functions in the same school.
When a new version is built, inquiring a database, and if no historical version exists, building a new empty version; if the historical version exists, all data of the historical version is copied to the new version (the data is stored by adopting mongodb which is a database; the copying to the new version is equivalent to adding related records in the database.)
A modified page adding module 200, configured to check whether the metadata of the modified page is the same as the metadata of the current page when the modified page is received, and add the modified page to the current page when the metadata of the modified page is different from the metadata of the current page.
The method specifically comprises the steps of adding a new modified page, persisting the operation of the new modified page into a database on the basis of a certain version, checking existing data during new modification, and rejecting the operation when repetition occurs.
The newly added modified buried point module 300 is configured to, when a modified buried point event is received, add a modified buried point event to the current page if the modified buried point event is different from the buried point event of the current page.
Specifically, the newly added modified page embedded point persists the newly added modified embedded point operation to the database on the basis of a certain page. The new modification will verify the existing data and the operation will be rejected when repetition occurs.
And the buried point checking module 400 is configured to, when the buried point event name is received, construct an inquiry statement according to the buried point event name, so that the total number of the current day of the corresponding buried point event which is inquired is displayed in the buried point event document.
And (4) performing intelligent check on the buried points, constructing query conditions according to document definition, and querying an Ariiyun API (application programming interface) to obtain corresponding buried point entry data. Among them, an API (Application Programming Interface).
For intelligent embedded point verification, on the basis of a certain page of a certain version, all embedded point event information of the page can be searched from a database, a query statement is constructed according to an event name, and the total number of the current day of a corresponding event is searched and returned to the front end to be displayed in an event document. The intelligent buried point verification is to display the buried point data in a document system.
The system of the embodiment is a buried point document system, and defines buried point requirements around products and develops and views the buried point requirements.
Generally, the embodiment is a background system, so the program includes a front-end interface and a back-end program, and the embodiment focuses on the correlation of the back-end program. Fig. 2 is a front end interface of the present embodiment.
In the embodiment, the version, the page and the new version change three visual angles to enable the embedded point document to be more three-dimensional, the existing data can be better analyzed and controlled by products and data colleagues, new embedded point requirements are added, and development classmates can more clearly see the requirements of the new version change on the relevant embedded points without interference. Global searching is more convenient and useful than traditional document tools. When newly added and modified, the existing data can be compared, the generation of repeated event pages is avoided, and the occurrence of inconsistent event definitions is prevented.
Example two
Based on the foregoing embodiment, parts of the present embodiment that are the same as those of the foregoing embodiment are not repeated, and this embodiment provides an embodiment of an intelligent site burying management system, which specifically includes all modules in the first embodiment, where as shown in fig. 3, the method further includes:
the display determination module 500 is configured to compare the version data of the current page with the version data of the historical page when the current page receives a click instruction, and display that different target version data exists between the version data of the current page and the version data of the historical page.
The display judgment module further comprises:
the page traversal submodule is used for traversing metadata of each sub-page in the current page, and if the sub-page does not exist in the historical page, the sub-page is a newly added page;
and the buried point traversing submodule is used for traversing the buried point event of the sub-page if the sub-page exists in the historical page.
Wherein the buried point traversal submodule is further configured to:
if the buried point event of the sub-page does not appear in the corresponding historical page, the buried point event of the sub-page is a newly added buried point event, and the newly added buried point event is placed into the sub-page;
if the embedded point event of the sub-page occurs in the corresponding historical page and the fields are inconsistent, the embedded point event of the sub-page is a modified embedded point event, and the modified embedded point event is put into the sub-page;
and if the embedded point event of the sub-page appears in the corresponding historical page and the fields are consistent, the embedded point event of the sub-page is not modified, and the embedded point event of the sub-page is skipped.
Illustratively, only data that changes from the current version to the previous version is displayed: this logic is executed when the user clicks on the background page to only show buried points that vary from the previous version:
the database is queried for all data for the respective two versions (current version a, last version b), and the comparison is made according to the following logic:
1) and c, traversing the page of the a:
the page a1 does not appear in the b version, a1 is a newly added page, and a1 is placed into the result page;
page a2 exists in version b (b2), continuing to compare page events.
2) Traverse a2 page event:
the event ae1 does not appear on the b2 page, ae1 is a newly added event, and ae1 is placed in an a2 page event;
the event ae2 appears on the b2 page and the fields are not consistent, ae2 is modified, and ae2 is placed in the a2 page event;
the event ae3 appears on the b2 page and has the same field, ae3 is not modified, and the ae3 event is skipped;
according to the above logic, the returned data (pseudo code schematic) is { pages: [ a1, a 2: { events: [ ae1, ae2] }.
In the embodiment, the display judgment module is additionally arranged, so that the product and data colleagues can better analyze and control the existing data, new embedded point requirements are added, and development classmates can more clearly see the requirements of the new version for changing the relevant embedded points without interference.
EXAMPLE III
Based on the foregoing embodiment, parts in this embodiment that are the same as those in the foregoing embodiment are not repeated, and this embodiment provides an embodiment of an intelligent site burying management system, which specifically includes: as shown in fig. 4, all modules of embodiment one; or; as shown in fig. 5, all modules in the first embodiment and the second embodiment further include:
and the global keyword search module 600 is configured to, when the version keyword is received, query the database according to the version keyword to obtain corresponding version data.
Specifically, the global keyword search module 600 is further configured to:
and traversing the metadata of each sub-page in the current page, and if the sub-page is matched with the keyword, putting the sub-page into a search result page.
And if the sub-page is not matched with the key words, traversing the buried point event of the sub-page.
And if the buried point event of the sub-page is matched with the keyword, putting the buried point event of the sub-page into the sub-page.
And if the buried point event of the sub-page is not matched with the keyword, skipping the buried point event of the sub-page.
Exemplary, global keyword search: the lower right input box in the page diagram shown in fig. 2 corresponds to the front page of this function.
Inquiring a database according to the specified version to obtain version data, and processing and searching according to the following logic:
1) and (3) traversing the page:
a) the page a1 metadata is matched with the search keyword, and a1 is wholly put into a result page;
b) page a2 metadata does not match the keywords and the search continues for page events of a 2.
2) Traverse a2 page event:
a) event ae1 metadata matches keywords, and ae1 is put into the a2 page event;
b) event ae2 metadata does not match keywords, skipping the ae2 event.
According to the above logic, the returned data (pseudo code schematic) is { pages: [ a1, a 2: { events:
[ae1]}]}。
in the embodiment, a global keyword search module is additionally arranged, so that version data can be conveniently searched through keywords, and global search is more convenient and better-used than a traditional document tool.
Example four
Based on the foregoing embodiment, parts in this embodiment that are the same as those in the foregoing embodiment are not repeated, and this embodiment provides an embodiment of an intelligent site burying management system, which specifically includes: as shown in fig. 6, all modules of embodiment one; or any combination of all the modules in the second embodiment and the third embodiment; wherein, still include:
and the page classification and sorting module 700 is configured to set a corresponding priority according to the degree of relevance of metadata of each sub-page in the current page when the current page is displayed, and perform classification and sorting on the sub-pages based on the priority.
Specifically, the page classification and sorting module is further configured to:
and setting a priority field of a digital type in the metadata of each sub-page, and sequencing and returning the sub-pages according to the priority field when a result is returned.
Illustratively, page sort order: the sequence is very important for the document, for example, related pages such as a children song course in the APP, details of the children song course and an album of the children song course need to be put together, and the development product can conveniently check related page embedded documents according to the APP function.
And setting a priority field of a digital type in each page metadata, and when a result is returned, always sequencing and returning the pages according to the priority field.
And the storage module is used for storing the metadata of the current page, the buried point event of the current page, the metadata of the modified page, the modified buried point event and the correlation degree data of the sub-pages.
In the embodiment, the intelligent buried point management system comprises a document background and an intelligent verification part. The document background is intended to create a clear, easy-to-maintain communication that can reduce the inefficiency between the product (document writer) and the development (implementing the burial points from the document). The intelligent verification can help development and test to improve the accuracy of the embedded point and reduce the error rate and the leakage rate.
The document background uses MongoDB as a database to store the data of the embedded point document, and the data level realizes the following functions:
the newly-built version inherits the data of the previous version, newly-added modified pages are added, points are buried in the newly-added modified pages, only the data of the current version and the data of the previous version which are changed are displayed, global keyword search is conducted, and the pages are sorted and sequenced. And (4) performing intelligent check on the buried points, constructing query conditions according to document definition, and querying an Ariiyun API (application programming interface) to obtain corresponding buried point entry data. Among them, an API (Application Programming Interface).
In the embodiment, the structured data storage provides possibility for automatic buried point check and big data integration. The version, the page and the new version change three visual angles to enable the buried point document to be more three-dimensional, the existing data can be better analyzed and controlled by the product and the data colleagues, new buried point requirements are added, and development students can more clearly see the requirements of the new version change on the buried points without interference. Global searching is more convenient and useful than traditional document tools. When newly added and modified, the existing data can be compared, the generation of repeated event pages is avoided, and the occurrence of inconsistent event definitions before and after the generation is prevented.
EXAMPLE five
Based on the foregoing embodiment, the same parts as those in the foregoing embodiment are not repeated in detail in this embodiment, and this embodiment provides an intelligent site burying management method, as shown in fig. 7, including:
s100, when a new version command is received, obtaining version data of a historical page to update the version data of a current page; the version data comprises metadata and a buried point event of the page.
S200, when a modified page is received, whether the metadata of the modified page is the same as the metadata of the current page is checked, and when the metadata of the modified page is different from the metadata of the current page, the modified page is added to the current page.
S300, when a modified buried point event is received, if the modified buried point event is different from the buried point event of the current page, adding a modified buried point event in the current page.
S400, when the buried point event name is received, a query statement is constructed according to the buried point event name, so that the total number of the current day of the corresponding buried point event which is queried is displayed in the buried point event document.
The steps do not have a sequence, are execution flows of different functions of the whole system, and can be directly used when a certain function is required to be used.
Example six
Based on the foregoing embodiment, parts in this embodiment that are the same as those in the foregoing embodiment are not repeated, and this embodiment provides an intelligent site burying management method, which may further include:
when the current page receives a click instruction, comparing the version data of the current page with the version data of the historical page, and displaying that different target version data exist in the version data of the current page and the version data of the historical page.
Preferably, when the current page receives a click instruction, comparing the version data of the current page with the version data of the historical page, and displaying that different target version data exists between the version data of the current page and the version data of the historical page, as shown in fig. 8, the method specifically includes:
s501, traversing metadata of each sub-page in the current page, and if the sub-page does not exist in the historical page, determining that the sub-page is a new page.
Specifically, a current page comprises a plurality of sub-pages, the specific content of each sub-page is different, but each sub-page quality inspection has correlation. Before a page is added, the newly added page needs to be checked to see whether the original page has the page or not, if so, the page is not added, and if not, the page is added.
In a specific scenario, when a version is updated, a page may need to be updated, but some pages may remain unchanged, so when a page is newly added, metadata of the page of the version is traversed, and whether the page needs to be newly added is determined.
S502, if the sub-page exists in the historical page, traversing the buried point event of the sub-page.
In S502, if the sub-page exists in the history page, traversing the buried point event of the sub-page specifically includes:
s5021, if the buried point event of the sub-page does not appear in the corresponding historical page, the buried point event of the sub-page is a newly added buried point event, and the newly added buried point event is placed into the sub-page.
S5022, if the embedded point event of the sub-page occurs in the corresponding historical page and the fields are not consistent, the embedded point event of the sub-page is modified, and the embedded point event of the sub-page is placed in the sub-page.
S5023, if the embedded point event of the sub-page occurs in the corresponding historical page and the fields are consistent, the embedded point event of the sub-page is not modified, and the embedded point event of the sub-page is skipped over.
The embodiment provides an intelligent site burying management method, which may further include:
and when the version keywords are received, querying a database according to the version keywords to obtain corresponding version data.
When the version keyword is received, querying the database according to the version keyword to obtain corresponding version data, as shown in fig. 9, specifically including:
s601, traversing metadata of each sub-page in the current page, and if the sub-page is matched with the keyword, putting the sub-page into a search result page.
S602, if the sub-page is not matched with the keyword, traversing the buried point event of the sub-page.
S603, if the buried point event of the sub-page is matched with the keyword, the buried point event of the sub-page is put into the sub-page.
S604, if the buried point event of the sub-page is not matched with the keyword, skipping the buried point event of the sub-page.
When the current page is displayed, setting corresponding priority according to the relevance degree of metadata of each sub-page in the current page, and sorting the sub-pages based on the priority.
Preferably, when the current page is displayed, setting a corresponding priority according to a degree of relevance of metadata of each sub-page in the current page, and sorting the sub-pages based on the priority, specifically including:
and setting a priority field of a digital type in the metadata of each sub-page, and sequencing and returning the sub-pages according to the priority field when a result is returned.
The intelligent embedded point management method provided by the invention at least has the following beneficial effects: and the structured data storage provides possibility for automatic buried point check and big data integration. The version, the page and the new version change three visual angles to enable the buried point document to be more three-dimensional, the existing data can be better analyzed and controlled by the product and the data colleagues, new buried point requirements are added, and development students can more clearly see the requirements of the new version change on the buried points without interference. Global searching is more convenient and useful than traditional document tools. When newly added and modified, the existing data can be compared, the generation of repeated event pages is avoided, and the occurrence of inconsistent event definitions is prevented.
In the foregoing embodiments, the descriptions of the respective embodiments have their respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or recited in detail in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed system and method may be implemented in other ways. The above-described system embodiments are merely exemplary, and it is exemplary that the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, and it is exemplary that a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units may be stored in a storage medium if they are implemented in the form of software functional units and sold or used as separate products. It should be noted that the storage medium may contain contents that are appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction, and for example, in some jurisdictions, the computer-readable storage medium does not include electrical carrier signals and telecommunication signals according to legislation and patent practice.
It should be noted that the above embodiments can be freely combined as necessary. The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims (10)

1. An intelligent point burying management system is characterized by comprising:
the new version module is used for acquiring version data of the historical page when a new version instruction is received so as to update the version data of the current page; the version data comprises metadata and a buried point event of a page;
the new modified page module is used for checking whether the metadata of the modified page is the same as the metadata of the current page or not when the modified page is received, and adding the modified page to the current page when the metadata of the modified page is different from the metadata of the current page;
the newly-added modified buried point module is used for receiving a modified buried point event, and if the modified buried point event is different from the buried point event of the current page, newly adding a modified buried point event on the current page;
and the buried point checking module is used for constructing a query statement according to the buried point event name when the buried point event name is received, so that the total number of the current day of the corresponding buried point event which is queried is displayed in the buried point event document.
2. The intelligent site burying management system as recited in claim 1, further comprising:
and the display judging module is used for comparing the version data of the current page with the version data of the historical page when the current page receives a click instruction, and displaying that different target version data exist in the version data of the current page and the version data of the historical page.
3. The intelligent embedded point management system of claim 2, wherein the display determination module further comprises:
the page traversal submodule is used for traversing metadata of each sub-page in the current page, and if the sub-page does not exist in the historical page, the sub-page is a newly added page;
and the buried point traversing submodule is used for traversing the buried point event of the sub-page if the sub-page exists in the historical page.
4. The intelligent buried point management system of claim 3, wherein the buried point traversal submodule is further configured to:
if the buried point event of the sub-page does not appear in the corresponding historical page, the buried point event of the sub-page is a newly added buried point event, and the newly added buried point event is placed into the sub-page;
if the embedded point event of the sub-page occurs in the corresponding historical page and the fields are inconsistent, the embedded point event of the sub-page is a modified embedded point event, and the modified embedded point event is put into the sub-page;
and if the embedded point event of the sub-page appears in the corresponding historical page and the fields are consistent, the embedded point event of the sub-page is not modified, and the embedded point event of the sub-page is skipped.
5. The intelligent site burying management system as recited in claim 1, further comprising:
and the global keyword searching module is used for querying the database according to the version keywords to acquire corresponding version data when the version keywords are received.
6. The intelligent site burying management system as recited in claim 5, wherein said global keyword search module is further configured to:
traversing metadata of each sub-page in the current page, and if the sub-page is matched with the keyword, putting the sub-page into a search result page;
if the sub-page is not matched with the keyword, traversing the buried point event of the sub-page;
if the buried point event of the sub-page is matched with the keyword, putting the buried point event of the sub-page into the sub-page;
and if the buried point event of the sub-page is not matched with the keyword, skipping the buried point event of the sub-page.
7. The intelligent site burying management system as recited in claim 1, further comprising:
and the page classification and sorting module is used for setting corresponding priority according to the relevance degree of the metadata of each sub-page in the current page when the current page is displayed, and classifying and sorting the sub-pages based on the priority.
8. The intelligent site burying management system as recited in claim 7, wherein said page classification ordering module is further configured to:
and setting a priority field of a digital type in the metadata of each sub-page, and sequencing and returning the sub-pages according to the priority field when a result is returned.
9. The intelligent site burying management system as claimed in any one of claims 1-8, comprising:
and the storage module is used for storing the metadata of the current page, the buried point event of the current page, the metadata of the modified page, the modified buried point event and the correlation degree data of the sub-pages.
10. An intelligent embedded point management method is characterized by comprising the following steps:
when a new version command is received, obtaining version data of a historical page to update the version data of the current page; the version data comprises metadata and a buried point event of a page;
when a modified page is received, checking whether the metadata of the modified page is the same as the metadata of the current page, and when the metadata of the modified page is different from the metadata of the current page, adding the modified page to the current page;
when a buried point modification event is received, if the buried point modification event is different from the buried point event of the current page, adding a buried point modification event in the current page;
and when the buried point event name is received, constructing a query statement according to the buried point event name so that the total daily number of the queried corresponding buried point event is displayed in the buried point event document.
CN202111677808.XA 2021-12-31 2021-12-31 Intelligent embedded point management system and method Pending CN114443120A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111677808.XA CN114443120A (en) 2021-12-31 2021-12-31 Intelligent embedded point management system and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111677808.XA CN114443120A (en) 2021-12-31 2021-12-31 Intelligent embedded point management system and method

Publications (1)

Publication Number Publication Date
CN114443120A true CN114443120A (en) 2022-05-06

Family

ID=81366224

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111677808.XA Pending CN114443120A (en) 2021-12-31 2021-12-31 Intelligent embedded point management system and method

Country Status (1)

Country Link
CN (1) CN114443120A (en)

Similar Documents

Publication Publication Date Title
US9020906B2 (en) Method for intelligent storing and retrieving in an enterprise data system
US7912816B2 (en) Adaptive archive data management
TWI223171B (en) System for classifying files of non-textual subject data, method for categorizing files of non-textual data and method for identifying a class for data file at a classification node
US11100469B2 (en) Cross-domain collaborative data log
KR20060054281A (en) System and method for electronically managing discovery pleading information
FR2888018A1 (en) METHOD AND SYSTEM FOR REALIZING A VIRTUAL DATABASE FROM DATA SOURCES HAVING HETEROGENEOUS SCHEMES
US20220035847A1 (en) Information retrieval
US20030225761A1 (en) System for managing and searching links
CN109241107A (en) Big data controlling device based on Hadoop
CN106095738A (en) Recommendation tables single slice
CN104750776A (en) Accessing information content in a database platform using metadata
EP1622042A1 (en) Database device, database search device, and method thereof
CN104182459A (en) System and method for presenting content to a user
CN111061733B (en) Data processing method, device, electronic equipment and computer readable storage medium
US7827153B2 (en) System and method to perform bulk operation database cleanup
US20210382885A1 (en) Collaborating using different object models
Brilakis et al. Multimodal image retrieval from construction databases and model-based systems
CN114443120A (en) Intelligent embedded point management system and method
CN109614467B (en) Knowledge association and dynamic organization method and system based on fragment similarity
US20130013613A1 (en) Structured requirements management
CN117009588A (en) Three-dimensional data association retrieval method based on knowledge graph
Masinde et al. A Knowledge Resource Management System (KRMS) for the Academic Community.
US11436220B1 (en) Automated, configurable and extensible digital asset curation tool
RU2479017C1 (en) System for analytical detection of problematic issues in legal regulation standards
US20140149655A1 (en) Narrowing Comparison Results of Associative Memories

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination