Alma
- How to query settings in Alma via the API Console
- Querying Alma SRU server
- How to know what library an LSC item came from
- Working with related records (boundwiths)
- WinSCP server setup
- Fulfillment administration
- Print Daemon Management
- Requesting management
- Calendar management
- Non-standard circulation desk configuration
- Fulfillment Testing
- Fulfillment Anonymization Configuration
- Reshelve without transit rules
- Applying loan limits and request limits
- Researching errors reported in the CRS
- Reviewing editing activity in Fulfillment rules
- Overdue and Lost Loan Profiles
- Querying the circstatus api
- Bulk renewing loans - by changing due date
- Troubleshooting overdue and lost notice deliveries
- Administering Letters and Notices
- Faculty delivery
- Damaged item processing
- Closing lost loans
- Migrated Aleph course reserves and ILR records
- Resource Sharing Administration
- ILLiad Z39.50 add-on configuration
- Testing NCIP transactions with Postman and the premium sandbox
- Configuring ReShare Server
- How to turn off lending at the tenant level in ReShare
- What to do if ReShare might be down
- Managing ReShare Users
- ReShare Info Space
- Manually sending a borrowing request from ReShare to Alma
- Configuring ILLiad as a resource sharing partner of last resort
- Configuring ILLiad as a Lending and Borrowing Partner
- Retiring ReShare configuration in Alma
- Courses administration
- Copyright rule configuration
- Student copyright notice for uploaded files with citations
- LTI integration
- Two ways of presenting Leganto content - as a navigation item and deeplinking
- Automated course loading
- Course Reserves Digitization Routing
- Troubleshooting when students say they cannot access Leganto course materials
- Users Administration
- Adding a new employee to the sandbox
- Troubleshooting when a patron is not loaded into Alma as expected or being updated by the patron loader as expected
- Special use cases for user access
- Updating Patron Loader with new employee departments
- Updating patron loader with new academic program codes
- Understanding Alma patron identifiers
- SCL Users that migrated from Aleph to Alma
- DRAFT SOP for annual User Role audit
- Patron access to Electronic Resources
- Changing patron loader statistical category mappings by academic program
- Practicum Students who are not Duke Students
- Running the Alma patron loader integration profile
- Acquisitions Administration
- Sandbox Refresh
- Procedure for deleting locations or libraries in Alma
- CAIASoft integrations and workflows
- Aleph final database extract location
- Identifier types for creating Itemized sets from a file
- Troubleshooting when the LSC reports they did not receive requests in CAIASoft as expected
- Finding records in Alma with repeating MARC fields - example process
Helpful links
Alma production: https://duke.alma.exlibrisgroup.com/SAML
Alma sandbox: https://duke-psb.alma.exlibrisgroup.com/SAML
RLTS Helpdesk: RLTS has a web form, but they have asked that reports be triaged to Meghan Lyon via email instead (MS Form: 