CN112905533A - File submission management method, device, equipment and storage medium - Google Patents
File submission management method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112905533A CN112905533A CN202110167637.XA CN202110167637A CN112905533A CN 112905533 A CN112905533 A CN 112905533A CN 202110167637 A CN202110167637 A CN 202110167637A CN 112905533 A CN112905533 A CN 112905533A
- 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.)
- Granted
Links
- 238000007726 management method Methods 0.000 title abstract description 43
- 238000013507 mapping Methods 0.000 claims abstract description 58
- 238000000034 method Methods 0.000 claims abstract description 29
- 230000000977 initiatory effect Effects 0.000 claims description 11
- 238000004590 computer program Methods 0.000 claims description 10
- 230000006399 behavior Effects 0.000 claims description 4
- 230000009977 dual effect Effects 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 11
- 238000011161 development Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 4
- 230000001360 synchronised effect Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000001105 regulatory effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 230000014509 gene expression Effects 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
- 230000002265 prevention Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer 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 Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- Automation & Control Theory (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Storage Device Security (AREA)
Abstract
The embodiment of the invention discloses a file submission management method, a file submission management device, file submission equipment and a storage medium, wherein the method comprises the following steps: receiving a file submission request of a user side; searching a file authority table recorded in a locking working area by using 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, acquiring a target public environment mapping table of the target file 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 or not 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 accurate management of file submission is realized in a two-stage dual control mode, the submission accuracy of the file to be submitted is improved, and the file in the database is effectively prevented from being tampered due to the submission of the current file.
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 realization of technologies such as program or website development, file sharing and the like can not avoid the link that files are submitted to a sharing server from a local environment in the testing and publishing processes.
When a program or a website is developed, updated or iterated, the development, the update or the iteration is often completed by a team of a plurality of persons with different functions, when a plurality of persons develop the same function or file, two persons cannot modify the same file at the same time, when the two persons submit the modified file from a local environment to a public environment, the file of a first submitter is always covered by the file of a second submitter or the content of the file submitted by the first submitter is altered, so that the content of the file of the public environment is disordered after the plurality of persons submit, and the function which the first submitter wants to realize is influenced.
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 the content of a file is disordered after a plurality of people submit the same file in sequence in the prior art.
In order to achieve the above object, a first aspect of the present invention provides a file submission management method, including:
receiving a file submission request of a user side, wherein the file submission 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 using 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, a first locking person field and a helper field of the locked file, the first locking person field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the helper field is used for recording an assistant user identifier of at least one assistant 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 is determined not to exist, acquiring a target public environment mapping table of the target file 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 lock person field, the file authority field is used for recording the control state of an administrator on the file, the second lock person field is used for recording a second authorized user identifier which is specified by the administrator and authorized to submit the locked file, and the control state of the file comprises a first control state which is locked by the administrator and can be viewed by a user, a second control state which is locked by the administrator and can not be viewed by the user and a third control state which is unlocked by the administrator;
and judging whether the target user has the right to submit the target file or not according to the file authority field and the second locker field.
In an optional implementation manner, the determining whether the target user has the right to submit the target file according to the file authority field and the second locker field includes:
if the file permission 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 has no right to submit the target file;
and if the file permission field is detected to be in the third control state and the second locker field is empty, determining that the target user has the right to submit the target file.
In an optional implementation manner, if it is detected that the file permission field is in the first management and control state or the second management and control state, or the second locker field is not empty, 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 a user end to the target file is received, adding a second target file authority table corresponding to the target file in the file authority table recorded in the locking working area, and recording a user identifier initiating locking in a first locking person field and a helper field of the second target file authority table.
In an optional embodiment, the method further comprises:
if the first target file authority table is determined to exist, the first target file authority table is obtained;
and judging whether the target user has the right to submit the target file or not by utilizing the first locked person field, the assistant person field and the target user identification.
In an optional implementation manner, the determining, by using the first locked person field, the assistant person field, and the target user identifier, whether the target user has the right to submit the target file includes:
if the target user identification is detected to be matched with the first locked person field or the assistant person 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 locked person field and the assistant person field, determining that the target user is not authorized to submit the target file.
In an optional implementation manner, the receiving a file submission request from a user side further includes:
and after the target user is confirmed to log in the user side, confirming an authority prompting message according to the corresponding relation between the target user identification and the authority of the file in the preset database and outputting the authority prompting message to the user side.
In an optional implementation manner, the determining whether the target user has the right to submit the target file further includes:
generating a submission record, a difference record and a file state record of the target file in real time, and storing the submission record, the difference record and the file state record of the target file to a behavior log of a preset database, wherein the submission record is used for recording the submission time of the target file and the submission user, the difference record is used for recording the difference position between the submission of the current target file and the submission of the previous 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 locked release state and an unlocked state.
To achieve the above object, a second aspect of the present invention provides a file submission management apparatus, including:
a request receiving module: the file submitting method comprises the steps that a file submitting request of a user side is received, wherein the file submitting request comprises a target user identifier of a target user initiating a request and a target file identifier of a target file to be submitted;
a first obtaining module: the file authority table is used for searching for a file authority table of a locked working area record by using 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, a first locked person field and a helper field of the locked file, the first locked person field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the helper field is used for recording an assistant user identifier of at least one assistant user which is introduced into the locked working area by an authorized user corresponding to the first authorized user identifier;
a second obtaining module: if the first target file authority table is determined not to exist, acquiring a target public environment mapping table of the target file 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 lock person field, the file authority field is used for recording the control state of an administrator on the file, the second lock person field is used for recording a second authorized user identifier which is specified by the administrator and authorized to submit the locked file, and the control state of the file comprises a first control state which is locked by the administrator and can be viewed by a user, a second control state which is locked by the administrator and can not be viewed by the user and a third control state which is unlocked by the administrator;
a submission management module: and the file management module is used for judging whether the target user has the right to submit the target file or not 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, including a memory and a processor, wherein the memory stores a computer program, and the computer program, when executed by the processor, causes the processor to perform the steps of 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 submission request of a user side; searching a file authority table recorded in a locking working area by using 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, acquiring a target public environment mapping table of the target file 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 or not according to the file authority field and the second locker field. The accurate management of file submission is realized in a two-stage dual control mode through the authority states of the files recorded in the file authority table and the public environment mapping table, the submission accuracy of the file to be submitted is improved, and the file in the database is effectively prevented from being tampered due to the submission of the current file.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Wherein:
FIG. 1 is a flowchart illustrating a file submission management method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating an operating mode of a file submission manager according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a field format according to an embodiment of the present invention;
FIG. 4 is a schematic diagram illustrating an internal operating mode of a file submission manager in an embodiment of the present invention;
FIG. 5 is a schematic flow chart illustrating a file submission management method according to an embodiment of the present invention;
FIG. 6 is a block diagram of a file submission management apparatus according to an embodiment of the present invention;
fig. 7 is a block diagram of a computer device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a schematic flow chart illustrating a file submission management method according to an embodiment of the present invention, where the method shown in fig. 1 includes:
the user identification is the unique identity identification of the user; the file identification is the unique identity of the file.
It can be understood that when a file submission request from a user side is received, the unique identity 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, and fig. 2 is a schematic diagram of a working mode of a file submission management program in the embodiment of the present invention, for example, an fsmc (file synchronization management control procedure) program shown in fig. 2 represents the file submission management program, and a program module carries a management method of file submission, and for example, as shown in fig. 2, the file submission management program is installed and deployed in local development environments 1, 2, and n of different users to be connected with different public environments 1, 2, or n (as shown by arrows), so that all users under different local environments but belonging to the same project group, that is, the same public environment can implement unified management through the file submission management program.
the file authority table comprises a first file identification field of a locked file, a first locker field and a helper field, wherein the first locker field is used for recording a first authorized user identification which is authorized to submit the locked file, and the helper field is used for recording an assistant user identification of at least one assistant user which is introduced into a locking working area by an authorized user and corresponds 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 control state of an administrator on a file, the second locker field is used for recording a second authorized user identification which is specified by the administrator and authorized to submit the locked file, and the control state of the file comprises a first control state which is locked by the administrator and can be checked by a user, a second control state which is locked by the administrator and can not be checked by the user and a third control state which is unlocked by the administrator.
In the embodiment of the invention, the file authority tables correspond to the locked file identifiers one to one, the file authority tables recorded in the locked working area are searched through the target file identifiers, and whether the file authority tables in the locked working area have the file authority tables corresponding to the target file identifiers or not is searched through the target file identifiers, so that whether the first target file authority table of the target file exists or not is determined.
In a feasible implementation manner, please refer to fig. 3, where fig. 3 is a field format diagram in an embodiment of the present invention, where the file authority table2 includes a first file identification field that may be represented as file _ id (int), a first file status field that may be represented as status (tinyint), a first locker field that may be represented as user _ id (int), and a assistant field that may be represented as role (tinyint), where contents in parentheses are field types corresponding to different fields.
The locked work area is a work area formed by locking an unlocked file by a user and is relatively independent of the locked file, and the locked user performs related operations of development, unlocking, development assistance and the like on the file in the locked work area.
It can be understood that, each time the FSMC program connects to a new common environment, i.e. a new item, the submission root directory needs to be specified and a corresponding common environment mapping area needs to be generated, and a real-time file mapping table, i.e. a common environment mapping table, of a corresponding common environment specified area and a file authority table are added in the FSMC database synchronously.
The common environment mapping table in the FSMC database is a mapping table of a common environment database table corresponding to the project, and the common environment database table is generated when the project file is created and is used for synchronizing the file state recorded in the common environment in real time; the file authority table is a locking record of a row of files inserted into the file authority table when the files are locked by a certain user, and the locking record is cleared when the user who executes locking unlocks.
In the embodiment of the invention, if the first target file authority table is determined not to exist, the file is indicated not to be 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 authority can submit the target file to be submitted to the target project database to update the project original file of 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 the files recorded in the public environment are mapped in the FSMC database, and when an administrator performs state control on any file in the public environment, the real-time public environment mapping table is updated to the public environment file mapping table in the FSMC database synchronously.
For better understanding the relationship between each user, the File, the public environment mapping area and the submission management in the embodiment of the present invention, please continue to refer to fig. 4, as shown in fig. 4, it is a schematic diagram of an internal working mode of a File submission management program in the embodiment of the present invention, as shown in fig. 4, each public environment mapping area and the corresponding public environment may perform real-time data interaction through an FTP (File Transfer Protocol) Protocol to synchronize the File state of the public environment, as an example, when a user b in a local development environment and a user a in a local development environment connect an FSMC program and a public environment (a public environment), a mapping area of a public environment is generated on an FSMC database through the FTP Protocol, and a public environment mapping table and a File permission table are added in the FSMC database; as shown in fig. 4, an arrow may represent a permission identifier between a user and a file, an arrow with an X identifier represents a file that a target user does not have permission to submit, and an arrow without an X identifier represents a file that a target user has permission to submit; taking the user B and the file shown in the figure as an example, the file locked by the user B is a file D, E, F; the file locked by the user A is a file A, B, C; the collaborative files of the user B and the user A, namely the assistant files, comprise a file Z, and the other files are permission free files, such as a file G, H and the like, so that permission identifications of the target user B and the file A, B, C are permission identifications between the users and the files, because other users are locked and the user B is not a helper, otherwise, the permission identifications between the user B and the other files are arrows without X identifications; whether an authority identification arrow between a user and a file has X is judged, namely when the authority is required to be submitted, the authority is judged by preferentially using records of fields in a file authority table, when the file does not have the file authority table, a public environment mapping table for recording the file state in real time is obtained, and the authority is judged by using the records of the fields in the table.
The expressions of fig. 4 and 4 are merely exemplary for facilitating understanding of the embodiment of the present invention, and do not limit the embodiment.
In an alternative embodiment, please continue to refer to fig. 3, wherein the common environment file mapping table (i.e. the common environment mapping table) table1 includes a second file identification field, which may be represented as file _ id (int), a directory field, which may be represented as category (varchar), a file authority field, which may be represented as open _1v (tinyint), a second file status field, which may be represented as status (tinyint), a second lock person field, which may be represented as lock (int), a lock date field, which may be represented as lock _ date (datatime), and a domain name field, which may be represented as info (text), and the content in the parentheses is the field type corresponding to the different fields.
The file authority field is used for recording the management and control state of the administrator on the file corresponding to the file identifier, and the second locker field is used for recording the user identifier corresponding to the user side which is specified by the administrator and has the submitting authority.
It should be noted that, the field content recorded in the public environment mapping table and the file in the public environment controlled by the administrator through the FTP can be synchronized, including but not limited to, the administrator changing the management and control status of the file in the public environment by adding, deleting, checking and modifying, the administrator designating the file submitting authority for any user end, or changing or unlocking the lock authority of the file locked by any user. By adding the secondary limitation of the administrator side, the stability of file submission management can be further improved.
It can be understood that when an item file is newly added in the item 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 the administrator manages and controls a certain file of the public environment, the file state is also updated in real time synchronously corresponding to the corresponding field in the public environment mapping table.
And step 104, judging whether the target user has the right to submit the target file or not 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 submission request of a user side; searching a file authority table recorded in a locking working area by using 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, acquiring a target public environment mapping table of the target file 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 or not according to the file authority field and the second locker field. The accurate management of file submission is realized in a two-stage dual control mode through the authority states of the files recorded in the file authority table and the public environment mapping table, the submission accuracy of the file to be submitted is improved, and the file in the database is effectively prevented from being tampered due to the submission of the current file.
Referring to fig. 5, fig. 5 is another schematic flow chart of a file submission management method according to an embodiment of the present invention, where the method shown in fig. 5 includes:
in a possible implementation manner, step 501 further includes, before:
and after the target user logs in the user side, determining an authority prompting message according to the corresponding relation between the target user identification and the authority of the file in the preset database, and outputting the authority prompting message to the user side.
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.
Exemplarily, (1) when the authority relationship between the target user identifier and the file in the preset database is locked or locked by any other user, but the target user identifier is recorded in the assistant field of the file authority table, that is, the user identifier corresponding to the user side can be detected through the first locked person field or the assistant field recorded in the first target file authority table, the color prompt identifier is taken as a first color to serve as the first authority prompt message. Continuing with FIG. 4, the relationship of user B to files D, E, F and Z can be understood.
(2) When the authority relationship between the target user identifier and the file in the preset database is the authority relationship for submitting the file without right, that is, the first target file authority table is acquired, but the target user identifier is not detected by the first locked person field or the assistant field or the first target file authority table is not acquired, and the file authority field detected in the target public mapping table is in the first control state or the second control state or the first locked person field is not empty, which may be represented as "open _ lv ═ 1or (open _ lv ═ 1and locker! ═ my id)", the color prompt identifier is used as the second color as the second authority prompt message. With continued reference to FIG. 4, the relationship of user B to files A, B and C can be understood.
(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 file authority field is detected to be the third control state in the target public mapping table, that is, "open _ lv ═ 1or (open _ lv ═ 1and locker | ═ my id)", the color prompt identifier is used as the third color as the third authority prompt message, and the related file of the third color can be locked by any user. Continuing with FIG. 4, it may be appreciated that user B is related to a file such as file G, H.
In a possible implementation manner, if the color identifier is used as the permission prompt message, the first color, the second color and the third color are different colors, and may be green for the first color, red for the second color and black for the third color, which is not limited by this example.
the file authority table comprises a first file identification field, a first locker field and a helper field of a locked file, wherein the first locker field is used for recording a first authorized user identification which is authorized to submit the locked file, and the helper field is used for recording an assistant user identification of at least one assistant user which is introduced into a locking working area by an authorized user and corresponds to the first authorized user identification;
in one possible implementation, step 502 is further followed by:
step a, if the first target file authority table is determined to exist, the first target file authority table is obtained;
and b, judging whether the target user has the right to submit the target file or not by utilizing the first locked person field, the assistant person field and the target user identification.
In an optional implementation manner, step b specifically includes: if the target user identification is detected to be matched with the first locked person field or the assistant person field, determining that the target user has the right to submit the target file; and if the target user identification is not matched with the first locked person field and the assistant person field, determining that the target user is not authorized to submit the target file.
It should be noted that the file authority table is corresponding to the locked file and the locked person inserted in the locked work area, and the file authority table in the locked area is also cleared synchronously after the locked person is unlocked. The lockers can be determined and recorded in the first locker field after the user terminal actively locks the unlocked files, or the administrator terminal can specify any user terminal as the lockers of any file, and the lockers are determined and recorded in the second locker field of the public environment mapping table and the assistant field of the file authority table.
Wherein, matching can be understood as that the user identifier which is the same as the target user identifier exists in the user identifiers recorded in the first authorized user identifier field or the assistant field in the file authority table.
Therefore, when the file authority table is obtained through the file identifier, it is indicated that the file corresponding to the file identifier at this time has a locker, and therefore, whether the user side has the right to submit can be judged through the user identifier corresponding to the user side which sends the submission request.
In an optional implementation manner, when a first locker field recorded in a file permission table is not empty, detecting whether a target user identifier corresponding to a user side submitting a request and a user identifier recorded in the first locker field are the same identifier, and if the target user identifier and the user identifier are the same identifier, determining that the user side has the right to submit a file; if not, continuously detecting whether the target user identifier corresponding to the user side submitting the request is the same as the user identifier of the assistant field record, if so, determining that the user side has the right to submit the file, and if not, determining that the user side does not have the right to submit the file.
Further, when the first locked person field recorded in the file authority table is empty, the above determination is performed by the user identifier recorded in the assistant person field, which is not described herein again.
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 control state of an administrator on a file, the second locker field is used for recording a second authorized user identification which is specified by the administrator and authorized to submit the locked file, and the control state of the file comprises a first control state which is locked by the administrator and can be checked by a user, a second control state which is locked by the administrator and can not be checked by the user and a third control state which is unlocked by the administrator.
As the contents of steps 501, 502, and 503 shown in fig. 5 are similar to the contents of steps 101, 102, and 103 shown in fig. 1, and for avoiding repeated descriptions, no further description is provided herein, and reference is specifically made to the description of the embodiment shown in fig. 1.
In a possible implementation manner, a file permission field in the public environment mapping table may be denoted as open _1v, and this field is used to record the management and control state of the administrator on the file corresponding to the file identifier.
For example, when open _1v ═ 0 represents the first regulatory state of the file, i.e., the file is locked by the administrator and is not viewable by the user; when open _1v ═ 1 represents the second management and control state of the file, that is, the file is locked by the administrator and can be viewed by the user; when open _1v ═ 2 represents the third regulatory state of the file, i.e., the file is not locked by the administrator and is free to operate by the user.
In one possible implementation, a second locker field in the public environment mapping table may be denoted as locker, which records a second authorized user identification specified by the administrator as being authorized to submit the locked file.
Illustratively, a second authorized user identifier that does not specify a submission authority on behalf of the administrator when locker is null; when the locker is not null, the representative administrator designates a second authorized user identifier with a submitting right, and the field records the second authorized user identifier and is also synchronized to a helper field in the file right table, and at this time, the identity of the user corresponding to the second authorized user identifier of the helper field is a locker.
In a feasible implementation manner, if it is detected that the file authority field is in a first control state or a second control state, or the second locker field is not in any one of the air, namely "open _ lv (0,1) or locker is not null", it indicates that the file is in the administrator locking state at this time, and therefore 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 permission field is detected to be in the third control state and the second locker field is null, that is, "open _ lv ═ 2and locker is null", it indicates that the administrator does not lock the file at this time and does not specify any user to lock the file, and it is determined that the target user has the right to submit the target file.
In this embodiment of the present invention, if it is detected that the file permission field is in the third management and control state and the second locker field is empty, it is determined that the target user has the right to submit the target file, and then:
if a locking request of a user end to the target file is received, a second target file authority table corresponding to the target file is added in a file authority table recorded in a locking working area, and a user identification initiating locking is recorded in a first locking person field and a helper field of the second target file authority table.
It can be understood that, if it is detected that the file permission field is in the third management and control state and the second locker field is empty, that is, "open _ lv is 2and locker is null", it indicates that at this time, the administrator does not lock the file, does not specify any user to lock the file, and does not lock any user to the file (preferentially perform the file permission state determination of the file permission table), and indicates that the file is in a permission free state, so that the user can submit or lock the file, therefore, if a lock request of the user for the target file is received, a file permission table corresponding to one row of file identifiers is added to the file permission table in the lock work area of the project, and corresponding file identifiers, file states, and user identifiers are recorded in corresponding fields in the table.
In the embodiment of the present invention, determining whether the target user has the right to submit the target file further includes: the method comprises the steps of generating submission records, difference records and file state records of a target file in real time, storing the submission records, the difference records and the file state records of the target file to a behavior log of a preset database, wherein the submission records are used for recording submission time of the target file and submitting users, the difference records are used for recording the difference position between submission of the current target file and submission of the previous target file in a pointer mode, and the file state records are used for recording authority states of the file in real time, including a locked state, a locked release state and an unlocked state.
In an alternative embodiment, the latest submission time, submission remarks and current lock on person for each file can be seen through the field records of the common environment mapping table at the same time.
The file state log (status _ log) can be used to determine the change value before and after any change of the public environment mapping table and the file authority table information, and when right click is performed on any file in the FSMC program, the file state log can be inquired, that is, the operation timeline for displaying the file includes a submission record, a locking and releasing record of a user, a locking and releasing 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 during each submission and can be recorded into the file _ log of the unified database of the FSMC in a pointer mode, so that a user can compare the difference between different versions conveniently, and the function of directly submitting a certain historical version on the FSMC by the user through the reverse pointer rollback of the current version file is realized.
It can be understood that before the project development, the users in the connected local environments can pull the project files in the public environment to the corresponding working areas through the FSMC program, so as to prevent the original files in the public environment from being changed randomly and being unable to be retrieved; therefore, after a user modifies the file in the local development environment, the file needs to be submitted to a public environment to update the original file in a covering manner; the above-mentioned rollback is set as a prevention mechanism to prevent the user with the filing authority from repenting after updating the original file, and then resubmitting the historical version through the history.
The embodiment of the invention discloses a file submission management method, which comprises the following steps: receiving a file submission request of a user side; searching a file authority table recorded in a locking working area by using 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 a helper field of a locked file; if the first target file authority table is determined to exist, acquiring the first target file authority table and judging whether a target user has the right to submit a target file or not by utilizing the first locker field and the helper field; if the first target file authority table is determined to be absent, acquiring a target public environment mapping table of the target file 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 or not according to the file authority field and the second locker field. The file authority table and the authority states of the files recorded in the public environment mapping table are used for realizing accurate management of file submission in a two-stage dual management and control mode, the accuracy of file submission to be submitted is improved, the files in a database are effectively prevented from being tampered due to the submission of the current files, corresponding prompt messages can be output according to authority relations between users and the files, and further a behavior log of the files can be generated in real time, so that the files can be effectively supervised before or after being submitted, and the user experience is further improved.
Referring to fig. 6, fig. 6 is a structural diagram of a file submission management device according to an embodiment of the present invention, where the file submission management device shown in fig. 6 includes:
the receive request module 601: 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 obtaining module 602: the file authority table is used for searching for a file authority table recorded in a locking working area by using a 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, a first locking person field and a helper field of the locked file, the first locking person field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the helper field is used for recording an assistant user identifier of at least one assistant user which is introduced into the locking working area by an authorized user corresponding to the first authorized user identifier;
the second obtaining module 603: the system comprises a target file identification, a public environment mapping table, a first locking person field, a second locking person field and a third locking person field, wherein the target file identification is used for acquiring the target public environment mapping table of a target file if the first target file authority table is determined not to exist, the public environment mapping table comprises the second file identification field, the file authority field and the second locking person field, the file authority field is used for recording the control state of a file by an administrator, the second locking person field is used for recording a second authorized user identification which is appointed by the administrator and authorized to submit the locked file, and the control state of the file comprises a first control state which is locked by the administrator and can be checked by a user, a second control state which is locked by the administrator and can not be checked by the user and a third control;
the submission management module 604: and the system is used for judging whether the target user has the right to submit the target file or not according to the file authority field and the second locker field.
For example, the content related to the embodiment of the apparatus shown in fig. 6 is similar to the content of the step shown in fig. 1, and for avoiding repeated descriptions, detailed description is not repeated here, and specific reference is made to the description of the embodiment shown in fig. 1.
The embodiment of the invention discloses a file submission management device, which comprises: a request receiving module: receiving a file submission request of a user side; a first obtaining module: searching a file authority table recorded in a locking working area by using the target file identifier, and determining whether a first target file authority table of the target file exists or not; a second obtaining module: if the first target file authority table is determined to be absent, acquiring a target public environment mapping table of the target file 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; a submission management module: and judging whether the target user has the right to submit the target file or not according to the file authority field and the second locker field. The accurate management of file submission is realized in a two-stage dual control mode through the authority states of the files recorded in the file authority table and the public environment mapping table, the submission accuracy of the file to be submitted is improved, and the file in the database is effectively prevented from being tampered due to the submission of the current file.
FIG. 7 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be a terminal, and may also be a server. As shown in fig. 7, the computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the memory includes a non-volatile 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 the processor, causes the processor to carry out the steps of the above-described method embodiments. The internal memory may also store a computer program, which, when executed by the processor, causes the processor to perform the steps of the above-described method embodiments. Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In an embodiment, a computer device is proposed, 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 of the method as shown in fig. 1or fig. 5.
In an embodiment, a computer-readable storage medium is proposed, in which a computer program is stored which, when being executed by a processor, causes the processor to carry out the steps of the method as shown in fig. 1or fig. 5.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile 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), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for managing file submissions, the method comprising:
receiving a file submission request of a user side, wherein the file submission 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 using 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, a first locking person field and a helper field of the locked file, the first locking person field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the helper field is used for recording an assistant user identifier of at least one assistant 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 is determined not to exist, acquiring a target public environment mapping table of the target file 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 lock person field, the file authority field is used for recording the control state of an administrator on the file, the second lock person field is used for recording a second authorized user identifier which is specified by the administrator and authorized to submit the locked file, and the control state of the file comprises a first control state which is locked by the administrator and can be viewed by a user, a second control state which is locked by the administrator and can not be viewed by the user and a third control state which is unlocked by the administrator;
and judging whether the target user has the right to submit the target file or not according to the file authority field and the second locker field.
2. The method of claim 1, wherein determining whether the target user has the right to submit the target document according to the document permission field and the second locker field comprises:
if the file permission 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 has no right to submit the target file;
and if the file permission field is detected to be in the third control state and the second locker field is empty, determining that the target user has the right to submit the target file.
3. The method according to claim 2, wherein if it is detected that the file permission field is in a first management state or a second management state, or a second locker field is not empty, determining that the target user is not authorized to submit the target file, and then further comprising:
if a locking request of a user end to the target file is received, adding a second target file authority table corresponding to the target file in the file authority table recorded in the locking working area, and recording a user identifier initiating locking in a first locking person field and a helper field of the second target file authority table.
4. The method of claim 1, further comprising:
if the first target file authority table is determined to exist, the first target file authority table is obtained;
and judging whether the target user has the right to submit the target file or not by utilizing the first locked person field, the assistant person field and the target user identification.
5. The method of claim 4, wherein determining whether the target user has the right to submit the target document using the first locked person field, the assistant person field, and the target user identifier comprises:
if the target user identification is detected to be matched with the first locked person field or the assistant person 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 locked person field and the assistant person field, determining that the target user is not authorized to submit the target file.
6. The method of claim 1, wherein the receiving a file submission request from a user end further comprises:
and after the target user is confirmed to log in the user side, confirming an authority prompting message according to the corresponding relation between the target user identification and the authority of the file in the preset database and outputting the authority prompting message to the user side.
7. The method of claim 1or 3, wherein said determining whether the target user has the right to submit the target document further comprises:
generating a submission record, a difference record and a file state record of the target file in real time, and storing the submission record, the difference record and the file state record of the target file to a behavior log of a preset database, wherein the submission record is used for recording the submission time of the target file and the submission user, the difference record is used for recording the difference position between the submission of the current target file and the submission of the previous 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 locked release state and an unlocked state.
8. An apparatus for managing file submissions, the apparatus comprising:
a request receiving module: the file submitting method comprises the steps that a file submitting request of a user side is received, wherein the file submitting request comprises a target user identifier of a target user initiating a request and a target file identifier of a target file to be submitted;
a first obtaining module: the file authority table is used for searching for a file authority table of a locked working area record by using 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, a first locked person field and a helper field of the locked file, the first locked person field is used for recording a first authorized user identifier which is authorized to submit the locked file, and the helper field is used for recording an assistant user identifier of at least one assistant user which is introduced into the locked working area by an authorized user corresponding to the first authorized user identifier;
a second obtaining module: if the first target file authority table is determined not to exist, acquiring a target public environment mapping table of the target file 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 lock person field, the file authority field is used for recording the control state of an administrator on the file, the second lock person field is used for recording a second authorized user identifier which is specified by the administrator and authorized to submit the locked file, and the control state of the file comprises a first control state which is locked by the administrator and can be viewed by a user, a second control state which is locked by the administrator and can not be viewed by the user and a third control state which is unlocked by the administrator;
a submission management module: and the file management module is used for judging whether the target user has the right to submit the target file or not according to the file authority field and the second locker field.
9. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 7.
10. A computer device comprising a memory and a processor, characterized in that the memory stores a computer program which, when executed by the processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 7.
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 true CN112905533A (en) | 2021-06-04 |
| CN112905533B 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) |
Cited By (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 (20)
| 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 |
| US5280612A (en) * | 1991-11-26 | 1994-01-18 | International Business Machines Corporation | Multiple version database concurrency control system |
| 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 |
| US8150820B1 (en) * | 2007-10-04 | 2012-04-03 | Adobe Systems Incorporated | Mechanism for visible users and groups |
| US8453215B1 (en) * | 2010-10-25 | 2013-05-28 | Go Daddy Operating Company, LLC | Suggesting access permission changes to lock a website |
| US20140156960A1 (en) * | 2012-11-30 | 2014-06-05 | Red Hat Israel, Ltd. | Managing permissions for logical volume managers |
| WO2017028688A1 (en) * | 2015-08-14 | 2017-02-23 | 阿里巴巴集团控股有限公司 | Method, device and system for reading and writing files |
| US20170075919A1 (en) * | 2015-09-14 | 2017-03-16 | Salesforce.Com, Inc. | Publication of collaborative file to library |
| CN106648789A (en) * | 2016-12-28 | 2017-05-10 | 北京奇虎科技有限公司 | File processing method and device |
| US9892242B1 (en) * | 2017-04-28 | 2018-02-13 | Global Tel*Link Corporation | Unified enterprise management of wireless devices in a controlled environment |
| 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 |
| CN109154969A (en) * | 2016-06-13 | 2019-01-04 | 弗霍斯公司 | The system and method for secure storage for the user information in user profile |
| CN109697191A (en) * | 2018-12-04 | 2019-04-30 | 深圳供电局有限公司 | Editing method, device and system based on network shared file |
| US20190278924A1 (en) * | 2015-04-17 | 2019-09-12 | Dropbox, Inc. | Collection folder for collecting file submissions in response to a public file request |
| CN110262997A (en) * | 2019-05-06 | 2019-09-20 | 阿里巴巴集团控股有限公司 | For managing the method and system of public documents |
| US20190332770A1 (en) * | 2018-04-30 | 2019-10-31 | EMC IP Holding Company LLC | Malware scanning for network-attached storage systems |
| CN110781507A (en) * | 2019-10-21 | 2020-02-11 | 中广核工程有限公司 | File authority control method and device, computer equipment and storage medium |
| 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 (20)
| 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 |
| US5280612A (en) * | 1991-11-26 | 1994-01-18 | International Business Machines Corporation | Multiple version database concurrency control system |
| 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 |
| US8150820B1 (en) * | 2007-10-04 | 2012-04-03 | Adobe Systems Incorporated | Mechanism for visible users and groups |
| US8453215B1 (en) * | 2010-10-25 | 2013-05-28 | Go Daddy Operating Company, LLC | Suggesting access permission changes to lock a website |
| US20140156960A1 (en) * | 2012-11-30 | 2014-06-05 | Red Hat Israel, Ltd. | Managing permissions for logical volume managers |
| US20190278924A1 (en) * | 2015-04-17 | 2019-09-12 | Dropbox, Inc. | Collection folder for collecting file submissions in response to a public file request |
| WO2017028688A1 (en) * | 2015-08-14 | 2017-02-23 | 阿里巴巴集团控股有限公司 | Method, device and system for reading and writing files |
| US20170075919A1 (en) * | 2015-09-14 | 2017-03-16 | Salesforce.Com, Inc. | Publication of collaborative file to library |
| CN109154969A (en) * | 2016-06-13 | 2019-01-04 | 弗霍斯公司 | The system and method for secure storage for the user information in user profile |
| 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 |
| US9892242B1 (en) * | 2017-04-28 | 2018-02-13 | Global Tel*Link Corporation | Unified enterprise management of wireless devices in a controlled environment |
| US20190332770A1 (en) * | 2018-04-30 | 2019-10-31 | 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 |
| CN110781507A (en) * | 2019-10-21 | 2020-02-11 | 中广核工程有限公司 | File authority control method and device, computer equipment and storage medium |
Cited By (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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112905533B (en) | 2023-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110620810B (en) | Non-linked ownership of continuous asset transfer over blockchain | |
| US10860784B2 (en) | Collaborative email with hierarchical signature authority | |
| EP0745239B1 (en) | Method and apparatus to secure distributed digital directory object changes | |
| EP1917608B1 (en) | Security in peer to peer synchronization applications | |
| US10331443B2 (en) | Data organization procedure and development environment system | |
| US8700560B2 (en) | Populating a multi-relational enterprise social network with disparate source data | |
| US6973463B2 (en) | Replication architecture for a directory server | |
| US20050177715A1 (en) | Method and system for managing identities in a peer-to-peer networking environment | |
| US20060242210A1 (en) | Contact management update protocols | |
| US20030088654A1 (en) | Directory server schema replication | |
| JP2004528636A (en) | Automatic data update | |
| US7457826B2 (en) | Systems and methods for synchronization of items without snapshots | |
| CN113672966B (en) | File access control method and system | |
| JPH1021061A (en) | Automatic version-up system for client software | |
| CN110309494A (en) | Method, device and computer equipment for synchronously editing documents based on page side | |
| GB2399663A (en) | Synchronising content between two sources using profiles | |
| CN112905533A (en) | File submission management method, device, equipment and storage medium | |
| US10657139B2 (en) | Information processing apparatus and non-transitory computer readable medium for distributed resource management | |
| US20030088615A1 (en) | Update resolution procedure for a directory server | |
| JP2003281118A (en) | Document management device, document edit device, document management method, document edit method and program | |
| US6681233B1 (en) | Data circulation between servers and clients | |
| Salehi | Integration of blockchain technologie in case of systems engineering and software engineering in an industrial context | |
| CN111526198A (en) | Data synchronization method and device for server and computer readable storage medium | |
| JPH07271569A (en) | Program specification preparation system | |
| US20040158564A1 (en) | System and method for facilitating information transformations |
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 |