Skip to content
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

Show number of archives represented in memento count in UI #282

Closed
machawk1 opened this issue Dec 14, 2017 · 5 comments
Closed

Show number of archives represented in memento count in UI #282

machawk1 opened this issue Dec 14, 2017 · 5 comments

Comments

@machawk1
Copy link
Owner

Currently we show the "number of mementos" within the window interface based on what the user entered in the text box. It would also be useful to show the number of archives from which these mementos originate. This information may need to be parsed out of the TimeMap returned from MemGator.

screen shot 2017-12-14 at 1 20 43 pm

@ibnesayeed
Copy link
Contributor

Once implemented, oduwsdl/MemGator#97 should make it very easy, while also providing more summary information.

@machawk1
Copy link
Owner Author

@ibnesayeed In the meantime, since we are just looking for a count of archives, I am thinking of just clustering based on archival host. Thoughts?

@ibnesayeed
Copy link
Contributor

That is certainly doable and can be easily implemented using a Counter dict. However, It might result in a slight delay for larger TMs. Currently, the total memento count can be accessed from the header even before the payload is fully downloaded (or just by making a HEAD request). Providing more information would require us to download the TM, parse it (or go through it one record/line at a time) to populate the counter dictionary before injecting the outcome in the UI.

@machawk1
Copy link
Owner Author

machawk1 commented Dec 14, 2017

Thanks for the pointer.

It's running locally and performed asynchronously, so should not incur too much delay. I would like to either move away from calling URI-Ms in the returned TimeMap "mementos" or be more clear on the basis of the count. Thus, relying on the X-Memento-Count header would be in a step in the opposite direction of what should be conveyed in the UI.

Also, performing a HEAD would still incur the delay of requesting the TimeMaps from the respective archives, which I believe is still much more significant than the delay to parse the TimeMap locally.

Also also, I'm using MemGator in one-off mode, not server mode, so the aforementioned is moot. I will be changing it to server mode once MemGator support runtime specification of archives (as is sub-optimally implemented in my MemGator fork).

@ibnesayeed
Copy link
Contributor

@machawk1, I have added a couple comments in your recent commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants