Identifying OpenSesame-Originated Content

Summary:

We are currently transitioning to Redwood and are evaluating the new OpenSesame Content Provider Integration that was released in 26B.

In our existing implementation, we created a custom DFF called Provider that is manually populated to identify content originating from OpenSesame. This has been extremely useful for reporting, catalog management, security, and content administration because it allows us to easily distinguish OpenSesame content from internally developed learning and content imported from other vendors.

As we move to Redwood, we are trying to understand the recommended approach for identifying OpenSesame-originated content without relying on a manually maintained DFF.

Based on Oracle documentation, it appears that the new integration supports the Publisher attribute and allows learners and administrators to search and filter imported content by Publisher. However, our understanding is that Publisher represents the actual content publisher (for example, Litmos, Mindscaling, etc.) rather than OpenSesame itself as the source platform.