How to implement organization-scoped filters

Open
#192 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reading the issue description and the linked community survey feedback to understand the proposed organization-scoped filters. No files, tests, or entry points are identified, so the implementation boundary and acceptance criteria need to be established before work begins.

Written by the indexing model from the issue text.

Description

documentation

Description

Some comments I've gathered from the community survey on the challenges/suggestions section:

I think it would be interesting for organizations to be able to create their own events without committing them to the core or forking. For example, could I create a package of my own and associate a new event with an exception or a model change?

This can be applied as well to filters.

Dominant language
Python
Stars
10
Forks
30
Avg merge
5h 49m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openedx/openedx-filters

All issues in openedx/openedx-filters

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.