enterprise-integrated-channels 0.1.8

An integrated channel is an abstraction meant to represent a third-party system which provides an API that can be used to transmit EdX data to the third-party system.

enterprise-integrated-channels

Purpose

An integrated channel is an abstraction meant to represent a third-party system which provides an API that can be used to transmit EdX data to the third-party system. The most common example of such a third-party system is an enterprise-level learning management system (LMS). LMS users are able to discover content made available by many different content providers and manage the learning outcomes that are produced by interaction with the content providers. In such a scenario, EdX would be the content provider while a system like SAP SuccessFactors would be the integrated channel.

Getting Started with Development

Please see the Open edX documentation for guidance on Python development in this repo.

Getting Help

Documentation

Start by going through the documentation. If you need more help see below.

(TODO: Set up documentation)

More Help

If you’re having trouble, we have discussion forums at https://discuss.openedx.org where you can connect with others in the community.

Our real-time conversations are on Slack. You can request a Slack invitation, then join our community Slack workspace.

For anything non-trivial, the best path is to open an issue in this repository with as many details about the issue you are facing as you can provide.

https://github.com/openedx/enterprise-integrated-channels/issues

For more information about these options, see the Getting Help page.

License

The code in this repository is licensed under the AGPL 3.0 unless otherwise noted.

Please see LICENSE.txt for details.

Contributing

Contributions are very welcome. Please read How To Contribute for details.

This project is currently accepting all types of contributions, bug fixes, security fixes, maintenance work, or new features. However, please make sure to discuss your new feature idea with the maintainers before beginning development to maximize the chances of your change being accepted. You can start a conversation by creating a new issue on this repo summarizing your idea.

The Open edX Code of Conduct

All community members are expected to follow the Open edX Code of Conduct.

People

The assigned maintainers for this component and other project details may be found in Backstage. Backstage pulls this data from the catalog-info.yaml file in this repo.

Reporting Security Issues

Please do not report security issues in public. Please email [e-mail].

Change Log

Unreleased

0.1.8 – 2025-06-26

Added

• fix test_migrations_are_in_sync test on edx-platform

0.1.7 – 2025-06-25

Added

• add migrations for various channel integrations

0.1.6 – 2025-06-25

Added

• Upgrade Python Requirements

0.1.5 – 2025-06-16

Added

• Rename xAPI management commands to avoid conflicts with existing commands in edx-enterprise.

0.1.4 – 2025-06-11

Added

• Added django52 support.

0.1.3 – 2025-06-10

Added

• Add DB migrations against index_together changes.

0.1.2 – 2025-05-30

Added

• Added management command to copy data from legacy tables to new tables.

• Added (Experimental) tag to app name in the admin interface.

0.1.1 – 2025-05-20

Added

• Renamed jobs to avoid conflicts with existing jobs in edx-enterprise.

0.1.0 – 2025-01-16

Added

• First release on PyPI.

• Created mock_apps for testing purposes.

• Updated requirements in base.in and run make requirements.

• Migrated integrated_channel app from edx-enterprise.