Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discovery: tracking upstream-downstream content links #242

Open
Tracked by #1097
navinkarkera opened this issue Dec 10, 2024 · 4 comments
Open
Tracked by #1097

Discovery: tracking upstream-downstream content links #242

navinkarkera opened this issue Dec 10, 2024 · 4 comments
Assignees

Comments

@navinkarkera
Copy link

  • Designs
  • Courses should display list of libraries from which content is being used in it. (Not yet finalized)
  • Courses should display list of content blocks from libraries that was updated in libraries after being imported.
  • Course outlines should display a notification when any library content under it has been updated in the original library.
  • Additional notes:
    • Update or ignore all updates for components in a given course.
    • Ability to sort components by library?
@bradenmacdonald
Copy link
Contributor

@navinkarkera We also need to use this data for the opposite case: within libraries, showing all the courses in which a given component (or Unit etc.) is used.

@bradenmacdonald
Copy link
Contributor

@kdmccormick and/or @ormsbee will probably be interested in reviewing this plan.

@kdmccormick
Copy link
Member

Something to consider: This needs to be backwards-compatible with instances that are upgraded from Sumac to Teak, and thus may have some V2 Library References that are not persisted in these new tables. There are a couple ways to handle this. One would be to mandate a backfill migration on the Sumac->Teak upgrade. Another would be to accept that the Library Sync page may be missing some of these existing downstream-upstream connections, and provide a "Refresh" button which would check for them.

@navinkarkera
Copy link
Author

@kdmccormick Thanks! I am actually thinking of tracking links in meilisearch index document of course blocks instead of new database tables. @pomegranited is yet to take a look and review it but re-indexing courses should automatically fill up upstream links for all old blocks and new ones are handled by signal/events.

Let me know if it is a terrible idea 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

3 participants