manifold icon indicating copy to clipboard operation
manifold copied to clipboard

Change Project Collections Filtering Options to Make it easier to remove projects from a collection

Open mkgold opened this issue 4 years ago • 1 comments

Feature Description

Find ways to make it easier to remove projects from a collection, principally by adding a filter option to a project collection that shows only those projects currently in the collection. Another option would be to add a "remove" button to the list of projects in a collection (we currently only allow the order of projects to be adjusted).

Why is this feature important? Who does it help?

This will be helpful to Manifold administrators on large installs with lots of projects on them.

User Stories

This happened to me today: I mistakenly added 4 or 5 projects to a collection. When I realized this, I needed to find a way to remove them from the collection. My first thought was to click on the name of the project collection in the dashboard; this brought up the projects in the collection, but only offered the chance to reorder them, not to remove them from the collection. So, I went to the "Manage Projects" option, but that listed all projects in the instance without showing the ones currently part of the collection at the top. Since the CUNY instance, where I am doing this work, has a ton of projects, scrolling through the whole list of them is onerous, as there is no way to filter to view just the projects that are part of the collection.

Design Notes

As I'm writing up this ticket, I think the easiest way to create this functionality would be to add a "remove project" option to the list of projects in the collection

Please see attached screenshots.

list-of-projects

project-collection-page

Development Notes

mkgold avatar Sep 29 '20 04:09 mkgold

Thank you for taking the time to open this feature request. The Manifold team reviewed this issue during our bi-weekly meeting and the consensus is that this feature makes sense and is in keeping with our overall vision for the platform. Moreover, we see this request as a viable candidate for development under our current available funding. We’re adding an “accepted” label to this request to indicate that it’s within scope and possibly within budget.

The next step is for us to estimate the work involved with this and add it to our feature backlog. Our acceptance of the issue is not a promise that it will be implemented. We will balance this request against the other accepted requests and do our best to implement it within our current available funding.

This was an automated message, but please don't hesitate to reply. Our team watches these issues closely and will respond as soon as we're able to!

zdavis avatar Oct 08 '20 19:10 zdavis