WO2015134340A1 - Social network presence management - Google Patents

Abstract

A computer-implemented method, implemented at least in part on hardware, the method includes: editing a resource associated with an entity's presence on at least one social networking site; and publishing information about the resource to multiple locations associated with that entity's presence on said at least one social networking site. The multiple locations may be associated with multiple social networking sites, and wherein said publishing includes publishing the information about the resource to said multiple locations on said multiple social networking sites.

Description

SOCIAL NETWORK PRESENCE MANAGEMENT

BACKGROUND OF THE INVENTION

COPYRIGHT STATEMENT

[0001] This patent document contains material subject to copyright protection. The copyright owner has no objection to the reproduction of this patent document or any related materials in the files of the United States Patent and Trademark Office, but otherwise reserves all copyrights whatsoever.

RELATED APPLICATIONS

[0002] This application is related to and claims priority from co-owned and co-pending

U.S. Provisional Patent Application No 61/948,091, filed March 5, 2014, the entire contents of which are hereby fully incorporated herein by reference for all purposes.

FIELD OF THE INVENTION

[0003] This invention relates to social network systems. More specifically, this invention relates to systems, methods and devices supporting consistent presence management in social networks.

GLOSSARY & DEFINITIONS

[0004] As used herein, unless used otherwise, the following terms or abbreviations have the following meanings:

[0005] API means Application Program(ing) Interface;

[0006] GUI means graphical user interface (i.e., graphical UI);

[0007] SN means social network;

[0008] SNS means social network site;

[0009] UI means user interface;

[0010] URI means Uniform Resource Identifier;

[0011] URL means Uniform Resource Locator;

[0012] VPN means virtual private network; and

[0013] WYSIWYG means what you see is what you get.

[0014] Unless otherwise defined, terms used in this description have their plain and ordinary meaning. However, various terms are defined here in a non-limiting manner in order to aid in this description.

[0015] As used herein, a "social network" refers, without limitation, to any computer network based service that enables a user to provide information and content to other users. For example, a social network may enable a user to enter comments, upload photos, and upload other media to the user's profile page, such that other users of the social network may access the information and content. Exemplary social networks include, without limitation, Facebook, Linkedln, and Twitter.

[0016] As used herein, a "location" in a social network refers, without limitation, to a place on a social network site associated with that social network. For example, a location in Facebook may refer to a page or a tab or the like that is on the Facebook web site. A location need not be accessible by all users of the social network, although preferably it is accessible and controllable by at least one user.

[0017] As used herein, a "user" of a social network refers, without limitation, to any person or entity that has or may have a presence on that social network. It should be noted that as used herein, a "user" may also refer to a user of one or more of the example systems described herein.

[0018] As used herein, in the context of a particular user of a social network, the term

"presence" refers, without limitation, to the locations in that social network's social network sites that are associated with that particular user.

[0019] For example, in the context of a social network such as Facebook, a user is any person or other entity that has a Facebook account, and a particular user's presence in Facebook may refer to that particular user's Facebook pages, tabs, apps, and the like on the Facebook website. In the context of an arbitrary entity (including an individual user), that entity's presence in Facebook may refer, without limitation, to that entity's pages, tabs, apps, etc. on the Facebook website.

[0020] As used herein, the term "social media asset" refers to any aspect of a user's social media presence that can be fully or partially controlled by the user. For example, and without limitation, a social media asset may refer to a social media page, tab, apps, content, information, and the like.

[0021] There is no requirement that a location actually be accessible to any or all users of a social network site, although, as noted above, preferably each location is accessible and controllable by at least one user. Furthermore, a user's social network presence may be accessible by users who do not have accounts with the social network service.

BACKGROUND

[0022] Social networks such as Facebook, Twitter, Linkedln, and the like, have become a major mode of interaction and communication between individuals. Many entities such as corporations, companies, organizations, groups, and the like have also taken to using social networks, and social networks play a major role in marketing strategies and campaigns for the products and/or services of many of these entities.

[0023] Social networks are generally available an accessible to their users by social network sites - typically web-based sites available via the Internet or via mobile networks. While a typical individual user of a social networking site may have a presence including a single page or group of pages (i.e., a single social network asset or group of assets), an entity using the site for product and/or service marketing may have a presence including multiple social network assets (e.g., pages), possibly under multiple user names (e.g., multiple product brand names). Further, such an entity may also have a presence with corresponding social network assets on multiple social networking sites.

[0024] When an entity has a social networking presence including multiple locations

(e.g., social network assets or pages) on one or more social networking sites, the coordination and updating of information and content at those locations may require individual updates of social network assets on each location on each social networking site. This update process is potentially time-consuming and error prone, and may result in inconsistent information across one or more social networks. For example, an entity that maintains multiple pages on a social networking site such as Facebook may have to individually update each of those pages in order to propagate a change to each of them. Furthermore, if that same entity maintained a social networking presence on other social networking sites, propagating a change to each site would also require individual manual updates.

[0025] It is desirable for all users to be able to control and update information and content associated with their presence on social networking sites in a consistent manner. It is further desirable for users to be able to control and update information and content associated with their social network presence in manner that supports timed / scheduled updates, including updates in real time.

[0026] Entities may monitor their social network presence, e.g., in order to evaluate their marketing strategies and campaigns. When an entity has a presence on multiple social networking sites, and/or has a presence that includes multiple locations on a social networking site, monitoring all of these sites and/or locations may have to be performed on a site-by-site and location-by-location basis. In addition to being potentially tedious, such an approach makes overall monitoring difficult and error-prone.

[0027] It is desirable to provide entities with a way to monitor their social network presence and assets in one or more locations on one or more social networking sites. It is further desirable to provide entities with a way to monitor their social network presence and assets including multiple social network locations on one or more social networking sites.

[0028] It is an object of the present invention to support entities in controlling, updating, and monitoring information and content (e.g., social media assets) associated with their social network presence. It is another object of this invention to support entities in consistent controlling, updating, and monitoring information and content associated with their social network presence in multiple social network locations.

[0029] Other objects, features, and characteristics of the present invention as well as the methods of operation and functions of the related elements of structure, and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification.

BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Various other objects, features and attendant advantages of the present invention will become fully appreciated as the same becomes better understood when considered in conjunction with the accompanying drawings, in which like reference characters designate the same or similar parts throughout the several views, and wherein:

[0031] FIG. 1 shows a logical overview of a system / framework for managing social network sites according to exemplary embodiments hereof;

[0032] FIG. 2 depicts a logical view of a typical social network page on a social network site;

[0033] FIG. 3 depicts a logical view of an entity's social network presence;

[0034] FIG. 4 depicts a logical view of applications according to exemplary

embodiments hereof;

[0035] FIGS. 5-8 depict a logical view of exemplary database information according to exemplary embodiments hereof;

[0036] FIG. 9 depicts a logical view of functionality provided by a system according to exemplary embodiments hereof;

[0037] FIG. 10 depicts exemplary operational flow using a system according to exemplary embodiments hereof;

[0038] FIG. 11 shows a typical computer in the system, according to exemplary embodiments hereof; and

[0039] FIGS. 12(A)-12(Z) depict aspects of an exemplary graphical user interface (GUI) according to embodiments hereof. DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EXEMPLARY

EMBODIMENTS

[0040] FIG. 1 shows a logical overview of a system / framework 100 to help and support social network presence management according to embodiments hereof. Such a

system/framework is sometimes referred to herein as a "presence management system" or a "presence management framework."

[0041] As shown in the drawing in FIG. 1, multiple users 102-1, 102-2, 102-n for some number n > 1 (generally denoted 102), each access one or more social network sites 104-1, 104-2, ... 104-JM for some number m > 1 (generally denoted 104), e.g. via a network 106 (e.g., the Internet). A user 102 may represent an individual person or may represent an entity (e.g., a company, corporation, school, group, organization, etc.) It should be appreciated and

understood that the rectangles in the drawings representing users may represent those user's computing devices used to access the social network sites 104 and other components of the system/framework 100 as described below. Each user may have an account and associated presence on more than one of the social network sites 104.

[0042] With reference again to FIG. 1, system 100 includes application(s) 108

(sometimes referred to herein as a "presence management application(s)") and one or more interfaces 110 to the presence management application(s) 108. The presence management application(s) 108 may reside and operate on a backend computer system 112 and may access and interact with one or more databases 114. Although the presence management application(s) 108 may be a single integrated application or may comprise multiple distinct applications, for the remainder of this document the presence management application(s) 108 may be referred to in the singular as "presence management application 108," it being understood that this term may refer to one or more actual applications.

[0043] A user 102 wishing to use the presence management application 108 may access the presence management application 108 via the interface(s) 110. The interface(s) 110 preferably provide one or more graphical user interfaces (GUIs) 116 to the presence

management application 108, and in a presently preferred implementation the presence management application 108 may be implemented, at least in part, as one or more web-based applications and the GUIs 116 of interface(s) 110 may include at least one web-based GUI that may be accessed and used in a conventional browser on a computer device.

[0044] A user 102 may thus access the presence management application 108 through a web-based GUI, via a network 106 such as the Internet. It should be appreciate that users may access the presence management application 108 via the same network 106 as they use to access the social network sites 104. In some implementations user's may be provided with secure access to the presence management application 108, however such access will still use the underlying network 106, although a virtual private network (VPN) or the like may be used to provide a secure connection.

[0045] FIG. 2 depicts a logical view of a typical social network page 202 on a social network site such as Facebook. The page 202 has one or more page elements (e.g., text, media such as images, video, sounds, etc., other pages or apps or tabs or the like), denoted 204-1, 204-2, 204-m in the drawing (for some number m≥ 1).

[0046] An entity (e.g., an individual user, a company, etc.) may have multiple social network accounts on one or more social networks. For the purposes of this description, an account on a social network corresponds to a distinct login for that social network. For example, as shown in FIG. 3, an entity may have k social network accounts, for some number k > 1. The accounts may all be on the same social network (e.g., all on Facebook), or they may be on different social networks (e.g., on Facebook and Linkedln and Twitter). Each account has account information (e.g., login information, authentication information, permissions, etc.) associated therewith. Each account also has a presence, including one or more locations (e.g. , pages, tabs, apps, etc.), associated therewith.

[0047] Each entity using the presence management system 100 preferably registers with the presence management system and becomes an authorized subscriber to and user of the presence management system. In the case of an individual user, the presence management system needs information about that user's social network accounts. In the case of an entity such as a company, the presence management system needs to know and maintain information about users who are authorized to use the presence management system on behalf of the entity. For the purposes of this description, entities (e.g., individual users, companies, etc.) of the system 100 are sometimes referred to herein as subscribers to the system. It should be appreciated that the term "subscriber" is not intended to imply any particular legal or contractual relationship between the system 100 and any entities, and the system is not limited by the formal or legal nature of the relationship between the system and the entities.

[0048] The presence management framework 100, via presence management application

108, enables users to manage their social network presence on some or all of their social network accounts via a single interface and location. With reference to FIG. 4, in a presently preferred implementation, the presence management application 108 (FIG. 1) may include: subscriber management application(s) 418 (including company management application(s) 420, and user management application(s) 422); interface application(s) 424 (including user interface application(s) 426); media management application(s) 428; presence management application(s) 430 (including page management application(s) 432 and page management application(s) 434); update application(s) 436 (including broadcast application(s) 438); campaigns 441; reporting 443; and miscellaneous application(s) 440.

[0049] Those of ordinary skill in the art will realize and appreciate, upon reading this description, that the separation of the presence management applications 108 into multiple component applications, as described above with reference to FIG. 4, is used as a convenience for the purposes of this description. Those of ordinary skill in the art will further realize and appreciate, upon reading this description, that different and/or other ways of logically describing the application components may be used and are within the scope of the system.

[0050] It should also be appreciated and understood that the various component applications described here may be integrated, in whole or in part, into one or more applications running on one or more computing devices that make up the backend 112. Even when implemented has multiple distinct software applications, aspects all applications may be shared.

[0051] As noted above, the applications 102 may store and maintain information in database 114. With reference to FIG. 5, an exemplary database 114 according to embodiments hereof may include user information 502, company information 504, media information 506, social network information 508, administrative information 510, and other miscellaneous information 512. Those of ordinary skill in the art will realize and appreciate, upon reading this description, that the description of the data/information in database 114 given here is merely exemplary, and that different and/or other information may be stored in the database 114.

Furthermore, it should be appreciated that some or all of the information described here may be stored in a single database point multiple distinct databases, in the manner of storing

information, the location of the information, and the number of distinct databases are not limiting on the scope of the system.

[0052] With reference to FIGS. 5-6, exemplary user information 502 in the database 114 may contain information about each user of the presence management system 100 (i.e., about each subscribing user), and may include, for each such user: that user's social network information 602 (e.g. , social network account information needed or used by the presence management application 108 to support operation of the presence management application), accounting/administrative information associated with that user 604, permissions associated with that user 606, and other miscellaneous information 608 associated with that user.

[0053] With reference to FIGS. 5 and 7, exemplary company information 504 in database 114 may contain information about each company that is a user of the presence management system 100 (i.e., about each subscribing company), and may include, for each such company, that company's social network information 702 (e.g., social network account information needed or used by the presence management system in order to support operation of the presence management application(s) for that company's users). The company information may also include permission information 704; accounting/administrative information 706;

information about users authorized to use the presence management system on behalf of the company 708; and other miscellaneous company information 710. For each user associated with a company, the system preferably stores and maintains user information (e.g. , as described above with reference to FIGS. 5 and 6).

[0054] With reference now to FIG. 8, exemplary social network information 608 in the database 114, both for a company and for a user, preferably includes login information 802 for each social network site associated with that company and/or user, permissions information 804, including permissions associated with each said social network site, and presence information 806 associated with each said social network site (including, e.g., page(s) information 808 and page element(s) information 810, such as information about apps or tabs and the like associated with each said social network site).

[0055] An overview of exemplary functionality provided by a system 100 via the presence management application 108 according to embodiments hereof is shown in FIG. 9. With reference to FIG. 9, the system supports user management; company management, a dashboard, page management, app management, a media library, posts and comments, and update broadcasts. A typical system 100 according to embodiments hereof may also include login management and registration, account set up assistance, and a support/help center.

[0056] User management features and aspects of the system may be supported by the applications 102, including the subscriber management applications 420 and further including user management applications 422. In an exemplary implementation, the user management features include: view user, assign permissions, add user, edit user, and list users

(paginated/filtered). As will be appreciated by those of ordinary skill in the art, the user management features may include different and/or other features without departing from the scope of the invention.

[0057] Company management features and aspects of the system may be supported by the applications 102, including the subscriber management applications 418, and further including company management applications for 420. In an exemplary implementation, the company management features include: add company, edit company, assign permissions, and list companies (paginated/filtered). As will be appreciated by those of ordinary skill in the art, the company management features may include different and/or other features without departing from the scope of the invention.

[0058] The dashboard features and aspects of the system may be supported by the applications 102, including interface applications 424 and further including user interface applications 426. In an exemplary implementation, the dashboard features may include: activity stream, and page "likes" graph. As will be appreciated by those of ordinary skill in the art, the dashboard features may include different and/or other features without departing from the scope of the invention.

[0059] The page management and app management features and aspects of the system may be supported by the applications 102, including the presence management applications 430, and further including the page management applications 432 and the app management applications 434. In an exemplary implementation, the page management features include: list pages, and page, update profile image, view page, import pages, and delete page; and the app management features include delete app, view app, preview app, add app, edit app, publish app, and list apps (paginated/filters). As will be appreciated by those of ordinary skill in the art, the page and tab and app management features may include different and/or other features without departing from the scope of the invention.

[0060] The media library features and aspects of the system may be supported by the applications 102, including the media applications 428. In an exemplary implementation, the media library features include: add media library, edit media library, view media library, assign permissions, and search media library. In addition, media library features may include: and its media object, add media object, delete media object, and tag media object. As will be appreciated by those of ordinary skill in the art, the media library features may include different and/or other features without departing from the scope of the invention.

[0061] The posts and comments features and aspects of the system may be supported by the applications 102, including interface applications 424 and further including user interface applications 426. In an exemplary implementation, the posts and comments features may include: view posts, including viewing trending posts, create post, edit post, and delete post. As will be appreciated by those of ordinary skill in the art, the posts and comments features may include different and/or other features without departing from the scope of the invention.

[0062] The broadcast updates features and aspects of the system may be supported by the applications 102, including update applications 436 and further including user broadcast applications 438. In an exemplary implementation, the broadcast updates features may include: broke cost profile image update, for cost post update, and cost cover image. As will be appreciated by those of ordinary skill in the art, the broadcast updates features may include different and/or other features without departing from the scope of the invention.

[0063] Campaigns features and aspects of the system may be supported by the applications 102, including the campaigns applications 441.

[0064] Reporting features and aspects of the system may be supported by the applications 102, including the reporting applications 443.

EXEMPLARY IMPLEMENTATION

[0065] The following section provides an outline of aspects of the functionality in a presently preferred exemplary embodiment of the system.

LOGIN/SIGNUP

Registration

[0066] The system may provide one more pricing packages, including one for small-to- medium enterprises (SME). The user will be able to register for the system proving an email address, password, company, and package (default is SME). A user can select to free trial (e.g., 120 Days) or can pay for subscription.

On Success

• Email confirmation is sent to the email address used for registration.

• The user is redirected to dashboard with a dialog box directing them to use a setup wizard.

• If payment is made then an email receipt is sent to the email address used for registration.

Login

[0067] The user can login to the system using either their email address or username.

After some number (e.g., 3) of failed login attempts require capture.

On Success

• The user is redirected to a dashboard with 'help' dialog based on cascading scenarios

o No Facebook Account connect

o No Pages in system

o No Tabs created

Facebook Registration

[0068] User can register for the system using their Facebook credentials (e.g. , Facebook

OAuth). Package will be determined from outbound link (one link for Enterprise, One link for

SME). The user will grant access to business pages, tabs, apps, posts, comments, and insights.

On Success

• Facebook Pages are loaded into system awaiting confirmation

• Email confirmation is sent

• Cascading o If plan is SME and multiple pages detect launch dialog suggesting

upgrade to Enterprise package

o Redirected to dashboard with a dialog box directing them to utilize setup wizard.

Login/ Facebook Login

[0069] The user can login using their Facebook credentials.

On Success

• Redirect user to dashboard with 'help' dialog based on cascading scenarios

o No Facebook Account connect

o No Pages in system

o No Tabs created

USER MANAGEMENT

Add User

[0070] A new user can be created by another existing user and added to any company of which that existing user is a member or to which that existing user has access.

On Success

• Redirect to relevant company page

• Email user with login token

Edit User

[0071] A user can be edited by another user that belongs to the same company or has access to edit that company.

On Success

• Redirect to relevant user view page

Delete User

[0072] A user can be deleted by another user that belongs to the same company or has access to edit that company. Confirmation must be given and a soft delete used.

On Success

• Redirect to relevant company page

List Users (Paginated)

[0073] Lists users with paginated and filtered results from company view page.

View User

[0074] Show user details including latest activity {e.g., 10 items such as posts, comments, tabs, apps, media library, pages, users, companies). Show owned items (posts, comments, tabs, apps).

Assign Permissions and Pages

[0075] A user can be assigned permissions by another user that belongs to the same company or has access to edit that company. On Success

• Redirect to relevant user page

COMPANY MANAGEMENT

Add Company

[0076] A company can be created by another user and added to any company of which that user is a member of or to which that user has access.

On Success

• Redirect to relevant company page

• Email user with login token

Edit Company

[0077] A Company can be edited by a user that belongs to that company or has access to edit that company.

On Success

• Redirect to relevant company view page

Delete Company

[0078] A company can be deleted by a user that belongs to that company or has access to edit that company. Confirmation must be given and a soft delete used.

On Success

• Redirect to relevant company page

List Companies (Paginated)

[0079] Lists users companies paginated and filtered.

View Company

[0080] Show company details.

Assign Permissions and Pages

[0081] A user can assign permissions to a company to which the user has access or to which the user has permission to edit.

On Success

• Redirect to relevant user page.

MEDIA LIBRARY

List Media Library (Paginated)

[0082] Lists files with paginated and filtered results. Files can be tagged from list page.

Upload a file

[0083] A user can upload a file into the media library and tag the file with free text values for searching later. On Success

• Redirect to media library

Edit File

[0084] A user can edit a file in the media library and tag the file with free text values for searching later.

On Success

• Redirect to media library

Delete File

[0085] A user can delete a file from media library. The system will preferably provide confirmation and warning if image is being used.

On Success

• Redirect to media library

BROADCAST UPDATES

Broadcast Profile Image

[0086] A user can send a broadcast profile image across any pages to which they have access.

Broadcast Cover Image

[0087] A user can send a broadcast cover image across any pages to which they have access.

Broadcast Post

[0088] A user can send a broadcast post across any pages to which they have access.

POSTS & COMMENTS

Cache Comments and Posts

[0089] Posts and comments may be synchronized with social media in so that requests are not made on demand to pull back recent data. Facebook's real-time updates service may be used to cache Facebook posts.

Schedule Posts

[0090] A user can create future posts that will be published to selected platforms. The posts can contain, text, images and links. While publishing at a scheduled time preferably occurs at that time, it should be understood that publishing at scheduled time may occur substantially at that time.

On Success

• Redirect to view scheduled posts page Create New Post

[0091] A user can create a current post that will be published to selected platforms. The post can contain, text, images and links.

On Success

• Redirect to view posts page

Edit Post

[0092] A user can edit a scheduled or existing post. The post can contain, text, images and links.

On Success

• Redirect to view posts page

Delete Post

[0093] A user can delete an existing or scheduled post from selected platforms.

On Success

• Redirect to view posts page

View posts / trending Posts

[0094] A user can view the listing paginated posts. The user can also view a list of trending posts. Trending posts are based on the number of likes and comments over time with multipliers applied to create a list of the most active posts.

APP MANAGEMENT

Add App

[0095] A user can be create an app and publish it to page to which that user has been granted access. A drag an drop editor will allow the following widgets to be added:

Text Widget

Gallery Widget

YouTube Widget

Twitter Feed Widget

Contact Form Widget

Iframe Widget

Image Widget

Facebook Poll Widget

Facebook Like Widget

On Success

• Redirect to relevant app

Edit App

[0096] A user can edit any app to which that user has been granted access

On Success

• Redirect to relevant user app page Delete App

[0097] A user can delete a app to which that user has been granted access. Preferably confirmation must be given and a soft delete used.

On Success

• Redirect to app list page

List Apps (Paginated)

[0098] Lists apps with paginated and filtered results

View App

[0099] Show app details including all pages on which the app is published. A preview of the app will be screen scraped and stored.

Publish App

[00100] Publishes saved content.

Preview App

[00101] View updated app content prior to publishing

ACCOUNT SETUP WIZARD

Step 1

• A user can connect one or many social media accounts from Facebook or Twitter Step 2

• A user can import one or many business pages from their connected social media accounts

DASHBOARD

Latest Activity

[00102] A user can view the dashboard containing a list of the latest activity relating to the company that he belongs. The following will be tracked via latest activity:

• Recent Comments

• Recent Posts

• Recently Created Scheduled Posts

• Recently Created/Updated Apps

• Recently Created/Updated Users

• Recent Broadcast updates

Likes over time

[00103] A user can see the number of likes/followers that belong to all pages to which that user has access. Permissions

[00104] The table below outlines permissions that will be created within the system and assigned at both a company and user level.

Module Permission

Create Mass Post

[00105] The following section summarizes additional aspects of a presently preferred exemplary embodiment of the system.

[00106] An exemplary implementation of the system uses the following technologies:

• Language

o PHP

• Framework

o Code Igniter is an MVC framework that handles the flow of information from the screen (view) to the database (model).

• Database

o The database has been implemented using MySQL. MySQL is a relational database schema and allows for relationships to be defined between tables.

• Operating System

o Linux

• Web Server

o Apache

[00107] In an exemplary implementation of the system the GUI provides uses the following screens and/or screen functionality:

[00108] Login: Allows user to enter their username and password to authenticate into their account. Validation provides responses based on the validity of the credentials and messages are returned to the user including the ability to reset their password. The login screen has the following fields: Username, Password

[00109] Password Reset: Allows the user to enter their email address triggering the password-reset process. If a valid email is entered a token for the associated account is randomly generated and an email with a link to the password reset screen is sent to that email. The Password Reset screen has the following fields:: Email

[00110] Change Password (Reset Password): If a valid token is used the user can update their password. Fields: Password, Confirm Password

[00111] Sign Up: Allows a user to sign up for a 60-day trial. Username and Email fields are unique and checked against existing users in the system. Passwords are required to be longer than four characters. Successful authentication directs the user to the dashboard. Fields:

Username, Email, First Name, Last Name, Password, Confirm Password.

[00112] Dashboard: Lists existing Facebook pages and any system controlled tabs with their published status and ability to edit those tabs. If the user has not connected any Facebook accounts a link is provided to connect the account. [00113] Comments and Posts: Contains a list of posts for the selected page and a form to add a new post. Each post in the list contains the avatar of the poster, number of like, comments and date of post and a link to comment on the post. Fields: Post, Link, Photo

[00114] Post Comments: Lists comments for the selected post with a reply/comment form to comment on the selected post. Fields: Comment

[00115] Add/Edit App: Contains an editor (preferably WYSIWYG) for app creation with a wide range of widgets offering different functionality. A list of available pages is listed with the ability to publish to one or many apps. Apps are periodically auto saved.

Widgets

• Text - Creates a resizable rich-text box

• Photo - Displays a photo selected from the media library

• YouTube - Displays an imbedded YouTube video using the external URL

• Google Maps - Embeds a Google Maps widget based on a user defined address

• Twitter Feed - Embeds a twitter feed based on the twitter account name

• Contact Form - Embeds a dynamic HTML contact form allowing for capture of name, email, phone, company, and custom enquiry.

• Gallery - Embeds a JQuery gallery based on images in the media gallery

• Poll - Embeds a dynamic poll widget with customizable options both singular and multiple choice.

• Facebook like - imbeds Facebook like into an app.

Tab Settings

• Height- customize the height of the app

• Background Image - Set a custom background image for the app with repeat,

scrollable, fixed position options.

• Background color - Set a custom background cover for the app

[00116] Fields: Title, Thumbnail Image

[00117] My Account: Contains forms to update both personal details and password.

Requires current password to make any changes. Fields: Current Password, Email, First Name, Last Name, New Password, New Password Confirm.

[00118] Edit Account: Contains form to edit the personal details of that user/account.

Fields: Email, First Name, Last Name.

[00119] Reset Account Password: Reset password form with ability to randomly generate a new password. Fields: New Password, New Password Confirm

[00120] Member Permissions. Manages the permissions for the user as well as which pages to which the user has access.

[00121] Templates: Lists of user-created tab/app templates with the following actions, edit, import, download, and delete.

[00122] Edit Templates: Functionality as per the tab/app editor page. [00123] Import: Allows user to create a template based on an existing tab/app with the option to overwrite an existing template via a drop down list of existing templates.

[00124] Tutorials: A list of tutorials.

[00125] My Teams. Lists all teams created under an enterprise account, including number of pages, users and tabs, with ability to add a new or connect a Facebook account to the team.

[00126] Create New Team: Allows the user to setup a new team account with an administrator. Fields: Team Name, Team Description, Username, Email, First Name, Last Name, New Password, New Password Confirm

[00127] Manager: Lists all system users with their user type, package, sign up date and the following actions: edit, show details. The listing page contains filters for each of the table columns for search functionality. It also links to the create account page.

[00128] Manager Mass Updates: Allows the user to publish updates across multiple Facebook pages

[00129] The system may be formed from a number of logical controllers containing functionality for specific parts of the application:

• Session: Contains all authentication functionality such as login, logout, forgot password and registration.

• Uploads: Contains functionality to upload documents into the upload and storage directory

• IPN: Contains functionality for Instant notification from PayPal. When a

payment is processed the IPN is triggered and the system updates the client status.

• Dashboard - Accounts: Contains functionality to connect and disconnect

Facebook pages to client accounts. Includes Facebook OAuth allowing the application access to the users Facebook page(s)

• Dashboard - Home: Utility controller that direct the user to the appropriate dashboard based on the account package

• Dashboard -Messages: Contains functionality for internal messaging of users allowing for resellers to message clients.

• Dashboard - Profile: Contains functionality for My Account, including updating of details and upgrading of packages.

• Dashboard - Tabs: Contains functionality for the creation, deletion and management of Facebook tabs including the WYSIWYG editor and widget control.

• Dashboard - Manager: Contains administration functionality for management users such as user management, payments, packages, and debugging.

[00130] The platform may allows for the following permissions to be assigned to a user:

• Access Dashboard

• Create new apps • Edit apps

• Publish apps

• List Facebook accounts

• Connect Facebook accounts

• Disconnect Facebook accounts

• Browse media library

• Upload, move, delete, change uploaded files

• List accounts

• Create new accounts

• Edit accounts

• Change account permissions

• Delete accounts

[00131] The system may use third party APIs, including the following:

[00132] The Facebook API is used to pass information between the system and Facebook, including the following data:

• Page Details

o Profile Image

o Timeline Image

• Page Posts

• Page Comments

• Page Custom Tabs

[00133] The Mail Chimp API or the like may be used to send email reminders

[00134] The PayPal API or the like may be used for the payment of client accounts including IPN.

[00135] Those of ordinary skill in the art will realize and appreciate, upon reading this description, that the GUI 106 may differ from device to device without departing from the scope of the invention. For example, the GUI on a small device (with a small display screen) such as a smartphone may differ from the GUI on a device such as a desktop computer with a relatively large display screen.

[00136] The backend computer system 110 may comprise one or more computers or computer systems. Computer systems are described in greater detail below. When formed of more than one component computer or computer system, the backend component computer systems may be co-located or in may be multiple locations.

[00137] The database(s) 112 may be co-located with the backend computer system 110 or may be at a separate location. The database(s) 112 may be fully or partially integrated into the presence management application 108. The presence management application 108 may access, maintain, and update the database(s) 112 using any database techniques, and the system is not limited by the manner in which the database(s) 112 is accessed, maintained, or updated. [00138] Although the database(s) 112 may by a single integrated database or may comprise multiple distinct databases, for the remainder of this document the database(s) 112 will be referred to in the singular as "database 112," it being understood that this term may refer to one or more actual databases.

CAMPAIGNS

[00139] A user can create a campaign which includes one or more content updates sent to one or more social media assets. Users can target social media assets in various ways, e.g., using predefined free text tags, geo location, time zone, and/or network.

Campaign Creation

[00140] A user created a new campaign using an internal title. A user may then create one or more content updated using the following steps:

1. Select pages based on targeting options.

2. Create content (new post, cover images update, profile image update, etc.)

3. Schedules time to publish

On Success

• The user is redirected to a campaign listing

Campaign Reporting

[00141] Once a campaign has been reported a user can view insights based on the content updates. The following exemplary metrics may be measured :

• Likes

• Reach

• Impressions

• Engagement

• Re -tweets

• Favorites

• Comments

REPORTING

[00142] Users may generate reports measuring their social media analytics. Reports may have filters, e.g., the following filters: Filter by pre-defined tags, geo location and time period. Reports can be shown visually in the GUI or exported, e.g., as CSVs (comma separated values).

[00143] The following exemplary metrics may be measured:

• Likes

• Reach

• Impressions

• Engagement

• Re -tweets

• Favorites

• Comments • Status

• Twitter Followers

• Linkedln Likes

OPERATION OF THE SYSTEM

[00144] In operation, an entity (an individual user or a company or the like) registers with a system (e.g., system 100), for example, via the web-based interface. Preferably the system is available on the Internet via one or more URLs. As part of a registration process, the entity provides information about their social network accounts that they wish to control and maintain via the system. The system preferably checks the login information provided buy the subscribing entity. Subscribers may edit and update their information as needed.

[00145] The user is provided with a dashboard that preferably contains a list of all the latest activity relating to that user or to the company to which that user belongs. In an exemplary implementation, the following information is tracked via latest activity and presented on the users dashboard: recent comments, recent posts, recently created scheduled posts, recently created/updated tabs, recently created/updated uses, and recently provide cost updates. A user may also be able to see the number of likes/followers that belong to all pages to which that user has access.

[00146] The user may use the UI to create, edit, or update their social network presence

(e.g., Facebook pages or the like). The user may create tabs or content on the system and propagate updates to multiple locations in multiple social network sites at a selected time (including in real time).

[00147] For example, as shown in the flowchart in FIG. 10, which depicts aspects of a present exemplary embodiment, a user with control over presence at multiple locations on one or more social network sites may create, edit, or update a resource (e.g., information and/or content) associated with those sites (at S1002), and may then publish that new/updated resource (at SI 004) to multiple locations on one or more social network sites.

[00148] The user may publish the resource in real time or may schedule a time for the resource to be published. At the selected time the system broadcasts the resource updates to the appropriate social network sites. In the case of a new resource (e.g., a new tab/app) the user may create the tab/app and then edit the tab/app using the dashboard. Existing apps/tabs may be edited. Resources such as text, images, widgets and the like may be added to or deleted from tabs. The resources may be obtained from the media library. EXEMPLARY GRAPHICAL USER INTERFACE

[00149] As noted above, the interface(s) 110 to presence management application 108 preferably includes GUI 106, including a web-based GUIs. FIGS. 12(A) to 12(U), depict aspects of the web-based GUIs according to embodiments hereof.

[00150] The graphical user interfaces illustrated in FIGS. 12(A) to 12(U) represent example web-based GUIs that may enable a user to control presence at multiple locations on one or more social network sites. Controlling presence may include creating, editing, or updating a resource (e.g., information and/or content) associated with those locations. Further, the example GUIs illustrated in FIGS. 12(A) to 12(U) may enable a user to publish new and/or updated resources to multiple locations on one or more social network sites.

[00151] FIG. 12(A) illustrates an example of a GUI implementing a dashboard, as described above. As illustrated in FIG. 12(A) the left side of the GUI includes an example activity stream, where the example activity stream includes a list of recent activity and associated information, including when an activity occurred, which user is associated with the activity, and the type of activity. As further, illustrated in FIG. 12(A) the right side of the GUI includes various exemplary graphs, including an example page "likes" graph, where the page "likes" graph illustrates the number of "likes" with respect to a time axis. The example graphs in FIG. 12(A) also include a "New Likes" graph; a page engagement graph, a page impressions graph, a page reach graph, and a post reach graph.

[00152] FIG. 12(B) illustrates an example of a GUI implementing a page list included in social media asset management as described above. The GUI illustrated in FIG. 12(B) may enable a user to view a list of social media assets (e.g., pages), where a list may include a page profile image, a social media asset name, a social media asset category, social networks where the social media asset has a presence, and tags associated with a social media asset. As illustrated in FIG. 12(B), for example with Empire Foods page, a social media asset may include a presence on a plurality of social networks (e.g., Facebook and Twitter). As illustrated in FIG. 12(B), the GUI includes respective Actions icons for each social media asset included in a social media asset list. Upon activation, an Actions icon may enable a user to perform actions associated with social media asset management. In one example, when a user selects a social media asset from the social media asset list, a GUI including a social media asset summary may be presented. FIG. 12(C) illustrates an example of a GUI including a social media asset summary. As illustrated in FIG. 12(C), a social media asset summary may include a social media asset profile image, a social media asset name, recent activity, and tabs. Further, as illustrated in FIG. 12(C) a tab associated with each social network presence may be provided (e.g., Facebook feed tab in FIG. 12(C)). In this manner, a user may select a tab to view relevant social network information. As further illustrated in FIG. 12(C), the GUI may include icons associated with the following actions: Create a New Post, Add App, Facebook Options, and More. Upon activation, each of these icons may cause respective GUIs to be presented that enable a user to perform the corresponding action.

[00153] FIG. 12(D) illustrates an example of a GUI the may be presented upon Create a

New Post icon being activated. That is, FIG. 12(D) illustrates an example of a GUI

implementing posts and comments, as described above. It should be noted that a post may be an example of a resource described above with respect to FIG. 10. As illustrated in FIG. 12(D), the GUI includes an Add a new post instruction, a message field, attach file icon, schedule a post field, pages selector, social network selector, and assignee selector. Add a new post instruction provides a brief explanation to a user regarding the use of the graphical user interface. Message field is a field that enables a user to enter text, such that a user can compose a message. As illustrated in FIG. 12(D), message field may indicate the number of available characters for a message. Attach file icon may enable a user to select a file to include with the post. That is, upon activation, select a file icon may enable a user to select a multimedia file to include as part of a post. Schedule a post field may enable a user to schedule when a post is published (e.g., can be viewed by other user) to selected social networks. For example, a user may wish to wait for a future scheduled event to occur before publishing the post. Pages selector enables a user to select pages (e.g. , social media profiles) where the post will publish. For example, when a company (e.g., Coca-Cola) maintains social media profiles for each of a plurality of brands (e.g., Coca-Cola, Diet Coke, Coke Zero, etc.), pages selector enables an authorized user to select the pages on which the post will publish. That is, page selector may enable a user to select a sub-set of available pages for publishing information. In the example illustrated in FIG. 12(D), the Empire Mejico page is selected and visually indicated as such. In a similar manner, social network selector enables a user to select social networks (e.g., Facebook, Twitter, Linkedin, etc.) on which the post will publish on the pages there of. That is, page selector may enable a user to select a sub-set of available social network services for publishing information. Assignee selector enable a user to select a user (including the user herself) that will appear to have published the post. Thus, the GUI illustrated in FIG. 12(D) enables a user to publish

information to multiple locations associated with that entity's presence on said at least one social networking site.

[00154] FIG. 12(E) illustrates an example of a GUI implementing a media library, as described above. As described above, example media library features include: add media library, edit media library, view media library, assign permissions, and search media library. In addition, media library features may include: adding a media object, deleting a media object, and tagging a media object. The example GUI illustrated in FIG. 12(E) enables a user to select one of a plurality of media libraries. As illustrated in FIG. 12(E) a media libraries may be categorized (e.g., Banners, Empire Foods, and Style Guides) such that a user may search, sort, and/or filter media files. The example GUI illustrated in FIG. 12(F) represents an example GUI that may be presented upon a media library being selected (e.g., clicking radio button associated with Empire Foods in FIG. 12(E)). The example GUI illustrated in FIG. 12(E) includes a list of media objects and respective Actions Icons. Upon activation, Action Icons, may enable a user to perform one or more of the features described above. Media library may be particularly useful for a company having a plurality of brands and a plurality of logos, videos, and images associated therewith. 12(F) illustrates an example of a GUI implementing a dashboard, as described above.

[00155] As described above, an entity may wish to monitor their social network presence in one or more locations on one or more social networking sites. FIG. 12(G) illustrates an example of a GUI implementing enabling a user to monitor their social network presence in one or more locations on one or more social networking sites. As illustrated in FIG. 12(G), a plurality of pages and associated posts are displayed in the GUI using page windows (i.e., Empire Foods on a first social network, Empire Gastron, and Empire Foods on a second social network). The GUI illustrated in FIG. 12(G) may be configured to update in a real-time manner (e.g., as soon as each of the pages update). As illustrated in FIG. 12(G) each of the page windows include an "x" in the title bar, which upon activation may cause the page window to close. Further, as illustrated in FIG. 12(G), a user may add feed if a page window space is available, as indicated to the right of FIG. 12(G).

[00156] As described above, user management features may include: viewing a user, assigning permissions, adding a user, editing a user, and listing users (paginated/filtered). FIG. 12(H) illustrates an example of a GUI implementing user management, as described above. The GUI illustrated in FIG. 12(H) may enable a user to view a list of users, where a list includes a first name, a surname, a username, an email address, a company of the user, an IsEnabled permission indicator, and respective Actions icons for each user included in a user list. Upon activation, an Actions icon may enable a user to perform actions associated with user

management (e.g., edit permissions). FIG. 12(1) illustrates an example of a GUI that may be presented upon a user selecting to edit another user's permissions. The GUI illustrated in FIG. 12(1) includes tabs (e.g., Global Permissions, Company Permissions, ... Media Library Permissions), each of which, when selected may enable a user to set corresponding permissions as illustrated for Global Permissions in FIG. 12(1). In one example, upon selecting a user from the list illustrated in FIG. 12(H), a GUI showing more information about particular user may be presented. FIG. 12(J) illustrates an example of a GUI showing more information about particular user. The GUI illustrated in FIG. 12(J) includes Details, Social Accounts, and Recent Activity of a particular user. Further, the GUI illustrated in FIG. 12(J) includes Edit Profile icon and Add Social Account icon. Upon activation, Add Social Account icon may enable a user to associate Social Accounts to a particular user and cause Socials Accounts section of the GUI to be updated.

[00157] As described above, company management features may include: adding a company, editing a company, assigning company permissions, and listing companies

(paginated/filtered). FIG. 12(K) illustrates an example of a GUI implementing exemplary company management, as described above. As illustrated in FIG. 12(K), a company is selected (i.e., Empire Magazine) and the GUI includes Add User, Add Business Asset, Users, Assets, Child Units, and More. The GUI illustrated in FIG. 12(K) corresponds to Overview tab being selected, FIG. 12(L) corresponds to Child Units tab being selected, the GUI illustrated in FIG. 12(M) corresponds to Users tab being selected, and the GUI illustrated in FIG. 12(N)

corresponds to Assets tab being selected. Further, the GUI illustrated in FIG. 12(0)

corresponds to Add Business Unit icon being activated. As illustrated in FIGS. 12(L) to 12(N) lists similar to those described above with respect to FIGS. 12(B), 12(E), and 12(H) are included in the GUIs illustrated in FIGS. 12(L) to 12(N). Each of the lists illustrated in FIG. 12(L) to 12(N) may enable a user to perform corresponding company management tasks. For the sake of brevity, each of FIGS. 12(L) to 12(N) are not described in complete detail and reference is made to the description of FIGS. 12(B), 12(E), and 12(H) above. The GUI in FIG. 12(0) includes Child Company name field, Tags field, Country selector, and address fields (note only State is shown in FIG. 12(0)). A user may respectively enter relevant information associated with a child company/unit using each of Child Company name field, Tags field, Country selector, and address fields and thereby populate Child Company information. Upon completion of information entry using the GUI in FIG. 12(0), the GUI illustrated in FIG. 12(L) may be updated to include the added child company.

[00158] FIGS. 12(P) to 12(U) illustrate examples of GUIs implementing an Account

Setup Wizard, as described above. The GUIs illustrated in each of FIGS. 12(P) to 12(U) enable a user to provide system 100 with information corresponding to a company. The GUI illustrated in FIG. 12(P) includes Company name and address fields for entering corresponding information for a company. The GUI illustrated in FIG. 12(Q) includes email, first name and last name fields for entering corresponding information for a user profile.

[00159] The GUI illustrated in FIG. 12(R) enables a user to add/connect social media accounts to system 100. That is, enable information sharing. As illustrated in FIG. 12(R) a user may connect a plurality of accounts each associated different social media services and profiles. In FIG. 12(R) the GUI includes icons associated with social media services (e.g. "Connect a Facebook Account" and "Connect a Twitter Account"). Upon activation of the icons, a user may be able to connect a corresponding account. Connection of an account may require credential verification. It should be noted that although the example illustrated in FIG. 12(R) includes two social network services, in other examples, other social network services may be included. As a user adds/connects social media accounts, the list of accounts in FIG. 12(R) may be updated.

[00160] The GUI illustrated in FIG. 12(S) illustrates an example of a GUI implementing an import social pages feature. The GUI illustrated in FIG. 12(T) illustrates an example of a GUI implementing media import feature. The GUI illustrated in FIG. 12(T) may enable a user to populate a media library. The GUI illustrated in FIG. 12(U) represents an example of a GUI that may be presented upon success completion of the setup wizard.

[00161] In this manner, a computing device configured to present the graphical user interfaces illustrated in FIGS. 12(A) to 12(U), represents an example of a computing device configured to edit a resource associated with an entity's presence on at least one social networking site, and publish information about the resource to multiple locations associated with that entity's presence on said at least one social networking site.

[00162] FIGS. 12(V)-12(W) depict aspects of an exemplary graphical user interface

(GUI) supporting reporting according to embodiments hereof.

[00163] FIGS. 12(X)-12(Z) depict aspects of an exemplary graphical user interface (GUI) supporting campaigns according to embodiments hereof.

COMPUTING

[00164] The operations and acts shown and described above are implemented, at least in part, by the teamwork software, running on one or more computers or devices.

[00165] One of ordinary skill in the art will readily appreciate and understand, upon reading this description, that the various processes described herein may be implemented by, e.g., appropriately programmed general purpose computers, special purpose computers and computing devices. One or more such computers or computing devices may be referred to as a computer system (as noted above, FIG. 11 illustrates a typical computer system 1100). [00166] A computer system includes a processor 1102, main memory 1104, read-only memory (ROM) 1106 connected, e.g., by a bus 1108. As used herein, a "processor" means one or more microprocessors, central processing units (CPUs), computing devices, microcontrollers, digital signal processors, or like devices or any combination thereof, regardless of their architecture. An apparatus that performs a process can include, e.g., a processor and those devices such as input devices and output devices that are appropriate to perform the process.

[00167] A computer system 1100 may also include mass storage device 1110, removable storage media 1112, communication port 1114, and I/O port(s) 1116. The computer system 1100 may include one or more peripheral devices, including display screen 1118 and input device(s) 1120. The so-called peripheral devices may be integral with the computer system 1100 {e.g., in the case of a laptop computer or a tablet computer or a smart phone or the like). The input device(s) 1120 may be virtual devices {e.g., a virtual keyboard).

[00168] The program(s) described herein, including the presence management application

108 (with associated tools) will typically reside as programs in the memory/memories of one or more computer devices {e.g., as application(s) 1122-1).

[00169] Programs that implement such methods (as well as other types of data) may be stored and transmitted using a variety of media (e.g., computer readable media) in a number of manners. Hard-wired circuitry or custom hardware may be used in place of, or in combination with, some or all of the software instructions that can implement the processes of various embodiments. Thus, various combinations of hardware and software may be used instead of software only.

[00170] As used herein, the term "computer-readable medium" refers to any medium, a plurality of the same, or a combination of different media, which participate in providing data {e.g. , instructions, data structures) which may be read by a computer, a processor or a like device. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non- volatile media include, for example, optical or magnetic disks and other persistent memory. Volatile media include dynamic random access memory, which typically constitutes the main memory of the computer. Transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise a system bus coupled to the processor. Transmission media may include or convey acoustic waves, light waves and electromagnetic emissions, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.

[00171] Various forms of computer readable media may be involved in carrying data (e.g. sequences of instructions) to a processor. For example, data may be (i) delivered from RAM to a processor; (ii) carried over a wireless transmission medium; (iii) formatted and/or transmitted according to numerous formats, standards or protocols; and/or (iv) encrypted in any of a variety of ways well known in the art.

[00172] A computer-readable medium can store (in any appropriate format) those program elements that are appropriate to perform the method.

[00173] One of ordinary skill in the art will readily appreciate and understand, upon reading this description, that embodiments of an apparatus may include a computer/computing device operable to perform some (but not necessarily all) of the described process.

[00174] Embodiments of a computer-readable medium storing a program or data structure include a computer-readable medium storing a program that, when executed, can cause a processor to perform some (but not necessarily all) of the described process.

[00175] Where a process is described herein, those of skill in the art will appreciate that the process may operate without any user intervention. In another embodiment, the process includes some human intervention (e.g. , a step is performed by or with the assistance of a human).

[00176] Various features and aspects of the system operate in real time. Those of ordinary skill in the art will realize and understand, upon reading this description, that, as used herein, the term "real time" means near real time or sufficiently real time. It should be appreciated that there are inherent delays built in to the system (e.g. , based on network traffic and distances), and these delays may cause delays in data reaching various components. Inherent delays in the system do not change the real-time nature of the data. In some cases, the term "real-time data" may refer to data obtained in sufficient time to make the data useful.

[00177] Although the term "real time" has been used here, it should be appreciated that the system is not limited by this term or by how much time is actually taken for data to arrive at a location or to have any effect.

[00178] When an event is to occur at a particular time, it should be appreciated that the event may occur substantially at that particular time.

[00179] It should be appreciated that the words "first" and "second" in the description and claims are used to distinguish or identify, and not to show a serial or numerical limitation. Similarly, the use of letter or numerical labels (such as "(a)", "(b)", and the like) are used to help distinguish and / or identify, and not to show any serial or numerical limitation or ordering (temporal or otherwise).

[00180] As used herein, including in the claims, the phrase "at least some" means "one or more," and includes the case of only one. Thus, e.g., the phrase "at least some ABCs" means "one or more ABCs", and includes the case of only one ABC.

[00181] As used herein, including in the claims, the phrase "based on" means "based in part on" or "based, at least in part, on," and is not exclusive. Thus, e.g., the phrase "based on factor X" means "based in part on factor X" or "based, at least in part, on factor X." Unless specifically stated by use of the word "only", the phrase "based on X" does not mean "based only on X."

[00182] As used herein, including in the claims, the phrase "using" means "using at least," and is not exclusive. Thus, e.g., the phrase "using X" means "using at least X." Unless specifically stated by use of the word "only", the phrase "using X" does not mean "using only X."

[00183] In general, as used herein, including in the claims, unless the word "only" is specifically used in a phrase, it should not be read into that phrase.

[00184] As used herein, including in the claims, the phrase "distinct" means "at least partially distinct." Unless specifically stated, distinct does not mean fully distinct. Thus, e.g., the phrase, "X is distinct from Y" means that "X is at least partially distinct from Y," and does not mean that "X is fully distinct from Y." Thus, as used herein, including in the claims, the phrase "X is distinct from Y" means that X differs from Y in at least some way.

[00185] As used herein, including in the claims, a list may include only one item, and, unless otherwise stated, a list of multiple items need not be ordered in any particular manner. A list may include duplicate items. For example, as used herein, the phrase "a list of XYZs" may include one or more "XYZs".

[00186] Thus are described systems, methods and devices for social network presence management.

[00187] While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiments, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

Claims

WHAT IS CLAIMED: I claim:

1. A computer-implemented method, implemented at least in part on hardware, the method comprising:

(A) editing a resource associated with an entity's presence on multiple social networking sites; and

(B) publishing information about the resource to multiple locations associated with that entity's presence on said multiple social networking sites.

2. The method of claim 1 wherein said multiple locations are associated with multiple social networking sites, and wherein said publishing in (B) comprises:

publishing the information about the resource to said multiple locations on said multiple social networking sites.

3. The method of claim 1 wherein the multiple locations are associated with a single social networking site.

4. The method of claim 1 further comprising, prior to said editing in (A):

creating said resource.

5. The method of claim 4 wherein said resource comprises one or more of: a tab, a page, an image, a media file, text, and links.

6. The method of claim 1 wherein said editing of said resource comprises deleting said resource, and wherein said publishing in (B) comprises publishing information about deletion of the resource.

7. The method of claim 1 wherein the publishing in (B) causes said information to be broadcast to said at least one social networking site.

8. The method of claim 7 wherein the information is broadcast at a scheduled time.

9. The method of claim 7 wherein the information is broadcast in real time.

8. A framework supporting consistent presence management in social networks, the framework comprising a computer system comprising hardware and software and at least one database, said software operable on said hardware and comprising a presence management application including program code to:

(A) provide a graphical user interface (GUI); and

(B) use said GUI to perform the method of claim 1.

9. A tangible computer-readable non-transitory storage medium comprising instructions for execution on a device, wherein the instructions, when executed, perform acts of a method of claim 1.