Skip to content

Directus Data Reorganization for Team Pageย #586

@Rutjake

Description

@Rutjake

๐Ÿ› ๏ธ Task Description

The objective of this issue is to refactor the Directus CMS data model for the team page to eliminate duplicate member entries and ensure unique profiles, regardless of the member's roles or teams.


โœ… Steps to Complete

๐Ÿ’พ Create a New Data Model:

  • Develop an entirely new collection for member data, separate from the existing one.
    • Crucial Note: The current data is live on the site. Do not modify or delete the old data model until the new model is fully tested and ready for deployment.

โš™๏ธ Design for Flexibility & API Compatibility:

  • Design the new structure to allow fields such as Task, Team, Profession, and Participation to be managed under the member's name. This will allow roles and placements on the site to be easily updated within a single member profile.
  • Aim to structure the model in a way that requires minimal editing to the existing API code that consumes the data.
    Note: The About page also utilizes the team data for member counts, so it may need attention as well.
  • Guidance: Prefer adding more fields over too few to accommodate future needs.

๐Ÿ“Š Data Organization Logic:

  • Most members should be associated with specific Team and Participation on the project fields.
  • Key personnel (e.g., Leaders, Owners) may require specialized fields or logic to handle their presence across multiple sections or outside a specific team.

๐Ÿ“ Documentation & Handover:

  • Document all necessary information and changes for the Production Team's onboarding to the new data model.
  • Alternatively, inform the issue author so he can create the relevant onboarding materials.

๐Ÿ“Ž Resources & Information

  • Refer to the current team page on the website to understand existing member roles, professions, and teams.
  • The complete list of members is available on Drive. Contact the issue author or the team producer for the link if needed.
  • Consult the issue author via direct message in Discord if you require clarification or encounter any structural questions.

Metadata

Metadata

Assignees

Labels

enhancementFor improvements to existing featureshardlevel_hardrefactorFor code refactoring

Type

No type

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions