The onboard project script needs to support onboarding for resources

[mmartin9684-sil]

The onboarding script can already onboard a project downloaded from Scripture Forge or downloaded from Paratext.
Paratext also allows a user to download resources, which are stored as password-protected zip files in a different location.

• When a Paratext project is downloaded, it is stored in a subfolder under the user's "My Paratext ... Projects" folder. The project's short name is used as the subfolder name.
• When a Paratext resource is downloaded, it is stored in the user's "My Paratext ... Projects > _Resources" folder. The downloaded resource is stored in a password-protected zip file with the name ".p8z".

Note: there are some circumstances when a download resource gets stored in the user's "My Paratext ... Projects > _resourcesById" subfolder instead. Resources stored in this subfolder are also password-protected zip files, with the name "..p8z". It's not clear why this happens at times. We may want to have a two-step lookup strategy for onboarding these resources (look in _Resources first, look in _resourcesById second).

[ddaspit]

Is the main issue the fact that the resource file is a password-protected zip file?

[mmartin9684-sil]

That's the two main complications - zipped, and password protected. It's also in slightly a different location.

[TaperChipmunk32]

@mmartin9684-sil Should Resources be treated the same as projects with all the same options (extracting, verse_counts, wildebeest, etc)?