-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Naive TimeMap counting algorithm causes UI to display possibly inaccurate count #283
Comments
Nice catch. This is a good candidate for a test case. Also a good idea to reuse the archive counting process (new as of < 12 hours ago, so pardon the delay ;)) for counting URI-Ms. |
@ibnesayeed What are your thoughts on using CDXJ then performing one of the following to obtain the count?
This would allow us to exploit the features of CDXJ but still incur the temporal expense of converting from a Link to a CDXJ in MemGator, for which a Link-based solution might be more efficient (at the cost of parsing the rel). |
A PR is on its way. :) |
Ah, ok. In the future, if you are working on a ticket, let me know and I can assign it to you so we don't waste work cycles (I was working on a solution as well). I'll defer to your upcoming PR. |
I thought I did, but apparently I forgot to mention here. Anyways, the PR #284 is in now for review. |
wail/bundledApps/WAIL.py
Line 397 in 76a6d4d
This rudimentary approach of counting the occurrence of the term
memento
in the response could result in wrong memento count when the term appears in URI-Ms. This could happen for two reasons:mementoweb.org
/memento/<datetime>/<URI-R>
A more reliable approach would be to count it when the TM is processed for counting archives. Currently the TM is being processed twice, which can be slow for big TMs.
The text was updated successfully, but these errors were encountered: