Skip to content

[BE] openedx-platform - Verify taxonomy_type passes through on Create & Import #629

Closed

Description

@mgwozdz-unicon

Part of #614. See parent for use case, acceptance criteria, and architecture rationale.

Depends on: openedx-core sub-issue #628

Files to verify/modify

File Change
openedx/core/djangoapps/content_tagging/rest_api/v1/views.py Verify TaxonomyOrgView.create_import() (lines 109–133) does not strip taxonomy_type before calling super().create_import(). Patch if it does.

This may require no code changes — the intent is to confirm the field flows through
correctly once the openedx-core changes are in place.

Example Resolution Prompt

In openedx/core/djangoapps/content_tagging/rest_api/v1/views.py, inspect
TaxonomyOrgView.create_import() (lines 109–133) and confirm that taxonomy_type is
not stripped from the request data before the super().create_import() call. If it is,
pass it through explicitly. Also verify the create() path does not strip the field.
No other changes are expected in this repo.

Activity

  1. moved this from Todo to Ready for Community Review in Competency Criteria and Student Progresson Jul 2, 2026
  2. moved this from Ready for Community Review to Final Axim Review in Competency Criteria and Student Progresson Aug 28, 2026
  3. ormsbee commented on Aug 31, 2026

    @ormsbee
    Contributor

    LGTM :shipit:

  4. moved this from In Progress to Code Review in Competency Criteria and Student Progresson Sep 3, 2026
  5. moved this from Unicon Code Review to Community Code Review in Competency Criteria and Student Progresson Sep 11, 2026
  6. moved this from Community Code Review to Ready for QA in Competency Criteria and Student Progresson Sep 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions