Note: Descriptions are shown in the official language in which they were submitted.
DATA COLLECTING METHOD, DEVICE, COMPUTER EQUIPMENT AND
STORAGE MEDIUM
BACKGROUND OF THE INVENTION
Technical Field
[0001] The present application relates to the field of big data analysis, and
more particularly to a
data collecting method, and corresponding device, computer equipment and
storage
medium.
Description of Related Art
[0002] With the internal data collection requirements of such various
professions and fields as
enterprises, schools and government offices, different forms should be
customized under
different scenarios (such as travel registrations, parking lot registrations,
etc.) to be
dispatched to various departments, and the forms are filled in by the various
departments
for subsequent summarization and statistics, the workload for such data
collecting process
is massive. Since the formats of the forms required by different scenarios are
different, the
developing personnel would develop corresponding forms with respect to the
different
scenarios, but such customized development of forms makes it impossible for
users to
convenient extend data collected by the forms, and storage of different form
data also
causes wastage of data storage space.
SUMMARY OF THE INVENTION
[0003] In view of the deficiencies prevailing in the state of the art, the
present invention provides
a data collecting method, and corresponding device, computer equipment and
storage
medium, and embodiments of the present invention facilitate the user to extend
data
collected by the form, and utilization rate of data storage space can be
enhanced when form
1
Date Recue/Date Received 2022-02-21
data is stored.
[0004] According to the first aspect, the present invention provides a data
collecting method, and
the method comprises, in one embodiment:
[0005] receiving a form obtaining request sent by a first client end;
[0006] obtaining target form definitive data to which the form obtaining
request corresponds from
first preset nested-type fields of a relational database;
[0007] sending the target form definitive data to the first client end to
instruct the first client end
to present a form fill-in page according to the target form definitive data;
[0008] receiving form data collected by the first client end through the form
fill-in page and
submitted by the first client end; and
[0009] storing the form data as a document into a document database.
[0010] In one embodiment, the step of storing the form data as a document into
a document
database includes:
[0011] recognizing data types of various pieces of form control data included
in the form data, and
storing the various pieces of form control data into second preset nested-type
fields
corresponding to the data types of the various pieces of form control data in
the document
database.
[0012] In one embodiment, the data types of the form control data are
character string, date and
long type, the first preset nested-type fields are JSON nested fields, and the
second preset
nested-type fields are nested fields.
[0013] In one embodiment, prior to the step of receiving a form obtaining
request sent by a first
client end, the method further comprises:
[0014] providing a form creating page to a form creating user through a second
client end;
2
Date Recue/Date Received 2022-02-21
[0015] receiving the target form definitive data submitted by the second
client end, wherein the
target form definitive data is generated by the second client end based on an
operation of
the form creating user in the form creating page, by identifying each form
control selected
thereby for creating a form, obtaining form descriptive data configured
thereby and control
configuration data configured thereby for each form control, and according to
the form
descriptive data and the control configuration data to which each form control
corresponds;
and
[0016] storing the form definitive data into the first preset nested-type
fields of the relational
database.
[0017] In one embodiment, the method further comprises: establishing index for
all form data of
each form stored in the document database;
[0018] the step of establishing index for all form data of each form stored in
the document database
includes:
[0019] employing a tokenizer to perform a tokenizing process on all form data
of each form in the
document database to obtain a plurality of tokens;
[0020] employing a language processor to linguistically process each token to
obtain a plurality
of terms; and
[0021] employing an indexer to create a document chain table based on the
plural terms to obtain
an index to which each form corresponds.
[0022] In one embodiment, the method further comprises:
[0023] receiving a form enquiring request submitted by the second client end,
wherein the form
enquiring request contains a query statement;
[0024] obtaining a target document to which the form enquiring request
corresponds from the
document database; and
[0025] generating an enquiring result according to the target document and
returning the enquiring
3
Date Recue/Date Received 2022-02-21
result to the second client end.
[0026] In one embodiment, the step of obtaining a target document to which the
form enquiring
request corresponds from the document database includes:
[0027] performing syntactic analysis and linguistic analysis on the query
statement to obtain a
syntax tree consisting of a series of terms;
[0028] searching for a pre-created index according to the syntax tree, and
obtaining a document
chain table to which each term in the syntax tree corresponds;
[0029] performing intersecting and excepting processes on all document chain
tables as obtained,
and obtaining a resultant document chain table;
[0030] calculating relevancy between each document associated with the
resultant document chain
table and the query statement; and
[0031] obtaining a document whose relevancy satisfies a preset condition from
all documents
associated with the resultant document chain table.
[0032] According to the second aspect, the present invention provides a data
collecting device,
and the device comprises, in one embodiment:
[0033] a first request receiving module, for receiving a form obtaining
request sent by a first client
end;
[0034] a definitive data obtaining module, for obtaining target form
definitive data to which the
form obtaining request corresponds from first preset nested-type fields of a
relational
database;
[0035] a definitive data sending module, for sending the target form
definitive data to the first
client end to instruct the first client end to present a form fill-in page
according to the target
form definitive data;
[0036] a form data receiving module, for receiving form data collected by the
first client end
through the form fill-in page and submitted by the first client end; and
4
Date Recue/Date Received 2022-02-21
[0037] a form data storing module, for storing the form data as a document
into a document
database.
[0038] According to the third aspect, the present invention provides a
computer equipment that
comprises a memory, a processor and a computer program stored on the memory
and
operable on the processor, and the steps of the embodiments of any
aforementioned method
are realized when the processor executes the computer program.
[0039] According to the fourth aspect, the present invention provides a
computer-readable storage
medium storing a computer program thereon, and the steps of the embodiments of
any
aforementioned method are realized when the computer program is executed by a
processor.
[0040] In the embodiments of the present invention, having received the form
obtaining request
sent by the first client end, the server end obtains target form definitive
data to which the
form obtaining request corresponds from the first preset nested-type fields of
the relational
database, and sends the target form definitive data to the first client end to
instruct the first
client end to present a form fill-in page according to the target form
definitive data, after
form data collected through the form fill-in page and submitted by the first
client end has
been received, the form data is stored in the document database as a document.
Complicated object types of a relational database are used in the embodiments
of the
present invention to store form structures, whereby it is made convenient for
the user to
extend data collected by the form, while the use of a non-relational database
to store the
form data makes it possible to enhance utilization rate of data storage space
when the form
data is stored.
BRIEF DESCRIPTION OF THE DRAWINGS
[0041] Fig. 1 is a view illustrating an application environment for a data
collecting method in an
Date Recue/Date Received 2022-02-21
embodiment;
[0042] Fig. 2 is a flowchart schematically illustrating a data collecting
method in an embodiment;
[0043] Fig. 3 is a view schematically illustrating form data in an embodiment;
[0044] Fig. 4 is a flowchart schematically illustrating a data collecting
method in another
embodiment;
[0045] Fig. 5 is a view schematically illustrating a form creating page in an
embodiment;
[0046] Fig. 6-a is a view schematically illustrating partial form controls in
an embodiment;
[0047] Fig. 6-b is a view schematically illustrating control definitive data
of a form control in Fig.
6-a;
[0048] Fig. 7 is a flowchart schematically illustrating document storage in an
embodiment;
[0049] Fig. 8 is a flowchart schematically illustrating establishing and
searching for index in an
embodiment;
[0050] Fig. 9 is a block diagram illustrating the structure of a data
collecting device in an
embodiment; and
[0051] Fig. 10 is a view illustrating the internal structure of a computer
equipment in an
embodiment.
DETAILED DESCRIPTION OF THE INVENTION
6
Date Recue/Date Received 2022-02-21
[0052] To make more lucid and clear the objectives, technical solutions and
advantages of the
present application, the present application is described in greater detail
below with
reference to accompanying drawings and embodiments. As should be understood,
the
specific embodiments as described here are merely meant to explain the present
application,
rather than to restrict the present application.
[0053] As shown in Fig. 1 is an application environment for a data collecting
method in an
embodiment of the present invention. In Fig. 1, reference numeral 10 indicates
a first client
end, 20 indicates a server end, a form filling-in user can send a form
obtaining request to
server end 20 via first client end 10, on receiving the form obtaining
request, server end 20
obtains form definitive data to which the form obtaining request corresponds
from a
relational database, for instance, the request carries therewith a form unique
identification,
and server end 20 obtains form definitive data corresponding to the form
unique
identification from the relational database and returns the data to first
client end 10,
whereupon first client end 10 can present to the user a form fill-in page
corresponding to
the form unique identification; after the user of the first client end has
filled in the form at
the form fill-in page, the first client end generates form data based on the
operation of the
user and sends the same to server end 20, and server end 20 will store the
form data into a
document database. Reference numeral 30 in Fig. 1 indicates a second client
end, the form
creating user can establish connection with server end 20 via the second
client end to obtain
a form creating page, and thereafter create a form through the form creating
page, the
second client end bases on the operation of the user in the form creating page
to generate
form definitive data and sends the data to server end 20, and server end 20
will store the
form definitive data into the relational database.
[0054] First client end 10 and second client end 30 can each be, but are not
limited to be, any of
various personal computers, notebook computers, smart mobile phones, panel
computers
7
Date Recue/Date Received 2022-02-21
and desktop computers, and server 20 can be embodied as an independent server
or a server
cluster consisting of a plurality of servers.
[0055] The present invention provides a data collecting method, and the method
is explained
below with an example of its being applied to the server end in Fig. 1. In one
embodiment,
as shown in Fig. 2, the method comprises the following steps.
[0056] S110 - receiving a form obtaining request sent by a first client end.
[0057] In this embodiment, any user needing to fill in a form can send a form
obtaining request to
the server end via the first client end, so as to obtain the relevant form
with which to fill in
relevant data. For instance, after a form creating user has created a form,
the relevant link
of the form can be shared with a user needing to fill in the form, and the
form filling-in
user accesses to the link via browser software installed in a smart terminal
(such as
computer, mobile phone, etc.) or software embedded with a browser to obtain a
form fill-
in page to which the relevant form corresponds, so that the form filling-in
user can fill
relevant data in the page.
[0058] In a certain scenario, one form can be assigned to plural users for
filling in, in other words,
there are many users needing to fill in the form, so the server end receives
form obtaining
requests coming from plural first client ends, but the server end processes
identically with
respect to any form obtaining request as received.
[0059] S120 - obtaining target form definitive data to which the form
obtaining request
corresponds from first preset nested-type fields of a relational database.
[0060] The relational database indicates a database that arranges data by
means of a relational
8
Date Recue/Date Received 2022-02-21
model, and stores data in the form of rows and columns; to facilitate
comprehension by
users, the series of rows and columns of a relational database is referred to
as a sheet, and
a set of sheets constitutes the database; the relational database employed in
this
embodiment can be a MySQL database, while the first preset nested-type fields
of the
relational database can be JSON nested fields.
[0061] S130 - sending the target form definitive data to the first client end
to instruct the first client
end to present a form fill-in page according to the target form definitive
data.
[0062] In this embodiment, having obtained the target form definitive data,
the server end sends
the data to the first client end, having received the target form definitive
data, the first client
end renders the form fill-in page on the basis of the target form definitive
data, and the
form fill-in page includes therein such various form controls as text boxes
and date boxes
in the relevant form.
[0063] S140 ¨ receiving form data collected by the first client end through
the form fill-in page
and submitted by the first client end.
[0064] In this embodiment, having filled data in the form fill-in page, the
form filling-in user can
issue a form data submitting instruction to the first client end, for
instance, the user can
click the "submit" button in the page to issue the instruction to the first
client end; in
response to the instruction, the first client end obtains the data filled by
the user in the page,
generates form data according to the obtained data, and sends the generated
form data to
the server end. Exemplarily, partial form data collected by a certain form can
be as shown
in Fig. 3, in which the fields of the data to be collected by the form are
"work number",
"plate number", "name", "location" and "expense", and the data of the various
fields are,
respectively, "10000001", "SU A00001", "Yan xuan", "Postgraduate 2" and "80".
9
Date Recue/Date Received 2022-02-21
[0065] As should be noted, partial or entire form controls in all the form
controls included in each
form can be designated as required to be filled or abbreviated as required
items, and it is
required for the form filling-in user to at least fill in all the required
items in the form before
the form data submitting instruction can be successfully issued to the first
client end.
Accordingly, the form control data included in the form data is not
necessarily the data to
which the entire form controls in the form correspond.
[0066] S150 - storing the form data as a document into a document database.
[0067] The relational database is usually used in the traditional technology
to store form data,
whereas a non-relational database is used in this embodiment to store form
data. The non-
relational database indicates a non-relational, distributed data storage
system that generally
is not necessarily ensured to abide by the ACID principle. The non-relational
database
stores with key-value pairs and its structure is not fixed, each tuple can
have different fields,
each tuple can be added with some key-value pairs of its own as required, it
is not restricted
to the fixed structure, and some temporal and spatial overhead is reduced.
What is
employed in this embodiment is a document database, such as MongoDB (a non-
relational
database based on distributed file storage), Elasticsearch (a search server
based on Lucene,
Elasticsearch supplies a total text search engine with distributed, multiple-
user capabilities)
to store collected form data. In comparison with the use of a relational
database to store
form data of yore, the use of a document database to store form data is
conducive to
reducing wastage of resources, in particular when the data volume of the form
data to be
stored is significantly large.
[0068] In one embodiment, prior to the step of receiving a form obtaining
request sent by a first
client end, step S100 is further comprised, namely a step of a form creating
user creating a
Date Recue/Date Received 2022-02-21
form;
[0069] Step S100 of a form creating user creating a form can include the
following steps as shown
in Fig. 4:
[0070] S101 - providing a form creating page to a form creating user through a
second client end;
[0071] S102 - receiving the target form definitive data submitted by the
second client end, wherein
the target form definitive data is generated by the second client end based on
an operation
of the form creating user in the form creating page, by identifying each form
control
selected thereby for creating a form, obtaining form descriptive data
configured thereby
and control configuration data configured thereby for each form control, and
according to
the form descriptive data and the control configuration data to which each
form control
corresponds; and
[0072] S103 - storing the form definitive data into the first preset nested-
type fields of the
relational database.
[0073] In prior-art technology, structures of forms used in different
scenarios are different, it is
therefore required for the developing personnel to develop different forms for
different
scenarios, but different forms share some identical portions, so a great deal
of repetitive
works is subsumed in the process of developing forms; moreover, in the form
design before,
there are too many contents stipulated between the client end and the server
end, this is not
a problem in the case the form is applied in few application scenarios, but in
the case the
form is applied in many application scenarios, it is required for the
developing personnel
to modify both the frontend and the backend due to change in application
scenarios of the
form.
[0074] Accordingly, this embodiment provides a more general and highly
effective form design in
view of the deficiencies in prior-art technology. In the present form design,
a dynamic form
structure is defined by the client end (such as a browser), while the server
end is only
11
Date Recue/Date Received 2022-02-21
responsible for the storage of the definitive data of the form structure but
does not
participate in the definition of the form structure, it is thusly made
possible to enhance the
robustness of the form design, reduce agreements between the client end and
the server
end, and reduce modifications to the frontend and the backend due to change in
scenarios.
[0075] In this embodiment, the form creating user can request a form creating
page from the server
end via the second client end, for instance, the user can access a relevant
link in browser
software installed in a smart terminal or software embedded with a browser to
establish
connection with the server end, and then request the form creating page from
the server
end via this link, whereupon the server end sends rendering data of the form
creating page
to the second client end in response to the request of the second client end,
so that the
second client end renders out the form creating page on the basis of the
rendering data.
[0076] In the form creating page are included many different types of basic
form controls (usable
only after attributes are defined), including, but not limited to, text input
box, dropdown
box, checkbox, radio button, automatic input box and date selection box, etc.,
the user can
select a basic form control required to be used in creating the form through
such operations
as dragging and/or clicking (it suffices for the second client end to identify
the form control
selected by the user by detecting the dragging and/or clicking operation(s) of
the user), and
define the attributes of the selected basic form control, for instance, the
user can define the
name of the form control, the data type of the data allowed for the user to
input to the form
control, and verification rule to the data input by the user, etc., so that a
useable form control
is generated. Of course, to facilitate use, in the form creating page can be
further included
a form control well predefined by the developing personnel at the server end
(hereinafter
abbreviated as "predefined control"), and the user can directly use this
predefined control
in the form creating page without having to firstly define the attributes of
the control,
whereby the efficiency for the user to create the form can be enhanced.
12
Date Recue/Date Received 2022-02-21
[0077] Exemplarily, a form creating page can be as shown in Fig. 5, the user
can drag the basic
form control supplied by the server end at the left side of the page to the
form design
window at the right side of the page through a dragging operation, and the
attributes of the
basic form control are defined in the window, so as to generate the form
control.
[0078] Having defined the entire form controls in the form, the user can issue
a form creating
instruction to the second client end (for instance, the user can click the
"release" button in
the form creating page to issue this instruction), in response to this
instruction, the second
client end obtains control identification information of form controls well
defined by the
user, configuration data (namely control configuration data) configured by the
user for each
form control selected by the user, and form descriptive data configured by the
user
(including, for instance, form name such as "Questionnaire on Annual Income",
and
including the number of copies allowed for the form to be filled in, such as
5000 copies
and/or the valid fill-in time period of the form, such as ending in February
28, 2021),
thereafter the second client end generates form definitive data according to
the data
obtained thereby and sends the same to the server end, whereupon, after having
received
the form definitive data, the server end stores the data into the first preset
nested-type fields
of the relational database, the form definitive data includes therein control
definitive data
of the various form controls in the form, when the control definitive data is
stored in the
relational database, it is also stored in the first preset nested-type fields
of the relational
database, as previously mentioned, the first preset nested-type fields of the
relational
database are JSON nested fields, and the storage of the control definitive
data in the JSON
nested fields makes it possible to very flexibly support horizontal extension
of the data
length and dynamic definition of the data structure, for instance, it is
supported after release
of the form for the user to modify the verification rules of certain fields
(one field in the
form is data collected by a form control, for example, the field "age" in the
form can be
13
Date Recue/Date Received 2022-02-21
collected by means of a single-line text box form control), the definitions of
field types and
the names of the fields in the form, etc. Exemplarily, what Fig. 6-a shows are
two form
controls well defined by the user in a certain form, the control definitive
data of these two
form controls can be as shown in Fig. 6-b, taking for example the first form
control, its
control definitive data includes 7 key-value pairs, of which the keys are to
the left (such as
"tip", "type", "value", "looktype"), and the values are to the right (such as
"please input",
"icon-danhang").
[0079] This embodiment can support the form creating user to dynamically set
up the attributes of
form controls through the client end (the second client end) to hence generate
the form
controls for collecting the data wanted by the user (for instance, the user
wants to collect
the two types of data, "height" and "age", of respondents, then the user can
define basic
form controls of the single-line text box type, so as to obtain a form control
specifically
used for collecting "age" data and a form control specifically used for
collecting "height"
data), it is thusly possible for the user, while creating the form, to freely
base on his own
requirements to generate any form control that satisfies his own requirements,
and the
number of form controls containable in the form is also not restricted,
whereby the user
can conveniently create forms for different scenarios through the second
client end.
[0080] In one embodiment, the step of storing the form data as a document into
a document
database includes: recognizing data types of various pieces of form control
data included
in the form data, and storing the various pieces of form control data into
second preset
nested-type fields corresponding to the data types of the various pieces of
form control data
in the document database.
[0081] In this embodiment, the data types of the form control data are
character string, date and
long type, the second preset nested-type fields in the document database are
nested fields,
14
Date Recue/Date Received 2022-02-21
and each data type of the form control data corresponds to one well predefined
nested field,
which can specifically be a nested field corresponding to character string
Keyword, date or
long type. In one mode of execution, data types of the data collected by the
form are only
the three types of character string, date and long type, and any
unidentifiable type as
encountered is stored in the form of character string.
[0082] In this embodiment, database complicated object types (namely JSON
nested fields and
nested fields) in the relational database and the document database are
merged, whereby
horizontal and longitudinal extensions of data collected by form controls can
be both
supported.
[0083] In one embodiment, the data collecting method further comprises:
establishing index for
all form data of each form stored in the document database.
[0084] When the data volume of the form data required to be collected is
relatively large, total text
index is established to enhance the data analyzing capability, that is to say,
an index is
established for all form data to which each form in the document database
corresponds to
enhance data enquiring efficiency, and hence enhance data analyzing
efficiency.
[0085] The step of establishing index for all form data of each form stored in
the document
database includes: employing a tokenizer to perform a tokenizing process on
all form data
of each form in the document database to obtain a plurality of tokens;
employing a language
processor to linguistically process each token to obtain a plurality of terms;
and employing
an indexer to create a document chain table based on the plural terms to
obtain an index to
which each form corresponds.
[0086] Exemplarily, the document storage mode can be as shown in Fig. 7, in
which Document
Date Recue/Date Received 2022-02-21
Frequency indicates how many documents contain a given term, and Frequency
indicates
how many terms are contained in a document numbered as Document ID. That is to
say,
while establishing index for each form, the server end can forward each
document of the
form (one piece of form data is a document in the document database) to a
tokenizer, and
the tokenizer splits the document into separate terms according to
punctuations and stop
words (namely semantically meaningless words, which are usually not taken as
search
keywords, but can be used as separators of words, such as "a" or "the" in the
English
language), the results of such tokenizing process can be referred to as
tokens.
[0087] Having completed the tokenizing process, the tokenizer passes the
tokens obtained thereby
to a language processor for a linguistic process, namely to process each term
to its root,
such as removing the plural suffix s from an English plural form, removing nal
from an
adjective (such processing can be made by reduction according to a fixed
algorithm), and
converting a tense to the present tense according to lexicographic knowledge.
The results
after processing by the language processor are referred to as terms.
[0088] Having completed the linguistic process, the language processor passes
its resultant terms
to an indexer, and the indexer creates document chain tables according to the
plural terms
it receives. Specifically, the indexer firstly creates the obtained terms as a
mapping
dictionary of character strings (a term is a character string) with document
IDs, thereafter
alphabetically sorts the character strings, and merges identical character
strings after
merging, so that a document inverted chain table is finally formed.
[0089] The server end in this embodiment disposes the entire data of each form
in the same index,
in which it is not required for the documents to have the same structure (or
scheme), the
inverted index provided by the server end is quicker in indexing speed than
the B-Tree in
a relational database, whereby enquiring efficiency is enhanced.
16
Date Recue/Date Received 2022-02-21
[0090] Based on the aforementioned embodiment of establishing an index, the
data collecting
method further comprises, in one embodiment:
[0091] receiving a form enquiring request submitted by the second client end,
wherein the form
enquiring request contains a query statement;
[0092] obtaining a target document to which the form enquiring request
corresponds from the
document database; and
[0093] generating an enquiring result according to the target document and
returning the enquiring
result to the second client end.
[0094] In this embodiment, when the form creating user needs to enquire
relevant form data, the
user can send a form enquiring request to the server end through the second
client end, and
the server end will search the document database based on the query statement
in the form
enquiring request to obtain the relevant target document, generate an
enquiring result
according to the target document and send the result to the second client end.
For instance,
if the user wants to enquire the proportion of males in all the people that
filled in the form,
all documents with the gender field being male can be searched out, the number
of the
documents is calculated, and the male proportion enquired by the user can be
obtained by
dividing this number by the total number of the documents.
[0095] The step of obtaining a target document to which the form enquiring
request corresponds
from the document database includes: performing syntactic analysis and
linguistic analysis
on the query statement to obtain a syntax tree consisting of a series of
terms; searching for
a pre-created index according to the syntax tree, and obtaining a document
chain table to
which each term in the syntax tree corresponds; performing intersecting and
excepting
processes on all document chain tables as obtained, and obtaining a resultant
document
chain table; calculating relevancy between each document associated with the
resultant
17
Date Recue/Date Received 2022-02-21
document chain table and the query statement; and taking a document whose
relevancy
satisfies a preset condition from all documents associated with the resultant
document
chain table.
[0096] The enquiring process can be as shown in Fig. 8. Specifically, the user
inputs the query
statement at the second client end, the second client end sends the query
statement to the
server end, and the server end performs syntactic analysis and linguistic
analysis on the
query statement, whereby a series of terms can be analyzed and obtained; a
syntax tree
(containing plural terms) can be obtained by the syntactic analysis of the
query statement,
the index is subsequently read in the memory through index storage, the index
is thereafter
searched on the basis of the syntax tree to obtain a document chain table to
which each
term corresponds, and the document chain tables obtained by searching are
subjected to
intersecting and excepting processes to thereby obtain a resultant document
chain table.
Each document chain table is associated with plural documents, it is therefore
required to
further calculate the relevancy between each document associated with the
resultant
document chain table and the query statement, after the corresponding
relevancy of each
document has been calculated, sorting can be performed based on the
intensities (or
magnitudes) of the relevancies, and those documents that satisfy the preset
condition are
subsequently obtained to serve as target documents. The preset condition can
be that the
value of the relevancy exceeds a preset threshold, then the document with such
relevancy
can be taken as a target document, while it is further possible to obtain a
preset threshold
number of documents with most intense relevancies after sorting to serve as
target
documents.
[0097] Moreover, the document database employed in this embodiment can be
preferably
embodied as Elasticsearch, because this database possesses total text
searching function, it
is therefore possible to establish the index directly on the basis of the
total text searching
18
Date Recue/Date Received 2022-02-21
function of the database, without having to seek for the help of (such as to
hire) other search
engines, and the enquiring efficiency is also enhanced during subsequent query
of
documents.
[0098] Figs. 2 and 4 are each a flowchart schematically illustrating a data
collecting method in an
embodiment. As should be understood, although the various steps in the
flowcharts of Figs.
2 and 4 are sequentially displayed as indicated by arrows, these steps are not
necessarily
executed in the sequences indicated by arrows. Unless otherwise explicitly
noted in this
paper, execution of these steps is not restricted by any sequence, as these
steps can also be
executed in other sequences (than those indicated in the drawings). Moreover,
at least
partial steps in the flowcharts of Figs. 2 and 4 may include plural sub-steps
or multi-phases,
these sub-steps or phases are not necessarily completed at the same timing,
but can be
executed at different timings, and these sub-steps or phases are also not
necessarily
sequentially performed, but can be performed in turns or alternately with
other steps or
with at least some of sub-steps or phases of other steps.
[0099] Based on the same inventive conception, the present invention further
provides a data
collecting device. In one embodiment, as shown in Fig. 9, the data collecting
device
comprises the following modules:
[0100] a first request receiving module 110, for receiving a form obtaining
request sent by a first
client end;
[0101] a definitive data obtaining module 120, for obtaining target form
definitive data to which
the form obtaining request corresponds from first preset nested-type fields of
a relational
database;
[0102] a definitive data sending module 130, for sending the target form
definitive data to the first
client end to instruct the first client end to present a form fill-in page
according to the target
form definitive data;
19
Date Recue/Date Received 2022-02-21
[0103] a form data receiving module 140, for receiving form data collected by
the first client end
through the form fill-in page and submitted by the first client end; and
[0104] a form data storing module 150, for storing the form data as a document
into a document
database.
[0105] In one embodiment, the form data storing module includes:
[0106] a data type recognizing sub-module, for recognizing data types of
various pieces of form
control data included in the form data, and
[0107] a control data storing sub-module, for storing the various pieces of
form control data into
second preset nested-type fields corresponding to the data types of the
various pieces of
form control data in the document database.
[0108] In one embodiment, the data types of the form control data are
character string, date and
long type, the first preset nested-type fields are JSON nested fields, and the
second preset
nested-type fields are nested fields.
[0109] In one embodiment, before the data collecting device executes the
corresponding function
of the request receiving module, functions corresponding to the following
modules are
further executed:
[0110] a page providing module, for providing a form creating page to a form
creating user through
a second client end;
[0111] a definitive data receiving module, for receiving the target form
definitive data submitted
by the second client end, wherein the target form definitive data is generated
by the second
client end based on an operation of the form creating user in the form
creating page, by
identifying each form control selected thereby for creating a form, obtaining
form
descriptive data configured thereby and control configuration data configured
thereby for
each form control, and according to the form descriptive data and the control
configuration
Date Recue/Date Received 2022-02-21
data to which each form control corresponds; and
[0112] a definitive data storing module, for storing the form definitive data
into the first preset
nested-type fields of the relational database.
[0113] In one embodiment, the data collecting device further comprises an
index establishing
module for establishing index for all form data of each form stored in the
document
database;
[0114] in one embodiment, the index establishing module includes:
[0115] a tokenizing sub-module, for employing a tokenizer to perform a
tokenizing process on all
form data of each form in the document database to obtain a plurality of
tokens;
[0116] a linguistically processing sub-module, for employing a language
processor to
linguistically process each token to obtain a plurality of terms; and
[0117] an indexing sub-module, for employing an indexer to create a document
chain table based
on the plural terms to obtain an index to which each form corresponds.
[0118] In one embodiment, the data collecting device further comprises:
[0119] an enquiring request receiving module, for receiving a form enquiring
request submitted
by the second client end, wherein the form enquiring request contains a query
statement;
[0120] a target document obtaining module, for obtaining a target document to
which the form
enquiring request corresponds from the document database; and
[0121] an enquiring result returning module, for generating an enquiring
result according to the
target document and returning the enquiring result to the second client end.
[0122] In one embodiment, the target document obtaining module includes:
[0123] a statement analyzing sub-module, for performing syntactic analysis and
linguistic analysis
on the query statement to obtain a syntax tree consisting of a series of
terms;
[0124] a document chain table obtaining sub-module, for searching for a pre-
created index
21
Date Recue/Date Received 2022-02-21
according to the syntax tree, and obtaining a document chain table to which
each term in
the syntax tree corresponds;
[0125] a resultant chain table obtaining sub-module, for performing
intersecting and excepting
processes on all document chain tables as obtained, and obtaining a resultant
document
chain table;
[0126] a relevancy calculating sub-module, for calculating relevancy between
each document
associated with the resultant document chain table and the query statement;
and
[0127] a target document obtaining sub-module, for obtaining a document whose
relevancy
satisfies a preset condition from all documents associated with the resultant
document
chain table.
[0128] Specific definitions relevant to the data collecting device may be
inferred from the
aforementioned definitions to the data collecting method, while no repetition
is made in
this context. The various modules in the aforementioned data collecting device
can be
wholly or partly realized via software, hardware, and a combination of
software with
hardware. The various modules can be embedded in the form of hardware in a
processor
in a computer equipment or independent of any computer equipment, and can also
be stored
in the form of software in a memory in a computer equipment, so as to
facilitate the
processor to invoke and perform operations corresponding to the aforementioned
various
modules.
[0129] In one embodiment, a computer equipment is provided, and its internal
structure can be as
shown in Fig. 10. The computer equipment comprises a processor, a memory, a
network
interface, and a database connected to each other via a system bus. The
processor of the
computer equipment is employed to provide computing and controlling
capabilities. The
memory of the computer equipment includes a nonvolatile storage medium and an
internal
memory. The nonvolatile storage medium stores therein an operating system, a
computer
22
Date Recue/Date Received 2022-02-21
program and a database. The internal memory provides environment for the
running of the
operating system and the computer program in the nonvolatile storage medium.
The
database of the computer equipment is employed to store such data as form
definitive data
and form data, etc. The network interface of the computer equipment is
employed to
connect to an external terminal via network for communication. The computer
program
realizes a data collecting method when it is executed by a processor.
[0130] As understandable to persons skilled in the art, the structure
illustrated in Fig. 10 is merely
a block diagram of partial structure relevant to the solution of the present
application, and
does not constitute any restriction to the computer equipment on which the
solution of the
present application is applied, as the specific computer equipment may
comprise
component parts that are more than or less than those illustrated in Fig. 10,
or may combine
certain component parts, or may have different layout of component parts.
[0131] In one embodiment, there is provided a computer equipment that
comprises a memory, a
processor and a computer program stored on the memory and operable on the
processor,
and the following steps are realized when the processor executes the computer
program:
[0132] receiving a form obtaining request sent by a first client end;
obtaining target form definitive
data to which the form obtaining request corresponds from first preset nested-
type fields
of a relational database; sending the target form definitive data to the first
client end to
instruct the first client end to present a form fill-in page according to the
target form
definitive data; receiving form data collected by the first client end through
the form fill-
in page and submitted by the first client end; and storing the form data as a
document into
a document database.
[0133] In one embodiment, when the processor executes the computer program to
realize the step
of storing the form data as a document into a document database, the following
steps are
23
Date Recue/Date Received 2022-02-21
further realized:
[0134] recognizing data types of various pieces of form control data included
in the form data, and
storing the various pieces of form control data into second preset nested-type
fields
corresponding to the data types of the various pieces of form control data in
the document
database.
[0135] In one embodiment, the data types of the form control data are
character string, date and
long type, the first preset nested-type fields are JSON nested fields, and the
second preset
nested-type fields are nested fields. Before the processor executes the
computer program
to realize the step of receiving a form obtaining request sent by a first
client end, the
following steps are further realized:
[0136] providing a form creating page to a form creating user through a second
client end;
receiving the target form definitive data submitted by the second client end,
wherein the
target form definitive data is generated by the second client end based on an
operation of
the form creating user in the form creating page, by identifying each form
control selected
thereby for creating a form, obtaining form descriptive data configured
thereby and control
configuration data configured thereby for each form control, and according to
the form
descriptive data and the control configuration data to which each form control
corresponds;
and storing the form definitive data into the first preset nested-type fields
of the relational
database.
[0137] In one embodiment, when the processor executes the computer program,
the following step
is further realized: establishing index for all form data of each form stored
in the document
database.
[0138] In one embodiment, when the processor executes the computer program to
realize the step
of establishing index for all form data of each form stored in the document
database, the
24
Date Recue/Date Received 2022-02-21
following steps are further realized:
[0139] employing a tokenizer to perform a tokenizing process on all form data
of each form in the
document database to obtain a plurality of tokens; employing a language
processor to
linguistically process each token to obtain a plurality of terms; and
employing an indexer
to create a document chain table based on the plural terms to obtain an index
to which each
form corresponds.
[0140] In one embodiment, when the processor executes the computer program,
the following
steps are further realized:
[0141] receiving a form enquiring request submitted by the second client end,
wherein the form
enquiring request contains a query statement; obtaining a target document to
which the
form enquiring request corresponds from the document database; and generating
an
enquiring result according to the target document and returning the enquiring
result to the
second client end.
[0142] In one embodiment, when the processor executes the computer program to
realize the step
of obtaining a target document to which the form enquiring request corresponds
from the
document database, the following steps are further realized:
[0143] performing syntactic analysis and linguistic analysis on the query
statement to obtain a
syntax tree consisting of a series of terms; searching for a pre-created index
according to
the syntax tree, and obtaining a document chain table to which each term in
the syntax tree
corresponds; performing intersecting and excepting processes on all document
chain
tables as obtained, and obtaining a resultant document chain table;
calculating relevancy
between each document associated with the resultant document chain table and
the query
statement; and obtaining a document whose relevancy satisfies a preset
condition from all
documents associated with the resultant document chain table.
Date Recue/Date Received 2022-02-21
[0144] In one embodiment, there is provided a computer-readable storage medium
storing thereon
a computer program, and the following steps are realized when the computer
program is
executed by a processor:
[0145] receiving a form obtaining request sent by a first client end;
obtaining target form definitive
data to which the form obtaining request corresponds from first preset nested-
type fields
of a relational database; sending the target form definitive data to the first
client end to
instruct the first client end to present a form fill-in page according to the
target form
definitive data; receiving form data collected by the first client end through
the form fill-
in page and submitted by the first client end; and storing the form data as a
document into
a document database.
[0146] In one embodiment, when the computer program is executed by a processor
to realize the
step of storing the form data as a document into a document database, the
following steps
are further realized:
[0147] recognizing data types of various pieces of form control data included
in the form data, and
storing the various pieces of form control data into second preset nested-type
fields
corresponding to the data types of the various pieces of form control data in
the document
database.
[0148] In one embodiment, the data types of the form control data are
character string, date and
long type, the first preset nested-type fields are JSON nested fields, and the
second preset
nested-type fields are nested fields. Before the computer program is executed
by a
processor to realize the step of receiving a form obtaining request sent by a
first client end,
the following steps are further realized:
[0149] providing a form creating page to a form creating user through a second
client end;
receiving the target form definitive data submitted by the second client end,
wherein the
target form definitive data is generated by the second client end based on an
operation of
26
Date Recue/Date Received 2022-02-21
the form creating user in the form creating page, by identifying each form
control selected
thereby for creating a form, obtaining form descriptive data configured
thereby and control
configuration data configured thereby for each form control, and according to
the form
descriptive data and the control configuration data to which each form control
corresponds;
and storing the form definitive data into the first preset nested-type fields
of the relational
database.
[0150] In one embodiment, when the computer program is executed by a
processor, the following
step is further realized: establishing index for all form data of each form
stored in the
document database.
[0151] In one embodiment, when the computer program is executed by a processor
to realize the
step of establishing index for all form data of each form stored in the
document database,
the following steps are further realized:
[0152] employing a tokenizer to perform a tokenizing process on all form data
of each form in the
document database to obtain a plurality of tokens; employing a language
processor to
linguistically process each token to obtain a plurality of terms; and
employing an indexer
to create a document chain table based on the plural terms to obtain an index
to which each
form corresponds.
[0153] In one embodiment, when the computer program is executed by a
processor, the following
steps are further realized:
[0154] receiving a form enquiring request submitted by the second client end,
wherein the form
enquiring request contains a query statement; obtaining a target document to
which the
form enquiring request corresponds from the document database; and generating
an
enquiring result according to the target document and returning the enquiring
result to the
second client end.
27
Date Recue/Date Received 2022-02-21
[0155] In one embodiment, when the computer program is executed by a processor
to realize the
step of obtaining a target document to which the form enquiring request
corresponds from
the document database, the following steps are further realized:
[0156] performing syntactic analysis and linguistic analysis on the query
statement to obtain a
syntax tree consisting of a series of terms; searching for a pre-created index
according to
the syntax tree, and obtaining a document chain table to which each term in
the syntax tree
corresponds; performing intersecting and excepting processes on all document
chain
tables as obtained, and obtaining a resultant document chain table;
calculating relevancy
between each document associated with the resultant document chain table and
the query
statement; and obtaining a document whose relevancy satisfies a preset
condition from all
documents associated with the resultant document chain table.
[0157] As comprehensible to persons ordinarily skilled in the art, the entire
or partial flows in the
methods according to the aforementioned embodiments can be completed via a
computer
program instructing relevant hardware, the computer program can be stored in a
nonvolatile
computer-readable storage medium, and the computer program can include the
flows as
embodied in the aforementioned various methods when executed. Any reference to
the
memory, storage, database or other media used in the various embodiments
provided by
the present application can all include nonvolatile and/or volatile
memory/memories. The
nonvolatile memory can include a read-only memory (ROM), a programmable ROM
(PROM), an electrically programmable ROM (EPROM), an electrically erasable and
programmable ROM (EEPROM) or a flash memory. The volatile memory can include a
random access memory (RAM) or an external cache memory. To serve as
explanation
rather than restriction, the RAM is obtainable in many forms, such as static
RAM (SRAM),
dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM
(DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM
28
Date Recue/Date Received 2022-02-21
(SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct Rambus dynamic
RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.
[0158] Technical features of the aforementioned embodiments are randomly
combinable, while all
possible combinations of the technical features in the aforementioned
embodiments are not
exhausted for the sake of brevity, but all these should be considered to fall
within the scope
recorded in the Description as long as such combinations of the technical
features are not
mutually contradictory.
[0159] The foregoing embodiments are merely directed to several modes of
execution of the
present application, and their descriptions are relatively specific and
detailed, but they
should not be hence misunderstood as restrictions to the inventive patent
scope. As should
be pointed out, persons with ordinary skill in the art may further make
various
modifications and improvements without departing from the conception of the
present
application, and all these should pertain to the protection scope of the
present application.
Accordingly, the patent protection scope of the present application shall be
based on the
attached Claims.
29
Date Recue/Date Received 2022-02-21
