Skip to content

This commit introduces two main changes to the backend scripts.

Edouard Legoupil requested to merge feature-deduplicate-and-find-references into main_dev

Created by: Edouard-Legoupil

First, the 1-populate_knowledge_cards.py script has been updated to deduplicate references based on their URL before inserting them into the database. This prevents redundant data and ensures that the many-to-many relationship between knowledge cards and references is correctly populated.

Second, a new script, 4-find-references.py, has been added. This script allows users to find and add new references for existing knowledge cards of a specified type (outcome, field_context, or donor). The script leverages the ReferenceIdentificationCrew to find relevant references and then populates the database accordingly.

  • 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