Browse Prior Art Database

Method And Apparatus For Document Linking In A Web And Rich Client Environment

IP.com Disclosure Number: IPCOM000190232D
Original Publication Date: 2009-Nov-23
Included in the Prior Art Database: 2009-Nov-23
Document File: 5 page(s) / 84K

Publishing Venue

IBM

Abstract

Rich links are provided in content management systems with web and desktop clients. End users create links to remote content, and then interact with that linked content as if the system stored the content locally.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 41% of the total text.

Page 1 of 5

Method And Apparatus For Document Linking In A Web And Rich Client Environment

This technique preserves high fidelity of user interaction on referenced content. An end user creates a link in a content management system. The user browses a remote repository, and selects a document as the target of the link (hereafter, target document). The user enters the server name to select the document from, or selects a server from a list pre-configured by an administrator (hereafter, target server).

The user browses for the target document and then clicks "Insert Link". The system stores an XML file representing the link and uses the target document's file name + ".qkr" as the file name for the XML file representing the link. Hereafter, a "qkr file" denotes an XML file stored in the system representing a link to the target document. The qkr file contains identifying information about the target document, including an identifier for the target server, unique identifiers (IDs) for the target document and the container of the target document in the target server.

Link creation involves no new APIs from the server containing the link (hereafter source server). Link creation requires the implementation of a browse API by the target server. Atom feeds for document libraries, folders and documents serve as the default implementation, but web services, RESTful services or another remote API serve as alternative protocols for an implementation.

Since the source system stores links as XML documents, any program capable of adding a document adds a link to the source system simply by uploading the qkr file. The source system includes capabilities for publishing a document to a remote system and at the same time replacing the local document with a link to the new remote document. The publish feature replaces the contents of the document published with XML and changes the file extension to "qkr" to convert the document to a link.

When rendering a list of documents in a view to an end user, if the source system encounters a file with the qkr extension, the system annotates the document's icon to indicate the document is a link. A browser plug-in, such as an ActiveX control in Internet Explorer or a plug-in to Firefox, requests a shortcut icon for a particular file type from the operating system. For a qkr file named "MyDoc.odt.qkr", the browser plug-in requests the shortcut icon for ".odt". The user interface removes ".qkr" from all file names before displaying and formats the name as "Link to {0}" where {0} is the file name of the qkr file minus the qkr extension. The system bases the language for the text "Link to" on the active user at the time of viewing the file list. The user interface uses the extension of the file to decide to show a different set of actions on links compared to other documents.

Content management systems commonly...