So, I finally hit the Scholarcy wall. After a few months of dumping research papers and articles in, my dashboard is a cluttered nightmare. The promise was to save me time, but now I'm wasting it trying to clean up.
There's a checkbox on the left for each item. Great. I check ten of them. I see the "Delete" button at the top. I click it. A single item disappears. The other nine remain checked, but the delete action only applied to the first one? There's no "Delete Selected" or bulk action menu that I can find. Am I missing something obvious, or is this a major oversight?
Tried it in two browsers. Same result.
- Check multiple items > Click Delete = One item gone.
- Tried shift-clicking a range. Nope.
- Looked for a "Select All" checkbox in the header. Doesn't exist.
For a tool built to handle *bulk* research, this is a pretty glaring flaw. Do I really have to delete 200 summary cards one... by... one? 😩 If there's a secret keyboard shortcut or a setting buried somewhere, please save me from this tedium. Otherwise, this is a deal-breaker for any serious workflow.
been there, migrated that
You're definitely not missing anything obvious, that's just how the dashboard works right now. It's a common point of frustration, and it's been brought up in the feedback channel a few times. The interface is treating that top delete button as a single-action command, even with multiple items selected.
The only workaround I've found is to use the API if you're technically inclined, but for most users, it's a manual process. I'd recommend adding your voice to the feature request thread about this. The more users who report it as a workflow blocker, the higher it'll climb on their development list.
Keep it civil, keep it real
Yeah, that API workaround is the only real solution right now. The dashboard UI is fundamentally broken for batch operations.
If you can handle a curl command or a simple Python script, you can loop through IDs and clean up in minutes. Check their API docs for the `DELETE /items/{id}` endpoint. It's not ideal, but it beats clicking a hundred times.
Their front-end team clearly built this without considering bulk data management. It's a classic case of the UI not matching the data model.
Integration is not a project, it's a lifestyle.