[go: up one dir, main page]

CN118312469A - Method and device for processing delivery document - Google Patents

Method and device for processing delivery document Download PDF

Info

Publication number
CN118312469A
CN118312469A CN202410379833.7A CN202410379833A CN118312469A CN 118312469 A CN118312469 A CN 118312469A CN 202410379833 A CN202410379833 A CN 202410379833A CN 118312469 A CN118312469 A CN 118312469A
Authority
CN
China
Prior art keywords
title
task
physical subsystem
document
delivery
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202410379833.7A
Other languages
Chinese (zh)
Inventor
李超
王清华
张翀
赵俊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CCB Finetech Co Ltd
Original Assignee
CCB Finetech Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by CCB Finetech Co Ltd filed Critical CCB Finetech Co Ltd
Priority to CN202410379833.7A priority Critical patent/CN118312469A/en
Publication of CN118312469A publication Critical patent/CN118312469A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/11File system administration, e.g. details of archiving or snapshots
    • G06F16/113Details of archiving
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/17Details of further file system functions
    • G06F16/178Techniques for file synchronisation in file systems
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/18File system types
    • G06F16/182Distributed file systems
    • G06F16/1824Distributed file systems implemented using Network-attached Storage [NAS] architecture
    • G06F16/183Provision of network file services by network file servers, e.g. by using NFS, CIFS
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/45Clustering; Classification
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1097Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Multimedia (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention discloses a method and a device for processing a delivery document, and relates to the technical field of big data, wherein the method comprises the following steps: acquiring development task information and version plan information of a specified demand item; according to a preset directory structure, creating a cloud disk document storage directory in combination with development task information, wherein the preset directory structure is divided into 4 layers, and the first layer is a task business group title or a system business group title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title; when a plurality of delivery documents uploaded by the delivery view system are received, each delivery document is stored in a cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document. The invention can improve the processing efficiency of the delivery document.

Description

Method and device for processing delivery document
Technical Field
The invention relates to the technical field of big data, in particular to a method and a device for processing a delivery document.
Background
This section is intended to provide a background or context for embodiments of the invention. The description herein is not admitted to be prior art by inclusion in this section.
Rapid developments in the financial and technological industry have made the development of various financial and technological products increasingly important. In the product development process, the requirement needs to be quickly converted into product delivery, the same delivery document faces the dual requirements of upward delivery and on-cloud archiving management, most of current delivery document processing systems are single-system document processing tools, the upward delivery and on-cloud archiving of the delivery document cannot be simultaneously realized, and the processing efficiency of the delivery document is low; in addition, when uploading the delivery documents to the cloud disk, the research personnel are required to manually inquire the directory files, and due to the huge quantity of the delivery documents, the manual file uploading mode wastes time and energy of the research personnel, increases operation difficulty and error rate of the research personnel, and is easy to cause problems of uploading errors or file loss and the like.
Disclosure of Invention
The embodiment of the invention provides a processing method of a delivery document, which is used for realizing the upward delivery and cloud archiving of the delivery document at the same time, reducing the operation difficulty and error rate when the delivery document is stored and improving the processing efficiency of the delivery document, and comprises the following steps:
Acquiring development task information and version plan information of a specified demand item from a task management system;
Calling a catalog creation script, and creating a cloud disk document storage catalog of the appointed demand item according to a preset catalog structure and combining development task information and version plan information of the appointed demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title;
When a plurality of delivery documents uploaded by the delivery view system are received, each delivery document is stored in a cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document.
The embodiment of the invention also provides a device for processing the delivery document, which is used for realizing the upward delivery and cloud archiving of the delivery document at the same time, reducing the operation difficulty and error rate when the delivery document is stored and improving the processing efficiency of the delivery document, and comprises the following steps:
The acquisition module is used for acquiring development task information and version plan information of the appointed requirement item from the task management system;
the catalog creation module is used for calling a catalog creation script and creating a cloud disk document storage catalog of the appointed demand item according to a preset catalog structure and combining development task information and version plan information of the appointed demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title;
And the document storage module is used for storing each delivery document in the cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document when receiving a plurality of delivery documents uploaded by the delivery view system.
The embodiment of the invention also provides computer equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the processing method of delivering the document when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the method for processing the delivered document when being executed by a processor.
The embodiment of the invention also provides a computer program product, which comprises a computer program, and the computer program realizes the processing method of the delivery document when being executed by a processor.
In the embodiment of the invention, development task information and version plan information of a specified demand item are acquired from a task management system; calling a catalog creation script, and creating a cloud disk document storage catalog of the appointed demand item according to a preset catalog structure and combining development task information and version plan information of the appointed demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title; when a plurality of delivery documents uploaded by the delivery view system are received, each delivery document is stored in a cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document. Compared with the existing document processing method, according to a preset directory structure, development task information and version scheduling information of a designated demand item are combined, a cloud disk document storage directory is automatically created, a delivery document is uploaded through a delivery view system, and according to the development task information and version scheduling information carried by each delivery document, the cloud disk document storage directory is matched, so that automatic document storage is realized, the operation difficulty and error rate in document storage delivery are reduced, and the document processing efficiency of delivery is improved; moreover, the catalog structure is composed of a task business group title or a system business group title, a project title or a physical subsystem title, a task title or a production date title and a file type title, and the cloud disk document storage catalog created according to the catalog structure can ensure that each delivery document is stored under a plurality of corresponding business group catalogues, so that the synchronization of the delivery document among a plurality of business group systems is realized, and further, the upward delivery and cloud archiving of the delivery document are simultaneously realized.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
FIG. 1 is a flow chart of a method of processing a delivery document provided in an embodiment of the present invention;
FIG. 2 is a flowchart of a method for creating a cloud disk document storage directory according to an embodiment of the present invention;
Fig. 3 is a schematic structural diagram of a cloud disk document storage directory provided in an embodiment of the present invention;
Fig. 4 is a schematic structural diagram of a cloud disk-based document management system according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of a processing device for delivering documents provided in an embodiment of the present invention;
fig. 6 is a schematic diagram of a computer device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present invention and their descriptions herein are for the purpose of explaining the present invention, but are not to be construed as limiting the invention.
In the description of the present specification, the terms "comprising," "including," "having," "containing," and the like are open-ended terms, meaning including, but not limited to. The description of the reference terms "one embodiment," "a particular embodiment," "some embodiments," "for example," etc., means that a particular feature, structure, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. The order of steps involved in the embodiments is illustrative of the practice of the application, and is not limited and may be suitably modified as desired.
In the embodiments of the present application, it should be noted that, in the embodiments of the present application, some software, components, models and other existing industries may be mentioned, which are to be considered as exemplary, for only explaining the feasibility of implementing the technical solution of the present application, but not meaning that the applicant has or must not use the solution.
Research has found that the rapid development of the financial and technological industry makes the development of various financial and technological products increasingly important. In the product development process, the requirement needs to be quickly converted into product delivery, the same delivery document faces the dual requirements of upward delivery and on-cloud archiving management, most of current document processing systems are single-system document processing tools, the upward delivery and on-cloud archiving of the delivery document cannot be simultaneously realized, and the processing efficiency of the delivery document is low; and manually uploading files to the cloud disk, the directory files need to be manually queried, and due to the huge quantity of delivered files, the manual file uploading mode can waste time and energy of research and development personnel, can increase operation difficulty and error rate of the research and development personnel, and is easy to cause problems of uploading errors or file loss and the like.
Aiming at the research, the embodiment of the invention provides a processing scheme of the delivery document, which can realize the upward delivery and cloud archiving of the delivery document at the same time, reduce the operation difficulty and error rate when the delivery document is stored, and improve the processing efficiency of the delivery document.
As shown in FIG. 1, a flowchart of a method for processing a delivery document is provided in an embodiment of the present invention. The method may comprise the steps of:
step 101, acquiring development task information and version plan information of a specified requirement item from a task management system;
Step 102, calling a catalog creation script, and creating a cloud disk document storage catalog of a designated demand item according to a preset catalog structure and combining development task information and version plan information of the designated demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title;
and step 103, when a plurality of delivery documents uploaded by the delivery view system are received, storing each delivery document in a cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document.
In the embodiment of the invention, development task information and version plan information of a specified demand item are acquired from a task management system; calling a catalog creation script, and creating a cloud disk document storage catalog of the appointed demand item according to a preset catalog structure and combining development task information and version plan information of the appointed demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title; when a plurality of delivery documents uploaded by the delivery view system are received, each delivery document is stored in a cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document. Compared with the existing document processing method, according to a preset directory structure, development task information and version scheduling information of a designated demand item are combined, a cloud disk document storage directory is automatically created, a delivery document is uploaded through a delivery view system, and according to the development task information and version scheduling information carried by each delivery document, the cloud disk document storage directory is matched, so that automatic document storage is realized, the operation difficulty and error rate in document storage delivery are reduced, and the document processing efficiency of delivery is improved; moreover, the catalog structure is composed of a task business group title or a system business group title, a project title or a physical subsystem title, a task title or a production date title and a file type title, and the cloud disk document storage catalog created according to the catalog structure can ensure that each delivery document is stored under a plurality of corresponding business group catalogues, so that the synchronization of the delivery document among a plurality of business group systems is realized, and further, the upward delivery and cloud archiving of the delivery document are simultaneously realized.
The following describes in detail the processing method of the delivery document shown in fig. 1.
In the above step 101, development task information and version plan information specifying a demand item may be acquired from the task management system by interacting with the task management system.
The development task information can comprise a project identifier, a task production date, a task production type and task development team information; the version plan information may include physical subsystem identification, physical subsystem development team information, physical subsystem commissioning date, and physical subsystem commissioning type.
In specific implementation, the task management system may automatically generate development task information (task dimension) and version plan information (physical subsystem dimension) of the project according to the production point, and store data such as the development task information and the version plan information in the task management system database. The development task information may include a plurality of task identifications, for example, a version task identification, a development task identification, etc.; the physical subsystem identification may be the name of the physical subsystem (chinese or english), the number of the physical subsystem, etc.
In the step 102, a catalog creation script may be invoked to create a cloud disk document storage catalog of a specified demand item according to a preset catalog structure in combination with development task information and version plan information of the specified demand item.
In specific implementation, the preset directory structure may be a unified directory structure designed to store and organize documents on the cloud disk. The catalog structure entity may include a catalog of development documents designed during the overall development process starting with the demand analysis and ending with the final delivery date. In the design process of the directory structure, the requirement analysis documents are considered to be strongly related to project and version tasks, so that the directory storage structure of project task dimension is required to be designed in the directory structure for archiving and managing the requirement analysis documents; considering that the design document is strongly related to the physical subsystem, the directory storage structure of the dimension of the physical subsystem needs to be designed in the directory structure, and the method can be used for archiving and managing the detailed design document. Specifically, the directory structure may include 4 layers, the first layer may be a business group layer including a task business group title or a system business group title, the second layer may include information such as project, physical subsystem, or business group management, the third layer may include information such as task, production date, and the fourth layer may include document types.
When the cloud disk file storage directory is implemented, after development task information and version plan information are acquired from a task management system, a directory creation script is triggered, and the directory creation script creates a cloud disk file storage directory of a specified requirement item according to a preset directory structure and the development task information and version plan information of the specified requirement item. The cloud disk document storage directory may include a project task related directory and a physical subsystem directory.
In one embodiment, as shown in fig. 2, the step 102 may specifically include:
Step 201, creating a project task related catalog of the appointed requirement item according to a preset catalog structure in combination with project identification, task production date, task production type and task development team information of the appointed requirement item;
step 202, creating a physical subsystem catalog of the appointed demand item according to a preset catalog structure and combining physical subsystem identification, physical subsystem development team information, physical subsystem production date and physical subsystem production type of the appointed demand item;
step 203, determining a cloud disk document storage directory of the specified requirement item according to the project task related directory and the physical subsystem directory.
In one embodiment, the step 201 may specifically include:
Determining task business cluster titles of the directory structure according to the task development team information; determining an item title of the directory structure according to the item identification; determining a task title of the directory structure according to the task identifier; determining a file type title corresponding to the task title according to the task production date and the task production type;
And creating a project task related catalog of the appointed requirement item according to the task business group title, the project title, the task title and the file type title corresponding to the task title of the catalog structure.
In one embodiment, the step 202 may specifically include:
Determining a system business cluster title of the directory structure according to the physical subsystem development team information; determining a physical subsystem title of the directory structure according to the physical subsystem identifier; determining a production date title of the directory structure according to the production date of the physical subsystem; determining a file type title corresponding to the production date title according to the production date of the physical subsystem and the production type of the physical subsystem;
And creating a physical subsystem catalog of the appointed requirement item according to the system business group title, the physical subsystem title, the production date title and the file type title corresponding to the production date title of the catalog structure.
In particular implementations, both the created project task related directory and the physical subsystem directory may be layer 4.
Specifically, the creating step of the project task related catalogue may be: determining a task business group title of a first layer according to task development team information in development task information; determining a project title of a second layer according to the project identification; determining a task title of the third layer according to the task identifier; and determining a file type title of the fourth layer according to the task commissioning date and the task commissioning type. The task title of the third layer may be a title named after the date of task delivery. The task identification may be a task name, a task number, etc.
Specifically, the creating step of the physical subsystem directory may be: determining a first layer of business cluster titles according to the physical subsystem development team information; determining a physical subsystem title of the second layer according to the physical subsystem identifier; determining a production date title of the third layer according to the production date of the physical subsystem; and determining a file type title of the fourth layer according to the physical subsystem production date and the physical subsystem production type.
In one embodiment, the step 203 may include:
And under the condition that the task business group title and the system business group title are the same, combining the project task related catalogue and the physical subsystem catalogue to obtain a cloud disk document storage catalogue of the specified requirement item.
In the specific implementation, if the project task related catalog and the physical subsystem catalog have the same business group title, it is noted that the project and the physical subsystem development team are the same, and the project task related catalog and the physical subsystem catalog may be combined under the same business group title. If not, no merging is needed.
Fig. 3 is a schematic structural diagram of a cloud disk document storage directory according to an embodiment of the present invention. As shown in fig. 3, the cloud disk document storage directory includes a project task related directory and a physical subsystem directory, and the project task related directory and the physical subsystem directory belong to the same business group. The first layer title of the cloud disk document storage directory is a business group A; the second tier title under utility group a includes XX project and XX physical subsystem; under the XX project title, the third layer comprises a stand, a knot and an XX version task title, wherein the stand and the knot are needed by each project; under the XX version task title, the fourth layer comprises a plurality of subtasks of the version task, namely, requirement analysis, architecture design, version development and integration test; under the XX physical subsystem title, the third layer is the physical subsystem production date, and the fourth layer is a plurality of subtasks corresponding to the physical subsystem production date, namely detailed design, nonfunctional test, security test, mobile test, delivery production and the like.
It should be noted that, fig. 3 may further include a service group management directory, specifically, a service group management header may be added in the second layer, and the third layer includes a plurality of management items corresponding to the service group management header, for example, version delivery, quality management, resource management, configuration management, risk management, and the like, where the management items may be set according to management requirements of each service group.
Thus, based on the steps 101 and 102 and fig. 2, by combining with the task management system, the embodiment of the invention can automatically create the project task related catalogue on the cloud disk according to the project identifier, the task production date, the task production type and the task development team information; and automatically creating a physical subsystem catalog on the cloud disk according to the physical subsystem identification, the physical subsystem development team information, the physical subsystem production date and the physical subsystem production type. Therefore, compared with the existing manual directory creation or unified storage directory design, the directory creation method has the advantages that the created directory meets the requirements of users, the flexibility is higher, and the directory creation efficiency can be improved.
In step 103, after the cloud disk document storage directory is successfully created, the delivery document of the project may be uploaded through the delivery view system. And triggering a catalog matching engine when receiving a plurality of delivery documents uploaded by the delivery view system, and storing the plurality of delivery documents under a corresponding cloud disk document storage catalog by the catalog matching engine based on a preset matching rule.
In specific implementation, the delivery view system is a file uploading system based on a software technology, and can realize the archiving and caching of files of various types. File types may include text files, spreadsheets, presentations, PDF files, compression packages, and the like.
For project task related catalogs, the matching rules may be: the directory names (directory titles) are matched by item identification. If multiple teams develop the same development project at the same time, i.e. the project identification exists in different business groups, multiple delivery documents need to be duplicated and copied in all business group directories. Namely, matching the project identifier of each delivery document with a cloud disk document storage catalog, and inquiring the project title which is the same as the project identifier of the delivery document; in the case where the project title and the task title which are the same as the project identifier and the task identifier of the delivery document exist in a plurality of business group titles, the delivery document is stored in a file type title corresponding to the type of the delivery document in each business group title in the same project title as the project identifier of the delivery document in the same task title as the task identifier of the delivery document.
For a physical subsystem system catalog, the matching rules may be: according to the service group to which the physical subsystem belongs, the method is to locate the service group first, and then match the directory name (directory title) corresponding to the service group according to the physical subsystem identification, wherein the matching mode can be to match the directory name by using a rule of 'brackets + unique identification of the physical subsystem + brackets', so as to avoid the directory being unable to be matched due to the change of the system name.
In one embodiment, the matching method for the physical subsystem system catalog specifically may include:
When a plurality of delivery documents uploaded by a delivery view system are received, matching the physical subsystem team information of each delivery document with a cloud disk document storage catalog to acquire a business group title which is the same as the physical subsystem team information of the delivery document; querying a physical subsystem title identical to the physical subsystem identification of the delivery document under the same business group title as the physical subsystem team information of the delivery document;
And storing the delivery document under a file type title corresponding to the document type of the delivery document under a physical subsystem title identical to the physical subsystem identification of the delivery document under a physical subsystem title identical to the physical subsystem team information of the delivery document according to the physical subsystem date and the document type of each delivery document.
In this way, the delivery document is uploaded to the cloud disk through a single delivery view system, and the delivery document is stored under the relevant catalogue through the preset matching rule of the catalogue matching engine, so that the synchronization among multiple service group systems can be realized after the completion of the document, and the delivery document is transferred in multiple places.
In addition, in the embodiment of the present invention, in step 103, when receiving a plurality of delivery documents uploaded by the delivery view system, if the project identifier and the task identifier of any delivery document are matched with the cloud disk document storage directory, and the project title and the task title which are the same as the project identifier and the task identifier of the delivery document are not matched, a project task related directory is created in real time according to the project identifier, the task development team information, the task identifier, the document type and a preset directory structure of the delivery document.
In another embodiment, when receiving a plurality of delivery documents uploaded by a delivery view system, if the physical subsystem team information of any delivery document is matched with a cloud disk document storage catalog and is not matched with a business group title which is the same as the physical subsystem team information of the delivery document, creating a physical subsystem catalog in real time according to the physical subsystem identification, the physical subsystem team information, the physical subsystem production date, the document type and a preset catalog structure of the delivery document; or under the condition that the same business group title as the physical subsystem team information of the delivery document is matched, but under the condition that the same business group title as the physical subsystem team information of the delivery document is not queried, under the condition that the same physical subsystem title as the physical subsystem identification of the delivery document is not queried, creating a physical subsystem catalog according to the physical subsystem identification, the physical subsystem date of production, the document type and a preset catalog structure of the delivery document under the condition that the same business group title as the physical subsystem team information of the delivery document is matched.
In the implementation, for the delivery document which is not matched with the target directory, the related directory can be directly created in real time according to a preset directory structure.
Meanwhile, in the embodiment of the invention, a cloud disk manual uploading channel can be reserved, and file multi-channel and multi-dimensional uploading is realized.
In summary, the method for processing the delivery document provided by the embodiment of the invention has the following beneficial effects:
1. According to a preset directory structure, cloud disk document storage directories (project task related directories and physical subsystem directories) are automatically created by combining development task information and version plan information of specified demand items, so that flexibility, accuracy and efficiency of directory creation can be improved.
2. And uploading the delivery document through the delivery view system, and matching the delivery document with the cloud disk document storage directory according to the project identification, the task identification and the document type of each delivery document, or matching the delivery document with the cloud disk document storage directory according to the physical subsystem team information, the physical subsystem title, the physical subsystem production date and the document type of each delivery document, so as to realize automatic document storage.
3. Under the condition that the project identifiers which are the same as the project identifiers of the delivery documents exist under a plurality of business group titles, the delivery documents are stored in a catalog corresponding to each business group title of the cloud disk, so that the synchronization and storage of the delivery documents among a plurality of business group systems can be realized, the upward delivery and the cloud archiving of the delivery documents are realized at the same time, the operation difficulty and the error rate of the storage of the delivery documents are reduced, and the processing efficiency of the delivery documents is improved.
Aiming at the processing method of the delivery document, the embodiment of the invention also provides a cloud disk-based document management system, which comprises a task management system, a delivery view system and a cloud disk as shown in fig. 4. Wherein:
task management system: and the system is used for generating development task information and version plan information according to the production point.
Delivery view system: for exposing all development tasks or physical subsystems, a document uploader may upload the requirements analysis documents and design documents for multiple development tasks or physical subsystems on the same interface.
Cloud disk: the cloud disk file storage directory is automatically created on the cloud disk according to development task information and version plan information; and stores the delivery document.
The document transmission between the delivery view system and the cloud disk can be realized through a file transmission channel, the file transmission channel belongs to an enterprise internal network, and a preset encryption mode is adopted during document transmission so as to ensure data security. When the delivery view system uploads the delivery document to the cloud disk for storage through the file transmission channel, the catalog corresponding to the delivery document can be automatically matched through the catalog matching engine.
According to the embodiment of the invention, the cloud disk-based document management system can improve the efficiency and reliability of document delivery management in a mode of being linked with the task management system and the delivery view system.
The technical scheme of the invention obtains, stores, uses, processes and the like the data, which all meet the relevant regulations of national laws and regulations.
The embodiment of the invention also provides a processing device for delivering the document, as described in the following embodiment. Because the principle of the device for solving the problem is similar to that of the processing method of the delivery document, the implementation of the device can be referred to the implementation of the processing method of the delivery document, and the repetition is omitted.
FIG. 5 is a schematic diagram of a document delivery processing apparatus according to an embodiment of the present invention, where the apparatus includes:
an obtaining module 501, configured to obtain development task information and version plan information of a specified requirement item from a task management system;
The catalog creation module 502 is configured to invoke a catalog creation script, and create a cloud disk document storage catalog of a specified demand item according to a preset catalog structure in combination with development task information and version plan information of the specified demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title;
The document storage module 503 is configured to, when receiving a plurality of delivery documents uploaded by the delivery view system, store each of the delivery documents in the cloud disk document storage directory according to development task information and version schedule information carried by each of the delivery documents.
In one embodiment, the development task information may include a project identification, a task commissioning date, a task commissioning type, and task development team information; the version plan information may include physical subsystem identification, physical subsystem development team information, physical subsystem production date and physical subsystem production type;
The catalog creation module can be specifically used for:
According to a preset directory structure, a project task related directory of the appointed requirement item is created by combining project identification, task production date, task production type and task development team information of the appointed requirement item;
According to a preset directory structure, a physical subsystem directory of the appointed demand item is created by combining a physical subsystem identifier, physical subsystem development team information, a physical subsystem production date and a physical subsystem production type of the appointed demand item;
And determining a cloud disk document storage directory of the specified demand item according to the project task related directory and the physical subsystem directory.
In one embodiment, the catalog creation module may be further operable to:
Determining task business cluster titles of the directory structure according to the task development team information; determining an item title of the directory structure according to the item identification; determining a task title of the directory structure according to the task identifier; determining a file type title corresponding to the task title according to the task production date and the task production type;
And creating a project task related catalog of the appointed requirement item according to the task business group title, the project title, the task title and the file type title corresponding to the task title of the catalog structure.
In one embodiment, the catalog creation module may be further operable to:
Determining a system business cluster title of the directory structure according to the physical subsystem development team information; determining a physical subsystem title of the directory structure according to the physical subsystem identifier; determining a production date title of the directory structure according to the production date of the physical subsystem; determining a file type title corresponding to the production date title according to the production date of the physical subsystem and the production type of the physical subsystem;
And creating a physical subsystem catalog of the appointed requirement item according to the system business group title, the physical subsystem title, the production date title and the file type title corresponding to the production date title of the catalog structure.
In one embodiment, the catalog creation module may be further operable to:
And under the condition that the task business group title and the system business group title are the same, combining the project task related catalogue and the physical subsystem catalogue to obtain a cloud disk document storage catalogue of the specified requirement item.
In one embodiment, the document storage module may be used to:
Matching the project identifier and the task identifier of each delivery document with the cloud disk document storage catalog, and inquiring the project title and the task title which are the same as the project identifier and the task identifier of the delivery document;
In the case where the project title and the task title which are the same as the project identifier and the task identifier of the delivery document exist in a plurality of business group titles, the delivery document is stored in a file type title corresponding to the type of the delivery document in each business group title in the same project title as the project identifier of the delivery document in the same task title as the task identifier of the delivery document.
In one embodiment, the document storage module may also be configured to:
When a plurality of delivery documents uploaded by a delivery view system are received, matching the physical subsystem team information of each delivery document with a cloud disk document storage catalog to acquire a business group title which is the same as the physical subsystem team information of the delivery document; querying a physical subsystem title identical to the physical subsystem identification of the delivery document under the same business group title as the physical subsystem team information of the delivery document;
And storing the delivery document under a file type title corresponding to the document type of the delivery document under a physical subsystem title identical to the physical subsystem identification of the delivery document under a physical subsystem title identical to the physical subsystem team information of the delivery document according to the physical subsystem date and the document type of each delivery document.
In one embodiment, the method may further include a catalog real-time creation module for:
If the project identification and the task identification of any delivery document are matched with the cloud disk document storage catalog, and the project title and the task title which are the same as the project identification and the task identification of the delivery document are not matched, the project task related catalog is created in real time according to the project identification, the task development team information, the task identification, the document type and the preset catalog structure of the delivery document.
In one embodiment, the catalog real-time creation module may also be configured to:
If the physical subsystem team information of any delivery document is matched with the cloud disk document storage catalog, and the same business cluster title as the physical subsystem team information of the delivery document is not matched, creating a physical subsystem catalog in real time according to the physical subsystem identification, the physical subsystem team information, the physical subsystem production date, the document type and a preset catalog structure of the delivery document;
Or under the condition that the same business group title as the physical subsystem team information of the delivery document is matched, but under the condition that the same business group title as the physical subsystem team information of the delivery document is not queried, under the condition that the same physical subsystem title as the physical subsystem identification of the delivery document is not queried, creating a physical subsystem catalog according to the physical subsystem identification, the physical subsystem date of production, the document type and a preset catalog structure of the delivery document under the condition that the same business group title as the physical subsystem team information of the delivery document is matched.
An embodiment of the present invention further provides a computer device, and fig. 6 is a schematic diagram of a computer device in the embodiment of the present invention, where the computer device 600 includes a memory 610, a processor 620, and a computer program 630 stored in the memory 610 and capable of running on the processor 620, and the processor 620 implements the method for processing the delivered document when executing the computer program 630.
The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the method for processing the delivered document when being executed by a processor.
The embodiment of the invention also provides a computer program product, which comprises a computer program, and the computer program realizes the processing method of the delivery document when being executed by a processor.
In the embodiment of the invention, development task information and version plan information of a specified demand item are acquired from a task management system; calling a catalog creation script, and creating a cloud disk document storage catalog of the appointed demand item according to a preset catalog structure and combining development task information and version plan information of the appointed demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title; when a plurality of delivery documents uploaded by the delivery view system are received, each delivery document is stored in a cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document. Compared with the existing document processing method, according to a preset directory structure, development task information and version scheduling information of a designated demand item are combined, a cloud disk document storage directory is automatically created, a delivery document is uploaded through a delivery view system, and according to the development task information and version scheduling information carried by each delivery document, the cloud disk document storage directory is matched, so that automatic document storage is realized, the operation difficulty and error rate in document storage delivery are reduced, and the document processing efficiency of delivery is improved; moreover, the catalog structure is composed of a task business group title or a system business group title, a project title or a physical subsystem title, a task title or a production date title and a file type title, and the cloud disk document storage catalog created according to the catalog structure can ensure that each delivery document is stored under a plurality of corresponding business group catalogues, so that the synchronization of the delivery document among a plurality of business group systems is realized, and further, the upward delivery and cloud archiving of the delivery document are simultaneously realized.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.

Claims (21)

1. A method of processing a delivery document, comprising:
Acquiring development task information and version plan information of a specified demand item from a task management system;
Calling a catalog creation script, and creating a cloud disk document storage catalog of the appointed demand item according to a preset catalog structure and combining development task information and version plan information of the appointed demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title;
When a plurality of delivery documents uploaded by the delivery view system are received, each delivery document is stored in a cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document.
2. The method of claim 1, wherein the development task information includes project identification, task commissioning date, task commissioning type, and task development team information; the version plan information comprises a physical subsystem identifier, physical subsystem development team information, a physical subsystem production date and a physical subsystem production type;
invoking a catalog creation script, and creating a cloud disk document storage catalog of a specified demand item according to a preset catalog structure and combining development task information and version plan information of the specified demand item, wherein the cloud disk document storage catalog of the specified demand item comprises:
According to a preset directory structure, a project task related directory of the appointed requirement item is created by combining project identification, task production date, task production type and task development team information of the appointed requirement item;
According to a preset directory structure, a physical subsystem directory of the appointed demand item is created by combining a physical subsystem identifier, physical subsystem development team information, a physical subsystem production date and a physical subsystem production type of the appointed demand item;
And determining a cloud disk document storage directory of the specified demand item according to the project task related directory and the physical subsystem directory.
3. The method of claim 2, wherein creating the project task related catalog specifying the demand item in combination with the project identification, the task commissioning date, the task commissioning type, and the task development team information specifying the demand item according to the preset catalog structure comprises:
Determining task business cluster titles of the directory structure according to the task development team information; determining an item title of the directory structure according to the item identification; determining a task title of the directory structure according to the task identifier; determining a file type title corresponding to the task title according to the task production date and the task production type;
And creating a project task related catalog of the appointed requirement item according to the task business group title, the project title, the task title and the file type title corresponding to the task title of the catalog structure.
4. The method of claim 3, wherein creating the physical subsystem catalog specifying the demand item in combination with the physical subsystem identification specifying the demand item, the physical subsystem development team information, the physical subsystem date of production, and the physical subsystem type of production according to the preset catalog structure comprises:
Determining a system business cluster title of the directory structure according to the physical subsystem development team information; determining a physical subsystem title of the directory structure according to the physical subsystem identifier; determining a production date title of the directory structure according to the production date of the physical subsystem; determining a file type title corresponding to the production date title according to the production date of the physical subsystem and the production type of the physical subsystem;
And creating a physical subsystem catalog of the appointed requirement item according to the system business group title, the physical subsystem title, the production date title and the file type title corresponding to the production date title of the catalog structure.
5. The method of claim 4, wherein determining a cloud disk document storage directory specifying a demand item based on the project task related directory and the physical subsystem directory comprises:
And under the condition that the task business group title and the system business group title are the same, combining the project task related catalogue and the physical subsystem catalogue to obtain a cloud disk document storage catalogue of the specified requirement item.
6. The method of claim 5, wherein upon receiving a plurality of delivery documents uploaded by the delivery view system, storing each delivery document in a cloud disk document storage directory based on development task information and version schedule information carried by each delivery document, comprising:
Matching the project identifier and the task identifier of each delivery document with the cloud disk document storage catalog, and inquiring the project title and the task title which are the same as the project identifier and the task identifier of the delivery document;
In the case where the project title and the task title which are the same as the project identifier and the task identifier of the delivery document exist in a plurality of business group titles, the delivery document is stored in a file type title corresponding to the type of the delivery document in each business group title in the same project title as the project identifier of the delivery document in the same task title as the task identifier of the delivery document.
7. The method of claim 5, wherein upon receiving a plurality of delivery documents uploaded by the delivery view system, storing each delivery document in a cloud disk document storage directory based on development task information and version schedule information carried by each delivery document, comprising:
When a plurality of delivery documents uploaded by a delivery view system are received, matching the physical subsystem team information of each delivery document with a cloud disk document storage catalog to acquire a business group title which is the same as the physical subsystem team information of the delivery document; querying a physical subsystem title identical to the physical subsystem identification of the delivery document under the same business group title as the physical subsystem team information of the delivery document;
And storing the delivery document under a file type title corresponding to the document type of the delivery document under a physical subsystem title identical to the physical subsystem identification of the delivery document under a physical subsystem title identical to the physical subsystem team information of the delivery document according to the physical subsystem date and the document type of each delivery document.
8. The method as recited in claim 6, further comprising:
If the project identification and the task identification of any delivery document are matched with the cloud disk document storage catalog, and the project title and the task title which are the same as the project identification and the task identification of the delivery document are not matched, the project task related catalog is created in real time according to the project identification, the task development team information, the task identification, the document type and the preset catalog structure of the delivery document.
9. The method as recited in claim 7, further comprising:
If the physical subsystem team information of any delivery document is matched with the cloud disk document storage catalog, and the same business cluster title as the physical subsystem team information of the delivery document is not matched, creating a physical subsystem catalog in real time according to the physical subsystem identification, the physical subsystem team information, the physical subsystem production date, the document type and a preset catalog structure of the delivery document;
Or under the condition that the same business group title as the physical subsystem team information of the delivery document is matched, but under the condition that the same business group title as the physical subsystem team information of the delivery document is not queried, under the condition that the same physical subsystem title as the physical subsystem identification of the delivery document is not queried, creating a physical subsystem catalog according to the physical subsystem identification, the physical subsystem date of production, the document type and a preset catalog structure of the delivery document under the condition that the same business group title as the physical subsystem team information of the delivery document is matched.
10. A delivery document processing apparatus, comprising:
The acquisition module is used for acquiring development task information and version plan information of the appointed requirement item from the task management system;
the catalog creation module is used for calling a catalog creation script and creating a cloud disk document storage catalog of the appointed demand item according to a preset catalog structure and combining development task information and version plan information of the appointed demand item; the preset directory structure is divided into 4 layers, wherein the first layer is a task business cluster title or a system business cluster title; the second layer is an item title or a physical subsystem title; the third layer is a task title or a production date title; the fourth layer is a file type title;
And the document storage module is used for storing each delivery document in the cloud disk document storage catalog according to development task information and version scheduling information carried by each delivery document when receiving a plurality of delivery documents uploaded by the delivery view system.
11. The apparatus of claim 10, wherein the development task information includes project identification, task commissioning date, task commissioning type, and task development team information; the version plan information comprises a physical subsystem identifier, physical subsystem development team information, a physical subsystem production date and a physical subsystem production type;
The catalog creation module is specifically used for:
According to a preset directory structure, a project task related directory of the appointed requirement item is created by combining project identification, task production date, task production type and task development team information of the appointed requirement item;
According to a preset directory structure, a physical subsystem directory of the appointed demand item is created by combining a physical subsystem identifier, physical subsystem development team information, a physical subsystem production date and a physical subsystem production type of the appointed demand item;
And determining a cloud disk document storage directory of the specified demand item according to the project task related directory and the physical subsystem directory.
12. The apparatus of claim 11, wherein the catalog creation module is further to:
Determining task business cluster titles of the directory structure according to the task development team information; determining an item title of the directory structure according to the item identification; determining a task title of the directory structure according to the task identifier; determining a file type title corresponding to the task title according to the task production date and the task production type;
And creating a project task related catalog of the appointed requirement item according to the task business group title, the project title, the task title and the file type title corresponding to the task title of the catalog structure.
13. The apparatus of claim 12, wherein the catalog creation module is further to:
Determining a system business cluster title of the directory structure according to the physical subsystem development team information; determining a physical subsystem title of the directory structure according to the physical subsystem identifier; determining a production date title of the directory structure according to the production date of the physical subsystem; determining a file type title corresponding to the production date title according to the production date of the physical subsystem and the production type of the physical subsystem;
And creating a physical subsystem catalog of the appointed requirement item according to the system business group title, the physical subsystem title, the production date title and the file type title corresponding to the production date title of the catalog structure.
14. The apparatus of claim 13, wherein the catalog creation module is further to:
And under the condition that the task business group title and the system business group title are the same, combining the project task related catalogue and the physical subsystem catalogue to obtain a cloud disk document storage catalogue of the specified requirement item.
15. The apparatus of claim 14, wherein the document storage module is to:
Matching the project identifier and the task identifier of each delivery document with the cloud disk document storage catalog, and inquiring the project title and the task title which are the same as the project identifier and the task identifier of the delivery document;
In the case where the project title and the task title which are the same as the project identifier and the task identifier of the delivery document exist in a plurality of business group titles, the delivery document is stored in a file type title corresponding to the type of the delivery document in each business group title in the same project title as the project identifier of the delivery document in the same task title as the task identifier of the delivery document.
16. The apparatus of claim 14, wherein the document storage module is further configured to:
When a plurality of delivery documents uploaded by a delivery view system are received, matching the physical subsystem team information of each delivery document with a cloud disk document storage catalog to acquire a business group title which is the same as the physical subsystem team information of the delivery document; querying a physical subsystem title identical to the physical subsystem identification of the delivery document under the same business group title as the physical subsystem team information of the delivery document;
And storing the delivery document under a file type title corresponding to the document type of the delivery document under a physical subsystem title identical to the physical subsystem identification of the delivery document under a physical subsystem title identical to the physical subsystem team information of the delivery document according to the physical subsystem date and the document type of each delivery document.
17. The apparatus of claim 15, further comprising a catalog real-time creation module to:
If the project identification and the task identification of any delivery document are matched with the cloud disk document storage catalog, and the project title and the task title which are the same as the project identification and the task identification of the delivery document are not matched, the project task related catalog is created in real time according to the project identification, the task development team information, the task identification, the document type and the preset catalog structure of the delivery document.
18. The apparatus of claim 16, wherein the catalog real-time creation module is further to:
If the physical subsystem team information of any delivery document is matched with the cloud disk document storage catalog, and the same business cluster title as the physical subsystem team information of the delivery document is not matched, creating a physical subsystem catalog in real time according to the physical subsystem identification, the physical subsystem team information, the physical subsystem production date, the document type and a preset catalog structure of the delivery document;
Or under the condition that the same business group title as the physical subsystem team information of the delivery document is matched, but under the condition that the same business group title as the physical subsystem team information of the delivery document is not queried, under the condition that the same physical subsystem title as the physical subsystem identification of the delivery document is not queried, creating a physical subsystem catalog according to the physical subsystem identification, the physical subsystem date of production, the document type and a preset catalog structure of the delivery document under the condition that the same business group title as the physical subsystem team information of the delivery document is matched.
19. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 9 when executing the computer program.
20. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of claims 1 to 9.
21. A computer program product, characterized in that the computer program product comprises a computer program which, when executed by a processor, implements the method of any of claims 1 to 9.
CN202410379833.7A 2024-03-29 2024-03-29 Method and device for processing delivery document Pending CN118312469A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410379833.7A CN118312469A (en) 2024-03-29 2024-03-29 Method and device for processing delivery document

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410379833.7A CN118312469A (en) 2024-03-29 2024-03-29 Method and device for processing delivery document

Publications (1)

Publication Number Publication Date
CN118312469A true CN118312469A (en) 2024-07-09

Family

ID=91726561

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410379833.7A Pending CN118312469A (en) 2024-03-29 2024-03-29 Method and device for processing delivery document

Country Status (1)

Country Link
CN (1) CN118312469A (en)

Similar Documents

Publication Publication Date Title
US20200065295A1 (en) Method for connecting a relational data store's meta data with hadoop
US8478726B2 (en) Parallel database backup and restore
CN114741375B (en) A system and method for fast and automatic data migration of multi-source heterogeneous databases
US8880463B2 (en) Standardized framework for reporting archived legacy system data
CN108337320A (en) The system and method being distributed for expansible structural data
Lydia et al. Big data analysis using hadoop components like flume, mapreduce, pig and hive
CN111026709B (en) Data processing method and device based on cluster access
CN109271871A (en) Sample store path generation method, device, computer equipment and storage medium
CN109902114A (en) ES company-data multiplexing method, system, computer installation and storage medium
US11711375B2 (en) Team member transfer tool
CN109947759A (en) A data index establishment method, index retrieval method and device
CN111259082B (en) A method to realize full data synchronization in a big data environment
US20120254105A1 (en) Synchronizing Records Between Databases
CN108549659A (en) A kind of data warehouse management system and management method
US20150095340A1 (en) Information Sets for Data Management
US12411869B2 (en) Data processing independent of storage, format or schema
CN105765570B (en) music recognition
US10296589B2 (en) Grouping content based upon user activity
CN118312469A (en) Method and device for processing delivery document
US10147061B2 (en) Integrating a construction jobsite system with external tools
CN105184550B (en) Manage method, server and the system of waiting data
US20140019410A1 (en) Using Database Content for Multiple Business Data Systems Connected to One Database
CN115952197A (en) Data query method and device
RU2690777C1 (en) Method and system for complex control of big data
US11954071B1 (en) File naming and management system

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