CN110489155B - Data file management method, device, electronic equipment and medium - Google Patents
Data file management method, device, electronic equipment and medium Download PDFInfo
- Publication number
- CN110489155B CN110489155B CN201910792397.5A CN201910792397A CN110489155B CN 110489155 B CN110489155 B CN 110489155B CN 201910792397 A CN201910792397 A CN 201910792397A CN 110489155 B CN110489155 B CN 110489155B
- Authority
- CN
- China
- Prior art keywords
- data file
- processed
- target account
- processing result
- account
- 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.)
- Active
Links
- 238000007726 management method Methods 0.000 title claims abstract description 43
- 238000012545 processing Methods 0.000 claims abstract description 93
- 238000000034 method Methods 0.000 claims abstract description 33
- 230000004048 modification Effects 0.000 claims description 61
- 238000012986 modification Methods 0.000 claims description 61
- 238000010200 validation analysis Methods 0.000 claims description 12
- 230000008569 process Effects 0.000 claims description 10
- 238000004891 communication Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000001133 acceleration Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The disclosure relates to a data file management method, a device, an electronic device and a medium, and relates to the technical field of computers, wherein the method can simplify the management of data files, and an embodiment of the disclosure comprises the following steps: and acquiring the data file to be processed, and then determining at least one target account corresponding to the data file to be processed based on a preset authority database. And sending the data file to be processed to at least one target account based on the authority of the at least one target account, and receiving a processing result of the data file to be processed by the at least one target account. The processed data file is then generated based on the at least one processing result.
Description
Technical Field
The disclosure relates to the field of computer technology, and in particular, to a data file management method, a device, an electronic device and a medium.
Background
Currently, a management method for data files (such as audio, video and documents) generally decouples the data files into multiple groups, and then each general responsible person is responsible for managing one group of data files. When managing the data files, the general responsible person needs to determine responsible persons corresponding to all parts in the group of data files, and all responsible persons manage a part of the data files. Because the responsible person corresponding to each part needs to manually determine, and the data files need to be decoupled when being managed, and the decoupled data files need to be integrated after the management is completed, the management method of the data files is complex.
For example: in the software development process, the software code needs to be continuously modified in order to repair and update the software. The software code is typically decoupled into individual module codes according to the differences in function, one module code being stored in each code repository, forming a plurality of code repositories for the software code. Each code repository is responsible for a general responsible person who can be assigned to an examiner to examine the modified codes in one code repository.
After a user modifies part of codes in a plurality of code warehouses of a software code, each modified code warehouse needs to be submitted to a total responsible person corresponding to each code warehouse, then the total responsible person distributes the censor to censor the code warehouses, and after each censor passes censor, the codes in each code warehouse need to be integrated, and the modified codes can normally run.
However, since the code warehouse is differentiated according to functions, the amount of code data for realizing one function is large, and the responsible person needs to distribute the modified code to the examiner who is most aware of the part of code for examination. After each code warehouse is checked, the codes in each code warehouse are integrated so as to realize the normal operation of the software corresponding to the software codes. Therefore, in the related art, the management method for the software code is complicated.
Disclosure of Invention
The disclosure provides a data file management method, a device, an electronic device and a medium, so as to at least solve the problem that a management method of data files in related technologies is complex. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a data file management method, including:
acquiring a data file to be processed;
determining at least one target account corresponding to the data file to be processed based on a preset authority database;
transmitting the data file to be processed to the at least one target account based on the authority of the at least one target account, and receiving a processing result of the at least one target account on the data file to be processed;
and generating a processed data file based on at least one processing result.
Optionally, the data file to be processed is a modified data file to be processed;
the generating a processed data file based on at least one of the processing results includes: a determination is made as to whether modification of the modified data file to be processed is effective.
Optionally, the determining, based on the predetermined authority database, at least one target account corresponding to the data file to be processed includes:
searching a target account corresponding to a first path of the data file to be processed from the preset authority database, wherein the preset authority database comprises paths of a plurality of data files and accounts corresponding to each path.
Optionally, the sending the data file to be processed to the at least one target account based on the authority of the at least one target account, and receiving a processing result of the at least one target account on the data file to be processed, includes:
determining a target account with the lowest account authority level as a first target account based on the authority of the at least one target account, wherein the target account with the lowest account authority level is an account corresponding to a leaf node in the first path;
step two, the data file to be processed is sent to the first target account;
step three, receiving a processing result of the first target account on the data file to be processed, wherein the processing result of the first target account on the data file to be processed comprises modification validation or modification non-validation;
and step four, when the processing result of the first target account on the data file to be processed is that the modification is effective, determining the last target account of the first target account in the first path as the first target account, and returning to the step two.
Optionally, the generating the processed data file based on at least one processing result includes:
if the at least one processing result is modification effective, determining that the modification of the modified data file to be processed is effective;
and if the at least one processing result comprises a processing result with the modification not effective, determining that the modification of the modified data file to be processed is not effective.
Optionally, after the sending the pending data file to the first target account, the method further includes:
if the processing result of the first target account on the data file to be processed is not received after the preset time period is elapsed, prompt information is sent to the first target account, and the prompt information is used for prompting the first target user to process the data file to be processed.
According to a second aspect of the embodiments of the present disclosure, there is provided a data file management apparatus comprising:
the acquisition module is configured to acquire a data file to be processed;
the determining module is configured to determine at least one target account corresponding to the data file to be processed, which is acquired by the acquiring module, based on a preset authority database;
the receiving and transmitting module is configured to send the data file to be processed to the at least one target account based on the authority of the at least one target account determined by the determining module, and receive a processing result of the at least one target account on the data file to be processed;
and the generating module is configured to generate a processed data file based on at least one processing result received by the receiving and transmitting module.
Optionally, the data file to be processed is a modified data file to be processed;
the generation module is specifically configured to: a determination is made as to whether modification of the modified data file to be processed is effective.
Optionally, the determining module is specifically configured to:
searching a target account corresponding to a first path of the data file to be processed from the preset authority database, wherein the preset authority database comprises paths of a plurality of data files and accounts corresponding to each path.
Optionally, the transceiver module is specifically configured to:
determining a target account with the lowest account authority level as a first target account based on the authority of the at least one target account, wherein the target account with the lowest account authority level is an account corresponding to a leaf node in the first path;
step two, the data file to be processed is sent to the first target account;
step three, receiving a processing result of the first target account on the data file to be processed, wherein the processing result of the first target account on the data file to be processed comprises modification validation or modification non-validation;
and step four, when the processing result of the first target account on the data file to be processed is that the modification is effective, determining the last target account of the first target account in the first path as the first target account, and returning to the step two.
Optionally, the generating module is specifically configured to:
if the at least one processing result is modification effective, determining that the modification of the modified data file to be processed is effective;
and if the at least one processing result comprises a processing result with the modification not effective, determining that the modification of the modified data file to be processed is not effective.
Optionally, the transceiver module is further configured to: after the data file to be processed is sent to the first target account, if a processing result of the first target account on the data file to be processed is not received after a preset time period is elapsed, prompt information is sent to the first target account, and the prompt information is used for prompting the first target user to process the data file to be processed.
According to a third aspect of embodiments of the present disclosure, there is provided a data file management electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to: when executing the instructions stored on the memory, the data file management method according to the first aspect is implemented.
According to a fourth aspect of embodiments of the present application, there is provided a non-transitory computer readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the data file management method as described in the first aspect above.
According to a fifth aspect of embodiments of the present application, there is provided a computer program product, which when executed by a processor of an electronic device, enables the electronic device to perform the data file management method as described in the first aspect above.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: the method and the device can send the data file to be processed to the target account for processing, and generate the processed file according to the processing result of the data file to be processed by the target account. Therefore, the method and the device can automatically determine the target account with the processing authority of the data file to be processed, and the data file is not required to be decoupled and split into a plurality of groups, so that the data file is not required to be integrated after the data file to be processed is processed. Embodiments of the present disclosure simplify the method of managing data files.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is a flowchart illustrating a method of data file management according to an exemplary embodiment;
FIG. 2 is a flowchart illustrating another method of data file management according to an exemplary embodiment;
FIG. 3 is a schematic diagram of a directory tree, shown in accordance with an exemplary embodiment;
FIG. 4 is a block diagram of a data file management apparatus according to an exemplary embodiment;
fig. 5 is a block diagram of an electronic device, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
Fig. 1 is a flowchart illustrating a data file management method according to an exemplary embodiment, and as shown in fig. 1, the data file management method is used in an electronic device, where the electronic device may be a terminal (e.g., a mobile phone, a computer, or a tablet computer) or a server. The method may comprise the steps of:
in step S11, a data file to be processed is acquired.
Alternatively, the data file to be processed may be a file or a folder in an overall data file.
For example, the whole data file may be a software code, and a part file (or folder) with different codes may be used as the data file to be processed by comparing the modified software code with the software code before modification.
Embodiments of the present disclosure may split a software code into respective files and folders, and may divide the software code into finer granularity because a module code of one function includes a large number of files and folders than a module code divided according to a function in the related art.
In step S12, at least one target account corresponding to the data file to be processed is determined based on the predetermined authority database.
Alternatively, the overall data file may correspond to a directory tree, as shown in FIG. 3. Each node of the directory tree corresponds to a file or folder of the overall data file, i.e. each file and folder comprised by the data file corresponds to a directory entry of the directory tree. And configuring authority accounts for the preset partial nodes, wherein a preset configuration authority list corresponding to the whole data file in the preset authority database is shown in a first table.
List one
| Path of data file to be processed | Account account |
| Root directory | 0 |
| Data file C corresponding node | 1 |
| Data file B corresponding node | 2 |
| Data file H corresponding node | 3 |
The authority account at a certain node has processing authority on files or folders at the node position of the authority account in the directory tree and all node positions below the authority account. For example, account 3 has processing rights for data file H, I, O, account 2 has data rights for data file B, E, F, G, H, I, O, and so on.
The path of each file or folder is the path of its corresponding directory entry.
Optionally, the configuration permission list includes paths of a plurality of files and/or folders in the whole data file, and accounts corresponding to each path.
In one embodiment, a target account corresponding to a path of the data file to be processed may be determined according to accounts corresponding to paths included in the configuration permission list.
For example, if the data file to be processed is the data file C, the corresponding first path is: root directory→c, corresponding target account is: account 0 and account 1.
In step S13, the data file to be processed is sent to the at least one target account based on the authority of the at least one target account, and the processing result of the data file to be processed by the at least one target account is received.
It can be appreciated that a user logging into a target account can process a data file to be processed and send a processing result to the electronic device.
In one embodiment, a link may be sent to the target account, the information pointed to by the link including: a data file to be processed and a specified file corresponding to the data file to be processed. And then receiving a processing result sent by the target account aiming at the data file to be processed.
For example, when the data file to be processed is a modified file included in the software code, the specified file corresponding to the data file to be processed may be a file before modification corresponding to the file. The user logging in the target account may process the data file to be processed in order to check whether the modification of the file to be processed is effective.
Optionally, a prompt message may also be sent to the target account, where the prompt message is used to describe the information pointed by the link.
In step S14, a processed data file is generated based on at least one processing result.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects: the method and the device can send the data file to be processed to the target account for processing, and generate the processed file according to the processing result of the data file to be processed by the target account. Therefore, the method and the device can automatically determine the target account with the processing authority of the data file to be processed, and the data file is not required to be decoupled and split into a plurality of groups, so that the data file is not required to be integrated after the data file to be processed is processed. Embodiments of the present disclosure simplify the method of managing data files.
Optionally, the determining the target account in step S12 includes: and searching a target account corresponding to the first path of the data file to be processed from a preset authority database. The preset authority database comprises paths of a plurality of data files and accounts corresponding to each path.
For example: in connection with fig. 3 and table one, assume that the data file to be processed is file O, and the first path of the data file to be processed is: root directory → B → F → H → O, corresponding target account is: account 0, account 2, and account 3.
Optionally, when the target account is a plurality of accounts, in the step S13, the data files to be processed may be sequentially sent to each target account according to the account authority level, see fig. 2, and the steps include:
in step S21, the target account with the lowest account authority level is determined as the first target account based on the authority of at least one target account.
The target account with the lowest account authority level is an account corresponding to the leaf node in the first path.
For example, in connection with fig. 3 and table one, the first path is: the target account with the lowest account authority level is the account 3 corresponding to the leaf node O. It can be understood that the account corresponding to the leaf node O is an account having the management authority to the node O, and the corresponding node is closest to the node O.
In step S22, a data file to be processed is sent to the first target account.
In step S23, a processing result of the data file to be processed by the first target account is received.
The processing result of the data file to be processed by the first target account comprises modification validation or modification non-validation.
In step S24, when the modification is effective for the processing result of the data file to be processed by the first target account, determining the previous target account of the first target account in the first path as the first target account. And returns to step S22.
For example, in connection with fig. 3 and table one, the first path is: root directory → B → F → H → O, and the first target account is account 3, then the last level target account of the first target account is account 2. The account 2 is determined as the first target account, and returns to step S22.
In step S25, when the modification is effective in the processing result of the data file to be processed by the first target account and the first target account is the highest account authority level, the data file to be processed is not sent.
In step S26, when the modification is not effective as the result of the processing of the data file to be processed by the first target account, the data file to be processed is not sent.
The following is exemplified in connection with step S21-step S26 and fig. 3. Assuming that the data file to be processed is a file O, a first path of the file O is: root directory → B → F → H → O. The target account includes: account 0, account 2 and account 3, and the first target account is account 3, so the data file to be processed is sent to account 3, and then the processing result of the data file to be processed by account 3 is received. When the processing result of the account 3 to-be-processed data file is that the modification is effective, the to-be-processed data file is sent to the account 2, and then the processing result of the account 2 to-be-processed data file is received. When the processing result of the account 2 to-be-processed data file is that the modification is effective, the to-be-processed data file is sent to the account 0, and then the processing result of the account 0 to-be-processed data file is received.
Embodiments of the present disclosure may also bring the following benefits: in the embodiment of the disclosure, the target file to be processed may be sent to the target account step by step, and when the processing result of the data file to be processed by the first target account is that the modification is effective, the file to be processed may be sent to the target account at the upper level of the first target account. And when the processing result of the data file to be processed by the first target account is that the modification is not effective, the file to be processed is not sent to the previous target account of the first target account. Compared with the mode of simultaneously sending the data files to be processed to each target account, the method and the device can reduce unnecessary processing times and labor cost.
Alternatively, the data file to be processed may be a modified data file to be processed. The generating of the processed data file in step S14 may include: it is determined whether a modification of the modified data file to be processed is effective.
The manner in which the modification of the modified data file to be processed is determined to be effective may include the following two cases:
in the first case, if at least one processing result is that the modification is effective, the modification of the modified data file to be processed is determined to be effective.
And in the second case, if at least one processing result comprises a processing result with the modification not effective, determining that the modification of the modified data file to be processed is not effective.
Embodiments of the present disclosure may also bring the following benefits: because in the embodiment of the disclosure, the modification of the data file requires the target account to be processed, only after the modification is effective, the modified data file will be effective. Embodiments of the present disclosure may reduce the loss of data files after they have been modified by mistake.
Optionally, after sending the data file to be processed to the first target account, a prompt message may also be sent to the first target account, including: and if the processing result of the data file to be processed by the first target account is not received after the preset time length is passed, sending prompt information to the first target account. The prompt information is used for prompting the first target user to process the data file to be processed.
It will be appreciated that the prompt may take the form of a picture and/or text. The prompt information is used for indicating that the prompt target account processes the data file to be processed and also comprises the data file to be processed.
Embodiments of the present disclosure may also bring the following benefits: the method and the device can automatically determine the target account for processing the data files to be processed, and the account corresponding to the path of each file and the path of the folder in the configuration permission list are preset, so that the accuracy of determining the target account can be improved.
In addition, the embodiment of the disclosure does not need to split the data files into a plurality of groups after decoupling and integrate the decoupled plurality of groups of files after management is completed, so that the embodiment of the disclosure shortens the management flow of the data files and improves the efficiency of data file management.
Corresponding to the above-described method embodiment, fig. 4 is a block diagram of a data file management apparatus according to an exemplary embodiment. Referring to fig. 4, the apparatus includes: an acquisition module 401, a determination module 402, a transceiver module 403 and a generation module 404.
An acquisition module 401 configured to acquire a data file to be processed;
a determining module 402, configured to determine, based on a predetermined authority database, at least one target account corresponding to the data file to be processed acquired by the acquiring module 401;
a transceiver module 403 configured to send a data file to be processed to at least one target account based on the authority of the at least one target account determined by the determining module 402, and receive a processing result of the data file to be processed by the at least one target account;
a generating module 404 configured to generate a processed data file based on at least one processing result received by the transceiving module 403.
Optionally, the data file to be processed is a modified data file to be processed;
the generation module 404 may be specifically configured to: it is determined whether a modification of the modified data file to be processed is effective.
Optionally, the determining module 402 may be specifically configured to:
searching a target account corresponding to a first path of the data file to be processed from a preset authority database, wherein the preset authority database comprises paths of a plurality of data files and accounts corresponding to each path.
Optionally, the transceiver module 403 may be specifically configured to:
determining a target account with the lowest account authority level as a first target account based on the authority of at least one target account, wherein the target account with the lowest account authority level is an account corresponding to a leaf node in a first path;
step two, sending a data file to be processed to a first target account;
step three, receiving a processing result of the data file to be processed of the first target account, wherein the processing result of the data file to be processed of the first target account comprises modification validation or modification non-validation;
and step four, when the processing result of the data file to be processed by the first target account is that the modification is effective, determining the last target account of the first target account in the first path as the first target account, and returning to the step two.
Optionally, the generating module 404 may be specifically configured to:
if at least one processing result is modification effective, determining that the modification of the modified data file to be processed is effective;
and if the at least one processing result comprises a processing result with the modification not effective, determining that the modification of the modified data file to be processed is not effective.
Optionally, the transceiver module 403 may be further configured to: after the data file to be processed is sent to the first target account, if the processing result of the data file to be processed by the first target account is not received after the preset time length is elapsed, prompt information is sent to the first target account, and the prompt information is used for prompting the first target user to process the data file to be processed.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
FIG. 5 is a block diagram illustrating an electronic device for data file management in accordance with an exemplary embodiment. For example, the electronic device may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 5, the electronic device may include one or more of the following components: a processing component 502, a memory 504, a power supply component 506, a multimedia component 508, an audio component 510, an input/output (I/O) interface 512, a sensor component 514, and a communication component 516.
The processing component 502 generally controls overall operation of the electronic device, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 502 may include one or more processors 520 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 502 can include one or more modules that facilitate interactions between the processing component 502 and other components. For example, the processing component 502 can include a multimedia module to facilitate interaction between the multimedia component 508 and the processing component 502.
The memory 504 is configured to store various types of data to support operations at the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phonebook data, messages, pictures, video, and the like. The memory 504 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power supply component 506 provides power to the various components of the electronic device. The power components 506 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the electronic device.
The multimedia component 508 includes a screen between the electronic device and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 508 includes a front-facing camera and/or a rear-facing camera. When the electronic device is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 510 is configured to output and/or input audio signals. For example, the audio component 510 includes a Microphone (MIC) configured to receive external audio signals when the electronic device is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 504 or transmitted via the communication component 516. In some embodiments, the audio component 510 further comprises a speaker for outputting audio signals.
The I/O interface 512 provides an interface between the processing component 502 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 514 includes one or more sensors for providing status assessment of various aspects of the electronic device. For example, the sensor assembly 514 may detect an on/off state of the electronic device, a relative positioning of the components, such as a display and keypad of the electronic device, the sensor assembly 514 may also detect a change in position of the electronic device or a component of the electronic device, the presence or absence of a user contact with the electronic device, the orientation or acceleration/deceleration of the electronic device, and a change in temperature of the electronic device. The sensor assembly 514 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 514 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 514 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 516 is configured to facilitate communication between the electronic device and other devices, either wired or wireless. The electronic device may access a wireless network based on a communication standard, such as WiFi, an operator network (e.g., 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 516 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 516 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the electronic device may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a storage medium is also provided, such as a memory 504 including instructions executable by the processor 520 of the electronic device to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
In yet another embodiment provided by the present disclosure, there is also provided a computer program product containing instructions that, when run on an electronic device, cause the electronic device to perform any of the data file management methods of the above embodiments.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (12)
1. A method of managing data files, comprising:
acquiring a data file to be processed, wherein the data file to be processed is one file or one folder in an overall data file, the overall data file corresponds to a directory tree, and each file and each folder included in the overall data file respectively correspond to one directory entry of the directory tree;
determining at least one target account corresponding to the data file to be processed based on a preset authority database;
transmitting the data file to be processed to the at least one target account based on the authority of the at least one target account, and receiving a processing result of the at least one target account on the data file to be processed;
generating a processed data file based on at least one of the processing results;
the determining at least one target account corresponding to the data file to be processed based on a predetermined authority database comprises the following steps:
searching a target account corresponding to a first path of the data file to be processed from the preset authority database, wherein the preset authority database comprises paths of a plurality of data files and accounts corresponding to each path, and the first path is a path of a directory entry corresponding to the data file to be processed.
2. The data file management method according to claim 1, wherein the data file to be processed is a modified data file to be processed;
the generating a processed data file based on at least one of the processing results includes: a determination is made as to whether modification of the modified data file to be processed is effective.
3. The method according to claim 1, wherein the sending the data file to be processed to the at least one target account based on the authority of the at least one target account, and receiving the processing result of the data file to be processed by the at least one target account, includes:
determining a target account with the lowest account authority level as a first target account based on the authority of the at least one target account, wherein the target account with the lowest account authority level is an account corresponding to a leaf node in the first path;
step two, the data file to be processed is sent to the first target account;
step three, receiving a processing result of the first target account on the data file to be processed, wherein the processing result of the first target account on the data file to be processed comprises modification validation or modification non-validation;
and step four, when the processing result of the first target account on the data file to be processed is that the modification is effective, determining the last target account of the first target account in the first path as the first target account, and returning to the step.
4. A data file management method according to claim 2 or 3, wherein said generating a processed data file based on at least one of said processing results comprises:
if the at least one processing result is modification effective, determining that the modification of the modified data file to be processed is effective;
and if the at least one processing result comprises a processing result with the modification not effective, determining that the modification of the modified data file to be processed is not effective.
5. A data file management method in accordance with claim 3, wherein after said sending the pending data file to the first target account, the method further comprises:
if the processing result of the first target account on the data file to be processed is not received after the preset time period is elapsed, prompt information is sent to the first target account, and the prompt information is used for prompting the first target user to process the data file to be processed.
6. A data file management apparatus, comprising:
the system comprises an acquisition module, a processing module and a storage module, wherein the acquisition module is configured to acquire a data file to be processed, the data file to be processed is one file or one folder in an overall data file, the overall data file corresponds to a directory tree, and each file and each folder included in the overall data file respectively correspond to one directory entry of the directory tree;
the determining module is configured to determine at least one target account corresponding to the data file to be processed, which is acquired by the acquiring module, based on a preset authority database;
the receiving and transmitting module is configured to send the data file to be processed to the at least one target account based on the authority of the at least one target account determined by the determining module, and receive a processing result of the at least one target account on the data file to be processed;
a generating module configured to generate a processed data file based on at least one of the processing results received by the transceiving module;
the determining module is specifically configured to:
searching a target account corresponding to a first path of the data file to be processed from the preset authority database, wherein the preset authority database comprises paths of a plurality of data files and accounts corresponding to each path, and the first path is a path of a directory entry corresponding to the data file to be processed.
7. The data file management apparatus according to claim 6, wherein said data file to be processed is a modified data file to be processed;
the generation module is specifically configured to: a determination is made as to whether modification of the modified data file to be processed is effective.
8. The data file management apparatus of claim 6, wherein the transceiver module is specifically configured to:
determining a target account with the lowest account authority level as a first target account based on the authority of the at least one target account, wherein the target account with the lowest account authority level is an account corresponding to a leaf node in the first path;
step two, the data file to be processed is sent to the first target account;
step three, receiving a processing result of the first target account on the data file to be processed, wherein the processing result of the first target account on the data file to be processed comprises modification validation or modification non-validation;
and step four, when the processing result of the first target account on the data file to be processed is that the modification is effective, determining the last target account of the first target account in the first path as the first target account, and returning to the step two.
9. The data file management apparatus according to claim 7 or 8, wherein said generating module is specifically configured to:
if the at least one processing result is modification effective, determining that the modification of the modified data file to be processed is effective;
and if the at least one processing result comprises a processing result with the modification not effective, determining that the modification of the modified data file to be processed is not effective.
10. The data file management apparatus of claim 8, wherein,
the transceiver module is further configured to: after the data file to be processed is sent to the first target account, if a processing result of the first target account on the data file to be processed is not received after a preset time period is elapsed, prompt information is sent to the first target account, and the prompt information is used for prompting the first target user to process the data file to be processed.
11. A data file management electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the data file management method of any of claims 1 to 5.
12. A storage medium, which when executed by a processor of a data file management electronic device, causes the data file management electronic device to perform the data file management method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910792397.5A CN110489155B (en) | 2019-08-26 | 2019-08-26 | Data file management method, device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910792397.5A CN110489155B (en) | 2019-08-26 | 2019-08-26 | Data file management method, device, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110489155A CN110489155A (en) | 2019-11-22 |
| CN110489155B true CN110489155B (en) | 2024-01-09 |
Family
ID=68554117
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910792397.5A Active CN110489155B (en) | 2019-08-26 | 2019-08-26 | Data file management method, device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110489155B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112181480A (en) * | 2020-09-29 | 2021-01-05 | 北京达佳互联信息技术有限公司 | Authority management method and device of version management system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108346028A (en) * | 2017-01-24 | 2018-07-31 | 阿里巴巴集团控股有限公司 | A kind of business approval processing method, apparatus and system |
| CN108763393A (en) * | 2018-05-21 | 2018-11-06 | 平安科技（深圳）有限公司 | Book management method, device, computer equipment and storage medium |
| CN109408476A (en) * | 2018-09-19 | 2019-03-01 | 腾讯科技（深圳）有限公司 | A kind of file-sharing management method, equipment and storage medium |
| CN109460252A (en) * | 2018-09-25 | 2019-03-12 | 中国平安人寿保险股份有限公司 | Configuration file processing method, device and computer equipment based on git |
| CN109471849A (en) * | 2018-10-12 | 2019-03-15 | 中国平安人寿保险股份有限公司 | Model treatment method and device, storage medium and electronic equipment |
| CN109767356A (en) * | 2018-12-14 | 2019-05-17 | 广东建邦计算机软件股份有限公司 | Hidden danger information processing method, device, computer equipment and storage medium |
| CN110083573A (en) * | 2019-04-30 | 2019-08-02 | 维沃移动通信有限公司 | A kind of file management method and mobile terminal |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060101443A1 (en) * | 2004-10-25 | 2006-05-11 | Jim Nasr | Source code management system and method |
| CN101282330B (en) * | 2007-04-04 | 2013-08-28 | 华为技术有限公司 | Method and apparatus for managing network memory access authority, network memory access control method |
-
2019
- 2019-08-26 CN CN201910792397.5A patent/CN110489155B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108346028A (en) * | 2017-01-24 | 2018-07-31 | 阿里巴巴集团控股有限公司 | A kind of business approval processing method, apparatus and system |
| CN108763393A (en) * | 2018-05-21 | 2018-11-06 | 平安科技（深圳）有限公司 | Book management method, device, computer equipment and storage medium |
| CN109408476A (en) * | 2018-09-19 | 2019-03-01 | 腾讯科技（深圳）有限公司 | A kind of file-sharing management method, equipment and storage medium |
| CN109460252A (en) * | 2018-09-25 | 2019-03-12 | 中国平安人寿保险股份有限公司 | Configuration file processing method, device and computer equipment based on git |
| CN109471849A (en) * | 2018-10-12 | 2019-03-15 | 中国平安人寿保险股份有限公司 | Model treatment method and device, storage medium and electronic equipment |
| CN109767356A (en) * | 2018-12-14 | 2019-05-17 | 广东建邦计算机软件股份有限公司 | Hidden danger information processing method, device, computer equipment and storage medium |
| CN110083573A (en) * | 2019-04-30 | 2019-08-02 | 维沃移动通信有限公司 | A kind of file management method and mobile terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110489155A (en) | 2019-11-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108304475B (en) | Data query method and device and electronic equipment | |
| US20170150290A1 (en) | Method and device for information push | |
| EP3041204A1 (en) | Method for prompting calling request and device for the same | |
| CN106445189B (en) | Candidate word display method and device | |
| CN106919629B (en) | Method and device for realizing information screening in group chat | |
| US10324910B2 (en) | Contact record processing method and apparatus | |
| CN109255128B (en) | Multi-level label generation method, device and storage medium | |
| CN104850643B (en) | Picture comparison method and device | |
| CN110489155B (en) | Data file management method, device, electronic equipment and medium | |
| CN110764847B (en) | User information processing method, device, electronic equipment and storage medium | |
| CN112862349B (en) | Data processing method, device and equipment based on ABS service data | |
| CN107257384B (en) | Service state monitoring method and device | |
| CN107295144B (en) | Method and device for deleting contact number | |
| CN113191792B (en) | Task processing method, device, electronic equipment, storage medium and program product | |
| CN110708427A (en) | Information processing method, device and storage medium | |
| CN112988822B (en) | Data query method, device, equipment, readable storage medium and product | |
| CN114422811B (en) | Method, device, equipment and storage medium for task allocation and task template generation | |
| CN113778385B (en) | Component registration method, device, terminal and storage medium | |
| CN114238728B (en) | Vehicle data processing method, device and equipment | |
| CN111221512B (en) | Function module mixed use method, electronic device and storage medium | |
| CN107728909B (en) | Information processing method and device | |
| CN116643673A (en) | Information collection method, device and equipment | |
| CN114416038A (en) | Code branch processing method and device, electronic equipment and storage medium | |
| CN117093486A (en) | Interface testing method, device, equipment and storage medium | |
| CN114169976A (en) | Financial data recommendation method, device and equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |