core(db): add a polymorphic weblinks table #82

New issue

Open

opened 2025-09-24 12:24:26 +00:00 by chartgerink · 0 comments

chartgerink commented

2025-09-24 12:24:26 +00:00

Owner

In order to store weblinks that are related to a profile, organization, or other entity where we may want to display it, we need a table to store them in.

This could be similar to the polymorphic invitations table, where invitations can be for various sources. In essence, the benefit of setting this up is that we would have a flexible table to store URLs in that are connected to other entities in the overall RE universe.

Concrete example: A person may want to store any number of links in relation to their profile. Mastodon, ORCID, tiktok. The order saved is the order displayed, providing some additional control. Same may be said for organizations (especially given that ROR provides links).

This is critical to maintain feature parity for 2.0. We do not need to immediately allow many links to be added, at least one to start.

In order to store weblinks that are related to a profile, organization, or other entity where we may want to display it, we need a table to store them in. This could be similar to the polymorphic `invitations` table, where invitations can be for various sources. In essence, the benefit of setting this up is that we would have a flexible table to store URLs in that are connected to other entities in the overall RE universe. Concrete example: A person may want to store any number of links in relation to their profile. Mastodon, ORCID, tiktok. The order saved is the order displayed, providing some additional control. Same may be said for organizations (especially given that ROR provides links). This is critical to maintain feature parity for 2.0. We do not need to immediately allow many links to be added, at least one to start.