Kanban Interface: Combining Data from Two Sources

Hmm, you could probably get something working with a Kanban view if you messed with your data enough but I wouldn’t recommend it

The first limitation you’d need to get around is that Kanban columns need to be single selects / user fields, and so to get this working you’d need to have a system to convert your jobs into options for the select field

The next limitation you’d need to get around is needing the ability to put the same candidate into different jobs.  To get that working you’d need to have a system that would help you to duplicate the Candidate record so that you could put it under a different job

---

I’d suggest having these three tables instead:

1. Candidates
2. Jobs
3. Matches, where each record represents a link between a Candidate and a Job

And the Matches table would look something like this:

Hey ​@Miroslav,

I’d suggest following Adam’s suggestion above re: Matches table.

In this case, Matches table would work as a “junction table”. You can check out the video below in why these are so important!

Mike, Consultant @ Automatic Nation

To group job listings with candidates in your Kanban interface, use a many-to-many relationship:

1. Job Listings (Source 1) have a list of Candidate IDs associated.

2. Candidates (Source 2) have a list of Job IDs they are linked to.

For each Job Listing, display the relevant Candidate Profiles in the Kanban column. Use drag-and-drop functionality to move candidates between job listings.

Tools like React DnD or React Beautiful DnD can help with drag-and-drop. Manage data efficiently with Redux or Context API.

This will allow candidates to be mapped to multiple job listings seamlessly.