I think the hardest part of each day is fitting in the time to look for and learn something new. There are so many projects running across my some days, I don’t have much free time. It’s taken a while to find a system that works. The one thing I’ve learned is that, in the area of time management, few things are universal. Regardless, I’ll share what is working for me, and hopefully get some ideas from you in the comments below.
The first thing I had to do was get organized. You may have remembered my BUJO experiment. Well that failed, mainly because I would forget to bring it or not have a pen. I tried several mobile task managers, but settled on Asana. It’s a group project manager, but I love the way it looks on my phone and it’s ubiquity. Once I could better organize the projects on my plate I opened up a great deal of time for myself.
My biggest friends are aggregators. I subscribe to LibrarySherpa (which is powered by Nuzzle) and utilize Feedly (adopted after Pulse was bought out and changed). Also, RSS feeds have proved to be a huge boon. So for that last one, I fought RSS feeds for a LONG LONG time. I didn’t see the point, until my inbox was already full and was now additionally cluttered with emails I didn’t have time for. The RSS feed leaves it on the side of my Outlook, waiting patiently for me, and does not follow me when I get home. RSS has really allowed me to step away when I got home, as my inbox was no longer pinging early in the morning and late at night with some new post. Instead, on my lunch break I scan through my different feeds, open what links seem most interesting, and I feel decently informed day to day. Continue reading “Keeping up with tech”
Sometimes you have to step away from a problem to better be able to tackle it. I have been wrestling with my google apps script for weeks. After that last post, I put it away for a bit, but apparently not long enough. I had a goal: create a form using Google Apps Script that uploaded files and the recorded the information submitted. Seems simple enough.
But the difficulty was my fault, not the code. My brain didn’t formulate the problem the way I phrased it above. My brain had already decided how we were going to solve the problem. So I spent weeks playing with the code so that I had a form that uploaded a file to Google Drive, imported information into a Google Sheet, and sent an email that there was a new submission.
Are your eyes rolling yet? Continue reading “Cas 1 – 0 Google Script”
If it isn’t obvious by now, I often take projects that force me to learn new things. This was not one of those times. As part of some committee work, I agreed to help build a form for member submissions to a social media platforms run by the organization (e.g. submit your twitter or blog post here!).
It seemed straight forward, until I realized Google Forms doesn’t have an upload option on the free version. Ok. So I went on to search other options. I found that many people used a combo of Google’s Drive and GoogleApps Script to code a Google Forms-esque upload form. I copied the code to my personal drive, and womp! It would not run, even in its initial iteration. I would just get a blank screen.
To be completely honest with everyone, I’m still not completely sure why the code would not work for me. I was sure it was an ID10-T user error, but after sending my sysadmin friend a video of what I was doing, he was stumped as well. It was working for him. He could run it with no issues, and it seemed like I was doing all the same things he was doing. After about an hour of tinkering, which left me with a deep desire to flip my desk, I closed the window to revisit later.
Later has not quite come yet; I started this project only four days ago. This post is a testament that using tech is never all success without complication. It’s completely ok to fail or hit a set-back. This is why you start things a month before they are due (take that procrastination brain). I’m jumping back into it today, hopefully. Expect a follow-up post once I get the code to submit, but for now, happy tinkering!
The last major focus for OpenCon was Open Education. Open education is about opening lecture notes, assignments, and creating and using open textbooks. With dwindling budgets, states scrambling to find qualified teachers in an ever dwindling pool, and teachers burning out on a daily basis, open education should have a brighter spotlight. Using open textbooks can save schools and college students a great deal of money. Open lecture notes and assignments helps often overworked teachers and new teachers save time by not having to build each class from scratch and lessening preparation time at home. Continue reading “OpenCon 2016: Part Two”
It may seem silly, but I have spent hours trying to design, tweak, and redesign from scratch our logo for this blog. Not only because I wanted the chance to play with different software to create it, but because I really believe in the potential for this blog to be more than a passing fancy. I would love for it to be something people look forward to reading. Researching to find tips and guidance made me realize that I was basically working to make a brand. That seems strange to say. This blog started as an excuse to learn new things and chronicle our efforts. Calling Tinkering Librarians a brand makes this all feel so stodgy. Regardless, since logos and branding are so intertwined, the logo creation project became a learn about branding project. And, well, a bit of madness ensued. Continue reading “We’re a brand?”
A couple of months ago I attended ER&L. It was all so new. I was shy and overwhelmed. I attended the reception, fantastically late, hoping to make some acquaintance. I moved to the far end of the only half full reception area to the wallflowers by the windows. My secret wish was to find a isolated seat where I could hide, tell myself I tried, and again read through my schedule for the next day. I was disappointed, and thankfully so.
I swallowed my nervousness and asked to sit next to a librarian, who I’ll call J., who looked confidently alone yet strangely welcoming. J was gracious and open. One more lone sole sat a chair away. J and I made eye contact and invited her over with a waive. She happily glided over chair in hand, and that was how I met Dee. There we sat, a council of new attendees discussing the pasts that led us here and our strategies for the next few days. We all had different reasons for being in that room, at that conference, on that journey, but our goal was similar, learn something, hopefully several things, that could make us better librarians.
It made me realize just how many paths there are. The next few days stressed just how much there is to learn. I returned to my room in my hostel at the end of day one wanting to tinker with all the new things I had seen. The idea for this blog was born, and somehow I convinced Dee to tag along. We’ll be posting on the 1st and 15th of each month. Let’s see where this rabbit hole goes!
Next up: Canva