Update archived item URLs about browsertrix HOT 6 CLOSED

Implemented /artifacts/upload/<id> only, the others are less urgent as they're not linked to directly.

from browsertrix.

See #922 for determining what things should be named

from browsertrix.

Awaiting final decision on the name

from browsertrix.

@ikreymer Do we still want separate subpaths for crawltype, like /artifacts/uploads and /artifacts/upload/{id}? I see some benefit to standardizing around a single subpath and using query params to filter the view for streamlining, now that the API endpoint all-crawls returns the same data shape as uploads and crawls.

Thoughts on the following:

• All Archived Items:/orgs/{oid}/archive/items
• Crawls:/orgs/{oid}/archive/items&type=crawl
• Uploads:/orgs/{oid}/archive/items&type=upload
• Any Archived Item detail: /orgs/{oid}/archive/items/{id}

from browsertrix.

@ikreymer Do we still want separate subpaths for crawltype, like /artifacts/uploads and /artifacts/upload/{id}? I see some benefit to standardizing around a single subpath and using query params to filter the view for streamlining, now that the API endpoint all-crawls returns the same data shape as uploads and crawls.

Yes, I think the old 'artifact' name no longer makes sense.

Thoughts on the following:

• All Archived Items:/orgs/{oid}/archive/items
• Crawls:/orgs/{oid}/archive/items&type=crawl
• Uploads:/orgs/{oid}/archive/items&type=upload

I think that makes sense.

• Any Archived Item detail: /orgs/{oid}/archive/items/{id}

For the details, I think the type specific endpoint might be better since we can include type-specific info in the detail?
Also, ArchiveWeb.page currently uses the /artifacts/upload/<upload-id> but I guess we should probably add a redirect regardless

from browsertrix.

Closed by #1064

from browsertrix.