Aside from accidental deletion when selecting multiple events, I don’t see a reason this request shouldn’t move forward. Perhaps though, the problem lies more with why erroneous events are being created rather than how they can easily be deleted.
It sounds like Benn Joseph has identified the issue (see comment on August 22, 2022 at 12:45 PM). Certain UTF-8 diacritics are not accepted by the import mechanism, even though those UTF-8 diacritics were generated by a database query. However, I am not sure he and Trevor Thornton (March 11, 2022) are experiencing the same problem. It does seem to warrant further testing.
I’m not sure the Repository Profile report (as suggested) would fulfill the original request of Chris Fitzpatrick, but both reports seem useful.
1.Workaround: increase the amount of search results that will display by modifying the config file. That said, the ability to increase the search results to different predefined amounts (30, 50, 100, etc.) directly from the staff interface would be useful.
2. Issue seems to be resolved with the updated Bulk Import AO XLSX available through ArchivesSpace 3.3.0
This ticket wants to split the existing date expression field into a date begin expression and a date end expression following the model of agent records, with existing data parsed as was done in the agent record implementation. I’m not clear how that parsing was previously done. It’s also not clear to me how useful having more ways to break out dates in a way that isn’t machine-actionable really is, but that is supported by EAD3, so I don’t object to passing this. I do recommend lowering the priority to minor and explicitly stating that this ticket should not be completed until more important date related tickets (specifically ANW-1475 and ANW-1273) are complete so that we continue to encourage people to use machine-actionable dates over date expressions.
This ticket is requesting a spreadsheet import or RDE function to create container profiles. Agree this would be very helpful and save a great deal of time. Suggest this needs a specification and then community development? Ticket is also requesting this for locations but batch location creation functionality already exists.
This ticket is requesting a CSV import function to bulk update top containers and locations across multiple resources. Agree this would be highly useful. Suggest requesting a specification.