Skip to content

feat: Revise populate_knowledge_cards.py to use Excel

Edouard Legoupil requested to merge feature-populate-db-from-excel into main_dev

Created by: Edouard-Legoupil

Revises the backend/scripts/populate_knowledge_cards.py script to populate the database from a multi-sheet Excel file (/db/seed_data.xlsx).

The script now populates the field_contexts, donors, outcomes, knowledge_cards, and knowledge_card_references tables, and links them via the knowledge_card_to_references table.

Adds a dummy seed_data.xlsx file for seeding the database.

  • Does my code meet the quality standards for releasing packages?
  • Does the reviewer have all the information to validate the features/issues without too much research?
  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports