Import Home Page

[bradenmacdonald]

https://www.figma.com/design/4wsTUbieYphB2qchIPxm10/%E2%9C%8F%EF%B8%8F-Library---Course-Authoring-v1.0--Open-edX-?node-id=14236-117715&t=6doa6ywVTLoi4sBK-4

In Scope:

• Tools > Import menu to access this new page (using Introduce Nav Dropdowns to Library Authoring View #2522 )
• Import cards - details on previous/current imports: success, partial, failed, and in progress
  • Do not include migrations from legacy libraries in the list.
  • If no previous / in progress imports, shows empty state (see Figma)
  • Clicking on the target collection link will open that collection
  • You can click on the course name to view the course in a new tab.
• Help sidebar

Out of Scope:

• "Import Course" button

[ahtesham-quraish]

@bradenmacdonald Can I work on this?

[bradenmacdonald]

See #2526 (comment)

[navinkarkera]

TBD can you click on the course name [to access the course]

@bradenmacdonald I think so, as clicking on title of course in course card in import page (starting import flow) opens the course in a new tab.

[rpenido]

Hi @navinkarkera! CC @sdaitzman @edschema @bradenmacdonald

1. From the designs, I saw that we have an incomplete status for the migration. I don't think we have it yet: the only way we have incomplete migrations is from incompatible components, which we silently skip during migration (ref).

Should I implement this as part of this task, or should we treat it alongside #2527?

2. Do we already have the documentation to be linked here?

[navinkarkera]

From the designs, I saw that we have an incomplete status for the migration. I don't think we have it yet: the only way we have incomplete migrations is from incompatible components, which we silently skip during migration (ref).

@rpenido Yes, it looks like we'll need to store information about failed blocks as well. Probably in ModulestoreBlockSource, and allowing to store null in target field of ModulestoreBlockMigration table. @kdmccormick Any suggestions?

Also when is a course considered as 100% migrated? Based on the Aggregated up to field, if we select Component, only components are migrated. But if we select section, all content is migrated. So it is also possible to have incomplete migration or partial completion based on the aggregated up to field choice. Note: we are going always import all content for now so it is not possible to partially import with this UI.

[rpenido]

Probably in ModulestoreBlockSource, and allowing to store null in target field of ModulestoreBlockMigration table.

Maybe we would need to actually create a block to show on the library, per #2527.

[navinkarkera]

@rpenido Yes, the block information can be extracted from meilisearch once we have its usage_key.

[navinkarkera]

@kdmccormick @bradenmacdonald Pinging in case you missed above comments. Let us know if you have any suggestions.