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.
Re-describe a person
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.
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 “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.
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.
What this is for
You changed someone's name and their lines still carry the old one. This rebuilds the stored names on their photos and queues those photos to be written again.
Change the name first, then run this.
It rewrites whole lines, including other people's
A photo with three people gets a completely new line, not the old one with a name swapped. The wording changes, not only the name — the line was written as one piece. On a large event that is a lot of rewriting, and it costs one call to the model per photo.
Approved photos are left alone
Photos already approved are not touched, even if they carry the old name, and are counted separately. Somebody signed those off and silently un-approving them would throw that away.
To redo an approved one, skip it and scan again — so the decision is yours and visible.
⚠ Could not rebuild should be zero. Anything there is a photo whose people could not be looked up; it keeps the old name and will not be rewritten.
It discards lines you wrote yourself
A photo still waiting (not yet marked ready) has its line thrown away and written again from scratch — including a line you typed by hand. That is on purpose: the reason to re-describe somebody is that their name changed, so every line naming them is now wrong, and yours is no more correct than the one Recued wrote.
Photos you have already approved are left alone, and the card counts them. So if you have corrected a line and want to keep it, mark that photo ready before re-describing anyone in it.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (40 steps)
profile
recued-core.photo-attribution.face_profile.get
Get face profile on photo attribution
found
compare
Check if profile record id has data
guard
guard
Stop if found equals
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
roster_sorted
sort
Sort by friendly_name
profile_ref
template
Generate text from a template
mine
recued-core.photo-attribution.attributed_result.search
Search attributed result on photo attribution
their_refs
pluck
Extract photo_ref from each item
uniq_refs
unique
Remove duplicates from
stripped
replace
Replace text in item
ids
map
Extract from each item
photos
recued-core.photo-attribution.photo.get
Get photo on photo attribution
p0
map
Extract from each item
readable
filter
Filter by condition
affected
filter
Filter by condition
a0
recued-core.photo-attribution.attributed_result.search
Search attributed result on photo attribution
a1
map
Extract from each item
a2
pluck
Extract profile_ref from each item
a3
map
Extract from each item
a4
filter
Filter by condition
a5
map
Extract from each item
a6
pluck
Extract friendly_name from each item
a7
map
Extract from each item
a8
join
Join items with ", "
refreshed
map
Extract from each item
resolvable
filter
Filter by condition
reset
recued-core.photo-attribution.photo.update
Update photo on photo attribution
reset_failed
filter
Filter by condition
reset_failed_n
count
Count items in reset failed
queued_n
count
Count items in resolvable
affected_n
count
Count items in affected
their_total
count
Count items in uniq refs
unresolved_n
math
Calculate affected n minus queued n
skipped_n
math
Calculate their total minus affected n
card
to_summary
Format results as a summary card
▼
Output
summary
card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
profile id
setting
=
[object Object]
Uses (6 operations)
Pack operation
Get face profile on photo attribution
recued-core.photo-attribution.face_profile.get
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
Search attributed result on photo attribution
recued-core.photo-attribution.attributed_result.search
Pack operation
Get photo on photo attribution
recued-core.photo-attribution.photo.get
Pack operation
Update photo on photo attribution
recued-core.photo-attribution.photo.update
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
Write
Pack
Photo Attribution
external change
Read: face_profile.get · No approvalRead: face_profile.search · No approvalRead: face_profile.count · No approvalRead: attributed_result.search · No approvalRead: photo.get · No approvalWrite: photo.update · No approval