Recued
Menu
← Back to recipes

Retire a person

by recued-core v2 49 views 2 installs

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.

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.

Retire a person
This recipe

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.

pack:photo-attributionrosterpeoplecleanup
by recued-core pinned v2

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v2

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v2

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.

photosrosterpeople
by recued-core pinned v1

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v1

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v2
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.

pack:photo-attributionrosterpeoplephoto
by recued-core pinned v1

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v2

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.

pack:photo-attributionrostercsvimport
by recued-core pinned v3

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.

pack:photo-attributionrostercsvexport
by recued-core pinned v1

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v1

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v2
Skip a photo
Background automation

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v2
Send one person their photos
Background automation

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v2

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.

pack:photo-attributionphotofacedelivery
by recued-core pinned v1
View pack details, dependencies, and permissions →

What this does

Takes one person off the roster. They stop being matched by future scans, stop counting toward the roster total, and stop appearing on the send screen.

Nothing is deleted. Every photo they are already attached to keeps its record and its history, and anything already sent stays sent. This is the difference between retiring and deleting, and it is why retiring is the safe move.

Anything of theirs still queued to go is released at the same time, so a retired person cannot sit on the send screen forever.

When you need it

A duplicate from a renamed reference photo. The file name is the identity, so renaming maggie.jpg to margaret.jpg makes a second person rather than renaming the first. The original keeps the history and is never matched again — retire it.

A face that should not have been added. A reference photo named after the camera, like IMG_4821.jpg, becomes a person called IMG_4821. Retire it and fix the file name.

Somebody who should no longer be sent to. Retiring is enough; you do not have to remove them from your records to stop the sending.

Bringing somebody back

There is no un-retire button. Their record is still there with everything on it, and the Data screen can set the status back to active if you need them again.

⚠ Move their reference photo out of the roster folder too

Retiring does not touch the folder. Leave the file there and every future scan tries to add them back, is refused because the retired record still holds their key, and counts one under people that could not be added. They are not re-added and no duplicate appears — but that count stays stubbornly above zero, and their face keeps being recognised without ever being attributed to anybody.

Move or rename the file and both stop.

How it works 12 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (12 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
■ profile_ref template
Generate text from a template
◆ queued recued-core.photo-attribution.attributed_result.search
Search attributed result on photo attribution
■ rows default
Apply default
◆ released recued-core.photo-attribution.attributed_result.update
Update attributed result on photo attribution
◆ retired recued-core.photo-attribution.face_profile.update
Update face profile on photo attribution
■ release_failed filter
Filter by condition
■ release_failed_n count
Count items in release failed
■ released_n count
Count items in rows
■ card to_summary
Format results as a summary card
▼
Output
summary card
Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

reason setting =
profile id setting = [object Object]

Uses (4 operations)

Pack operation Get face profile on photo attribution recued-core.photo-attribution.face_profile.get
Pack operation Search attributed result on photo attribution recued-core.photo-attribution.attributed_result.search
Pack operation Update attributed result on photo attribution recued-core.photo-attribution.attributed_result.update
Pack operation Update face profile on photo attribution recued-core.photo-attribution.face_profile.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: attributed_result.search · No approvalWrite: attributed_result.update · No approvalWrite: face_profile.update · No approval

About

Tags

pack:photo-attributionrosterpeoplecleanupphoto

Details

12 steps 2 configurable settings recipe_id: retire-person