[Archivesspace_Users_Group] Display of punctuation in PUI
Majewski, Steven Dennis (sdm7g)
sdm7g at eservices.virginia.edu
Tue Jun 27 17:31:10 EDT 2017
May be able to be fixed in EAD import.
Or, perhaps added to pre-flight schematrons and fixed in XSLT before import, since there are already a number of required fixes.
But that would be too late to fix resources you’ve already imported.
Those, you can fix it in MySQL with something like:
select count(*) from archivesspace.archival_object WHERE title LIKE '%,,%';
SET SQL_SAFE_UPDATES=0;
UPDATE archivesspace.archival_object
SET
title = REPLACE(title, ',,', ',')
WHERE
title LIKE '%,,%';
select count(*) from archivesspace.archival_object WHERE title LIKE '%,,%';
except repeat the archival_object.title update for archival_object.display_string, resource.title, accession.title, and accession.display_string as needed. ( I think that's all of them. )
May require triggering a reindex afterwards.
Note: I find too many false positives using regex search rlike: display_string rlike "[.,;],”
i.e. strings with an abbrev., : “… U.S. Commissioners, et.al., 1931-56;” or "Photographs, India, Thomas Gampper, M.D., undated” . And searching for double periods ( like “%..%” ) mostly brings up intended ellipses in my sample, so if you want to try any other patterns, you should inspect the search results first.
The above is all assuming that the problem is in the database and not just some display string constructed on the fly. I’ve found some matching “,,” instances in my sample, so that’s my guess at the source of the problem. However, I have no way to search display only instances other than by eyeball. ( Reminds me of the joke about the drunk looking for his keys under the streetlight! ;-)
— Steve Majewski
On Jun 27, 2017, at 4:28 PM, Lara Friedman-Shedlov <ldfs at umn.edu<mailto:ldfs at umn.edu>> wrote:
I was sure I had seen a JIRA issue for this a while back, but now I can't find it. We have thousands of finding aids imported from EAD that have punctuation (commas and periods) at the end of the unittitle and/or unitdate fields. Since ArchivesSpace automatically inserts commas between unittitles and unitdates, you end up with double punctuation. Rather than edit thousands and thousands of records to remove this superfluous punctuation, is there a way for ASpace to just ignore it? Please say yes! :-)
/ Lara Friedman-Shedlov
--
_________________________________
Lara D. Friedman-Shedlov
Kautz Family YMCA Archives<http://www.lib.umn.edu/ymca> | University of Minnesota Libraries
ldfs at umn.edu<mailto:ldfs at umn.edu> | 612.626.7972 |
[www.facebook.com/IHRCA]<http://www.facebook.com/yarchives> [https://twitter.com/yarchives] <https://twitter.com/yarchives>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170627/e7987ee4/attachment.html>
More information about the Archivesspace_Users_Group
mailing list