US 12,242,426 B2
Bi-directional synchronization of content and metadata between repositories
Pardeep Kumar, Bangalore (IN); Vikash Sharma, Bangalore (IN); Varun Pandit, Bangalore (IN); and Anusha Hemanth Veda, Bangalore (IN)
Assigned to OPEN EXT HOLDINGS, INC., Menlo Park, CA (US)
Filed by Open Text Holdings, Inc., San Mateo, CA (US)
Filed on Aug. 31, 2021, as Appl. No. 17/462,789.
Claims priority of provisional application 63/078,826, filed on Sep. 15, 2020.
Prior Publication US 2022/0083510 A1, Mar. 17, 2022
Int. Cl. G06F 16/00 (2019.01); G06F 16/176 (2019.01); G06F 16/178 (2019.01); G06F 16/23 (2019.01); G06F 16/25 (2019.01)
CPC G06F 16/178 (2019.01) [G06F 16/176 (2019.01); G06F 16/2358 (2019.01); G06F 16/256 (2019.01); G06F 16/258 (2019.01)] 17 Claims
OG exemplary drawing
 
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.