Monday, July 27, 2020

Functioning at Lightspeed: Day One of the OBS/TS Summit 2020 & Linked Data in Libraries Conference

Screenshot from the Summit's OBS-SIS Business Meeting
Seriously, how fast is time going by these days? It seems like just yesterday I was attending the Work Smarter Not Harder Technical Services virtual conference from Amigos in mid-February, but here we are at the end of July on the heels of AALL 2020! Today the first ever summit of our two special interest sections is literally happening as I type this blog post. I could not contain my excitement for the topics covered so far, and felt compelled to go ahead and blog about two of the sessions. To find out more about the summit schedule which is still underway, (including business meetings too!) visit the AALL Calendar item. A big announcement from the OBS-SIS business meeting is that the official name of the SIS was voted to change to "Library Systems and Resource Discovery"! Now without delay, here are my two favorites with takeaways:
    • Facilitating Open Knowledge: The Intersection of Wikidata and Libraries - Presenters shared how "inter-collectional connections broaden the experience to go into parallel and related items". What a fantastic summary of Linked Data, and Wikidata in particular. The hyperlink for this session title will take you to the slides which I highly recommend saving as a resource if you are interested in more Wikidata. Many slides gave specific examples of using Wikidata for legal faculty scholarship.  Of course it was noted in the session and from commenters in the Q&A that "we’re in the wild west days of wikidata (just like wikipedia used to be - it is very community based)." When considering Wikidata, remember that most things in wikipedia are in wiki data, but it is not always true the other way around. The discussion following the presentation focused heavily on "notability". Presenters made sure to comment that Wikidata allows you to create entries for faculty members that might not make it into Wikipedia. Questions were asked like "is just being a faculty member enough notability to be in Wikidata?" But the goal here is to build a robust citation network in Wikidata, adding items to support structure and more. One problem discussed what that not all language versions of Wikipedia have embraced Wikidata (yet) so the benefit of Wikidata is not across the board. Presenters also shared about a new Wiki-project called Wiki abstract which hopes to dynamically pull summaries from Wikidata). The biggest takeaway was “Notability (wikidata) is not the same as bibliographic warrant (authority control - NACO)”.
    • Finding the Silver Lining in System Migrations -  What I discovered at the end of this session was that it was originally intended as a large face-to-face program in new Orleans had the AALL annual meeting and conference not gone virtual. It was planned to be a platform-neutral panel with speakers from a variety of law libraries talking about their migrations. As a result of things going virtual, this smaller session amd the one following it (Hot Topic/Local Systems Committee Meeting Making Post System Migration Efficient and Effective") covered the same terrain in two slices. There were so many takeaways from this session that I can't possibly share them all here, and even though the two speakers talked primarily about their library platforms, their joint experiences with systems and the discussion from attendees still rounded the session out to include a vareity of platforms including iii to alma, aleph, tind, wms, folio, sirsi, etc. A few of my favorite quotes and lessons from the presenters included:
      • You have to always look out for other people (not just the records you touch)
      • Always draw on the experience of people at other institutions who migrated before you, and don't be afraid to ask them "Please help me! How did you do this?"
      • You’ve got to build your own team. There’s the team you are forced to be part of (your department, your library, your university, your consortium) and then your own external team. That is the team you can build yourself, where you can gather info about the migration process from those at other institutions, and share it with others like you later after you have gone through it. 
      • Carve out management and leadership opportunities for staff and other librarians  using migration as the backbone, since it is such a major effort, it can be a milestone for any individual's professional growth and take them further in their career. 
      • Turn it into a bootcamp (like a mini 2 day conference) where you are migrating from one platform to another. Invite others in your area going through the same process (example was a DC area libraries migrating from Sierra to Alma). 
      • Know that other things may have to be sacrificed along the way. You will not survive migration if you try to do everything you have always done during a migration (or any other major project). If you’re the manager, you should be shielding your team from the onslaught of "all the things" during a big migration.
      • If you keep trying to do it all you will not do any of it very well...and you may not make it. You have to think about prioritizing things in advance. What will you stop or delay to get the new, major work done? 
      • 3 years out and many are STILL cleaning up post-migration data messes. But it becomes the new normal… so it will be OK!
      • Get to know and use your university IT department as much as you can. That has been more helpful for people migrating than their law school's IT when there is not an ILS expert in your library or a true systems librarian at your library. 
      • Negotiate with staff and librarians to parse out what they really want and need to know how to do (you may need to reference interview the reference librarians!)
      • Host a series of in-person if you can (or virtual if you can't) sessions to show staff and librarians how to do all the things they need for workflows as a live demo.
      • Keep track of your training offerings and other documentation so you can show you did your due diligence for your library.

Also still currently happening throughout this week is TONS of programming from the Linked Data in Libraries 2020 Conference. The entire slate of sessions have been FREE to attend! You can find the schedule including links to the sessions in sched. You can also find all completed session recordings in the YouTube LD4 2020 playlist. I'm going to embed that below, but first my favorite session (so far) was today's "Linked Data for Sound" session. This excellent live program presented the work of Bethany Radcliff of the University of Texas in Austin. She talked about AudiAnnotate, and shared all of the resources related to the project. The session slides are available online, which include links to GitHub and all of the other pieces of this project. It was fascinating to hear how Bethany is using Linked Data in a practical way to make audio more accessible. The tool is also being used by professors as a teaching tool for literary criticism. Part of Bethany's resources realted to AudiAnnotate include short virtual workshops that show you how to download and use Audactiy (one of my personal favorite free audio editing tools!) to make annotations to audio of all kinds. The discussion was interesting and robust too, with attendees speculating how the tool could be expanded and adapted for video, or for non-traditional audio recordings like bird songs. The conversations and discussions are continuing throughout this week on LD4 2020's slack channel. Join in if you can, and watch the wide variety of sessions (there are 46 videos and counting!!) that already have recordings available in YouTube below:

 

No comments: