Third Party Integration Task Force (Discovery)
Project Owner: Keven Jeffery
Goals
- Help facilitate a community of JavaScript developers
- Create a library of code that can be implemented at the institution level
- SMS/Texting call number and book information
- Implementing solution for a chat help widget
- QuestionPoint Qwidget
- SpringShare LibChat
- Integrate LibGuides into the ULMS
- Implement Book Plates
Overall Status
WE'RE WORKING ON IT
Project Links
Major Milestones
Stage | Complete By | Status |
---|---|---|
Initial Task Force Meeting | May 20 | COMPLETED |
Research Various applications and Orbis Documentation | June n (Release of local Instances of PRIMO in June) | STARTED |
Meet to debrief on local Primo instances | June n + 1 week | NOT STARTED |
Implement Action Plan | NOT STARTED | |
Explore Libguides appearance and functionality in new Primo UI | NOT STARTED | |
Project Team
Role | Name |
---|---|
Sponsor | @Brandon Dudley |
Project Lead | Keven Jeffery - San Diego |
Team Members | Jodi Shepherd - Chico Paul Park - Stanislaus Jessie Cai - San Jose Brett Bodemer - SLO |
Vendor Contracts | |
Informed/Other Stakeholders | ULMS Systems Group ULMS Access Services and Resource Sharing Group |
Why are we doing this?
Numerous applications can be integrated into PRIMO, such as Learning Management Systems, Libguides, Chat Widgets, Book Covers, etc. This Task Force is exploring the variety as pertinent to CSU institutions and attempting to determine best options and/or practices. It will also explore the potential for possible installation-level integrations.
Prioritized List of Integrations to Explore
1) Angular JS
2) SMS
3) Chat Widgets {Libguides; LibraryHelp; QuestionPoint}
4) Book Covers { Syndetics; Amazon; Google}
5) Readings Lists {Leganto, Sipx}
6) LMS {Canvas; Moodle; Blackboard}– Liase with Systems Group for Primo implications
7) ILL - Liase with Access Services and Resource Sharing for Primo implications
8) Libguides – Defer exploration until August when new Primo UI goes live – ELUNA presentation promised many changes
9) Selection to rerun search terms in specified resources – for example, after a Primo Search, choose to rerun looking for “reference” results in reference databases, or newspaper articles in newspaper databases
Time-line
Phase 1: May to June n ( n = release of local instances of Primo in June)
General exploration of items 1-5 to identify players and issues
Phase 2: Hold next meeting 1 week after June n to
A) debrief on observations of Primo local instances
B) discuss general findings on items 1-5
C) devise action plan for providing helpful documentation items 1-5
D) reach out to Systems and Discovery Group for LMS issues
E) reach out to Access Services and Resource sharing for ILL issues
Phase 3: July – August: Begin implementing action plan
Explore Libguides appearance and functionality in new Primo UI
Goals
Scope
Deliverables
Related Activities