Alma Chat Transcript 4/27/17

Owned by brandon dudley (Unlicensed)
Last updated: Aug 17, 2017 by Mallory DeBartolo (Unlicensed)

20170427 Alma functional call chat transcript

from Mark B (Los Angeles) to everyone:

Hello!

(Dolph advises the group to follow Depeche Mode’s lead and “enjoy the silence”)

from Brandon to everyone:

a timeless music reference!

from Micah SJSU to everyone:

Can someone remind me if there was a limitation on the amount of  NOTE(ORDER) data that could be migrated?

from Pam to everyone:

We have a location (with items) in our main library that wasn't migrated over the first time.  We plan to migrate it this upcoming time.  But we were told that we must add this new location into Alma -prior- to migration.  Is this true?  Or will migration take care of adding in the new location for us?

from Pam to everyone:

Great, thank you.

from Matthew Prutsman to everyone:

in the migration form, item type tab, how do we map our current Millennium item types to _not_ map to an item policy in Alma?

from Matthew Prutsman to everyone:

thanks!

from Micah SJSU to everyone:

Thats correct

from Micah SJSU to everyone:

If I have 10 notes

from Micah SJSU to everyone:

And they are small paragraphs

from Micah SJSU to everyone:

sadly

from Micah SJSU to everyone:

Ok, thank you

from SFSU to everyone:

Migration Form: PO Acq. Method Tab question - Most of our fields are populated with Vendor System Purchase. Are we using Technical for Packages, Memberships, anything else? PLease sare scenarios where we want Technical?

from Eva Sorrell to everyone:

If we are not migrating Acq data, do we need to fill in the Acquisitions questions on the Questionnaire tab of the Migration form?

from SFSU to everyone:

Ok great. Thank you

from Cal Poly SLO to everyone:

Regarding vendor claims tab, do we need to fill out if we are not sending vendors again or migrating our acq data?

from Eva Sorrell to everyone:

Okay, I wasn't sure if that was part of configuration that we may have already done

from yvonne to everyone:

second means 2018? pls. confirm

from Micah SJSU to everyone:

On the Migration form:  Cover tab,  We are still getting an error regarding the Questionaire Tab regarding the Central and Default library - You must choose 1 library from the Alma Libraries - Central or Default ordering library "You must choose 1 library from the Alma Libraries - Central or Default ordering library"

 

from Megan Drake to everyone:

Vendor claim is not required if you are not migrating acq

from Megan Drake to everyone:

Micah - in that case, pick one so the form is happy.  :)

from Micah SJSU to everyone:

Can we ignore this if we have indeed added the correct data and are choosing from the drop-down?

from Pam to everyone:

If we're leaving the Item Type tab blank intentionally, should we make note of that somewhere?  We were told to fill in this tab.

from Cal Poly SLO to everyone:

In Fulfillment section of Questionnaire, Patron ID for Loans w/o Patron--do we include the check digit on the P number?

from yvonne to everyone:

thanks, dolph

from SFSU to everyone:

We have another question for the Questionairre page regarding Rush values. We currently do not have a rush value in RACTION in Sierra. If we leave this blank, what will happen when we migrate?

from Pam to everyone:

Got it, thank you!

from Sarina Sinick to everyone:

I think that the patron ID should include the check digit on the form - your patron extracts include the check digit.

from Cal Poly SLO to everyone:

ok

from Moon Kim (privately):

In terms of the mechanics of the migration itself, what will be the order of operation that ExL will follow? For example, it could be: build the NZ, take care of the p2e, load the bibs, load the order records, load the order payments, load circ data, etc.

from Eva Sorrell to everyone:

Since we are not going live til June 27 and not migrating Acq data, will we have to run fiscal close in Alma? I'm trying to figure out how to answer about what FY is your current FY on migration form

from Moon Kim to everyone:

In terms of the mechanics of the migration itself, what will be the order of operation that ExL will follow? For example, it could be: build the NZ, take care of the p2e, load the bibs, load the order records, load the order payments, load circ data, etc.

from Cal Poly SLO to everyone:

I'm really confused on the item type tab. I thought configuration would not be overlaid in this migration. Wouldn't entering data in the item type tab change configuration?

from SFSU to everyone:

Ok, thank you

from Eva Sorrell to everyone:

Should we do it right before tech freeze, so we can continue to play til then?

from Eva Sorrell to everyone:

And if we do fiscal close before tech freeze, what should I say is our current fiscal period on migration form? Next year?

from Mark B. (Los Angeles) to everyone:

Thanks Dolph for rehearsing that, it's a helpful reminder...

from Moon Kim to everyone:

Our Millennium acq types don't fit so nicely into the Alma acq types

from Moon Kim to everyone:

It was largely an exercise in forceful shoehorning, so being reminded about the order of operation helps me better figure out how to slot them

from SFSU to everyone:

PO Entry Point Tab question - Can you explain when you would select Waiting for Invoice in the drop down? We didn't select this at all in the initial migration form.

from Eva Sorrell to everyone:

Thanks

from Moon Kim to everyone:

thanks, I'll go back and check the calendar more closely

from Eva Sorrell to everyone:

Can you clarify what we may put in the UserStatCategories in the migration form versus what is coming over from the PS load?

from Fresno to everyone:

Are you saying that if I do fiscal close in Sierra before migration that I don't need to do rolloever in Alma?

from Cal Poly SLO to everyone:

We had trouble logging in and missed the first 5 minutes -- did you answer the quesiton of whether  location names and external names will be overlaid by what is in the location tab of the form (some of our names have changed since the initial migration)

from SFSU to everyone:

Ok, we'll look into our own instance further. Thanks

from Tom - CSUDH (privately):

On the Field Mapping Form, could you go over expected entries for the Items Tab - Item Secondary file section? These were not noted or explained in last year's version.

from Fresno to everyone:

Thanks.

from Cal Poly SLO to everyone:

We want to retain the millennium i type codes in alma to use for creating sets, etc. Does this get mapped into a field in alma or can we move it into a note field and if so should we use stat note or is there a better place?

from Dolph Chaney to everyone:

from Tom - CSUDH:

On the Field Mapping Form, could you go over expected entries for the Items Tab - Item Secondary file section? These were not noted or explained in last year's version.

from Sarina Sinick to everyone:

You can also map it to an internal note field to create sets based on the old ITYPE value

from Cal Poly SLO to everyone:

We don't want to use them for item policy

from Cal Poly SLO to everyone:

Okay, thanks

from SFSU to everyone:

Just to clarify, when we do credit card purchases, this is not indicated at the point of ordering, correct? In ALMA, the credit card box needs to be checked under vendors and then when we pay an invoice, this is where we indicate it is credit card purchase. (In Sierra we are used to having a credit card Acq type that is chosen at the point of ordering.)

from Tom - CSUDH (privately):

Got it.  Thanks much.

from SFSU to everyone:

Just wanted to check. Thanks!

from Eva Sorrell to everyone:

In the test load, it looks like the III it looks like the item created date was used as the receiving date. This time around there is a received date on the field mapping form. Should I map the item creation date there as well or is that used for something else?

from Eva Sorrell to everyone:

so it won't go there automatically like the test load?

from Moon Kim to everyone:

Cause the received date is in the order record in Millennium

from SFSU to everyone:

In Alma configuration, we turned off auto-claim. In the migration form, there are a few places we need to input claim days. Does turning off auto-claim affect these days that we inputted on the form in any way?

from SFSU to everyone:

Great. Thank you

from Mark B. (Los Angeles) to everyone:

I'll say that this was a great help...it reminds me of a session at Test Load led by Vanguard Libraries.

from yvonne to everyone:

Thank you all, very helpful!

from Moon Kim to everyone:

This was helpful, thanks!

from Pam to everyone:

Thank you!

from SFSU to everyone:

One last double checking question...this session has been super helpful...:-)...For Reporting Codes on the migration form, can this field be pulled in Analytics to create an analysis? (Sort of a GAAP report related question.

from Pam to everyone:

:D

from SFSU to everyone:

sorry!

from SFSU to everyone:

:-)

from SFSU to everyone:

Thanks!