US20110289401A1 - Multiple graphical annotations of documents using overlays - Google Patents

Multiple graphical annotations of documents using overlays Download PDF

Info

Publication number
US20110289401A1
US20110289401A1 US13/112,855 US201113112855A US2011289401A1 US 20110289401 A1 US20110289401 A1 US 20110289401A1 US 201113112855 A US201113112855 A US 201113112855A US 2011289401 A1 US2011289401 A1 US 2011289401A1
Authority
US
United States
Prior art keywords
document
annotations
overlay window
user
annotation information
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.)
Abandoned
Application number
US13/112,855
Inventor
Ronald F. Fischer
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Salesforce Inc
Original Assignee
Salesforce com Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Salesforce com Inc filed Critical Salesforce com Inc
Priority to US13/112,855 priority Critical patent/US20110289401A1/en
Assigned to SALESFORCE.COM, INC. reassignment SALESFORCE.COM, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FISCHER, RONALD F.
Publication of US20110289401A1 publication Critical patent/US20110289401A1/en
Priority to US14/700,392 priority patent/US9858252B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/10Text processing
    • G06F40/166Editing, e.g. inserting or deleting
    • G06F40/169Annotation, e.g. comment data or footnotes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/10Text processing
    • G06F40/103Formatting, i.e. changing of presentation of documents

Definitions

  • the present generally relates to sharing documents, and more particularly to sharing one or multiple graphical annotations of a document using overlays.
  • the present invention generally relates to document sharing and collaboration, and more particularly to providing graphical annotations of documents using overlays.
  • the techniques are applicable for use in an on-demand database and/or application service or any environment or environments in which electronic documents are shared or exchanged.
  • a computer-implemented method for sharing document annotations.
  • the method typically includes displaying a document on a first graphical user interface, displaying a document overlay window over the document, wherein the document is visible through the overlay window, and receiving annotations from a first user via a user-input device.
  • the input device may include a mouse or keyboard, or a touch screen (e.g., user gestures on a touch-screen, such as a tablet computer, touch-screen peripheral, iPad, or mobile cell phone device such as a Blackberry or an iPhone).
  • the method also typically includes displaying the annotations in the overlay window, storing annotation information, the annotation information including the annotations and positioning information for the overlay window relative to the document, and allowing access to the document and the annotation information to a second user.
  • the method further typically includes displaying the document and the overlay window with the annotations on a second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface.
  • allowing access to the document and the annotation information includes either a) sending to the second user the annotation information and the document, or b) storing the annotation information and the document to a server system, whereby the second user retrieves the stored annotation information and the document from the server system.
  • the positioning information is used to facilitate the alignment of the overlay on devices or systems having a different or alternate resolution interfaces.
  • the first graphical user interface has a first resolution and the second graphical user interface has a second resolution different than the first resolution, wherein displaying the document and the overlay window with the annotations on the second graphical user interface includes scaling the size of the displayed overlay window and annotations to match the second resolution based on the annotation information.
  • a computer-implemented method for sharing document annotations.
  • the method typically includes displaying a document on a graphical user interface, receiving first annotation information for the document created by a first user, the annotation information including first annotations and positioning information for positioning a first overlay window relative to the document; and displaying the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
  • a tangible computer-readable medium stores code which, when executed by one or more processors, causes the processor(s) to display a document on a graphical user interface, to receive first annotation information for the document created by a first user, the annotation information including first annotations and positioning information for positioning a first overlay window relative to the document, and to display the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
  • a tangible computer-readable medium that stores code for enabling sharing of document annotations.
  • the code typically includes instructions that when executed by one or more processor cause the processor(s) to display a document on a first graphical user interface, to display a document overlay window over the document, wherein the document is visible through the overlay window, and to receive annotations from a first user via a user-input device.
  • the code also typically includes instructions to display the annotations in the overlay window, to store annotation information, the annotation information including the annotations and positioning information for the overlay window relative to the document, and to allow access to the document and the annotation information to a second user.
  • the code further typically includes instructions to display the document and the overlay window with the annotations on a second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface.
  • the code to allow access includes either: a) code to send to the second user the annotation information and the document, or b) code to enable the second user to retrieve the annotation information and the document from a server system.
  • a document sharing system typically includes a display device for displaying a graphical user interface, and a processor configured to display a document on the graphical user interface, to receive first annotation information for the document created by a first user, the annotation information including first annotations and positioning information for positioning a first overlay window relative to the document, and to display the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
  • a document sharing system typically includes a first computer system having a display device for displaying a first graphical user interface, and a first processor configured to display a document on the graphical user interface, to display a document overlay window over the document, wherein the document is visible through the overlay window, to receive annotations from a first user via a user-input device, and to display the annotations in the overlay window.
  • the first processor is also typically configured to store annotation information, the annotation information including the annotations and positioning information for the overlay window relative to the document, and to allow access to the document and the annotation information to a second user.
  • the system also typically includes a second computer system, communicably coupled with the first computer system over a network, the second computer system having a display device for displaying a second graphical user interface, and a second processor configured to display the document and the overlay window with the annotations on the second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface.
  • the first processor allows access to the document and the annotation information by a) sending to the second computer system the annotation information and the document, or b) storing the annotation information and the document to a server system, whereby the second computer system retrieves the stored annotation information and the document from the server system.
  • FIG. 1 illustrates a block diagram of an environment wherein an on-demand database service might be used.
  • FIG. 2 illustrates a block diagram of an embodiment of elements of FIG. 1 and various possible interconnections between these elements according to an embodiment of the present invention.
  • FIG. 3 illustrates a method of creating and sharing document annotations according to one embodiment.
  • FIG. 4 a illustrates a graphical user interface display including a document displayed therein;
  • FIG. 4 b illustrates an overlay window displayed over the displayed document.
  • FIG. 5 a illustrates a graphical user interface display on the second user's system where the resolution is the same as on the first user's system
  • FIG. 5 b illustrates a situation where the second user's system has a different resolution and/or aspect ratio than the first user's system.
  • FIG. 6 illustrates an example of an overlay floating over a document according to one embodiment.
  • FIG. 7 illustrates an example of two different overlays displayed over a document according to one embodiment.
  • the present invention provides systems and methods for document sharing and collaboration, and more particularly for providing graphical annotations of documents using overlays.
  • the various embodiments are useful in an on-demand multi-tenant database and/or application service or any system or systems in which electronic documents are shared or exchanged.
  • multi-tenant database system refers to those systems in which various elements of hardware and software of the database system may be shared by one or more customers.
  • a given application server e.g. running an application process
  • a given database table may store rows for a potentially much greater number of customers.
  • FIG. 1 illustrates a block diagram of an environment 10 wherein an on-demand database service might be used.
  • Environment 10 may include user systems 12 , network 14 , system 16 , processor system 17 , application platform 18 , network interface 20 , tenant data storage 22 , system data storage 24 , program code 26 , and process space 28 .
  • environment 10 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above.
  • Environment 10 is an environment in which an on-demand database service exists.
  • User system 12 may be any machine or system that is used by a user to access a database user system.
  • any of user systems 12 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices.
  • user systems 12 might interact via a network 14 with an on-demand database service, which is system 16 .
  • An on-demand database service such as system 16
  • system 16 is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users).
  • Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS).
  • MTS multi-tenant database system
  • “on-demand database service 16 ” and “system 16 ” will be used interchangeably herein.
  • a database image may include one or more database objects.
  • Application platform 18 may be a framework that allows the applications of system 16 to run, such as the hardware and/or software, e.g., the operating system.
  • on-demand database service 16 may include an application platform 18 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 12 , or third party application developers accessing the on-demand database service via user systems 12 .
  • the users of user systems 12 may differ in their respective capacities, and the capacity of a particular user system 12 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 12 to interact with system 16 , that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 16 , that user system has the capacities allotted to that administrator.
  • users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.
  • Network 14 is any network or combination of networks of devices that communicate with one another.
  • network 14 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration.
  • TCP/IP Transfer Control Protocol and Internet Protocol
  • Internet the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein.
  • I Transmission Control Protocol and Internet Protocol
  • User systems 12 might communicate with system 16 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc.
  • HTTP HyperText Transfer Protocol
  • user system 12 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at system 16 .
  • HTTP server might be implemented as the sole network interface between system 16 and network 14 , but other techniques might be used as well or instead.
  • the interface between system 16 and network 14 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.
  • system 16 implements a web-based customer relationship management (CRM) system.
  • system 16 includes application servers configured to implement and execute CRM software applications (application processes) as well as provide related data, code, forms, web pages and other information to and from user systems 12 and to store to, and retrieve from, a database system related data, objects, and Webpage content.
  • CRM software applications application processes
  • data for multiple tenants may be stored in the same physical database object, however, tenant data typically is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared.
  • system 16 implements applications other than, or in addition to, a CRM application.
  • system 16 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application.
  • User (or third party developer) applications which may or may not include CRM, may be supported by the application platform 18 , which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 16 .
  • FIG. 1 One arrangement for elements of system 16 is shown in FIG. 1 , including a network interface 20 , application platform 18 , tenant data storage 22 for tenant data 23 , system data storage 24 for system data 25 accessible to system 16 and possibly multiple tenants, program code 26 for implementing various functions of system 16 , and a process space 28 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 16 include database indexing processes.
  • each user system 12 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection.
  • WAP wireless access protocol
  • User system 12 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 12 to access, process and view information, pages and applications available to it from system 16 over network 14 .
  • HTTP client e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like.
  • Each user system 12 also typically includes one or more user interface devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a graphical user interface (GUI) provided by the browser on a display (e.g., a monitor screen, LCD display, etc.) in conjunction with pages, forms, applications and other information provided by system 16 or other systems or servers.
  • GUI graphical user interface
  • the user interface device can be used to access data and applications hosted by system 16 , such as documents and annotation overlays as discussed below, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user.
  • embodiments are suitable for use with the Internet, which refers to a specific global internetwork of networks. However, it should be understood that other networks can be used instead of the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.
  • VPN virtual private network
  • each user system 12 and all of its components are operator configurable using applications (such as a browser application, a document viewer or editing application, etc.) including computer code run using a central processing unit such as an Intel Pentium® processor or the like.
  • applications such as a browser application, a document viewer or editing application, etc.
  • system 16 and additional instances of an MTS, where more than one is present
  • application(s) including computer code to run using a central processing unit such as processor system 17 , which may include an Intel Pentium® processor or the like, and/or multiple processor units.
  • a computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein.
  • Computer code for operating and configuring system 16 to intercommunicate and to process web pages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
  • any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
  • the entire program code, or portions thereof may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known.
  • a transmission medium e.g., over the Internet
  • any other conventional network connection e.g., extranet, VPN, LAN, etc.
  • any communication medium and protocols e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.
  • computer code for implementing embodiments of the present invention can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, JavaTM, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used.
  • JavaTM is a trademark of Sun Microsystems, Inc.
  • each system 16 is configured to provide web pages, forms, applications, data and media content to user (client) systems 12 to support the access by user systems 12 as tenants of system 16 .
  • system 16 provides security mechanisms to keep each tenant's data separate unless the data is shared.
  • MTS Mobility Management Entity
  • they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B).
  • each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations.
  • server is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein.
  • database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.
  • FIG. 2 also illustrates environment 10 . However, in FIG. 2 elements of system 16 and various interconnections in an embodiment are further illustrated.
  • user system 12 may include processor system 12 A, memory system 12 B, input system 12 C, and output system 12 D.
  • FIG. 2 shows network 14 and system 16 .
  • system 16 may include tenant data storage 22 , tenant data 23 , system data storage 24 , system data 25 , User Interface (UI) 30 , Application Program Interface (API) 32 , PL/SOQL 34 , save routines 36 , application setup mechanism 38 , applications servers 100 1 - 100 N , system process space 102 , tenant process spaces 104 , tenant management process space 110 , tenant storage area 112 , user storage 114 , and application metadata 116 .
  • environment 10 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.
  • processor system 12 A may be any combination of one or more processors.
  • Memory system 12 B may be any combination of one or more memory devices, short term, and/or long term memory.
  • Input system 12 C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks.
  • Output system 12 D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks.
  • system 16 may include a network interface 20 (of FIG.
  • Each application server 100 may be configured to tenant data storage 22 and the tenant data 23 therein, and system data storage 24 and the system data 25 therein to serve requests of user systems 12 .
  • the tenant data 23 might be divided into individual tenant storage areas 112 , which can be either a physical arrangement and/or a logical arrangement of data.
  • user storage 114 and application metadata 116 might be similarly allocated for each user.
  • a UI 30 provides a user interface and an API 32 provides an application programmer interface to system 16 resident processes to users and/or developers at user systems 12 .
  • the tenant data and the system data may be stored in various databases, such as one or more OracleTM databases.
  • Application platform 18 includes an application setup mechanism 38 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 22 by save routines 36 for execution by subscribers as one or more tenant process spaces 104 managed by tenant management process 110 for example. Invocations to such applications may be coded using PL/SOQL 34 that provides a programming language style interface extension to API 32 . A detailed description of some PL/SOQL language embodiments is discussed in commonly owned co-pending U.S. Provisional Patent Application 60/828,192 entitled, PROGRAMMING LANGUAGE METHOD AND SYSTEM FOR EXTENDING APIS TO EXECUTE IN CONJUNCTION WITH DATABASE APIS, by Craig Weissman, filed Oct. 4, 2006, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manages retrieving application metadata 116 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.
  • Each application server 100 may be communicably coupled to database systems, e.g., having access to system data 25 and tenant data 23 , via a different network connection.
  • one application server 100 1 might be coupled via the network 14 (e.g., the Internet)
  • another application server 100 N-1 might be coupled via a direct network link
  • another application server 100 N might be coupled by yet a different network connection.
  • Transfer Control Protocol and Internet Protocol TCP/IP are typical protocols for communicating between application servers 100 and the database system.
  • TCP/IP Transfer Control Protocol and Internet Protocol
  • each application server 100 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 100 .
  • an interface system implementing a load balancing function e.g., an F5 Big-IP load balancer
  • the load balancer uses a least connections algorithm to route user requests to the application servers 100 .
  • Other examples of load balancing algorithms such as round robin and observed response time, also can be used.
  • system 16 is multi-tenant, wherein system 16 handles storage of, and access to, different objects, data and applications across disparate users and organizations.
  • one tenant might be a company that employs a sales force where each salesperson uses system 16 to manage their sales process.
  • a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 22 ).
  • tenant data storage 22 e.g., in tenant data storage 22 .
  • the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.
  • user systems 12 (which may be client systems) communicate with application servers 100 to request and update system-level and tenant-level data from system 16 that may require sending one or more queries to tenant data storage 22 and/or system data storage 24 .
  • System 16 e.g., an application server 100 in system 16
  • System data storage 24 may generate query plans to access the requested data from the database.
  • a table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields.
  • a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc.
  • Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc.
  • Yet another table or object might describe an Opportunity, including fields such as organization, period, forecast type, user, territory, etc.
  • tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields.
  • U.S. patent application Ser. No. 10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields in a Multi-Tenant Database System”, and which is hereby incorporated herein by reference, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system.
  • a system works across any document type by providing visual overlays on top of a document without modifying the original document.
  • Multiple, alternative annotations can exist together or independently.
  • any drawing on an overlay can be immediately shared with other users. Since overlays are transparent, multiple overlays may be shown at the same time. These overlays could be from one or more users. If multiple overlays are created, a display order is maintained in one embodiment. Initially, this can be the order in which they were created, but it is possible to override this default manually. By maintaining an overlay order it is possible to annotate an existing overlay.
  • FIG. 3 illustrates a method 300 of creating and sharing document annotations according to one embodiment.
  • a document is created or accessed or retrieved and displayed on a graphical user interface.
  • a user may create a document to be shared for collaboration using any of a variety of document creation applications, or the user may retrieve a document from storage, or a user may receive a document from another user or source.
  • Examples of document types include text-based documents, image-based documents, video-based documents, or any other document type viewable on a graphical user interface. Specific examples include Word documents, PowerPoint documents, Visio document, Flash-based images or videos, and Excel spreadsheets, however one skilled in the art will understand that any document type may be created or accessed using any document creation or editing application.
  • a document overlay window is displayed over the document, for example in response to a user request to provide annotations to the displayed document.
  • the user request may be by way of accessing a specific application (e.g., a stand-alone application) designed to generate the document overlay, or using functionality included and integrated with a document editing tool.
  • document annotations are input by a user using a user input device, and the annotations are displayed in the overlay window in step 340 .
  • FIG. 4 a illustrates a graphical user interface display 400 including a document 410 displayed therein. As shown, the document 410 represents a text based (e.g., a Word document).
  • FIG. 4 b illustrates an overlay window 420 displayed over document 410 in display 400 .
  • the overlay window 420 includes annotations provided by a user; specifically the annotations shown include two handwritten “circle” marks and some text: “xxxxx”, as input by the user.
  • the boundary of the overlay window is larger than the document, however, the boundary may be configurable such that the user can make the boundary smaller or larger than the document, e.g., by selecting an icon on or by the overlay and adjusting the size/dimensions thereby.
  • FIGS. 6 and 7 show example of smaller overlays displayed over a document. Also, controls are provided to a user to change the positioning of the displayed overlay relative to the document, e.g., by selecting the overlay and dragging to a new position.
  • User input may include handwritten or typed text, or pasting of documents, icons or images selected from the user's system.
  • an overlay includes a transparent work area which aligns with the document, a border indicator to show the bounds of the overlay, and overlay controls.
  • the overlay window within the border indicator is transparent, in certain aspects, to allow unfettered viewing of the document contents.
  • the user can use standard controls to create annotations, e.g., by drawing or typing on top of an overlay, using any user input device, such as a mouse, keyboard, pen or stylus, touch-screen or touch pad, etc. The user's input will appear as if it is located (e.g., written) on top of the underlying document.
  • drawing controls include lines, standard shapes, useful icons, text and images.
  • annotation information is stored to the system, e.g., local system memory, or persisted to a remote memory such as a database system or application server.
  • the stored information includes the annotations provided by the user as well as positioning information such as the position(s) of annotations within the overlay window, and positioning information of the overlay window relative to the document.
  • positioning information might include the document size/resolution, the document zoom, and the document position. Using this information an overlay can be scaled for a different interface such that it closely matches its original position relative to the document on a different interface.
  • the annotation information is shared with another user.
  • the user that creates the annotations allows access to the annotations to a second user.
  • this includes sending the annotation information to the second user (e.g., the second user's computer system) by way of a network connection, such as a VPN, WAN, LAN, Internet, etc.
  • this includes enabling the second user to retrieve the annotation information, e.g., from memory or a server system, such as by sending a link to the annotation information, or otherwise alerting the second user that the annotation information may be accessed.
  • the document may also be sent with, or retrieved with, the annotation information. For example, if the second user already has access to the document, only the annotation information need be enabled for access. This may occur where the second user is the creator of the document, or where the second user may have already accessed the document and asked the first user for comments/annotations.
  • the annotation information accessed or received by the second user is used to generate an overlay on the document on the second users system.
  • the overlay window is displayed with the first user's annotations on the second user's graphical user interface, the second user is able to see the annotations overlaying the document.
  • FIG. 5 a illustrates a graphical user interface display 500 on the second user's system where the resolution is the same as on the first user's system, e.g., overlay window 420 is displayed over document 410 in the same resolution as shown in FIG. 4 b .
  • FIG. 5 b illustrates a situation where the second user's system has a different resolution and/or aspect ratio than the first user's system.
  • the graphical user interface 550 (with a different aspect ratio for example), includes the displayed document (now 560 to indicate a different document aspect ratio or size).
  • the positioning information associated with the overlay is used to appropriately scale the overlay 570 so that the sizing and positions of the displayed annotations relative to the document contents closely match that in the original system.
  • FIG. 6 illustrates an example of an overlay floating over a document. As shown annotations by a user are displayed in the overlay over the document (underlined “the” and an arrow pointing to Sample 2 ).
  • the first user may create a second overlay for the document 410 and allow access to the second user.
  • the second user may access and display the second overlay over the document in addition to the first overlay, or as a replacement for the first overlay.
  • a third user may create a separate overlay for the document and allow access to other users, including the second user.
  • the second user may access and display the third user's overlay (and annotations) over the document in addition to the first user's overlay, or as a replacement for the first user's overlay.
  • a visual indicator may be displayed to indicate the number of available overlays for the document and/or to allow the viewing user to select from among the available overlays.
  • the viewing user may select one, more than one, or all of the available overlays to be simultaneously displayed over the document being viewed.
  • the overlays may be color-coded according to creating user, or otherwise distinguished based on user.
  • FIG. 7 illustrates two different overlays displayed over a document. As shown, overlay 1 is positioned over a different portion of the document than overlay 2 . In the situation where overlay 1 and overlay 2 were created by different users, they may be displayed in different colors or shadings to help the viewing user distinguish the source. Alternatively or additionally, a user indicator such as an icon or text can be displayed with the overlay to identify the source.
  • overlays can be shared in real-time, or in near real time, as the overlay is being created.
  • annotations being input by a user on one system can be transmitted to systems of other users partaking in the collaborative effort as the annotations are being created, or just after the annotations have been created (and the creating user indicates acceptance, for example).
  • a user is able to integrate annotations provided in an overlay into the underlying document. For example, a user may be able select or indicate 0, 1, or a number of the overlays and flatten or permanently integrate them into the underlying document. In FIG. 3 this is represented as step 380 , where the selected overlays are considered to be ‘approved’ and therefore are incorporated into the final document.
  • various overlay controls are provided for use by a user.
  • useful overlay controls include controls to create a new overlay, to save or delete an overlay, to control display parameters of an overlay.
  • one or more of the following user controls are provided:
  • This control allows a user to save an overlay or a set of overlays, along with information relevant to the overlays and the documents (e.g., overlay size/resolution, document name, document page(s), document zoom, display order, etc.)
  • Overlay notes This control allows a user to add additional notes to an overlay which do not actually appear on the overlay (these notes are not annotations of the document).
  • One purpose of these notes may be to provide context or background information.
  • Overlay display control This control allows a user to display an individual overlay or sets of overlays. If sets of overlays are shown, the display order is respected, by default.
  • Overlay default color control To help with discrimination when multiple overlays are shown, this control allows a user to set the default color for an overlay. For instance, different users could use different colors, making it possible, even when all overlays are shown, to determine who specified what.
  • a tool to ‘hide’ sections of the underlying document is provided. While this will not actually delete material from the underlying document (nor cause it to reflow), it will hide that section while the overlay is displayed.
  • the position information includes a percentage of the current screen resolution. For example, if the vertical position is indicated as extending from 20% to 80% from the top to the bottom of the document (and similarly the horizontal position as extending from x % to y % from left to right) this can be used to scale the overlay over a different resolution. The pixel count can change between documents, but the percentage would remain the same.

Abstract

Systems and methods for sharing document annotations. A document is displayed on a graphical user interface and first annotation information for the document is created by a first user, the annotation information including first annotations and positioning information for positioning a first overlay window relative to the document. The first overlay window with the first annotations is displayed over the document wherein the document is visible through the first overlay window. The annotation information is sharable with other users, whereby a different user is able to display the overlay with annotations made by the first user over the document on a different system, and the annotations do not modify the underlying document.

Description

    CROSS-REFERENCES TO RELATED APPLICATIONS
  • This application claims the benefit of U.S. Provisional Application Ser. No. 61/346,844, filed May 20, 2010, the disclosure of which is incorporated herein by reference in its entirety.
  • COPYRIGHT NOTICE
  • A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
  • BACKGROUND
  • The present generally relates to sharing documents, and more particularly to sharing one or multiple graphical annotations of a document using overlays.
  • Often when collaborating on a document there is a desire to annotate the document and consider a variety of information and approaches. For many document types, certain annotation tools already exist (for instance, change tracking in MS Word, or comment balloons in PDF files). These tools either support the direct manipulation of the document or allow users to annotate the documents, share the annotations and eventually coalesce the annotations into one and only one set. It can be cumbersome, however, using existing technologies to remove changes that are part of the document and/or wade through the various changes or comments made by various users when multiple users are commenting on, or modifying a document
  • There is therefore a need for improved systems and methods that overcome the above problems and that provide improved document collaboration capabilities.
  • SUMMARY
  • The present invention generally relates to document sharing and collaboration, and more particularly to providing graphical annotations of documents using overlays. The techniques are applicable for use in an on-demand database and/or application service or any environment or environments in which electronic documents are shared or exchanged.
  • According to one embodiment, a computer-implemented method is provided for sharing document annotations. The method typically includes displaying a document on a first graphical user interface, displaying a document overlay window over the document, wherein the document is visible through the overlay window, and receiving annotations from a first user via a user-input device. The input device may include a mouse or keyboard, or a touch screen (e.g., user gestures on a touch-screen, such as a tablet computer, touch-screen peripheral, iPad, or mobile cell phone device such as a Blackberry or an iPhone). The method also typically includes displaying the annotations in the overlay window, storing annotation information, the annotation information including the annotations and positioning information for the overlay window relative to the document, and allowing access to the document and the annotation information to a second user. The method further typically includes displaying the document and the overlay window with the annotations on a second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface. In certain aspects, allowing access to the document and the annotation information includes either a) sending to the second user the annotation information and the document, or b) storing the annotation information and the document to a server system, whereby the second user retrieves the stored annotation information and the document from the server system. In certain aspects, the positioning information is used to facilitate the alignment of the overlay on devices or systems having a different or alternate resolution interfaces. In certain aspects, the first graphical user interface has a first resolution and the second graphical user interface has a second resolution different than the first resolution, wherein displaying the document and the overlay window with the annotations on the second graphical user interface includes scaling the size of the displayed overlay window and annotations to match the second resolution based on the annotation information.
  • According to another embodiment, a computer-implemented method is provided for sharing document annotations. The method typically includes displaying a document on a graphical user interface, receiving first annotation information for the document created by a first user, the annotation information including first annotations and positioning information for positioning a first overlay window relative to the document; and displaying the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
  • According to yet another embodiment, a tangible computer-readable medium is provided that stores code which, when executed by one or more processors, causes the processor(s) to display a document on a graphical user interface, to receive first annotation information for the document created by a first user, the annotation information including first annotations and positioning information for positioning a first overlay window relative to the document, and to display the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
  • According to still another embodiment, a tangible computer-readable medium is provided that stores code for enabling sharing of document annotations. The code typically includes instructions that when executed by one or more processor cause the processor(s) to display a document on a first graphical user interface, to display a document overlay window over the document, wherein the document is visible through the overlay window, and to receive annotations from a first user via a user-input device. The code also typically includes instructions to display the annotations in the overlay window, to store annotation information, the annotation information including the annotations and positioning information for the overlay window relative to the document, and to allow access to the document and the annotation information to a second user. The code further typically includes instructions to display the document and the overlay window with the annotations on a second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface. In certain aspects, the code to allow access includes either: a) code to send to the second user the annotation information and the document, or b) code to enable the second user to retrieve the annotation information and the document from a server system.
  • According to yet a further embodiment, a document sharing system is provided that typically includes a display device for displaying a graphical user interface, and a processor configured to display a document on the graphical user interface, to receive first annotation information for the document created by a first user, the annotation information including first annotations and positioning information for positioning a first overlay window relative to the document, and to display the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
  • According to still a further embodiment, a document sharing system is provided that typically includes a first computer system having a display device for displaying a first graphical user interface, and a first processor configured to display a document on the graphical user interface, to display a document overlay window over the document, wherein the document is visible through the overlay window, to receive annotations from a first user via a user-input device, and to display the annotations in the overlay window. The first processor is also typically configured to store annotation information, the annotation information including the annotations and positioning information for the overlay window relative to the document, and to allow access to the document and the annotation information to a second user. The system also typically includes a second computer system, communicably coupled with the first computer system over a network, the second computer system having a display device for displaying a second graphical user interface, and a second processor configured to display the document and the overlay window with the annotations on the second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface. In certain aspects, the first processor allows access to the document and the annotation information by a) sending to the second computer system the annotation information and the document, or b) storing the annotation information and the document to a server system, whereby the second computer system retrieves the stored annotation information and the document from the server system.
  • Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples of the invention, the invention is not limited to the examples depicted in the figures.
  • FIG. 1 illustrates a block diagram of an environment wherein an on-demand database service might be used.
  • FIG. 2 illustrates a block diagram of an embodiment of elements of FIG. 1 and various possible interconnections between these elements according to an embodiment of the present invention.
  • FIG. 3 illustrates a method of creating and sharing document annotations according to one embodiment.
  • FIG. 4 a illustrates a graphical user interface display including a document displayed therein; FIG. 4 b illustrates an overlay window displayed over the displayed document.
  • FIG. 5 a illustrates a graphical user interface display on the second user's system where the resolution is the same as on the first user's system; FIG. 5 b illustrates a situation where the second user's system has a different resolution and/or aspect ratio than the first user's system.
  • FIG. 6 illustrates an example of an overlay floating over a document according to one embodiment.
  • FIG. 7 illustrates an example of two different overlays displayed over a document according to one embodiment.
  • DETAILED DESCRIPTION
  • The present invention provides systems and methods for document sharing and collaboration, and more particularly for providing graphical annotations of documents using overlays. The various embodiments are useful in an on-demand multi-tenant database and/or application service or any system or systems in which electronic documents are shared or exchanged.
  • As used herein, the term multi-tenant database system refers to those systems in which various elements of hardware and software of the database system may be shared by one or more customers. For example, a given application server (e.g. running an application process) may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers.
  • System Overview
  • FIG. 1 illustrates a block diagram of an environment 10 wherein an on-demand database service might be used. Environment 10 may include user systems 12, network 14, system 16, processor system 17, application platform 18, network interface 20, tenant data storage 22, system data storage 24, program code 26, and process space 28. In other embodiments, environment 10 may not have all of the components listed and/or may have other elements instead of, or in addition to, those listed above.
  • Environment 10 is an environment in which an on-demand database service exists. User system 12 may be any machine or system that is used by a user to access a database user system. For example, any of user systems 12 can be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in FIG. 1 (and in more detail in FIG. 2) user systems 12 might interact via a network 14 with an on-demand database service, which is system 16.
  • An on-demand database service, such as system 16, is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users). Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, “on-demand database service 16” and “system 16” will be used interchangeably herein. A database image may include one or more database objects. A relational database management system (RDMS) or the equivalent may execute storage and retrieval of information against the database object(s). Application platform 18 may be a framework that allows the applications of system 16 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, on-demand database service 16 may include an application platform 18 that enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 12, or third party application developers accessing the on-demand database service via user systems 12.
  • The users of user systems 12 may differ in their respective capacities, and the capacity of a particular user system 12 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 12 to interact with system 16, that user system has the capacities allotted to that salesperson. However, while an administrator is using that user system to interact with system 16, that user system has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.
  • Network 14 is any network or combination of networks of devices that communicate with one another. For example, network 14 can be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it should be understood that the networks that the present invention might use are not so limited, although TCP/IP is a frequently implemented protocol.
  • User systems 12 might communicate with system 16 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, user system 12 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at system 16. Such an HTTP server might be implemented as the sole network interface between system 16 and network 14, but other techniques might be used as well or instead. In some implementations, the interface between system 16 and network 14 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.
  • In one embodiment, system 16, shown in FIG. 1, implements a web-based customer relationship management (CRM) system. For example, in one embodiment, system 16 includes application servers configured to implement and execute CRM software applications (application processes) as well as provide related data, code, forms, web pages and other information to and from user systems 12 and to store to, and retrieve from, a database system related data, objects, and Webpage content. With a multi-tenant system, data for multiple tenants may be stored in the same physical database object, however, tenant data typically is arranged so that data of one tenant is kept logically separate from that of other tenants so that one tenant does not have access to another tenant's data, unless such data is expressly shared. In certain embodiments, system 16 implements applications other than, or in addition to, a CRM application. For example, system 16 may provide tenant access to multiple hosted (standard and custom) applications, including a CRM application. User (or third party developer) applications, which may or may not include CRM, may be supported by the application platform 18, which manages creation, storage of the applications into one or more database objects and executing of the applications in a virtual machine in the process space of the system 16.
  • One arrangement for elements of system 16 is shown in FIG. 1, including a network interface 20, application platform 18, tenant data storage 22 for tenant data 23, system data storage 24 for system data 25 accessible to system 16 and possibly multiple tenants, program code 26 for implementing various functions of system 16, and a process space 28 for executing MTS system processes and tenant-specific processes, such as running applications as part of an application hosting service. Additional processes that may execute on system 16 include database indexing processes.
  • Several elements in the system shown in FIG. 1 include conventional, well-known elements that are explained only briefly here. For example, each user system 12 could include a desktop personal computer, workstation, laptop, PDA, cell phone, or any wireless access protocol (WAP) enabled device or any other computing device capable of interfacing directly or indirectly to the Internet or other network connection. User system 12 typically runs an HTTP client, e.g., a browsing program, such as Microsoft's Internet Explorer browser, Netscape's Navigator browser, Opera's browser, or a WAP-enabled browser in the case of a cell phone, PDA or other wireless device, or the like, allowing a user (e.g., subscriber of the multi-tenant database system) of user system 12 to access, process and view information, pages and applications available to it from system 16 over network 14. Each user system 12 also typically includes one or more user interface devices, such as a keyboard, a mouse, trackball, touch pad, touch screen, pen or the like, for interacting with a graphical user interface (GUI) provided by the browser on a display (e.g., a monitor screen, LCD display, etc.) in conjunction with pages, forms, applications and other information provided by system 16 or other systems or servers. For example, the user interface device can be used to access data and applications hosted by system 16, such as documents and annotation overlays as discussed below, and to perform searches on stored data, and otherwise allow a user to interact with various GUI pages that may be presented to a user. As discussed above, embodiments are suitable for use with the Internet, which refers to a specific global internetwork of networks. However, it should be understood that other networks can be used instead of the Internet, such as an intranet, an extranet, a virtual private network (VPN), a non-TCP/IP based network, any LAN or WAN or the like.
  • According to one embodiment, each user system 12 and all of its components are operator configurable using applications (such as a browser application, a document viewer or editing application, etc.) including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, system 16 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such as processor system 17, which may include an Intel Pentium® processor or the like, and/or multiple processor units. A computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein. Computer code for operating and configuring system 16 to intercommunicate and to process web pages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for implementing embodiments of the present invention can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).
  • According to one embodiment, each system 16 is configured to provide web pages, forms, applications, data and media content to user (client) systems 12 to support the access by user systems 12 as tenants of system 16. As such, system 16 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.
  • FIG. 2 also illustrates environment 10. However, in FIG. 2 elements of system 16 and various interconnections in an embodiment are further illustrated. FIG. 2 shows that user system 12 may include processor system 12A, memory system 12B, input system 12C, and output system 12D. FIG. 2 shows network 14 and system 16. FIG. 2 also shows that system 16 may include tenant data storage 22, tenant data 23, system data storage 24, system data 25, User Interface (UI) 30, Application Program Interface (API) 32, PL/SOQL 34, save routines 36, application setup mechanism 38, applications servers 100 1-100 N, system process space 102, tenant process spaces 104, tenant management process space 110, tenant storage area 112, user storage 114, and application metadata 116. In other embodiments, environment 10 may not have the same elements as those listed above and/or may have other elements instead of, or in addition to, those listed above.
  • User system 12, network 14, system 16, tenant data storage 22, and system data storage 24 were discussed above in FIG. 1. Regarding user system 12, processor system 12A may be any combination of one or more processors. Memory system 12B may be any combination of one or more memory devices, short term, and/or long term memory. Input system 12C may be any combination of input devices, such as one or more keyboards, mice, trackballs, scanners, cameras, and/or interfaces to networks. Output system 12D may be any combination of output devices, such as one or more monitors, printers, and/or interfaces to networks. As shown by FIG. 2, system 16 may include a network interface 20 (of FIG. 1) implemented as a set of HTTP application servers 100, an application platform 18, tenant data storage 22, and system data storage 24. Also shown is system process space 102, including individual tenant process spaces 104 and a tenant management process space 110. Each application server 100 may be configured to tenant data storage 22 and the tenant data 23 therein, and system data storage 24 and the system data 25 therein to serve requests of user systems 12. The tenant data 23 might be divided into individual tenant storage areas 112, which can be either a physical arrangement and/or a logical arrangement of data. Within each tenant storage area 112, user storage 114 and application metadata 116 might be similarly allocated for each user. For example, a copy of a user's most recently used (MRU) items might be stored to user storage 114. Similarly, a copy of MRU items for an entire organization that is a tenant might be stored to tenant storage area 112. A UI 30 provides a user interface and an API 32 provides an application programmer interface to system 16 resident processes to users and/or developers at user systems 12. The tenant data and the system data may be stored in various databases, such as one or more Oracle™ databases.
  • Application platform 18 includes an application setup mechanism 38 that supports application developers' creation and management of applications, which may be saved as metadata into tenant data storage 22 by save routines 36 for execution by subscribers as one or more tenant process spaces 104 managed by tenant management process 110 for example. Invocations to such applications may be coded using PL/SOQL 34 that provides a programming language style interface extension to API 32. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned co-pending U.S. Provisional Patent Application 60/828,192 entitled, PROGRAMMING LANGUAGE METHOD AND SYSTEM FOR EXTENDING APIS TO EXECUTE IN CONJUNCTION WITH DATABASE APIS, by Craig Weissman, filed Oct. 4, 2006, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manages retrieving application metadata 116 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.
  • Each application server 100 may be communicably coupled to database systems, e.g., having access to system data 25 and tenant data 23, via a different network connection. For example, one application server 100 1 might be coupled via the network 14 (e.g., the Internet), another application server 100 N-1 might be coupled via a direct network link, and another application server 100 N might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 100 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.
  • In certain embodiments, each application server 100 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 100. In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 100 and the user systems 12 to distribute requests to the application servers 100. In one embodiment, the load balancer uses a least connections algorithm to route user requests to the application servers 100. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain embodiments, three consecutive requests from the same user could hit three different application servers 100, and three requests from different users could hit the same application server 100. In this manner, system 16 is multi-tenant, wherein system 16 handles storage of, and access to, different objects, data and applications across disparate users and organizations.
  • As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses system 16 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in tenant data storage 22). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.
  • While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by system 16 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant-specific data, system 16 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.
  • In certain embodiments, user systems 12 (which may be client systems) communicate with application servers 100 to request and update system-level and tenant-level data from system 16 that may require sending one or more queries to tenant data storage 22 and/or system data storage 24. System 16 (e.g., an application server 100 in system 16) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. System data storage 24 may generate query plans to access the requested data from the database.
  • A table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. Yet another table or object might describe an Opportunity, including fields such as organization, period, forecast type, user, territory, etc.
  • In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. U.S. patent application Ser. No. 10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields in a Multi-Tenant Database System”, and which is hereby incorporated herein by reference, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system.
  • Graphical Annotations of Documents Using Overlays
  • Often when collaborating on a document there is a desire to annotate the document and consider a variety of information and approaches. This is true whether the document under discussion is primarily text, image, graphical design, video or some other document type. The collaboration can include a single user or multiple users proposing changes or modifications either offline, or in a live, online setting. For most specific document types, certain annotation tools already exist (for instance, change tracking in MS Word, or comment balloons in PDF files). These tools either support the direct manipulation of the document or allow users to annotate the documents, share the annotations and eventually coalesce the annotations into one and only one set.
  • According to one embodiment, a system is provided that works across any document type by providing visual overlays on top of a document without modifying the original document. Multiple, alternative annotations can exist together or independently.
  • In an interactive online environment, any drawing on an overlay can be immediately shared with other users. Since overlays are transparent, multiple overlays may be shown at the same time. These overlays could be from one or more users. If multiple overlays are created, a display order is maintained in one embodiment. Initially, this can be the order in which they were created, but it is possible to override this default manually. By maintaining an overlay order it is possible to annotate an existing overlay.
  • Document Overlays
  • FIG. 3 illustrates a method 300 of creating and sharing document annotations according to one embodiment. In step 310, a document is created or accessed or retrieved and displayed on a graphical user interface. For example, a user may create a document to be shared for collaboration using any of a variety of document creation applications, or the user may retrieve a document from storage, or a user may receive a document from another user or source. Examples of document types include text-based documents, image-based documents, video-based documents, or any other document type viewable on a graphical user interface. Specific examples include Word documents, PowerPoint documents, Visio document, Flash-based images or videos, and Excel spreadsheets, however one skilled in the art will understand that any document type may be created or accessed using any document creation or editing application.
  • In step 320, a document overlay window is displayed over the document, for example in response to a user request to provide annotations to the displayed document. The user request may be by way of accessing a specific application (e.g., a stand-alone application) designed to generate the document overlay, or using functionality included and integrated with a document editing tool. In step 330, document annotations are input by a user using a user input device, and the annotations are displayed in the overlay window in step 340. FIG. 4 a illustrates a graphical user interface display 400 including a document 410 displayed therein. As shown, the document 410 represents a text based (e.g., a Word document). FIG. 4 b illustrates an overlay window 420 displayed over document 410 in display 400. As shown in FIG. 4 b, the overlay window 420 includes annotations provided by a user; specifically the annotations shown include two handwritten “circle” marks and some text: “xxxxx”, as input by the user. Also as shown, the boundary of the overlay window is larger than the document, however, the boundary may be configurable such that the user can make the boundary smaller or larger than the document, e.g., by selecting an icon on or by the overlay and adjusting the size/dimensions thereby. FIGS. 6 and 7 show example of smaller overlays displayed over a document. Also, controls are provided to a user to change the positioning of the displayed overlay relative to the document, e.g., by selecting the overlay and dragging to a new position.
  • User input may include handwritten or typed text, or pasting of documents, icons or images selected from the user's system. In one embodiment, an overlay includes a transparent work area which aligns with the document, a border indicator to show the bounds of the overlay, and overlay controls. The overlay window within the border indicator is transparent, in certain aspects, to allow unfettered viewing of the document contents. The user can use standard controls to create annotations, e.g., by drawing or typing on top of an overlay, using any user input device, such as a mouse, keyboard, pen or stylus, touch-screen or touch pad, etc. The user's input will appear as if it is located (e.g., written) on top of the underlying document. In certain aspects, drawing controls include lines, standard shapes, useful icons, text and images.
  • In step 350, annotation information is stored to the system, e.g., local system memory, or persisted to a remote memory such as a database system or application server. The stored information includes the annotations provided by the user as well as positioning information such as the position(s) of annotations within the overlay window, and positioning information of the overlay window relative to the document. To facilitate the alignment of the overlay relative to the document on devices or systems having a different or alternate resolution interfaces such positioning information might include the document size/resolution, the document zoom, and the document position. Using this information an overlay can be scaled for a different interface such that it closely matches its original position relative to the document on a different interface.
  • In step 360, the annotation information is shared with another user. For example, in one embodiment, the user that creates the annotations allows access to the annotations to a second user. In one embodiment, this includes sending the annotation information to the second user (e.g., the second user's computer system) by way of a network connection, such as a VPN, WAN, LAN, Internet, etc. In another embodiment, this includes enabling the second user to retrieve the annotation information, e.g., from memory or a server system, such as by sending a link to the annotation information, or otherwise alerting the second user that the annotation information may be accessed. In certain embodiments, the document may also be sent with, or retrieved with, the annotation information. For example, if the second user already has access to the document, only the annotation information need be enabled for access. This may occur where the second user is the creator of the document, or where the second user may have already accessed the document and asked the first user for comments/annotations.
  • In step 370, the annotation information accessed or received by the second user is used to generate an overlay on the document on the second users system. When the overlay window is displayed with the first user's annotations on the second user's graphical user interface, the second user is able to see the annotations overlaying the document. FIG. 5 a illustrates a graphical user interface display 500 on the second user's system where the resolution is the same as on the first user's system, e.g., overlay window 420 is displayed over document 410 in the same resolution as shown in FIG. 4 b. FIG. 5 b illustrates a situation where the second user's system has a different resolution and/or aspect ratio than the first user's system. Here the graphical user interface 550 (with a different aspect ratio for example), includes the displayed document (now 560 to indicate a different document aspect ratio or size). The positioning information associated with the overlay is used to appropriately scale the overlay 570 so that the sizing and positions of the displayed annotations relative to the document contents closely match that in the original system.
  • FIG. 6 illustrates an example of an overlay floating over a document. As shown annotations by a user are displayed in the overlay over the document (underlined “the” and an arrow pointing to Sample 2).
  • The first user may create a second overlay for the document 410 and allow access to the second user. The second user may access and display the second overlay over the document in addition to the first overlay, or as a replacement for the first overlay. Similarly, a third user may create a separate overlay for the document and allow access to other users, including the second user. The second user may access and display the third user's overlay (and annotations) over the document in addition to the first user's overlay, or as a replacement for the first user's overlay. For example, in one embodiment, when multiple overlays are available for display over a document (whether created by the same user or multiple users) a visual indicator may be displayed to indicate the number of available overlays for the document and/or to allow the viewing user to select from among the available overlays. For example, the viewing user may select one, more than one, or all of the available overlays to be simultaneously displayed over the document being viewed. In certain aspects, where multiple overlays are available for display, the overlays may be color-coded according to creating user, or otherwise distinguished based on user. FIG. 7 illustrates two different overlays displayed over a document. As shown, overlay 1 is positioned over a different portion of the document than overlay 2. In the situation where overlay 1 and overlay 2 were created by different users, they may be displayed in different colors or shadings to help the viewing user distinguish the source. Alternatively or additionally, a user indicator such as an icon or text can be displayed with the overlay to identify the source.
  • It should be appreciated that overlays can be shared in real-time, or in near real time, as the overlay is being created. For example, in an on-line interactive collaboration session, annotations being input by a user on one system can be transmitted to systems of other users partaking in the collaborative effort as the annotations are being created, or just after the annotations have been created (and the creating user indicates acceptance, for example).
  • In one embodiment, a user is able to integrate annotations provided in an overlay into the underlying document. For example, a user may be able select or indicate 0, 1, or a number of the overlays and flatten or permanently integrate them into the underlying document. In FIG. 3 this is represented as step 380, where the selected overlays are considered to be ‘approved’ and therefore are incorporated into the final document.
  • Overlay Controls
  • According to one embodiment, various overlay controls are provided for use by a user. Examples of useful overlay controls include controls to create a new overlay, to save or delete an overlay, to control display parameters of an overlay. In one embodiment, one or more of the following user controls are provided:
  • 1) Create new overlay. This control allows a user to create a new overlay for a document, or page of a document. Note that support for more than one overlay is useful as it allows for alternate annotations.
  • 2) Save overlays. This control allows a user to save an overlay or a set of overlays, along with information relevant to the overlays and the documents (e.g., overlay size/resolution, document name, document page(s), document zoom, display order, etc.)
  • 3) Delete overlays. This control allows a user to delete specific overlays or sets of overlays which are no longer needed.
  • 4) Overlay notes. This control allows a user to add additional notes to an overlay which do not actually appear on the overlay (these notes are not annotations of the document). One purpose of these notes may be to provide context or background information.
  • 5) Overlay display control. This control allows a user to display an individual overlay or sets of overlays. If sets of overlays are shown, the display order is respected, by default.
  • 6) Overlay default color control. To help with discrimination when multiple overlays are shown, this control allows a user to set the default color for an overlay. For instance, different users could use different colors, making it possible, even when all overlays are shown, to determine who specified what.
  • In one embodiment, a tool to ‘hide’ sections of the underlying document is provided. While this will not actually delete material from the underlying document (nor cause it to reflow), it will hide that section while the overlay is displayed.
  • Overlay Positioning and Scaling
  • In one embodiment, to properly show an overlay across different systems or in different viewings of a document, certain pieces of information are persisted with each overlay set: the document size/resolution, the document zoom, and the document position. Using this information it is possible to scale the overlays such that they closely match their original position. In one embodiment, the position information includes a percentage of the current screen resolution. For example, if the vertical position is indicated as extending from 20% to 80% from the top to the bottom of the document (and similarly the horizontal position as extending from x % to y % from left to right) this can be used to scale the overlay over a different resolution. The pixel count can change between documents, but the percentage would remain the same.
  • While the invention has been described by way of example and in terms of the specific embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements.

Claims (27)

1. A computer-implemented method of sharing document annotations, the method comprising:
displaying a document on a first graphical user interface;
displaying a document overlay window over the document, wherein the document is visible through the overlay window,
receiving annotations from a first user via a user-input device; and
displaying the annotations in the overlay window;
storing annotation information, said annotation information including the annotations and positioning information for the overlay window relative to the document;
allowing access to the document and the annotation information to a second user, and
displaying the document and the overlay window with said annotations on a second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface.
2. The method of claim 1, further including:
receiving second annotation information from a third user, said second annotation information including second annotations and positioning information for positioning a second overlay window relative to the document; and
allowing access to the second annotation information by a second user.
3. The method of claim 2, further including displaying the second overlay window with the second annotations over the first overlay window, whereby the second user is able to see both annotations overlaying the document on the second graphical user interface.
4. The method of claim 3, wherein the first annotations are displayed in a first color, wherein the second annotations are displayed in a second color different than the first color.
5. The method of claim 2, further including:
displaying a selectable indicator for the second overlay window; and
upon selection of the selectable indicator by the second user:
removing the first overlay window from the display; and
displaying the second overlay window with the second annotations over the document, whereby the second user is able to see the second annotations overlaying the document on the second graphical user interface.
6. The method of claim 1, wherein allowing access includes sending to the second user the annotation information and the document.
7. The method of claim 1, wherein allowing access includes enabling the second user to retrieve the annotation information and the document from a server system.
8. The method of claim 1, wherein the first graphical user interface has a first resolution and the second graphical user interface has a second resolution different than the first resolution, and wherein displaying the document and the overlay window with said annotations on the second graphical user interface includes scaling the size of the displayed overlay window and annotations to match the second resolution based on the annotation information.
9. The method of claim 1, further including:
receiving second annotation information from the first user, said second annotation information including second annotations and positioning information for positioning a second overlay window relative to the document;
allowing access to the second annotation information by a second user; and
displaying one or both of the first and second overlay windows over the document responsive to input from the second user.
10. The method of claim 1, further including integrating the annotations into the document responsive to user input.
11. The method of claim 1, wherein the document includes one of a text-based document, an image-based document or a video-based document.
12. The method of claim 1, wherein the positioning information includes document size information, document zoom information and document position information.
13. The method of claim 1, further including temporarily removing the annotations from the displayed overlay window on the second graphical user interface responsive to input from the second user.
14. A computer-implemented method of sharing document annotations, the method comprising:
displaying a document on a graphical user interface;
receiving first annotation information for the document created by a first user, said annotation information including first annotations and positioning information for positioning a first overlay window relative to the document; and
displaying the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
15. The method of claim 14, further including receiving second annotation information for the document created by a second user, said second annotation information including second annotations and positioning information for positioning a second overlay window relative to the document.
16. The method of claim 15, further including receiving a selection from a user identifying one of the first overlay window or the second overlay window; and responsive thereto displaying one of the first or the second overlay window with the first or second annotations, respectively, over the document wherein the document is visible through the displayed overlay window.
17. The method of claim 15, further including displaying the second overlay window with the second annotations over the first overlay window, wherein the document is visible through the displayed overlay windows.
18. The method of claim 17, wherein the first annotations are displayed in a first color, and wherein the second annotations are displayed in a second color different than the first color.
19. The method of claim 14, further including receiving second annotation information for the document created by the first user, said second annotation information including second annotations and positioning information for positioning a second overlay window relative to the document.
20. The method of claim 19, further including receiving a selection from a user identifying one of the first overlay window or the second overlay window; and responsive thereto displaying one of the first or the second overlay window with the first or second annotations, respectively, over the document wherein the document is visible through the displayed overlay window.
21. The method of claim 17, further including displaying the second overlay window with the second annotations over the first overlay window, wherein the document is visible through the displayed overlay windows.
22. A tangible computer-readable medium that stores code that, when executed by one or more processors, causes the processor(s) to:
display a document on a graphical user interface;
receive first annotation information for the document created by a first user, said annotation information including first annotations and positioning information for positioning a first overlay window relative to the document; and
display the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
23. A tangible computer-readable medium that stores code for enabling sharing of document annotations, wherein the code includes instructions that when executed by one or more processor cause the processor(s) to:
display a document on a first graphical user interface;
display a document overlay window over the document, wherein the document is visible through the overlay window,
receive annotations from a first user via a user-input device; and
display the annotations in the overlay window;
store annotation information, said annotation information including the annotations and positioning information for the overlay window relative to the document;
allow access to the document and the annotation information to a second user, and
display the document and the overlay window with said annotations on a second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface.
24. The computer-readable medium of claim 23, wherein the code to allow access includes either: a) code to send to the second user the annotation information and the document, or b) code to enable the second user to retrieve the annotation information and the document from a server system.
25. A document sharing system, comprising:
a display device for displaying a graphical user interface; and
a processor configured to:
display a document on the graphical user interface;
receive first annotation information for the document created by a first user, said annotation information including first annotations and positioning information for positioning a first overlay window relative to the document; and
display the first overlay window with the first annotations over the document wherein the document is visible through the first overlay window.
26. A document sharing system, comprising:
a first computer system having a display device for displaying a first graphical user interface, and a first processor configured to:
display a document on the graphical user interface;
display a document overlay window over the document, wherein the document is visible through the overlay window,
receive annotations from a first user via a user-input device;
display the annotations in the overlay window;
store annotation information, said annotation information including the annotations and positioning information for the overlay window relative to the document; and
allow access to the document and the annotation information to a second user, and
a second computer system, communicably coupled with the first computer system over a network, the second computer system having a display device for displaying a second graphical user interface, and a second processor configured to:
display the document and the overlay window with said annotations on the second graphical user interface, whereby the second user is able to see the annotations overlaying the document when the overlay window is displayed on the second graphical user interface.
27. The system of claim 26, wherein the first processor allows access to the document and the annotation information by a) sending to the second computer system the annotation information and the document, or b) storing the annotation information and the document to a server system, whereby the second computer system retrieves the stored annotation information and the document from the server system.
US13/112,855 2010-05-20 2011-05-20 Multiple graphical annotations of documents using overlays Abandoned US20110289401A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/112,855 US20110289401A1 (en) 2010-05-20 2011-05-20 Multiple graphical annotations of documents using overlays
US14/700,392 US9858252B2 (en) 2010-05-20 2015-04-30 Multiple graphical annotations of documents using overlays

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US34684410P 2010-05-20 2010-05-20
US13/112,855 US20110289401A1 (en) 2010-05-20 2011-05-20 Multiple graphical annotations of documents using overlays

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/700,392 Division US9858252B2 (en) 2010-05-20 2015-04-30 Multiple graphical annotations of documents using overlays

Publications (1)

Publication Number Publication Date
US20110289401A1 true US20110289401A1 (en) 2011-11-24

Family

ID=44973493

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/112,855 Abandoned US20110289401A1 (en) 2010-05-20 2011-05-20 Multiple graphical annotations of documents using overlays
US14/700,392 Active US9858252B2 (en) 2010-05-20 2015-04-30 Multiple graphical annotations of documents using overlays

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/700,392 Active US9858252B2 (en) 2010-05-20 2015-04-30 Multiple graphical annotations of documents using overlays

Country Status (1)

Country Link
US (2) US20110289401A1 (en)

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120174009A1 (en) * 2010-12-29 2012-07-05 Samsung Electronics Co., Ltd. Method for inputting memo in touch screen terminal and device thereof
US20130091550A1 (en) * 2011-10-11 2013-04-11 Paramount Pictures Corporation Systems and methods for controlling access to content distributed over a network
US20130145269A1 (en) * 2011-09-26 2013-06-06 University Of North Carolina At Charlotte Multi-modal collaborative web-based video annotation system
US20130179805A1 (en) * 2012-01-10 2013-07-11 Adobe Systems Incorporated Sketch annotation tool
US8538942B2 (en) 2008-09-12 2013-09-17 Salesforce.Com, Inc. Method and system for sharing documents between on-demand services
US20150149882A1 (en) * 2013-11-26 2015-05-28 Adobe Systems Incorporated Content adaptation based on selected reviewer comment
US20150149900A1 (en) * 2012-06-29 2015-05-28 Nippon Telegraph And Telephone Corporation Terminal device, annotation method, computer system, and computer program
US20150242064A1 (en) * 2014-02-21 2015-08-27 Toshiba Tec Kabushiki Kaisha Information display apparatus that displays document page
US20150326925A1 (en) * 2014-05-06 2015-11-12 At&T Intellectual Property I, L.P. Embedding Interactive Objects into a Video Session
US20160019195A1 (en) * 2014-05-20 2016-01-21 Jesse Kelly SULTANIK Method and system for posting comments on hosted web pages
US9247146B2 (en) 2012-05-21 2016-01-26 Lg Electronics Inc. Mobile terminal and control method thereof
US20160232144A1 (en) * 2015-02-06 2016-08-11 Liang Zhou Browser extension allowing web users to draw on live web pages
US20170060829A1 (en) * 2015-09-01 2017-03-02 Branchfire, Inc. Method and system for annotation and connection of electronic documents
US20170147537A1 (en) * 2015-11-23 2017-05-25 Canon Kabushiki Kaisha Method, apparatus and system for reproducing a document defined in a page description language
US9858252B2 (en) 2010-05-20 2018-01-02 Salesforce.Com, Inc. Multiple graphical annotations of documents using overlays
US10079039B2 (en) 2011-09-26 2018-09-18 The University Of North Carolina At Charlotte Multi-modal collaborative web-based video annotation system
US10102183B2 (en) * 2013-06-21 2018-10-16 3Rb Llc System for transferring annotations between documents displayed side by side
US20180352012A1 (en) * 2015-09-25 2018-12-06 International Business Machines Corporation Multiplexed, multimodal conferencing
US10416952B2 (en) * 2017-06-27 2019-09-17 Salesforce.Com, Inc. Identifying a viewport within a browser window
US20190370319A1 (en) * 2018-05-30 2019-12-05 Microsoft Technology Licensing, Llc Top-Align Comments: Just-in-time Highlights and Automatic Scrolling
US10628631B1 (en) * 2017-10-31 2020-04-21 Amazon Technologies, Inc. Document editing and feedback
US11310292B2 (en) * 2020-08-13 2022-04-19 Cisco Technology, Inc. Application aware annotations in online collaborative sessions
US20220237367A1 (en) * 2021-01-25 2022-07-28 Microsoft Technology Licensing, Llc Documentation augmentation using role-based user annotations

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5893126A (en) * 1994-09-30 1999-04-06 Intel Corporation Method and apparatus for annotating a computer document incorporating sound
US6342906B1 (en) * 1999-02-02 2002-01-29 International Business Machines Corporation Annotation layer for synchronous collaboration
US20030146934A1 (en) * 2002-02-05 2003-08-07 Bailey Richard St. Clair Systems and methods for scaling a graphical user interface according to display dimensions and using a tiered sizing schema to define display objects
US20040122898A1 (en) * 2002-12-20 2004-06-24 International Business Machines Corporation Collaborative review of distributed content
US20050094732A1 (en) * 2003-10-30 2005-05-05 Debargha Mukherjee Data communications methods, compressed media data decoding methods, compressed media data decoders, articles of manufacture, and data communications systems
US20060200760A1 (en) * 2005-03-04 2006-09-07 Microsoft Corporation Method and system for displaying and interacting with paginated content
US20080222542A1 (en) * 1999-12-07 2008-09-11 Microsoft Corporation System and emthod for annotating an electronic document independently of its content
US7590947B1 (en) * 2004-05-28 2009-09-15 Adobe Systems Incorporated Intelligent automatic window sizing
US8195659B2 (en) * 2005-08-23 2012-06-05 Ricoh Co. Ltd. Integration and use of mixed media documents

Family Cites Families (157)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5649104A (en) 1993-03-19 1997-07-15 Ncr Corporation System for allowing user of any computer to draw image over that generated by the host computer and replicating the drawn image to other computers
US5608872A (en) 1993-03-19 1997-03-04 Ncr Corporation System for allowing all remote computers to perform annotation on an image and replicating the annotated image on the respective displays of other comuters
US7991347B1 (en) 1994-04-07 2011-08-02 Data Innovation Llc System and method for accessing set of digital data at a remote site
US5577188A (en) 1994-05-31 1996-11-19 Future Labs, Inc. Method to provide for virtual screen overlay
US7181758B1 (en) 1994-07-25 2007-02-20 Data Innovation, L.L.C. Information distribution and processing system
GB2300991B (en) 1995-05-15 1997-11-05 Andrew Macgregor Ritchie Serving signals to browsing clients
JPH10504127A (en) 1995-06-09 1998-04-14 フィリップス エレクトロニクス ネムローゼ フェンノートシャップ Method for enabling a user to derive a particular information item from a set of information items, and a system for performing such a method
US5715450A (en) 1995-09-27 1998-02-03 Siebel Systems, Inc. Method of selecting and presenting data from a database using a query language to a user of a computer system
US5831610A (en) 1996-02-23 1998-11-03 Netsuite Development L.P. Designing networks
US5821937A (en) 1996-02-23 1998-10-13 Netsuite Development, L.P. Computer method for updating a network design
US5873096A (en) 1997-10-08 1999-02-16 Siebel Systems, Inc. Method of maintaining a network of partially replicated database system
US6604117B2 (en) 1996-03-19 2003-08-05 Siebel Systems, Inc. Method of maintaining a network of partially replicated database system
WO1998038586A1 (en) 1997-02-26 1998-09-03 Siebel Systems, Inc. Method of determining the visibility to a remote databaseclient of a plurality of database transactions using simplified visibility rules
WO1998038762A2 (en) 1997-02-26 1998-09-03 Siebel Systems, Inc. Determining visibility to a remote database client
AU6183698A (en) 1997-02-26 1998-09-18 Siebel Systems, Inc. Method of determining visibility to a remote database client of a plurality of database transactions having variable visibility strengths
AU6440398A (en) 1997-02-26 1998-09-18 Siebel Systems, Inc. Method of using a cache to determine the visibility to a remote database client of a plurality of database transactions
AU6336698A (en) 1997-02-26 1998-09-29 Siebel Systems, Inc. Distributed relational database
AU6183798A (en) 1997-02-27 1998-09-29 Siebel Systems, Inc. Method of migrating to a successive level of a software distribution incorporating local modifications
WO1998040805A2 (en) 1997-02-27 1998-09-17 Siebel Systems, Inc. Method of synchronizing independently distributed software and database schema
EP1015997A4 (en) 1997-02-28 2006-03-29 Siebel Systems Inc Partially replicated distributed database with multiple levels of remote clients
US5983227A (en) 1997-06-12 1999-11-09 Yahoo, Inc. Dynamic page generator
US6169534B1 (en) 1997-06-26 2001-01-02 Upshot.Com Graphical user interface for customer information management
US6560461B1 (en) 1997-08-04 2003-05-06 Mundi Fomukong Authorized location reporting paging system
US5918159A (en) 1997-08-04 1999-06-29 Fomukong; Mundi Location reporting satellite paging system with optional blocking of location reporting
US6236978B1 (en) 1997-11-14 2001-05-22 New York University System and method for dynamic profiling of users in one-to-one applications
US20020059095A1 (en) 1998-02-26 2002-05-16 Cook Rachael Linette System and method for generating, capturing, and managing customer lead information over a computer network
US6732111B2 (en) 1998-03-03 2004-05-04 Siebel Systems, Inc. Method, apparatus, system, and program product for attaching files and other objects to a partially replicated database
US6772229B1 (en) 2000-11-13 2004-08-03 Groupserve, Inc. Centrifugal communication and collaboration method
US6161149A (en) 1998-03-13 2000-12-12 Groupserve, Inc. Centrifugal communication and collaboration method
US5963953A (en) 1998-03-30 1999-10-05 Siebel Systems, Inc. Method, and system for product configuration
CA2341871A1 (en) 1998-08-27 2000-03-09 Upshot Corporation A method and apparatus for network-based sales force management
AU6410699A (en) 1998-10-13 2000-05-01 Chris Cheah Method and system for controlled distribution of information over a network
US6601087B1 (en) 1998-11-18 2003-07-29 Webex Communications, Inc. Instant document sharing
US6728960B1 (en) 1998-11-18 2004-04-27 Siebel Systems, Inc. Techniques for managing multiple threads in a browser environment
US6549908B1 (en) 1998-11-18 2003-04-15 Siebel Systems, Inc. Methods and apparatus for interpreting user selections in the context of a relation distributed as a set of orthogonalized sub-relations
WO2000033226A1 (en) 1998-11-30 2000-06-08 Siebel Systems, Inc. Smart scripting call centers
JP2002531900A (en) 1998-11-30 2002-09-24 シーベル システムズ,インコーポレイティド Assignment manager
EP1135723A4 (en) 1998-11-30 2005-02-16 Siebel Systems Inc Development tool, method, and system for client server applications
EP1183636A1 (en) 1998-11-30 2002-03-06 Siebel Systems, Inc. State models for monitoring processes
US7356482B2 (en) 1998-12-18 2008-04-08 Alternative Systems, Inc. Integrated change management unit
US6574635B2 (en) 1999-03-03 2003-06-03 Siebel Systems, Inc. Application instantiation based upon attributes and values stored in a meta data repository, including tiering of application layers objects and components
US20020072951A1 (en) 1999-03-03 2002-06-13 Michael Lee Marketing support database management method, system and program product
US6288717B1 (en) 1999-03-19 2001-09-11 Terry Dunkle Headline posting algorithm
US6907566B1 (en) 1999-04-02 2005-06-14 Overture Services, Inc. Method and system for optimum placement of advertisements on a webpage
US8095413B1 (en) 1999-05-07 2012-01-10 VirtualAgility, Inc. Processing management information
US7698160B2 (en) 1999-05-07 2010-04-13 Virtualagility, Inc System for performing collaborative tasks
US6411949B1 (en) 1999-08-12 2002-06-25 Koninklijke Philips Electronics N.V., Customizing database information for presentation with media selections
US6732330B1 (en) * 1999-09-30 2004-05-04 International Business Machines Corporation Scripting language blocks to support multiple scripting languages in a single web page
US6621834B1 (en) 1999-11-05 2003-09-16 Raindance Communications, Inc. System and method for voice transmission over network protocols
US6535909B1 (en) 1999-11-18 2003-03-18 Contigo Software, Inc. System and method for record and playback of collaborative Web browsing session
US6671714B1 (en) 1999-11-23 2003-12-30 Frank Michael Weyer Method, apparatus and business system for online communications with online and offline recipients
US6324568B1 (en) 1999-11-30 2001-11-27 Siebel Systems, Inc. Method and system for distributing objects over a network
US6654032B1 (en) 1999-12-23 2003-11-25 Webex Communications, Inc. Instant sharing of documents on a remote server
US7136860B2 (en) 2000-02-14 2006-11-14 Overture Services, Inc. System and method to determine the validity of an interaction on a network
US6732100B1 (en) 2000-03-31 2004-05-04 Siebel Systems, Inc. Database access method and system for user role defined access
US6577726B1 (en) 2000-03-31 2003-06-10 Siebel Systems, Inc. Computer telephony integration hotelling method and system
US7266502B2 (en) 2000-03-31 2007-09-04 Siebel Systems, Inc. Feature centric release manager method and system
US6336137B1 (en) 2000-03-31 2002-01-01 Siebel Systems, Inc. Web client-server system and method for incompatible page markup and presentation languages
US7730072B2 (en) 2000-04-14 2010-06-01 Rightnow Technologies, Inc. Automated adaptive classification system for knowledge networks
US6665655B1 (en) 2000-04-14 2003-12-16 Rightnow Technologies, Inc. Implicit rating of retrieved information in an information search system
US6434550B1 (en) 2000-04-14 2002-08-13 Rightnow Technologies, Inc. Temporal updates of relevancy rating of retrieved information in an information search system
US6842748B1 (en) 2000-04-14 2005-01-11 Rightnow Technologies, Inc. Usage based strength between related information in an information retrieval system
US6763501B1 (en) 2000-06-09 2004-07-13 Webex Communications, Inc. Remote document serving
EP1307831A4 (en) 2000-07-11 2007-05-09 Yahoo Inc Online playback system with community bias
US7069231B1 (en) 2000-07-20 2006-06-27 Oracle International Corporation Methods and systems for defining, applying and executing customer care relationship plans
KR100365357B1 (en) 2000-10-11 2002-12-18 엘지전자 주식회사 Method for data communication of mobile terminal
US7581230B2 (en) 2001-02-06 2009-08-25 Siebel Systems, Inc. Adaptive communication application programming interface
USD454139S1 (en) 2001-02-20 2002-03-05 Rightnow Technologies Display screen for a computer
US7310687B2 (en) 2001-03-23 2007-12-18 Cisco Technology, Inc. Methods and systems for managing class-based condensation
US6829655B1 (en) 2001-03-28 2004-12-07 Siebel Systems, Inc. Method and system for server synchronization with a computing device via a companion device
US7174514B2 (en) 2001-03-28 2007-02-06 Siebel Systems, Inc. Engine to present a user interface based on a logical structure, such as one for a customer relationship management system, across a web site
US7363388B2 (en) 2001-03-28 2008-04-22 Siebel Systems, Inc. Method and system for direct server synchronization with a computing device
US20030206192A1 (en) 2001-03-31 2003-11-06 Mingte Chen Asynchronous message push to web browser
US20030018705A1 (en) 2001-03-31 2003-01-23 Mingte Chen Media-independent communication server
US6732095B1 (en) 2001-04-13 2004-05-04 Siebel Systems, Inc. Method and apparatus for mapping between XML and relational representations
US7761288B2 (en) 2001-04-30 2010-07-20 Siebel Systems, Inc. Polylingual simultaneous shipping of software
US6782383B2 (en) 2001-06-18 2004-08-24 Siebel Systems, Inc. System and method to implement a persistent and dismissible search center frame
US6711565B1 (en) 2001-06-18 2004-03-23 Siebel Systems, Inc. Method, apparatus, and system for previewing search results
US6728702B1 (en) 2001-06-18 2004-04-27 Siebel Systems, Inc. System and method to implement an integrated search center supporting a full-text search and query on a database
US6763351B1 (en) 2001-06-18 2004-07-13 Siebel Systems, Inc. Method, apparatus, and system for attaching search results
US20030004971A1 (en) 2001-06-29 2003-01-02 Gong Wen G. Automatic generation of data models and accompanying user interfaces
US7370269B1 (en) * 2001-08-31 2008-05-06 Oracle International Corporation System and method for real-time annotation of a co-browsed document
US6993712B2 (en) 2001-09-28 2006-01-31 Siebel Systems, Inc. System and method for facilitating user interaction in a browser environment
US7761535B2 (en) 2001-09-28 2010-07-20 Siebel Systems, Inc. Method and system for server synchronization with a computing device
US6826582B1 (en) 2001-09-28 2004-11-30 Emc Corporation Method and system for using file systems for content management
US6724399B1 (en) 2001-09-28 2004-04-20 Siebel Systems, Inc. Methods and apparatus for enabling keyboard accelerators in applications implemented via a browser
US6978445B2 (en) 2001-09-28 2005-12-20 Siebel Systems, Inc. Method and system for supporting user navigation in a browser environment
US7146617B2 (en) 2001-09-29 2006-12-05 Siebel Systems, Inc. Method, apparatus, and system for implementing view caching in a framework to support web-based applications
US7962565B2 (en) 2001-09-29 2011-06-14 Siebel Systems, Inc. Method, apparatus and system for a mobile web client
US6901595B2 (en) 2001-09-29 2005-05-31 Siebel Systems, Inc. Method, apparatus, and system for implementing a framework to support a web-based application
US8359335B2 (en) 2001-09-29 2013-01-22 Siebel Systems, Inc. Computing system and method to implicitly commit unsaved data for a world wide web application
US7289949B2 (en) 2001-10-09 2007-10-30 Right Now Technologies, Inc. Method for routing electronic correspondence based on the level and type of emotion contained therein
US7062502B1 (en) 2001-12-28 2006-06-13 Kesler John N Automated generation of dynamic data entry user interface for relational database management systems
US6804330B1 (en) 2002-01-04 2004-10-12 Siebel Systems, Inc. Method and system for accessing CRM data via voice
US7058890B2 (en) 2002-02-13 2006-06-06 Siebel Systems, Inc. Method and system for enabling connectivity to a data system
US7672853B2 (en) 2002-03-29 2010-03-02 Siebel Systems, Inc. User interface for processing requests for approval
US7131071B2 (en) 2002-03-29 2006-10-31 Siebel Systems, Inc. Defining an approval process for requests for approval
US6850949B2 (en) 2002-06-03 2005-02-01 Right Now Technologies, Inc. System and method for generating a dynamic interface via a communications network
US7594181B2 (en) 2002-06-27 2009-09-22 Siebel Systems, Inc. Prototyping graphical user interfaces
US8639542B2 (en) 2002-06-27 2014-01-28 Siebel Systems, Inc. Method and apparatus to facilitate development of a customer-specific business process model
US7437720B2 (en) 2002-06-27 2008-10-14 Siebel Systems, Inc. Efficient high-interactivity user interface for client-server applications
US20040010489A1 (en) 2002-07-12 2004-01-15 Rightnow Technologies, Inc. Method for providing search-specific web pages in a network computing environment
US7251787B2 (en) 2002-08-28 2007-07-31 Siebel Systems, Inc. Method and apparatus for an integrated process modeller
US7069497B1 (en) 2002-09-10 2006-06-27 Oracle International Corp. System and method for applying a partial page change
US9448860B2 (en) 2003-03-21 2016-09-20 Oracle America, Inc. Method and architecture for providing data-change alerts to external applications via a push service
US7406501B2 (en) 2003-03-24 2008-07-29 Yahoo! Inc. System and method for instant messaging using an e-mail protocol
JP2006523353A (en) 2003-03-24 2006-10-12 シーベル システムズ,インコーポレイティド Common common object
WO2004086197A2 (en) 2003-03-24 2004-10-07 Siebel Systems, Inc. Custom common object
US7904340B2 (en) 2003-03-24 2011-03-08 Siebel Systems, Inc. Methods and computer-readable medium for defining a product model
US8762415B2 (en) 2003-03-25 2014-06-24 Siebel Systems, Inc. Modeling of order data
US7685515B2 (en) 2003-04-04 2010-03-23 Netsuite, Inc. Facilitating data manipulation in a browser-based user interface of an enterprise business application
US7412455B2 (en) 2003-04-30 2008-08-12 Dillon David M Software framework that facilitates design and implementation of database applications
US7620655B2 (en) 2003-05-07 2009-11-17 Enecto Ab Method, device and computer program product for identifying visitors of websites
US7409336B2 (en) 2003-06-19 2008-08-05 Siebel Systems, Inc. Method and system for searching data based on identified subset of categories and relevance-scored text representation-category combinations
US20040260659A1 (en) 2003-06-23 2004-12-23 Len Chan Function space reservation system
US7237227B2 (en) 2003-06-30 2007-06-26 Siebel Systems, Inc. Application user interface template with free-form layout
US7694314B2 (en) 2003-08-28 2010-04-06 Siebel Systems, Inc. Universal application network architecture
US7779039B2 (en) 2004-04-02 2010-08-17 Salesforce.Com, Inc. Custom entities and fields in a multi-tenant database system
US8046409B2 (en) * 2003-10-31 2011-10-25 Hewlett-Packard Development Company, L.P. Communications methods, collaboration session communications organizers, collaboration sessions, and articles of manufacture
US7269590B2 (en) 2004-01-29 2007-09-11 Yahoo! Inc. Method and system for customizing views of information associated with a social network user
US7289976B2 (en) 2004-12-23 2007-10-30 Microsoft Corporation Easy-to-use data report specification
US7747648B1 (en) 2005-02-14 2010-06-29 Yahoo! Inc. World modeling using a relationship network with communication channels to entities
US20060215630A1 (en) * 2005-03-25 2006-09-28 Cherng-Daw Hwang Feature scalability in a multimedia communication system
US7827208B2 (en) 2006-08-11 2010-11-02 Facebook, Inc. Generating a feed of stories personalized for members of a social network
US7945653B2 (en) 2006-10-11 2011-05-17 Facebook, Inc. Tagging digital media
WO2007103352A2 (en) * 2006-03-03 2007-09-13 Live Cargo, Inc. Systems and methods for document annotation
US7925993B2 (en) 2006-03-30 2011-04-12 Amazon Technologies, Inc. Method and system for aggregating and presenting user highlighting of content
US8566301B2 (en) 2006-05-01 2013-10-22 Steven L. Rueben Document revisions in a collaborative computing environment
US9135228B2 (en) 2006-05-01 2015-09-15 Domo, Inc. Presentation of document history in a web browsing application
US8209308B2 (en) 2006-05-01 2012-06-26 Rueben Steven L Method for presentation of revisions of an electronic document
US20070266335A1 (en) * 2006-05-12 2007-11-15 Microsoft Corporation Providing a standard user interface (UI) across disparate display interfaces
US7853881B1 (en) 2006-07-03 2010-12-14 ISQ Online Multi-user on-line real-time virtual social networks based upon communities of interest for entertainment, information or e-commerce purposes
US7779475B2 (en) 2006-07-31 2010-08-17 Petnote Llc Software-based method for gaining privacy by affecting the screen of a computing device
US8095531B2 (en) 2006-10-03 2012-01-10 Salesforce.Com, Inc. Methods and systems for controlling access to custom objects in a database
US7730478B2 (en) 2006-10-04 2010-06-01 Salesforce.Com, Inc. Method and system for allowing access to developed applications via a multi-tenant on-demand database service
US8082301B2 (en) 2006-11-10 2011-12-20 Virtual Agility, Inc. System for supporting collaborative activity
US8954500B2 (en) 2008-01-04 2015-02-10 Yahoo! Inc. Identifying and employing social network relationships
US8073850B1 (en) 2007-01-19 2011-12-06 Wordnetworks, Inc. Selecting key phrases for serving contextually relevant content
US8719287B2 (en) 2007-08-31 2014-05-06 Business Objects Software Limited Apparatus and method for dynamically selecting componentized executable instructions at run time
US20090100342A1 (en) 2007-10-12 2009-04-16 Gabriel Jakobson Method and system for presenting address and mapping information
US8490025B2 (en) 2008-02-01 2013-07-16 Gabriel Jakobson Displaying content associated with electronic mapping systems
US8504945B2 (en) 2008-02-01 2013-08-06 Gabriel Jakobson Method and system for associating content with map zoom function
US9449333B2 (en) 2008-02-01 2016-09-20 Gabriel Jakobson Online advertising associated with electronic mapping systems
US8032297B2 (en) 2008-05-08 2011-10-04 Gabriel Jakobson Method and system for displaying navigation information on an electronic map
US8014943B2 (en) 2008-05-08 2011-09-06 Gabriel Jakobson Method and system for displaying social networking navigation information
US8646103B2 (en) 2008-06-30 2014-02-04 Gabriel Jakobson Method and system for securing online identities
US8510664B2 (en) 2008-09-06 2013-08-13 Steven L. Rueben Method and system for displaying email thread information
US8661056B1 (en) 2008-11-03 2014-02-25 Salesforce.Com, Inc. System, method and computer program product for publicly providing web content of a tenant using a multi-tenant on-demand database service
US8510045B2 (en) 2009-12-22 2013-08-13 Steven L. Rueben Digital maps displaying search-resulting points-of-interest in user delimited regions
US8583587B2 (en) 2010-03-08 2013-11-12 Salesforce.Com, Inc. System, method and computer program product for performing one or more actions utilizing a uniform resource locator
US8925041B2 (en) 2010-04-01 2014-12-30 Salesforce.Com, Inc. System, method and computer program product for performing one or more actions based on a determined access permissions for a plurality of users
US20110289401A1 (en) 2010-05-20 2011-11-24 Salesforce.Com, Inc. Multiple graphical annotations of documents using overlays
US8566654B2 (en) 2010-08-13 2013-10-22 Salesforce.Com, Inc. Debugging site errors by an admin as a guest user in a multi-tenant database environment
US8943002B2 (en) 2012-02-10 2015-01-27 Liveperson, Inc. Analytics driven engagement
US8769004B2 (en) 2012-02-17 2014-07-01 Zebedo Collaborative web browsing system integrated with social networks
US8756275B2 (en) 2012-02-17 2014-06-17 Zebedo Variable speed collaborative web browsing system
US8769017B2 (en) 2012-02-17 2014-07-01 Zebedo Collaborative web browsing system having document object model element interaction detection

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5893126A (en) * 1994-09-30 1999-04-06 Intel Corporation Method and apparatus for annotating a computer document incorporating sound
US6342906B1 (en) * 1999-02-02 2002-01-29 International Business Machines Corporation Annotation layer for synchronous collaboration
US20080222542A1 (en) * 1999-12-07 2008-09-11 Microsoft Corporation System and emthod for annotating an electronic document independently of its content
US20030146934A1 (en) * 2002-02-05 2003-08-07 Bailey Richard St. Clair Systems and methods for scaling a graphical user interface according to display dimensions and using a tiered sizing schema to define display objects
US20040122898A1 (en) * 2002-12-20 2004-06-24 International Business Machines Corporation Collaborative review of distributed content
US20050094732A1 (en) * 2003-10-30 2005-05-05 Debargha Mukherjee Data communications methods, compressed media data decoding methods, compressed media data decoders, articles of manufacture, and data communications systems
US7590947B1 (en) * 2004-05-28 2009-09-15 Adobe Systems Incorporated Intelligent automatic window sizing
US20060200760A1 (en) * 2005-03-04 2006-09-07 Microsoft Corporation Method and system for displaying and interacting with paginated content
US8195659B2 (en) * 2005-08-23 2012-06-05 Ricoh Co. Ltd. Integration and use of mixed media documents

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Adobe Acrobat 9 PDF Bible, Ted Padova, John Wiley & Sons, Nov 17, 2008, pp 653-731 *
Adobe Acrobat 9 Pro, Version 9.3.1, Feb 2010, pp 1-12 *

Cited By (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8538942B2 (en) 2008-09-12 2013-09-17 Salesforce.Com, Inc. Method and system for sharing documents between on-demand services
US10423715B2 (en) 2008-09-12 2019-09-24 Salesforce.Com, Inc. Method and system for sharing documents between on-demand services
US11227100B2 (en) 2008-09-12 2022-01-18 Salesforce.Com, Inc. Method and system for sharing documents between on-demand services
US9858252B2 (en) 2010-05-20 2018-01-02 Salesforce.Com, Inc. Multiple graphical annotations of documents using overlays
US20120174009A1 (en) * 2010-12-29 2012-07-05 Samsung Electronics Co., Ltd. Method for inputting memo in touch screen terminal and device thereof
US20180358049A1 (en) * 2011-09-26 2018-12-13 University Of North Carolina At Charlotte Multi-modal collaborative web-based video annotation system
US20130145269A1 (en) * 2011-09-26 2013-06-06 University Of North Carolina At Charlotte Multi-modal collaborative web-based video annotation system
US10079039B2 (en) 2011-09-26 2018-09-18 The University Of North Carolina At Charlotte Multi-modal collaborative web-based video annotation system
US9354763B2 (en) * 2011-09-26 2016-05-31 The University Of North Carolina At Charlotte Multi-modal collaborative web-based video annotation system
US20130091550A1 (en) * 2011-10-11 2013-04-11 Paramount Pictures Corporation Systems and methods for controlling access to content distributed over a network
WO2013055766A1 (en) * 2011-10-11 2013-04-18 Paramount Pictures Corporation Systems and methods for controlling access to content distributed over a network
US8495751B2 (en) * 2011-10-11 2013-07-23 Paramount Pictures Corporation Systems and methods for controlling access to content distributed over a network
US8898742B2 (en) 2011-10-11 2014-11-25 Paramount Pictures Corporation Systems and methods for controlling access to content distributed over a network
US20130179805A1 (en) * 2012-01-10 2013-07-11 Adobe Systems Incorporated Sketch annotation tool
US9247146B2 (en) 2012-05-21 2016-01-26 Lg Electronics Inc. Mobile terminal and control method thereof
US20150149900A1 (en) * 2012-06-29 2015-05-28 Nippon Telegraph And Telephone Corporation Terminal device, annotation method, computer system, and computer program
US9715396B2 (en) * 2012-06-29 2017-07-25 Nippon Telegraph And Telephone Corporation Terminal device, annotation method, computer system, and computer program
US10102183B2 (en) * 2013-06-21 2018-10-16 3Rb Llc System for transferring annotations between documents displayed side by side
US20150149882A1 (en) * 2013-11-26 2015-05-28 Adobe Systems Incorporated Content adaptation based on selected reviewer comment
US9898451B2 (en) * 2013-11-26 2018-02-20 Adobe Systems Incorporated Content adaptation based on selected reviewer comment
US20150242064A1 (en) * 2014-02-21 2015-08-27 Toshiba Tec Kabushiki Kaisha Information display apparatus that displays document page
US20150326925A1 (en) * 2014-05-06 2015-11-12 At&T Intellectual Property I, L.P. Embedding Interactive Objects into a Video Session
US10638194B2 (en) * 2014-05-06 2020-04-28 At&T Intellectual Property I, L.P. Embedding interactive objects into a video session
US20160019195A1 (en) * 2014-05-20 2016-01-21 Jesse Kelly SULTANIK Method and system for posting comments on hosted web pages
US20160232144A1 (en) * 2015-02-06 2016-08-11 Liang Zhou Browser extension allowing web users to draw on live web pages
US10380235B2 (en) * 2015-09-01 2019-08-13 Branchfire, Inc. Method and system for annotation and connection of electronic documents
US20170060829A1 (en) * 2015-09-01 2017-03-02 Branchfire, Inc. Method and system for annotation and connection of electronic documents
US11514234B2 (en) * 2015-09-01 2022-11-29 Branchfire, Inc. Method and system for annotation and connection of electronic documents
US20190361969A1 (en) * 2015-09-01 2019-11-28 Branchfire, Inc. Method and system for annotation and connection of electronic documents
WO2017040652A1 (en) * 2015-09-01 2017-03-09 Branchfire, Inc. Method and system for annotation and connection of electronic documents
US20180352012A1 (en) * 2015-09-25 2018-12-06 International Business Machines Corporation Multiplexed, multimodal conferencing
US10630734B2 (en) 2015-09-25 2020-04-21 International Business Machines Corporation Multiplexed, multimodal conferencing
US20170147537A1 (en) * 2015-11-23 2017-05-25 Canon Kabushiki Kaisha Method, apparatus and system for reproducing a document defined in a page description language
US11074030B2 (en) 2017-06-27 2021-07-27 Salesforce.Com, Inc. Identifying a viewport within a browser window
US10416952B2 (en) * 2017-06-27 2019-09-17 Salesforce.Com, Inc. Identifying a viewport within a browser window
US10628631B1 (en) * 2017-10-31 2020-04-21 Amazon Technologies, Inc. Document editing and feedback
US11030395B2 (en) * 2018-05-30 2021-06-08 Microsoft Technology Licensing, Llc Top-align comments: just-in-time highlights and automatic scrolling
US20190370319A1 (en) * 2018-05-30 2019-12-05 Microsoft Technology Licensing, Llc Top-Align Comments: Just-in-time Highlights and Automatic Scrolling
US11310292B2 (en) * 2020-08-13 2022-04-19 Cisco Technology, Inc. Application aware annotations in online collaborative sessions
US20220237367A1 (en) * 2021-01-25 2022-07-28 Microsoft Technology Licensing, Llc Documentation augmentation using role-based user annotations
US11630946B2 (en) * 2021-01-25 2023-04-18 Microsoft Technology Licensing, Llc Documentation augmentation using role-based user annotations

Also Published As

Publication number Publication date
US20150293892A1 (en) 2015-10-15
US9858252B2 (en) 2018-01-02

Similar Documents

Publication Publication Date Title
US9858252B2 (en) Multiple graphical annotations of documents using overlays
US10713066B2 (en) Generating content objects using an integrated development environment
US9600155B2 (en) Computer implemented methods and apparatus for customizing a data interface in an on-demand service environment
US11327987B2 (en) Configuring service consoles based on service feature templates using a database system
US9823813B2 (en) Apparatus and methods for performing an action on a database record
US20170371876A1 (en) Augmented reality display apparatus and related methods using database record data
US10547583B2 (en) Combining updates of a social network feed
US8732606B2 (en) Computer implemented methods and apparatus for dynamic windowing in user interfaces
US10198484B2 (en) Displaying reduced and detailed visual representations of calendar items based on mouse cursor movement
US10180837B2 (en) Version control and management
US8994777B2 (en) Method and system for web conference recording
US20150312191A1 (en) Methods and systems for managing multiple timelines of network feeds
US11030210B2 (en) Hierarchical rules for displaying user interface pages
US20130097500A1 (en) Method and system for providing positionable dynamic content
US20160283947A1 (en) Sharing knowledge article content via a designated communication channel in an enterprise social networking and customer relationship management (crm) environment
US20110302222A1 (en) System, method and computer program product for creating a child database object using a child database object type identified from a parent database object
US9489660B2 (en) Methods and systems for public collaborative interface for private network groups
US9477369B2 (en) System, method and computer program product for displaying a record as part of a selected grouping of data
US20200097464A1 (en) Content management system implemented using a database structure
US8589740B2 (en) System, method and computer program product for testing an aspect of a user interface determined from a database dedicated to the testing
US9785620B2 (en) Creating linked communications
US9953301B2 (en) Searchable screen sharing sessions
US9395881B2 (en) Methods and systems for navigating display sequence maps
US20140115458A1 (en) System and method for context-sensitive help for touch screen inputs
US10318924B2 (en) User interface date selectors for historical reports

Legal Events

Date Code Title Description
AS Assignment

Owner name: SALESFORCE.COM, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FISCHER, RONALD F.;REEL/FRAME:026317/0914

Effective date: 20110519

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION