A currently viewing section 115 can comprise the participants (e.g., Matt, Abby, Ryland). A tag section 120 can comprise any or all of the following tags which can enable a participant to tag the meeting: Budget, Negotiation, Pricing, Intro, Next Steps, Objection, Needs, Business, Outcome, Timing, and Authority. A tag (also called “comment tag”) can be pinned to an exact moment of its creation (or a moment before its creation) within the context of the recording of the meeting and designated by the user (e.g., related to Budget, related to Pricing) so that the user can easily go back and access or replay any tagged portions of the meeting. Those of ordinary skill in the art will see that any other type of meeting tag can be created.
To create a tag, a comment tag category that can later be associated to a specific comment tag can be created, as show in the following example code:
A comment tag with a category id associated to it can then be inserted, as illustrated in the following example code (e.g., where the timestamp is for 10 seconds ago):
// DB library syntax inspired by knex.js database connection library
// next, using the newTagId created in the snippet above
conn(‘comment’).insert({text: /* comment text */”, created_at_in_milliseconds: Date.now( )−(10*1000), tag_id: newTagId})
As mentioned above, when a comment tag is created, the date can be moved to a certain time period before the comment tag is created so that the beginning of the important information is captured. This time period can be 1 second-25 seconds, or even longer. The above example code uses an example of saving a comment with a date of 10 seconds ago. In some embodiment, a user can designate a certain time period for each of the comment tags (e.g., all tags can go back 3 seconds, or the Pricing tag can go back 2 seconds, but a Budget tag can go back 10 seconds)
A meeting platform section 305 can allow a user to enter in a platform (e.g., ZOOM) for the bot, A meeting title section 310 can allow a user to enter in a title for the meeting (e.g., “meeting with customer”). A meeting ID or URL section 315 can allow the user to enter in the meeting ID or URL. The pseudo-code below illustrates an example of how a bot can join a meeting by URL. The code below illustrates how the URL the user provides is parsed in order to find details about the meeting required to join the meeting (e.g., the meeting ID) from the URL (in this example a UBERCONFERENCE platform is used, although any platform can be used):
const userInput=‘https://uberconference.com/personal_meeting_example_id’;
const regex=/uberconference\.com\/([a-z0-9-_.]+)/i;
const matches=userInput.match(regex);
const meetingId=matches[1];
Any URL can be parsed to find the meeting ID. For example, the following types of URLs can be parsed:
The code below illustrates how the meeting ID can be used to join a meeting in a web browser (using, for example, node.js_webdriver bindings for a browser):
const driver=new webdriver.Builder( ).build( );
const url=‘https://www.uberconference.com/${meetingId}’;
console.log(‘LOG: doing ${meetingPlatform} url: ${url}’);
driver.get(‘https://www.uberconference.com/${meetingId}’);
While the disclosure has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the disclosure can be embodied in other specific forms without departing from the spirit of the disclosure. In addition, a number of the figures illustrate processes. The specific operations of these processes may not be performed in the exact order shown and described. The specific operations may not be performed in one continuous series of operations, and different specific operations may be performed in different embodiments. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.
While various embodiments have been described above, it should be understood that they have been presented by way of example and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail may be made therein without departing from the spirit and scope. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement alternative embodiments. Thus, the present embodiments should not be limited by any of the above-described embodiments.
In addition, it should be understood that any figures or description which highlight the functionality and advantages are presented for example purposes only. The disclosed methodology and system are each sufficiently flexible and configurable such that they may be utilized in ways other than that shown. For example, any steps or limitations in the specification, figures and claims may be done in another order than the order portrayed.
Further, the purpose of any Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. An Abstract of the Disclosure is not intended to be limiting as to the scope of the present invention in any way.
Although the term “at least one” may often be used in the specification, claims and drawings, the terms “a”, “an”, “the”, “said”, etc. also signify “at least one” or “the at least one” in the specification, claims and drawings.
Additionally, the terms “including”, “comprising” or similar terms in the specification, claims and drawings should be interpreted as meaning “including, but not limited to.”
Finally, it is the applicant's intent that only claims that include the express language “means for” or “step for” be interpreted under 35 U.S.C. 212, paragraph 6. Claims that do not expressly include the phrase “means for” or “step for” are not to be interpreted under 35 U.S.C. 212, paragraph 6.
The present application claims priority to U.S. provisional Ser. No. 62/713,281, filed on Aug. 1, 2018, titled “SYSTEMS AND METHODS FOR ELECTRONIC NOTETAKING.” This provisional application is herein incorporated by reference in its entirety for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
7760865 | Awan et al. | Jul 2010 | B2 |
8064342 | Badger | Nov 2011 | B2 |
8631069 | Maes | Jan 2014 | B2 |
9256695 | Willis et al. | Feb 2016 | B1 |
9392122 | Sall | Jul 2016 | B2 |
9699409 | Reshef et al. | Jul 2017 | B1 |
9992448 | Reshef et al. | Jun 2018 | B2 |
10218839 | Gupta et al. | Feb 2019 | B2 |
10325284 | Aggarwal et al. | Jun 2019 | B1 |
20070206759 | Boyanovsky | Sep 2007 | A1 |
20090274284 | Arsenault et al. | Nov 2009 | A1 |
20100135477 | Chen | Jun 2010 | A1 |
20100205543 | Von Werther et al. | Aug 2010 | A1 |
20100223389 | Ananthanarayanan | Sep 2010 | A1 |
20110228921 | Singh | Sep 2011 | A1 |
20110271210 | Jones et al. | Nov 2011 | A1 |
20120051267 | Ma et al. | Mar 2012 | A1 |
20130076853 | Diao | Mar 2013 | A1 |
20130191719 | Underhill | Jul 2013 | A1 |
20140006611 | Perez | Jan 2014 | A1 |
20150036810 | Rashid et al. | Feb 2015 | A1 |
20160253314 | Pottier | Sep 2016 | A1 |
20160381215 | Goyal et al. | Dec 2016 | A1 |
20170257598 | Reshef et al. | Sep 2017 | A1 |
20170345325 | Metts | Nov 2017 | A1 |
20180082208 | Comier et al. | Mar 2018 | A1 |
20180121828 | Keysers | May 2018 | A1 |
20180176661 | Varndell | Jun 2018 | A1 |
20180191901 | Aleksin et al. | Jul 2018 | A1 |
20180227339 | Rodriguez | Aug 2018 | A1 |
20180239822 | Reshef et al. | Aug 2018 | A1 |
20180249122 | Reshef et al. | Aug 2018 | A1 |
20180268318 | Matam et al. | Sep 2018 | A1 |
20180330736 | Faulkner | Nov 2018 | A1 |
20190068390 | Gross | Feb 2019 | A1 |
20190068526 | Xie | Feb 2019 | A1 |
20190102846 | Loschiavo | Apr 2019 | A1 |
20190182183 | Hubauer | Jun 2019 | A1 |
20190205772 | Kohlmeier | Jul 2019 | A1 |
20190318743 | Reshef et al. | Oct 2019 | A1 |
Entry |
---|
WebEx Meeting Center with Collaboration Meeting Rooms (CMR Cloud) User Guide, https://www.cisco.com/c/en/us/td/docs/collaboration/meeting_center/wbs2913/CMR_Cloud_User_Guide.pdf, total 24 pages, Publication Date: Aug. 1, 2014. |
Pexip Mobile App for Android Quick Guide, https://docs.pexip.com/files/v8/Pexip_Mobile_App_Android_Quickguide v8.a.pdf, Total 4 pages, Publication Date: Feb. 2015. |
Lync conference invitations in SIP terms, http://blog.greenl.ee/2011/12/15/lync-conference-invitations/, Total 7 pages, Publication Date: Dec. 15, 2011. |
RFC4579—Session Initiation Protocol (SIP) Call Control—Conferencing for User Agents, https://datatracker.ietf.org/doc/rfc4579/ , pp. 3, Publication Date: Aug. 2006. |
U.S. Appl. No. 16/518,367 on Nov. 15, 2019. |
U.S. Appl. No. 16/518,367 on Apr. 21, 2020 from Feb. 25, 2020 to Apr. 21, 2020. |
U.S. Appl. No. 16/558,692 on Apr. 21, 2020 from Feb. 25, 2020 to Apr. 21, 2020. |
U.S. Appl. No. 15/852,259 on Apr. 21, 2020 from Feb. 25, 2020 to Apr. 21, 2020. |
U.S. Appl. No. 16/518,367 on Feb. 25, 2020 from Nov. 15, 2019 to Feb. 25, 2020. |
U.S. Appl. No. 16/558,692 on Feb. 25, 2020. |
U.S. Appl. No. 15/852,259 on Feb. 25, 2020. |
U.S. Appl. No. 16/518,367 on Jun. 3, 2020 from Apr. 21, 2020 to Jun. 3, 2020. |
U.S. Appl. No. 16/558,692 on Jun. 3, 2020 from Apr. 21, 2020 to Jun. 3, 2020. |
U.S. Appl. No. 16/855,610 on Jun. 3, 2020. |
U.S. Appl. No. 16/558,692, filed Sep. 3, 2019, Pending. |
U.S. Appl. No. 15/852,259, filed Dec. 22, 2017, Pending. |
U.S. Appl. No. 16/518,367, filed Jul. 22, 2019, Pending. |
U.S. Appl. No. 16/855,610, filed Apr. 22, 2020, Pending. |
Number | Date | Country | |
---|---|---|---|
62713281 | Aug 2018 | US |