Connecting tables to a big collection

Hi all, I’m struggling figuring out how to come up with a better plan to connect lots of tables to a large collection.

I have created a collection which has approximately 100 items, each is a profile for an individual athlete. I want each profile to have a separate tables, one for their professional career and one for their college career. Obviously, each individual will have different years and different data, so there will be 200 unique tables.

As far as I can tell, the only way to do this is by creating and connecting 200 other different dataset collections for each unique table. Obviously, this is a huge amount of work and seems needlessly complicated for what I need to achieve. If that’s the case, I would rather avoid using dataset collections at all and just make regular pages for each player. But if it can be done more efficiently, I would much rather keep the collection.

My question is if there’s a more efficient way to do what I’m trying to do. Ideally, I would only have to create 1 or 2 large collections for all of this data and then somehow ration fields within the 1/2 collections to each player or table, but I don’t even know if anything like that is possible.

Thanks in advance

Depending on how you are storing your data in datasets, you can just display logged in users content or members only content without code as shown here.
https://support.wix.com/en/article/filtering-database-content-displayed-on-your-page

To get it by logged in user then you can see how to do this in previous forum posts like these here.
https://www.wix.com/corvid/forum/community-discussion/solved-get-any-data-from-wixusers
https://www.wix.com/corvid/forum/community-discussion/solved-get-current-data-value-based-on-current-user-login?origin=member_posts_page

Not sure if you understood my question, because my site doesn’t have users or members. When I mentioned athlete profiles, I’m not talking about user pages. An athlete profile is simply an item in the data collection with a unique page. Sorry if I’m not getting the terminology right because I’m new to data collections.

Okay so the athletes are not going to be viewing it as their own pages, so why not have a look at using reference fields for this.

You can see examples here that will help you with it.
https://support.wix.com/en/article/about-reference-fields-in-database-collections
https://support.wix.com/en/article/displaying-content-from-multiple-database-collections-using-reference-fields-4034931
https://support.wix.com/en/article/about-referencing-multiple-items-in-one-field
https://support.wix.com/en/article/working-with-multiple-item-reference-fields

You can query them in code as shown here in the Wix Data API.
https://www.wix.com/corvid/reference/wix-data.html
https://www.wix.com/corvid/reference/wix-data.WixDataQuery.html
https://www.wix.com/corvid/reference/wix-data.WixDataQuery.html#include
https://www.wix.com/corvid/reference/wix-data.html#queryReferenced

Another option would be to use conditional dropdowns so that the first dropdown the user will choose the athlete, then you can have the second dropdown choosing a year etc.

You can have a read of it here that does not use code.
https://support.wix.com/en/article/filtering-content-based-on-user-selection

You can see this example here about filtering repeaters and cascading dropdowns here, along with other examples on how to search too.
https://www.wix.com/corvid/example/mega-search
https://www.wix.com/corvid/example/cascading-form

There are many previous posts about filtering with dropdowns if you use the search function.
https://www.wix.com/corvid/forum/community-discussion/filter-table-from-dropdown-menu-solved
https://www.wix.com/corvid/forum/community-discussion/repeater-dropdown-filter