EBSCO’s Export to NoodleTools

I’ll admit, it’s been a struggle lately finding inspiration to write. I usually have a number of ideas floating around, but lately, nothing really came to mind. This did not bode well for getting this month’s post written. I’m beginning to wonder if lack of inspiration and inability to focus and finish projects is a COVID-19 social-distancing side effect. So when I opened my email this morning there was good news. Hold on, not just good news—GREAT NEWS—the kind of news that elicits joy from librarians that are, as Alyssa Mandel calls us on Twitter, BIBLIONERDS! In the time of COVID-19, when days seems to blend into each other, good news is often hard to come by—that is if you even know what day it is. So perhaps knowing what day it is (Friday) and getting a task completed even if it’s not your best work is enough for now. Here’s hoping it is.

In the summer of 2019, I was watching a NoodleTools webinar, and at the very end Damon Abilock shared that EBSCO was working on an export to NoodleTools feature that was planned to be integrated by November 2019. I waited patiently and shared with anyone in earshot that export to NoodleTools was coming in November. The months passed—November 2019, December 2019, January 2020, February 2020—well by then I had more important things on my mind (didn’t we all?) and had completely forgotten about the release. Which made the news this morning that it was finally here that much more exciting. I was looking forward to doing a couple searches to see if the export function worked as well as I hoped.

Information is Exported, NOT Copied

An important thing to keep in mind is that when a citation is exported into NoodleTools, it isn’t simply copied and pasted. The information that is imported into the sources page comes from a file that operates much like a spreadsheet with a tag (think named row) that then aligns with the same tag on the source page interface. So, even if the pre-formatted citation from a database is incorrect—and many are—the folks at NoodleTools are wizards on properly formatting MLA, APA, and Chicago style. I don’t generally trust pre-formatted database citations, but I DO trust the folks at NoodleTools to get it right. We all know that the end citation is only as good as the data provided, so as Alyssa Mandel stated in her comment, be aware that your students need to check citations and edit as needed. Following Alyssa’s comment and an email from another AISL librarian on this topic, I’ve added this section and thank both of them for the helpful feedback. Here’s an example of the edit interface for the citation imported from EBSCO—all of the information is in the corresponding field—not copied and pasted in whole.

To Export or Not to Export

Ask any group of librarians how they feel about students exporting citations and you’ll get varied responses ranging from the belief that students should be creating their citations manually so they really understand the source they are using (true) to others who couldn’t live without bibliographic software like NoodleTools because it allows students to properly cite sources with the least amount of friction (also true). I know that I appreciate having the time to teach students how to identify the parts of a citation, but that doesn’t always happen. I also appreciate having students respond in a positive, sometimes even cheerful way when they realize how easy it is to keep their sources organized and properly cited. It’s definitely a two-edged sword, but I’m going to go out on a limb and say for most research, I’m onboard with students exporting citations. I have limited time with students and would rather work with them on mastering higher order thinking skills such as lateral fact checking and understanding how to evaluate their sources and search results.

A Trial Run

I decided to try the export function to see if it was as seamless as the ones on Gale databases and JSTOR. I searched from our EBSCO EDS search box on our library website, and in keeping with most student search behavior, chose the first article in the results list, “New Investigation …” I opened the article and you can see it in PDF format viewed on EBSCO in the third slide below.`

The Export Function is Format Agnostic

This journal article had two options for viewing: HTML and PDF Full Text. When I clicked on the Export link on the right hand side, the option for Direct Export to NoodleTools was at the bottom of the options on the Export Manager for both formats. The first image is the PDF format. Scroll through the slides to see the progression from the Export Manager to the NoodleTools interface. As always on the NoodleTools interface, there is a text box where you can submit corrections to them if you find any errors. The final two slides in this section show the bibliographic citation and the footnote pop-up window. I did a test with the HTML format and found the export worked regardless of the format. So far, so good.

Database Export vs. EBSCO Export

Next I chose an article from JSTOR (first slide), which has its own citation export to NoodleTools (second slide). I wanted to see if the citations exported were identical and found there were two differences (third slide). The article exported from EBSCO did not list the primary author’s name in last name, first name order, while the citation from JSTOR only listed the first page in the page range. As an aside, JSTOR often exports the title in all caps, which can be avoided with an EBSCO export. I guess it’s a trade-off and you’ll have to make your own decision after trying it out. A note on the Detailed Record: there are thirteen (13) authors! This is probably one of those articles students would pass over when creating a citation manually.

Tracking Down Errors

In trying to figure out the EBSCO author/ name error, I found the answer by returning to the Detailed Record. Note on the Detailed Record (second slide) all of the authors are listed first name/ last name order. This isn’t a problem as long as the names have their own unique tag that will populate in the correct field when exporting. When I opened the JSTOR export citation, the author names were correctly listed (third slide). But when I opened the EBSCO export citation (fourth slide), I discovered the first name/ last name combination was in the last name text field, leading to the error. It was easily corrected (fifth slide), but I’m not sure our students would catch this without a checklist or prompting from us. Likewise, the page range can also be corrected from the edit page.

First Impressions

So, is it love at first site? Yes, mostly. I’ll need to do a bit more testing on our various databases including Gale that currently export to NoodleTools before I can make a truly informed decision. During the end of last school year, as we pivoted to emergency remote teaching, I found I was much more lenient with students when it came to creating citations manually. I made concessions in that I allowed and even encouraged them to copy and paste citations from databases and sites like the Digital Public Library of America when I knew they were close, but not 100% correct. Does that make me a bad librarian? I hope not. Based on the disruption my students were experiencing, the fidelity of citations seems not as important to me as it did when they were working on pre-COVID projects. As we move into a new school year that feels very tenuous and uncertain, I will be thinking hard about how to maintain the academic rigor our students deserve while keeping their social and emotional well-being a priority.