US20130325632A1

Movatterモバイル変換

Info

Publication number: US20130325632A1
Application number: US13/962,867
Authority: US
Inventors: C. Douglass Thomas
Original assignee: Individual
Current assignee: Individual
Priority date: 2000-10-07
Filing date: 2013-08-08
Publication date: 2013-12-05
Also published as: US8521576B2; US20020062219A1

Abstract

Improved approaches to notifying others of publications are disclosed. These improved approaches enable notifications to be timely and reliably made. In one embodiment, a notifor requests notification of certain publications be performed in an automated and controlled manner, and then notifications for such certain publications are automatically prepared and electronically transmitted to one or more notifees.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 09/969,049, filed Oct. 1, 2001, and entitled “METHOD AND SYSTEM FOR PROVIDING NOTIFICATION OF PUBLICATIONS,” which is hereby incorporated herein by reference, which in turn claims priority benefit of U.S. Provisional Patent Application No. 60/238,565, filed Oct. 7, 2000, and which is hereby incorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to notifications and, more particularly, to methods and systems for notifying persons of certain publications.

2. Description of the Related Art

Today, publications occur frequently and often. As a result, it is difficult to manage and monitor those of the publications that are of interest. Conventionally, key word searches are performed to locate publications of interest. Recently, services have been available to periodically perform searches of publications and notify the requestor of the results (i.e., the matching publications). Such searches are used with trademark searches (i.e., trademark watching), patent searches (i.e., patent watching), or court opinion searches.

Beyond identification of publications through searches, notice of certain publications can have legal ramifications. The notification of others of the existence of these publications is normally performed one-by-one. Often these notifications are letters that are prepared and send by postal or courier mail service or facsimile. Hence, the conventional approaches to notifying others of publications is inefficient and relatively burdensome. Still further, these conventional approaches to providing notifications are often neglected such that no notifications are performed.

Thus, there is a need for improved approaches to notify others of publications.

SUMMARY

Broadly speaking, the invention relates to improved approaches to notifying others of publications. These improved approaches enable notifications to be timely and reliably made. In one embodiment, a notifor requests notification of certain publications be performed in an automated and controlled manner, and then notifications for such certain publications are automatically prepared and electronically transmitted to one or more notifees.

The invention can be implemented in numerous ways, including as a method, system, device, user interface, and computer readable medium. Several embodiments of the invention are discussed below.

As a computer-implemented method for notifying notifees of publications, one embodiment of the invention includes at least the acts of: identifying for a publication matching predetermined notification criteria; identifying an appropriate notifee to be notified of the publication matching predetermined notification criteria; preparing a notification message; and sending the notification message to the appropriate notifee.

As a computer-implemented method for notifying notifees of publications, one embodiment of the invention includes at least the acts of: identifying a publication; obtaining notification information pertaining to a notifor; identifying a notifee that is to be notified of the publication based on the notification information for the notifor; preparing a notification message; and transmitting the notification message to the notifee.

As a computer-implemented method for a notification system that notifies notifees of publications, one embodiment of the invention includes at least the acts of: identifying a publication; determining whether the publication is associated with a notifor that has previously provided notification information, including at least notification criteria and notifee information, to the notification system for notifications with respect to at least those publications associated with the notifor; and transmitting a first message to the notifor inviting the notifor to participate with the notification system when it is determined that the notifor has not previously provided notification information to the notification system. When it is determined that the notifor has previously provided notification information to the notification system, the embodiment of the invention further includes at least the acts of: identifying a notifee that is to be notified of the publication based on the notifee information; preparing a notification message; and transmitting the notification message to the notifee.

As a notification system, one embodiment of the invention includes at least a database for storing notification send criteria and notification sent data, and a notification server operatively connected to the database. The notification server operates to automatically send notifications of publications that satisfy the notification send criteria and to create the notification sent data pertaining to the notifications of publications.

As a computer readable medium including at least computer program code for notifying notifees of publications, one embodiment of the invention includes at least: computer program code for identifying a publication matching predetermined notification criteria; computer program code for identifying an appropriate notifee to be notified of the publication matching predetermined notification criteria; computer program code for preparing a notification message; and computer program code for sending the notification message to the appropriate notifee.

Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:

FIG. 1 is a block diagram of a notification system according to one embodiment of the invention.

FIG. 2 is a block diagram of a notification server according to one embodiment of the invention.

FIG. 3 is a flow diagram of basic notification processing according to one embodiment of the invention.

FIG. 4A is a flow diagram of notification management processing according to one embodiment of the invention.

FIG. 4B is a flow diagram of registration processing according to one embodiment of the invention.

FIG. 4C is a flow diagram of login processing according to one embodiment of the invention.

FIG. 4D is a flow diagram of notification set-up processing according to one embodiment of the invention.

FIG. 4E is a flow diagram of notification review processing according to one embodiment of the invention.

FIG. 5 is a flow diagram of detailed notification processing according to one embodiment of the invention.

FIG. 6 is a flow diagram of notification processing according to one embodiment of the invention.

FIG. 7 is a flow diagram of notification message send processing according to one embodiment of the invention.

DETAILED DESCRIPTION

The invention relates to notifying others of publications. These improved approaches enable notifications to be timely and reliably made. In one embodiment, a notifor requests notification of certain publications be performed in an automated and controlled manner, and then notifications for such certain publications are automatically prepared and electronically transmitted to one or more notifees.

Embodiments of this aspect of the invention are discussed below with reference toFIGS. 1-7. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments.

FIG. 1 is a block diagram of anotification system100 according to one embodiment of the invention. Thenotification system100 includes anotifor machine102 that interacts with anotification server104 through the Internet106. The Internet106 is a network of interconnected computers. Thenotifor machine102 is a computing device that couples to the Internet106. In one embodiment, thenotifor machine102 couples to the Internet106 through an Internet Service Provider (ISP). Thenotification server104 also couples to the Internet106. Thenotification server104 is a computer system, referred to as a server or web server.

Thenotification system100 also includes anotifee A machine108 and anotifee B machine110. The

notifee machines

108 and110 are computing devices that couple to theInternet106. Thenotification system100 operates to automatically notify one or more notifees via the

notifee machines

108 and110. Thenotification server104 provides such notifications to the appropriate notifees based on instructions provided by thenotifor machine102 to thenotification server104. Thenotification server104 also interacts with adatabase112 such that the automatic notifications can be sent to the appropriate notifees. Typically, the notifications to particular notifees are requested by particular notifors.

Although thenotification system100 uses theInternet106 to provide data transfer, it should be understood that other data networks (wired or wireless) can likewise be used. The data transfer can also be achieved through various different interconnected networks.

FIG. 2 is a block diagram of anotification server200 according to one embodiment of the invention. Thenotification server200 is, for example, a representative detailed embodiment of thenotification server104 illustrated inFIG. 1.

Thenotification server200 includes anHTTP server202 that couples to a network (e.g., the Internet106) via acommunication link204. TheHTTP server202 can interact with a registration/log-inmanager206, a notification set-upmanager208, and anotification manager210. The registration/log-inmanager206 operates to facilitate either the registration or log-in of a particular user to the notification system. The user can, for example, be a notifor or a notifee. The notification set-upmanager208 is primarily utilized by a notifor to set up the particular types of notifications they desire to automatically deliver to particular notifees. Thenotification manager210 operates to identify when and what notifications need to be delivered and then operates to deliver the notifications to appropriate notifees.

In one embodiment, the notifications pertain to certain publications. Notifors often desire to have notifees informed of such publications. Thus, the notification system can automatically notify notifees of publications (e.g., often the publications are associated with the notifors). The notification system documents the notifications and provides historical or archive type storage for prior notifications. Typically, the registration/log-inmanager206, the notification set-upmanager208, and thenotification manager210 store data to and retrieve data from a database (database112 inFIG. 1).

FIG. 3 is a flow diagram ofbasic notification processing300 according to one embodiment of the invention. Thebasic notification processing300 is, for example, performed by thenotification server104 illustrated inFIG. 1 or thenotification server200 illustrated inFIG. 2.

Thebasic notification processing300 initially establishes302 notification criteria for a notifor. The notification criteria, for example, identifies particular notifees or categories of industry that are to be notified when particular documents become published. Examples of categories of industry are: computer manufacturers; microprocessor companies; integrated circuit processing equipment companies; disk drive manufacturers; toy companies; bicycle manufacturers; semiconductor memory companies; oil companies; pharmaceutical companies; etc. The categories of industry can be predetermined or can be provided or established by a notifor.

Next, asearch304 is performed to identify one or more publications that match the notification criteria. For example, in one embodiment, the notification criteria might indicate that certain published U.S. patent applications of the notifor are to be selected. After the one or more publications that match the notification criteria have been identified, appropriate notifees to be notified are identified306. Typically, the notification criteria also indicates, or can be used to identify, the appropriate notifees. The appropriate notifees can be specific businesses or entities, can be specific individuals of businesses or entities, or can be those businesses or entities (or specific individuals therein) within an industrial group (category of industry). In general, the appropriate notifees can be specifically identified or can be associated with a selected category of industry. For example, if one or more categories of industry are indicated in the notification criteria, then the appropriate notifiees can include those companies (namely, identified representatives therefor) associated with the one or more categories of industry.

After the appropriate notifees have been identified306, a notification message is prepared308. The notification message that is prepared308 can be the same or can be different for the different ones of the appropriate notifees. In one embodiment, the type of notification message can be selected by the requesting notifor. In any case, assuming that the notification message is substantially the same for each of the appropriate notifees (which need not be the case), the notification message is then sent310 to the identified notifees.

After the notification message has been sent, the notification message can be archived312. By archiving the notification message, the notification server can log the sending of the message to the appropriate notifees such that the information regarding the sending of the notification messages (and optionally their receipt) can be subsequently retrieved. This provides a means to later prove that a notification message was sent and/or received.

FIG. 4A is a flow diagram ofnotification management processing400 according to one embodiment of the invention. Thenotification management processing400 is, for example, performed by thenotification server104 illustrated inFIG. 1 or thenotification server200 illustrated inFIG. 2.

Thenotification management processing400 begins with adecision402 that determines whether a registration request has been received. Here, the notification server can receive various types of requests from users (e.g., notifors). When adecision402 determines that a registration request has been received, aregistration processing404 is performed. On the other hand, when thedecision402 determines that a registration request has not been received, then adecision406 determines whether a login request has been received. When thedecision406 determines that a login request has been received, then login processing408 is performed.

Alternatively, when thedecision406 determines that a login request has not been received, then adecision410 determines whether a notification set-up request has been received. When thedecision410 determines that a notification set-up request has been received, then notification set-upprocessing412 is performed. Alternatively, when thedecision410 determines that a notification set-up request has not been received, then adecision414 determines whether a notification review request has been received. When thedecision414 determines that a notification review request has been received, thennotification review processing416 is performed.

Following thedecision414 when a notification review request has not been received, as well as following the

operations

404,408,412 and416, thenotification management processing400 then returns to repeat thedecision402 and subsequent operations so that the notification server is continuously available to receive various different requests and process those requests as required.

FIG. 4B is a flow diagram ofregistration processing420 according to one embodiment of the invention. Theregistration processing420 details the operations performed by theregistration processing404 illustrated inFIG. 4A.

Theregistration processing420 initially sends422 a registration page to a requestor. The requestor is, for example, a notifor or a notifee seeking to register for use of the notification system. Then, adecision424 determines whether a registration submission has been received. When adecision424 determines that a registration submission has not yet been received, thedecision424 causes theregistration processing420 to await such a submission. Once thedecision424 determines that a registration submission has been received, the requestor is registered426 with the notification system. After the requestor has been registered426 with the notification system, a registration confirmation page is sent428 to the requestor. Following theoperation428, aregistration processing420 is complete and ends.

FIG. 4C is a flow diagram oflogin processing440 according to one embodiment of the invention. Thelogin processing440 details the operations performed by thelogin processing408 illustrated inFIG. 4A.

Thelogin processing440 initially sends442 a login page to a requestor. The requestor is, for example, a notifor or a notifee seeking to utilize the notification system. Then, adecision444 determines whether a login submission has been received. When thedecision444 determines that a login submission has not yet been received, thelogin processing440 awaits such a submission. Once thedecision444 determines that a login submission has been received, login parameters provided with the login submission are verified446. Here, the login parameters are verified against previously stored information at the notification server. For example, login parameters might include a user name and password that are previously assigned and stored in a database associated with the notification server during a registration process. Hence, during the login verification, the login parameters provided with the login submission can be verified against the previously stored values within the database.

In any event, after the login parameters are verified446, adecision448 determines whether the login verification was successful. When thedecision448 determines that the login verification was successful, then an initial page is sent450 to the requestor, thereby providing the requestor with access to restricted areas (e.g., web pages) of the notification server. Alternatively, when thedecision448 determines that the login request was not successful, then a login denied page is sent452 to the requestor. Following theoperation450 and theoperation452, thelogin processing440 is complete and ends.

FIG. 4D is a flow diagram of notification set-upprocessing460 according to one embodiment of the invention. The notification set-upprocessing460 details the operations performed by the notification set-upprocessing412 illustrated inFIG. 4A. The notification set-upprocessing460 assumes that the requestor is already properly logged in.

FIG. 4E is a flow diagram ofnotification review processing480 according to one embodiment of the invention. Thenotification review processing480 details the operations performed by thenotification review processing416 illustrated inFIG. 4A. Thenotification review processing480 assumes that the requestor is already properly logged in.

Thenotification review processing480 initially identifies482 archived notifications sent for the requestor. The requestor is a notifor that is access the notification system to retrieve and view the notifications that have been provided by the notification system on their behalf. Typically, the archived notifications are retrieved from a database, such as thedatabase112 shown inFIG. 1. Next, a notification review page is formed484. Then, the notification review page is sent486 to the requestor. Following theoperation484, thenotification review processing480 is complete and ends.

FIG. 5 is a flow diagram ofdetailed notification processing500 according to one embodiment of the invention. Thedetailed notification processing500 is, for example, performed by thenotification server104 illustrated inFIG. 1 or thenotification server200 illustrated inFIG. 2. Thedetailed notification processing500 can be performed periodically or after pertinent publication events.

Thedetailed notification processing500 initially selects502 a notifor. Then, notification criteria for the selected notifor is obtained504. Then, asearch506 for those publications that match the notification criteria is performed. Adecision508 then determines whether one or more matching publications have been identified by thesearch506. When thedecision508 determines that one or more matching publications have been identified, then a matching publication is selected510. Then, notifee information is then determined512. Among other things, the notifee information can identify one or more notifees that are to be notified with respect to a matching publication.

Next, one of the notifees is selected514. After the notifee is selected514, notification information for the selected notifee is obtained516. As an example, the notification information for the selected notifee can indicate how the selected notifee is to be notified. For example, for the selected notifee, the notification information could provide the notification type, the electronic mail address, and name, title and associated organization. A notification message is then generated518. Typically, the notification message that is generated518 would be customized at least with respect to the information pertaining to the selected matching publication. As noted previously, different notifees can also receive different types of messages. The notification message is then sent520 to the selected notifor. Typically, the notification information provides the electronic mail address of the selected notifee such that the notification message can be sent520 electronically to the selected notifee as an electronic mail message. After the notification message has been sent520, the notification message is archived522. In one embodiment, the sent notification messages can be archived in a database associated with the notification server.

Next, adecision524 determines whether there are more notifees that are to be notified with respect to the selected matching publication. When thedecision524 determines that there are more notifees to be notified, then thedetailed notification processing500 returns to repeat theoperation514 and subsequent operations for a next notifee.

Alternatively, when thedecision524 determines that there are no more notifees for the selected matching publications, adecision526 determines whether there are more matching publications to be processed. When adecision526 determines that there are more matching publications to be processed, thedetailed notification processing500 returns to repeat theoperation510 and subsequent operations for a next matching publication.

On the other hand, once thedecision526 determines that there are no more matching publications to be processed, thedetailed notification processing500 performs adecision528. Additionally, when thedecision508 determines that there are no matching publications, thedetailed notification processing500 also performs thedecision528. In any case, thedecision528 determines whether there are more notifors to be processed. When the decision determines that there are more notifors to be processed, then thedetailed notification processing500 returns to repeat theoperation502 and subsequent operations so that other notifors can be similarly processed. However, once thedecision528 determines that there are no more notifors to be processed, thedetail notification processing500 is complete and ends.

FIG. 6 is a flow diagram ofnotification processing600 according to one embodiment of the invention. Thenotification processing600 is, for example, performed by thenotification server104 illustrated inFIG. 1 or thenotification server200 illustrated inFIG. 2. Thenotification processing600 can be performed periodically or after pertinent publication events.

Thenotification processing600 begins with adecision602 that determines whether a new publication for an owner is available. Owner refers, for example, to title holder, author or editor. When thedecision602 determines that a new publication is not available at this time, then thenotification processing600 awaits the availability of such a new publication. On the other hand, once thedecision602 determines that a new publication is available, thenotification processing600 continues. In effect, thenotification processing600 begins when a new publication becomes available.

When thenotification processing600 does continue, adecision604 determines whether the owner of the publication is a member. Here, members are those businesses or individuals that are registered for notification service. In this embodiment, the owner has requested notification service of its publications. However, in general, third-party (i.e., non-owners) could also request notification service of publications of others in other embodiment. In any case, when thedecision604 determines that the owner is not a member, then thenotification processing600 can send606 the owner a message inviting their utilization of the notification service. In one implementation, the message sent to the owner is an electronic mail message advising them of their new publication and offering to provide notification services.

Alternatively, when thedecision604 determines that the owner is a member, then thenotification processing600 obtains608 notification criteria for the owner. The notification criteria specifies the criteria which determines which publication and which notifees are to be notified. In one embodiment, the notification criteria is obtained and stored through a registration or notification request process. Next, adecision610 determines whether there are any notifees for the new publication. When thedecision610 determines that there are one or more notifees that are to be notified of the new publication, a notification message is prepared, sent and archived612. On the other hand, when thedecision610 determines that there are no notifees, then the operation613 can be bypassed. Following theoperation612 as well as thedecision610 when there are no notifees, thenotification processing600 returns to repeat thedecision602 and subsequent operations so that other new publications can be similarly processed.

Theoperation612 ofFIG. 6 can be implemented in a variety of ways. Typically, the message is an electronic message that is automatically prepared and electronically transmitted (i.e., electronic mail) to one or more notifees and then electronically archived. Documentation or evidence that the message was sent, delivered and confirmed can also be archived. The message can alternatively be electronically sent as a facsimile.

FIG. 7 is a flow diagram of notification message send processing700 according to one embodiment of the invention. The notification message send processing700 can, for example, represent processing associated with one embodiment of theoperation612 ofFIG. 6. The notification message send processing700 can be used in place of operations516-522 ofFIG. 5.

The notification message send processing700 begins with adecision702 that determines whether a pre-notification authorization is required. When thedecision702 determines that a pre-notification authorization is required, an authorization message is prepared and sent704 to the member. Pre-notification authorization means that the notifor has requested (e.g., when registering) that the notifor be informed prior to sending out a notification message. Here, the authorization message permits the notifor to permit or decline the sending of the notification message to the notifee. The authorization can optionally also enable the notifor to preview the notification message before it is sent. Next, adecision706 determines whether authorization has been is received. The authorization is, for example, a reply to the authorization message. In one implementation, the authorization message is an electronic mail message and the authorization is a reply to that electronic mail message. As another example, the authorization could be the notifor interacting with the notification server to provide the authorization. In one implementation, the electronic mail message could include a link (e.g., active link or hyperlink) to the notification server to facilitate the acquisition of the authorization. In any case, the authorization may take minutes, hours or days to be received following the sending the authorization message. Hence, the processing for this publication can wait for the authorization and then continue once received.

When thedecision706 determines that authorization has been received as well as following thedecision702 when no pre-authorization is required, notification information for the one or more notifees to receive the message is obtained708. One or more notification messages are then prepared710. Next, the one or more notification messages are sent712. In one implementation, the notification messages are sent as electronic mail messages. In an alternative implementation, the notification messages can be sent as facsimiles. After the one or more notification messages are sent712, the notification messages are archived714. Additionally, any delivery confirmation can also be archived714. For example, the delivery confirmation can be an indication that the notification message was received, an indication that the notification message was opened, or a reply to the notification message. Also, when thedecision706 determines that authorization is denied, then operations708-714 are bypassed as notification message are not to be sent.

The notification messages utilized by the invention are generally predetermined but can also be customized by notifors. The different types of messages can provide notifors with an opportunity to use different messages in different situations. The notification messages can contain an active link to the publication. For example, the active line can be a hyperlink that, when selected, retrieves and displays the publication for the requestor (e.g., notifee). The notification messages can also contain active links to license information, an analysis of the publication in general or with respect to the notifee, or other documentation or presentations. The requesting notifor can be anonymous or identified in the notification messages.

The notification types can vary with implementation. In one embodiment, in which the publications are patent related, the notification types can include: (i) a mere patent information, (ii) patent information and license offer (non-aggressive), (iii) patent information and license offer (aggressive), and (iv) cease and desist infringement. Hence, the content or text of these notifications will vary with type. As an example, a notification of the “mere patent information” type might state the following:

You are hereby notified of U.S. patent application Ser. No. ______, which was published on [month, day, year], and thereby now enjoys provisional rights. The text of the published application can be obtained from various sources, including by selecting the following link to published application.

For Licensing opportunities, click here.

Here, this exemplary message includes not only the notification message to inform the recipient of the patent publication, but also optionally includes a hyperlink to the publication document and a hyperlink to access licensing information.

The invention provides notification of publications in an automated, computer-implemented way. The publications can be of various types. Some examples of particularly useful publications include published patent application and issued patents. The notification of these patent-related publications have legal consequences. Accordingly, the ability to affect notification in a reliable and automated way is a welcome advance to the state of the art.

The notification system according to one embodiment of the invention operates in a client-server environment. The clients are notifors or notifees, or their machines or network browsers operating on their machines. Typically, the notifor interacts with a network browser operating on a computing device to in turn interact with the notification server. The information provided to the notifor is then often a markup language document or page (e.g., web page). Notifees typically only need to access a computing device to receive electronic mail. The notifor may also need access to electronic mail.

The invention is preferably implemented in software, but can be implemented in hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can be thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, magnetic tape, optical data storage devices, carrier waves. The computer readable medium can also be distributed over a network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

The advantages of the invention are numerous. Different embodiments or implementations may yield one or more of the following advantages. One advantage of the invention is that notifications of publications can be efficiently scheduled and carried-out. Another advantage of the invention is that notifications that are performed are documented. Still another advantage of the invention is that it is network-based so that access is available whenever network access is available.

The many features and advantages of the present invention are apparent from the written description and, thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be deemed limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.

Claims

What is claimed is:

1. A non-transitory computer readable medium including at least executable computer program code stored thereon for notifying notifees of publications, said computer readable medium comprises:

computer program code for obtaining predetermined notification information associated with a notifor to be utilized in notifying one or more particular notifees, the predetermined notification information includes notification criteria that serves to identify those publications of the notifor that are to be delivered to the one or more particular notifees, and the predetermined notification information further includes or serves to electronic mail addresses for the one or more particular notifees;

computer program code for automatically determining whether a publication of the notifor matches the predetermined notification criteria;

computer program code for determining, based on the predetermined notification criteria, an appropriate notifee to be notified of the publication matching the predetermined notification criteria, the appropriate notifee being one of the one or more particular notifees;

computer program code for sending an authorization request to the notifor;

computer program code for preparing an electronic notification message, the electronic notification message including or referencing the publication matching the predetermined notification criteria; and

computer program code for sending the electronic notification message to the appropriate notifee using the electronic mail address corresponding to the appropriate notifee if said computer program code for determining determines that the appropriate notifee is to be notified of the publication matching the predetermined notification criteria,

wherein said computer program code for sending the electronic notification message is performed only after receiving from the notifor an indication of authorization for the notification message to be sent.