IP Library Granted Patent US 10,733,256
Granted Patent B2
US 10,733,256 · App. 15/040,133 · Granted Aug 4, 2020

Online publication system and method

Inventors: Horst Fickenscher (Berlin, DE); Niall Kelly (Berlin, DE); Vyacheslav Zholudev (Berlin, DE); Darren Alvares (Berlin, DE); Stephen Mansfield (Berlin, DE)
Assignee: ResearchGate GmbH
G06F16/955G06F3/0482G06F3/04842G06F16/1794G06F16/22G06F16/2255G06F16/245G06F16/248G06F16/93G06F16/9535G06F40/117G06F40/123G06F40/14G06F40/166G06F40/169G06F40/197G06F40/20G06F40/205G06F40/221
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,733,256
App. No.
15/040,133
Granted
Aug 4, 2020
Kind
B2
Abstract

Various systems and methods for creating, storing, structuring, displaying, enhancing, and/or referencing publications and related content in an online user network are described. In some embodiments, documents are stored in the form of individually addressable document elements in conjunction with an ordered list of the document elements. Updates to a document can then be analyzed to identify omissions of document elements and/or additions of new document elements, which can be reflected in an updated list of document elements.

Claims (49)

1. A method comprising:

at a publication server,

receiving a document;

analyzing contents of the document to identify a plurality of document elements that collectively constitute the contents of the document,

creating a first representation of the document by storing, in one or more databases, entries for the plurality of document elements and a first document view representing the document as a whole, each document-element entry comprising a unique document-element identifier and one or more document-element attributes characterizing a content of the respective document element, and the first document view comprising an ordered list of document-element identifiers, but not document-element attributes, of the plurality of document elements;

associating a first version identifier with the first document view;

receiving an update to the document, the update comprising a change to at least one of the document elements;

analyzing the update to identify one or more document-element omissions and one or more added document elements that collectively constitute the update, wherein the change within the at least one document element is treated as an omission of that document element and an addition of a new document element reflecting the change;

creating a second representation of the document, corresponding to the document as modified by the received update, by creating, in the one or more databases, entries for the added document elements and a second document view representing the modified document as a whole,

wherein each added document-element entry comprises a unique document-element identifier and one or more document-element attributes characterizing a content of the respective document element,

wherein the second document view comprises an updated list of document-element identifiers, but not document-element attributes, of all document elements of the modified document, including both document elements overlapping with the first representation and the one or more added document elements and not including any omitted document elements, and

wherein a document-element identifier of the at least one document-element subject to the change is replaced in the updated list by a document-element identifier of the at least one new document element reflecting the change; and

associating a second version identifier with the second document view,

wherein the first and second document views are stored in one or more data structures separate from the document-element entries, and wherein creating the second representation of the document affects neither the document-element entries of the first representation of the document nor the first document view.

2. The method of claim 1 , wherein the first and second version identifiers are based on hashes of document-element identifiers associated with the document elements listed in the first and second document views, respectively.

3. The method of claim 1 , further comprising receiving an annotation to the document, the annotation being associated with one or more document elements listed for the first document view, but not the second document view.

4. The method of claim 3 , further comprising, in response to user selection of one of the first or second views, creating a user interface screen comprising the document elements listed in the selected view and comprising the annotation only in response to selection of the first view.

5. The method of claim 1 , further comprising associating time stamps with the first and second versions.

6. The method of claim 1 , further comprising:

receiving further updates to the document;

repeating the analyzing, creating, and associating actions for each of the further updates; and

generating a history of the document based on the first document view and the document views created for the respective updates.

7. The method of claim 1 , wherein analyzing the update comprises analyzing the updated document to identify document elements that collectively constitute the contents of the updated document, and comparing the identified document elements against the document elements listed in the first document view.

8. A system comprising:

one or more databases storing a first representation of a document, the first representation comprising database entries for a plurality of document elements collectively constituting contents of the document, and a first document view representing the document as a whole, each document-element entry comprising a unique document-element identifier and one or more document-element attributes characterizing a content of the respective document element, and the first document view comprising an ordered list of document-element identifiers, but not document-element attributes, of the document elements, the first document view having an associated first version identifier; and

one or more processor-implemented modules configured to:

analyze an update to the document that comprises a change to at least one of the document elements to identify one or more document-element omissions and one or more added documents that collectively constitute the update, wherein the change within the at least one document element is treated as an omission of that document element and an addition of a new document element reflecting the change;

create a second representation of the document, corresponding to the document as modified by the received update, by storing, in the one or more databases, entries for the added document elements and a second document view representing the modified document as a whole,

wherein each added document-element entry comprises a unique document-element identifier and one or more document-element attributes characterizing a content of the respective document element,

wherein the second document view comprising an updated list of document-element identifiers, but not document-element attributes, of all document elements of the modified document, including both document elements overlapping with the first representation and the one or more added document elements and not including any omitted document elements, and

wherein a document-element identifier of the at least one document-element subject to the change is replaced in the updated list by a document-element identifier of the at least one new document elements reflecting the change; and

associate a second version identifier with the second document view,

wherein the first and second document views are stored in one or more data structures separate from the document-element entries, and wherein the second representation of the document affects neither the document-element entries of the first representation of the document nor the first document view.

9. The system of claim 8 , wherein the one or more processor-implemented modules are configured to compute the first and second version identifiers based on hashes of document-element identifiers associated with the document elements listed in the first and second document views, respectively.

10. The system of claim 8 , wherein the one or more processor-implemented modules are further configured to receive an annotation to one or more document elements listed for the first document view, but not the second document view.

11. The system of claim 10 , wherein the one or more processor-implemented modules are further configured create, in response to user selection of one of the first or second views, a user interface screen comprising the document elements listed in the selected view and comprising the annotation only in response to selection of the first view.

12. The system of claim 8 , wherein the one or more processor-implemented modules are further configured to associate time stamps with the first and second versions.

13. The system of claim 8 , wherein the one or more processor-implemented modules are further configured to generate a history of the document based on the first document view and a plurality of document views created for a plurality of respective updates to the document.

14. The system of claim 8 , wherein the one or more processor-implemented modules are configured to analyze the update by analyzing the updated document to identify document elements that collectively constitute the contents of the updated document, and comparing the identified document elements against the document elements listed in the first document view.

15. A non-transitory machine-readable medium storing instructions that, when executed by one or more hardware processors, cause the one or more hardware processors to:

in response to receipt of a document,

analyze contents of the document to identify a plurality of document elements that collectively constitute the contents of the document;

create a first representation of the document by storing, in one or more databases, entries for the plurality of document elements and a first document view representing the document as a whole, each document-element entry comprising a unique document-element identifier and one or more document-element attributes characterizing a content of the respective document element, and the first document view comprising an ordered list of document-element identifiers, but not document-element attributes, of the plurality of document elements; and

associate a first version identifier with the first document view; and

in response to receipt of an update to the document that comprises a change to at least one of the document elements,

analyze the update to identify one or more document-element omissions and one or more added document elements that collectively constitute the update, wherein the change within the at least one document element is treated as an omission of that document element and an addition of a new document element reflecting the change;

create a second representation of the document, corresponding to the document as modified by the received update, by creating, in the one or more databases, entries for the added document elements and a second document view representing the modified document as a whole, the second document view comprising an updated list of document-element identifiers, but not document-element attributes, of all document elements of the modified document, including both document elements overlapping with the first representation and the one or more added document elements and not including any omitted document elements, a document-element identifier of the at least one document-element subject to the change being replaced in the updated list by a document-element identifier of the at least one new document element reflecting the change; and

associate a second version identifier with the second document view,

wherein the first and second document views are stored in one or more data structures separate from the document-element entries, and wherein creating the second representation of the document affects neither the document-element entries of the first representation of the document nor the first document view.

Assignments (3)
RELEASE OF SECURITY INTEREST Recorded Jan 7, 2025
From: OBSIDIAN AGENCY SERVICES, INC.
To: RESEARCHGATE GMBH
Reel/Frame 069773/0545 →
SECURITY INTEREST Recorded Nov 7, 2019
From: RESEARCHGATE GMBH
To: OBSIDIAN AGENCY SERVICES, INC.
Reel/Frame 050952/0439 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 23, 2017
From: FICKENSCHER, HORST; KELLY, NIALL; ZHOLUDEV, VYACHESLAV; ALVARES, DARREN; MANSFIELD, STEPHEN
To: RESEARCHGATE GMBH
Reel/Frame 041360/0245 →
Continuity (2)
Provisional Application 62114341 · Feb 10, 2015
Related Publication 20160232143A1 · Aug 11, 2016
Cited By (21)
US 12,197,560 US 12,260,190 US 12,271,849 US 12,314,882 US 12,353,419 US 12,367,011 US 12,379,835 US 12,430,825 US 12,572,867 US 12,573,105 US 12,586,268 US 12,619,833 US 12,639,402 US 12,645,759 US 12,694,636 US 12,699,962 US 12,705,552 US 12,705,579 US 12,711,259 US 12,711,464 US 12,717,468