55966ba5ec
Add ID field to Artist and Song structs in the agents package. When resolving similar artists and top songs, the provider now uses a three-phase lookup: 1. Direct ID match (if agent returns internal Navidrome IDs) 2. MBID exact match (if MusicBrainz ID is available) 3. Fuzzy name/title match (existing behavior) This enables agents to return more precise matches when they have access to internal database IDs, while maintaining backward compatibility with name-based matching. |
||
|---|---|---|
| .. | ||
| deezer | ||
| lastfm | ||
| listenbrainz | ||
| spotify | ||
| agents.go | ||
| agents_plugin_test.go | ||
| agents_suite_test.go | ||
| agents_test.go | ||
| interfaces.go | ||
| local_agent.go | ||
| README.md | ||
| session_keys.go | ||
| session_keys_test.go | ||
This folder abstracts metadata lookup into "agents". Each agent can be implemented to get as much info as the external source provides, by using a granular set of interfaces (see interfaces).
A new agent must comply with these simple implementation rules:
- Implement the
AgentName()method. It just returns the name of the agent for logging purposes. - Implement one or more of the
*Retriever()interfaces. That's where the agent's logic resides. - Register itself (in its
init()function).
For an agent to be used it needs to be listed in the Agents config option (default is "lastfm,spotify"). The order dictates the priority of the agents
For a simple Agent example, look at the local_agent agent source code.