As an archivist, I would like a 'select all' feature when selecting location records for batch editing

Description

Hi all, there may be a reason or workaround for this that I'm not aware of, but it would be very helpful to have the option of selecting all listed records when managing locations. Currently, if I want to batch edit records or delete more than one record at a time, I have to scroll and individually select each location record. If I want to edit every location within a space, clicking each record can become time-consuming. I am working with version 2.7.0 (not available in version drop-down).

Thanks,
Lori

Activity

Show:
Lora Woodford
December 3, 2019, 6:43 PM

- This will only select those items visible on the page. So, assuming you haven’t upped the page size in your config file, it will just select the 10 (or fewer, if there aren’t 10) results on the current page.

Robin Wendler
December 3, 2019, 6:47 PM

Thanks, Lora. That’s what we were going to do.

Joshua Shaw
December 20, 2019, 1:45 PM

I think the multiselect is working, but the batch editing appears to be broken. I can select multiple objects, but when I edit on the batch edit page, those changes do not appear to stick. Not sure if that’s related to this change or not. I also managed to trigger a frontend ‘something went wrong’ error by doing the following

  1. Select multiple objects

  2. Go to batch edit

  3. click on one of the listed objects in the left hand list

  4. use the back button in the browser to get back to the list of objects (search pane)

  5. reselect all objects

  6. go to batch edit

 

 

Lora Woodford
January 3, 2020, 9:21 PM

Hey The errors you’ve noted here appear to preexist this pull request as they can be replicated in earlier releases of ArchivesSpace. is working on addressing them.

This testing did unearth a small bit of unintended behavior in that the interface could get in a state wherein, after using the browser’s back button, clicking “select all” would actually deselect all items, and then un-clicking would reselect these items. I’ve put in a pull request to remedy this by ensuring that the page that is loaded on hitting the back button is loaded without the cached checkmark state (e.g. all items will be de-selected after hitting back).

That PR is here:

Brittany Newberry
January 4, 2020, 6:13 PM

Tested and the select all feature is working

Assignee

Lora Woodford

Reporter

Lori Dedeyan

Fix versions

Priority

Minor
Configure