What could a possible UX look like? These ideas come to mind:

• Replace pagination with a "Show more" button, so that we get not separate pages, but extend the one list step by step
• Add a "Show on one page" button, that turns off pagination and shows all bitstreams in one list
• Add a "Change position" button for each bitstream, that opens a context menu that let's the user set the position in the list by entering a number

@MW3000 : In my opinion, there two "easiest" solutions might be:

• The "show more" option you mention which just extends the list.
• OR, a way to control the number of bitstreams per page in the pagination. If the Pagination had a control (like it does in Browse by pages) where you can change the number of bitstreams per page to 5,10,20,40,100... then that may be "good enough". You could just change the page size to move things across the current page boundary.

Hi @tdonohue we'd like to contribute to this issue, can you assign it to me?

I think the second option (change number of bitstream per page) is the better option to resolve the issue.

It is already possible to move a bitstream to a separate page. If you drop a bitstream on the page number, it should open that page and put the dropped bitstream at the top of it. From there you should be able to drop it exactly where you want it within the page

It does look like there are some issues with it at the moment though. Most of the time when you drop it on a page number, and the page switches you see a loading component that only goes away when something else on the page changes (e.g. you hover over the admin sidebar to make it open). That means that change detection isn't triggered automatically when the page has loaded. The usual solution is to use a behaviorsubject for the observable responsible

I also agree that this way of working isn't very obvious. We should make it more clear that the page numbers are valid drop-targets somehow (making them bigger, a different color, simply showing a tooltip as soon as you start dragging?)