Define a limit for legacy library migration

[jmakowski1123]

[sdaitzman]

May need to update designs to reflect limit on the frontend if this limit turns out to be needed: https://www.figma.com/design/4wsTUbieYphB2qchIPxm10/%E2%9C%8F%EF%B8%8F-Library---Course-Authoring-v1.0--Open-edX-?node-id=14169-39395&t=cxT0nfIXdQ5oIbfF-11

[rpenido]

Hi team! Maybe I'm out of the loop here, but what are our concerns? The current migration code runs as tasks (async), so they should simply be queued up if the user migrates a large number of libraries, no?

The migration time probably scales with the library size, more than the number of libraries. Therefore, if we are concerned that a migration might get stuck in the queue, one BIG library might be enough. 😅 Did we have some hint of what our limits are?

Perhaps a user interface for viewing and managing migration jobs would be more useful?
Please let me know your thoughts! CC @bradenmacdonald @ormsbee @jmakowski1123 @sdaitzman

[bradenmacdonald]

@rpenido Yeah for now this is a placeholder while we figure it out. The current UX designs assume that it's something that happens right away (i.e. the import is fairly fast), so one approach that @sdaitzman is considering is just to tell the user that the import is in progress and give them a way to check later if it completed or not. But it may also be preferable to wait until the import has completed and give a direct success/failure message and in that case a limit may be helpful. Or a limit may be helpful just to reduce UI complexity of selecting the libraries to import (dealing with checkboxes across paginated lists of libraries). So yeah, the details are still being worked out but your point is valid that it is an async task.