Music Database Join Question

Hey guys, I am about to embark on a project to convert an old database made in a different system (filemaker) to bubble. It is a music database which contains Songs. Each song contains a list of musicians involved on that song, their role and their share of the song. So three main tables 1) Songs 2) Musicians 3) Roles. The shares(%) are currently stored on the JOIN TABLE that links the writers to the songs. So for example the join table looks something like this:

Screenshot 2021-02-07 at 22.46.11

(so in this example SongID “1” would have two musicians associated with it. SongID “2” only has one musicians associated with it)

The portal (“repeating group”) then shows the relevant details based on when the current SongID matches the SongIDs on the join table. Hope that makes sense.

My question is what is the best way to achieve this in Bubble? Do i continue to use this “Join Table” approach or does bubble hope I do things differently? Ie no uniqueID numbers and no join tables - just connected fields and the use of ‘list’ fields? I’ve read lots of posts on this forum but i am still not clear what is the best approach. For example, if i use lists, then where would I store the “Share%” data? or maybe i also want to add a “notes” field, which may contain info specific to that musician on that particular song.

The secondary question is one of compatibility… i’m going to have to, at some point, import all the data from my current system to the new bubble one. (over 1000 songs). If i switch to a non join-table approach would importing from old database then become a major headache? Will it be easiest to simply copy the structure & data used on previous database including all the unique IDs?

I’ll really appreciate any help given.

ok so today i’ve got a little further with this, although still just experimenting really…

Currently I still have a join-table, but i was able to lose the custom ID’s (ie Primary/Foreign keys). I keep reading about how this is what bubble prefers, and it seems to work fine. So as it stands I have a join table, but no keys - bubble is handling that nicely for me. :slight_smile:

My data specific to the relationship (such as “shares”) is stored on this join table too. I think this is the correct thing to do, but again not 100% sure. [but it is working]

I think i’m now on the right lines, but would appreciate someone letting me know for sure.

As to how i’m going to import the previous records without using the keys, i have no idea. I guess i can only keep experimenting and gradually figuring it out.