[felipemontoya]

Summary

load-db can write fake learner competency statuses for the Aspects Competency dashboard (openedx-aspects#387). It also gains the config needed to keep fake taxonomy rows apart from real ones.

• Statuses are written only for a competency load: when taxonomy_export_id starts with competency-, the prefix Aspects uses until the taxonomy sink carries a flag
• Two tables:
  • student_competency_status: one row per learner and competency
  • student_competency_criteria_group_status: one course-level row per learner, competency and course; fake groups exist as ids only
• Realism:
  • Each competency gets its own difficulty, a median mastery time drawn between about 4 hours and 30 days
  • First statuses land soon after enrollment
  • Parents are Demonstrated when every assessed child is
• New writers in every backend: clickhouse, csv and chdb; ralph and vector reuse the clickhouse writer
• Fixes along the way:
  • Object tags were tagged at random again by each backend, and their ids restarted per course
  • Taxonomy ids differed between backends
• Defaults keep today's output: org_prefix: Org, first ids at 1, fake export id. The exceptions are the object tag ids, which no longer restart per course.

[openedx-webhooks]

Thanks for the pull request, @felipemontoya!

This repository is currently maintained by @openedx/xapi-db-load-maintainers.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

❌ Patch coverage is 87.12446% with 30 lines in your changes missing coverage. Please review.
✅ Project coverage is 89.97%. Comparing base (f84a12b) to head (8715cca).

Files with missing lines	Patch %	Lines
xapi_db_load/backends/chdb.py	71.42%	6 Missing and 4 partials ⚠️
xapi_db_load/backends/clickhouse.py	64.28%	8 Missing and 2 partials ⚠️
xapi_db_load/backends/csv.py	80.00%	4 Missing and 2 partials ⚠️
xapi_db_load/generate_load_async.py	96.66%	3 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #289      +/-   ##
==========================================
- Coverage   90.26%   89.97%   -0.29%     
==========================================
  Files          36       36              
  Lines        2988     3203     +215     
  Branches      322      355      +33     
==========================================
+ Hits         2697     2882     +185     
- Misses        260      281      +21     
- Partials       31       40       +9     

Flag	Coverage Δ
unittests	89.97% <87.12%> (-0.29%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.