CN112905533B - File submission management method, device, equipment and storage medium - Google Patents
File submission management method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112905533B CN112905533B CN202110167637.XA CN202110167637A CN112905533B CN 112905533 B CN112905533 B CN 112905533B CN 202110167637 A CN202110167637 A CN 202110167637A CN 112905533 B CN112905533 B CN 112905533B
- Authority
- CN
- China
- Prior art keywords
- file
- target
- field
- user
- authority
- 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 description 59
- 238000013507 mapping Methods 0.000 claims abstract description 56
- 238000000034 method Methods 0.000 claims abstract description 39
- 230000000977 initiatory effect Effects 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 9
- 230000006399 behavior Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 11
- 238000011161 development Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000001105 regulatory effect Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003449 preventive effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/122—File system administration, e.g. details of archiving or snapshots using management policies
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/113—Details of archiving
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- Automation & Control Theory (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Storage Device Security (AREA)
Abstract
The embodiment of the invention discloses a method, a device, equipment and a storage medium for managing file submission, wherein the method comprises the following steps: receiving a file submitting request of a user; searching a file authority table recorded in the locking working area by utilizing the target file identifier, and determining whether a first target file authority table of the target file exists or not; if the first target file authority table is determined to be absent, a target public environment mapping table of the target file is obtained by using the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file authority field and a second locker field; and judging whether the target user has the right to submit the target file according to the file authority field and the second locker field. Through the authority records of the files in the file authority table and the public environment mapping table, the file submission is accurately managed in a two-stage double management and control mode, the file submission accuracy to be submitted is improved, and the files in the database caused by the current file submission are effectively prevented from being tampered.
Description
Technical Field
The present invention relates to the field of file management technologies, and in particular, to a method, an apparatus, a device, and a storage medium for managing file submission.
Background
With the rapid development of the internet, server technologies such as distributed services and cloud services are widely used, for example: the implementation of the technology such as program or website development, file sharing and the like does not bypass the link that the file is submitted to the sharing server from the local environment in the testing and publishing processes.
When a program or website is developed, updated or iterated, a team is often required to participate in the development, and when multiple persons develop the same function or file, the situation that the same file is modified by two persons at the same time is avoided, and when the two persons submit the modified file from a local environment to a public environment, the file of the first submitter is always covered by the file of the second submitter or the file content submitted by the first submitter is tampered, so that the file of the public environment is disordered after the files are submitted by the multiple persons, and the function which the first submitter wants to realize is affected.
Disclosure of Invention
The invention mainly aims to provide a file submission management method, a file submission management device, computer equipment and a storage medium, which can solve the problem that file contents are disordered after a plurality of people submit the same file in the prior art.
To achieve the above object, a first aspect of the present invention provides a method for managing file submission, the method including:
Receiving a file submitting request of a user side, wherein the file submitting request comprises a target user identifier of a target user initiating the request and a target file identifier of a target file to be submitted;
searching a file authority table recorded in a locking working area by utilizing the target file identifier, and determining whether a first target file authority table of the target file exists or not, wherein the file authority table comprises a first file identifier field of a locked file, a first locker field and an assisted field, the first locker field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the assisted field is used for recording an assisted user identifier of at least one assisted user which is introduced into the locking working area by an authorized user corresponding to the first authorized user identifier;
if the first target file authority table does not exist, acquiring a target public environment mapping table of the target file by utilizing the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file authority field and a second locker field, the file authority field is used for recording the management state of an administrator on the file, the second locker field is used for recording a second authorized user identifier which is appointed by the administrator and is authorized to submit the locked file, and the management state of the file comprises a first management state which is locked by the administrator and can be checked by a user, a second management state which is locked by the administrator and cannot be checked by the user and a third management state which is not locked by the administrator;
And judging whether the target user has the right to submit the target file according to the file authority field and the second locker field.
In an optional implementation manner, the determining, according to the file authority field and the second locker field, whether the target user has authority to submit the target file includes:
if the file authority field is detected to be in a first control state or a second control state or the second locker field is not empty, determining that the target user is not authorized to submit the target file;
and if the file authority field is detected to be in the third control state and the second locking person field is detected to be empty, determining that the target user is authorized to submit the target file.
In an optional implementation manner, if it is detected that the file authority field is in the first control state or the second control state, or the second locking person field is not null, it is determined that the target user does not have the right to submit the target file, and then the method further includes:
if a locking request of the user side to the target file is received, a second target file permission table corresponding to the target file is added in the file permission table recorded in the locking work area, and a user identification initiating locking is recorded in a first locking person field and an assisting person field of the second target file permission table.
In an alternative embodiment, the method further comprises:
if the first target file permission table is determined to exist, acquiring the first target file permission table;
and judging whether the target user has the right to submit the target file or not by using the first locker field, the helper field and the target user identifier.
In an optional implementation manner, the determining whether the target user has the right to submit the target file by using the first locker field, the helper field and the target user identifier includes:
if the target user identification is detected to be matched with the first locker field or the helper field, determining that the target user is authorized to submit the target file;
and if the target user identification is not matched with the first locker field and the helper field, determining that the target user is not authorized to submit the target file.
In an optional implementation manner, the receiving the file submitting request of the user side further includes:
after determining that the target user logs in the user terminal, determining a permission prompt message according to the corresponding relation between the target user identifier and the permission of the file in the preset database, and outputting the permission prompt message to the user terminal.
In an alternative embodiment, the determining whether the target user has the right to submit the target file further includes:
generating a submitting record, a difference record and a file state record of the target file in real time, and storing the submitting record, the difference record and the file state record of the target file into a behavior log of a preset database, wherein the submitting record is used for recording the submitting time and the submitting user of the target file, the difference record is used for recording the difference position between the current submitting of the target file and the previous submitting of the target file in a pointer mode, and the file state record is used for recording the authority states of the file in real time, including a locked state, a locking release state and an unlocked state.
To achieve the above object, a second aspect of the present invention provides a management apparatus for file submission, the apparatus comprising:
a request receiving module: the file submitting method comprises the steps of receiving a file submitting request of a user side, wherein the file submitting request comprises a target user identifier of a target user initiating the request and a target file identifier of a target file to be submitted;
a first acquisition module: the method comprises the steps that a file authority table recorded in a locking working area is searched by utilizing the target file identifier, whether a first target file authority table of the target file exists or not is determined, the file authority table comprises a first file identifier field of a locked file, a first locker field and an assisted field, the first locker field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the assisted field is used for recording an assisted user identifier of at least one assisted user which is introduced into the locking working area by an authorized user corresponding to the first authorized user identifier;
And a second acquisition module: if the first target file permission table does not exist, acquiring a target public environment mapping table of the target file by utilizing the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file permission field and a second locker field, the file permission field is used for recording the management state of an administrator on the file, the second locker field is used for recording a second authorized user identifier which is appointed by the administrator and is authorized to submit the locked file, and the management state of the file comprises a first management state which is locked by the administrator and can be checked by a user, a second management state which is locked by the administrator and cannot be checked by the user and a third management state which is not locked by the administrator;
and a submission management module: and the target user is used for judging whether the target user has the right to submit the target file according to the file authority field and the second locker field.
To achieve the above object, a third aspect of the present invention provides a computer readable storage medium storing a computer program, which when executed by a processor causes the processor to perform the steps as described in the first aspect and any possible implementation manner.
To achieve the above object, a fourth aspect of the present invention provides a computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps as described in the first aspect and any possible implementation manner.
The embodiment of the invention has the following beneficial effects:
the embodiment of the invention discloses a file submission management method, which comprises the following steps: receiving a file submitting request of a user; searching a file authority table recorded in the locking working area by utilizing the target file identifier, and determining whether a first target file authority table of the target file exists or not; if the first target file authority table is determined to be absent, a target public environment mapping table of the target file is obtained by using the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file authority field and a second locker field; and judging whether the target user has the right to submit the target file according to the file authority field and the second locker field. The file authority states recorded in the file authority table and the public environment mapping table are used for realizing accurate management of file submission in a two-stage double management and control mode, so that the file submission accuracy to be submitted is improved, and the file in the database is effectively prevented from being tampered due to the current file submission.
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.
Wherein:
FIG. 1 is a flow chart of a method for managing file submission according to an embodiment of the invention;
FIG. 2 is a schematic diagram illustrating an operation mode of a management program for file submission according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a field format according to an embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating an internal operation mode of a file submission manager according to an embodiment of the invention;
FIG. 5 is a flowchart illustrating another method for managing file submission according to an embodiment of the present invention;
FIG. 6 is a block diagram illustrating a file submission management apparatus according to an embodiment of the present invention;
fig. 7 is a block diagram of a computer device in an embodiment of the invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for managing file submission according to an embodiment of the present invention, where the method shown in fig. 1 includes:
the user identification is a unique identity of the user; the file identity is the unique identity of the file.
It can be understood that when a file submitting request of the user side is received, unique identification of the user initiating the request and the file to be submitted can also be obtained.
In the embodiment of the present invention, please refer to fig. 2, fig. 2 is a schematic diagram of a working mode of a file submission management program in the embodiment of the present invention, wherein a FSMC (File synchronization management control procedure) program in fig. 2 represents the file submission management program, and the program module carries a file submission management method, as shown in fig. 2, and uses the installation and deployment of the file submission management program in local development environments 1, 2 and n of different users to connect with different public environments 1, 2 or n (as shown by arrows), so that all users in different local environments but belonging to the same project group, namely, the same public environment, can realize unified management through the file submission management program.
the file authority table comprises a first file identification field of the locked file, a first locker field and a helper field, wherein the first locker field is used for recording a first authorized user identification of the authorized file submitted to the locking, and the helper field is used for recording a helper user identification of at least one helper user, which is introduced into the locking working area, of a authorized user corresponding to the first authorized user identification.
the public environment mapping table comprises a second file identification field, a file authority field and a second locker field, wherein the file authority field is used for recording the management and control state of an administrator on a file, the second locker field is used for recording a second authorized user identification, which is designated by the administrator and is authorized to submit the locked file, of the file, and the management and control state of the file comprises a first management and control state, which is locked by the administrator and can be checked by a user, a second management and control state, which is locked by the administrator and cannot be checked by the user, and a third management and control state, which is unlocked by the administrator, of the file.
In the embodiment of the invention, the file permission tables are in one-to-one correspondence with the locking file identifications, the file permission tables recorded in the locking working area are searched through the target file identifications, and whether the file permission tables corresponding to the target file identifications exist in the file permission tables of the locking working area is searched through the target file identifications so as to determine whether a first target file permission table of the target file exists.
In a possible implementation manner, referring to fig. 3, fig. 3 is a schematic diagram of a field format in an embodiment of the present invention, where a file permission table2 includes a first file identification field that may be denoted as a file_id (int), a first file status field that may be denoted as a status (tinyint) field, a first locking person field that may be denoted as a user_id (int), and an assisting person field that may be denoted as a role (tinyint), and the contents in brackets are field types corresponding to different fields.
The locked working area is a working area which is formed by locking an unlocked file by a certain user and is relatively independent between the locked user and the locked file, and the locked user performs related operations of developing, unlocking, assisting in developing and the like files in the locked working area.
It will be appreciated that whenever the FSMC program connects a new public environment, i.e. a new project, it is necessary to specify the submitted root directory and generate a corresponding public environment mapping area, a real-time file mapping table, i.e. a public environment mapping table, of the corresponding public environment specified area and a file authority table are added in the FSMC database in synchronization.
The public environment mapping table in the FSMC database is a mapping table of a public environment database table corresponding to the project, and the public environment database table is generated when the project file is created and is used for synchronizing the file states recorded in the public environment in real time; the file authority table is a table in which a lock record of a row of files is inserted when a file is locked by a certain user, and the lock record is cleared when the user performing locking is unlocked.
In the embodiment of the invention, if the first target file permission table is determined to be absent, the file is not locked by the user, and whether the target file can be submitted or not is determined through the public environment mapping table, so that the user with the submitting permission can submit the target file to be submitted to the target project database to update the project original file in the public environment.
It should be noted that, the public environment mapping table is a real-time public environment mapping table in which real-time states of all files recorded in the public environment are mapped in the FSMC database, and when an administrator performs state management and control on any file in the public environment, the public environment mapping table is synchronously updated to the public environment file mapping table in the FSMC database.
For better understanding the relationships between users, files, public environments, and public environment mapping areas and submission management in the embodiment of the present invention, please refer to fig. 4, which is a schematic diagram of an internal operation mode of a file submission management program in the embodiment of the present invention, as shown in fig. 4, the public environment mapping areas and the corresponding public environments may perform real-time data interaction through an FTP protocol (File Transfer Protocol ) to synchronize the file states of the public environments, and when the user b locally develops an environment and the user a locally develops an environment, an FSMC program is connected to a public environment (a public environment), a mapping area of the public environment is generated on the FSMC database through the FTP transfer protocol, and a public environment mapping table and a file authority table are added in the FSMC database; as shown in FIG. 4, an arrow may represent a rights identification between a user and a file, an arrow with an X identification represents a file that the target user does not have rights to submit, and an arrow without an X identification represents a file that the target user has rights to submit; taking the file shown in the figure as an example, the file locked by the user B is a file D, E, F; the files locked by the user A are files A, B, C; the collaborative file of the user B and the user A is the assisting file which is a file Z, and the other files are authority free files, such as a file G, H, etc., so that the authority identification of the target user B and the file A, B, C is the authority identification between the user and the file, because other users lock and the user B is not an assisting person, otherwise, the authority identification between the user B and the other files is an arrow without an X identification; judging whether the permission identification arrow between the user and the file is X or not, namely when the permission is required to be submitted, preferentially judging the permission by using the record of the field in the file permission table, and when the file does not exist in the file permission table, acquiring the public environment mapping table for recording the file state in real time, judging the permission by using the record of the field in the table, wherein the specific judging process is described with reference to the related embodiment, and is not repeated.
The descriptions of fig. 4 and fig. 4 are only for illustrating the embodiments of the present invention, and are not limited to the embodiments.
In an alternative embodiment, please continue to refer to fig. 3, wherein the public environment file mapping table (i.e. public environment mapping table) table1 includes a second file identification field may be denoted as file_id (int), a directory field may be denoted as catalog (varchar), a file authority field may be denoted as open_1v (tinyint), a second file status field may be denoted as status (tinyint), a second locking person field may be denoted as lock (int), a locking date field may be denoted as lock_ date (datetime), and a domain name field may be denoted as info (text), and the contents in brackets are field types corresponding to different fields.
The file authority field is used for recording the management and control state of the file corresponding to the file identifier by the administrator, and the second locking person field records the user identifier corresponding to the user terminal with the submitting authority designated by the administrator terminal.
It should be noted that, when the content of the recording field in the public environment mapping table and the administrator perform corresponding management and control on the files in the public environment, synchronization can be implemented through FTP, including but not limited to that the administrator end adds, deletes, checks and changes the management and control state of the files in the public environment, and the administrator end designates file submission authority for any user end or performs locking right change or locking release on the files locked by any user end. By adding the secondary limit of the manager side, the stability of file submission management can be further improved.
It can be understood that when a project file is newly added in the project public environment, a row of file mapping table corresponding to the file identifier is added in the public environment file mapping table; it can be understood that when an administrator manages a certain file in the public environment, the corresponding fields in the public environment mapping table are synchronously updated in real time.
And 104, judging whether the target user has the right to submit the target file according to the file authority field and the second locker field.
The embodiment of the invention discloses a file submission management method, which comprises the following steps: receiving a file submitting request of a user; searching a file authority table recorded in the locking working area by utilizing the target file identifier, and determining whether a first target file authority table of the target file exists or not; if the first target file authority table is determined to be absent, a target public environment mapping table of the target file is obtained by using the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file authority field and a second locker field; and judging whether the target user has the right to submit the target file according to the file authority field and the second locker field. The file authority states recorded in the file authority table and the public environment mapping table are used for realizing accurate management of file submission in a two-stage double management and control mode, so that the file submission accuracy to be submitted is improved, and files in a database caused by the current file submission are effectively prevented from being tampered.
With continued reference to fig. 5, fig. 5 is another flow chart of a method for managing file submission according to an embodiment of the invention, where the method shown in fig. 5 includes:
in a possible implementation, step 501 further includes, before:
after determining that the target user logs in the user terminal, determining a permission prompt message according to the corresponding relation between the target user identifier and the permission of the file in the preset database, and outputting the permission prompt message to the user terminal.
In an alternative embodiment, the prompt message may be a color identifier, and the corresponding color prompt identifier is output according to the authority relationship between different user identifiers and each file of the preset database.
Exemplary, (1) when the authority relationship between the target user identifier and the file in the preset database is locking or any other user is locking, but the target user identifier is recorded in an assistant field of the file authority table, that is, the user identifier corresponding to the user terminal can be detected through a first locking field or an assistant field recorded in the first target file authority table, the color prompt identifier is used as a first color to serve as a first authority prompt message. With continued reference to fig. 4, it can be appreciated that the relationship of user b to files D, E, F and Z.
(2) When the authority relationship between the target user identifier and the file in the preset database is that the file is not authorized to be submitted, that is, the first target file authority table is acquired, but the first locker field or the helper field does not detect the target user identifier or does not acquire the first target file authority table, and the detected file authority field in the target public mapping table is in the first management state or the second management state or the first locker field is not null, the first authority table may be expressed as "open_lv=1 or (open_lv=1 and locker |=my id)", and the color prompt identifier is taken as a second authority prompt message. With continued reference to fig. 4, it can be appreciated that the relationship of user b to files A, B and C.
(3) When the authority relationship between the target user identifier and the file in the preset database is the authority relationship capable of submitting the file, that is, the first target file authority table is not acquired, and the target public mapping table detects that the file authority field is in a third management state, that is, "open_lv=1 or (open_lv=1 and lock-. With continued reference to fig. 4, it can be understood that the relationship of user b to files such as file G, H.
In one possible implementation manner, if the color identifier is used as the permission prompt information, the first color, the second color and the third color are different colors, and may be green, red and black, which is not limited herein.
the file authority table comprises a first file identification field of the locked file, a first locker field and a helper field, wherein the first locker field is used for recording a first authorized user identification of the authorized file submitted to the locking, and the helper field is used for recording a helper user identification of at least one helper user, which is introduced into the locking working area, of a authorized user corresponding to the first authorized user identification;
in one possible implementation, step 502 further includes:
step a, if the first target file permission table is determined to exist, acquiring the first target file permission table;
and b, judging whether the target user has the right to submit the target file by using the first locker field, the helper field and the target user identifier.
In an alternative implementation, the step b specifically includes: if the target user identification is detected to be matched with the first locker field or the helper field, determining that the target user is authorized to submit the target file; and if the target user identification is not matched with the first locker field and the helper field, determining that the target user is not authorized to submit the target file.
It should be noted that, the file permission list is a corresponding locked file and a corresponding locked person inserted in the locked working area, and the file permission list of the locked area is also cleared synchronously after the locked person is unlocked. The locking person can be determined and recorded in the first locking person field after the user side performs active locking on the unlocked file, or can be determined and recorded in the second locking person field of the public environment mapping table and the assisting person field of the file authority table by the administrator side performing the locking person designating any user side as any file.
The matching may be understood as that the user identifier which is the same as the target user identifier exists in the first authorized user identifier field or the user identifier recorded in the helper field in the file authority table.
Therefore, when the file permission table is obtained through the file identifier, it is indicated that the file corresponding to the file identifier has a locking person at the moment, so that whether the user terminal has the submitting right can be judged through the user identifier corresponding to the user terminal sending the submitting request.
In an optional implementation manner, when a first locker field recorded in the file authority table is not empty, detecting whether a target user identifier corresponding to a user terminal submitting a request and a user identifier recorded in the first locker field are the same identifier, and if so, determining that the user terminal has the right to submit a file; if the target user identification corresponding to the user end of the submitting request and the user identification recorded in the helper field are not the same, whether the target user identification is the same as the user identification recorded in the helper field is continuously detected, if the target user identification is the same as the user identification recorded in the helper field, the user end is determined to have the right to submit the file, and if the target user identification is not the same, the user end is determined to have the right to submit the file.
Further, when the first locking person field recorded in the file permission table is empty, the user identifier recorded in the person field is assisted to execute the above judgment, which is not described herein.
the public environment mapping table comprises a second file identification field, a file authority field and a second locker field, wherein the file authority field is used for recording the management and control state of an administrator on a file, the second locker field is used for recording a second authorized user identification, which is designated by the administrator and is authorized to submit the locked file, of the file, and the management and control state of the file comprises a first management and control state, which is locked by the administrator and can be checked by a user, a second management and control state, which is locked by the administrator and cannot be checked by the user, and a third management and control state, which is unlocked by the administrator, of the file.
The contents of steps 501, 502 and 503 shown in fig. 5 are similar to those of steps 101, 102 and 103 shown in fig. 1, and for avoiding repeated explanation, please refer to the embodiment shown in fig. 1 for details.
In one possible implementation, the file authority field in the public environment mapping table may be denoted as open_1v, which is used to record the administrative state of the administrator for the file corresponding to the file identifier.
Illustratively, when open_1v=0 represents the first regulatory state of a file, i.e., the administrator has locked the file and is not viewable by the user; when open_1v=1 represents the second regulatory state of the file, i.e., the administrator has locked the file and the user is viewable; when open_1v=2 represents the third regulatory state of the file, i.e., the administrator does not lock the file and the user is free to operate.
In one possible embodiment, a second locker field in the public context map may be represented as a locker, which records a second authorized user identification specified by the administrator to submit a locked file.
Illustratively, a second authorized user identification that does not designate a commit right on behalf of the administrator when the lock is null; when locker is not null, the second authorized user identification with the submitting authority is appointed by the representative administrator, and not only the second authorized user identification is recorded in the field, but also the second authorized user identification is synchronized to an assisting person field in the file authority table, and the identity of the user corresponding to the second authorized user identification of the assisting person field is a locking person.
In a possible implementation manner, if it is detected that the file authority field is in the first control state or the second control state, or the second locker field is not in any air, namely "open_lv in (0, 1) or locker is not null", it is indicated that the file is in the administrator locking state at this time, so that the user side cannot submit the file, and it is determined that the target user does not have the right to submit the target file; if the file authority field is detected to be in the third control state and the second locker field is empty, namely 'open_lv=2 and locker is null', the fact that the administrator does not lock the file at this time and any user is not specified to lock the file is indicated, and the fact that the target user is authorized to submit the target file is determined.
In the embodiment of the present invention, if it is detected that the file authority field is in the third control state and the second locker field is empty, determining that the target user is authorized to submit the target file, and then further includes:
If a locking request of the user side to the target file is received, a second target file permission table corresponding to the target file is added in the file permission table recorded in the locking work area, and a user identification initiating locking is recorded in a first locking person field and an assisting person field of the second target file permission table.
It can be understood that if the third management state of the file permission field is detected and the second locker field is empty, "open_lv=2 and locker is null", it is indicated that the administrator does not lock the file at this time and does not designate any user to lock the file (preferably, the file permission state of the file permission table is determined), and the file is in a permission free state, so that the user can submit or lock the file, and therefore if a request for locking the target file from the user terminal is received, a file permission table corresponding to a row of file identifiers is added to the file permission table in the locking working area of the item, and the corresponding file identifiers, file states and user identifiers are recorded in the corresponding fields of the table.
In the embodiment of the invention, judging whether the target user has the right to submit the target file further comprises the following steps: generating a submitting record, a difference record and a file state record of the target file in real time, and storing the submitting record, the difference record and the file state record of the target file into a behavior log of a preset database, wherein the submitting record is used for recording the submitting time and the submitting user of the target file, the difference record is used for recording the difference position between the current target file submitting and the last target file submitting in a pointer mode, and the file state record is used for recording the authority state of the file in real time, wherein the authority state comprises a locked state, a locked release state and an unlocked state.
In an alternative embodiment, the latest commit time of each file, commit remarks and current locking people can be seen through the field records of the public environment mapping table at the same time.
The record of the file status log table (status_log table) may be used to determine the front-back change value of any change of the public environment mapping table and the file authority table information, and when clicking right on any file in the FSMC program, the file status log may be queried, that is, the operation timeline for displaying the file may include a commit record, a lock and release record of a user, a lock and release record of an administrator, and the like.
The file log table (file_log table) can be used for recording the difference position and content of each file when submitted each time and can be recorded into the file_log of the unified database file of the FSMC in a pointer mode, so that a user can conveniently compare the differences between different versions, and meanwhile, the function of directly submitting a certain historical version on the FSMC by the user is realized through reverse pointer rollback of the current version file.
Before project development, users in each connected local environment can pull project files in the public environment to corresponding working areas through the FSMC program so as to prevent the original files in the public environment from being changed randomly and not retrieved; therefore, after the user modifies the file in the local development environment, the file needs to be submitted to the public environment to update the original file in an overlaying manner; the rollback setting is used as a preventive mechanism to prevent users with submitting rights from re-submitting historical versions through the history record after updating the original file.
The embodiment of the invention discloses a method for managing file submission, which comprises the following steps: receiving a file submitting request of a user; searching a file authority table recorded in a locking working area by utilizing a target file identifier, and determining whether a first target file authority table of a target file exists or not, wherein the file authority table comprises a first file identifier field, a first locking person field and an assisting person field of the locked file; if the first target file permission table is determined to exist, acquiring the first target file permission table, and judging whether the target user is authorized to submit the target file by utilizing the first locker field and the helper field; if the first target file authority table is determined to be absent, a target public environment mapping table of the target file is obtained by using the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file authority field and a second locker field; and judging whether the target user has the right to submit the target file according to the file authority field and the second locker field. The file submitting accuracy is improved by means of two-stage double management and control modes through the authority states of the files recorded in the file authority table and the public environment mapping table, the files in the database are effectively prevented from being tampered due to the submitting of the files at present, corresponding prompt messages can be output according to the authority relation between each user and the files, and further behavior logs of the files can be generated in real time, so that effective supervision of the files is achieved before or after the files are submitted, and user experience is further improved.
Referring to fig. 6, fig. 6 is a block diagram of a management apparatus for file submission according to an embodiment of the present invention, where the apparatus shown in fig. 6 includes:
the receive request module 601: the file submitting method comprises the steps of receiving a file submitting request of a user side, wherein the file submitting request comprises a target user identifier of a target user initiating the request and a target file identifier of a target file to be submitted;
the first acquisition module 602: the file authority table is used for searching a file authority table recorded in the locking working area by utilizing the target file identification, determining whether a first target file authority table of the target file exists or not, wherein the file authority table comprises a first file identification field of the locked file, a first locker field and an assisted field, the first locker field is used for recording a first authorized user identification which is authorized to submit the locked file, and the assisted field is used for recording an assisted user identification of at least one assisted user, which is introduced into the locking working area, of an authorized user corresponding to the first authorized user identification;
the second acquisition module 603: if the first target file permission table does not exist, acquiring a target public environment mapping table of the target file by utilizing the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file permission field and a second locker field, the file permission field is used for recording the management and control state of an administrator on the file, the second locker field is used for recording a second authorized user identifier which is appointed by the administrator and is authorized to submit the locked file, and the management and control state of the file comprises a first management and control state which is locked by the administrator and can be checked by a user, a second management and control state which is locked by the administrator and can not be checked by the user and a third management and control state which is unlocked by the administrator;
The submit-management module 604: and the target user is used for judging whether the target user is authorized to submit the target file according to the file authority field and the second locker field.
The embodiment of the apparatus shown in fig. 6 is similar to the above-mentioned steps shown in fig. 1, and for avoiding repeated explanation, reference is made to the description of the embodiment shown in fig. 1.
The embodiment of the invention discloses a management device for file submission, which comprises: a receiving request module: receiving a file submitting request of a user; a first acquisition module: searching a file authority table recorded in the locking working area by utilizing the target file identifier, and determining whether a first target file authority table of the target file exists or not; and a second acquisition module: if the first target file authority table is determined to be absent, a target public environment mapping table of the target file is obtained by using the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file authority field and a second locker field; and a submission management module: and judging whether the target user has the right to submit the target file according to the file authority field and the second locker field. The file authority states recorded in the file authority table and the public environment mapping table are used for realizing accurate management of file submission in a two-stage double management and control mode, so that the file submission accuracy to be submitted is improved, and the file in the database is effectively prevented from being tampered due to the current file submission.
FIG. 7 illustrates an internal block diagram of a computer device in one embodiment. The computer device may specifically be a terminal or a server. As shown in fig. 7, the computer device includes a processor, a memory, and a network interface connected by a system bus. The memory includes a nonvolatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system, and may also store a computer program which, when executed by a processor, causes the processor to implement the steps of the method embodiments described above. The internal memory may also have stored therein a computer program which, when executed by a processor, causes the processor to perform the steps of the method embodiments described above. It will be appreciated by those skilled in the art that the structure shown in fig. 5 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is presented comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method as shown in fig. 1 or fig. 5.
In one embodiment, a computer-readable storage medium is provided, storing a computer program which, when executed by a processor, causes the processor to perform the steps of the method as shown in fig. 1 or fig. 5.
Those skilled in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by a computer program for instructing relevant hardware, where the program may be stored in a non-volatile computer readable storage medium, and where the program, when executed, may include processes in the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application is to be determined by the claims appended hereto.
Claims (8)
1. A method of managing file submissions, the method comprising:
receiving a file submitting request of a user side, wherein the file submitting request comprises a target user identifier of a target user initiating the request and a target file identifier of a target file to be submitted;
searching a file authority table recorded in a locking working area by utilizing the target file identifier, and determining whether a first target file authority table of the target file exists or not, wherein the file authority table comprises a first file identifier field of a locked file, a first locker field and an assisted field, the first locker field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the assisted field is used for recording an assisted user identifier of at least one assisted user which is introduced into the locking working area by an authorized user corresponding to the first authorized user identifier;
If the first target file authority table does not exist, acquiring a target public environment mapping table of the target file by utilizing the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file authority field and a second locker field, the file authority field is used for recording the management state of an administrator on the file, the second locker field is used for recording a second authorized user identifier which is appointed by the administrator and is authorized to submit the locked file, and the management state of the file comprises a first management state which is locked by the administrator and can be checked by a user, a second management state which is locked by the administrator and cannot be checked by the user and a third management state which is not locked by the administrator;
judging whether the target user has the right to submit the target file according to the file authority field and the second locker field;
wherein the method further comprises:
if the first target file permission table is determined to exist, acquiring the first target file permission table;
judging whether the target user has the right to submit the target file or not by utilizing the first locking person field, the assistant field and the target user identifier;
Wherein, according to the file authority field and the second locker field, determining whether the target user has authority to submit the target file includes:
if the file authority field is detected to be in a first control state or a second control state or the second locker field is not empty, determining that the target user is not authorized to submit the target file;
and if the file authority field is detected to be in the third control state and the second locking person field is detected to be empty, determining that the target user is authorized to submit the target file.
2. The method of claim 1, wherein if the file authority field is detected to be in the first control state or the second control state, or the second locker field is not empty, determining that the target user is not authorized to submit the target file further comprises:
if a locking request of the user side to the target file is received, a second target file permission table corresponding to the target file is added in the file permission table recorded in the locking work area, and a user identification initiating locking is recorded in a first locking person field and an assisting person field of the second target file permission table.
3. The method of claim 1, wherein said determining whether the target user is authorized to submit the target file using the first locker field, the facilitator field, and the target user identification comprises:
if the target user identification is detected to be matched with the first locker field or the helper field, determining that the target user is authorized to submit the target file;
and if the target user identification is not matched with the first locker field and the helper field, determining that the target user is not authorized to submit the target file.
4. The method of claim 1, wherein the receiving the file submission request from the user terminal further comprises:
after determining that the target user logs in the user terminal, determining a permission prompt message according to the corresponding relation between the target user identifier and the permission of the file in the preset database, and outputting the permission prompt message to the user terminal.
5. The method of claim 1 or 2, wherein said determining whether the target user has the right to submit the target file further comprises:
generating a submitting record, a difference record and a file state record of the target file in real time, and storing the submitting record, the difference record and the file state record of the target file into a behavior log of a preset database, wherein the submitting record is used for recording the submitting time and the submitting user of the target file, the difference record is used for recording the difference position between the current submitting of the target file and the previous submitting of the target file in a pointer mode, and the file state record is used for recording the authority states of the file in real time, including a locked state, a locking release state and an unlocked state.
6. A document submission management apparatus, the apparatus comprising:
a request receiving module: the file submitting method comprises the steps of receiving a file submitting request of a user side, wherein the file submitting request comprises a target user identifier of a target user initiating the request and a target file identifier of a target file to be submitted;
a first acquisition module: the method comprises the steps that a file authority table recorded in a locking working area is searched by utilizing the target file identifier, whether a first target file authority table of the target file exists or not is determined, the file authority table comprises a first file identifier field of a locked file, a first locker field and an assisted field, the first locker field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the assisted field is used for recording an assisted user identifier of at least one assisted user which is introduced into the locking working area by an authorized user corresponding to the first authorized user identifier;
and a second acquisition module: if the first target file permission table does not exist, acquiring a target public environment mapping table of the target file by utilizing the target file identifier, wherein the public environment mapping table comprises a second file identifier field, a file permission field and a second locker field, the file permission field is used for recording the management state of an administrator on the file, the second locker field is used for recording a second authorized user identifier which is appointed by the administrator and is authorized to submit the locked file, and the management state of the file comprises a first management state which is locked by the administrator and can be checked by a user, a second management state which is locked by the administrator and cannot be checked by the user and a third management state which is not locked by the administrator;
And a submission management module: the target user is used for judging whether the target user has the right to submit the target file according to the file right field and the second locker field;
wherein the device is further for: if the first target file permission table is determined to exist, acquiring the first target file permission table; judging whether the target user has the right to submit the target file or not by utilizing the first locking person field, the assistant field and the target user identifier;
the submission management module is specifically configured to: if the file authority field is detected to be in a first control state or a second control state or the second locker field is not empty, determining that the target user is not authorized to submit the target file; and if the file authority field is detected to be in the third control state and the second locking person field is detected to be empty, determining that the target user is authorized to submit the target file.
7. A computer readable storage medium storing a computer program, which when executed by a processor causes the processor to perform the steps of the method according to any one of claims 1 to 5.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program which, when executed by the processor, causes the processor to perform the steps of the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110167637.XA CN112905533B (en) | 2021-02-05 | 2021-02-05 | File submission management method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110167637.XA CN112905533B (en) | 2021-02-05 | 2021-02-05 | File submission management method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112905533A CN112905533A (en) | 2021-06-04 |
| CN112905533B true CN112905533B (en) | 2023-04-25 |
Family
ID=76124412
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110167637.XA Active CN112905533B (en) | 2021-02-05 | 2021-02-05 | File submission management method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112905533B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115022307A (en) * | 2022-07-26 | 2022-09-06 | 中银金融科技有限公司 | A file downloading method and device, storage medium and electronic device |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0278312A2 (en) * | 1987-02-13 | 1988-08-17 | International Business Machines Corporation | Distributed file and record locking |
| CN1227644A (en) * | 1996-08-02 | 1999-09-01 | 通讯软件有限公司 | Method and apparatus for allowing distributed control of shared resources |
| US5953419A (en) * | 1996-05-06 | 1999-09-14 | Symantec Corporation | Cryptographic file labeling system for supporting secured access by multiple users |
| CN101192262A (en) * | 2006-11-24 | 2008-06-04 | 鸿富锦精密工业（深圳）有限公司 | File authority control system and method |
| US8453215B1 (en) * | 2010-10-25 | 2013-05-28 | Go Daddy Operating Company, LLC | Suggesting access permission changes to lock a website |
| US9892242B1 (en) * | 2017-04-28 | 2018-02-13 | Global Tel*Link Corporation | Unified enterprise management of wireless devices in a controlled environment |
| CN109154969A (en) * | 2016-06-13 | 2019-01-04 | 弗霍斯公司 | The system and method for secure storage for the user information in user profile |
| CN110781507A (en) * | 2019-10-21 | 2020-02-11 | 中广核工程有限公司 | File authority control method and device, computer equipment and storage medium |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5280612A (en) * | 1991-11-26 | 1994-01-18 | International Business Machines Corporation | Multiple version database concurrency control system |
| US8150820B1 (en) * | 2007-10-04 | 2012-04-03 | Adobe Systems Incorporated | Mechanism for visible users and groups |
| US9342703B2 (en) * | 2012-11-30 | 2016-05-17 | Red Hat Israel, Ltd. | Managing storage permissions for logical volume managers |
| US10885209B2 (en) * | 2015-04-17 | 2021-01-05 | Dropbox, Inc. | Collection folder for collecting file submissions in response to a public file request |
| CN106469150B (en) * | 2015-08-14 | 2019-10-08 | 阿里巴巴集团控股有限公司 | File read/write method, device and system |
| US10146915B2 (en) * | 2015-09-14 | 2018-12-04 | Salesforce.Com, Inc. | Publication of collaborative file to library |
| CN106648789A (en) * | 2016-12-28 | 2017-05-10 | 北京奇虎科技有限公司 | File processing method and device |
| TW201828100A (en) * | 2017-01-19 | 2018-08-01 | 阿里巴巴集團服務有限公司 | File reading and writing method, apparatus and system avoiding conflicts between contents submitted by multiple users when operating the same file |
| US11086995B2 (en) * | 2018-04-30 | 2021-08-10 | EMC IP Holding Company LLC | Malware scanning for network-attached storage systems |
| CN109697191A (en) * | 2018-12-04 | 2019-04-30 | 深圳供电局有限公司 | Editing method, device and system based on network shared file |
| CN110262997A (en) * | 2019-05-06 | 2019-09-20 | 阿里巴巴集团控股有限公司 | For managing the method and system of public documents |
| CN110958292A (en) * | 2019-09-17 | 2020-04-03 | 平安银行股份有限公司 | File uploading method, electronic device, computer equipment and storage medium |
-
2021
- 2021-02-05 CN CN202110167637.XA patent/CN112905533B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0278312A2 (en) * | 1987-02-13 | 1988-08-17 | International Business Machines Corporation | Distributed file and record locking |
| US5953419A (en) * | 1996-05-06 | 1999-09-14 | Symantec Corporation | Cryptographic file labeling system for supporting secured access by multiple users |
| CN1227644A (en) * | 1996-08-02 | 1999-09-01 | 通讯软件有限公司 | Method and apparatus for allowing distributed control of shared resources |
| CN101192262A (en) * | 2006-11-24 | 2008-06-04 | 鸿富锦精密工业（深圳）有限公司 | File authority control system and method |
| US8453215B1 (en) * | 2010-10-25 | 2013-05-28 | Go Daddy Operating Company, LLC | Suggesting access permission changes to lock a website |
| CN109154969A (en) * | 2016-06-13 | 2019-01-04 | 弗霍斯公司 | The system and method for secure storage for the user information in user profile |
| US9892242B1 (en) * | 2017-04-28 | 2018-02-13 | Global Tel*Link Corporation | Unified enterprise management of wireless devices in a controlled environment |
| CN110781507A (en) * | 2019-10-21 | 2020-02-11 | 中广核工程有限公司 | File authority control method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112905533A (en) | 2021-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110620810B (en) | Non-linked ownership of continuous asset transfer over blockchain | |
| AU2018347193B2 (en) | Cross-chain interactions using a domain name scheme in blockchain systems | |
| AU2018348320B2 (en) | A domain name scheme for cross-chain interactions in blockchain systems | |
| JP6821020B2 (en) | Domain name management method for cross-chain interaction in blockchain system | |
| DE69902749T2 (en) | ENCAPSULATION, DATA DISPLAY AND TRANSMISSION OF CONTENT-ADDRESSABLE DATA | |
| US20070288835A1 (en) | Apparatus, computer readable medium, data signal, and method for document management | |
| US20030088654A1 (en) | Directory server schema replication | |
| JP2004528636A (en) | Automatic data update | |
| US7457826B2 (en) | Systems and methods for synchronization of items without snapshots | |
| CN110598413B (en) | Method, system and equipment for maintaining rules of anti-attack platform | |
| EP3779755B1 (en) | A computer-implemented method for cross-chain-interoperability | |
| JPH1021061A (en) | Automatic version-up system for client software | |
| CN112632947A (en) | Online document processing method, online document processing device and electronic equipment | |
| CN112905533B (en) | File submission management method, device, equipment and storage medium | |
| JPH0785020A (en) | Document management method | |
| US20130346432A1 (en) | Shared data with relationship information | |
| JP2001306372A (en) | Method for managing document and storage medium storing program for executing the method | |
| WO2005062250A2 (en) | Distributed knowledge management system | |
| JP3934965B2 (en) | Document management apparatus, document management method, and program | |
| US10657139B2 (en) | Information processing apparatus and non-transitory computer readable medium for distributed resource management | |
| US20030088615A1 (en) | Update resolution procedure for a directory server | |
| US20080046439A1 (en) | Automatic capture of associations between content within a content framework system | |
| CN113094753A (en) | Big data platform hive data modification method and system based on block chain | |
| CN111858627A (en) | Academic degree and academic calendar query system and method based on block chain | |
| US6681233B1 (en) | Data circulation between servers and clients |
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 |