<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Platform Engineering on katzir.xyz</title><link>https://katzir.xyz/tags/platform-engineering/</link><description>Recent content in Platform Engineering on katzir.xyz</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 12 May 2026 14:21:06 -0400</lastBuildDate><atom:link href="https://katzir.xyz/tags/platform-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>From Classic to NDE: Upgrading a discovery layer</title><link>https://katzir.xyz/posts/discovery-layer/</link><pubDate>Tue, 12 May 2026 14:21:06 -0400</pubDate><guid>https://katzir.xyz/posts/discovery-layer/</guid><description>&lt;p&gt;I have now migrated a library discovery layer twice in two years. At my previous institution I finished an EBSCO Discovery Service update just before leaving. Then I arrived at my current job, assessed the environment, and realized that the Primo instance I&amp;rsquo;d inherited was still running Classic — not Primo VE, not NDE, but the original, pre-Angular, pre-modern-stack Primo that Ex Libris has been nudging libraries away from for years. Nobody had upgraded it because, until I arrived, there was no dedicated systems administrator to do it.&lt;/p&gt;</description></item></channel></rss>