Fix: Added organization membership sample data for API_ADMINISTRATOR_USER

[PratapRathi]

What kind of change does this PR introduce?
This PR will add the organization_memberships records for API_ADMINISTRATOR_USER_EMAIL_ADDRESS user.

Issue Number:
Fixes #3178

Snapshots/Videos:

If relevant, did you update the documentation?
N/A

Summary
Does this PR introduce a breaking change?
No

Checklist

CodeRabbit AI Review

• I have reviewed and addressed all critical issues flagged by CodeRabbit AI
• I have implemented or provided justification for each non-critical suggestion
• I have documented my reasoning in the PR comments where CodeRabbit AI suggestions were not implemented

Test Coverage

• I have written tests for all new changes/features
• I have verified that test coverage meets or exceeds 95%
• I have run the test suite locally and all tests pass

Other information
N/A

Have you read the contributing guide?
Yes

Summary by CodeRabbit

• New Features
  • Enhanced the data import process to automatically assign a designated administrator role to each organization.
  • Improved error handling now validates administrative settings during data import to help ensure consistent and reliable organization management.

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

1. We don't merge PRs with poor code quality.
   1. Follow coding best practices such that CodeRabbit.ai approves your PR.
2. We don't merge PRs with failed tests.
   1. When tests fail, click on the Details link to learn more.
   2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
   3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[coderabbitai]

Walkthrough

The pull request updates the data insertion process within the insertCollections function in src/utilities/loadSampleData.ts. It adds logic to retrieve an administrator's email from environment variables and verifies the existence of that user in the database. If the user exists, the function constructs organization membership entries for the administrator; if not, appropriate error messages are logged. No changes were made to the public interface of the module.

Changes

File Path	Change Summary
src/utilities/loadSampleData.ts	Added logic within insertCollections to retrieve the admin email from env, query the database for the user, create organization membership entries if found, and log errors if not.

Sequence Diagram(s)

sequenceDiagram
    participant F as insertCollections
    participant E as Environment Variables
    participant D as Database
    participant L as Logger

    F ->> E: Retrieve Admin Email
    E -->> F: Return email value / undefined
    alt Email is provided
        F ->> D: Query user by email
        D -->> F: Return user record / not found
        alt User exists
            F ->> D: Create organization membership entries
        else No user found
            F ->> L: Log error "User not found"
        end
    else Email not provided
        F ->> L: Log error "Email not defined"
    end

Loading

Possibly related PRs

• elevate existing initial administrator user's role on api startup #2875: Modifies the administrator role in the database, directly relating to the enhanced administration linking logic.
• Fixes #2841: Invalid emails and names in import:sample-data script #3160: Also updates insertCollections for organization data handling, indicating a connection with handling user interactions and date management.
• fixed : #2841 NoMongo: Create an equivalent sample database for importation by the setup script  #3118: Introduces changes to the insertCollections function for varied data types, which is directly related to modifications for managing organization memberships.

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

• palisadoes
• gautam-divyanshu

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

1. We don't merge PRs with poor code quality.
   1. Follow coding best practices such that CodeRabbit.ai approves your PR.
2. We don't merge PRs with failed tests.
   1. When tests fail, click on the Details link to learn more.
   2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
   3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
2. Read the CONTRIBUTING.md file make

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 40 lines in your changes missing coverage. Please review.

Project coverage is 43.85%. Comparing base (51c11d2) to head (3469268).
Report is 1 commits behind head on develop-postgres.

Files with missing lines	Patch %	Lines
src/utilities/loadSampleData.ts	0.00%	40 Missing ⚠️

Additional details and impacted files

@@                 Coverage Diff                  @@
##           develop-postgres    #3208      +/-   ##
====================================================
- Coverage             43.90%   43.85%   -0.06%     
====================================================
  Files                   455      455              
  Lines                 33644    33684      +40     
  Branches                664      664              
====================================================
  Hits                  14772    14772              
- Misses                18868    18908      +40     
  Partials                  4        4              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Actionable comments posted: 3

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 51c11d2 and 3469268.

📒 Files selected for processing (1)

• src/utilities/loadSampleData.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Run tests for talawa api
• GitHub Check: Analyse Code With CodeQL (typescript)