WO2008071992A2

WO2008071992A2 - Improvements to a communications system

Info

Publication number: WO2008071992A2
Application number: PCT/GB2007/004816
Authority: WO
Inventors: Duncan Hugh Barclay
Original assignee: Individual
Current assignee: Individual
Priority date: 2006-12-15
Filing date: 2007-12-14
Publication date: 2008-06-19
Anticipated expiration: 2009-06-15
Also published as: WO2008071992A3

Abstract

A notification icon on a graphical user interface of a user computer, the user computer being in communication with a remotely located server computer wherein the behaviour of the notification icon is arranged to change in dependence upon events occurring at the remotely located server computer.

Description

Improvements to a Communications System

Field of Invention

This invention relates to an improvement to a communications system. Specifically, the present invention relates to a distributed communications system and associated communications tools and to the storage and management of digital content. In particular, the present invention provides a system and method for the storage and accessing of digital content by a plurality of users.

Background to the Invention

With the advent and proliferation of high speed Internet access ("broadband" access), traditional working practices are changing and there is a move to more flexible working patterns. In Western Europe and the USA there are over 180 million "mobile" workers with 86% of firms having workers that spend at least one day per week outside of the office.

These workers can "telecommute" and communicate with team members in the office via broadband Internet access. As such the "office" may be viewed as an increasingly asynchronous and distributed environment where people are working, whenever and wherever they can.

It is clear that there are significant technological challenges in the scheduling and management of interaction between such workers and that there are challenges in the storage and management of digital content that allows efficient working to take place.

Local area networks and email have evolved as critical enablers of the digital office space.

Within an office or a company, users tend to collaborate internally by grouping files into folders on a shared file server. The structure of the organisational system for such files is dependent on the organisation. For example, files can be arranged by document status, information type etc. It may also be the case that an organisation has no fixed storage policy and different users may store content differently from one another. For example, folder/sub-folder naming schemes may differ from person to person and the actual location chosen to store information (e.g. local hard drive or network drive) may vary.

Within a distributed working environment, most teams communicate via email. Email enables the exchange of project plans, in the form of files and messages, and also the exchange of other information. Once received, emails tend to be stored within a dedicated email application. Attachments to emails may be stored locally or on a shared file server but it is noted that the organisation of such local or network drives is not consistent between users or organisations.

It is further noted that, in both the single organisation and distributed environments identified above, the textual content of emails is often stored in a different location within the computer network than any attachments enclosed with the email.

It is therefore an object of the present invention to provide a communications system (and associated method and tools) to more efficiently structure and organise digital content, to coordinate digital assets and resources and to provide a communications system that allows more efficient communication between contributors.

It is a further object of the present invention to provide a communications system which interacts with a remotely located user to update them of changes to the communication system.

Statements of Invention

According to a first aspect of the present invention there is provided a notification icon on a graphical user interface of a user computer, the user computer being in communication with a remotely located server computer wherein the behaviour of the notification icon is arranged to change in dependence upon events occurring at the remotely located server computer.

The present invention envisages a distributed communications system in which a plurality of users interact via their user terminals/computers with a remotely located server/server computer which may be arranged to store a plurality of content items that each user may access.

In order to keep each user informed of changes to the content held at the server computer the first aspect of the present invention provides a notification icon which may reside on the graphical user interface (GUI) of a user's computer. The notification icon is arranged to provide a communications link between the user computer and the server computer such that as events occur at the remotely located server computer, e.g. the addition of new content or the amendment of existing content, the behaviour of the notification icon is arranged to change.

The present invention provides the user of the system with a convenient means for keeping track of changes occurring to the system and obviates the need for the user to poll the server to check whether updates have occurred.

Preferably, the icon comprises a plurality of different behaviour options (e.g. changing colour, changing shape, changing size etc.), each of which is associated with a different event occurring at the remotely located server computer.

Preferably, the associations between icon behaviour and events at the server computer may be customisable by the user. This provides the user with a powerful tool for determining specific events that may be occurring on the communications system. For example, a user may be waiting for a specific person to upload a file to the remotely located server. In the embodiment where the notification icon according to the present invention may be customisable then the user could set their icon to exhibit certain behaviour as soon as the file is uploaded, e.g. the could set the icon to flash repeatedly.

Conveniently, the icon is arranged to respond to push communications from the serer computer.

Conveniently, the icon may be arranged to be animated.

In the event that the GUI comprises a traditional "window" arrangement, then the icon may be arranged to either always sit on top of the window areas or conveniently, may be arranged to move to the topmost layer upon receiving a push communication. Preferably, the behaviour of the icon is arranged to change dynamically with changes on the remotely located server computer. Conveniently, the icon may be arranged such that a user can interact with it (e.g. by "hovering" a cursor over the icon) to determine further information regarding the vents on the server computer (e.g. upon hovering of the cursor over the icon a dialog box could open summarising the change on the server).

In order to view content stored on the server computer the user computer may be provided with a separate application arranged to organise and display the content items on the GUI. Conveniently, the icon may be arranged such that user interaction with the icon is arranged to launch this associated application.

According to a second aspect of the present invention there is provided a graphical user interface on a user computer, the user computer being in communication with a remotely located server computer wherein the graphical user interface' comprises a notification icon in accordance with the first aspect of the present invention.

The second aspect of the present invention provides a graphical user interface on a user computer, the GUI comprising a notification icon according to the first aspect of the present invention.

It will be appreciated that preferred and/or optional features of the first aspect of the invention may be provided with the second aspect of the invention also, either alone or in appropriate combinations.

In particular, according to the second aspect of the present invention user interaction with the icon in the GUI may conveniently launch a display window area within the GUI which is arranged to display the events that have occurred on the server computer.

The display window area may also conveniently be arranged to display at least some of the content items stored on the server computer. Conveniently, the notification icon and display window area that is arranged to display content items stored on the server computer are part of a common application stored on the user computer.

Conveniently, the display window area is arranged to notify the user of an event on the server computer by associating a notification flag with a new or amended content item that is on display in the window area.

According to a third aspect of the present invention there is provided a server for storing content for access by users of a content storage system, each user communicating with the system via a user computer, the server comprising: input means for receiving content related data from users of the system; a data store for storing content; and output means for outputting a notification signal to users of the system wherein the system is arranged to output a notification signal to users of the system in dependence on changes to the content stored in the data store.

The third aspect of the present invention provides a server computer for storing content that can be accessed by remotely located users via their user computers. The third aspect of the present invention provides a server which stores content in a data store. The server comprises input means for receiving information from users of the system, e.g. user requests to access content in the data store or user-originating uploads of new content, or amendments to current content.

The system provides an output means for outputting a notification signal to users of the system in dependence upon changes to the content stored on the data store, i.e. the system notifies users of events occurring on the server.

Preferably, the notification signal is a push communication.

Conveniently, the content stored in the data store comprises a content item (e.g. a digital document, an email communication, a video file etc) and associated metadata. Furthermore, the meta-data stored in the data store may be arranged to allow the content to be grouped by content category. In a preferred aspect of the invention, users may be associated with content belonging to a particular content category and the notification signal output by the system may be directed towards only those users associated with content categories that have had their content changed.

Preferably, the output means is arranged to output a content signal to users of the system to allow content to be displayed on a graphical user interface of a user's computer.

Preferably, the system further comprises a messaging module for sending messages from the system wherein the messaging module is arranged to tag outgoing messages with meta-data. Conveniently, meta-data can be added by the messaging module into the sender's address field.

The server of the present invention provides a user with the ability to email users and also non-users from within the system environment. All emails outgoing from the communications system of the present invention are tagged with meta-data such that any replies to the original message can be associated with the correct content category (i.e. the correct theme) regardless of whether the email subject heading is correct or has been altered. Emails identified in this way by the system can then be stored in such a manner that they are presented to users of the group within the context of the common interface.

Meta-data/tags applied by the server according to the present invention can, conveniently, be inserted into the email header portion. Such portion of an email is generally invisible to email senders/recipients but may be used to carry information that can be detected by the server. This advantageously allows any email that is sent from a user or non user (if the originating email came from a user of the server) to be automatically grouped within the organisational structure of the server.

It is further noted that any entries made to the server, be they messages that are exchanged between users or other assets that are uploaded, are also tagged with meta-data and are conveniently presented in chronological order within the common user interface. According to a fourth aspect of the present invention there is provided a distributed content storage system comprising a server according to the third aspect of the present invention and a plurality of user computers in communication with the server, each user computer comprising a notification icon according to the first aspect of the present invention and a graphical user interface according to the second aspect of the present invention.

The fourth aspect of the present invention provides a distributed content storage system for facilitating the management and storage of information/messages from a number of users, the system comprising a server according to the third aspect of the present invention and a plurality of user computers having graphical user interfaces and notification icons in accordance with the second and first aspects of the present invention respectively.

Conveniently, the distributed system comprises a server to manage interaction between users of the system, a data management system (DMS) for managing digital assets and other information stored in a data store and a user access management system (UAMS) for managing user access to data stored within the data store.

The UAMS facilitates user-to-user interaction within the confines of the system. Users are allowed to create user groupings and to invite users to join specific groups (virtual private spaces). The UAMS subsequently allows the members of a group to communicate with one another.

The data management system provides access to a relational database for the storage of content comprising communications, assets and other digital information exchanged between users of the system. Data within the system is tagged by the use of meta-data to facilitate easy search and retrieval of the information contained therein.

Content within the system according to the present invention is grouped thematically ("content category"). All digital content, regardless of its type or format, is organised under a subject heading and is presented to the user via a common interface. Content exchanged between users of the system (be it message-type content, such as email of instant messages (IM), or file assets such as Word/spreadsheet/audio- visual files) is stored within the DMS such that a central copy of the content is maintained.

The system allows a variety of communications methods to be used between users, for example, email, instant messaging, audio and/or visual messages, forums, blogs, whiteboards. Digital content, in the form of assets, may also be uploaded to the system such that it can be accessed by any member of a group that has access to a particular topic.

The system according to the present invention allows a specific user to be a member of multiple groups. A user of the system may therefore participate in a number of distinctly different groupings relating to different themes/subjects. Members of a group may invite additional or new users into the group.

According to a fifth aspect of the present invention there is provided a method of communicating with a remotely located server computer comprising: receiving a communication from the server computer and modifying the behaviour of a notification icon on a graphical user interface of a user computer, wherein the behaviour of the notification icon is arranged to change in dependence upon events occurring at the remotely located server computer.

According to a sixth aspect of the present invention there is provided a carrier medium for carrying a computer readable code for controlling a processor or computer to carry out the method of the fifth aspect of the invention.

According to the sixth aspect of the present invention, users are able to download a software application embodying the various aspects of the present invention to their local PC, PDA or other device. The downloaded application enables user interaction with the communication system and allows a user to update content to the system, to invite other users to join a specific group and to manage all the content that that user has access to.

In one embodiment, the user interface is represented by an icon, and preferably, a ball-like icon that modifies its behaviour in dependence upon tasks, activities and communications that are occurring within the distributed environment. As such, the user interface icon provides a portal into the distributed environment of the present invention.

The core concept of the present invention (also referred to herein as Think Ball¹) is a set of communication and data related tools that are themed and encapsulated in a ball allowing the user to create private or public networks by shared access to the data stored on that ball. In this sense the Think Ball functions as a high level operating system contained in a unique visual interface: A ball.

Think Ball is designed to be compatible with all other mainstream operating systems and platforms including PDA and mobile phone.

The ThinkBall web platform allows users to access their Thinkball via the Ball server. As all entries, web-links, digital assets, and final documents are saved to the Ball server and communications take place through the Ball server, a copy may be saved and accessed remotely via the web. If a user subscribes to the ThinkBall web platform, they will have the ability to access their Thinkball at anytime with full functionality. Upon login back in from their desktop application, the server will automatically update their Thinkball ldeaspaces with added entries, web-links, digital assets, communications and final documents that had been added earlier.

Users can access all high level components of their Thinkball and save any changes, updates and communications back to the Ball Server. These may be retrieved and accessed either by another remote location, or from their Thinkball desktop application.

Brief Description of the Drawings

In order that the invention may be more readily understood, reference will now be made, by way of example, to the accompanying drawings in which:

Figures 1a, 1b, 2 to 5 show the general structure of the system according to an embodiment of the present invention;

Figures 6 to 15 show the process of registering and using the system according to an embodiment of the present invention; Figures 16 to 18 show the processes and interfaces used during the log in process according to an embodiment of the present invention;

Figures 19 to 37 are screenshots of various interface screens according to an embodiment of the present invention; Figures 38 to 50 are flow charts relating to the screenshots of Figures 19 to 37;

Figures 51 to 62 are further screenshots of interface screens according to an embodiment of the present invention;

Figures 63 to 79 are further screenshots and flow charts relating to information managers used by users of the present invention to view, edit and manipulate digital content according to an embodiment of the present invention;

Figures 80 to 86 are representations of ball like icons that may be used in accordance with an embodiment of the present invention;

Figure 87 is an example of an email header section in accordance with an embodiment of the present invention.

Description of the Invention

In the context of the present invention, the following shorthand terms are used to refer to various aspects of the system: (i) "Thinkball" - the system according to the present invention is embodied in one embodiment within a software application that has an icon that is ball like in shape. Interaction with this icon opens a user interface that a user may then use to interact with the communications system. In light of the ball like nature of the icon the term "Thinkball" is used as a shorthand notation to refer to the icon. Aspects of the system, such as the central file server may also be referred to as the "Thinkball server" and the system according to the present invention may be referred to as the Thinkball system. It is noted however, that the icon need not be ball fike and that therefore the term "Thinkball" should not be viewed as limiting the embodiments of the invention in any way; (ii) "Ideaspace" - as is described in more detail below, the Thinkball communications system groups content along thematic lines. Each content area (i.e. each subject or theme) is referred to as an "Ideaspace". Again this term is used as a convenient shorthand notation and is not viewed as a limiting term in any way.

Turning to Figure 1a, a general system architecture is shown describing the communications system (the "Thinkball" system) according to the present invention. The system, generally referred to by the numeral 1 , comprises a main server 3 which comprises a communications services system 5, a data management services system (DMS) 7 and a user access management services system (UAMS) 9. Systems 5, 7 and 9 are all in communication with a database server 10 which comprises N separate data stores (1Oa₁ 1Ob₁ 10c, ....1On).

The main server 3 also comprises a web application server 11 and a user session manager 13 (which is in communication with the communications services system 5, a data management services system (DMS) 7 and the user access management services system (UAMS) 9) to allow the system to interact with remote users via any appropriate communications channel or network 14 (e.g. LAN, Internet etc).

Each user of the system 1 has a user terminal (not shown in Figure 1a) which can interact with the main server 3 via the appropriate communications channel or network 14.

Each user terminal comprises a software application 15 that allows user interaction with the Thinkball system 1.

Communications, assets (such as Word, Excel, Audio, Video files) and other digital content are stored within the data store 10 and are managed by the DMS 7. The system provides a common interface (described below) which each user may view and interact with in order to access and upload digital content, messages and assets.

Two users who are part of the same group and who are contributing to the same content subject area (or Ideaspace) may view the same system assets and may communicate with one another within the Thinkball environment. It is therefore noted that the system according to the present invention effectively allows user-to-user links to be created via the server 3.

Figure 1 b shows the component parts of the software application 15 in more detail. Figure 1b shows the main server 3 connected to the software application 15 via the internet 14. The software application 15 (the Thinkball) comprises two main parts, an animation component 17 and a user interface component 19.

As noted above, the user interface is represented by an icon, and preferably, a ball- like icon that modifies its behaviour in dependence upon tasks, activities and communications that are occurring within the distributed environment. These behaviour changes are enabled by the animation component 17 of the application 15 which comprises a notification module 17a that details the various notifications that the application 15 can convey (e.g. an update to an Ideaspace, a new user joining the system); a behaviour module 17b that defines the various different icon behaviours that the application 15 may exhibit depending on the type of notification to be conveyed (e.g. icon to glow for new user, icon to increase in size for new Ideaspace etc).; and an animated graphics module 17c that provides a range of icon animations to be used depending on the behaviour to be expressed.

The application 15 also comprises a user interface component 19 that enables the user to view and use the various video services 19a, audio services 19b and text and graphic services 19c that the system 1 provides. It is noted that the user interface 19 is a Flash/DHTML interface that allows a user to interact with the system 1 regardless of the actual video/audio software applications that may be loaded onto their local PC.

Figure 2 shows a user terminal 30 which is running the software application 15 described above. It can be seen that the user terminal 30 comprises a graphical user interface (GUI) 32 which is displaying a notification icon 34 and a window area 36 in accordance with an embodiment of the present invention.

The user terminal is in communication (via the Internet 14) with the remotely located server computer 3 described above.

The window area is displaying a number of entries 38 which have been grouped by subject.

The user of the user terminal 30 and users of other similar user terminals (not shown in Figure 2) may send new content 40 to the remotely located server computer 3 for storage within the data store 10. In Figure 2, the addition of such new content is associated with a first event at the server computer 3, Event 1.

The user of the user terminal 30 and users of other similar user terminals may also amend or update content 42 that is already stored within the data store 10. In Figure 2, the amendment of content is associated with a second event at the server computer 3, Event 2.

It is noted that there may be a plurality of different "events" that may occur within the context of the Thinkball system of the present invention. For example, the receipt of emails may be associated with an event, the creation of new content subject areas may also be associated with an event.

In accordance with an embodiment of the present invention an event occurring at the server computer 3 results in a change in the behaviour of the icon 34. Where the event results in the addition or an update to an entry 38 in the window area 36, the entry in question may be displayed in a different font type (e.g. entry 38a is shown in bold font). A symbol 44 may also be inserted next to the entry to indicate to the user of user terminal 30 that a change has occurred to the displayed content.

In accordance with an embodiment of the present invention, changes to the content held on the server computer 3 are communicated to the user terminal 30 by means of a push communication 46.

It is therefore noted that the behaviour of the icon 34 and the changes to the entries 38 happens dynamically in real-time and the user of user terminal 30 is not required to constantly poll the server computer 3 for updates.

This dynamic notification feature clearly improves the user experience compared to other prior art content management systems.

Figure 3 shows the notification icon 34 and examples of different behaviour options in dependence on different events.

As noted above, different events such as new content, updated content, the creation of a new content subject area, an email, the joining of new users may be signalled to the user of user terminal 30 by changes in the behaviour of the icon 34.

Where there are no new events occurring with respect to the server computer 3 the icon 34 has a default appearance 50. In the example shown in Figures 2 and 3 the icon 34 is ball-like in shape and may, for example, be a solid coloured ball that sits on the GUI 32.

A first event, e.g. new email, may result in the ball icon 34 increasing in size. A second event, e.g. a new content subject area, may result in the ball rotating. A third event, e.g. a new entry in an established content subject area, may result in the ball vibrating and a fourth event, e.g. the joining of a new user in response to an invitation to join the Thinkball system, may result in the ball changing colour.

It is noted that the ability of the present embodiment to signal different events to the user of user terminal 30 is limited only by the different behaviours of the icon 34 that may be programmed into the software application 15.

Advantageously, the user of user terminal 30 may be able to customise the behaviour of the icon 34 to specific events. For example, if the user of user terminal 30 has sent an invitation to an individual to join the Thinkball system and is waiting for them to join so that he can start a new content subject area, he may customise the system such that the acceptance of the individual of the invitation to join the system causes the behaviour of the icon 34 to change in a particular way.

Since the present invention dynamically updates the icon 34 with events occurring on the server computer 3 then the user of user terminal 30 will be immediately and automatically notified of the event in question.

Figures 4 and 5 outline the major user interactions that may take place between the system 1 according to the present invention and the associated software application 15 running on a user's terminal.

Turning to Figure 4, the server 3 of Figure 1 is shown along with a plurality of users 60 (users 60a-60j). Each user is shown is shown undertaking one of a variety of actions that the system supports.

It is noted, for example, that user 60a is downloading the Thinkball software from the server 3. In other words, user 60a is a new user to the system and is in the process of downloading a copy of the software application 15 to his terminal that will then allow him to use the Thinkball system. It is noted that the registration and sign up process is described in more detail below.

User 60k is working offline. Within the context of the present invention it is possible to work in a stand-alone mode such that there is no real time communication with the system 1. For example, user 60k may be in the process of recording a video message or writing an email. He may also be working on a word-processor based report which is to be sent to the system at a later time. These example activities do not require the user 60k to be in communication with the system 1 and a user may therefore choose whether to work whilst online or to work offline. This feature of the system also allows the user to continue working during periods when Internet access is unavailable.

Once user 60k has completed his offline work he will need to connect to the system 1 and to synchronise all the work he has prepared with the system 1. The software application 15 on his local PC will preferably have already collected the necessary meta-data to allow the content to be posted directly to the system. Alternatively, the system may prompt the user 60k to add meta-data so that the content can be classified in the correct manner to be entered onto the system. The process of adding content (assets) to the system is described in more detail below.

It is noted that user 6Of is in the process of synchronising with the system 1. This may include the uploading of content that has been prepared offline (in a similar manner to user 60k) or, alternatively, the downloading of up-to-date system information and content following a period of offline.

Once a user is registered with the ThinkBall system 1 they may search a directory of other users and invite any of those users to join and participate in a particular subject (an Ideaspace). A user may add text entries, digital assets (e.g. Word, Excel and other files), record communications and emails to an Ideaspace. They may also add remote entries including SMS messages and voice messages as audio files.

As noted above, entries and other updates made by one user are synchronised with all participants of an Ideaspace by the Thinkball system 1. The user hosted software application 15 will generally comprise a web based platform that allows a user to interact with the Thinkball system from any location. As noted above the software application 15 also comprises a ball like icon 34 which sits, minimised, on a user's desktop 30 when they are not logged into the Thinkball server 3.

Once a user is connected to the Internet the icon 34 may be capable of providing details of activity on the system to the user without the need for the web-based platform application to be launched. For example, as described in relation to Figure 4 above, the icon may change colour or shape if updates to ldeaspaces that the user is a member of occur.

As also noted above, the icon may be customisable by the user. For example, different "skins" may be downloaded from the server 3 to change and personalise the appearance of the icon.

Figure 5 shows an alternative view of the system architecture to Figure 4. In Figure 5 a single user only is shown. The various potential activities and actions the user may take are shown branching out from the IdeasServer 3. It is noted that the IdeasServer is linked to further system 1 components, the ThinkBall Server 3 and the communication services system 5, the data management services system 7 and the user access management services 9.

User Registration and Interaction

Figures 6 to 15 show how a new user, Bob, registers with the system 1 according to the present invention and how he interacts with the system to create and participate in IdeaSpaces and how he interacts with a new user, Mary.

Figure 6 shows the first stage in the process of registering and using the system according to the present invention. In Figure 6, a new user, Bob, who wishes to sign up to the Thinkball system downloads the software he needs (the software application 15). Bob may conveniently log onto a web page that contains a link to download the software application. During the download process started in Figure 6, Bob registers his software with the

Thinkball server 3 (see Figures 7 and 8). During this registration process Bob's email will be taken as this provides a unique piece of identifying information. At this stage, the main server 3 creates a temporary storage area [on the DMS] for storing any assets or content that Bob may wish to load onto the system. These assets/content will be visible to other registered users of the system.

In Figure 9, the download process has been completed. Bob's PC is now in communication with the server 3. The software application 15 runs in the background on Bob's PC and is identifiable via an icon 34, e.g. the ball like icon described above.

Once the software application 15 has been downloaded, Bob may use the system 1 according to the present invention to start up a new subject thread/discussion/workspace and to discuss this with other users of the system. In the course of setting up his new content area (Ideaspace) Bob may invite other users to join his Ideaspace as well as uploading content such as multimedia assets, weblinks and other documents for the idea.

It is noted that Bob may invite other users of the system to join his Ideaspace or he may invite non-users. In the latter case, the invitee will be invited to download and register the software application 15 in the same manner as described for Bob.

In Figure 10 the Ideaspace has been formalised within the environment of the Thinkball system 1 and Bob's software application 15 now allows him to access a dedicate Ideaspace area 60 which comprises a plurality of entries (e.g. text, email, file, chat etc entries). It is noted that each entry may be associated with: one or more other users (Thinkers in the terminology of Figure 10); one or more attachments (e.g. digital files); and one or more weblinks. Each entry may also be associate with a comment.

As noted above, Bob may invite anyone to contribute to his Ideaspace. In Figure 11 Bob has decided to invite Mary to contribute. Mary is not currently a registered user of the system 1 but her email address is known to Bob. In order to invite Mary to join, Bob sends a request to the system 1 to invite Mary to join in. As part of this request Bob sends Mary's email (maryrose@hotbot.com) to the system 1. Once the server 3 receives Bob's request it checks whether Mary is already a user of the system 1. If Mary is a registered user already then an invitation to join in Bob's workspace can be sent to Mary within the environment of the system.

If Mary is not currently a registered user of the system 1 then an email 70 will be dispatched to her from the system 1 including an invitation to download the software application 15 and an invitation to join into Bob's workspace. This process is illustrated in Figure 12.

If Mary accepts the invitation sent by the system 1 in Figure 11 , then she may download, install and register the software application 15 in the same manner as described for Bob above. As shown in Figure 13, however, the system will additionally send a message 72 to Bob once Mary's registration is complete to let him know that she has downloaded the required software and is now a user.

Once Mary has registered with the system her local software application is updated with details of Bob's ldeaspace 60 (or given access to the Ideaspace). She may then feed her comments 74 back to the server 3. Additionally, she may upload any assets 74 that are relevant. Once the system has been updated Bob is informed about the changes and he free to view the new information within his Ideaspace. This process is shown in Figure 14.

Figure 15 illustrates how Bob's Ideaspace can be developed further.

Bob and May may continue to communicate and share contributions and develop the Ideaspace 60 via the software application 15 on their PCs. They may also create and develop further ldeaspaces 76 for different ideas and invite different groups of contacts 78, 80 to participate and contribute to the idea process.

Any invitees who are not member of the system will go through the same registration process as described above.

The Thinkball environment allows ideas to develop within a collaborative environment. One idea can be passed to many contacts and conversely many contacts can contribute to an idea or ideas. It is noted that users do not need to be online to share ideas or contribute to them. Instead, the server 3 according to the present invention keeps a record of updates whenever a user activates their desktop software application 15.

System Components - Overview

As noted above, the software application 15 will run minimised on a user's PC until such time as they wish to activate the software application. When the user activates the Thinkball software, they may interact with it either by either viewing, editing, amending or collaborating in an ldeaspace or alternatively they may manage their Thinkball environment, e.g. by adding contacts, creating a new ldeaspace etc.

Activating the software application 15 therefore allows a user access to the following components:

1- ldeaspace Interface - An ldeaspace allows individuals or teams of users to participate in online "discussion threads". The ldeaspace is a multi-media web-log platform (entries supported by comments) which contains folders for different elements belonging to an idea. These include: web-links, assets, production, contacts of ldeaspace contributors, and tools for communication and print. The ldeaspace contains a list of entries in chronological order and will interact with the control panel and information managers described below. User access to ldeaspaces will be via the ldeaspace interface;

2- Control Panel. A user may not wish to contribute to an ldeaspace but instead may wish to access various management features relating to their user account.

A control panel may be provided to give the user such management access and it is expected that the control panel may further provide access to one or more of the following information managers: i) Ideas Manager - enables users to log in, view, sort, create and delete ldeaspaces as well as notifications about ldeaspaces.

H) Global Contacts - enables users to search a registered User Directory, edit contacts, add contacts to ldeaspaces, delete a contact from an ldeaspace and filter contacts. iii) Assets Library Manager -The assets library manager enables users to view, structure, add assets to ldeaspaces and create new ldeaspaces from digital assets. iv) Web-Link Store Manager - Enables users to view, structure, and launch idea related web-links. v) Online Communications Manager - The communications manager enables users to view, structure and search for multimedia entries of Ideaspaces. Users can list all video entries, chat log entries, audio entries, email entries and whiteboard sketches across all Ideaspaces. vi) Production Manager - Enables users to store final documents resulting from an ldeaspace in a Production folder, along with its associated meta-data. Users may also view, edit, and delete meta-data in this folder. The Production Manager enables users to publish to export final compressed outputs to a variety of file formats and destinations. vii) Preferences Manager - Enables users to customise the application according to personal preferences.

It is noted that the user will need to be online to access up to date information from the system 1. A user may work offline however and the system provides a user with the option of downloading a directory of users to their local user terminal to allow off line working.

The above components and functionality are represented by Figures 16 and 17.

Figure 16 shows a representation of a Control Panel (a "Thinkball" manager) having various control buttons providing the following functionality:

• Access Information Managers - these buttons (84, 86, 88, 90, 92, 94) enable users to access the following managers: Global Contacts ("Thinkers) 84, Attachments library 86, Web-Links Store 88, Entries 90, Settings 92 and Directory 94.

• Create New ldeaspace 96- this enables users to create a new ldeaspace. Existing Ideaspaces may also be accessed via button 98.

• Help Menu 100 - this allows users to access a system Help menu.

• Quit Application 102

Figure 17 shows a diagram of the top level menu that the software application 15 presents to the user 11 during use. It is noted that the user enters the menu via a general ideas manager 104 and various menu options 106 which allow the user to access an ldeaspace interface and various information managers.

Figure 18 is a flow chart showing an overview of how a user interacts with the system.

ldeaspace Interface

The ldeaspace interface allows individuals or teams of users to participate in online "discussions threads" about ideas. Each ldeaspace will contain folders for final outputs, web-links, contributors, and assets associated with the ldeaspace. A user can select a group of users to participate in the ldeaspace and subsequently they may submit entries to the ldeaspace. These entries may be text, graphics, sounds, file recordings of interactive white board sessions or online chats. Entries may be submitted locally into the ldeaspace or via mobile communications.

Content submitted to the Thinkball system is stored within the database management system 7. It is noted that the system is arranged such that content is visible to all users within the context of the system. For example, if a first user uploads a video file the system is arranged to convert the video file format into a version that can be played within the confines of the user common interface regardless of the particular software that a viewing user may have on their PC.

A screenshot of an example of the ldeaspace Interface is shown in Figure 19. The screenshot shown in Figure 19 comprises a number of different window sections which either directly access the features described below or provide the means for a user to access the features described below.

The ldeaspace interface provides a user with the following options/functions: • Create ldeaspace - A users may create a new ldeaspace, an entry, an asset, a web-link, or independently.

• Invite contacts to the ldeaspace 120 - A user may select other users to participate in a ldeaspace either from the global contacts list or by creating a new contact (entering the name and e-mail address of the contact). Contacts are notified via e-mail that they have been invited to the ldeaspace. • Create/Edit ldeaspace meta-data - ldeaspaces have meta-data associated with them that is entered when users create a new ldeaspace. ldeaspace meta-data can be modified at anytime by the ldeaspace owner.

• Create/Edit entry 122- Entries may be submitted to the ldeaspace by contributors. Only the entry contributor may edit it but editing may occur at any time. As shown in Figures 19 the user may create a wide variety of different entry types (e.g. text, video entry, email entry etc.)

• Receive remote entry to ldeaspace - Entries may be submitted to the ldeaspace via remote mechanisms such as sending the entry via an e-mail. • Synchronize ldeaspace - In order to receive and update entries from other participants in an Ideapsace, users must synchronise their ldeaspace with the Ball server.

• Create comment - Contributors can submit comments to an entry. Comments cannot be edited. • Communicate with a contact in ldeaspace - Contributors can participate in an VOIP telephone conversation, video conference, whiteboard session, realtime online chat, record it and attach it as a digital asset to an entry in the ldeaspace.

• Forward entry to an e-mail - Users can forward entries to the e-mail address of other ldeaspace contacts or to individuals not in the ldeaspace by typing an e-mail manually.

• Flag entry - entries within a ldeaspace may be flagged using icons (configured in Idea Settings)

• Exit ldeaspace - Contributors and subscribers will be able to exit the ldeaspace and return to the ldeaspace manager where they will be able to select another ldeaspace.

• Close/Reopen ldeaspace - Owners can close a ldeaspace. When a ldeaspace is closed the status of the ldeaspace changes to closed but may be reopened again by the ldeaspace owner. • ldeaspace Assets folder - Users may add, edit, protect, delete and preview assets

• ldeaspace Web-links folder - Users may add edit, delete, and browse web- link

• ldeaspace contacts folder - Users may add, delete and communicate with contacts • Online Communications Manager - User may participate in a VOIP₁ video conferencing, email, Real-time chat, or interactive white board session with another contributor.

• Sort/Scroll ldeaspace entries - Users may scroll through all ldeaspace entries which can also be sorted - by contributor, category, date, title and users.

It is noted that each new ldeaspace will comprise various pieces of information (meta-data) that will either be requested of the user or automatically assigned from the user's system profile. Specifically, an ldeaspace will comprise the following types of information:

• Title of ldeaspace

• Type of ldeaspace [project, brainstorm, initiative, research, cost saving etc.] - this information may be administered via a settings option with the system

• Description of ldeaspace

• Folder Label [Colour + Text] this information may be administered via a settings option with the system

• Goal • Keywords

• Owner - this information can be automatically determined by the system via a user's system profile.

• Date opened - this information may be automatically assigned when the ldeaspace is created • Ideaspace-ID - this identification number is allocated by the system

• Deadline

• Status - [Open/close]

• Invite Contacts

• Source

It is further noted that an ideaspace will be composed of multiple entries and each ldeaspace entry will be characterised by the following meta-data:

• Title of entry. This information is provided by the user. • Description. This information is provided by the user. • Date - each entry is dated. This information is entered automatically by the system.

• Contributor - the identity of the contributing author is entered automatically by the system. • Time - each entry is time stamped. This information is entered automatically by the system.

• Digital Assets - an entry may be associated with one or more digital assets (files). The entry is provided with links to these assets as the entry is created and the assets uploaded. • Web-links - an entry may be associated with one or more weblinks. The entry is provided with links as it is created.

• Flag [icon + text] - defined in settings

• Comments - each entry may be linked with comments from other users. As detailed below, each comment also comprises meta-data. • ldeaspace - the identification number of the ideaspace to which the entry is associated is included automatically within the entry meta-data.

• Entry- the entry is assigned a unique ID number by the system.

As noted above, users may enter comments against entries on the Thinkball system. Each comment is accessed from an Ideaspace entry via an appropriate link. Each comment is associated with the following meta-data:

• Description

• Date - each comment is dated. This information is entered automatically by the system. • Entry- each entry is provided with an ID number by the system and the entry

ID system is entered as part of the meta-data for the comment

• Comment- the comment itself is provided with an ID number by the system.

• Contributor - the originating user for each comment is recorded by the system

The current Ideaspace is indicated by a title bar 124 across the top of the screen.

A list 126 of all entries made to the current Ideaspace is located below the title bar and to the left hand side of the screen. This list of entries comprises a list of entry titles. It is noted that these entries are in chronological order. In Figure 19, Ideaspace entry 2 has been selected. To the right of the list of ldeaspace titles and in the centre of the screen is an entry window 128 which comprises the entry itself. The entry may comprise text entries, video entries, audio entries, chatroom messages or any other available messaging or file type. In the current example, a text entry is visible.

The entry window comprises a toolbar that allows a user of the system to make a new entry. A range of entry types 122 is available and there are icons representing each type of entry that is available to the user, specifically text entry, email entry, chatroom/blog entry, file entry, audio entry or video entry.

In the current example, the text entry icon has been selected and the user has entered text that is now associated with the title entry number 27 in the title list to the left of the screen.

In the example of Figure 19, ldeaspace entry 2 is highlighted and below the window comprising the ldeaspace entry list is a series of three tabs (attachments 130, weblinks 132 and contacts 134) that control information that may be presented in a window that runs across the bottom of the screen (not shown in Figure 19).

Figure 19 shows a welcome screen that a user is presented with on creation of a new ideaspace 60.

Figures 20 and 21 show alternative views to Figure 19 in which content has been added to the Ideaspace.

Turning first to Figure 20, it can be seen that the first entry in the list 126 has been selected. Once selected_^ the content associated with this first entry 136 appears in the entry window 128. To the right of the entry window is a comments window 138. This area is for users of the system to add comments that relate to the highlighted entry. For example, if text entry 136 related to a meeting then the comments could be from other users indicating that their intention to attend the meeting or alternatively notifying of a conflict in their schedule. In Figure 20, it can be seen that there is one entry within each of the comments 134, attachments and weblinks 132 tabs, this case, the attachments tab is highlighted and a description of the attachment is shown in window 140.

It is noted that in Figure 20, there are three contacts associated with ldeaspace 2 - see Thinker tab 120. In Figure 21 , the Thinker tab has been highlighted and details of the three contacts associated with this ldeaspace are visible in window 142. The status (online or offline) of each contact is indicated next to each contact and the contact's details and any other notes are available in window 140.

Figures 22 to 29 show examples of the different entry types available to the user. If the user is creating a new entry and has selected, for example, the email icon then an email application will be launched (see Figure 23) and the user will be able to compose and send an email in the usual way.

Once the email has been sent a copy of the email will be recorded in the ldeaspace as a numbered entry in the title list. Any user who selects this entry in the future will be presented with a copy of the email that was sent.

It is noted that if the email comprises attachments then these may be added as attachments associated with the ldeaspace entry.

As well as attachments, each entry may be also associated with weblinks or contacts.

Specifically Figure 22 to 29 show:

• a text entry screen - Figure 22. The user has selected text entry button 144 and window 128 is presenting a text entry form to the user.

• an email entry screen - Figure 23. The user has selected email entry button 146 and window 128 is presenting an email entry form to the user. It is noted that the user may select between existing users 148 and general entry 150 of email addresses.

• A file entry screen - Figure 24. The user has selected file entry button 152 and window 128 is presenting a file entry form to the user. • A chat entry screen - Figure 25. The user has selected chat entry button 154 and window 128 is presenting a chat entry form to the user. It is noted that Thinkers 1 , 2 and 3 are already in the chat room.

• a sketchpad entry screen - Figure 26. The user has selected sketchpad entry button 156 and window 128 is presenting a sketchpad to the user.

• an audio file entry screen - Figure 27. The user has selected audio entry button 158 and window 128 is presenting an audio entry form to the user.

• a video entry screen - Figure 28. The user has selected video entry button 160 and window 128 is presenting a video entry form to the user; and, • a comment entry screen - Figure 29. The user has selected comment tab 134 and window 140 is presenting a comment entry form to the user.

Figures 30 to 37 show how the entries made in Figures 22 to 29 appear on screen once they are completed and posted to the system.

Figures 38 to 50 are flow charts detailing various processes associated with the screenshots shown in Figures 19 to 37.

The Assets, Weblinks and Contacts tabs on the ldeaspace interface have been briefly described above and are now described in more detail:

1 ) Web-links Folder (see Figures 19 and 51 )- The ldeaspace web-links folder centralises all web-links added to the ldeaspace either directly (through explicit user action) or indirectly via an entry made within the ldeaspace. This folder allows references, such as recommended links to be made available to invited users and described using searchable meta-data. The weblinks are associated with a number of functions and attributes: a) Functions i) Add a web-link to a ldeaspace folder - Web-links can be added to an ldeaspace folder directly by cutting and pasting the web-link directly to the web-link folder. Web-links may also be added to the ldeaspace folder indirectly as users include web-links in entries. All web-links added to an entry (e.g. entry 136) are automatically included in the ldeaspace web-links folder (see Figure 51). ii) Create/Edit Web-link Meta-data - Users can create or edit metadata by which to classify and identify web-links. Meta-data may be created or edited for web-links at anytime (see Figure 52 where the "add weblink" button 170 has been selected and Figure 53 where the "edit weblink" button 172 has been selected. Meta-data appears in window area 174). iii) Delete a Web-link - When web-links are deleted the user will first be asked to confirm that they wish to delete the web-link and then the web-link will be removed from the system (see Figure 54). iv) Browse a Web-link - Users can browse uploaded web-links. Web pages display in a new browser window (see Figure 55). b) Attributes. Each web-link has the following meta-data attached: i) Title of Web-link ii) Web-link Address [full hyperlink] iii) Description of Web-link iv) Date stored [Auto] v) Category [Marketing, Competitors, Product] - defined in the admin vi) Ideaspace-ID vii) Entry-ID

2) ldeaspace Attachments Folder (see Figure 56) - The ldeaspace attachments folder allows a user or groups of users to store digital assets related to an ldeaspace. Digital assets that can be stored in the asset folder include sound, video, animation, text photos, and graphics. It is important to note that the "ThinkBall" will support collaboration via realtime chat, and interactive concept maps, and these online conversations may also be recorded and stored in the folder as an entry in the ldeaspace. The Assets folder is associated with a number of functions and attributes: a) Functions i) Add an Attachment - Users may add an asset directly to the ldeaspace assets folder via an entry. Users should be able to add multiple assets at one time. See Figure 56 in which the "attachments" tab 130 has been selected and the "add new attachment" button 176 has been highlighted. ii) Create/Edit Attachments Meta-Data - Users may add and edit meta-data such as creator, title, type, created date, date last modified. Users should be able to add metadata keywords to multiple assets at one time (see Figure 57 in which "edit attachment" button 178 has been selected. Also note preview window 180 which displays a thumb nail view preview of any attached content). iii) Export/Update Attachments - Users may export asset outside of the ThinkBall and Launch Attachments in its associated application to make updates. iv) Launch Attachments - Users may selected an open attachments. See Figure 58 in which the attachment has opened in a new window 182. v) Delete Digital Attachments - Users may delete asset from the system or just delete it from the ldeaspace (see Figure 59). vi) Attach asset to ldeaspace - Users may attach assets to an ldeaspace. vii) Create an ldeaspace from an asset - Users may create a new ldeaspace from an asset. viii) Send Asset to Production Folder - From the Assets Folder, a user may select an asset and send it to the Production folder for this ldeaspace. b) Attributes. Each Digital Asset has the following meta-data attached: i) Title [Full file name] ii) Description iii) Date stored [Auto] iv) Owner [Auto] v) Type [Photo, Text, Sound, Video, Graphic] vi) Keywords vii) Ideaspace-ID viii) Entry-ID

3) ldeaspace Contacts Folder (see Figure 60 - Note: that Contacts are also referred to as Thinkers in the Figures and the terms Contacts and Thinkers are regarded as interchangeable) - The ldeaspace Contacts Folder displays all of the contributors invited to an ldeaspace. The Contacts folder is associated with a number of functions and attributes: a) Functions i) Add contacts to an ldeaspace - A user may select a contact by selecting the "invite new thinker" button 190 and then by either selecting from other users who are part of the Thinkball system 1 (see list 192 in Figure 60) or by entering the email address 194 of contacts who are yet to join the system 1. Once the invite is approved, a contact becomes a participant in the ldeaspace, and their name is displayed in the ldeaspace Contacts Folder 142 (see Figure 56). Figure 61 shows confirmation of the invites that have been sent. ii) Communicate with a contact - Once a contact has accepted an invite to join an Ideaspace, other participants may contact them from the Ideaspace Contacts Folder via the Online Communications. iii) Delete a contact from an Ideaspace - Only the administrator of an Ideaspace has the ability to delete a participant from the Ideaspace Contacts Folder. Right click and select remove from Ideaspace. This ultimately makes the Ideaspace unavailable to that user. (However, they remain as a contact in the user's list of Global Contacts) (see Figure 57). iv) Display Online Users - Contacts Folder displays all contacts that are in ldeaspaces and highlights those that are online. Contacts/Thinker details may also be editable. v) Send Invite for ThinkBall - When users invite contacts to their ldeaspaces, an invite is generated by the Ball server. If that contact does not have the ThinkBall application, the server generates an email inviting them to download the software and register it with the Ball server (see Figure 62). vi) Search ThinkBall Directory - Users may search the ThinkBall Directory held on the Ball server for other ThinkBall users. b) Attributes. A Contact can input the following meta-data about themselves: i) First name ii) Last name iii) Title (Ms. Mrs. Miss. Mr. Dr.) iv) Team [Product, Marketing, etc.] - configured in settings or the global contacts manager v) Company vi) Job title vii) Email at work viii) Email at home ix) Daytime telephone x) Mobile telephone xi) IM address(s) xii) Physical address xiii) Type of contact (type of company, external contact, personal contact) xiv) Password (only available to the contact) xv) User name (available to all) xvi) Photo

As noted above in relation to Figure 17 various menu options on a user's Thinkball are presented to the user as they enter the manu system. The ldeaspace interface has in part been described above and the various information managers will now be described in detail. It is noted that Figure 63 represents the various interaction and links between the various menu options.

ldeaspace Manager - see Figures 64 -68

A screenshot of a typically ldeaspace Manager Interface is shown in Figure 64. A list of ldeaspaces appears in a window 200 to the left of the manager. To the right of this window is a description 202 of the highlighted ldeaspace. Function buttons within the description window provide the user with the ability to open 204 an ldeaspace, edit 206 or delete 208 ldeaspaces. A function button 210 allows a user to create a new ldeaspace.

A toolbar across the top of the screen provides access to other information managers. It is noted in Figure 64 that the ldeaspaces tab is highlighted. The remaining tabs/icons relate to the other information managers which are described below.

The Ideas Manager is used to display and manage lists of ldeaspaces. A user can view all ldeaspaces to which the user belongs (either as a contributor or as a subscriber), ldeaspaces in the Manager may be arranged and sorted by title, creator, type, date created, and date last modified.

The Ideas Manager provides a number of functions that the user may access, namely:

1. Display - The Manager displays ldeaspaces according to user preferences (see Figure 62).

2. Open - Users may open selected ldeaspaces directly from the ldeaspace Manager. 3. Create - A user can create an ldeaspace from the ldeaspace Manager and is then prompted to enter the meta-data for this new idea (see Figure 65).

4. Delete - Users may delete ldeaspaces from the system (see Figure 66).

5. Filter - ldeaspaces may be filtered by Status [open/closed] 6. Sort - ldeaspaces may be sorted by title, owner, created date, date last modified and flag (See figure 65 where a search has been done to see which ldeaspaces the user shares with co-user "Weibel")

7. Communicate with contact- Users may review communications made as entries with ldeaspaces via the Online Communications Manager and review and playback discussions recorded as audio, video, chat logs, email and saved as entries in the across all ldeaspaces within the Thinkball.

8. Edit ldeaspace Information - see Figure 67.

Figure 68 is a flowchart relating to the above actions.

Web-links Manager

The web-links manager centralises all web-links added to all ldeaspaces. It enables a user to add, browse, import, edit, search, delete, and filter web-links. Additionally, users may create new ldeaspaces, and attach web-links to existing ldeaspaces directly from the web-links store manager.

A screenshot of a typical Web-links Manager Interface is shown in Figure 69 with a flow chart relating to the actions that a user may perform within this interface in Figure 70.

The Web-links Manager provides a number of functions that the user may access, namely:

1. Browse Web-links - Users can browse uploaded web-links directly from the ldeaspace folder (web page opens in second browser window).

2. Import bookmarks - Bookmarks can be imported from popular Internet browsers such as Internet Explorer, Netscape, Safari, and Firefox.

3. Create an ldeaspace from Web-link - Users can create a new ldeaspace directly from a web-link stored within the software. The web-link will be automatically added to the ldeaspace web-links folder. 4. Create/Edit Web-links Meta-data - Users can create or edit meta-data by which to classify and identify web-links.

5. Attach Web-links to a ldeaspace - Web-links may be associated with a specific ldeaspace by right clicking on the web-link and sending it to a ldeaspace. 6. Delete a Web-link - When web-links are deleted the user will first be asked to confirm that they wish to delete the web-link and then the web-link will be removed from the system.

7. Sort Web-links - Web-links may be sorted - by title, owner, date created, or category.

Attachments Library Manager

A screenshot of a typical attachment Manager Interfaces is shown in Figure 71 with a flow chart relating to the actions that a user may perform within this interface in Figure 72.

The Attachments Library Manager allows a user or groups of users to store digital assets related to an ldeaspace. Digital assets that can be stored in the Library include sound, video, animation, text, photos, and graphics. It is important to note that the ThinkBall will support collaboration, real-time chat, and interactive concept maps, and these online conversations may also be recorded and stored in the Assets Library Manager.

The Attachment Manager provides a number of functions that the user may access, namely:

1. List Assets - Users can list assets from all the ldeaspaces within the Thinkball (see list 220 in Figure 71).

2. Create/Edit Asset Meta-Data - Users may add and edit meta-data such as creator, title, type, created date, date last modified. Users are able to add metadata keywords to multiple assets at one time.

3. Export/Import Asset - Users may export asset outside of the ThinkBall and Launch Asset in its associated application to make updates.

4. Preview Asset and Meta-data - Users may preview asset (thumb nail view) and meta-data before launching the asset . 5. Delete Digital Assets - Users may delete asset from the system or just delete it from the ldeaspace. ' 6. Sort - by title, type, owner, date stored.

7. Attach asset to ldeaspace - Users may attach assets to a Ideaspace.

8. Create an Ideaspace from an asset - Users may create a new Ideaspace from an asset.

Global Contacts Manager

The Global Contacts Manager is effectively an electronic rolodex for users' contacts and associated details. It is not a replacement for Outlook or any other fully fledged contacts system.

A screenshot of a typical Contacts Manager Interface is shown in Figure 73 with a flow chart relating to the actions that a user may perform within this interface in Figure 74.

Contacts available to the user are displayed in the left hand window of the Contacts interface window 222 and it can be seen that there are currently six contacts visible within the window.

Details relating to each contact are shown in the right hand window 224 within the Interface screen.

The Contacts Manager provides a number of functions that the user may access, namely: 1. List All Contacts - A user may view all contacts (see Figure 73)

2. Sort Contacts - Sort contacts by first name, last name, team, job title.

3. Create a Team- Contacts may be put into small groups within the global contacts manager. A user does this by creating a group name and selecting contacts that form a part of that group. 4. Edit a Contact - A user can edit their contact details.

5. Add Contacts- A user may add a contact by, either creating a new contact and manually adding contact details, or by importing contacts from other address books such as a local Outlook Address book.

6. Communicate with a Contact - A user may access their Online Communication Toolset via the Global Contacts Manager. These discussions can be recorded and saved as a file in the Assets Library Folder. 7. Delete a Contact or Group of Contacts - An administrative user may delete a contact or group of contacts

8. Search ThinkBall Directory - Users may search the ThinkBall Directory held on the Ball server for other ThinkBall users.

A Contact within the Contacts Manager is also associated with various meta-data, namely:

• First name

• Last name • Title (Ms. Mrs. Miss. Mr. Dr.)

• Team [Product, Marketing, etc.] - configured in settings or the global contacts manager

• Company

• Job title • Email at work

• Email at home

• Daytime telephone

• Mobile telephone

• IM address(s) • Physical address

• Type of contact (type of company, external contact, personal contact)

• Password (only available to the contact)

• User name (available to all)

• Photo

Figure 85 shows a flow chart summarizing some of the above actions.

Think Ball Settings Manager

The Settings Manager - Figure 75 - allows users to customise their own personal views and manage system defaults.

The Preferences Manager provides a number of functions that the user may access, namely: 1. Administer system defaults - such as: a. Date settings - select to display dates in American or European format (mm/dd/yy or dd/mm/yy). b. Time zone settings - select time zone to adjust system time settings to your time zone c. Notification Settings - select how and when to be notified about changes occurring in ldeaspaces d. Configure meta-data options - such as the options available in metadata of some system objects. Meta-data that can be configured include the following options: i. Entries - configure flags ii. ldeaspaces- configure type and folder label iii. Contacts - configure groups iv. Web-links - configure categories e. Log in settings - automatic login/manual log-in f. Synchronisation Settings - when and how often

2. Customise personal views - such as: a. Select Theme (Colour) - select colour theme for the ideaball icons + ideaspace panels b. Select Interface layout - select basic layout for the interface c. Set font size and type - select a font [arial, times, verdana] and size d. Set Skin - upload bitmap image/select default skins e. Layout options - which programme items (such as control panel/windows) should "always be on top". 3. Administer usernames and passwords - Users may change their personal username and password.

Entries Manager

A screenshot of a typical Entries Manager Interface is shown in Figure 76 with a flow chart relating to the actions that a user may perform within this interface in Figure 77.

The Entries manager allows a user to view all entries separate from all ldeaspaces. List 226 on the left side of the screenshot details all the entries that the user can access and window 228 displays the details of a particular entry (in this case the second entry in the list). Directories Manager

A screenshot of a typical Directory Manager Interface is shown in Figure 78 with a flow chart relating to the actions that a user may perform within this interface in Figure 79.

The Directory manager allows a user to view all ldeaspaces by title. List 230 on the left side of the screenshot details all the entries that the user can access and window 232 displays the details of a particular entry (in this case the second entry in the list).

As explained above, the software application 15 will run minimised on a user's PC until such time as they wish to activate the software application. When the user activates the Thinkball software, they may interact with it using any or all of the system components described above.

Prior to launching the Thinkball software on his local PC the application will run as a minimised version. The minimised version of the ThinkBall may either be a desktop launch icon or a minimised version of the application that sits in the corner of the user's desktop, or a combination of both.

A User may login to their ThinkBall with their user name and password. Upon entering this information, the application will open the users Thinkball and all of their ldeaspaces. When the open application is minimised, it rests on the desktop and notifies the user of ThinkBall updates.

The main functions of the desktop launchbar are as follows: 1. Login - User may log into the Ball server and start their Thinkball via the minimised ball with a user name and password. 2. Receive notifications - When the ThinkBall application is open but minimised, a user is notified of ThinkBall updates by a visual movement of the minimised application. Inform users when contact logs in - users should be informed when a contact logs in.

It is therefore noted that the Thinkball icon provides information regarding the communications system to the user even when the software application 15 is minimized. The icon therefore has added functionality compared to known icon representations and effectively acts as a portal to the communications system behind it.

The icon behaviour may vary depending on activities that are occurring on the system. Furthermore, the behaviour of the icon in response to different situations may be customized by the user.

Examples of icon behaviour include: changing size, changing shape, changing colour, changing texture etc.

Figures 80 to 87 show examples of various icons and icon behaviour that may be used in accordance with an embodiment of the present invention.

Figure 80 shows an example of a bouncing icon. Figure 81 shows the icon from Figure 80 with a noisy surface. Figure 82 shows a similar icon behaviour as Figure 80 but in this case the ball is configured to look like the Earth instead of a smooth ball.

Figures 83 to 85 show variations on the Earth icon, namely a rotating logo, a sonar ping and a noisy surface respectively. Figure 86 shows the icon changing shape into a cube and being sliced.

Figure 87 shows an example of the way in which meta-data is embedded into email headers to allow the system to automatically add incoming emails to the relevant Ideaspace.

In Figure 87, meta data is imbedded within the header of an standard email. The <007900793734-da99-5c09-120f 000011ee79a1@thinkball.net> code is used as a unique key by the Thinkball server to redirect the email to the appropriate idea space and then entry within that ideaspace

It will be understood that the embodiments described above are given by way of example only and are not intended to limit the invention. It will also be understood that the embodiments described may be used individually or in combination.

Claims

1. A notification icon on a graphical user interface of a user computer, the user computer being in communication with a remotely located server computer wherein the behaviour of the notification icon is arranged to change in dependence upon events occurring at the remotely located server computer.

2. An icon according to Claim 1 , wherein the icon comprises a plurality of different behaviour options each of which is associated with a different event occurring at the remotely located server computer.

3. An icon according to Claim 2, wherein the associations between icon behaviour options and server computer event is user customisable.

4. An icon according to Claim 2 or Claim 3, wherein at least some of the plurality of different behaviour options comprise animations.

5. An icon according to any of Claims 2 to 4, wherein the behaviour option is selected from the group: change in colour of the icon; change in size of the icon; change in shape of the icon; rotation of the icon; animation of the icon.

6. An icon according to any preceding claim, wherein the icon is configured to respond to push communications from the server computer.

7. An icon according to Claim 6, wherein the graphical user interface comprises tiled and/or overlapping window areas and the icon is arranged to move to the topmost layer upon receiving a push communication

8. An icon according to Claim 6, wherein the graphical user interface comprises tiled and/or overlapping window areas and the icon is arranged to be located in the topmost layer

9. An icon according to any preceding claim, wherein the icon is arranged such that the user can interact with the icon in order to be provided with information regarding the events occurring on the sever computer.

10. An icon according to Claim 9, wherein the server computer is arranged to store a plurality of content and wherein user interaction with the icon is arranged to launch an associated application on the graphical user interface for viewing content stored on the remotely located server computer.

11. An icon according to any preceding claim, wherein the behaviour of the icon is arranged to change dynamically with the events occurring at the remotely located server computer.

12. An icon according to any preceding claim, wherein the icon is ball-like in shape.

13. An icon according to any preceding claim, wherein the icon is arranged to function as a communications portal to the remotely located server computer

14. An icon according to any preceding claim, wherein the server computer is arranged to store a plurality of content items and the events that change the behaviour of the icon comprise the addition of new content items to the server computer or the amendment of existing content items on the server computer.

15. A graphical user interface on a user computer, the user computer being in communication with a remotely located server computer wherein the graphical user interface comprises a notification icon in accordance with any one of Claims 1 to 14.

16. A graphical user interface according to Claim 15, wherein the graphical user interface comprises tiled and/or overlapping window areas and the icon is arranged to move to the topmost layer upon receiving a push communication

17. A graphical user interface according to Claim 15, wherein the graphical user interface comprises tiled and/or overlapping window areas and the icon is arranged to be located in the topmost layer

18. A graphical user interface according to any of Claims 15 to 17, wherein the interface is arranged such that user interaction with the icon launches a display window area within the graphical user interface which is arranged to display the events that have occurred at the server computer.

19. A graphical user interface as claimed in any of Claims 15 to 18, wherein the server computer is arranged to store a plurality of content items grouped by content category and associated content attributes and the graphical user interface is arranged to display at least some of the content items stored on the server computer

20. A graphical user interface as claimed in any of Claims 15 to 19, wherein the graphical user interface further comprises a display window area that is arranged to display the at least some of the content items stored on the server computer.

21. A graphical user interface as claimed in Claim 20, wherein the icon and display window area are components of a common application installed on the user computer.

22. A graphical user interface as claimed in Claim 20 or Claim 21 , wherein new content may be uploaded to the server computer and/or existing content stored on the server computer may be amended by any user computer connected to the communications network and the graphical user interface is arranged to notify the user of a user computer of such an event by dynamically updating the display window area of the graphical user interface in response to the event.

23. A graphical user interface as claimed in Claim 22, wherein the notification icon is arranged to notify the user of the user computer of the event simultaneously with the change in the display window area of the graphical user interface.

24. A graphical user interface as claimed in Claim 22 or Claim 23, wherein the display window area is arranged to notify the user of an event by associating a notification flag with the new or amended content.

25. A graphical user interface as claimed in any of Claims 15 to 24, wherein the content server is arranged to send a push communication to the user computer as content is uploaded or amended.

26. A graphical user interface as claimed in any of Claims 15 to 25, wherein the remote server computer is part of a distributed communications network that is accessible by a plurality of user computers.

27. A server for storing content for access by users of a content storage system, each user communicating with the system via a user computer, the server comprising: input means for receiving content related data from users of the system; a data store for storing content; and output means for outputting a notification signal to users of the system wherein the system is arranged to output a notification signal to users of the system in dependence on changes to the content stored in the data store.

28. A server as claimed in Claim 27, wherein data received at the input means is new content for storage in the data store.

29. A server as claimed in Claim 27 or Claim 28, wherein data received at the input means is an instruction to amend content currently stored in the data store.

30. A server as claimed in any of Claims 27 to 29, wherein the notification signal is a push communication.

31. A server as claimed in any of Claims 27 to 30, wherein content stored in the data store comprises a content item and associated meta data.

32. A server as claimed in Claim 31 , wherein the meta data stored in the data store is arranged to allow content to be grouped by content category.

33. A server as claimed in Claim 32, wherein, following changes to content associated with a particular content category, the system is arranged to output a notification signal to users who are associated with the particular content category.

34. A server as claimed in any of Claims 27 to 33, wherein the output means is arranged to output a content signal to users to allow content to be displayed on a graphical user interface of the user's user terminal.

35. A server as claimed in any of Claims 27 to 34, further comprising a messaging module arranged to allow users to send messages, wherein the messaging module is arranged to insert meta data into outgoing messages.

36. A server as claimed in Claim 35, wherein outgoing messages have a sender address field and the messaging module is arranged to insert meta data into the address field of each outgoing message.

37. A distributed content storage system comprising a server according to any one of Claims 27 to 36 and a plurality of user computers in communication with the server, each user computer comprising a notification icon according to any one of Claims 1 to 14 and a graphical user interface according to any one of Claims 15 to 26.

38. A method of communicating with a remotely located server computer comprising: receiving a communication from the server computer modifying the behaviour of a notification icon on a graphical user interface of a user computer, wherein the behaviour of the notification icon is arranged to change in dependence upon events occurring at the remotely located server computer.

39. A carrier medium for carrying a computer readable code for controlling a computer to carry out the method of Claim 38.