Figure out purl-fetcher generated XML diff

[jcoyne]

From https://app.honeybadger.io/projects/48916/faults/107962440/01HYKVFM570YZ4FCGFM24D5KNJ?page=0#notice-context

lyberadmin@purl-fetcher-prod:~/purl-fetcher/current$ diff ~/kc427yh0031-public-generated.xml ~/kc427yh0031-public-dsa.xml
55c55
<     <dc:relation type="collection">Stanford University, Fisher Family Honors Program in Democracy, Development, and the Rule of Law</dc:relation>
---
>     <dc:relation type="collection">Stanford University, Fisher Family Honors Program in Democracy, Development, and the Rule of Law. (CDDRL)</dc:relation>
109c109
<         <title>Stanford University, Fisher Family Honors Program in Democracy, Development, and the Rule of Law</title>
---
>         <title>Stanford University, Fisher Family Honors Program in Democracy, Development, and the Rule of Law. (CDDRL)</title>

It looks like the collection (https://argo.stanford.edu/view/druid:sv179hy0727) recently had a title change, but for some reason we're not pulling that in.

3.3.0 :002 > Purl.find_by(druid: 'druid:sv179hy0727')
 =>
#<Purl:0x00007f9f60958d30
 id: 938238,
 druid: "druid:sv179hy0727",
 object_type: "collection",
 deleted_at: nil,
 created_at: Tue, 23 May 2017 17:14:48.000000000 UTC +00:00,
 updated_at: Wed, 15 May 2024 19:01:04.000000000 UTC +00:00,
 published_at: Wed, 15 May 2024 19:01:04.000000000 UTC +00:00,
 title: "Stanford University, Fisher Family Honors Program in Democracy, Development, and the Rule of Law",
 catkey: "">

[jcoyne]

I've fixed the by republishing the collection:

3.3.0 :002 > Purl.find_by(druid: 'druid:sv179hy0727')
 =>
#<Purl:0x00007fdb5c163fc0
 id: 938238,
 druid: "druid:sv179hy0727",
 object_type: "collection",
 deleted_at: nil,
 created_at: Tue, 23 May 2017 17:14:48.000000000 UTC +00:00,
 updated_at: Fri, 24 May 2024 12:47:02.000000000 UTC +00:00,
 published_at: Fri, 24 May 2024 12:47:02.000000000 UTC +00:00,
 title: "Stanford University, Fisher Family Honors Program in Democracy, Development, and the Rule of Law. (CDDRL)",
 catkey: "">

I think the code wasn't working correct when it previously republished back on May 15.