Create organization using website if not found

[yeganathan18]

Changes proposed ✍️

What

🤖 Generated by Copilot at a1a1139

This pull request refactors the logic for querying and creating organizations by website domain across different layers of the application. It also adds a feature to automatically assign members to organizations based on their email domains. The main files affected are organizationRepository.ts, organization.repo.ts, batchCreateOrganizations.ts, memberService.ts, and organizationService.ts.
​

🤖 Generated by Copilot at a1a1139

Sing, O Muse, of the skillful refactorings and features
That the valiant developers wrought in the organizationService
How they made it find or create by domain, with swift and graceful queries
And how they linked the members to their rightful organizations

Why

How

🤖 Generated by Copilot at a1a1139

• Simplify and standardize the domain normalization and comparison logic for finding and creating organizations by using the websiteNormalizer utility function from the @crowd/common package (link, link, link, link)
• Rename the findByDomain method to findOrCreateByDomain in the organizationService and organizationRepository classes to reflect the new functionality of creating a new organization if none is found by the domain (link, link, link)
• Update the calls to the organizationService method in the memberService classes to use the new findOrCreateByDomain method and assign members to existing or newly created organizations based on their email domains (link, link)
• Add the fallback logic for creating a new organization with the domain as its name and website in the organizationRepository classes in the backend and data_sink_worker folders (link, link)
• Remove the unnecessary variables for the different variations of the domain in the organizationRepository class in the data_sink_worker folder (link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screehshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.

[yeganathan18]

I'd suggest that we merge and execute the website normalizer migration scripts first, and then proceed with this. Since the current PR discards iLike operations and uses an exact domain match search, helps in improving performance.

[epipav]

included 2 comments