Alright, I'll go ahead and get started. It's two o'clock started the recording. So this is our, our may edition of the MSP update
Feel free to unmute yourself and ask questions if you have them. Or I'll also be monitoring chat so you can put questions in chat and, you know, as always, I'll either answer them if it's relevant answer them. Then, or say that I'll get to them at a later point in the presentation.
So just one thing to keep in mind because this is going to be, you know, a pretty stressful month, month and a half. I'm not suggesting that we're not all nice to each other already, but just keep in mind that there is a lot of things going on and
You know with 60 campuses. It is very, very hard to make one thing a priority over all others. Certainly there are protocols to be, you know,
To use for something that will will be a number one priority, such as, you know, problems with your data that would require reloading but you know try to just keep in mind that we're all in this together.
From the and the Sunni and everybody's trying to do the best that we can.
But we're all human there's only so many hours in the day.
And, you know, just try to keep that in mind as as we go forward until you know July.
And with that, to keep in mind that
Internal prioritization is something that you also want to think of as well and
In your own institution tried to help us manage the larger project by
You know, keeping everyone on the same page and
You know, keeping everything together at the campus level as well. So I know the project managers from the Sudan. We've definitely been highly involved in
At least 3035 campuses and we are going to have to pivot towards managing the overall project more so, you know, this is a great time for everyone to
Manage, you know, to manage your expectations and let us know when we need to provide attention to specific things but just try to be as nice to everyone as you possibly can be throughout the next month because things are going to get really, really hectic.
So be nice, I guess, right, that includes us as in everyone else and you know try to
Just try to keep that in mind.
So just a review of where we're at with SUNY library shared services staffing so
Not going to read the whole list, but the new addition to the SUNY library shared services is Michelle eichelberger who's going to be the resources and Discovery Program Manager. She's going to start in mid July.
Many of you know her from from her time and Sunni at currently at Genesee Community College, she's been doing a lot of things with
You know, just a lot of different areas, most notably primo in in the implementation. So really happy to have her on board.
And I know she's going to help us out immensely Maggie's already on board. Tim has started as well and is, you know, both Maggie and Tim
It's been trial by fire. I will say, and maybe not fire, but something perhaps more stressful than that and they're both doing fantastic job and Gail has been doing
You know, just massive amounts of work that many of you probably don't see an aggregate, but we do on a project side so
You know, the, the patron.
What we're calling internally is kind of a patron crisis because, you know, the thing that we were anticipating
When we were looking at ALEC data and the test load is we knew that most campuses. Where did not have authenticated data or had issues with patron data.
We thought we were going to be able to handle this with si es load that's just not happening. So Gail's been doing a ton of work to help campuses with
A lot of really just complex data cleanup work and also some data enhancement work with their Alice patrons so that they're as prepared as we possibly can get them.
For the transition Natalie and Maureen on the oldest end has been doing a lot of work getting everything ready to go to
So,
This is
You know, this is who we have for the Sunni library shared services. We're looking to
You know, we already have someone who we're just finalizing the contract for who will be an additional support and special projects librarian.
She's going to be getting in the fall and then we'll have additional staff positions forthcoming. I don't want to give timelines on those right this right this moment because
It's tough to say exactly when we'll have them Christie continues with us until end of December 2019 and then Heidi.
Finally, gets a breather. After two years her contracts ending at the end of at the end of June, you know, we've been really, really thankful for all of her help through this as well.
You know as as Christie has done a fantastic job and the project manager roles and they'll be they'll both be going back to their
Home campuses and then we have a variety of people on short term release time agreements, many of you know how they're helping you doing a lot of small group training helping with helping campuses configure their instances.
You know, doing training doing courses.
Doing custom development for patron loads, just a variety of things that we have people working on on short time release assignments and we think all of them as well. Bill Jones Alaina
You know, many other people have been working on that Natalie's on a short time agreement with us as well. So a lot of people working on this. And then we have the SUNY library Shared Services staff who will go after after go live as well.
So the question. The question that we get asked a lot. I just wanted to, you know, talk a little bit about this. The banner Alma integration update
So your, your it contact for seek is
That person can get the banner patch. That's that will be what you would use and the application that would come with it. That would be what you would use to extract your banner data in a format that will be almost compliant.
So it's a good idea to at least get this on your, your IT person's radar and that they need to request the patch. Install the patch.
Seekers recommends that you install the patch on a test environment. And then when it is
Successful successfully worked out on the test environment that you install it on your production banner environment. And then that's what you would use going forward.
So we've only the current version of the patch has only been tested at one campus and I'm not, you know, putting that out there to really say that I don't think that it's you know it's solid, as much as
You know, I think that will still be finding things that need to potentially be tweaked or gaps and documentation, etc. As we start to roll this out.
So there are some campuses, who
We've asked to just get on this really quickly so that we can get some more campuses through the process. So we understand it more so that we know more about the known issues or the things that that your IT department might have to
Think about as they work through this
And as soon as you can produce an XML file to test you can meet with Sunni, Sunni project management team, you could test it yourself if you wanted to.
But we're happy to, you know, work with you and help you out with that, if desired. What we may tell you is you know you need to go back to seek us
Because if there are errors being generated by the application or there's something, you know, in one case, we found that multiple other patches needed to be installed before the
The banner to all ma patch would work correctly. So it may be that we say, well, you need to go back to your IT department, but we will certainly help you through that.
But the thing that we ask is that you at least are capable of generating that XML file before you reach out to us because
There is setup work that needs to happen and seek us is the number you know there are the people who will walk you through that will give you all that information.
If we tried to get involved in that part of the process, it would just be frustrating for
Everybody involved. So, you know, get on your IT departments scheduled to at least get that patch and to get the you know the infrastructure setup so that you can start to, you know, at least generate that XML file.
And generally how it's going to break down. Is she kisses going to support the banner application they they've asked that they're seeking contact us a service now.
What we would ask from a Sunni perspective is is is that if you're seeing something that you think might be an issue that is going to
Be problematic for other institutions, let us know so that we can at least document it. And if it comes up that, you know, not every single campus will have to struggle with that. We could say that's a known issue.
report it to seek us. But here's the workaround. Whatever. So, you know, try to share as much information as you possibly can.
Any questions on that you can continue to. You can do this banner to all my integration.
Past the configuration freeze with Alma get Gail, correct me if I'm wrong here, but I think you have the configuration part of it already done at at
Yes, I do.
So yeah, so that that part of it is, is there. So you could you have up until a couple of days before go live that you can test banner on the integration and that's good because you're not going to be in essence testing on your life system.
So, you know, don't think of that that you can't do this past any specific date that we have other than
You know your your alma test environment will go away a couple of days before your go live date when they take your alma environment and wipe it and reinstall all of the data that you will using for go live.
I would, I would point out that the only the only glitch that people might come across as if there are ideas in the new sis load that aren't currently in
There aren't that weren't migrated to almost from all of you may get some different results. So just keep that in mind. And if you change your primary ID and things like that. So you're testing, maybe a little
A little funky.
Right. Right. Yeah. I should have put in a small asterisk with the terms and conditions and qualifications hundred percent right Gail, I mean,
They're having have been a lot of campuses, who have done a lot of changing on the Alpha and the alma and and just know that. Yeah, you're testing.
You need to factor, all of that in. If you're going to test between now and go live. Yeah, that's a great point. I know many campuses have changed their primary ID that would affect the match point potentially
And some campuses have enhanced or cleaned up their ALEC data. So whatever is your results testing between now and go live.
May not be exactly what you're going to get at go live. If you've done a massive amount of work on your patron data. Yeah, that's a fantastic point, Gail. Thanks for bringing that up.
So any questions on banner or banner Alma integration.
As. Yeah. Hi.
John from Jefferson, I'm just going reviewing what you just said, we are definitely one of those campuses that has made some changes in terms of the identifiers and whatnot. But your suggestion is to go ahead and test any way and just see what happens.
Yeah, it can't hurt.
And I would say, you might want to reach out to us to say we're when you're ready to produce that or when you've produced an XML file reach out to us and then we can kind of talk to you about it and say,
You know, you need to change your, you need to change your identifier and we can have a conversation, but it certainly does not hurt to
Test it just, you know, Gail is 100% right if you've changed identifiers, you're going to, it's not going to be plug and play after go live because, you know, I think you changed your primary identifier and then you put in extra an additional identifier. Right.
You know,
So you'd have to potentially change your match point and then, you know, you'd have to factor in that
That identifier, you know, what do you need to factor in on both sides with that but but it certainly wouldn't hurt to test
Okay, thanks.
Any other questions.
All right. And I know I do know that seekers has continued development plans for this, you know, one issue that we immediately saw
That we wanted to talk about. And it became a much easier problem to solve by changes in Alma was preferred names and that's on the, I think, phase two development plan for this.
Is to figure out how to get that out of banner into Alma. So I would say that, you know, we should be prepared or or US campuses, which I think are the strongest advocates.
To continue to talk to secrets about this and to have your IT departments who are the primary contacts to
You know, take note of what you would like to have in a second version because
My understanding is that there's a Phase two planned and that, for those of you who went to that presentation.
You know, they said that there's a phase two. And I think they listed some of the things but but now is a good time to start talking to them to say, we would like this and phase two, so that you can get it in their, in their plans.
All right. And thank you all for your patience on that I you know it's we've all been trying to get this to work. Thanks a lot to Maggie from
You know, from now the Sunni team who was getting this working on the Oneonta and, you know, and trying to just kind of keep this on.
On everybody's radar and, you know, thanks to Joe and his IT department at buff state and Christy and her ID IT department at New Paltz for being testers of this
Alright, so I wanted to do a primo update. So the last presentation I talked about two major issues which were the network zone and then responsiveness and speed issues. I'm just going to give an update on both of those things. And I'll start with the bad news, I guess.
So, uh, actually bris released some speed enhancements to some of our environments to say, you know, they think that this was
They thought that this would make some market improvements to responsiveness we tested it. We saw some very limited speed improvements, but I would say not enough where we would say that there was an improvement in the responsiveness. So
We know that actually this is working on improving that responsiveness Sunni we are taking this seriously and we're working to escalate the issue to continue to improve performance.
You know, at the, at least. Currently, and we're still working on a variety of things to make this a high priority because, you know, we don't want to be apologizing for a slow system actually Russ doesn't want to do that.
We have been assigned
You know, to be working with the VP of discovery at x Libra is to figure out how we can
Begin to improve speed with with primo v. And then we're also working with a variety of other people and the
End in the support area of excellence as well and Sunni is also exploring other options on you know how we can continue to make this a priority for actually bris to make this better as quickly as we possibly can.
You know, get it to be to be better. So
A lot of thanks to the discovery working group.
Especially the chairs Aaron and Michelle for
Working with us and then continuing to work with us to make sure that we're prepared to engage with actually research on this, because
You know, we certainly don't want to get into the situation where we're just saying it's slow
That doesn't help a developer to improve it. They need to know where, how, how slow and what scenarios. So there's a fair amount of work to be done to improve this
And, you know, both sides are dedicated to improving this. I know that doesn't necessarily fix the issue in the next month. But, you know, we're just know that this is something that's considered a serious issue on both sides. Any questions on that.
And I would say, you know, any, anything that you can look at in your in your primo
You're kind of in your strategy with primo if if if you want to try to minimize speed issues.
You know, think about that as well. I know that, you know, for example, direct linking is one major speed issue and not to say that there's not a variety of others. But, you know, direct linking might be something that you would want to turn off temporarily as we improve the speed
And you know there whatever ways that you can think of to
You know, to, to try to help out as much as possible, but we will continue to try to improve this from both of you know individual scenario standpoint and an overall standpoint.
Good news is, so, you know, got the bat out of the way. The good news is the
Sunni catalog or the network's own scope or search that we
had intended to implement that was something that actually Bruce did a fantastic job of prioritizing that development we let them know this is really important for us.
And they released a QA environments to us a few weeks ago that had the version of primo v that will be released in June.
And that had some changes that would allow the network's own to behave as we want it to, which is that the Sunni catalog has
Only the physical resources of all of Sunni and then your he resources, not the physical resources and he resources of all of Sunni, which is how it was, you know, behaving and will behave for everyone. Until the June release.
So that was something that you know we tested and we were happy that the fix that. They deployed.
made that change and that you know if you are on the fence about implementing the Sunni catalog because of those a resource issues. Just know that in June that that looks to be, you know, I don't want to
You know I'm knocking on wood here but you know the June releases what they released to us should be no problem and it should be what we anticipated having from from the start.
Any questions on that or comments.
Alright, so I just wanted to talk a little bit about something that the project management team has been working on.
And a lot of credit to Michelle eichelberger who has been helping out on this.
With what has been requested a lot by campuses. They said, Well, what do I need to do to go live. And, you know, what do I need to think about or prioritize
So we've created a go live checklist and we're going to release that go live checklist and then do a session with just some pointers and some overview on May 20 next Monday from 11 to 12 it's on all of the base camp schedules.
And this checklist is really intended for you as a campus to download it, or copy it, it's going to be a Google Doc.
And then tailor it to meet your own needs and we will try to be as exhaustive and comprehensive as we can be. But the more exhaustive and comprehensive we get, the more that makes it unusable for
For smaller campuses or campuses, who have a relatively straightforward. Go Live Plan or go live needs. So we've also tried to take the tasks and the checklist and then link out to the documentation or pointers with that will have further information about how to do the tasks.
And then on June six, we're going to have a second session, which will focus more on
Data review strategies for go live. That's going to be from 10 to 11
And, you know, we're going to try to kind of strike that balance between something that's useful for everyone. And, you know, really meaty but not being overwhelming.
We've, we've we've put it together in a way that prioritize is and will will hopefully be something that will be useful for
Almost everyone in the in the consortium and I think we're going to leave that checklist open for comments So that'll be something that we can look at it as a
As somewhat of a living document where you can post comments to say, oh, well, we're thinking about doing this, you know, could this be added to the checklist as well.
Because we're we're human, we can't think of every possible thing that would need to be done. Some of them, we might say, yeah, that's a good idea. But, you know, it only
It only really is pertinent to some campuses and not all. So, you know, think of it as a conversation. So, you know, if you haven't already. Put that on your calendar, please do put the you know the may 20 presentation on your calendar. We're going to go over the go live checklist.
A quick update on the walk and borrowing and fulfillment network, you know, this is an example of Tim Tim getting up to speed, just by diving off the deep end or jumping into the deep end.
So the status on this and and you know the walking borrowing we're using a fulfillment network which enables a campus to pull parts of the patron data from another campus and really push us forward or allow for a much more streamlined approach to the
The Open SUNY borrowing policies that have been in place for decades now 51 campuses have been configured for walking borrowing.
And, you know, that was because we asked four campuses to either do it themselves, or tell us to do it.
And at this point, we don't have plans to do the rest of them in the near future I think we'll do a few more of campuses that we know that we just need to configure it for them. So, you know, just, it should be almost all campuses by go live but not, you know, maybe not all 60
So what happens with this and this is a screenshot from from Alma when you're in the managed patron services or you're in a screen where you can add a new user
You will see another option to find the user in another institution and then you'll see a drop down of those institutions and then you would be able to
Find the patron by their, you know, by their name, or their ID, whatever they might have to search and then you would be able to know that you would be giving these borrowing privileges to somebody who is
An active user from from the other campus or is at least legitimately affiliated and, you know, hopefully this this encourages our, our, our users to feel like any Sunni from a collection standpoint, any cities library is their home library. If it's the closest one to them.
So we, we did apply
We did put in terms of use for these open Sunni what we're calling them. Open SUNY borrowers which mapped up to the visitor privileges. But I think as we're moving forward into a more group or consortium environment, what we what we're thinking of is that we want to try to get to a
Or at least entertain the notion that it would be a good idea to have a standard loan period and the standard fines fees to you policy for
These walking users because, you know, it's just something that that makes it more of a one Sunni collection that all Sunni campuses.
Can serve all Sunni patrons, as far as borrowing and the access services and resource sharing group will be sending a survey out soon to review possible standard loan periods.
And fines. And then also, you know, explore explore options and get input on standard fines fees in terms of use. So please do participate in that survey, if you're the appropriate person to participate.
Can because we want to get you know feedback from all campuses.
To to inform whatever policy, we might we might make on that.
Any questions on that. So the, the walk in borrowing, you should be able to test this now. And, you know, pull in pulling patrons from from other campuses.
You know, just it's a good time to test it so that you're prepared when this happens from a, you know, from a live standpoint.
So another initiative that we're working on. Elena has been Elena. Who's, who's working with us on release time has been
Leading this with with quite a bit of assistance from Maggie as well.
So we're working on. OCLC publishing profiles for all campuses, so that everything is ready.
Or as ready as we can get it before go live so that this isn't an additional stressful, or, you know, time consuming thing that needs to be done, we put out a call for
Campuses to say, you know, we would like you to do this for us, or we're fine doing it for you for ourselves and 27 campuses responded that Sunni that they would like to need to do this for them.
And that deadline has passed. So if you're a campus who didn't respond and did not, and do not want to do this yourself. You're going to have to wait until after go live because our resources are just tapped out now.
And we're working through configuration now and you know as part of our of our overall project plan will be reaching out to campuses that we either haven't set up or we haven't verified that they have set up. OCLC publishing just to figure out what your plans are for setting this up.
After, after go live.
So just a prompt for key dates coming up for cut over so in and also what we did with some of the key dates that just passed last last week or, you know, few days ago.
All of the migration forums or files if you're a 360 RM or 360 link campus. Those were due on the 10th.
Maybe 30% of the campuses met that deadline.
And, you know, actually this was understanding that, you know, not everybody would meet the deadline so they you will likely see that they've engaged with you if you put in your form late or or whatever it may be.
A little bit more than 20 campuses didn't submit anything. So I just wanted to kind of say what we did for you.
So, especially if you are a link resolve reform campus of those 20 campuses. If you did not respond. You did not put anything in your case you did not
You know, say whether you updated your link resolve or form what I did for you. Last weekend was go through your form I updated Science Direct if you are a stat ref campus.
I updated stat ref to be the most current and if I if I could figure it out. I looked at your PDF form.
And or PDF file and your link resolve or form and put in your case, if I made any changes to your link resolve or form because I really didn't want to, you know, have, have you create duplicate data.
Through the migration and those notes were in your Salesforce case. So take a look if you were a campus who did not respond and you want to know what happened what your link resolve reform looks like what your PDF file looks like or what your Allah. Allah migration form looks like.
So for the most part, all of the forums are submitted finalized.
I know there's still some discussions going on and the consultants from actually working on your cases are negotiating those things with you. So please do pay attention to.
The Salesforce notices and make sure that there is somebody on your campus who's keeping an eye on your Salesforce cut over case.
And then if you want more than one person to get notifications. Put that person in as an additional contact so that they get a notice if there's any sort of question or change on the Salesforce case.
The project team we get notifications for all of them, but there's just way too much chatter where we don't necessarily see every single thing. And we're not going to be monitoring it for all campuses.
If you have questions on how to add an additional contact posted in base camp and somebody will be able to help you there, either from the actually beside or or somebody from SUNY
Because I know enough of you have have done that already.
So later this afternoon at five o'clock, I think, is when Maureen has this scheduled right
The OCLC master record query will be submitted. So as a five o'clock today. That's what is going to be in the network zone. That's what we're going to use as the seed.
Is that master record query which in essence is doing the best that we can to filter out digital resources or electronic resources and only include
physical resources. So things like print books print cereals DVDs blu rays laser discs. If you still have those LPS, that type of thing would be in the OCLC master record query.
Coming up may 24 that is the absolute last day for Lyft loads. So, you know, if you have something that you, you know, you want to make sure you have the current
You know your most current user information in an Alice, make sure you plan to do that by May 24 if you have oldest do your plaintiffs for you. Please don't all do that on the same day maybe give them, you know, a day or two to kind of work through it.
And then coming up in late May we have the group one and group two specific dates.
Coming up with all of the go live activities. So now's a good time to look at that migration page if somebody could paste in the
May 24 close so Marianne.
All of our dates assume close of business unless we unless we say differently.
If you planned on doing it at around 10pm.
Reach out to us. Thank you, Susan, reach out to us, just to make sure that there's nothing planned. I DON'T THINK THAT YOU DOING IT MAY 24 at 10pm is going to create a problem, but I also don't want to commit to that.
Shannon, I can stop it. I'm just wanted to make sure. I mean, I just have to tell it not to do it.
Yeah I would do it. I would do it at five or six
Our banner doesn't automatic extract and loads up to our Dropbox in footprints. And then there's a script that runs it automatically does it so it's going to do it unless I tell it to stop. So I'll just tell it to stop on Friday afternoon.
Okay, that would be great. Yeah. And usually, you know, we try to put close of business but assume if we don't put anything and we say a date something as do it means close of business which is generally 5pm you know usually these, these do times are not, you know, if it's it's not like
We're gonna find you or something. But, you know, just trying to get it so that if there's any sort of problem that we have some time to react to it, but yeah.
Alright.
So networks own just
I talked about the OCLC master record query being submitted at the end of the day today. June 12 that's when the network zone goes live on the first group.
And then we're not going to be able to do our updates of the networks own until July 2 so just know that during that month that the network's own and the institution zone is going to be out of sync.
And you know the network zone and the institution zone is always going to be kind of a moving target, so to speak, will try to make it as good as we possibly can. But it's never going to be 100% match.
So what this means is, after May 17 you're busy and you're NZ maybe a little bit out of sync. If you continue on with cataloguing and everything else, which you know is understandable if your, if your tech services freezes later.
And I'm just putting this out there again and I talked about this slide last time.
Because actually Abras will give you the advice. Well, there's a linking job that you can run that will link your eyes, your unlinked records to the network zone.
Be very careful with that. And that might not be something or that would not be something that I would say would be a number one priority for you to do right off the bat.
Let some of us get our legs underneath us so we can help you with that a little bit more because what we found in our testing is that you could easily
Add a lot of things to the network zone that you don't want to. And we don't want you to. It's not the worst thing in the world. But don't you know don't put it as a priority that you need to rush to sync up those 50 books that you catalog between May 17 and may 30
Between the ice and the NZ just kind of get working with, you know, get get working with everything else. And then we'll loop back to to those sinks. Obviously if you're a highly developed campus who knows how to do this.
You know some of the University Centers, you've done this testing already not suggesting that you know I'm discouraging you from doing that. But just everyone in the consortium. I don't think that that's necessarily a priority.
So during July and August. As soon as we can start to automate. We're going to start to pull in all those all those files that the query collection will create
After the may 17 so they will try to sync it up as quickly as we possibly can.
And, you know, Maggie's been doing a fantastic job of networking out with other networks and coordinators, getting to know the system.
A lot of things to Gail and Maureen and Christy for, you know, working through all of the processes we figured out and getting Maggie up to speed on that as well. So any questions on the network. So
Alright, alright.
So just wanted to talk a little bit about transitioning interactions support communication, things like that.
So as we round into cut over and go live the Libra Space Camp is still going to be around. But you'll notice a a shift in their approach to it.
And that they're going to be much more likely to suggest that you open a case.
And much less likely to
provide detailed answers back and forth. So I think they will continue to provide assistance, especially if it's something that they can answer quickly in base camp.
But if it's something that requires more investigation or some back and forth, they're most likely going to ask you to submit a Salesforce case. So now's a really good time to make sure that you have your Salesforce logins in order and that you know how to login to Salesforce.
Many of you might need to go back into your email and search for Carol keys ke y es who gave you your login credentials months and months ago, many of you have probably been submitting cases all along. So this is going to be just a natural transition
And, you know, just, I know that. And I don't want to be kind of an apologist here, but you've probably noticed and we've been engaging with them on this to try to improve this as well is that their response times on base camp posts has slowed significantly recently.
And, you know, at this point, our focus with them on kind of a relationship management isn't going to be
How do you get, you know, tell me how you're going to get the base camp responses faster. We're going to be focused on the migration activities, just because that's top priority. Obviously, there's going to be communication going back and forth likely via email or via the Salesforce case.
About delivery of environments and letting us know if there's issues with environments. So, you know, if you're expecting that, you know, on June 11 that that's a good time to
Start to ask more general questions just kind of to you know get started on your configuration. Just know that there may not be as quick of a response as maybe we've had in the past. And that's kind of unexpected unexpected thing.
And what I found recently, too, is that some of your Sunni colleagues.
provide really good responses as well. So it might be another thing where, you know, more crowdsourcing or community answering a base camp questions but you know if it's something that actually Russ needs and investigate. Just know that there'll be shifting a little bit more towards Salesforce.
Questions on that comments.
So we talked about X lubricious talk about Sunni now and what we're going to try to do as much as possible through the go live process. So from now until then.
We're going to continue to do topic based webinars. So things like the go live checklist as much as we can, but know that we're going to be a little bit limited so
You know, if you ask us for, you know, another refresher on fulfillment units or fulfillment unit rules, we might say we're not going to be able to do that in the near future.
We won't be able to do any any more of the focus topic courses. I'm not sure you know what the future of those of the courses are we got really good feedback from them, but it was a significant investment and work from the people who lead them.
What else will be doing, we will be working to manage the relationship with x Libra.
Which would mean that we can help escalate something if you let us know. And just as Gail gave a qualifier to that the banner statement. I'll give a qualifier to this, please don't email me if you submitted a Salesforce case 12 hours ago and it was about something.
You know, a small issue.
That I probably will say yeah wait wait on that. But if it's something that is really important for your go live. And, you know, maybe you feel actually brisk kind of lost track of it or you need some help with it. Let us know and we can help escalate it but
Don't
Don't put us in a situation where we manage the entire relationship, especially if it's something where you want us to manage
your IT department Exley bris maybe another vendor, we're probably just going to say at that point that has to wait until after go live. So just try to have expectations, you know, have reasonable expectations.
Throughout that as well. But if you submitted a case and it it's, you know, causing a lot of problems. And it's just not gotten a response, just let us know and we can ping actually risk to say
You know, have you looked at this, can you can you know can you take a look and see if you can escalate this or what might be the issue.
We're also going to be facilitating a lot of communication about the delivery of your environments acceptance of environments.
And then issues for migration, that's going to be priority number one because we have a short amount of time to review data, especially with primo
It's, you know, a half a day, the online environment it's it's a guaranteed to two business days. So once we get the environment delivered to us.
That is the first thing that is always going to take precedence over whatever else we're doing because we want to give you the full 48 hours or the full amount of time that that we can to review your data. If you choose to review your data.
Just know that if you respond if you do not respond, we will we will try to reach out to you but if no one answers the phone at your library. You don't respond to Salesforce cases, you don't respond to emails.
We are not going to review your data. We're just going to accept it and say you did not respond and that you know assumes that you did not find any issues so
Just know that to that.
Look at your migration timeline and if, if you are a campus who wants to participate and data review. Make sure you have people there to participate.
So after go live talking a little bit about this.
What support is going to look like from Sunni or Sunni library shared services.
So if
We won't be managing we won't be Tier one and Salesforce for you unless you come to us and say, you know, we really want you to be the one who we really want Sunni, Sunni library Shared Services staff to be managing our, you know, our alma primo environment.
And at least be moving towards extended support.
And I'll talk a little bit about what that means, but I'll just get on with the rest of it here, but if you have general questions or issues.
Go through our live answers will assume the library shared services will be transitioning to a new ticketing system at the end of the year and a new managed knowledge management system.
Live answers will be around for another year, as far as the FAQ, at least, or most of the year. And we're just looking at kind of what that migration is because
The other academic technology departments that we're affiliated with are going to a new ticketing system. So it makes sense for us to go to that system with them.
So that's where all the questions should go please don't get into the habit of emailing any of us individually.
Because that's just going to be less and less and less sustainable for us and we will be more and more strict on not responding to you at all via email and just forwarding your email to the ticketing system.
And then we'll try to as much as possible. Provide you general support pointing to the FAQs and give you some general guidance on how to resolve the issue.
And then if it's an issue related to networks own level configuration or functionality that's something that will own. That's what we're, you know, preparing to do
And then we'll, you know, get back to you or if there's multiple people involved. We would communicate out what the resolution is on network zone or you know system wide issues from a, from an energy standpoint.
So some of the limitations that on on support and I'm mostly putting this up there because for about 30 campuses. We brought on a lot more support to do very, very targeted.
You know, one on one. Often, or in some cases there were four of us from Sunni five from X Libra is and two people from the campus who was like a 10 to two maybe
A. So there was a lot of support and I understand that we're moving away from that and it it's it's a transition so
We that's just not sustainable. We did that because we wanted to have people go live successfully. But beyond go live. Our focus is going to be on pointing people to how to solve their problems and not going in and configuring their system for them.
We won't be doing individual meetings hour long sessions we won't be doing campus visits, unless you make arrangements with us to either move towards extended support or you know we can do, you know, consulting service for you for for charge
So we won't be able to do high level or extended configuration of workflows setup integrations customization. That's something that just basics SUNY library shared services support. We're not going to get into that.
Will show you how to, you know, will will point you to the documentation on how to do it give you some pointers. And then it would be your responsibility and then staff training that we will provide that's going to be all group or all system webinars.
And then anything beyond that, if you wanted
You know, lots of one to one training or you know campus visits that requires an extended support agreement.
That you need to start talking with us soon but it won't be something where we will say yes, we will support you for an extended period of time and then, you know, we're going to have to be working towards that until we will offer you that extended support.
So if you know that you want more extensive support or extended support reach out to me and we can start that conversation. Talk about costs, talk about what that will get you
And start moving towards that as soon as possible. And what that will generally mean is that if you
If you're in a situation where you either cannot or you want to, you cannot
Manage your online primo environment or you want to have your librarians or staff, maybe shift to other things and have the senior library shared services do more.
Of the management of configuration that we can certainly discuss that. And we're, you know, we've made quite a few strides, even in the last few weeks of
Having
A lot more ready to give to campuses to choose from.
And with our new agreement with Empire State and you know SUNY system that we can grow to add staff to allocate specifically to supporting
Those specific campuses, who want extended support, so it's not going to come out of the five people that we have currently on on contract or working as part of that team, we would be adding people so that we could
Do the best possible job that we can do.
For extended support campuses.
Alright, so I know we've only got a few more minutes, I'll go through this quickly resource shark rollout plan we're working on this, it should be coming out in the next week, the access services and resource sharing group.
They're developing a plan or they have developed a plan. Tim's been a instrumental in creating that as well. And then the SP task force is going to review that next week.
And it's likely not going to have everyone going live immediately on lending and borrowing, but we'll have more of a phased in approached, but
You know more details coming about that. But if you were, you know, extremely concerned about lending and borrowing right at go live. Keep an eye out for the resource sharing rollout plan.
And then, thanks to the access services and resource sharing working group members for agreeing to do some small group sessions where you'll be able to walk through those workflows and kind of do
You know, moving transactions back and forth with each other from step one to finished for those workflows and that's going to happen may an early June timeframe as well. So Sarah said, can we request to be later the rollout of resource sharing. So I would say
You probably don't need to be
We will put out a plan and
You can look at where you are in the plan. And then if you really can't meet those that that part of the schedule you would
You could request that so
What we're thinking of at least with resource sharing is a campus would have to know how to manage the primo and have not going live on borrowing for resource sharing. So we assume that everyone will be live
With borrowing at resource sharing when they go live. So you would need to be at least prepared for that.
Unless you want to prepare yourself to do a lot of quick primo changes. I don't think it's outrageously complex, but it is work that you would need to do
So I would say, Hang tight. Look at the schedule and then yes you could you could request some changes, but please do know that you know it's a it's a puzzle that once you move one piece, the other pieces also need to move as well.
So we developed this model based on other large consortium, who had gone live in a phased approach with us that are similar to us as well. So trying to kind of make it work for Sunni, but also seeing what worked for others to
Last slide I have with actual content is we do need three volunteers for the MSP Advisory Board, which is going to replace the current MSP task force.
And by replace. I mean, mostly like the LSD task force will become the LSD advisory board. There's a forum where you can
Volunteer may 20 is the deadline. So if you're considering please do put your name in because we need we need more people to help us shape the
Shared Library Services platform and our collaborative work. All right, questions. Sorry, I didn't leave a whole lot of time, but these last few there's has been a ton of content to get through.
Feel free to unmute yourself or type in the chat.
Alright, last call. I guess, give it another few seconds.
Any other questions.
Could be.
Could be a specific question or larger question doesn't matter. Feel free to
unmute or type in chat.
Alright, I will stop the recording.
And stop the share
Alright. Have a great weekend. Everyone