u/One_Reference612

I’m working on a system that maps emotion vectors into Jungian-style archetypes, and I’d love suggestions on the best methodology/framework for doing this.

I’m working on a system that maps emotion vectors into Jungian-style archetypes, and I’d love suggestions on the best methodology/framework for doing this.

Current setup:

  • I have ~28 normalized emotions: admiration, amusement, anger, annoyance, approval, caring, confusion, curiosity, desire, disappointment, disapproval, disgust, embarrassment, excitement, fear, gratitude, grief, joy, love, nervousness, optimism, pride, realization, relief, remorse, sadness, surprise, neutral

Goal:
Map combinations/intensities of these emotions into archetypes such as:

https://conorneill.com/2018/04/21/understanding-personality-the-12-jungian-archetypes/

  • Explorer
  • Sage
  • Hero
  • Lover
  • Creator
  • Outlaw
  • Caregiver
  • Jester etc.

Right now I’m experimenting with:
emotion → motivational drives → archetypes

Example:

  • curiosity → freedom / understanding
  • fear → safety / control
  • pride → mastery / power

Questions:

  • Is there any established psychological framework for mapping emotions to archetypes/motivations?
  • Would you approach this using:
    • heuristic weighting,
    • embeddings,
    • clustering,
    • latent dimensions,
    • or supervised learning?
  • Are Jungian archetypes even a good structure for this, or should I instead derive emergent archetypes from clustering emotional space?
  • Any papers/books/research areas worth looking into?
  • Any suggestions for making the mappings feel psychologically coherent instead of arbitrary?

I’m especially interested in:

  • affective computing
  • computational psychology
  • personality systems
  • semantic embeddings
  • narrative archetypes
  • latent trait modeling
u/One_Reference612 — 9 days ago
▲ 1 r/spotifyapi+1 crossposts

Spotify API works locally but fails on Vercel — playlists return 0 tracks while Liked Songs works fine

I’m facing a weird Spotify API issue that only happens in production on Vercel.

Locally:

  • playlist fetch works perfectly
  • returns playlist name
  • correct total track count
  • all tracks load properly

On Vercel:

  • Liked Songs collection works correctly
  • playlist metadata loads
  • BUT playlist tracks.total always becomes 0
  • app thinks every playlist is empty

Example:
Locally:

  • Playlist Name: OK
  • Total Tracks: 42
  • Tracks returned: YES

Vercel:

  • Playlist Name: OK
  • Total Tracks: 0
  • Tracks returned: NO
  • “Playlist is empty”

Stack:

  • Python Flask backend
  • Spotify Web API
  • deployed on Vercel serverless functions

Things I already checked:

  • same Spotify account
  • same scopes
  • token exists
  • auth flow succeeds
  • playlist IDs are valid
  • liked songs endpoint works

What’s confusing:

  • only playlist track retrieval breaks
  • metadata still loads
  • issue happens only in production

Possible causes I’m considering:

  • serverless caching/state issue
  • expired/partial token during playlist fetch
  • pagination issue with serverless execution
  • private playlist permissions behaving differently on Vercel
  • API limitations on development mode

Has anyone seen Spotify playlists return tracks.total = 0 only in production/Vercel while working locally?

reddit.com
u/One_Reference612 — 11 days ago