[BD-14] Sync 2020-10-02

Owned by Kyle McCormick (Deactivated)
Last updated: Jan 14, 2021
4 min read

  • Demo of latest features

    • MFE

      • Library license configuration

      • User access configuration

      • Video-type libraries

      • Problem-type libraries

      • Filtering and pagination in the library list

    • Studio and LMS

      • Adding library content to a course

      • What happens when you update a library?

    • Notes

      • License + access configuration

      • Library listing page:

        • No API currently to paginate (V1 union V2) libraries.

          • So, you cannot list “All” libraries currently - only one type at a time

          • This is a result of V1 and V2 libraries being stored differently.

          • One possible listing would be “V2 only”, though.

        • Kyle: Could V1 libraries be added to the ES index? Would that solve it?

          • (is this worth doing, though? we’ll want to DEPR V1 libs as soon as we can)

          • Dave: It’s actually better to keep them separate. +1 Nimisha

          • Nimisha: Could be confusing if V2-only is all of a sudden the default listing, as some folks expect to see their V1 libraries there. Keep this in mind during rollout.

          • Nimisha: Using a multi-select or some other experience might be better than drop-down.

        • Dave: Need to make sure this page works with huge # of libraries (for example, some MIT admins are given access to thousand(s) of libraries).

          • @Former user (Deleted) will test this

          • Dave: We need to be able to support being able to manage 1000 libraries, but that doesn’t mean we need to be able to display 1000+ libs at once. A “you need to filter it down” experience could be fine.

          • Adolfo: The backend should be in a good place to handle this.

        •  

      • Library block editor:

        • HTML is one of those blocks that doesn’t work in the MFE

          • Video editor doesn’t work either.

          • But the blocks render fine through the library sourced block in the LMS.

          • Drag and Drop block does work.

          • Kyle: Is there a clear distinction between blocks that do and don’t work in the MFE author_view iframe?

            • It’s blocks that make assumptions about the page they are being rendered in. This is especially true of the author/studio_view of blocks built into edx-platform.

          •  

          • (We’ll talk about this after the demo)

      • Library sourced content

        • New tentative UI – feedback expected, mockup would help

        • Key difference:

          • V2 libraries require an explicit publishing step, whereas V1 libraries are automatically updated

        • Library block updating / falling out-of-date with library.

          • @Former user (Deleted) will explore this.

          • Dave: Hammering down what the edit/publish/update flow should look like is really important.

            • With V2 (blockstore) libraries, we can have more sanely versioned libraries (v1,v2,…)

            • Should we surface versioning to users?

            • @Kyle McCormick (Deactivated) add to the agenda for meeting next week and create a discovery ticket to track these discussions.

            • @Dave Ormsbee (Deactivated) can write up an doc/page/something to set the stage for this conversation.

      • Marco: as a high-level comment, lots of stuff to iterate on UX-wise in M3, but overall, nothing jumping out as too concerning.

      • Marco: Both library detail view and component editing pages have “Publish” button. Would be good to make it clear to the user what exactly those publish.

        • Adolfo: That’s a result of Ramshackle inheritance. Currently working on new library editor that is more Studio-esque. Publishing button will only be in one place.

      • Nimisha: Static asset UI?

        • Adolfo: Is temporary. Current view is “operator” view, will be smoothed out.

      •  

  • Block editor modernization

  • UX feedback timeline

    • Marco will be making lo-fi collateral for this project.

    • @Marco Morales (Deactivated) - Can you speak to when the team will be able to see mocks?

    • How does that timeline affect the project?

  • 500s on Stage

  • Milestone 3 planning

    • M3 was originally the beginning of Taxonomies, Tagging.

    • We identified last time that we should instead focus on bringing M2 results to parity with V1 libraries. Does that still sound good?

    • Can we identify a high-level objective for this milestone?

    • Import/export is part of this milestone

      • This is blocked by publishing/updating/versioning questions

    •