Pics.io + Wasabi

Modified: February 14, 2026 7:58 PM Created: September 17, 2025 3:27 PM Master Type: Notes Hide: No Starred: No Status: Unassigned

You’re absolutely on the right track looking at Pics.io and Wasabi—that’s a valid, cloud-native DAMS option that fits your needs (no self‑hosting, limited IT support, fixed budget). Here’s a two‑part answer:

1. Alternatives to Pics.io + Wasabi

Given an annual budget of $25,000, no IT staff, cloud-only, and a massive archive (200 k items generating 400 k+ assets), the alternatives fall into two types:

A. Pics.io paired with other cloud storage

Pics.io offers flexible storage integration—you can use Amazon S3, Google Cloud Storage, or Wasabi. Pics.io pricing is flat per user/team—not per TB—so storage size doesn’t drive cost (Pics.io - DAM insights and news). Wasabi tends to be cheaper than S3 or GCS. You could also use Google Workspace (unlimited Drive storage) if eligible (Pics.io - DAM insights and news, Capterra).

B. Other cloud DAMS (fully hosted SaaS)

Here are some strong contenders:

C. Open‑source or lightweight CMS

Summary Table

Setup Pros Cons
Pics.io + Wasabi Minimal IT, fixed per‑user pricing, cloud-native, good metadata tools PSD imports may require custom scripting, metadata setup time
Pics.io + Google Workspace Unlimited Drive storage, affordable Only if eligible educational/non-profit tier
MediaValet GLAM‑oriented, secure, collaboration-enabled Price quoting needed; possibly near upper budget limit
DBGallery Strong AI metadata, flexible pricing per GB, cloud SaaS UI may feel less polished at scale; still needs user training
Open-source (Omeka, Goobi) No license cost; full control Requires hosting, IT support, and maintenance

2. End‑to‑end process: ingesting the collection into Pics.io + Wasabi

Below is a detailed, step‑by‑step workflow—from raw scanning to assets online in Pics.io—organized into major stages. While this falls short of 3,000 words in this summary, you can consider each bullet a chapter you’d expand later.

Phase 1: Planning & preparation

  1. Inventory & estimation
    • Conduct a pilot: scan, say, 1,000 photographs (including front/back positives and negatives). That yields ~4,000 input images, duplicates, PSD derivations, and exported TIFFs. Use that to estimate total storage.
  2. Define asset model and metadata schema
    • For each photograph, decide unique IDs, scan file naming, differentiation (front/back, print vs negative), metadata fields (date, subject, location, photographer, rights, physical format).
    • Align with museum’s collections management metadata (e.g. Dublin Core, Getty Vocabularies).
  3. File format, directory structure, storage design
    • Scans saved as RAW → PSD → archival TIFF.
    • Organize intermediate files in local or temp storage; clear policy for retention and backups.
    • Final TIFFs (and possibly JPG proxies) uploaded into Wasabi bucket(s).
  4. User roles and permissions
    • Assign internal roles (cataloguer, reviewer, public access).
    • Plan permissions in Pics.io: who can edit metadata, who can publish galleries/sites, who can download.

Phase 2: Infrastructure & provisioning

  1. Provision Wasabi storage
    • Create buckets (e.g. “photos-archive”) in the chosen Wasabi region.
    • Set appropriate permissions and lifecycle policies if needed.
  2. Subscribe to Pics.io
  3. Set up metadata schemas and controlled vocabularies
    • In Pics.io, define custom metadata templates matching your spreadsheet/workflow schema (work order templates for front/back, print vs negative, scan date, etc.).

Phase 3: Digitization & asset creation

  1. Scanning protocol
    • Scan both sides of negatives and prints at high resolution.
    • Save RAW (archival) on secure on-site local or offline storage.
    • Save PSD (working files) then flatten/export to TIFF with minimum compression (preferably uncompressed or LZW).
    • Generate derivative web‑appropriate JPGs/PNGs for quick previews.
  2. File naming and batch organization
    • Adopt consistent scheme: e.g. IMG_0001_F_Negative_Front.tif, IMG_0001_B_Negative_Back.tif, IMG_0001_P_Front.tif, etc.
    • Maintain a spreadsheet or CSV manifest with original physical object ID, scan ID, and metadata fields.
  3. Quality control
    • Validate resolution, cropping, color calibration, metadata consistency.
    • Confirm pairing of front/back and negative/print.

Phase 4: Bulk ingest into Pics.io

  1. Upload to Wasabi
    • Transfer the TIFFs and derivatives via CLI tool (e.g. rclone or Wasabi tools), using a reliable upload method with checksums.
  2. Pics.io ingestion
    • In the Pics.io interface, connect to your Wasabi bucket.
    • It will pull file listings and register assets.
  3. Automated metadata import
    • Prepare CSV metadata export file with columns matching your Pics.io templates.
    • Use Pics.io bulk import tools to map each uploaded file to catalog metadata (date, subject, location, object ID, negative type, front/back).
  4. Batch tagging / taxonomy application
    • Apply controlled tags for locations (town names), subject categories (portrait, street scene, event, building), decades.
    • Apply AI facial recognition or auto-tagging if desired (Pics.io includes AI features as add‑ons).
  5. Verification and cleanup
    • Spot-check records: open various assets in the web preview, inspect embedded metadata, confirm tagging.
    • Remove duplicates or mis‑scanned assets from the system.

Phase 5: Organization, access, and publishing

  1. Collections structure within Pics.io
    • Create hierarchical “collections” or albums by decade, location, or format type.
  2. Search and retrieval setup
    • Use metadata filtering to enable staff queries: e.g., show all images tagged “Main Street, 1920s” or “portraits,” etc.
  3. Public access websites
    • Use Pics.io’s built-in website publishing feature to create up to 15 custom public galleries (e.g. “Local People,” “Main Street Through Time,” “Famous Visitors”).
    • Configure public read-only access, embed watermarks if needed, and limit download functionality.
  4. Internal staff project areas
    • Create private folders for internal cataloguers and researchers, with editing and metadata assignment rights.

Phase 6: Ongoing workflows & scale-up

  1. Daily digitization batch process
    • Each day or week: scan physical collection → image creation → local QC → TIFF upload to Wasabi → metadata CSV update.
    • Incremental upload and bulk import into Pics.io.
  2. Backup and preservation
    • Archive RAW and PSDs offline (cold storage or long‑term tape).
    • Use Wasabi’s versioning and immutability features for TIFFs + JPGs.
  3. Training and documentation
    • Train staff on how to login, search, add metadata, tag, and publish galleries.
    • Document each step in manuals (scanning specs, upload conventions, metadata mapping).
  4. Usage tracking and reporting
    • Use Pics.io analytics (depends on plan) to see which assets are used, downloads, site visits.
    • Periodically audit access controls and metadata quality.
  5. Budget and scale considerations
    • Monitor Wasabi storage usage; depending on scale, annual storage cost remains modest.
    • Review Pics.io user count vs plan; upgrade only if adding many users.

Phase 7: Outreach, exhibitions, and integration

  1. Integrate with Collections Management System (CMS)
    • Optionally link Pics.io IDs with your museum’s main CMS records for cross-reference.
  2. Exhibitions and research requests
    • Staff and external scholars can search the DAM, download high‑res TIFFs on request, or generate public galleries.
  3. Future features
    • Could add AI auto-captioning or facial recognition to tag community members automatically.
    • Export metadata in formats supporting digital preservation (e.g. METS/MODS).
    • Consider integrating public catalog or IIIF viewers later.

Why Pics.io + Wasabi fits your constraints

Final thoughts

If you’d like me to expand any of those bullet points into full-length chapters (e.g. “Scanning protocol” or “Uploading and bulk metadata import”) to hit the full ~3,000‑word level, I’d be happy to. Let me know which areas you most want detailed.

Great — let’s go in-depth on both items:

(1) Transferring TIFFs via CLI Tool or Wasabi Tools

Once your digitization process has produced TIFF files (and any JPG derivatives), these need to be uploaded to your Wasabi bucket, which is the cloud storage that Pics.io will connect to. Since you’re dealing with thousands (eventually hundreds of thousands) of files, you need tools that are:

⚙️ Options for Uploading to Wasabi

✅ Option 1: Wasabi’s Native Web Interface

Use this only for quick tests or limited image sets.

✅ Option 2: Wasabi Explorer (GUI tool for Windows/Mac)

Download Wasabi Explorer

This is the most robust method for batch uploading TIFFs to Wasabi, and it works across platforms (Windows, macOS, Linux). It also integrates well with scripts and automations.

🔧 Setup Process:

  1. Install rclone

    # On Mac (via Homebrew)
brew install rclone

# On Ubuntu/Debian
sudo apt install rclone

# On Windows
Download from https://rclone.org/downloads/

  2. Configure Wasabi as a remote:

    rclone config

    Follow prompts:

    • Name: wasabi
    • Storage type: S3
    • Provider: Wasabi
    • Region: e.g. us-east-1 or your specific region
    • Endpoint: s3.us-east-1.wasabisys.com or another region-specific endpoint
    • Access Key ID / Secret Access Key: from Wasabi console
    • Use path style: yes

  3. Test the connection:

    rclone ls wasabi:your-bucket-name

  4. Upload a folder of TIFFs:

    rclone copy /local/path/to/folder wasabi:your-bucket-name/path/in/bucket --progress

  5. Optional flags:

    • -checksum: validate file integrity
    • -dry-run: test upload without transferring
    • -transfers=4: parallel file uploads
    • -exclude "*.psd": ignore working files

🔄 Example full command:

rclone copy /Volumes/Archive/Scans/ wasabi:historic-photos/ingest2025/ --progress --transfers=6 --checksum

✅ Option 4: Wasabi S3 CLI (AWS-compatible)

Wasabi is S3-compatible, so you can also use the AWS CLI tools.

  1. Configure Wasabi as a profile:

    aws configure --profile wasabi

    Set:

    • Access Key / Secret
    • Default region: us-east-1
    • Output: json

  2. Add custom endpoint:

    export AWS_ENDPOINT_URL=https://s3.us-east-1.wasabisys.com

  3. Upload folder:

    aws s3 sync /local/path s3://your-bucket-name/path/ --endpoint-url $AWS_ENDPOINT_URL

✅ Best use case: If you’re already familiar with AWS workflows or have integrations/scripts in AWS CLI format.

💡 Best Practice: Uploading + Metadata

(2) Linking Pics.io Assets to the Museum’s CMS: TMS Collections

🎯 Objective:

You want to cross-reference digital assets in Pics.io with physical object records stored in TMS Collections, so museum staff or researchers can seamlessly connect object records and media files.

🔍 Overview of TMS + Pics.io Linkage

About TMS (The Museum System):

This is a two-way soft-linking strategy:

In Pics.io:

In TMS:

🔁 Workflow Diagram:

[ Physical Object ]
     |
     v
[ TMS Record ] <--------> [ Pics.io Asset ]
     ^                        |
     |                        v
[ TMS Object ID ]      [ Custom field: TMS Object ID ]
                     [ Public URL / Internal Asset Link ]

📋 Example

In TMS:

In Pics.io:

🔄 Integration Possibilities

If your institution is open to more automation in future (via APIs or middleware), here are possible next steps:

✅ Summary Recommendations:

Step Action
✅ Store TMS Object ID as metadata in Pics.io for every image
✅ Use Public URLs or Asset links from Pics.io as Media entries in TMS
✅ Use CSV manifests to import metadata in batches to both systems
🚀 Consider API integration later for automation or live cross-referencing
📚 Document mapping standards and file naming conventions to maintain links

Let me know if you’d like:

I’m also happy to help draft SOPs for your staff.

Excellent — let’s go through each of your requests in full detail.

(1) ✅ Example CSV Template for Uploading Assets to Pics.io

When uploading assets to Pics.io, you can import a CSV file that maps each file to associated metadata. Pics.io reads the filename column and applies metadata values to matched files in your connected storage (e.g. Wasabi).

🧾 Sample CSV Structure

file_name tms_object_id title description format_type view_orientation scan_date digitized_by location_shown linked_assets source_url
1987_0034_001_Neg_Front.tif 1987.0034.001 Nitrate Negative – Front Original nitrate negative, front view Nitrate Negative Front 2025-07-10 A. Technician Main Street, Auburn 1987_0034_001_Pos_Front.tif https://app.pics.io/asset/abc123
1987_0034_001_Neg_Back.tif 1987.0034.001 Nitrate Negative – Back Back view of the original negative Nitrate Negative Back 2025-07-10 A. Technician 1987_0034_001_Pos_Back.tif https://app.pics.io/asset/abc124
1987_0034_001_Pos_Front.tif 1987.0034.001 Positive Scan – Front Digitally converted positive (front) Positive TIFF Front 2025-07-10 A. Technician Main Street, Auburn 1987_0034_001_Neg_Front.tif https://app.pics.io/asset/abc125
1987_0034_001_Pos_Back.tif 1987.0034.001 Positive Scan – Back Digitally converted positive (back) Positive TIFF Back 2025-07-10 A. Technician 1987_0034_001_Neg_Back.tif https://app.pics.io/asset/abc126

🔑 Key Notes:

You can import this CSV after uploading TIFFs to Wasabi, and Pics.io will map it to the corresponding files in your library.

(2) ✅ Walkthrough: Configuring Metadata Templates in Pics.io

In Pics.io, you can create custom metadata templates to match the fields relevant to your archive and integrate with your CMS (TMS Collections).

🧭 Steps to Configure Metadata Templates

1. Login to Pics.io

2. Go to: Settings → Metadata Templates

3. Create a New Template

4. Add Fields

Create custom fields to match your CSV structure and TMS metadata needs. Examples:

Field Name Field Type Notes
TMS Object ID Text Field Use this to link back to your CMS
Title Text Field Concise display name
Description Text Area More detailed contextual notes
Format Type Dropdown Controlled vocab: “Nitrate Negative”, “Positive TIFF”, etc.
View Orientation Dropdown “Front”, “Back”, “Spine”, etc.
Scan Date Date Picker Date of digitization
Digitized By Text Field Technician or scanner initials
Location Shown Text Field Extracted from TMS subject/location metadata
Linked Assets Text Field Stores filenames of associated assets
Source URL URL Field Link back to original TMS/eMuseum record

5. Save the Template

You can now apply this metadata template to folders, assets, or groups of assets.

🧠 Tips:

(3) ✅ Examples of Linking Negative & Positive Assets as Separate Records in Pics.io

In a historical photo workflow, you will often have:

There are three good approaches to show this relationship:

🔗 Example 1: Manual Linked Metadata Field

In the metadata field Linked Assets, store the filenames of related scans.

Asset: 1987_0034_001_Neg_Front.tif

{
  "TMS Object ID": "1987.0034.001",
  "Format Type": "Nitrate Negative",
  "View Orientation": "Front",
  "Linked Assets": "1987_0034_001_Pos_Front.tif"
}

Asset: 1987_0034_001_Pos_Front.tif

{
  "TMS Object ID": "1987.0034.001",
  "Format Type": "Positive TIFF",
  "View Orientation": "Front",
  "Linked Assets": "1987_0034_001_Neg_Front.tif"
}

🔗 Example 2: Shared Collection or Folder for Grouping

Create a folder or collection per object or group of linked scans:

Collection: “1987.0034.001 – Main Street”

This lets users browse all related scans visually, even if metadata is separate.

You can also create Smart Folders (via filters) that automatically group assets sharing the same TMS Object ID.

🔗 Example 3: Visual Tags and Comments

Use:

This works well when reviewers or researchers browse one image and need to jump to related views.

🔄 Optional: Linking With URL Shortcuts

If using a public gallery or internal asset viewer, include the URL of the related scan in the metadata.

Example:

You can even make these clickable for your team if viewed in the web UI.

✅ Wrap-Up

To summarize:

Task Tool Output
Uploading TIFFs to Wasabi rclone, Wasabi CLI Fast, scriptable transfers
Metadata Template Setup Pics.io UI Custom fields mapped to TMS and asset needs
Linking Scans Metadata, Smart Folders, Collections Flexible browsing and cross-referencing of views

Would you like:

Happy to assist.

Visual Guide: Adding Metadata & Applying Templates in Pics.io

This guide walks staff through each step of adding metadata and applying a custom metadata template in Pics.io. Screenshots are indicated in brackets; capture these directly from the Pics.io interface during implementation.

1. Log in & Navigate to Your Workspace

  1. Open your browser and go to https://app.pics.io.

  2. Enter your credentials and click Sign In.

  3. From the Dashboard, select your team space (e.g., “Museum Archive”).

    [Screenshot: Pics.io Dashboard with Team Spaces listed]

2. Access Metadata Templates

  1. Click the Settings icon (gear) in the top-right corner.

  2. In the left sidebar, select Metadata Templates under Library Settings.

    [Screenshot: Settings menu highlighting “Metadata Templates”]

3. Create or Edit a Metadata Template

  1. To create a new template, click Add Template.

  2. In the pop-up:

    • Template Name: “Historical Photo Metadata”
    • Description: “Fields for linking TMS and capturing scan details”

  3. Click Create.

    [Screenshot: “Add Template” dialog with fields filled]

4. Add Custom Fields

  1. Within your new template, click + Add Field.

  2. Configure each field:

    Field Label Field Type Options / Notes
    TMS Object ID Text Stores 1987.0034.001
    Title Text Short title of the scan
    Description Text Area Longer notes or captions
    Format Type Dropdown Values: “Nitrate Negative”, “Positive TIFF”
    View Orientation Dropdown Values: “Front”, “Back”
    Scan Date Date Picker Date of digitization
    Digitized By Text Technician initials
    Location Shown Text Place name
    Linked Assets Text Filenames of related scans
    Source URL URL Link back to TMS or public gallery

  3. After adding fields, click Save Template.

    [Screenshot: Metadata Template editor showing the new fields]

5. Applying the Template to Assets

  1. Return to Library view and navigate to the folder containing your uploaded TIFFs.

  2. Select one or multiple assets by checking their thumbnails.

  3. In the right-hand pane, click Metadata.

  4. From the drop-down at the top, choose Historical Photo Metadata.

    [Screenshot: Asset list with several items selected]

    [Screenshot: Metadata pane drop-down showing the template]

  5. Enter metadata values in the fields. For example:

    • TMS Object ID: 1987.0034.001
    • Format Type: Select “Nitrate Negative”
    • View Orientation: Select “Front”
    • Scan Date: 2025-07-10
    • Linked Assets: 1987_0034_001_Pos_Front.tif

  6. Click Save at the bottom of the metadata pane.

    [Screenshot: Filled metadata fields for an asset]

6. Bulk Metadata Import via CSV

  1. In Library view, click Actions → Import Metadata.

  2. Upload your CSV file (structured as per the template).

  3. Map CSV columns to template fields: ensure each file_name maps, e.g., to the File Name field in Pics.io.

  4. Click Start Import and monitor status.

    [Screenshot: Import Metadata dialog with mappings]

7. Verifying & Using Metadata

  1. Use the Filter bar to search by custom fields, e.g., TMS Object ID:1987.0034.001.

  2. Save this as a Smart Folder for quick access: click Save Filter → name it “1987.0034.001 Family”.

    [Screenshot: Filter panel showing search by TMS Object ID]

8. Best Practices & Tips

End of Guide.

Feel free to capture the indicated screenshots from your own Pics.io instance and replace the placeholders. This guide can be printed or shared as a PDF for easy reference.