Uploaded image for project: 'Opencast'
  1. MH-12266

As a user, I expect metadata changes to be propagated to third-party applications

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed and reviewed
    • Affects Version/s: 3.1
    • Fix Version/s: 4.0
    • Component/s: Backend Software

      Description

      When using OAI-PMH to interface with third-party applications, there are at least three copies of metadata:

      • Opencast (as displayed in the Admin UI)
      • OAI-PMH server (database table)
      • Third-party application (own representation)

      Currently, when a user changes metadata in the Opencast Admin UI, most of those changes (some indeed are propagated) are not propagated to Events that have been published to OAI-PMH.

      Problems:

      • It is not possible to know what metadata has been published using the Admin UI - that would require looking into the database or the third-party application
      • Metadata changes get complex and cumbersome. For example, fixing a typo requires users to re-publish content

      To goal of this story is to make the following changes being propagated automatically to the OAI-PMH server:

      • Changes to dublincore/episode and dublincore/series
      • Changes to ACLs of series and events

      Optional:

      • Make automatic propagation optional in case other Adopters prefer the old way

        TestRail: Results

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                staubesv Sven Stauber
              • Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  TestRail: Cases