Tag: consortia

Cloud Apps: Retrieving Data from Other Institutions
One of the powerful features of Cloud Apps is the ability to make API requests in the context of the current user. This means that no API key is required and the user's privileges are considered when determining which APIs are accessible. In a consortial setting, there is often a need to retrieve or update…


Exporting Electronic Portfolios from Alma to BrowZine in a network topology
Related article: Exporting Electronic Portfolios from Alma to BrowZine for institutions that are not part of a network. Initial Setup Campuses that have an Alma NZ setup with Electronic content that is managed centrally in the NZ using the group setting need to run the publishing job in both the NZ and their individual IZs.…


Cataloging in a Network Zone
The Orbis Cascade Alliance has some policies/guidelines for cataloging and working in the Network Zone. If you are migrating to Alma, and are going to use the NZ capabilities, you will need to define some workflows and principles among the consortia members. The Orbis Cascade Alliance guidelines can be found here.


Customized Brief Results Summary Status in Consortial Primo
Primo, at the time of writing (version 4.9.4), by default offers a mechanism to calculate summary statuses on each brief result's record, such as: But the mechanism is obviously insufficient such as "on order" item cannot be reflected. The undesirability becomes salient when the mechanism comes to a consortial setting; such as, the mechanism cannot…


Working with APIs in a Network Topology
Alma supports data sharing and collaboration across institutions in a streamlined manner. Each institution may choose its collaborative partners and establish a collaborative network to jointly manage shared resources: For general information about networks in Alma, see Alma OLH This article focuses on API and integration workflows in a network topology. NZ API key vs.…