US2019155799A1PendingUtilityA1
Unified system for connecting a content repository to a file sharing service
Est. expiryFeb 3, 2034(~7.5 yrs left)· nominal 20-yr term from priority
G06F 16/178G06F 16/235G06F 21/6218
49
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Techniques to provide access to repository content, via a file sharing service, are disclosed. In various embodiments, a revised content associated with a repository content object, reflecting a modification made to the repository content in the context of a file sharing service to which the repository content object was published in connection with a synchronized share of the repository object, is received. It is determined whether the revised content is to be stored in the repository and, if so, the revised content is stored in the repository.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method, comprising:
receiving, from a client device associated with a user, a revised content associated with a repository content object, wherein the revised content corresponds to a version of the repository content object comprising a modification; determining that the revised content is to be stored in the repository based at least in part on one or more policies associated with the user and on a determination of whether the modification is in the context of a file sharing service, wherein at least one of the one or more policies are enforced at an attribute level of content to be shared via the file sharing service; storing the revised content in the repository, wherein the repository is a central repository for a plurality of client devices; and publishing the revised content to the file sharing service in connection with the synchronized share.
2 . The method of claim 1 , wherein the determining that the revised content is to be stored in the repository comprises determining how the revised content is to be shared via the file sharing service, the determining of how the revised content is to be shared via the file-sharing service comprises determining a manner in which the revised content is to be stored in the repository.
3 . The method of claim 1 , wherein the determining that the revised content is to be stored in the repository comprises determining whether to publish the content on the file sharing service based at least in part on whether the modification is in the context of the file sharing service.
4 . The method of claim 1 , wherein the revised content is published to the file sharing service in connection with the synchronized share in response to at least a determination that the revised content is to be published via the file sharing service in connection with a synchronized share.
5 . The method of claim 1 , wherein the revised content is received at least in part by participating in a file sharing service share to which the repository object was published and determining that the revised content has been stored in connection with the file sharing service share.
6 . The method of claim 5 , wherein determining that the revised content has been stored in connection with the file sharing service share comprises receiving an indication that the revised content has been saved in a share folder with which the file sharing service share is associated.
7 . The method of claim 1 , wherein determining that the revised content is to be stored in the repository includes reading a configuration data associated with the synchronized share.
8 . The method of claim 8 , wherein the configuration data indicates that changes made in the context of the file sharing service to the repository object are to be propagated to the repository.
9 . The method of claim 8 , wherein the configuration data indicates a manner in which changes made to the repository object in the context of the file sharing service are to be propagated to the repository.
10 . The method of claim 9 , wherein the manner indicated by the configuration data comprises one or more of the following: an update to a current version of the repository object as stored in the repository; a major version of the repository object as stored in the repository; a minor version of the repository object as stored in the repository; a new repository object; and a clone repository object.
11 . The method of claim 1 , wherein publishing the repository object to the file sharing service in connection with the synchronized share includes determining that the repository object is associated with the synchronize share.
12 . The method of claim 11 , wherein determining that the repository object is associated with the synchronize share includes determining that the repository object is associated with a repository folder with which the synchronized share is associated.
13 . The method of claim 11 , wherein determining that the repository object is associated with the synchronize share includes determining that the repository object includes applying a configuration data to metadata associated with the repository object at the repository to determine that the repository object meets a criteria to be published to the file sharing service in connection with the synchronized share.
14 . The method of claim 13 , wherein the criteria includes one or more of the following: the repository object is of an object type indicated in the configuration data; the repository object is in a format indicated in the configuration data; and the repository object has an attribute value that meets an attribute-based criteria in the configuration data.
15 . The method of claim 1 , wherein the determining that the revised content is to be stored in the repository comprises determining how the revised content is to be shared via the file sharing service based at least in part on based at least in part on one or more policies associated with the user, and one or more higher-level policies to which the one or more policies associated with the user are subject.
16 . The method of claim 1 , wherein the determining that the revised content is to be stored in the repository further comprises applying a conflict resolution process in the event that a conflict between versions of the repository content object.
17 . The method of claim 1 , wherein the determining that the revised content is to be stored in the repository comprises determining how the revised content is to be shared via the file sharing service, the determining of how the revised content is to be shared via the file-sharing service comprises determining an extent to which the revised content is to be stored in the repository.
18 . The method of claim 1 , wherein the determining that the revised content is to be stored in the repository comprises determining a manner in which the revised content is to be stored in the repository based at least in part on at least one policy associated with the user.
19 . The method of claim 1 , wherein the determining that the revised content is to be stored in the repository comprises determining whether the revised content is to be stored so as to overwrite the repository content object.
20 . The method of claim 1 , wherein the one or more policies indicate a manner by which the revised content is to be synchronized.
21 . The method of claim 21 , wherein the one or more policies indicates whether the revised content is to be synchronized one-way or two-way.
22 . A system to provide access to repository content, comprising:
a communication interface; and a processor coupled to the communication interface and configured to:
receive, from a client device associated with a user, via the communication interface a revised content associated with a repository content object, wherein the revised content corresponds to a version of the repository content object comprising a modification;
determine that the revised content is to be stored in the repository based at least in part on one or more policies associated with the user and on a determination of whether the modification is in the context of a file sharing service, wherein at least one of the one or more policies are enforced at an attribute level of content to be shared via the file sharing service;
store the revised content in the repository, wherein the repository is a central repository for a plurality of client devices; and
publish the revised content to the file sharing service in connection with the synchronized share.
23 . A computer program product to provide access to repository content, the computer program product being embodied in a non-transitory computer readable medium and comprising computer instructions for:
receiving, from a client device associated with a user, a revised content associated with a repository content object, wherein the revised content corresponds to a version of the repository content object comprising a modification; determining that the revised content is to be stored in the repository based at least in part on one or more policies associated with the user and on a determination of whether the modification is in the context of a file sharing service, wherein at least one of the one or more policies are enforced at an attribute level of content to be shared via the file sharing service; storing the revised content in the repository, wherein the repository is a central repository for a plurality of client devices; and publishing the revised content to the file sharing service in connection with the synchronized share.Join the waitlist — get patent alerts
Track US2019155799A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.