record status with person-matching meetings

2026-02-21 16:03:56 -07:00
parent 877df0a0b4
commit 5547148aa3
3 changed files with 10 additions and 3 deletions
@@ -180,6 +180,8 @@ Phase 1.4:
  - [X] Store in a new partner table named profile_embedding with the profile ID and with the embeddings as a comma-separated vector string
  - [X] For anyone with the generateEmbeddings flag on their profile: call to OpenAI to get their embedding vector when the flag is set, and also when a profile with that flag is changed.
  - [X] Allow blank value for embedding and hard-code their vector as the "data.empty.embedding" value from the test/embedding-empty-string.json file
+  - [x] Allow organizers with generateEmbeddings flag to select from their list of contacts, and then hit a button to "Check for Profile" that takes them to a screen which will check each of those contacts for a valid profile, one-by-one, and give a report. Each contact should have a link to the DID view so they can see that person's contact info.
+
 - [ ] Implement matching algorithm
  - [X] Meeting organizer can trigger a pairing session
  - [ ] Allow attendees to be excluded
@@ -187,12 +189,15 @@ Phase 1.4:
  - [x] Calculate similarity scores between all pairs
  - [x] Create pairing algorithm (maximize total similarity)
  - [ ] Create "do not pair" groups
- [ ] Basic matching endpoint
+
+- [x] Basic matching endpoint
  - [x] POST endpoint for organizer to trigger matching
  - [x] Return list of pairs with similarity scores
+
 - [x] Simple results display
  - [x] Show matched pairs to attendees
  - [x] Assign numbers to each pair
+
 - [ ] Automated Testing

 **Validation:** Organizer can trigger matching, and all attendees can see AI-generated pairs with reasonable similarity