Use “See what has been delivered” in Recued. Show who has received which photo and when, one row per person per picture, with the message it arrived under. It reads information without changing anything.
See what has been delivered
Use “See what has been delivered” in Recued. Show who has received which photo and when, one row per person per picture, with the message it arrived under. It reads information without changing anything.
Complete workflow
Photo Attribution
16 pinned recipes
Use Photo Attribution in Recued to match one event's photos to the people you know, write a warm line for each picture, review them, and send everyone their own. Faces are matched on your machine; your photos are never copied; sending asks first. First install two programs on the server: face_recognition (pipx) and libvips (brew install vips). Then allow their actions on each tool pack's Access tab. Open “Scan an event folder” for the rest of the setup.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Scan an event folder” in Recued. Compare every photo in one event folder against the people you know, and record who appears in each picture. Photos stay where they are and are never copied. Matching happens on your own machine.
Use “Write the photo lines” in Recued. Look at each scanned photo and write one warm line naming the people recognised in it. A small copy with its embedded details removed is what the model sees, and the original is never sent. Run it again until the queue is empty.
Use “The roster” in Recued. See everyone Recued can recognise, whether each person can actually be written to, and who has been retired — and open any of them from here, which is the only way in to a person.
Use “Review photos before sending” in Recued. List the photos waiting for a look, with the line that will arrive alongside each one and the names it was written for. Open a photo to approve it, rewrite the line, or leave it out.
Use “Review one photo” in Recued. See the picture itself beside the names Recued matched in it, correct the line it wrote, and say whether it is ready to send — the one place a wrong name or a wrong sentence can be caught before it reaches somebody.
Show all 16 recipes
Use “Look at one person” in Recued. See who a roster entry actually is — their reference photo shown from your own folder, beside the name and address Recued will use for them — so a wrong or duplicated face is something you can see rather than guess at.
Use “Set someone's details” in Recued. Fill in an email address and the name that messages should use for one person on your roster. A field left blank keeps what is already there rather than clearing it. The key derived from their reference photo cannot be changed.
Use “Retire a person” in Recued. Take somebody off the roster without deleting anything they are attached to — a duplicate left behind by a renamed reference photo, or someone who should not be sent to any more. Their photos stay on record; they simply stop being matched and stop being sent to.
Use “Import the roster (CSV)” in Recued. Add everyone to the roster from a spreadsheet in one go — their key, the name messages should use, and their email address — instead of typing each person in after the first scan.
Use “Export the roster (CSV)” in Recued. Copy out everyone on the roster as a spreadsheet, or - on an empty roster - get the column headings the importer expects, so you can fill them in and import the list instead of typing it.
Use “See who is ready to receive” in Recued. List everyone with approved photos waiting, and separately everyone recognised who has no email address yet. Send each person from here. Nobody is dropped quietly, because a missing address is the usual reason a photo never arrives.
Use “Re-describe a person” in Recued. After changing someone's name, rebuild the stored names on their photos and queue those photos to be written again. Photos already approved are left alone and counted, because somebody signed those off.
Use “Skip a photo” in Recued. Leave one photo out of the sending queue and release everyone who was waiting on it. Their other photos are untouched, so this cancels one picture for everyone in it rather than cancelling a person.
Use “Send one person their photos” in Recued. Send one person a single message carrying every photo of them that has been approved. A fresh copy of each picture is made with its embedded details removed, and that copy is what travels.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
What this shows
One row per person per photo — who received which picture, when, and under which message. This is the ledger the other screens do not keep: Review photos asks what needs your judgement, this asks what has actually gone out.
Why it is not a column on the photo
A photo goes to everyone in it, so it can be delivered to one person and still waiting on another who has no address yet. Sent-ness belongs to the pairing of a photo and a person, which is what each row here is.
Reading it
Still waiting counts pairings that are approved and addressed but not yet sent, plus any waiting on an email address. Left out counts photos you skipped, which release everyone who was queued for them.
⚠ Two hundred rows at a time. A long event with many people will have more pairings than that; narrow by status to see the rest.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (21 steps)
links
recued-core.photo-attribution.attributed_result.search
Search attributed result on photo attribution
rows
default
Apply default
shown_n
count
Count items in rows
roster_all
recued-core.photo-attribution.face_profile.search
Search face profile on photo attribution
roster_total
recued-core.photo-attribution.face_profile.count
Count face profile on photo attribution
roster_got
count
Count items in roster all records
roster_whole
compare
Check if roster total count equals roster got
roster_guard
guard
Stop if roster whole equals
roster_indexed
map
Extract from each item
l0
map
Extract from each item
l1
replace
Replace text in item photo ref
l2
map
Extract from each item
l3
recued-core.photo-attribution.photo.get
Get photo on photo attribution
l4
map
Extract from each item
l5
filter
Filter by condition
entries
map
Extract from each item
sent_total
recued-core.photo-attribution.attributed_result.count
Count attributed result on photo attribution
pending_total
recued-core.photo-attribution.attributed_result.count
Count attributed result on photo attribution
skipped_total
recued-core.photo-attribution.attributed_result.count
Count attributed result on photo attribution
table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
▼
Output
summary
card
table
table
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
status
setting
=
sent
Uses (5 operations)
Pack operation
Search attributed result on photo attribution
recued-core.photo-attribution.attributed_result.search
Pack operation
Search face profile on photo attribution
recued-core.photo-attribution.face_profile.search
Pack operation
Count face profile on photo attribution
recued-core.photo-attribution.face_profile.count
Pack operation
Get photo on photo attribution
recued-core.photo-attribution.photo.get
Pack operation
Count attributed result on photo attribution
recued-core.photo-attribution.attributed_result.count
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.
What it's allowed to do
Read
Pack
Photo Attribution
read-only
Read: attributed_result.search · No approvalRead: face_profile.search · No approvalRead: face_profile.count · No approvalRead: photo.get · No approvalRead: attributed_result.count · No approval