By Junior Tidal

This is my second and last time as coordinating editor for Code4Lib Journal. After serving on the editorial committee for 7 years, I am rotating off of the committee to focus on other research projects. Code4Lib has played a big part in my career. In 2012, I published my first article for the journal. After attending my first Code4Lib Conference at North Carolina State University in 2014, funded by a Code4Lib Diversity Scholarship, I really wanted to get more involved with this wonderful and supportive community. I was co-convener for the local New York City chapter of Code4Lib, presented at two national pre-conferences, and served on a couple of Code4Lib national conference committees since then.

Out of participating in various Code4Lib related activities, I have to say that working with the editorial committee (EC) has been the most rewarding experience. I have learned quite a deal from my fellow editorial committee members, and for that I am immensely grateful. This includes everything from copy editing, the article review process, communicating and collaborating with authors, and most especially, managing a journal. I would like to share two recent developments with the journal: a guest editorial policy and a retraction policy.

The EC has implemented a guest editor policy. Editorial members have a wide skill set reflective of library coders and technologists, however, some of the articles that we review are beyond our scope of expertise. In those situations, we feel it necessary to consult with experts outside of the EC. The guest editor policy is in place to make it clear to the author, guest editor, and readers, their role in the review process.

A retraction policy has also been implemented. This retraction policy was developed so the EC could withdraw articles that may include work that violate ethical standards or may be unreliable. Retractions are not to be taken lightly, and as such, the journal will inform readers why the article was retracted. This will be another part of the article’s lifecycle post-publication.

Since there is now an opening on the editorial committee of Code4Lib Journal, please respond to this call for editors. If you are interested in reading and learning about library information technology, as well as being part of a great team of editors, then this is an excellent opportunity. Applicants from diverse communities are highly encouraged to apply.

I believe that every issue of Code4Lib Journal has practical applications for almost any library, archive, museum, and other related spaces, and this issue is no exception. This issue includes:

• A Fast and Full-Text Search Engine for Educational Lecture Archives which outlines the development of a search engine for educational videos using Python in India.
• Click Tracking with Google Tag Manager for the Primo Discovery Service explores how to track Open Access content through UnPaywall links.
• Creating a Custom Queueing System for a Makerspace Using Web Technologies is a case study on streamlining the queue process of a makerspace.
• Data Preparation for Fairseq and Machine-Learning using a Neural Network details the use of sequence-to-sequence models and how it can be applied for a variety application with the appropriate formatting of datasets.
• Designing Digital Discovery and Access Systems for Archival Description compares the differences between archival and bibliographic description and the challenges of utilizing discovery based systems for digital born materials.
• DRYing Our Library’s LibGuides-based Webpage by Introducing Vue.js investigates how to better streamline redundant HTML code from the popular LibGuides web content management system.
• Revamping Metadata Maker for ‘Linked Data Editor’: Thinking Out Loud looks at using and evaluating the catalog record creation tool using linked data sources.
• Using Python Scripts to Compare Records from Vendors with Those from ILS examines the use of Python to identity and synchronize out-of-sync vendor and ILS catalog records.