Electronic devices such as eBook readers (“eBook readers”), cellular telephones, portable media players, tablet computers, netbooks, desktop computers, and the like may display digital content such as eBooks (“eBooks”) or other electronic media content to a user. Given the incredible growth in the availability of digital content and variability of formatting, it can be cumbersome to determine where transitions occur between sections of a book, such as front matter, body matter, and back matter.
The detailed description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items.
Digital content continues to proliferate in terms of the volume of content being created, the numbers of devices that can play digital content, and the numbers of users who are accessing and consuming digital content. Digital content may include eBooks, video, multimedia presentations, audio, and so forth. Users are accustomed to particular presentations of different types of content, which may vary according to the type of content. For example, songs on an album may be segregated into separate tracks, video may have scenes, a book may have front matter, body matter including chapters, back matter, and so forth. Providing an expected presentation to a user increases user satisfaction and encourages consumption of digital content.
Given the growing body of digital content offered by a large number of publishers and put forth by a larger number of authors, formatting of digital content to a uniform standard suitable for presentation is a challenge. This challenge is further exacerbated by a growing trend of self-publication. Individual publishers or authors may omit, or incorrectly add, breaks between sections. Proper breaks between sections provide a presentation which is expected by the user, while also providing information suitable for analysis. For example, it may be useful to a publisher to realize that a large number of users are accessing back matter, in order to determine whether an update to the section is desired for a new edition.
Described in this application are techniques and systems suitable for determining breaks or transitions between sections of digital content, and formatting the digital content with tags indicating these breaks. Content may be received from an author, publisher, or other originating entity at a content server. A content processing module within the content server analyzes the content to determine the position of transitions from one section to another. For example, in an eBook, the content processing module may determine the position of breaks between front matter to body matter, and body matter to back matter. In other implementations, other portions of the content may be determined and identified, such as chapters, indices, bibliographies, and so forth.
Once these breaks are identified, formatting may be generated. This formatting may include the creation of tags which are associated with the position at which a break has been identified, or for a determined interval of the content. Tags may include entries using hypertext markup language (HTML) tag, extensible markup language (XML), programming script, plain text of pre-determined parameters, and so forth. Tags may be associated with the position either by placement inline with the content, be placed within a file separate from the content, or a combination of the two. For example, a formatting file may contain the location within the content of one or more breaks.
In one implementation, the content processing module may generate the formatted content from the original content automatically, that is, without any human intervention. This processing may include identifying keywords, using last position read, analyzing changes in formatting, analyzing changes in reading speed, and so forth.
In other implementations, processing of the content may incorporate human users to assess an automatically generated preliminarily formatted content. For example, humans may approve or modify an automatically generated break showing an end-of-body matter. These humans may either be users, such as those reading the book, or analysts who are confirming the automated formatting.
While content processing is described in the context of textual content, the concepts described herein are also applicable to processing of other digital content, such as multimedia, audio, video, and so forth. Also, while processes are described as being implemented using eBook reader devices, digital content may be processed for display on other devices, such as cellular telephones, portable media players, tablet computers, netbooks, notebooks, desktop computers, and the like.
Content Processing Architecture
An author 102, or other originating entity such as a publisher, may use an electronic device 104 to transfer original content 106 via network 108 to one or more content servers, such as the illustrated content servers 110(1)-(S). The electronic device 104 may be embodied in any number of ways, including as a desktop computer, laptop, server, smartphone, eBook reader device, and so forth. In
The original content 106 may include any form of digital content, such as a multimedia item or an eBook. This original content 106 may include some formatting, but may in some cases be lacking specific formatting tags or indicators which are usable during the presentation of the eBook. For example, the original content 106 may comprise an eBook with line breaks and italic fonts, but lack a definitive machine-readable tag recognized by the eBook reader 104 indicating the conclusion of body matter.
The network 108 may be implemented as one or more various networks, such as the Internet, a cable television network, wireless network, wired network, wireless wide area network, and so forth. The content servers 110(1)-(S) may comprise a single server, cluster of servers, data center, and so forth.
At the content servers 110, a content processing module 112 processes the original content 106. Among the various tasks performed by the content processing module 112, it determines positions within the original content 106 which correspond to breaks or transitions between sections. A number of different techniques are described more fully below with reference to
In some implementations, the preliminarily formatted content 114 may be presented to a human for approval or modification. As shown here, the preliminarily formatted content 114 is delivered via the network 108 to an analyst 116. The analyst 116 views the presented preliminarily formatted content 114, and may approve the automatically generated formatting or modify it. Approval or modification then results in formatted content 118. The content servers 110 may then distribute formatted content 118 via the network 108 to users 120. Thus, the users 120 view the formatted content 118 which is suited for presentation on their devices 104.
A digital content database 206 and a customer database 208 are stored in the memory 204. The digital content database 206 comprises digital content, for example music, books, movies, and so forth. Digital content may include original content 106, preliminarily formatted content 114, and formatted content 118. Digital content may be accessed in common. That is, each user with access to a particular content may access a common copy of that content, or each user may access his or her own discrete copy of content stored in a digital locker. The customer database 208 is accessible by the processor 202 for use in distributing content from the digital content database 206. The customer database 208 comprises information about users participating in the community, access rights to content, and so forth.
The content processing module 112 is also present within memory 204 and accesses the digital content database 206. As described above, the content processing module 112 is configured to analyze the content 106 to make determinations such as the position of transitions from one section to another.
The content server 110 is in communication with a client 210, which may represent any one of the devices 104 shown in
Front matter is the first section of a book, and may contain initial material such as a table of contents, foreword, preface, acknowledgement, introduction, dedication, prologue, and so forth. Front matter may have formatting different from other sections such as the body matter. For example the page numbers in front matter may be lowercase roman numerals.
Body matter is the core of the book, and contains the materials that are typically of greatest interest to the reader, for example, the story. The particular formatting of the body matter may vary with the type of work, for example, compare the formatting of a novel with a dictionary. The novel is primarily text with perhaps line and paragraph breaks, while the dictionary may have a more complicated indentation, italicization, and so forth. Regardless, within the body section, the formatting is generally consistent.
Body matter may include subsections, such as chapters, parts, and so forth. Consistently incrementing inline text, for example “Chapter 1,” “Chapter 2,” and so forth may delineate breaks between subsections. Often, but not always, body matter may conclude with a particular word or phrase. For example, in English books keywords such as “the end,” “conclusion,” or “fin,” and so forth may indicate the conclusion of a section. Presence of other text such as line breaks before and after the keyword may also be considered.
In some implementations, the capitalization or case of these phrases may be considered. For example, “The End” or “THE END” may be considered a keyword, while “the end” does not, to avoid determination of false breaks. As above, presence of other text such as line breaks before and after the keyword may also be considered.
Back matter may be present, and may include appendices, glossaries, bibliographies, indices, and so forth. In some implementations, back matter may also include an epilogue, afterword, conclusion, postscript and so forth. The content processing module 112 may automatically, or with the input from the analyst 116 determine whether portions such as the epilogue, afterword, conclusion, postscript and so forth are to be included within the body matter or the back matter of a particular eBook. As shown in
Within the body matter 302 may be seen a final passage 306 of the text of the eBook. Inline text 308 is text which is part of the content. Here, inline text 308 includes the phrase “THE END” which may be used at least in part to determine an end of the body section 302.
A page break tag 310 is also shown. Tags, including the page break tag 310, may be configured to affect the presentation of the content, but may not be presented to the user. For example, the user may not see the text “</PAGE_BREAK>” or similar tag but may see the user interface presented which is associated with the page break. Tags may be inline with the text, or separate and associated with a particular position within the file.
The content may include titles 312, such as “AFTERWORD” which is shown here. Titles may be distinguished based upon capitalization, formatting, as well as their correspondence to previously determined keywords. For example, titles may include the keywords “CHAPTER,” “FOREWORD,” “EPILOGUE,” and so forth.
In some implementations, a manual end marker tag 314 may be present. The author 102, a publisher, typesetter, or other entity may insert this manual end marker tag 314 prior to submission to the content servers 110. As above, the user may not see the text “</END_BODY_TEXT>” or similar tag but may instead see the user interface associated with presentation of an end of the book. The placement of the manual end marker tag 314 may reflect the intention of the author 102 to change the location of breaks between the sections. For example, as shown in this illustration, the manual end marker tag 314 is positioned after the conclusion of the afterword text. This is at variance with conventional book design, in which the afterword is usually considered a part of back matter, and not the body matter.
Also illustrated here are reference indicators 316, such as specific formatting, character strings and types of strings which may indicate particular types of material. For example, as shown here, the reference indicators 316 may include the text “Chapter 1” and “p.” text used to denote pages, and so forth. These reference indicators 316 may be used to determine sections within the content. Comparison between the reference indicators 316 may be used to disambiguate sections. For example, in the “ENDNOTES” as shown, chapters are delineated with subsequent endnote entries. A determination that the phrase “Chapter” occurs with increasing numbers may result in an erroneous conclusion that the endnotes are part of the body matter 302. To avoid this, a pre-determined threshold distance may be used. For example, when the reference indicators 316 are within a pre-determined threshold distance of 400 characters of one another, the portion is not body matter 302.
Citation text 318 is shown, which conforms to pre-determined citation formats. The presence of citation text 318 may be used to designate sections of text. For example, a plurality of citation text 318 entries, separated by line breaks and proximate to one another, may indicate a listing of citations in a bibliography, such as shown here.
Sections may also be distinguished by analyzing specific formatting 320, such as that shown with a table in an index, table of contents, and so forth. Here, we have a short string of text followed by a comma and a number. This may be analyzed and recognized as an index. In some implementations, this determination may be checked by searching the body matter. For example, a search of the work at page 239 which indicates that the word “Defarge” is present would confirm that the text in this format is likely an index.
Determination of End of Section
Several processes are described below, including those shown in
At 404, an end-of-body position within the content is determined based at least in part upon data within the received original content. The data within the received original content may be structural data, such as formatting, page layout, tags, and so forth. The data within the received original content includes substance such as text in an eBook, audio, video, and so forth. As described below in more detail with regards to
At 406, content is formatted with an end-of-body tag associated with the determined end-of-body position of the content. As described above, this tag may be incorporated into the content, or associated with the content in a formatting file.
At 408, the formatted content 118 is provided to the user 120. The user 120, upon accessing the formatted content 118, is thus presented with section breaks, and a clear indication of where within the eBook the determined of the body matter 302 is via appropriate formatting.
Once scanned, at 504, the one or more of the end-of-body keywords are identified. At 506, a position within the content proximate to the keywords is designated as an end-of-body position. This position may be relative to the type of break being designated and the specific keyword. For example, a position following the keyword “THE END” may be associated with the conclusion of body matter 302, while a position before the keyword “FOREWORD” may be associated with a beginning of front matter.
At 508, an end-of-body tag associated with the designated end-of-body position is generated. As described above, this end-of-body tag may be inline with the content, or external to it, such as in a separate formatting file. The association between the designated position and a given command may be accomplished by using an invariant reference to the text. For example, the end-of-body position may be designated as occurring after the 387th line break, at byte count 557,179, and so forth.
As shown here, the usage of the eBook content by each of the plurality of users A-G has been gathered. When the user ceases to access the content, deletes the content from their device 104, or another action, the content processing module 112 may designate the position at which the user left off as the last position read 602. For example, as shown here, user A has a last position read of position 7 corresponding to the word “END.”
By analyzing distribution of last positions read within the content, a computed last position read (CLPR) may be determined. For example, the last position read 602 for a majority of the users A-G was position 10, which is thus the computed last position read (CLPR) 604. As shown here, position 10 corresponds to the conclusion of the “Afterword” in the sample of
At 704, the CLPR is designated as the end-of-the-body position. For example, as described above, the conclusion of the “afterword” may be considered the end of the body matter, at least by the users. In some implementations, such as described below with regards to
At 706, as described above, an end-of-body tag is generated which is associated with the designated end-of-body position. This tag may then be used to affect presentation of the content to the user.
At 804, the one or more portions containing an indication of transition are identified, such as formatting consistent with back matter. For example, a transition from regular unjustified text to a portion of text formatted into a table may indicate a transition from body text to an index of the eBook. This portion of the text with the formatting may be designated a portion of a particular section, such as the back matter 304.
At 806, an end-of-body position is designated prior to the start of the one or more portions containing formatting associated with the back matter. For example, the body matter 302 comes before the index in the back matter 304, thus the end-of-body position is designated at a point in the eBook before the position where the index has been determined. At 808, an end-of-body tag associated with the determined end-of-body of the content is generated.
In some implementations, a plurality of users may also be monitored, with the results generating a distribution of user speed. This distribution from the plurality of users may in turn be used to determine an overall change in reading speed by a population of users.
At 904, changes of the reading speed beyond a pre-determined threshold are determined. The pre-determined threshold may be a maximum, a minimum, or a bounded region. For example, the threshold may designate a minimum reading speed of 100 words per minute, and the user may have dropped to 50 words per minute at a given position.
At 906, a position where the reading speed changed beyond the pre-determined threshold is designated as an end-of-body position. For example, as described above, the abrupt decrease in reading speed may indicate the user is more slowly progressing through less readable back matter, such as end notes. At 908, an end-of-body tag associated with the determined end-of-body position is generated.
At 1002, breaks are automatically determined, such as a preliminary end-of-body position. This preliminary position, is combined with the original content 106 to form the preliminarily formatted content 114.
At 1004, the preliminarily formatted content 114 is presented to one or more of the human analysts 116(1)-(A). The analyst 116 views the preliminarily formatted content 114 and determines whether the automatically determined break is correct. The analyst 116 then confirms or modifies the automatically determined break.
At 1006, the confirmation or modification is received from the analyst 116. At 1008, based at least in part upon the analyst's 116 input, a tag such as an end-of-body tag associated with the determined end-of-body position is generated.
Also presented by the device 104 is a user prompt 1104 asking the user 120 “Is the cursor at the end of the book?” and seeking a yes or no response. The user may thus respond, and the content processing module 112 may use the response to add, confirm or modify the end-of-book tag.
In some implementations, the content processing module 112 may vary the position of a break, and present the results to a plurality of users. By assessing the responses from a plurality of users, the content processing module 112 may determine where the actual section break, such as an end-of-body is.
At 1204, the user responses are received. These users responses may be analyzed to look for trends and distributions. For example, some users may misinterpret a prompt, intentionally enter erroneous data, and so forth. However, the overall distribution of positions associated with a section break should typically indicate the actual section break.
At 1206, as above, an end-of-body tag associated with the position indicated by a number of users is generated. In some implementations, a pre-determined threshold of a count of users may be set, which would require that the threshold number of users must agree on a position for the position to be considered a break.
At 1302, an estimated end-of-body position (EOBP) is determined based at least in part upon a last position read or a computed last position read. This may be from one or a plurality of users.
At 1304, when the estimated EOBP is within a pre-determined threshold distance of a content start point, at 1306 the estimated EOBP is discarded. The content start point comprises the beginning of the content, such as the first word on the first page of a book. This check prevents the placement of the end-of-body position at or close to the beginning.
When at 1304 the estimated EOBP exceeds the pre-determined threshold distance of a content start point, then the process proceeds to 1308. At 1308, when the estimated EOBP exceeds a pre-determined threshold distance from a previously determined EOBP, the process proceeds to 1306 and discards the estimated EOBP. When at 1308 the estimated EOBP is within the pre-determined threshold distance from a previously determined EOBP or no previous EOBP exists, then the process proceeds to 1310. When at 1310 the content does not include page or other internal breaks, the process proceeds to 1312. At 1312, an end-of-body tag associated with the estimated EOBP is generated.
Returning to 1310, when the content includes internal breaks the process proceeds to 1314. At 1314, when one or more internal breaks are within a pre-determined threshold distance of the estimated EOBP, the process proceeds to 1312 to generate the end-of-body tag associated with the estimated EOBP. When at 1314 the one or more internal breaks exceed the pre-determined threshold distance to the estimated EOBP, the process proceeds to 1306 and discards the estimated EOBP.
Although specific details of illustrative methods are described with regard to the figures and other flow diagrams presented herein, it should be understood that certain acts shown in the figures need not be performed in the order described, and may be modified, and/or may be omitted entirely, depending on the circumstances. As described in this application, modules and engines may be implemented using software, hardware, firmware, or a combination of these. Moreover, the acts and methods described may be implemented by a computer, processor or other computing device based on instructions stored on one or more computer-readable storage media.
Number | Name | Date | Kind |
---|---|---|---|
5663748 | Huffman et al. | Sep 1997 | A |
5697793 | Huffman et al. | Dec 1997 | A |
5743746 | Ho et al. | Apr 1998 | A |
6098064 | Pirolli et al. | Aug 2000 | A |
6544294 | Greenfield et al. | Apr 2003 | B1 |
6584480 | Ferrel et al. | Jun 2003 | B1 |
6853982 | Smith et al. | Feb 2005 | B2 |
6947922 | Glance | Sep 2005 | B1 |
6963848 | Brinkerhoff | Nov 2005 | B1 |
7103848 | Barsness et al. | Sep 2006 | B2 |
7315826 | Guheen et al. | Jan 2008 | B1 |
7490045 | Flores et al. | Feb 2009 | B1 |
7545398 | Sawada | Jun 2009 | B2 |
7552068 | Brinkerhoff | Jun 2009 | B1 |
7636677 | McGonigal et al. | Dec 2009 | B1 |
8046272 | Nguyen | Oct 2011 | B1 |
8103665 | Abbott et al. | Jan 2012 | B2 |
8341513 | Lattyak et al. | Dec 2012 | B1 |
8692763 | Kim | Apr 2014 | B1 |
20010007980 | Ishibashi et al. | Jul 2001 | A1 |
20010011366 | Beck et al. | Aug 2001 | A1 |
20010049623 | Aggarwal et al. | Dec 2001 | A1 |
20020174145 | Duga et al. | Nov 2002 | A1 |
20030093336 | Ukita et al. | May 2003 | A1 |
20030193423 | Ng et al. | Oct 2003 | A1 |
20030210226 | Ho et al. | Nov 2003 | A1 |
20030225609 | Klipfell, III | Dec 2003 | A1 |
20040030781 | Etesse et al. | Feb 2004 | A1 |
20040140975 | Saito et al. | Jul 2004 | A1 |
20040181746 | McLure et al. | Sep 2004 | A1 |
20050027671 | Hind et al. | Feb 2005 | A1 |
20050071864 | Denoue et al. | Mar 2005 | A1 |
20050267861 | Jassin et al. | Dec 2005 | A1 |
20060041538 | King et al. | Feb 2006 | A1 |
20060093998 | Vertegaal | May 2006 | A1 |
20060122716 | Bortnik et al. | Jun 2006 | A1 |
20060229944 | Walker et al. | Oct 2006 | A1 |
20060287046 | Walker et al. | Dec 2006 | A1 |
20070011039 | Oddo | Jan 2007 | A1 |
20070043817 | Oliver et al. | Feb 2007 | A1 |
20070061755 | Taboada et al. | Mar 2007 | A1 |
20070064626 | Evans | Mar 2007 | A1 |
20070078675 | Kaplan | Apr 2007 | A1 |
20070298385 | Jenkins et al. | Dec 2007 | A1 |
20070298399 | Shao et al. | Dec 2007 | A1 |
20080077492 | Ho et al. | Mar 2008 | A1 |
20080136838 | Goede et al. | Jun 2008 | A1 |
20080140652 | Millman et al. | Jun 2008 | A1 |
20080141182 | Barsness et al. | Jun 2008 | A1 |
20080162206 | Mak et al. | Jul 2008 | A1 |
20080199042 | Smith | Aug 2008 | A1 |
20080201348 | Edmonds et al. | Aug 2008 | A1 |
20080227076 | Johnson | Sep 2008 | A1 |
20080229182 | Hendricks et al. | Sep 2008 | A1 |
20080249893 | Knoll et al. | Oct 2008 | A1 |
20080263014 | Garijo Mazario et al. | Oct 2008 | A1 |
20080288862 | Smetters et al. | Nov 2008 | A1 |
20090024621 | Burgess et al. | Jan 2009 | A1 |
20090031244 | Brezina et al. | Jan 2009 | A1 |
20090070454 | McKinnon, III et al. | Mar 2009 | A1 |
20090083116 | Svendsen | Mar 2009 | A1 |
20090089177 | Dayton et al. | Apr 2009 | A1 |
20090156310 | Fargo | Jun 2009 | A1 |
20090240647 | Green et al. | Sep 2009 | A1 |
20090300670 | Barish | Dec 2009 | A1 |
20090326953 | Peralta Gimenez et al. | Dec 2009 | A1 |
20090326970 | Estrada et al. | Dec 2009 | A1 |
20100070899 | Hunt et al. | Mar 2010 | A1 |
20100076274 | Severson | Mar 2010 | A1 |
20100086130 | Wang et al. | Apr 2010 | A1 |
20100092095 | King et al. | Apr 2010 | A1 |
20100122178 | Konig et al. | May 2010 | A1 |
20100169906 | Takahashi | Jul 2010 | A1 |
20100174596 | Gilman et al. | Jul 2010 | A1 |
20100198693 | Lidwell et al. | Aug 2010 | A1 |
20100275233 | Soohoo et al. | Oct 2010 | A1 |
20100306122 | Shaffer | Dec 2010 | A1 |
20100313161 | Le Chevalier et al. | Dec 2010 | A1 |
20100315359 | Seong et al. | Dec 2010 | A1 |
20110010307 | Bates et al. | Jan 2011 | A1 |
20110040657 | Roswell | Feb 2011 | A1 |
20110050594 | Kim et al. | Mar 2011 | A1 |
20110066965 | Choi | Mar 2011 | A1 |
20110081867 | Issa et al. | Apr 2011 | A1 |
20110082719 | Dutta | Apr 2011 | A1 |
20110087955 | Ho et al. | Apr 2011 | A1 |
20110191692 | Walsh et al. | Aug 2011 | A1 |
20110191701 | Kim et al. | Aug 2011 | A1 |
20110195388 | Henshall et al. | Aug 2011 | A1 |
20110320276 | Ray et al. | Dec 2011 | A1 |
20120001923 | Weinzimmer et al. | Jan 2012 | A1 |
20120005617 | Lee et al. | Jan 2012 | A1 |
20120016772 | Sadagopan et al. | Jan 2012 | A1 |
20120030227 | Mital et al. | Feb 2012 | A1 |
20120041967 | Askey et al. | Feb 2012 | A1 |
20120206472 | Kandekar et al. | Aug 2012 | A1 |
Entry |
---|
Carey, “13 Summer reading programs avoid brain drain and get rewards”, Examiner.com, Family & Parenting, Jun. 3, 2010, Houston Family Examiner, pp. 1-pp. 3. |
Hart, “Summer 2009: Summer Reading Progams with a Reward for Kids”, Jun. 4, 2009, <<http://voices.yahoo.com>>, pp. 1-pp. 3. |
Non-Final Office Action for U.S. Appl. No. 12/888,086, mailed on Apr. 16, 2012, Simoina K. Dargan et al., “Content Tracking and Reward Architecture”, 19 pages. |
Non-Final Office Action for U.S. Appl. No. 13/294,883, mailed on May 8, 2012, Aaron James Dykstra et al., “Content Statistics ”, 31 pages. |
Final Office Action for U.S. Appl. No. 12/859,705, mailed on Aug. 15, 2012, Dykstra et al., “Content Completion Activities”, 49 pages. |
Non-Final Office Action for U.S. Appl. No. 12/859,662, mailed on Aug. 23, 2012, Aaron James Dykstra et al., “Content Completion Recommendations”, 20 pages. |
Howard, “Peer Influences on Young Teen Readers an Emerging Taxonomy”, Young Adult Library Services 8.2(Winter 2010), retrieved on Dec. 18, 2012, at http://search.proquest.com/docview/217681821/13B1452426F2ECBEB3C/14?accountid=14753, 9 pages. |
MacGibbon, “Pack a bag of books for your summer vacation”, The Times-Trascript, at http://search.proquest.com/docview/422986352/13B14EAE966F93C82B/1?accountid=14753, retreived on Dec. 18, 2012, 3 pages. |
Musgrove, “Waiting for Netflix's Plot to Advance: [Final Edition]”, The Washington Post, at http://search.proquest.com/docview/410232502/13AFFBF6A7C2B81DOBE/1?accountid=14753, retrieved on Dec. 14, 2012, 3 pages. |
Final Office Action for U.S. Appl. No. 13/294,883, mailed on Jan. 4, 2012, Aaron James Dykstra et al., “Content Statistics ”, 44 pages. |
Office action for U.S. Appl. No. 12/859,662, mailed on Dec. 28, 2012, Dykstra et al., “Content Completion Recommendations”, 22 pages. |
Office Action for U.S. Appl. No. 12/888,086, mailed on Mar. 26, 2014, Simoina K. Dargan, “Content Tracking and Reward Architecture”, 16 pages. |
Office Action for U.S. Appl. No. 12/859,705, mailed on Apr. 9, 2014, Aaron James Dykstra, “Content Completion Activities”, 52 pages. |
Proquest.com, “Discover and Share the Best of the Web with PrkL8 for IPhone: Personalized Web Discovery with Easy Sharing on Facebook”, PR Newswire Association LLC, at http://search.proquest.com/docview/450465234/13E60942898E781AA21/1?accountid=14753. on May 31, 2013, 2010, 2 pages. |
Proquest.com, “Next Plan Commission Meeting Taking Place, Aug. 18”, HT Media LTD, at http://search.proquest.com/docview/744504301/13E60942898E781AA21/3?accountid=14753, on May 31, 2013, 2010, 2 pages. |
YouTube.com, “Clarkson University Rap”, at http:www.youtube.com/watch?v=lezesOvNoWE&feature=featured, on May 31, 2013, 2009, 2 pages. |
Non-Final Office Action for U.S. Appl. No. 13/294,855, mailed on Oct. 26, 2012, Simoina K. Dargan et al., “Content Rewards”, 28 pages. |
Final Office Action for U.S. Appl. No. 12/888,086, mailed on Oct. 26, 2012, Simoina K. Dargan et al., “Content Tracking and Reward Architecture”, 24 pages. |
Final Office Action for U.S. Appl. No. 12/859,686, mailed on Nov. 9, 2012, Aaron James Dykstra et al., “Content Completion Reports”, 17 pages. |
Office action for U.S. Appl. No. 12/894,417, mailed on Sep. 14, 2012, Chatterjee et al., “Finding an End-of-Body Within Content”, 27 pages. |
Office action for U.S. Appl. No. 13/294,883, mailed on Aug. 20, 2013, Dykstra et al., “Content Statistics ”, 52 pages. |
Office action for U.S. Appl. No. 12/859,705, mailed on Sep. 6, 2013, Dykstra et al., “Content Completion Activities”, 51 pages. |
Office action for U.S. Appl. No. 12/888,086, mailed on Oct. 2, 2014, Vasen et al., “Content Tracking and Reward Architecture,” 17 pages. |
Office Action for U.S. Appl. No. 13/294,883, mailed on Apr. 2, 2014, Aaron James Dykstra, “Content Statistics,” 63 pages. |
Office action for U.S. Appl. No. 12/859,686, mailed on Jul. 30, 2014, Dykstra et al., “Content Completion Reports,” 32 pages. |
Office Action for U.S. Appl. No. 12/859,705, mailed on Aug. 18, 2014, Aaron James Dykstra, “Content Completion Activities,” 56 pages. |
Office Action for U.S. Appl. No. 13/294,883, mailed on Nov. 7, 2014, Aaron James Dykstra, “Content Statistics,” 51 pages. |
Office Action for U.S. Appl. No. 12/859,705, mailed on Dec. 9, 2014, Aaron James Dykstra, “Content Completion Activities,” 9 pages. |
U.S. Appl. No. 12/859,662, filed Aug. 19, 2010, Dykstra, et al., “Content Completion Recommendations”. |
U.S. Appl. No. 12/859,705, filed Aug. 19, 2010, Dykstra, et al., “Content Completion Activities”. |
U.S. Appl. No. 61/375,195, filed Aug. 19, 2010, Dargan, et al., “Content Tracking and Reward Architecture”. |
Office action for U.S. Appl. No. 12/859,705, mailed on May 7, 2015, Dykstra et al., “Content Completion Activities”, 8 pages. |
Office Action for U.S. Appl. No. 13/294,883, mailed on Jun. 25, 2015, Aaron James Dykstra, “Content Statistics”, 62 pages. |
Final Office Action for U.S. Appl. No. 12/888,086, mailed on Jul. 13, 2015, Simoina K. Dargan, “Content Tracking and Reward Architecture”, 22 pages. |
Office action for U.S. Appl. No. 13/294,883, mailed on Feb. 12, 2016, Dykstra et al., “Content Statistics”, 64 pages. |
Final Office Action for U.S. Appl. No. 12/859,686, mailed on Feb. 11, 2015, Aaron James Dykstra, “Content Completion Reports”, 39 pages. |
Office Action for U.S. Appl. No. 13/294,855, mailed on Feb. 18, 2015, Simoina K. Daragan, “Content Rewards”, 23 pages. |
Office action for U.S. Appl. No. 13/294,855 mailed on Sep. 10, 2015, Vasen et al., “Content Rewards”, 24 pages. |
Office action for U.S. Appl. No. 12/859,686 mailed on Oct. 6, 2015, Dykstra et al., “Content Completion Reports”, 32 pages. |
Office action for U.S. Appl. No. 12/859,705 mailed on Oct. 16, 2015, Dykstra et al., “Content Completion Activities”, 10 pages. |
Office action for U.S. Appl. No. 12/859,705, mailed on Mar. 15, 2016, Dykstra et al., “Content Completion Activities”, 55 pages. |
Office action for U.S. Appl. No. 12/859,686, mailed on May 5, 2016, Dykstraet al.,“Content Completion Reports”, 33 pages. |
U.S. Appl. No. 12/859,686, filed Aug. 19, 2010, Lee & Hayes, “Content Completion Reports”. |
U.S. Appl. No. 12/888,086, filed Sep. 22, 2010, Lee & Hayes, “Content Tracking and Reward Architecture”. |
“How to Write a Book Review”, retrieved on Jan. 25, 2012 at http://web.archive.org/web/20090420124930/http://www.lavc.edu/Library/bookreview.htm, Los Angeles Valley College Library, 4 pages. |
Office action for U.S. Appl. No. 12/859,705, mailed on Feb. 3, 2012, Dykstra et al., “Content Completion Activities”, 45 pages. |
Non-Final Office Action for U.S. Appl. No. 12/859,686, mailed on Feb. 6, 2012, Aaron James Dykstra et al., “Content Completion Reports”, 14 pages. |