The Network Zone should have the ability to suppres dedup/frbr at the library>location which exists when suppressing dedup/frbr for IZ only bib records from displaying in Primo VE.

IZ only bib records suppress dedup/frbr allows a library to suppress on the permanent physical location in a library. New records added to the location automatically suppress dedup/frbr in Primo VE once this has been configured.

For NZ linked records using the Network Zone, suppressing dedup/frbr for an library/location in the network means multiple steps and constant updating are required from an institution and Network Zone. A local extension needs to be added from the Institution’s Alma instance, which means creating a normalization rule. Then, an indication rule needs to be created in order to run it against a set to identify records that fail to get the local extensions added during the normalization job. The file of records that have the local extension need to be sent to the NZ to have the "Prevent FRBR and or/Dedup in Discovery" job run on the file.

The Institution will need to add the local extension each time an NZ record is added to the Library>location where dedup/frbr are suppressed. A compiled file of these new NZ records for this library>location will need to be regularly sent to the NZ where the "Prevent FRBR and or/Dedup in Discovery" job needs to be run in order to keep the suppress dedup/frbr process up to date.

There should be a tree of the Institution>Library>Locations that can be selected in the NZ configuration that allows new NZ linked records for the Institution>Library>Location to be suppressed automatically without all this human intervention to keep suppress dedup/frbr up-to-date

At University of Tennessee we have found we are often waiting on lengthy system jobs to process before manually ran jobs are completed. It would be nice if this page had a built in auto-refresh to reload job percentage completion. It is rather tedious to repetitively click the refresh button to see if a job has began or made any substantial progress. If possible the button should be able to be clicked for instant refreshes but it should also refresh automatically in a timely matter. I believe increments of thirty seconds would be favorable or up to a minute. Thank you for considering this idea!

It would be very helpful if ExL included a Differences report (.diff file) for the Delivery-System-Skin mashup CSS file (mashupnew.css) and also any Letter-template XSLT files which have changed for each new Alma Release, and to post them alongside the Knowledge Base article for the release (ie. https://knowledge.exlibrisgroup.com/Alma/ReleaseNotes/00992017/May2017 ).

Any institution which has made local customizations based on these files needs to perform a manual review each month. While this isn't so horrific for the single mashup_new.css file, it is for the Letter-templates. Having a section which lists the differences would be a huge time-saver. Bonus points for a human readable explanation of the change.

Hello.

I'm testing the new layout of Alma. https://knowledge.exlibrisgroup.com/Alma/ProductDocumentation/010AlmaOnlineHelp(English)/010GettingStarted/050AlmaUserInterface%E2%80%93GeneralInformation/045UsabilityImprovements/LayoutImprovements

One major change is that the Main Menu (with the Alma functional areas: Acq, Resources, Fulfillment,...) is now on the left side. The Alma Configuration Menu is also on the left side.

It can be difficult to visually distinguish between the Main Menu and the Configuration Menu. (Please see "Alma new layout, Main Menu vs Config Menu.png")

For example, I think I'm in the Alma Main Menu so I click on Resources to Manage Import Profiles. But I'm actually in the Configuration Menu so when I click on Resources I go to Resource Management settings.

Is there a way to better distinguish (with distinct colors or maybe a large gear icon at the top of the Configuration menu) when the user is in the Alma Main Menu versus Alma Configuration?

The current/old layout clearly indicates that the user is in Alma Configuration. (See "Alma old layout, Config Menu.png")

Thank you.

-Marcus

We need to be able to affiliate the same reading list with multiple course objects in Alma. Currently, reading lists can only be assigned to a single Alma Course object at a given time. At our university with a complex course timetable structure we need to be able to accommodate complex relationships between cross-listed and "meets with" courses. For these courses, we must accommodate a single course that is offered by multiple departments or at multiple course numbers (e.g., undergraduate and graduate versions of the same course "meet with" each other by sharing a lecture).

For example, our Computer Sciences 352 course is cross listed with Electrical Engineering 352. In this case, in order to align the Alma course objects to student enrollments, we must create two distinct courses, one for each department. In this case the Alma Course object's Academic Department metadata is different. However, from the perspective of our university, these are not distinct courses. Therefore, they have the same course content, including their reserves reading lists. We need to be able to associate a single reading list with ECE 352 course object as well as the CS 352 course object.

Copying and creating a duplicate reading list is not a good solution because reading lists evolve throughout a semester. Our library relies upon student staff to process our reserves reading lists. These non-professional employees cannot be expected to know the intricacies of complex courses. They should only need to update a single reading list, not two.

When a task is completed in Alma, such as the creation of PO Line, a confirmation message appears at the top of the screen in Alma, such as:

Your request to order now POL-227 has been submitted.

OR

The request was successfully submitted : request id = 701397340002914

In these cases, we would like the identifying number given in the confirmation message to be clickable as a hyperlink and route the operator to the record, request, or POL that was just created or modified. So for the PO line, POL-227 would be clickable and open the POL for edit; for the request ID, it would take you to the Resource Request Monitoring screen for that request ID.

I've attached a screenshot of the confirmation message I'm referring to.