Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Assumption is AFN would not be available for any campus that hasn’t gone live. Some campuses will not be immediately doing ILL so won’t be enabling AFN on day one.
Next step is to get clarity on AFN: would any fulfillment requests wither on the vine if a campus is not yet “live” or does the request move to the next campus for fulfillment? Will AFN be turned on and working even if the campus is not yet live (i.e., before a campus has asked ExL to run the go-live job)? Carlo will ask on BC.
A go live time is for the messaging; to set patron expectations.
New-to-Almas must provide fulfillment data which takes some time.
UCLA would prefer an earlier time than noon.
UCI would prefer an earlier time than noon. Would like to wait for the ExL meeting (June 2 with existing Almas) before deciding.
Revisit this decision next week after we get answers from ExL about AFN. Carlo will post on BC.
@Carlo Medina (Unlicensed) will post on BC: would any fulfillment requests wither on the vine if a campus is not yet “live” or does the request move to the next campus for fulfillment? Will AFN be turned on and working even if the campus is not yet live (i.e., before a campus has asked ExL to run the go-live job)?
Document Alma/Primo slowness in SalesForce, see instructions.
Stay up to date on timeline / deadlines
5
Lena
Any questions on the timeline?
Question: Any objections to using the Alma account allocation for API purposes? Do Alma campuses have a good way to monitor it? There’s a report. Use the Alma account allocation to keep things simple.
Question: Do we need best practices/guidelines for APIs? Is this something that can wait until post-go-live? Wait. No one is hitting their limit now.
Awareness that NA04-NA07 servers are being physically moved to a new location over Memorial Day weekend and there will be a scheduled downtime from May 29 6pm PT to May 30 6pm PT. Check on Tuesday to make sure things look good.
UCD Escalation (3/17) is resolved. Working through some issues.
Update on Alma/Primo slowness issue: Ex Libris has agreed to lead a meeting about how they plan to solve the slowness issues in Alma/Primo VE. They want to introduce what they're calling a "warmup tool." The meeting will be led by ExL senior staff from Israel (thus the early start time): Ahuva Mazuz, VP of Development and Omri Gerson, Corp VP Platform & Tech. There will be time for Q&A. Attendance is optional.
Tuesday June 8 at 8am
THE MEETING WILL BE RECORDED.
A few WG members will also attend.
3
Q&A (recurring)
Do you have a question to discuss at the meeting? Add it below with your name.
(Lynne) Suppressing items – how do Alma campuses do this level of suppression?
(Lynne/Lena) Consortium response to Primo response time & named user questions
(Susan/Lisa S): for electronic resources which make use of outbound linking we will need the base URL and possibly an image file (in some cases the URL for the image location rather than the image file itself). AEFG has an MVP item for the CDL resources needing updating as this requires extensive coordination between CDL and campuses and can vary across content providers. AEFG is following up with the Discovery FG for the “get it at UC” logo (which replaces UC-eLinks) to ensure that the image files that are created will meet most content providers' image file type and size requirements. Please have a look at (Initial Post-Go-Live) Outbound Linking from Vendor Platforms (AEFG MVP 006).
(Gillian) from my Resource Sharing rep: it sounds like there are quite a few cases that will need to be opened for the whole consortia. Apparently there is an account where someone (at CDL I assume) can do that - do you know if we can see those cases?
(Alison): FYI - emailed everyone the ‘sfx freeze’ info, please spread to your team as appropriate/needed.
TBD
Team
Concern over the number of serious defects in digitization workflows (no ability to see comments, etc.). Not feeling confident about this critical functionality.
Jeremy shared a code repository for APIs that CSU is using to share: CSU Unified Library Management System This is an excellent model of sharing APIs and custom coding across a consortium. Thank you, again, CSUs!
CDL should manage the Get it at UC button and make it publicly available for vendors. Vendors prefer a link to an image file, not the image file itself.
For systemwide cases, Alison/Gem will open SF cases with a cc to the ICs SILS-IC-L@ucop.edu so ICs have visibility into these cases.
@Alison Ray (CDL)@Caitlin Nelson and @Gem Stone-Logan will find a home for the new “Get it at UC” button (image file). (CDL should manage the “Get it at UC” button and make it publicly available for vendors. Vendors prefer a link to an image file, not the image file itself. )
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu