feat: Add url that exposes taxonomy tags CRUD API

[yusuf-musleh]

Description

This PR exposes the CRUD API for Taxonomy Tags implemented in

Supporting information

Related tickets:

• Depends on feat: CRUD API for Taxonomy Tags [FC-0036] openedx-core#96

Testing instructions

1. Run this branch in your local devstack
2. Make sure you have some sample/test taxonomy data populated in your db, you generate some by following the instructions from this repo: https://github.com/open-craft/taxonomy-sample-data
3. Check that the endpoint is available, example:
   1. You should be able to access the tags of a taxonomy by going to the following URL (replace PK with an actual PK): http://localhost:18010/api/content_tagging/v1/taxonomies/[PK]/tags/

---

Private-ref: FAL-3519

[openedx-webhooks]

Thanks for the pull request, @yusuf-musleh! Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[yusuf-musleh]

@bradenmacdonald @pomegranited I found an issue while testing. When I try to view Taxonomy Tags that have multiple level, the serializer in the openedx-learning fails because the reverse cannot find oel_tagging in the name space when running from edx-platform. When I remove the oel_tagging part, it works in edx-platform, but tests fail in openedx-learning.

I'll look more into it, but I assume there is a way to have the URL name spaces carry over for installed django apps?

[bradenmacdonald]

@yusuf-musleh I'm not sure exactly what the issue is but it's definitely fixable. You may need to tweak something about how we import the URLs into cms. See here and here. Though from reading those docs it sounds like the namespace should already be automatically set up correctly, so I'm not sure exactly what the issue is. Maybe try adding an explicit namespace like this ?

[yusuf-musleh]

@bradenmacdonald

Maybe try adding an explicit namespace like this ?

Seems like that did the trick, thanks! Looks like it was missing the inclusion of oel_tagging namespace from the urls. After adding it here fixed the issue.

[pomegranited]

👍 Works well, thank you for working out the issue here @yusuf-musleh !

• I tested this on my devstack with openedx/openedx-core#96, using the exposed REST API.
• I read through the code
• I checked for accessibility issues N/A
• Includes documentation N/A
• Commit structure follows OEP-0051

[openedx-webhooks]

@yusuf-musleh 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.