Skip to main content

CameraHub Tagger

CameraHub Tagger is a companion command-line app for CameraHub to tag JPG scans of negatives with EXIF metadata from the CameraHub API. This means you can organise your film scans in a digital photo management app with full metadata.

To use CameraHub Tagger, you must already have entered your cameras, lenses, films and negatives into CameraHub. When you scan your negatives, name them consistently like {FILM}-{FRAME}-IMG0001.jpg (for example 45-12-IMG0001.jpg is frame 12 on film 45).

Run CameraHub Tagger in the same directory. CameraHub Tagger will attempt to match the JPGs with the negatives by using the filename (it will ask you if it can't figure it out). It will then generate a unique ID for that scanned JPG to tie it conclusively to the negative. Once the link is made, CameraHub Tagger will retrieve all data about that negative, film, lens and camera and use it to generate EXIF metadata, the same as digital cameras do. It is safe to run CameraHub Tagger multiple times on the same files, as only changed tags are written.

When your images have been tagged, any digital photo app will read and display these tags in the same way as digital photos.

Installation

Install from PyPI with Pip:

pip install camerahub-tagger

This installs a tagger binary in your $PATH.

Usage

tagger [-h] [-r] [-a] [-y] [-d] [-f FILE] [-p PROFILE]

-h --help

Display help message and exit

-r --recursive

Search for scans recursively from current directory

-a --auto

Don't prompt user to identify scans, only guess based on filename

-y --yes

Accept all changes without confirmation

-d --dry-run

Don't write any tags to image files

-d --update-only

Only update tags which have previously been written. Don't make any new Scan records in CameraHub.

-f --file FILE

Image file to be tagged. If not supplied, tag everything in the current directory.

-p --profile PROFILE

CameraHub connection profile. Default: prod.

-c --clear

Clear existing EXIF metadata from the image file.

Config

CameraHub Tagger needs some basic connection details to connect to CameraHub. On first run, it will ask for credentials for CameraHub and save them for future use.

If you need multiple profiles (e.g. if you have multiple users, or you need to connect to a development instance of CameraHub) you can configure the extra profiles manually by editing ~/camerahub.ini and adding more blocks.

The names of each profile are arbitrary, but CameraHub Tagger will automatically use the prod profile unless you override it with the --profile option. Here's an example:

[prod]
server = https://camerahub.info/api
username = anseladams
password = yosemite

[dev]
server = https://dev.camerahub.info/api
username = annieleibovitz
password = johnandyoko

[local]
server = http://127.0.0.1:8000/api
username = admin
password = admin

Metadata

Release files for camerahub-tagger 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for camerahub-tagger 0.6.0
File Size Uploaded Provenance
camerahub_tagger-0.6.0.tar.gz 9.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for camerahub-tagger 0.6.0
File Interpreter ABI Platform
camerahub_tagger-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 19.8 kB

Release files / camerahub_tagger-0.6.0.tar.gz

Download URL camerahub_tagger-0.6.0.tar.gz
Size 9.5 kB
Tags Source
SHA-256 checksum
How to use checksums
d839945d1cfea071a3d8e9a3bd2b242c7870a6003dbf03b477a0470d27444874
BLAKE2b-256 checksum
How to use checksums
90ae5dd943edea2f3bd80f0099ca1a6b3c36a524a9836230f5c567a41a6ba35d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.4.2 CPython/3.10.11 Linux/5.15.0-1037-azure

Release files / camerahub_tagger-0.6.0-py3-none-any.whl

Download URL camerahub_tagger-0.6.0-py3-none-any.whl
Size 10.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3b81cfd899a68311737de643faa8cb2537ad5e21856add442af48963d0d2dd03
BLAKE2b-256 checksum
How to use checksums
02d74711843d52197be45dd05fb03e18eef5929fb5bb79f597c8bd615641f5c7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via poetry/1.4.2 CPython/3.10.11 Linux/5.15.0-1037-azure

Security for camerahub-tagger 0.6.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page