Hi, That’s definitely possible. There are definitely multiple ways to do that, with different risks and benefits.
The ones I can think of offhand are: 1. Do that in the MySQL database, then clear out and rebuild ArchivesSpace’s Solr indexes. This would probably be overall fastest, but would mean some downtime, and Solr index rebuilds can take a fair amount of time if your collection is large. 2. Do it via a scripting language and the ArchivesSpace API. In this case, you’d basically write a loop over all your records, download the object, alter the description, and save the object. If you wouldn’t mind talking a little about what your available resources, access (can you directly access MySQL? Can you run Python scripts against the backend? What version of Python can you use? That sort of thing), and available expertise, I might be able to provide more help/advice? -- Dave Mayo ASpace Core Committers Group From: <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Danielle Butler <dbut...@cals.org> Reply-To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> Date: Friday, August 10, 2018 at 12:21 PM To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] Duplicate Commas Following Description In Archivists’ Toolkit before migrating to ASpace, we manually added commas to the end of each description element, so that there would be commas between the description and date elements in our XSL style sheet. When we migrated to ASpace all of the commas are duplicated in display, because ASpace automatically inserts a comma (so nice!). To have cleaner data going forward I would like to remove that comma and just add something to the style sheet to insert the comma at the end of each description element (which is what we likely should have been doing all along anyway). I have never run a script on a dataset, but I imagine that it should be fairly uncomplicated to remove the last character from a particular table using some sort of a script. We are running 2.3.2 on a Windows Server using a MySQL database. Does anyone have any experience doing such a thing and could perhaps provide some guidance? Thank you, Danielle Butler, CA | Archivist Butler Center for Arkansas Studies | Central Arkansas Library System www.butlercenter.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.butlercenter.org_&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=puAsPbSpW20GlT_NqvlDkjGZHJxHYUdtZLp4FuUUnlo&s=FCZRP17PcQUHTiAAQj9Rc-CBvl9onspPnxUi6Z8fEn4&e=> 100 Rock Street Little Rock, AR 72201 501-320-5724
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
