Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Organizational Record Collection - Model #1349

Open
david-rocca opened this issue Feb 21, 2025 · 0 comments
Open

Implement Organizational Record Collection - Model #1349

david-rocca opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
Backend user story Issues that follow user story format in order to describe community needs

Comments

@david-rocca
Copy link
Collaborator

User Story

The CVE User Registry service needs to maintain information about organizational affiliations and associated metadata.

Acceptance Criteria

A mongoose collection has been defined with the following Items:

  • Org Metadata
    • ID (UUID)
    • Long Name (String)
    • Short Name (String)
    • Aliases (Array of Strings)
    • CVE Program Organization Function (Enum)
    • ReportsTo
      • Link to organization that current org reports to
      • Relationship
    • Oversees
    • List of organizations this oversees
    • root_or_rlr
    • Users (List of users)
    • Charter / Scope (URL)
    • Disclosure Policy (URL)
    • Product list (URL)
    • Soft Quota (int)
    • Hard Quota (int)
    • Organization Contact Info
      • List of Users (Array of UUID)
      • Point of Contact user (String)
      • Point of contact email (String)
      • Point of contact Phone number (String)
      • Admins (list of users)
      • Email of organization
      • Web site of organization
@david-rocca david-rocca added draft Initial issue state user story Issues that follow user story format in order to describe community needs labels Feb 21, 2025
@github-project-automation github-project-automation bot moved this to Needs Triage in Issue Triage Feb 21, 2025
@david-rocca david-rocca added Backend and removed draft Initial issue state labels Feb 24, 2025
@david-rocca david-rocca moved this from Todo to In Progress in User Registry Planning & Development Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend user story Issues that follow user story format in order to describe community needs
Projects
Status: Needs Triage
Status: In Progress
Development

No branches or pull requests

2 participants