The Alma Tech Team (ATT) supports Alma, working with functional areas throughout the Library to streamline workflows in order to more efficiently acquire, catalog, publish, and circulate materials.
This page is to help with onboarding, as well as to provide a high-level overview of how we work as a team.
ZenHub Board
Requires GitHub login and membership in Princeton University Library GitHub organization (request from ATT or other members):
- https://app.zenhub.com/workspaces/alma-tech-team-613a4884b84c6e00165fc2d1/board
- Prioritization of tasks: ATT Prioritization Matrix
Routines
Recurring tasks, not represented on the ZenHub board
- Recurring meetings with functional areas: Acquisitions, Cataloging, Circulation, E-Resources, Finance, IT, Inventory Management, Resource Sharing
- Fiscal Period Close tasks
- Running import profiles
- Reports: ad hoc, for Inventory Management and Cataloging
- Clearing out SCSB exceptions
- Adding, editing, and auditing Alma user roles
- Reviewing Alma releases and sharing new features with functional groups
Review
- At least one other pair of eyes, those of a team member who did not do the original work, to review resolved issues (e.g., new import profiles, norm/indication/merge rules, changes of configurations, etc.)
- The higher the priority and greater the impact, the more important the review
Tools
- Alma
- Drools: norm rules, merge rules
- Analytics
- Data Visualization
- Google Drive (docs, sheets, etc.)
- GitHub repos
- alma-config - general configuration and tasks
- alma-ncip - ILLiad add-on
- alma-notices - letters
- lsp-data - reports
- spine-o-matic - spine label prefixes
- Microsoft Office suite
- MarcEdit
- Ruby / iRB
- SN@P (Service Now at Princeton)*
- ZenHub (to manage tickets in GitHub repos)
*For tickets taking more than ~30 min we are creating a ZenHub ticket, including just the link to the SN@P ticket, with all comments remaining in SN@P.