Hello, and welcome to my articles! I’m thrilled to have you here. My name is Jason, and I am the library assistant for electronic resources at Loyola Marymount University in Los Angeles, California. I am incredibly passionate about the intersection of technology and library science.

In my day-to-day work, I handle a range of tasks, from updating the LibGuides A-Z list and troubleshooting electronic resource access issues to developing custom scripts for metadata harvest. I frequently interface with library stakeholders and vendors to resolve issues, develop systems-based approaches to manage metadata, and create custom scripts for ensuring metadata compliance. Additionally, I’ve been involved in creating procedural documentation, analyzing workflows, and spearheading assessments to improve acquisition workflows, especially after our Integrated Library System (ILS) migration.

As someone who spends a significant amount of time managing metadata, troubleshooting electronic resource access, and creating custom tools for library workflows, scripting has become an indispensable part of my professional toolkit. Early in my journey, I made the decision to adopt Python as my primary scripting language, a choice that has shaped how I approach problem-solving and automation in technical services. But like any decision, it’s worth revisiting periodically to ensure it still aligns with my needs and goals. Lately, I’ve been broadening my horizons, exploring other scripting languages, particularly Bash, and reflecting on what Python offers compared to other tools.