Fix/273 deaccessioned dataset unauthenticated

[ekraffmiller]

What this PR does / why we need it:

This PR fixes an issue where the Dataset page of a deaccessioned dataset is not viewable for unauthenticated users.

To recreate this error, create dataset, publish it, then deaccession it. In JSF, when you log out, the deaccessioned dataset is still viewable to the unauthenticated user. If you go to the SPA and try to view the dataset, you get 'Page Not Found'

Which issue(s) this PR closes:

• Closes FIx dataset loading logic for Deaccessioned Dataset #273

Special notes for your reviewer:

Suggestions on how to test this:

Follow the steps to reproduce above. Test that the Dataset page is still viewable when the user is logged out.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

Additional documentation:

[coveralls]

coverage: 97.416% (-0.04%) from 97.459%
when pulling a5eec33 on fix/273-deaccessioned-dataset-unauthenticated
into c0f2d0b on develop.

[g-saracca]

Nice fix, looks great to me. I have already tested the behavior in the JSF version and tested the behavior in this branch and everything works as expected.

The error was occurring because Promise.all failed due to the api call to downloadSizes when canEditDataset was false right?
Attached is a screenshot of how a non-authenticated user can view a deaccesioned dataset.

[ekraffmiller]

Nice fix, looks great to me. I have already tested the behavior in the JSF version and tested the behavior in this branch and everything works as expected.

The error was occurring because Promise.all failed due to the api call to downloadSizes when canEditDataset was false right? Attached is a screenshot of how a non-authenticated user can view a deaccesioned dataset.

Yes, that's right, the unauthenticated user doesn't have permission to get the downloadSizes

[MellyGray]

LGTM! Deaccessioned page it's working well with an unauthenticated user