Dan: Spoke with chris today about your build so far. All good things. We have one thing we'd like you to try and test when you have a chance. We were wondering if you could pull up a list of application serial numbers that are very recent that have the new status of "Notice of Allowance Mailed" and/or "Issue Fee Paid". We recognize that these statuses exist along with a corresponding "Status Date", but that doesnt mean the JSON was updated at the same time as the "status date" date. What we want to know, for predicting our ability to quickly alert customers of these changes, is actually how long it was between when the event actually happened, which we can check on the transaction history tab at Public Pair behind the captcha wall on USPTO website. For example, if you can find some examples where the JSON "status" changed from one day to the next to "Notice of Allowance Mailed" and/or to "Issue Fee Paid", that would be awesome cause then we have a day the status changed in the JSON. If we can actually catch when one of those status changes occurs in the PAIR JSON data you have, we can check to see when the event actually occurred in real life in the transaction history and determine if there is any lag time, and if so, how much lag time between the actual event happening and the JSON status field changing. If for example, you can take data from say 2013-2015 filing dates and compare this coming tuesday's data to this coming monday's data to look for a status change to either of the ones listed above.....and you can give us app serial no, for example, we can check public pair to see when the event actually occurred. If the JSON status is changing within a day or two of the transaction actually happening, then that would be VERY good news for setting up trustworthy alerts for customers about these two major events and other major events when know our customers would want to be alerted about, without needing to use Reed Tech's daily transaction history update scrape data. 99% of the transactions that occur in the transaction history tab are of little or no interest to customers...but these two are very important ones. There are others that we can have you check, such as "Non-Final Office Action Mailed", once we check these two in particular. Let me know if you can try to get us two lists, one of a day to day change to "Notice of Allowance Mailed" and one of a day to day change to "Issue Fee Paid", then we can verify the lag time to update our assumptions on how quick JSON data is actually reflecting that change. We hope its occurring within one day...but even if we find its happening within a week, that would prob still be ok for most cases.
Dan: Spoke with chris today about your build so far. All good things. We have one thing we'd like you to try and test when you have a chance. We were wondering if you could pull up a list of application serial numbers that are very recent that have the new status of "Notice of Allowance Mailed" and/or "Issue Fee Paid". We recognize that these statuses exist along with a corresponding "Status Date", but that doesnt mean the JSON was updated at the same time as the "status date" date. What we want to know, for predicting our ability to quickly alert customers of these changes, is actually how long it was between when the event actually happened, which we can check on the transaction history tab at Public Pair behind the captcha wall on USPTO website. For example, if you can find some examples where the JSON "status" changed from one day to the next to "Notice of Allowance Mailed" and/or to "Issue Fee Paid", that would be awesome cause then we have a day the status changed in the JSON. If we can actually catch when one of those status changes occurs in the PAIR JSON data you have, we can check to see when the event actually occurred in real life in the transaction history and determine if there is any lag time, and if so, how much lag time between the actual event happening and the JSON status field changing. If for example, you can take data from say 2013-2015 filing dates and compare this coming tuesday's data to this coming monday's data to look for a status change to either of the ones listed above.....and you can give us app serial no, for example, we can check public pair to see when the event actually occurred. If the JSON status is changing within a day or two of the transaction actually happening, then that would be VERY good news for setting up trustworthy alerts for customers about these two major events and other major events when know our customers would want to be alerted about, without needing to use Reed Tech's daily transaction history update scrape data. 99% of the transactions that occur in the transaction history tab are of little or no interest to customers...but these two are very important ones. There are others that we can have you check, such as "Non-Final Office Action Mailed", once we check these two in particular. Let me know if you can try to get us two lists, one of a day to day change to "Notice of Allowance Mailed" and one of a day to day change to "Issue Fee Paid", then we can verify the lag time to update our assumptions on how quick JSON data is actually reflecting that change. We hope its occurring within one day...but even if we find its happening within a week, that would prob still be ok for most cases.