Browse Prior Art Database

Simplified update process for cloud based documents

IP.com Disclosure Number: IPCOM000234644D
Publication Date: 2014-Jan-24
Document File: 2 page(s) / 49K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes the use of simple user locally-edited files to access and update cloud-based documents and datastores like spreadsheets as an ad hoc data management system. Cloud based document storage and editing typically require complex APIs for authentication and editing. This invention is an add-on for existing solutions which piggybacks on authentication and editing provided by the service's cloud and local portal processes. It is the least intrusive way of simplifying cloud document editing.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Page 01 of 2

Simplified update process for cloud based documents

There exists cloud based document storage and editing services which consists of an online storage service, and a local portal, typically implemented as a folder that is watched by a background daemon on a local computer.

A reference consists of a small text file , with JSON pointing to the URL of the document: {"url": " https://url.to.document.in.could", "resource_id": "document:18CQvSY4GK1JUjaGvnWl5FoWwoTAqxru5pSJFi67G42c"}

The main way to edit the document is to open the document in the web browser by double clicking on the reference in the local portal.

This fires up a web browser, or tab, and cloud's office suite's web interface opens up.

Any modifications is saved to the cloud account belonging to the user .

The other way to edit documents, and to access online contents in general , is to use the RESTful HTTP API provided by the cloud document service.

They consist of HTTP requests, and an XML protocol that more specifically describes the actions required.

For spreadsheets, it provides these actions, among others: deleting, inserting, updating rows, columns and cells.

In addition, users need to authenticate to access the documents using either ClientLogin , OAuth1.0a or OAuth2.0.

Some cloud services provides Java and .NET libraries to ease the process, and wraps the REST API calls for the programmer.

Problems that can be improved is to make this process simpler with the least requirements on the user or programmer:

Reduce the complexity of authenticating the user


Remove the need for programming libraries to access cloud documents


Reduce the complexity of accessing cloud documents


Provide a human readable and writable way to access cloud documents

The core idea is to update the local reference files as normal text files using a markup language like JSON to describe the update.

This would allow documents to be manually updated without going through the cloud document editing

web interface. It can also allow reading.

This would remove the need to programmatically authenticate , because the daemon stores the user 's cloud account authentication information on setup . Every time the daemon detects an update, it connects and authenticates using the user's account login information automatically .

The only security required is user access to the local portal 's folder, which is handled by the OS in the

form of folder access permissions . Only the local user that owns that local portal 's folder can read and

write to files within.

The programming model is simplified because no programming libraries are needed - just text/markup output.

The invention can be applied to a wide variety of cloud storage /document services that may have widely varied ways of achieving the same functionality. For example, it could be applied to source control systems that has structured workitems.

A scenario for creating and adding cells to a spreadsheet called WaterTemperature , with a worksheet for eac...