Normalize ApiMetadata and Organizations collections

[kyyberi]

ApiMetadata collection contains organization (and organization contact) data, while there already is an organization collection.

Goal

All data is stored in database once or in one collection only.

Definition of done

• Organization fields exist only in Organizations collection
• API Metadata object contains organizationId field
  • organizationId field is a string, containing the ID of an Organization document
• API Metadata UI displays fields from the related organization document, if connected
• Schema migration has been defined from old database structure to new changes

[marla-singer]

@bajiat Interested

[bajiat]

@marla-singer Assigned to you. Can you please estimate?

[marla-singer]

@bajiat Done

[marla-singer]

@bajiat @kyyberi We need to migrate the data from the old structure to a new one, if possible.

1. What to do with old organization data from ApiMetadata document?
   We can archive the data but a user will not have access to the data.
2. Do we need to display old data? How can it be realized?
   We can't create a new organization based on ApiMetadata document because organization needs URL just as ApiMetadata doesn't provide URL

[marla-singer]

I've tested migration and feature on local. Described the different cases and results.

Case №1

• ApiMetadata contained information about Contact and Service
• API was connected

Result after migration

• Organization block has information about connected organization
• Contact & Service information are still here

Case №2

• ApiMetadata contained information about Contact and Service
• API was not connected

Result after migration

• Contact & Service information are still here
• Organization block is empty as before

Case №3

• ApiMetadata contained information about Organization & Contact
• API was connected

Result after migration

• Contact information is still here
• Organization block has information about connected organization
• Old information from organization block is not displayed and is stored in database

Case №4

• ApiMetadata contained information about Organization & Contact
• API was not connected

Result after migration

• Contact information is still here
• Organization block isn't displayed and information is stored in database

Case №5

• ApiMetadata didn't contain information
• API was connected

Result after migration

• Contact & service blocks are empty as before
• Organization block has information about connected organization

Case №6

• ApiMetadata contained information about Contact and Service
• API was not connected

Result after migration

• Nothing happened

[marla-singer]

@bajiat If everything works as expected, I will label my PR is ready

[bajiat]

@marla-singer
We should not create an organization based on the old data on the API Metadata tab, you are definitely right about this.
Where do you store the old data from metadata tab after migration, if there is no organization? I'm not sure it is needed, if there is no way to see or to take any actions about it.