"Not found" entry page needs adjustment

[svonworl]

Describe the bug
When you navigate to the public URL of an existing Dockstore entry that is no longer published, Dockstore displays some "could not be found" content. This content needs some fixin':

1. The correct entry type should be displayed. For example, in the screenshot below, "workflow" should be "notebook".
2. The links appear to be malformed/wrong.
3. Arguably, if I have access to the entry's private page, I should be redirected there, instead.

There could be other issues.

It should be noted that I found the bug when clicking on the link on my profile page, to one of my own notebooks. In lieu of the above redirect, perhaps, when, I’m viewing my own profile, the entry links should be to the private entry page?

Inspect for the various entry types, devise solutions, and implement them.

To Reproduce
Steps to reproduce the behavior:

1. Enter the public URL of a Dockstore entry that exists, but is not published.
2. See the bugs.

Expected behavior
Correct information is displayed, and the redirection mentioned above happens.

Screenshots

Additional context
[Domain] - https://qa.dockstore.org

Webservice

• 3879929

UI

• 2.12.0-beta.0-14-g6251a483

Deploy

• 1.14.4-62-gef77999

cwlParsingLambdaVersion: n/a

wdlParsingLambdaVersion: n/a

nextflowParsingLambdaVersion: n/a

galaxyParsingLambdaVersion: 0.0.6

checkUrlLambdaVersion: n/a

┆Issue is synchronized with this Jira Story
┆Fix Versions: Dockstore 1.16
┆Issue Number: DOCK-2499
┆Sprint: 137 - Jacksonville
┆Issue Type: Story

[denis-yuen]

See also #5728

[unito-bot]

➤ Steve Von Worley commented:

When I tried to reproduce these problems, I noticed that the “not found” page had changed since this ticket was written. The new text is good, generic, and doesn’t contain links. So, most of the proposed work is no longer applicable.

This ticket proposes that “Arguably, if I have access to the entry's private page, I should be redirected there, instead.” After consideration, although that would be neat, it’s a relatively edge case and the benefit would not be worth the cost.

While testing, I thought that I’d spotted another issue, but I couldn’t reproduce it later. It’s possible that I was testing on the wrong server (staging or prod versus qa).

So, there is nothing left to do.

Rejecting.