Research Evidence Upload

What the uploader does

The operator selects a finalized local evidence directory and a versioned destination. The uploader copies the selected files to Google Drive, verifies the transfer using file checksums, and records a delivery receipt on the research server.

The evidence workflow preserves its local source files, skips identical destination files, and reports conflicts instead of replacing existing evidence in Drive. Local deletions do not delete the uploaded copies.

Evidence from multiple research projects

Research projects can reuse the same authorized Google account. Each project selects its own destination folder and uses versioned subfolders for individual experiment deliveries.

The operator supplies the destination settings for the selected project. Changing research projects changes the destination configuration; a separate Google authorization is not required for each project while the existing authorization remains valid and the account has access to the destination.

Google Drive access

The Google account owner signs in and grants access through Google's authorization screen. The workflow uses the Google Drive API to list destination files, upload selected evidence, and compare file information for verification.

The authorization requests the Google Drive scope, which can permit access across the authorized account's Drive. Each evidence delivery targets the folder selected for that project; the destination configuration does not narrow the Google authorization itself.

These informational pages do not accept account passwords, tokens, or evidence uploads. Authorization credentials are handled by the command-line tool on the research server.

Support and data requests

This tool is operated for personal research use. Contact the project owner using the user-support email displayed on the Google authorization screen.

Read the privacy policy for details about data access, storage, retention, and revoking access.