Granted Patent B2

US 12,242,426 · App. 17/462,789 · Granted Mar 4, 2025

Inventors: Pardeep Kumar (Bangalore, IN); Vikash Sharma (Bangalore, IN); Varun Pandit (Bangalore, IN); Anusha Hemanth Veda (Bangalore, IN)

Assignee: OPEN EXT HOLDINGS, INC.

G06F16/178G06F16/176G06F16/2358G06F16/256G06F16/258

Abstract

Claims (36)

1. A repository connector system for synchronization comprising:

a synchronization server including a processor and a memory, the synchronization server communicatively connected to a first data repository, the synchronization server communicatively connected to a second data repository, the memory storing instructions executable by the processor for:

configuring one or more content shares from the first data repository to the second data repository, in accordance with one or more user defined mappings of content from the first data repository to the second data repository; and

for each content share;

instantiating a notification service instance associated with a notification service running on a notification server of the repository connector system,

creating a robot account as a collaborator on the content share, the robot account, as a collaborator, monitoring changes on the each content share on the second data repository,

the notification service instance initiating replication of notification records in the second data repository corresponding to the robot account to a local notification database that is local to the notification server and to the repository connector system, and that is remote from the second data repository, and

accessing the local notification database at predetermined regular intervals to identify notification records in the local notification database indicating changes in the second data repository to data of the content share, and synchronizing the changes to the first data repository to synchronize the content share to the first data repository.

2. The system of claim 1 , wherein each of the one or more content shares comprises a mapped content share, the mapped content share mapping a selected subset of content folders on the first data repository to a corresponding set of content folders on the second data repository.

3. The system of claim 2 , wherein each of the selected subset of content folders on the first data repository and the corresponding set of content folders on the second data repository contains one or more content objects, each of the content objects having corresponding metadata.

4. The system of claim 1 , wherein the server configures the one or more content shares according to administrative user input received via an administrative configuration interface.

5. The system of claim 1 , wherein the notification service instance performs a replication loop in which notification records corresponding to the robot account are identified and replicated to the local notification database according to a predetermined schedule.

6. The system of claim 1 , wherein the server performs, according to a predetermined schedule, a synchronization loop in which the server accesses the notification records in the local notification database and synchronizes changes corresponding to the notification records from the second data repository to the first data repository.

7. The system of claim 6 , wherein in the synchronization loop the server parses the notification records in the local notification database, identifies from the notification records changes to specific content objects in the second data repository, and makes identified changes to specific content objects in the first data repository corresponding to the specific content objects in the second data repository.

8. A computer implemented repository connector method for synchronization comprising:

configuring, in a synchronization server of a repository connector system, one or more content shares from a first data repository which is coupled to the synchronization server to a second data repository which is coupled to the synchronization server, in accordance with one or more user defined mappings of content from the first data repository to the second data repository; and

for each content share:

instantiating a notification service instance associated with a notification service running on a notification server of the repository connector system,

creating a robot account as a collaborator on the content share, the robot account, as a collaborator, monitoring changes on the each content share on the second data repository,

the notification service instance initiating replication of notification records in the second data repository corresponding to the robot account to a local notification database that is local to the notification server and to the repository connector system, and that is remote from the second data repository, and

accessing the local notification database at predetermined regular intervals to identify notification records in the local notification database indicating changes in the second data repository to data of the content share, and synchronizing the changes to the first data repository to synchronize the content share to the first data repository.

9. The method of claim 8 , wherein each of the one or more content shares comprises a mapped content share, the mapped content share mapping a selected subset of content folders on the first data repository to a corresponding set of content folders on the second data repository, and wherein each of the selected subset of content folders on the first data repository and the corresponding set of content folders on the second data repository contains one or more content objects, each of the content objects having corresponding metadata.

10. The method of claim 8 , further comprising performing, by the notification service instance, a replication loop in which notification records corresponding to the robot account are identified and replicated to the local notification database according to a predetermined schedule.

11. The method of claim 8 , further comprising performing, by the server according to a predetermined schedule, a synchronization loop in which the server accesses the notification records in the local notification database and synchronizes changes corresponding to the notification records from the second data repository to the first data repository.

12. The method of claim 11 , further comprising, by the server in the synchronization loop, parsing the notification records in the local notification database, identifying from the notification records changes to specific content objects in the second data repository, and making identified changes to specific content objects in the first data repository corresponding to the specific content objects in the second data repository.

13. A computer program product comprising a non-transitory computer-readable medium storing instructions executable by one or more processors to perform:

configuring one or more content shares from a first data repository which is coupled to a synchronization server of a repository connector system, to a second data repository which is coupled to the synchronization server, in accordance with one or more user defined mappings of content from the first data repository to the second data repository;

for each content share;

instantiating a notification service instance associated with a notification service running on a notification server of the repository connector system,

creating a robot account as a collaborator on the content share, the robot account, as a collaborator, monitoring changes on the each content share on the second data repository,

the notification service instance initiating replication of notification records in the second data repository corresponding to the robot account to a local notification database that is local to the notification server and to the repository connector system, and that is remote from the second data repository; and

accessing the local notification database at predetermined regular intervals to identify notification records in the local notification database indicating changes in the second data repository to data of the content share, and synchronizing the changes to the first data repository to synchronize the content share to the first data repository.

14. The computer program product of claim 13 , wherein each of the one or more content shares comprises a mapped content share, the mapped content share mapping a selected subset of content folders on the first data repository to a corresponding set of content folders on the second data repository, and wherein each of the selected subset of content folders on the first data repository and the corresponding set of content folders on the second data repository contains one or more content objects, each of the content objects having corresponding metadata.

15. The computer program product of claim 13 , wherein the instructions are further executable by the one or more processors to perform a replication loop in which notification records corresponding to the robot account are identified and replicated to the local notification database according to a predetermined schedule.

16. The computer program product of claim 13 , wherein the instructions are further executable by the one or more processors to perform, according to a predetermined schedule, a synchronization loop in which the server accesses the notification records in the local notification database and synchronizes changes corresponding to the notification records from the second data repository to the first data repository.

17. The computer program product of claim 16 , wherein the instructions are further executable by the one or more processors to perform, in the synchronization loop, parsing the notification records in the local notification database, identifying from the notification records changes to specific content objects in the second data repository, and making identified changes to specific content objects in the first data repository corresponding to the specific content objects in the second data repository.

Assignments (2)

Continuity (2)

References Cited (41)