To view cases from other institutions in Salesforce, click on the tab Search Cases and switch the Case Options filter to My Consortium Cases.
Alma Functional Known Issues
| Case# | Issue | Notes | Reported | Status |
|---|---|---|---|---|
| 00222669 | Not possible to change the display of indexes in the Advanced Search screen | This was sent to development, and Ex Libris developed an enhancement for the August 2016 release that allows you to alter the order of search indexes in the Advanced Search. To change the display order in Advanced Search, go to Resource Configuration | Configuration Menu | Search Indexes and change the "Index Order" column. | RESOLVED Fixed in August 2016 release | |
| 00343876 | The subfield $$9LOCAL does not appear in the metadata editor in Alma | When local field is added in upper or lower case Alma stores 'local' behind the scenes. Instead of the $$9 displaying in the metadata editor, the house icon displays next to the MARC field. This graphical icon is what represents the $$9 local subfield, so the subfield does not display in the Metadata editor. The Ex Libris development team has decided not to add local field display to the MD Editor to Alma work plan. |
| NO RESOLUTION REQUIRED |
00359528 | It's unclear if a user has proxies from the Alma user screen (difficult to tell if a user is a proxy of another user). | This issue is treated as a planned enhancement request by Ex Libris: "the development team has confirmed that this is a planned enhancement. We plan to leave the current display for "User is a proxy for" largely unchanged. We plan to add a display showing users that are a proxy for a given user which will also allow adding users on the same screen. Additionally, we plan to add a feature that will send a notification to the proxy and sponsor when the relationship is added or removed. Since this is currently planned as a project with no specific release target I'll set this case to closing. But this feature will be featured prominently in the release notes when it is made available." |
| PLANNED ENHANCEMENT |
| 00413213 | When you select Add Holdings from the Metadata Editor, the campus institution code appears as an available library in addition to all campus libraries | Response from Ex Libris: "It turns out that it had been reported before and at that time, Development took at look at the severity and the number of customers affected and decided it won't be part of the road map at this time." |
| NO PLANNED FIX |
Alma Migration Known Issues
| Case# | Issue | Notes | Reported | Status |
|---|---|---|---|---|
| 00237034 | IZ record has single OCLC number but doesn't link to the NZ during migration when there is a record in both the NZ and CZ with a matching OCLC number | This is caused by the fact that there are multiple matches in the NZ for this record, so there isn't a way to determine which record the IZ record should link to. As a possible solution: remove electronic records from the OCLC load that also exist in SFX to prevent multiple records with the same OCLC number appearing in the NZ. | RESOLVED 12/3 Ex Libris is modifying their migration procedure to merge NZ and CZ records to reduce the number of multi-matches | |
| 00230389 | Extra holding is created without call number information or items attached, but contains LIB HAS statement | This happens during the migration if you are using summary statements from the bib record, and your summary statements do not contain any subfield with the location code that represents the holding. There isn't a way to determine which holding the statement should be attached to, so a new holding is created. CO is working on a fix for bib records that have one holding attached. The best fix for bib records with multiple holdings attached is to include a location subfield in the summary statement. Or, the summary statement can be retained in a local note in the bib record instead of in the holding record. |
| CO DEVELOPMENT IN PROGRESS |
| Not receiving report confirmation emails or emails sent to a printer | Ensure that all email addresses that you expect to receive mail are included in the General Configuration | Configuration Menu | External Systems | Allowed Emails table. | RESOLVED | ||
| 00208329 | Items on reserve at the time of migration migrate with the reserves location as the permanent location | Script developed for post-migration fix. Details on how to implement this are available here: Updating item locations for items that were on reserve at the time of migration | RESOLVED | |
| $9LOCAL protection did not lead to successful migration of local notes. | Some III export tables add a '.' to the end of some of these MARC fields, resulting in '$9LOCAL.' at the end of the MARC field. Because of the additional '.', this field was not treated as a local field in the migration. In order to resolve this issue, submit a ticket with III asking for all full stops/trailing '.' characters to be removed from your export table. | RESOLVED | ||
| 00369334 | Items that were on loan at the time of migration were migrated with a Num of Loans + 1 instead of the correct total number of loans | For items that were included in the loans data extract during the migration, the total checkout (or number of loans) was incremented by 1 extra loan. This will inflate analytics by 1 for every item that was checked out at the time of migration. This issue is slated to be fixed for our final load, so that items will migrate over with the correct total number of loans instead of the total number of loans + 1. In order to get correct stats for items that were on loan at the time of migration, you may want to subtract the total number of loans that are in your final loans file from your total circulation stat counts. |
| NOT FIXED Ex Libris decided not to fix this migration issue |