In my previous post on the WMS Global Community & User Group Meeting, I shared my thoughts on some great presentations from a developer perspective. As I mentioned, the meeting was a chance for members of the WMS community to share best practices, tools, tips and workflows with one another. Many presentations featured helpful hints for developers who want to create integrations or customizations.
Two presentations in particular sparked my desire to learn more about particular tools available to the community. The first presentation was "Using the WorldCat Query Collection to Load Holdings to a Third-Party ILL System such as InnReach." This presentation talked about how Lawrence Technological University is exporting their data for consortial borrowing via MelCat from Midwest Collaborative for Library Services (MCLS) . For me, it was interesting because it highlighted how WorldShare Collection Manager can be used to bulk export records based on a set of search criteria. For WMS institutions that want to implement an open-source discovery tool—like VuFind or Blacklight—and that need to export their records for indexing, this functionality would be a good starting point. Another use case would be if a library wanted to export and enhance institutionally unique records, such as thesis and dissertations, in order to make batch enhancements.
The second presentation that got me thinking about possibilities was a panel presentation on inventory tasks and workflows. This presentation gave me a better window into the types of reports that are downloadable from WMS. I definitely want to explore these more and to think about how reports and APIs could be used to streamline workflows. What would it take to get the “new books” report to power a list on a library website without human intervention?
As always, whenever I get to talk with librarians and library staff who are trying to solve problems, I'm both impressed and excited. These interactions inspire me to think about what types of APIs might better help libraries save time and money and improve the user experience.
If you have experiences to share from the meeting or other developer tips, please let us know. We are eager to share best practices and ideas from the developer community.
Senior Product Analyst