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

Dealing with decommissioned and current homepage URLs for the same website #369

Open
crarugal opened this issue Jan 12, 2023 · 2 comments
Open

Comments

@crarugal
Copy link
Collaborator

By default, users are taken to the first capture of a target (when browsing Collections).

For example https://www.webarchive.org.uk/en/ukwa/collection/3085?page=2
image

Clicking on the openly accessible copy will take us to the first capture, the homepage of which in 2010 was http://www.florence-nightingale.co.uk/cms/
image

However, the live site uses http://florence-nightingale.co.uk/ as the homepage, which isn't apparent to the user.

So navigating to the first capture, then to the calendar, will present the user with the captures of the URL that was first archived/viewing at the time:
image

But, there are actually recent captures of the current website:
image

https://www.webarchive.org.uk/act/targets/5311

I've not thought about the best way to deal with this, but it's something worth considering in any future updates

@anjackson
Copy link
Contributor

As per ukwa/ukwa-services#81 (comment) it is possible to add an @alias mapping that makes the CDX lookup treat different URLs as if they were the same.

We could try experimenting with that, and if it provides a reasonable experience, consider ways of managing these aliases and making sure they're up to date.

@crarugal
Copy link
Collaborator Author

thanks, Andy, sounds like a fix worth exploring

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