As a short term approach, I added an ORDER BY and LIMIT clause to the SELECT statements that would otherwise potentially return multiple rows where only one was expected.
In addition, I have added an unwrapped upgrade script that contains the updated biblio.extract_located_uris() definition as well as a stored procedure for reingesting records in which the associated asset.uri row has href = label.
I believe this is appropriate for backporting through 2.0; cleaning up the duplicate asset.uri entries would be nice but is not essential for the short term. Review / sign-off / commit would be greatly appreciated:
As a short term approach, I added an ORDER BY and LIMIT clause to the SELECT statements that would otherwise potentially return multiple rows where only one was expected.
In addition, I have added an unwrapped upgrade script that contains the updated biblio. extract_ located_ uris() definition as well as a stored procedure for reingesting records in which the associated asset.uri row has href = label.
I believe this is appropriate for backporting through 2.0; cleaning up the duplicate asset.uri entries would be nice but is not essential for the short term. Review / sign-off / commit would be greatly appreciated:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dbs/lp797304_ lp797307