Integrations overwriting existing organization data, displayName for organizations

[epipav]

Changes proposed ✍️

• memberExists function now also returns existing organizations of a member - This helps with upserting existing & incoming organizations of a member through integrations
• Organizations new field: displayName - We now use this field to do name updates on an organization via user. This is for ensuring edited organization names to be considered as the same organization. Since we're checking the existence of an organization by name, when user edits the name field, incoming data was creating new organizations - to prevent this now we're using displayName

What

🤖 Generated by Copilot at 1d71d95

This pull request adds a new feature that allows organizations to have a display name that is different from their name. The display name is used in the frontend to show the organization's label. The pull request modifies the organization model, table, repository, service, and test files in the backend, as well as the organization model, component, and page files in the frontend. It also includes migration scripts to add and drop the displayName column in the database.
​

🤖 Generated by Copilot at 1d71d95

We're changing the name of the orgs, me hearties
We're adding a displayName to the table
We're updating the models and the components
We're heaving away on the count of three

Why

How

🤖 Generated by Copilot at 1d71d95

• Add displayName column to organizations table and organization model to allow organizations to have a label different from their name (link,link,link)
• Assign displayName the same value as name by default in organizationRepository.create and organizationService.createOrUpdate methods (link,link)
• Update organizationRepository.update method to include displayName in the data object (link)
• Add displayName to the select clause of SQL queries in organizationRepository.findAndCountAll, organizationRepository.findAllAutocomplete, and organizationRepository.findById methods (link,link,link)
• Add textContains operator for displayName in the where clause of SQL query in organizationRepository.filter method (link)
• Use displayName instead of name to match the query and populate the label in organizationRepository.findAllAutocomplete method (link,link)
• Add displayName property to organization objects in test cases for memberRepository, memberService, and organizationRepository (link,link,link,link,link,link,link,link,link)
• Remove unnecessary deletion of organizations property from member objects in test cases for memberRepository and memberService (link,link,link)
• Add getOrganizationIds method to memberRepository to query the database for organization ids of a given member (link)
• Modify memberRepository.findById method to return a plainMember object that includes the organizations property as an array of organization ids (link)
• Modify organization.name expressions to organization.displayName in frontend components that show the organization label, such as member-organizations, organization-form-details, organization-name, organization-view-header, and organization-form-page (link,link,link,link,link,link,link,link,link)
• Modify name field to displayName field in organization-model.js in the frontend (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.

[joanagmaia]

I think there are 2 places still missing to update:

• In dashboard-organization-item line 31
• In member-form-details in line 133. This is where in member's form we are adding organizations to the member and if they don't exist, we create a new organization

Another thing that is currently failing and needs update is in organization-form-page. You've updated the forms to read from displayName. But as you mentioned when creating an organization you still need to create it with name.
So in method onSubmit on that file, you should add the property name if you are in the create form. Probably on line 357, below ...formModel.value, you can add name: formModel.value.displayName if isEditPage.value === false and add displayName: formModel.value.displayName if isEditPage.value === true