ManifoldScholar/manifold

Clicking resource thumbnails in the text causes URL to traverse from using the slug to using the UUID

karenhanson opened this issue · 1 comments

Relates to feedback from Mellon-funded Embedding Preservability project. We noted that each page in the text can be referenced either using the slug or the UUID:
https://manifold.umn.edu/read/metagaming/section/00d65eb7-926c-4159-9d95-5fee5285e7b8
https://manifold.umn.edu/read/c5926868-00c4-45f8-8e91-45cfd9140a87/section/00d65eb7-926c-4159-9d95-5fee5285e7b8
If both versions of the URL are linked to within the publication, a web crawl will need to record both copies in order for the archived copy to function - this causes the resulting archived files to be larger than they need to be with a lot of redundancy - it also doubles the crawl time/impact on the Manifold server (it may affect search engine crawl times as well). We noted that most links use the slug version of the URL, but a traversal occurs when clicking on a resource thumbnail in the left margin of a text.

Expected Behavior

I expect the resource thumbnail to link to the /read/{slug}/section/{uuid}/resource/{uuid} version of the URL.

Current Behavior

Clicking a resource thumbnail switches the URL from using the slug to /read/{uuid}/section/{uuid}/resource/{uuid}. It then continues to use UUID instead of slug as you continue to navigate the text.

Possible Solution

Change the resource thumbnails to point to the slug URL

Steps to Reproduce

  1. Start here: https://manifold.umn.edu/read/metagaming/section/00d65eb7-926c-4159-9d95-5fee5285e7b8
  2. Click the thumbnail for Triforce in the left margin. You end up here: https://manifold.umn.edu/read/c5926868-00c4-45f8-8e91-45cfd9140a87/section/00d65eb7-926c-4159-9d95-5fee5285e7b8/resource/1f532704-37c4-4396-b39c-ad492915cf8f (note the word "metagaming" has been replaced with a UUID).
  3. X-out the resource modal - the UUID will now be used as you navigate the text.

Context (Environment)

Trying to make web crawls more efficient, smaller, less burdensome on the server.

Detailed Description

Covered by other fields.

Thank you for taking the time to report this bug. We've reviewed the issue and agree that this should be fixed. We’re adding a “planned” label to indicate that we consider this bug as part of our current work plan.

This was an automated message, but please don't hesitate to reply. Our team watches these issues closely and will respond as soon as we're able to!