|
| 1 | +### April 4, 2023 |
| 2 | +A very basic intro to Python for librarians who have little to no experience with Python but who want to get started. |
| 3 | +The mini-workshop titled, "An Introduction to Python for Absolute Beginners": |
| 4 | ++ What is Python and why is it useful? (5 min) |
| 5 | ++ Hands-on practice with basic operations in Python, using Google Colaboratory (25 min) |
| 6 | ++ Print function |
| 7 | ++ Data types |
| 8 | ++ Arithmetic operations |
| 9 | ++ String concatenation |
| 10 | ++ Variable assignment |
| 11 | ++ Q&A/Resources (15 min) |
| 12 | + |
| 13 | +### March 21, 2023 |
| 14 | ++ Talked about this group’s [new repository](https://github.com/code4lib/python4lib-resources), and that we want to encourage others to contribute changes via PRs (or reach out to the group) |
| 15 | ++ Talked about combining JS and python for web visualization |
| 16 | + + [Data Visualization with Python and JavaScript, 2nd Edition by Kyran Dale](https://www.oreilly.com/library/view/data-visualization-with/9781098111861/) |
| 17 | ++ Talked about if on macOS we should currently be using homebrew for installing Python on macOS |
| 18 | + + https://docs.brew.sh/Homebrew-and-Python |
| 19 | + + consensus was that it should work fine |
| 20 | + + “if you use VSCode, it recommends homebrew on mac. I used home-brew to install 3.10 and I haven’t encountered any issues |
| 21 | + + (https://code.visualstudio.com/docs/python/python-tutorial”) |
| 22 | + + we talked about how Anaconda or Anaconda can be used for python installations |
| 23 | ++ Talked about [Library Carpentry lessons](https://librarycarpentry.org/lessons/) on Python and other skills like bash, OpenRefine |
| 24 | ++ Spoke a bit about [Google Collab](https://colab.research.google.com/), which are essentially Jupyter Notebooks in the cloud, no need for local installation |
| 25 | ++ Pivoted to talk about interesting things seen in during Code4lib |
| 26 | + + the Python GUI package mentioned named [Gooey](https://pypi.org/project/Gooey/) |
| 27 | + + “There was a poster about updating subject headings as well. Which was something we had briefly talked about briefly a week before C4L.” |
| 28 | ++ Touched on a suggested breaking change to [pymarc](https://gitlab.com/pymarc/pymarc), [MR details](https://gitlab.com/pymarc/pymarc/-/merge_requests/194) |
| 29 | + + this change uses Python “namedtuples” |
| 30 | + + this change is welcome by many |
| 31 | + + We then covered how to use pymarc with authority records, as opposed to bibliographic records - more research needs to be done |
| 32 | ++ NOTE: this Python group in the future plans to host a pymarc “code recipe” sharing session |
| 33 | ++ Talked about current issues in pymarc with MARC bib tag 880 |
| 34 | + |
| 35 | +### March 7, 2023 |
| 36 | ++ Introductions with a few new members |
| 37 | ++ Move the Python{4}Lib resource page to a Code{4}Lib, thanks @klinga |
| 38 | ++ @Rebecca Hyams working on an ELUNA Dev. Day presentation gathering specific holding data (granular) from Alma via API and parsing it via python script. |
| 39 | +Chat about maintaining authorities when you’ve decided to change from standard language. Is/should there be a tool to check for changes for authorities you select? |
| 40 | ++ A project for a heat map visual for circulation might be a new way of helping to weed/collection develop. |
| 41 | + + Perhaps there's interest to have a working group dive into different projects. Could be helpful for design ideas. |
| 42 | ++ Dashboards and/or developing scripts that can translate one form of data to another; identifying transformation steps and when to streamline them in one script vs. multiple. |
| 43 | ++ IPEDS data transformations. A lot of data isn’t as streamlined as we’d like every time IPEDS comes up. Still quite local though. (Changes year to year?) |
0 commit comments