Use Archive Number instead of Archive ID

[kfogel]

This issue might better belong in the SDK or back-end repository. If so, this ticket can become a pointer to the underlying ticket over there. But right now I just need to get this documented, because it's one step in a towering and unexpected yak shave that I need to finish, so here's what's going on:

Using SFTP to fetch a single specific archive down, or to upload up to a specific archive, requires knowing the internal archive ID number. For example, in a command like this...

rclone copy -v -P --create-empty-src-dirs --size-only --sftp-set-modtime=false \
       "permanent-prod:/archives/kfogel OTS test (13539)/My Files/" ./my-permanent-data

...that's the "13539" in parentheses.

The problem is that there is no way for the user to get that number from the web UI, as @cecilia-donnelly and I were just discussing in Slack.

Now, you can get the public ID by going to the archive's profile page while logged in and clicking the "View On Web" button in the upper right -- then the URL will switch to something like "https://www.permanent.org/p/archive/09lg-0000/profile" and you can see the "09lg-0000" in the URL.

But that is not the number we're looking for. We're looking for something like "13539", and currently there's no way to discover it except by downloading all of your archives via rclone (or whatever SFTP client) and then looking in the downloaded folder names for numbers in parentheses.

Assigning this to @cecilia-donnelly for now, because she's in the best position to decide how to / who should handle this.

[slifty]

For some extra context -- I made the mistake of closing a broader issue that included this idea but didn't capture the idea here. Thank you Karl!

Here's the link: #14 (comment)

So to be clear I think the decision actually had been made and I lost it in translation when I closed that issue as complete: We want to use "archive number" rather than "archive ID"

[cecilia-donnelly]

Yes, and I think (?) this is the right place for this issue to live - the back-end returns both. It looks to me like the SDK does not fill in the archiveNbr, though, so it will need a partner issue. I made PermanentOrg/permanent-sdk#78 which I hope covers what's needed. Once that's complete, this service will use that new field and adjust the path names it creates to use a string "archiveNbr" instead of an integer "archiveId."