CN116304266A - File management system - Google Patents
File management system Download PDFInfo
- Publication number
- CN116304266A CN116304266A CN202310222090.8A CN202310222090A CN116304266A CN 116304266 A CN116304266 A CN 116304266A CN 202310222090 A CN202310222090 A CN 202310222090A CN 116304266 A CN116304266 A CN 116304266A
- Authority
- CN
- China
- Prior art keywords
- file
- archive
- processed
- information
- target
- 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.)
- Granted
Links
- 238000012545 processing Methods 0.000 claims abstract description 102
- 238000000034 method Methods 0.000 claims description 22
- 238000004422 calculation algorithm Methods 0.000 claims description 17
- 238000013479 data entry Methods 0.000 claims description 15
- 238000001514 detection method Methods 0.000 claims description 15
- 238000004458 analytical method Methods 0.000 claims description 14
- 238000006243 chemical reaction Methods 0.000 claims description 14
- 230000008569 process Effects 0.000 claims description 14
- 238000000605 extraction Methods 0.000 claims description 11
- 230000000670 limiting effect Effects 0.000 claims description 9
- 238000010801 machine learning Methods 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 29
- 238000012986 modification Methods 0.000 description 10
- 230000004048 modification Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 6
- 239000000463 material Substances 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 230000014759 maintenance of location Effects 0.000 description 3
- 230000000644 propagated effect Effects 0.000 description 3
- 230000002829 reductive effect Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000006378 damage Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000018109 developmental process Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012552 review Methods 0.000 description 2
- 241000579895 Chlorostilbon Species 0.000 description 1
- 102100032202 Cornulin Human genes 0.000 description 1
- 101000920981 Homo sapiens Cornulin Proteins 0.000 description 1
- 241001441724 Tetraodontidae Species 0.000 description 1
- 241000700605 Viruses Species 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000013075 data extraction Methods 0.000 description 1
- 238000003066 decision tree Methods 0.000 description 1
- 238000005202 decontamination Methods 0.000 description 1
- 230000003588 decontaminative effect Effects 0.000 description 1
- 239000010976 emerald Substances 0.000 description 1
- 229910052876 emerald Inorganic materials 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 239000010977 jade Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 239000003607 modifier Substances 0.000 description 1
- 238000010606 normalization Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000036961 partial effect Effects 0.000 description 1
- ZLIBICFPKPWGIZ-UHFFFAOYSA-N pyrimethanil Chemical compound CC1=CC(C)=NC(NC=2C=CC=CC=2)=N1 ZLIBICFPKPWGIZ-UHFFFAOYSA-N 0.000 description 1
- 238000007637 random forest analysis Methods 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
- 238000007789 sealing Methods 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/93—Document management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/907—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
Abstract
The application discloses a file management system. The system comprises: the file acquisition module is configured to directly acquire a file to be processed, which is sent by a file provider, wherein the file to be processed comprises an information system electronic file such as an electronic file obtained after electronic processing or office automation; the archive processing module is configured to perform one or more of the following operations: acquiring metadata of the file to be processed; automatically identifying characteristic data corresponding to the file to be processed, wherein the characteristic data is determined by the structural information of the file to be processed after being arranged, combined and/or information supplemented; and generating a target file containing the electronic signature at least based on the file to be processed. And the archive storage module is configured to store the archive to be processed, the metadata, the characteristic data and the target file.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a single-system archive management system.
Background
With the rapid development of digital technology, it has become a major trend to replace traditional papered files/documents with electronic files/documents. The current file management system performs double-sleeve system, because of various and complex types of files and years of development, under the condition that the total amount of files is continuously accumulated, the consumption (including manpower, material resources, time and the like) of the double-sleeve file management system is further improved, and meanwhile, the file management efficiency is also further reduced.
Disclosure of Invention
The technical problem to be solved by the embodiments of the present application is how to provide a correct and efficient file management system.
In order to solve the above problems, the present application discloses an archive management system. The file acquisition module is configured to directly acquire a file to be processed, which is sent by a file provider, wherein the file to be processed comprises an information system electronic file such as an electronic file obtained after electronic processing or office automation; the archive processing module is configured to perform one or more of the following operations: acquiring metadata of the file to be processed; automatically identifying characteristic data corresponding to the file to be processed, wherein the characteristic data is determined by the structural information of the file to be processed after being arranged, combined and/or information supplemented; and generating a target file containing the electronic signature at least based on the file to be processed. And the archive storage module is configured to store the archive to be processed, the metadata, the characteristic data and the target file.
According to some embodiments of the application, the metadata is used to indicate data attributes of the archive to be processed, including one or more of the following: sequence number, creator, creation time, title, body, file size.
According to some embodiments of the application, to obtain the feature data, the archive processing module is configured to: processing the file to be processed by using an identification model to obtain intermediate data; and processing the intermediate data by using an analysis model to acquire the characteristic data.
According to some embodiments of the application, the recognition model includes a machine learning model based on a word recognition algorithm, and the archive processing module is configured to, for obtaining intermediate data: performing character recognition on the file to be processed by using the recognition model to acquire character information carried by the file to be processed; and designating the text information as the intermediate data.
According to some embodiments of the application, the analytical model comprises a machine learning model based on a keyword extraction algorithm; to obtain the feature data, the archive processing module is configured to: extracting keywords from the intermediate data by using the analysis model to obtain structural information included in the intermediate data; the file processing module calls the different analysis sub-models to process files to be processed of different file types; the feature data is determined based on the structured information.
According to some embodiments of the application, to generate the target file, the archive processing module is configured to: determining a target image based on the file to be processed; acquiring element information forming an electronic signature to be generated on the file to be processed and first size information of the target image; generating a candidate signature on the target image based at least on the element information and first size information of the target image; and generating the target signature on the file to be processed by utilizing the candidate signature based on the first size information of the target image and the second size information related to the file to be processed so as to acquire the target file.
According to some embodiments of the application, the element information is determined based on additional data of the archive to be processed and/or by receiving an external data input.
According to some embodiments of the application, to determine additional data, the archive processing module is configured to: acquiring a valid data entry determined based on the metadata; converting the format of the valid data entry to obtain a target entry; the additional data is determined based on the target entry.
According to some embodiments of the present application, the archive processing module is configured to: acquiring signature limiting information; determining a candidate frame range of the candidate signature on the target image based on the signature limiting information and the first size information of the target image; determining candidate font specifications of the element information in the candidate frame range; and generating the candidate signature by using the element information based on the candidate border range and the candidate font specification.
According to some embodiments of the application, to generate the target signature, the archive processing module is configured to: determining a conversion relation between the first size information and the second size information; and converting the candidate signature into the target signature based on the conversion relation.
According to some embodiments of the application, to generate the target signature, the archive processing module is configured to: determining an information distribution area of a target page of the file to be processed and target size information of the target signature; wherein the target signature is applied over the target page; generating the target signature outside the information distribution area of the target page based on the target size information; wherein the target signature does not overlap with the information distribution area.
According to some embodiments of the application, the system further comprises a profile detection module configured to detect a four-way nature of the pending profile during processing of the pending profile.
According to some embodiments of the application, the system further comprises a archive monitoring module configured to monitor whether the relevant data of the archive to be processed exceeds a custody limit.
The file management system disclosed by the application can efficiently and correctly process various related files. And better manage the archival data of the related archives. The complex information processing can be operated efficiently, and the manpower and material resources and time consumption in the file management process are reduced.
Drawings
The present application will be further illustrated by way of example embodiments, which will be described in detail with reference to the accompanying drawings. The embodiments are not limiting, in which like numerals represent like structures, wherein:
FIG. 1 is an exemplary schematic diagram of an archive management system shown in accordance with some embodiments of the present application;
FIG. 2 is an exemplary schematic diagram of a processing device according to some embodiments of the present application;
FIG. 3 is an exemplary block diagram of an archive management system shown in accordance with some embodiments of the present application;
FIG. 4 is an exemplary diagram of data entry conversion shown in accordance with some embodiments of the present application.
Detailed Description
In order to make the above objects, features and advantages of the present application more comprehensible, embodiments accompanied with figures are described in detail below. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is, however, susceptible of embodiment in many other forms than those described herein and similar modifications can be made by those skilled in the art without departing from the spirit of the application, and therefore the application is not to be limited to the specific embodiments disclosed below.
It will be understood that when an element is referred to as being "mounted" to another element, it can be directly mounted to the other element or intervening elements may also be present. When an element is referred to as being "connected" to another element, it can be directly connected to the other element or intervening elements may also be present. The terms "vertical," "horizontal," "left," "right," and the like are used herein for illustrative purposes only.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the description of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The term "and/or" and/or "as used herein includes any and all combinations of one or more of the associated listed items.
Some preferred embodiments of the present application are described below with reference to the accompanying drawings. It should be noted that the following description is for illustrative purposes and is not intended to limit the scope of the present application.
{ { FIG. 1 })
FIG. 1 is an exemplary schematic diagram of an archive management system shown in accordance with some embodiments of the present description. In some embodiments, the archive management system 100 may be used for automated collation and information entry of electronic archives or electronic documents. As shown in fig. 1, archive management system 100 may include a processing device 110, a storage device 120, a terminal 130, a network 140, and a data source 150.
Processing device 110 may be used to process information and/or data related to an archive to perform one or more of the functions disclosed in this specification. For example, processing device 110 may receive a pending archive sent directly by an archive provider. For another example, the processing device 110 may perform operations such as metadata acquisition, feature data identification, and generation of an electronic signature on the acquired file to be processed. For another example, the processing device 110 may store the obtained originals of the pending archive along with metadata, feature data, and an object file with an electronic signature generated based on the pending archive. In some embodiments, the processing device 110 may be implemented by a single server or a group of servers. The processing device 110 may be a single server or a group of servers. The server farm may be centralized or distributed. The processing device 110 may be local or remote in some embodiments. For example, processing device 110 may access information and/or data stored on storage device 120 or received from data source 150 via network 140. As another example, processing device 110 may be directly connected to storage device 120 to access stored information and/or data. In some embodiments, processing device 110 may be implemented on a cloud platform. For example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, a multiple cloud, or the like, or any combination of the foregoing examples. In some embodiments, processing device 110 may be implemented on a computing device as shown in fig. 2 of the present application. For example, processing device 110 may be implemented on one computing device 200 as shown in fig. 2, including one or more components in computing device 200.
In some embodiments, processing device 110 may include one or more processing engines (e.g., single core processing engines or multi-core processors). By way of example only, the processing device 110 may include one or more combinations of a central processing unit (cpu), an Application Specific Integrated Circuit (ASIC), an application specific instruction set processor (ASIP), an image processor (GPU), a physical arithmetic processing unit (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a microcontroller unit, a Reduced Instruction Set Computer (RISC), a microprocessor, and the like.
The storage device 120 may store data and/or instructions. In some embodiments, storage device 120 may store data resulting from processing of a archive to be processed by processing device 110. For example, the original and metadata of the file to be processed, the characteristic data, and the target file with electronic signature generated based on the file to be processed. In some embodiments, the storage device 120 may store data and/or instructions for execution or use by the processing device 110, which may be executed or used by the processing device 110 to implement the exemplary methods in this specification. In some embodiments, the storage device 120 may be part of the processing device 110. In some embodiments, the storage device 120 may include mass memory, removable memory, volatile read-write memory (RAM), read-only memory (ROM), and the like, or any combination thereof. Exemplary mass storage devices may include magnetic disks, optical disks, solid state disks, and the like. Exemplary removable memory may include flash drives, floppy disks, optical disks, memory cards, compact disks, tape, and the like. Exemplary RAM may include Dynamic RAM (DRAM), double rate synchronous dynamic RAM (DDR SDRAM), static RAM (SRAM), thyristor RAM (T-RAM), zero capacitance RAM (Z-RAM), and the like. Exemplary ROMs may include Mask ROM (MROM), programmable ROM (PROM), erasable programmable ROM (PEROM), electrically Erasable Programmable ROM (EEPROM), compact disk ROM (CD-ROM), and digital versatile disk ROM, among others. In some embodiments, storage device 120 may be a distributed storage system. In some embodiments, storage device 120 may be implemented on a cloud platform. For example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an internal cloud, a multi-layer cloud, or the like, or any combination thereof. For example, some algorithms or data in this specification may be stored on a cloud platform, and updated periodically, and the processing device 110 accesses the algorithms or data through a network, so as to implement unification and interaction of the algorithms or data of the entire platform.
The terminal 130 may be an operational front end of the processing device 110 and may include, but is not limited to, a mobile device 130-1, a tablet computer 130-2, a notebook computer 130-3, a desktop computer 130-4, etc., or any combination thereof. For example, an operator may input control instructions corresponding to operations that archive processing system 100 may perform on terminal 130. Such as query instructions to query an archive stored on storage device 120. In some embodiments, terminal 130 may be inter-coupled with processing device 110. For example, the computing power (e.g., CPU, GPU, etc.) of the terminal 130 itself may be used to implement the functionality of the processing device 110. While input ports of the terminal 130 (e.g., a touch virtual keyboard of the mobile device 130-1 and the tablet 130-2 such as a smart phone smart pad, a mouse keyboard of the notebook 130-3 and the desktop 130-4, etc.) may be used for input of operation instructions.
The network 140 may facilitate the exchange of information and/or data. In some embodiments, one or more components of archive management system 100 (e.g., processing device 110, storage device 120, and data source 150) may communicate information to other components of archive management system 100 via network 140. For example, processing device 110 may obtain a pending archive from data source 150 via network 140. In some embodiments, network 140 may be any form of wired or wireless network, or any combination thereof. By way of example only, the network 140 may be one or more combinations of a wired network, a fiber optic network, a telecommunications network, an internal network, the internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a Public Switched Telephone Network (PSTN), a bluetooth network, a zigbee network, a Near Field Communication (NFC) network, a global system for mobile communications (GSM) network, a Code Division Multiple Access (CDMA) network, a Time Division Multiple Access (TDMA) network, a General Packet Radio Service (GPRS) network, an enhanced data rates for GSM evolution (EDGE) network, a Wideband Code Division Multiple Access (WCDMA) network, a High Speed Downlink Packet Access (HSDPA) network, a Long Term Evolution (LTE) network, a User Datagram Protocol (UDP) network, a transmission control protocol/internet protocol (TCP/IP) network, a Short Message Services (SMS) network, a Wireless Application Protocol (WAP) network, a wideband (UWB) network, a mobile communications (1G, 2G, 3G, 4G, 5G) network, wi-Fi, li-Fi, narrowband internet of things (NB-infrared (IoT), ultra-band internet of things), etc. In some embodiments, network 140 may include one or more network access points. For example, network 140 may include wired or wireless network access points such as base stations and/or internet switching points. Through which one or more components of archive management system 100 may connect to network 140 to exchange information and/or data.
The data source 150 may provide various types of archives. The file can be obtained after the paper file is electronic, and can also be an electronic file of an information system such as office automation. For example, data sources 150-1, 150-2, and 150-3 may be separate data systems or databases of different companies, or various types of information systems such as office automation systems. These systems or databases may generate or store various types of electronic archives or electronic files. The data source 150 may send the archive to the processing device 110 via the network 140 for archive finishing. Processing device 110 may perform the operations described in the previous specification upon receiving directly via network 140 these profiles sent by data source 150. In some embodiments, the archive transmitted by data source 150 may be encrypted. For example, various encryption algorithms (such as PGP, MD5, AES, RC4, and triplet DES, RSA, blowfish, twofish) such as symmetric encryption, asymmetric encryption, hybrid encryption, and hashing are used to encrypt the file data, and then data transmission is performed. In one example, data source 150 may first convert the archive data to base64 bytecode before MD5 encryption and then transmit the encrypted archive data to processing device 110 via network 140.
{ { FIG. 2}
Fig. 2 is a block diagram of an exemplary processing device, shown in accordance with some embodiments of the present description. Processing device 110 may include any of the components used to implement the systems described in the embodiments of the present description. For example, the processing device 110 may be implemented in hardware, software programs, firmware, or a combination thereof. For convenience, only one processing device is depicted, but the computing functions described in connection with the recommendation area determining system 100 of the present embodiments may be implemented in a distributed manner by a set of similar platforms to distribute the processing load of the system.
In some embodiments, processing device 110 may include a processor 210, a memory 220, an input/output component 230, and a communication port 240. In some embodiments, the processor (e.g., CPU) 210 may execute program instructions in the form of one or more processors. In some embodiments, the memory 220 includes various forms of program memory and data memory, such as a hard disk, read-only memory (ROM), random Access Memory (RAM), etc., for storing a wide variety of data files for processing and/or transmission by a computer. In some embodiments, the input/output component 230 may be used to support input/output between the processing device 110 and other components. In some embodiments, the communication port 240 may be connected to a network for enabling data communication. An exemplary processing device may include program instructions stored in read-only memory (ROM), random Access Memory (RAM), and/or other types of non-transitory storage media for execution by processor 210. The methods and/or processes of the embodiments of the present description may be implemented in the form of program instructions. The processing device 110 may also receive the programs and data disclosed in the present specification through network communication.
For ease of understanding, only one processor is schematically depicted in fig. 2. However, it should be noted that the processing device 110 in the embodiments of the present specification may include a plurality of processors, and thus the operations and/or methods described in the embodiments of the present specification as being implemented by one processor may also be implemented by a plurality of processors collectively or individually. For example, if in this specification the processors of processing device 110 perform operations 1 and 2, it should be understood that operations 1 and 2 may also be performed jointly or independently by two different processors of processing device 110 (e.g., a first processor performing operation 1, a second processor performing operation 2, or both first and second processors jointly performing operations 1 and 2).
{ { FIG. 3 })
FIG. 3 is an exemplary block diagram of a processing device of the archive management system, shown in accordance with some embodiments of the present description. The file management system can realize efficient and rapid arrangement of electronic files and/or electronic files. As shown in fig. 3, processing device 300 may include a profile acquisition module 310, a profile processing module 320, and a profile storage module 330.
The archive acquisition module 310 may be configured to directly acquire the pending archive sent by the archive provider. The archive provider (e.g., data source 150) may be a person or entity that generates various archives, such as various level units, various companies, etc. By way of example, the office files of various documents produced by the unit departments, information system electronic files such as office automation produced by information systems of various companies such as office automation systems, etc. The file provider can electronically process the paper file to obtain an electronic file, and send the electronic file to the file management system for being obtained by the file obtaining module 310. Illustratively, an electronic version of a document in a variety of file formats, such as DOC, DOCX, XLS, XLSX, DBF, BMP, JPG, TIFF, GIF, PNG, CAD, TXT, PDF, OFD, may be obtained after scanning the paper document using a digital scanning device, such as a scanner.
In some embodiments, the archive acquisition module 310 may categorize the acquired pending archive. For example, classification is based on the source of the data. It will be appreciated that the file attributes (e.g., same format, same number of file entries, etc.) of the files to be processed provided by the same data source are the same. For pending files of the same data source, the file acquisition module 310 may store them under the same data directory for batch operations by the processing device 110 in a subsequent process. Such as batch data extraction and conversion, batch file format conversion, etc.
In some embodiments, the file obtaining module 310 may perform normalization processing on the obtained files to be processed with different specifications. For example, for situations where there are different specifications of the paper document (e.g., whether the paper document is a color part or a black and white part), different damage levels (e.g., a stain or a partial missing part on the paper, etc.), and tilting/warping occurs during scanning, the document acquisition module 310 may perform one or more of graying, binarizing, decontamination, tilt detection, and correction to maintain the uniform specifications of the document to be processed. For the case of different format sizes of electronic files of an information system such as office automation, the file acquisition module 310 may perform file size transformation to make the specifications of files to be processed consistent.
In some embodiments, archive acquisition module 310 may be implemented by communication port 240. The port may be a wireless network card or a wired port, and is connected to the network 140 to receive the file to be processed.
In some embodiments, the profile processing module 320 (e.g., the identifying unit 324) may automatically identify the feature data corresponding to the profile to be processed. The recognition unit 324 may process the file to be processed with the recognition model to obtain intermediate data. The recognition model may include a machine learning model based on a word recognition algorithm, including but not limited to CRNN, 2D-CTC, attention, ACE, SVTR, R 2 AM, SAR, trOCR, etc. The recognition model can be obtained by training an initial model based on a large amount of sample data, or can be a trained model which is opened by a public model platform and used by users. The recognition unit 324 may schedule the API interfaces of these common model platforms to upload the pending files for subsequent word recognition processing. It is apparent that the types of files are various, for example, document files, personnel files, litigation files, accounting files, judicial files, foreign exchange files, urban construction files, patent files, etc., and the format and content of each file are different. Therefore, for accurately recognizing characters of various files, the recognition model can be formed by combining a plurality of sub-models. A corresponding sub-model can be used for processing each type of archive so as to achieve the purpose of accurate identification.
In some embodiments, the recognition unit 324 may perform text recognition on the file to be processed by using the recognition model to obtain text information carried by the file to be processed. The text information may include all text-related information on the archive to be processed. For example, the specific content of the file, the text in an attached signature, the text manually drawn on the file, such as a signature, etc., or any combination thereof. The acquired text information may be used as intermediate data.
After acquiring the intermediate data, the identifying unit 324 may process the intermediate data with an analysis model to acquire the feature data. The analytical model may include a machine learning model based on keyword extraction algorithms, e.g., unsupervised keyword extraction algorithms such as TF-IDF algorithm, textRank algorithm, LDA algorithm, etc., or supervised keyword extraction algorithms such as Word2Vec Word cluster based keyword extraction algorithm, tree model based keyword extraction algorithms such as decision tree or random forest, etc. The recognition unit 324 may perform keyword extraction on the intermediate data using the analysis model to obtain the structural information included in the intermediate data. The analytical model may include analytical sub-models corresponding to different archive types. When the archive to be processed is a text archive, the recognition unit 324 may call an analysis sub-model corresponding to the text archive to extract structured information including a plurality of keywords indicating main contents of the document archive. Such as people, time, place, event, etc. And constructing independent sentences for summarizing the files to be processed based on the keywords. For example, the structured information is sequentially combined and a connective is added to the adjacent structured information to obtain an independent sentence summarizing the file to be processed.
When the file to be processed is a civil-engineering file, the identifying unit 324 may call an analysis sub-model corresponding to the civil-engineering file to extract all information contained in the civil-engineering file as the structural information. For example, various information such as city building units, engineering names, reference numbers, sub item names, sub item numbers, design professions, drawing numbers, drawing names, drawings, dates, and the like. And various types of signatures included, manual signatures on files such as those of engineering-related responsible persons, personnel signatures on corresponding parts of the as-built signature, and the like. Since the urban archives are typically presented in tabular form, the recognition unit 324 may utilize the analysis submodel to extract various types of information (e.g., header, rank data) in the table and populate such information into a constructed data table (e.g., excel spreadsheet). The form of the constructed data table may be consistent with the form of the urban set-up archive. The location and order of all information in the data table is also consistent with the location and order of the tables in the urban set-up archive. The filled data table may be designated as the structured data.
In some embodiments, the characteristic information may refer to information that can be used to indicate the primary content or content summary of the archive to be processed. When the file to be processed is a text file, the structural information obtained by the analysis sub-model for the text file, which is called by the recognition unit 324 after processing, can be used as the keyword/abstract of the text file, so that the matters mentioned by the text file can be succinctly and clearly shown. I.e. as said characteristic data. When the file to be processed is a civil engineering file, the structural information obtained by the analysis sub-model for the civil engineering file, which is called by the recognition unit 324 after processing, is completely consistent with the information carried by the civil engineering file, and the key information is displayed and is not omitted. And may also be used as the characteristic data.
In some embodiments, archive management system 100 may archive the received pending archive. The archive processing module 320 (e.g., signature generation module 326) may generate a target file containing an electronic signature (e.g., an archive electronic signature) based at least on the archive to be processed. The electronic signature may be an electronic signature with a CA certificate. The target file may be stored as archive data for the archive to be processed.
In some embodiments, signature generation module 326 may determine the target image based on the archive to be processed. The target image may be obtained based on the portion of the data of the archive to be processed that requires the generation of the electronic signature. In general, an electronic signature may be assigned to a top page or end page of a text file, for example, directly in the middle of the top page. The image resulting from converting the first page or the last page of the text file may be the target image. Signature generation module 326 may perform viable format conversion operations to determine the target image based on characteristic data of the archive to be processed. The target image may be a PNG image. The PNG format image file can retain information related to image quality while the file size is compressed to the limit, and can ensure minimal distortion. The display rate is fast and helps to speed up the data processing speed. It will thus be appreciated that converting a file of a different format type to a target image (e.g. PNG format image) for processing may help to improve processing efficiency when processing the file.
In some embodiments, the signature generation module 326 may obtain the element information that constitutes the target signature to be generated on the pending archive, as well as the first size information of the target image. The element information may be information containing specific content of the target signature. For example, the archive chapter may include necessary information such as a total number, a year, a part number, an organization (problem), a storage period, and the number of pages. In some embodiments, signature generation module 326 may determine based on additional data of the archive to be processed and/or by receiving external data input. The additional data may be determined based on metadata of the archive to be processed. The data entry determined by the content contained in the metadata may reflect part or all of the element information. Thus, the signature generation module 326 may determine additional data based on the metadata. With reference to fig. 4, fig. 4 is an exemplary schematic diagram of data entry conversion shown in accordance with some embodiments of the present application. The signature generation module 326 may first obtain valid data entries determined based on the metadata. As shown in fig. 4, the metadata contains 6 data entries. The valid data items are "serial number", "creation time", and "file title". The signature generation module 326 may convert the format of the valid data entry to obtain the target entry. For example, "sequence number" may be formatted into "case number", "creation time" may be formatted into "vertical date", "file title" may be formatted into "title". These target entries may be used to determine part of the attachment information. For example, "case number" and "date of the case" may be used to determine the full-block number and year. The signature generation module 326 may also acquire element information from external inputs. For example, the operator inputs the element information through an input part of the terminal 130. In some embodiments, the first size information of the target image may include an image width and an image height in pixels (i.e., dpi). For example, the first size information of the target image may be represented as 320×240. That is, the pixel height of the target image is 320 pixels and the pixel width is 240 pixels.
In some embodiments, signature generation module 326 may generate a candidate signature on the target image based at least on the element information and the first size information of the target image. The candidate signature may be one having the same signature content as the target signature. And typically the size of the target signature is specified. For example, the size of a six-grid archive chapter needs to be 4.5cm×1.6cm. Thus, in generating the candidate signature and/or generating the target signature in the candidate flow, the signature generation module 326 may determine the size of the candidate signature based on the size definition information for the target signature and the first size information. And determining that the text format includes a font size or the like according to how much content is contained in the element information. In the subsequent processing process, the target signature is generated based on the candidate signature through proportional conversion.
In some embodiments, the signature generation module 326 may obtain signature definition information. The signature limiting information may be information for indicating the size of the signature, limiting the size of the signature in a practical case, that is, on a paper document. For example, a six-cell archive chapter is required to be rectangular in size. The long side is 4.5cm and the wide side is 1.6cm. The signature definition information may be data containing the signature size information described above.
In some embodiments, the signature generation module 326 may determine a candidate bounding box range for the candidate signature on the target image based on the signature definition information and the first size information for the target image. Taking the first size information of the target image as 144/150dpi as an example, 1 cm= 28.346 pixels. Therefore, when it is necessary to impart a six-grid archival chapter having a size of 4.5 cm×1.6 cm on the target image, the required pixel length and width are 4.5× 28.346 = 127.557 pixels and 1.6× 28.346 = 45.3536 pixels, respectively. The pixel range formed by the pixel length and the pixel width can be a candidate frame range of the candidate signature.
In some embodiments, signature generation module 326 may determine candidate font specifications for the element information within the candidate bounding box. The signature generation module 326 may select an appropriate font size according to the size of the candidate frame range and the content of the element information, so as to generate the specific content contained in the element information in the candidate frame range. The font specification includes fonts, font sizes, and the like. In some embodiments, the signature generation module 326 may first determine the thickness of the lines that make up the candidate signature, and then determine the blank area within the range of the candidate border in combination with the range. The signature generation module 326 may calculate the size of the blank area, and determine the required font and font size according to the number of words of the content that need to be generated in the blank area, so as to achieve the purpose of displaying clearly and completely. In some embodiments, signature generation module 326 may, after determining the candidate bounding box range and the candidate font specification, generate the element information within the candidate bounding box range with requirements specified by the candidate font specification to complete generation of the candidate signature.
In some embodiments, the signature generation module 326 may generate the target signature on the archive to be processed using the candidate signature to obtain a target file based on the first size information of the target image and the second size information related to the archive to be processed. The second size information may be size information indicating a page carrying the target signature, or may be expressed in terms of image height and image width as the first size information. Taking a file to be processed as a PDF file, assuming that the resolution of the PDF file is 144/150dpi, the conversion relationship between one centimeter and a pixel may be 1 centimeter= 28.346 pixels. When the paper size to be printed is A4 (210 mm×297 mm), the second size information of the PFD may be 595.266 × 841.8762.
In some embodiments, signature generation module 326 may determine a conversion relationship of the first size information and the second size information and convert the candidate signature into the target signature based on the conversion relationship. The conversion relationship may be, for example, a size ratio (e.g., the ratio between 320×240 and 595.266 × 841.8762 mentioned above). Since the candidate signature differs from the target signature in size, the signature generation module 326 may transform the size of the candidate signature based on the size ratio to generate the target signature.
In some embodiments, the signature generation module 326 may generate the target signature in a blank area of a target page of the archive to be processed. The target page may be a page to which the target signature is given, for example, a top page of a PDF (if the file format of the file to be processed is not PDF, the file to be processed may be converted into PDF format). The signature generation module 326 may utilize a target segmentation model to identify and segment blank regions on a target page. A target signature is then generated within the blank region.
In some embodiments, when the file to be processed is an electronic file of an information system such as office automation, in order to ensure the uniqueness, authenticity and reliability of the electronic file, the signature generation module 326 may further generate encrypted timestamp information for the target signature after giving it, so as to perform "identification" for the file to be processed. The encrypted timestamp information may be CA center based timestamp information.
In some embodiments, the archive management system 100 may detect the four properties of the archive to be processed while performing the foregoing processing of the archive to be processed. For example, the archive detection module 340 is configured to perform four-way detection on an archive to be processed, including authenticity detection, integrity detection, availability detection, and security detection. For example, when the file to be processed is received, the file detection module 340 may first detect whether there is a signature given by the other party in the file to be processed (for example, the signature is generated after the electronic scan after the actual sealing, or directly generated on the electronic OA file). If so, the document detection module 340 may verify the signature. If not, the authenticity of the content can be detected. The detection result can be stored. After extracting the metadata, the archive detection module 340 may compare the metadata with the file data of the archive to be processed, and perform a consistency check to detect authenticity. For another example, the file detecting module 340 may determine whether there is a deletion or duplication in the file to be processed according to the file sequence number (sequence number in metadata) of the file to be processed received to detect the integrity. For another example, the archive detection module 340 may detect availability by detecting readability, whether an archive to be processed can be opened, enabled, edited, etc., to determine whether the archive to be processed is damaged. For example, archive detection module 340 may also detect whether files (e.g., viruses, trojans, invalid files, etc. of various types of all non-declared attached files) are entrained in the pending archive to detect the security of the pending archive.
In some embodiments, the stored relevant data of the pending archive may be monitored. For example, the archive monitoring module 350 may monitor whether the relevant data of the archive to be processed exceeds the custody limit. For example, it is determined whether the retention period is exceeded based on a comparison of the retention period of the archive to be processed and the roll date (e.g., determined from metadata) of the archive to be processed. If the retention period is exceeded, the relevant data of the file to be processed can be transferred to a specific storage area, such as a storage area dedicated to storing expired file data. The subsequent operations are performed according to an external input instruction (e.g., extended custody or archive destruction).
In some embodiments, the file management system 100 can also perform various file operations according to the external input instructions. Illustratively, an operator may log into an account of the profile management system 100 through the terminal 130. Various instructions are then entered via the interactive interface. Illustratively, the account of the operator of archive management system 100 may be of various types. Such as a system administrator account, a department employee account, etc. An operator logs into a system administrator account and can perform operations such as operating global users, e.g., delete users, modify users, add users, etc., operating archives, e.g., archive warehouse management (storage management), archive unified migration, archive audit, etc., workflow operations, e.g., workflow approval, etc. Logging into the department administrator account, operations such as department user deletion, modification, addition, etc., department profile such as profile warehouse management (storage management), profile borrowing, profile auditing, etc., department workflow operations such as workflow approval (e.g., application requesting profile review), etc., may be performed. Logging into employee department employee accounts, operations such as operating their own accounts, such as modifying users, operating department files, such as file add-on, file borrowing, file modification, file utilization, file querying, file statistics, etc., and department workflow operations such as workflow application (e.g., application for file review), workflow viewing (e.g., viewing the current state of the application, such as passing or not), etc., may be performed.
It should be understood that the system shown in fig. 3 and its modules may be implemented in a variety of ways. For example, in some embodiments, the system and its modules may be implemented in hardware, software, or a combination of software and hardware. Wherein the hardware portion may be implemented using dedicated logic; the software portions may then be stored in a memory and executed by a suitable instruction execution system, such as a microprocessor or special purpose design hardware. Those skilled in the art will appreciate that the methods and systems described above may be implemented using computer executable instructions and/or embodied in processor control code, such as provided on a carrier medium such as a magnetic disk, CD or DVD-ROM, a programmable memory such as read only memory (firmware), or a data carrier such as an optical or electronic signal carrier. The system of the present specification and its modules may be implemented not only with hardware circuits such as very large scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, etc., or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc., but also with software executed by various types of processors, for example, and with a combination of the above hardware circuits and software (e.g., firmware).
It should be noted that the above description of the modules is for convenience of description only and is not intended to limit the present description to the scope of the illustrated embodiments. It will be appreciated by those skilled in the art that, given the principles of the system, various modules may be combined arbitrarily or a subsystem may be constructed in connection with other modules without departing from such principles. For example, each module may share one memory module, or each module may have a respective memory module. Such variations are within the scope of the present description.
Having described the basic concepts herein, it will be apparent to those skilled in the art that the foregoing detailed disclosure is by way of example only and is not intended to be limiting. Although not explicitly described herein, various modifications, improvements, and adaptations to the present disclosure may occur to one skilled in the art. Such modifications, improvements, and modifications are intended to be suggested within this specification, and therefore, such modifications, improvements, and modifications are intended to be included within the spirit and scope of the exemplary embodiments of the present invention.
Meanwhile, the specification uses specific words to describe the embodiments of the specification. Reference to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic is associated with at least one embodiment of the present description. Thus, it should be emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various positions in this specification are not necessarily referring to the same embodiment. Furthermore, certain features, structures, or characteristics of one or more embodiments of the present description may be combined as suitable.
Furthermore, those skilled in the art will appreciate that the various aspects of the specification can be illustrated and described in terms of several patentable categories or circumstances, including any novel and useful procedures, machines, products, or materials, or any novel and useful modifications thereof. Accordingly, aspects of the present description may be performed entirely by hardware, entirely by software (including firmware, resident software, micro-code, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as a "data block," module, "" engine, "" unit, "" component, "or" system. Furthermore, aspects of the specification may take the form of a computer product, comprising computer-readable program code, embodied in one or more computer-readable media.
The computer storage medium may contain a propagated data signal with the computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take on a variety of forms, including electro-magnetic, optical, etc., or any suitable combination thereof. A computer storage medium may be any computer readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code located on a computer storage medium may be propagated through any suitable medium, including radio, cable, fiber optic cable, RF, or the like, or a combination of any of the foregoing.
The computer program code necessary for operation of portions of the present description may be written in any one or more programming languages, including an object oriented programming language such as Java, scala, smalltalk, eiffel, JADE, emerald, C ++, c#, vb net, python, and the like, a conventional programming language such as C language, visual Basic, fortran 3003, perl, COBOL 3002, PHP, ABAP, a dynamic programming language such as Python, ruby, and Groovy, or the like. The program code may execute entirely on the user's computer or as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any form of network, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet), or the use of services such as software as a service (SaaS) in a cloud computing environment.
Furthermore, the order in which the elements and sequences are processed, the use of numerical letters, or other designations in the description are not intended to limit the order in which the processes and methods of the description are performed unless explicitly recited in the claims. While certain presently useful inventive embodiments have been discussed in the foregoing disclosure, by way of various examples, it is to be understood that such details are merely illustrative and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements included within the spirit and scope of the embodiments of the present disclosure. For example, while the system components described above may be implemented by hardware devices, they may also be implemented solely by software solutions, such as installing the described system on an existing server or mobile device.
Likewise, it should be noted that in order to simplify the presentation disclosed in this specification and thereby aid in understanding one or more inventive embodiments, various features are sometimes grouped together in a single embodiment, figure, or description thereof. This method of disclosure, however, is not intended to imply that more features than are presented in the claims are required for the present description. Indeed, less than all of the features of a single embodiment disclosed above.
In some embodiments, numbers describing the components, number of attributes are used, it being understood that such numbers being used in the description of embodiments are modified in some examples by the modifier "about," approximately, "or" substantially. Unless otherwise indicated, "about," "approximately," or "substantially" indicate that the number allows for a 20% variation. Accordingly, in some embodiments, numerical parameters set forth in the specification and claims are approximations that may vary depending upon the desired properties sought to be obtained by the individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and employ a method for preserving the general number of digits. Although the numerical ranges and parameters set forth herein are approximations that may be employed in some embodiments to confirm the breadth of the range, in particular embodiments, the setting of such numerical values is as precise as possible.
Each patent, patent application publication, and other material, such as articles, books, specifications, publications, documents, etc., referred to in this specification is incorporated herein by reference in its entirety. Except for application history documents that are inconsistent or conflicting with the content of this specification, documents that are currently or later attached to this specification in which the broadest scope of the claims to this specification is limited are also. It is noted that, if the description, definition, and/or use of a term in an attached material in this specification does not conform to or conflict with what is described in this specification, the description, definition, and/or use of the term in this specification controls.
Finally, it should be understood that the embodiments described in this specification are merely illustrative of the principles of the embodiments of this specification. Other variations are possible within the scope of this description. Thus, by way of example, and not limitation, alternative configurations of embodiments of the present specification may be considered as consistent with the teachings of the present specification. Accordingly, the embodiments of the present specification are not limited to only the embodiments explicitly described and depicted in the present specification.
Claims (13)
1. A archive management system, the system comprising:
The file acquisition module is configured to directly acquire a file to be processed, which is sent by a file provider, wherein the file to be processed comprises an information system electronic file such as an electronic file obtained after electronic processing or office automation;
the archive processing module is configured to perform one or more of the following operations:
acquiring metadata of the file to be processed;
automatically identifying characteristic data corresponding to the file to be processed, wherein the characteristic data is determined by the structural information of the file to be processed after being arranged, combined and/or information supplemented; and
and generating a target file containing the electronic signature at least based on the file to be processed.
And the archive storage module is configured to store the archive to be processed, the metadata, the characteristic data and the target file.
2. A archive management system according to claim 1 wherein the metadata is indicative of data attributes of the archive to be processed, including one or more of: sequence number, creator, creation time, title, body, file size.
3. A archive management system according to claim 1 wherein, to obtain the characteristic data, the archive processing module is configured to:
Processing the file to be processed by using an identification model to obtain intermediate data;
and processing the intermediate data by using an analysis model to acquire the characteristic data.
4. A archive management system according to claim 3 wherein the recognition model comprises a machine learning model based on a word recognition algorithm, and wherein to obtain intermediate data, the archive processing module is configured to:
performing character recognition on the file to be processed by using the recognition model to acquire character information carried by the file to be processed;
and designating the text information as the intermediate data.
5. A profile management system as in claim 3, wherein the analysis model comprises a machine learning model based on a keyword extraction algorithm; to obtain the feature data, the archive processing module is configured to:
extracting keywords from the intermediate data by using the analysis model to obtain structural information included in the intermediate data; the file processing module calls the different analysis sub-models to process files to be processed of different file types;
The feature data is determined based on the structured information.
6. A archive management system according to claim 1 wherein, to generate the target file, the archive processing module is configured to:
determining a target image based on the file to be processed;
acquiring element information forming an electronic signature to be generated on the file to be processed and first size information of the target image;
generating a candidate signature on the target image based at least on the element information and first size information of the target image;
and generating the target signature on the file to be processed by utilizing the candidate signature based on the first size information of the target image and the second size information related to the file to be processed so as to acquire the target file.
7. A archive management system according to claim 6 wherein the element information is determined based on additional data of the archive to be processed and/or by receiving external data input.
8. A archive management system according to claim 7 wherein, to determine additional data, the archive processing module is configured to:
acquiring a valid data entry determined based on the metadata;
Converting the format of the valid data entry to obtain a target entry;
the additional data is determined based on the target entry.
9. A archive management system according to claim 6 wherein the archive processing module is configured to generate candidate signatures:
acquiring signature limiting information;
determining a candidate frame range of the candidate signature on the target image based on the signature limiting information and the first size information of the target image;
determining candidate font specifications of the element information in the candidate frame range;
and generating the candidate signature by using the element information based on the candidate border range and the candidate font specification.
10. A archive management system according to claim 9 wherein, to generate the target signature, the archive processing module is configured to:
determining a conversion relation between the first size information and the second size information;
and converting the candidate signature into the target signature based on the conversion relation.
11. A archive management system according to claim 10 wherein, to generate the target signature, the archive processing module is configured to:
Determining an information distribution area of a target page of the file to be processed and target size information of the target signature; wherein the target signature is applied over the target page;
generating the target signature outside the information distribution area of the target page based on the target size information; wherein the target signature does not overlap with the information distribution area.
12. A archive management system according to claim 1 further comprising an archive detection module configured to detect the quadrilateralness of the archive to be processed during processing of the archive to be processed.
13. A archive management system according to claim 1 further comprising an archive monitoring module configured to monitor whether the relevant data of the archive to be processed exceeds a custody limit.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310200810 | 2023-03-03 | ||
| CN2023102008100 | 2023-03-03 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116304266A true CN116304266A (en) | 2023-06-23 |
| CN116304266B CN116304266B (en) | 2024-02-27 |
Family
ID=86828235
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310222090.8A Active CN116304266B (en) | 2023-03-03 | 2023-03-09 | File management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116304266B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102968426A (en) * | 2012-07-04 | 2013-03-13 | 南京斯谱蓝自动化科技有限公司 | Archive comprehensive management system |
| CN108491442A (en) * | 2018-02-12 | 2018-09-04 | 广东绍林科技开发有限公司 | A kind of document management method, device, storage medium and system |
| US20180253439A1 (en) * | 2017-03-02 | 2018-09-06 | Virustotal SLU | Characterizing files for similarity searching |
| CN111242759A (en) * | 2019-12-25 | 2020-06-05 | 航天信息股份有限公司 | Accounting electronic file processing method and system based on network |
| WO2020155763A1 (en) * | 2019-01-28 | 2020-08-06 | 平安科技（深圳）有限公司 | Ocr recognition method and electronic device thereof |
| WO2020233037A1 (en) * | 2019-05-20 | 2020-11-26 | 深圳壹账通智能科技有限公司 | Data processing method and apparatus, and storage medium |
| CN113360506A (en) * | 2021-07-26 | 2021-09-07 | 江苏燕宁工程科技集团有限公司 | Highway engineering BIM-based paper archive digital processing method and system |
| CN113779656A (en) * | 2021-09-18 | 2021-12-10 | 厦门海迈科技股份有限公司 | Stamping method, electronic file platform and computer readable storage medium |
| CN114067335A (en) * | 2021-11-08 | 2022-02-18 | 清远市中盛合力网络科技有限公司 | Electronic archive text recognition method, system, computer equipment and storage medium |
| CN114359553A (en) * | 2022-03-17 | 2022-04-15 | 北京惠朗时代科技有限公司 | Signature positioning method and system based on Internet of things and storage medium |
| CN114463774A (en) * | 2022-02-25 | 2022-05-10 | 厦门合立道工程设计集团股份有限公司 | Intelligent identification method for picture of engineering drawing |
-
2023
- 2023-03-09 CN CN202310222090.8A patent/CN116304266B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102968426A (en) * | 2012-07-04 | 2013-03-13 | 南京斯谱蓝自动化科技有限公司 | Archive comprehensive management system |
| US20180253439A1 (en) * | 2017-03-02 | 2018-09-06 | Virustotal SLU | Characterizing files for similarity searching |
| CN108491442A (en) * | 2018-02-12 | 2018-09-04 | 广东绍林科技开发有限公司 | A kind of document management method, device, storage medium and system |
| WO2020155763A1 (en) * | 2019-01-28 | 2020-08-06 | 平安科技（深圳）有限公司 | Ocr recognition method and electronic device thereof |
| WO2020233037A1 (en) * | 2019-05-20 | 2020-11-26 | 深圳壹账通智能科技有限公司 | Data processing method and apparatus, and storage medium |
| CN111242759A (en) * | 2019-12-25 | 2020-06-05 | 航天信息股份有限公司 | Accounting electronic file processing method and system based on network |
| CN113360506A (en) * | 2021-07-26 | 2021-09-07 | 江苏燕宁工程科技集团有限公司 | Highway engineering BIM-based paper archive digital processing method and system |
| CN113779656A (en) * | 2021-09-18 | 2021-12-10 | 厦门海迈科技股份有限公司 | Stamping method, electronic file platform and computer readable storage medium |
| CN114067335A (en) * | 2021-11-08 | 2022-02-18 | 清远市中盛合力网络科技有限公司 | Electronic archive text recognition method, system, computer equipment and storage medium |
| CN114463774A (en) * | 2022-02-25 | 2022-05-10 | 厦门合立道工程设计集团股份有限公司 | Intelligent identification method for picture of engineering drawing |
| CN114359553A (en) * | 2022-03-17 | 2022-04-15 | 北京惠朗时代科技有限公司 | Signature positioning method and system based on Internet of things and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 陈新;杨桂明;: "智慧时代的电子档案管理系统", 信息记录材料, no. 12, 1 December 2019 (2019-12-01), pages 70 - 73 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116304266B (en) | 2024-02-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11188657B2 (en) | Method and system for managing electronic documents based on sensitivity of information | |
| US11032437B2 (en) | Method to create a secure distributed data validation system using a distributed storage system and artificial intelligence | |
| CN110457302B (en) | Intelligent structured data cleaning method | |
| US9256798B2 (en) | Document alteration based on native text analysis and OCR | |
| CN110990390B (en) | Data cooperative processing method, device, computer equipment and storage medium | |
| US11461298B1 (en) | Scoring parameter generation for identity resolution | |
| US11316669B2 (en) | Audit result data storage method and device, audit result data query method and device, and audit item storage method and device | |
| US11138426B2 (en) | Template matching, rules building and token extraction | |
| US11403283B2 (en) | Distributed ledger based generation of electronic documents | |
| US20220200995A1 (en) | Method and server for access verification in an identity and access management system | |
| CN110544035A (en) | internal control detection method, system and computer readable storage medium | |
| CN114416638A (en) | Automatic electronic file filing method and system | |
| WO2021013057A1 (en) | Data management method and apparatus, and device and computer-readable storage medium | |
| US20130321867A1 (en) | Typographical block generation | |
| CN116304266B (en) | File management system | |
| US11436359B2 (en) | System and method for managing permissions of users for a single data type column-oriented data structure | |
| US20190005038A1 (en) | Method and apparatus for grouping documents based on high-level features clustering | |
| CN103761290A (en) | Data management method and system based on content aware | |
| US20150030241A1 (en) | Method and system for data identification and extraction using pictorial representations in a source document | |
| CN116503889B (en) | File and electronic file processing method, device, equipment and storage medium | |
| US11314765B2 (en) | Multistage data sniffer for data extraction | |
| CN115630409B (en) | Data storage control method and device | |
| CN116189203B (en) | Electronic signature generation method, device, equipment and storage medium | |
| CN113643082B (en) | Invoice processing method and device based on artificial intelligence, computer equipment and medium | |
| US11790677B2 (en) | System for distributed server network with embedded image decoder as chain code program runtime |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 1608, Building 1, Rongsheng Business Center, No. 135 Wangdun Road, Suzhou Industrial Park, Suzhou Area, China (Jiangsu) Pilot Free Trade Zone, Suzhou City, Jiangsu Province, 215000 Applicant after: Suzhou Industrial Park Hangxing Information Technology Service Co.,Ltd. Address before: 3rd Floor, Zone A, Archive Building, No. 328 Suzhou Avenue East, Suzhou City, Jiangsu Province, 215000 Applicant before: Suzhou Industrial Park Hangxing Information Technology Service Co.,Ltd. |
|
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Mei Hong Inventor after: Pan Peiyuan Inventor after: Hu Chen Inventor after: Chen Jinpeng Inventor before: Pan Peiyuan Inventor before: Chen Jinpeng Inventor before: Hu Chen Inventor before: Mei Hong |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |