63 results found

1. Alma “scan-in” API: Marc21 field 852 - call number prefix and suffix

   We are using the Alma “scan-in” API
   /almaws/v1/items?itembarcode={itembarcode}
   which redirects to
   /almaws/v1/bibs/{mmsid}/holdings/{holdingid}/items/{item_pid}
   to print book labels.

   Some sublibraries also use call number prefixes or suffixes in some cases.
   
   Please see the following example record:
   - Marc21 field 852 in the Holding record
   - XML output

   (1) Example: Call number with prefix 852 $$k
   852 8_ |b XHOG |c XGRY |h G-1234567 |k Präfix

   XML output:
   item/holdingdata/permanentcallnumber: Präfix G-1234567
   item/holdingdata/callnumber: Präfix G-1234567
   item/holdingdata/accession_number: G-1234567

   item/itemdata/parsedcallnumber:
   <parsedcallnumber>
   <callno/>
   <call_no>Präfix</call_no>
   <call_no>G-1234567</call_no>
   </parsed_call_number>

   (2) Example: Call number with suffix 852 $$m
   852 8_ |b XHOG |c XGRY |h G-1234567 |m Suffix

   XML output:
   item/holdingdata/permanentcallnumber: G-1234567 Suffix
   item/holdingdata/callnumber: G-1234567 Suffix
   item/holdingdata/accession_number: G-1234567

   item/itemdata/parsedcallnumber:
   <parsedcallnumber>
   <callno>G-1234567</call_no>
   <call_no/>
   <call_no>Suffix</call_no>
   </parsed_call_number>

   (3) Example: Call number with prefix 852 $$k and suffix 852 $$m
   852 8_ |b XHOG |c XGRY |h G-1234567 |k Präfix |m Suffix

   XML output:
   item/holdingdata/permanentcallnumber: Präfix G-1234567 Suffix
   item/holdingdata/callnumber: Präfix G-1234567 Suffix
   item/holdingdata/accession_number: G-1234567

   item/itemdata/parsedcallnumber:
   <parsedcallnumber>
   <callno/>
   <call_no>Präfix</call_no>
   <call_no>G-1234567</call_no>
   <call_no/>
   <call_no>Suffix</call_no>
   </parsed_call_number>

   and after some tests the <parsed_call_number> section looks like this:

   <parsed_call_number>
   <call_no/>
   <call_no>Präfix</call_no>
   <call_no>G-1234567</call_no>
   <call_no/>
   <call_no>Suffix</call_no>
   </parsed_call_number>

   Conclusion:
   - Marc21 subfields 852 $$k and $$m are not listed sperately in the XML :-(
   - In <parsed_call_number> section the content of <permanent_call_number> or <call_number> is splitted up into the content of 852 $$k, $$h and $$m. The order of the <call_no> tags is correct (call number prefix / call number / call number suffix) but there are also empty <call_no/> tags.

   Please provide us a XML output with Marc21 852 content in seperate fields. The important call number fields for us are:
   - 852 $$k ... call number prefix
   - 852 $$h ... call number (classification part)
   - 852 $$m ... call number suffix
   - <accession_number> includes 852 $$h only if the call number has been generated via a call number (accession number) counter.

   Other libraries may be interested also in other subfields of Marc21 852:
   https://www.loc.gov/marc/holdings/concise/hd852.html
   $h - Classification part (NR)
   $i - Item part (R)
   $j - Shelving control number (NR)
   $k - Call number prefix (R)
   $l - Shelving form of title (NR)
   $m - Call number suffix (R)

   Having the content of 852 $$k, $$h and $$m in separate XML fields gives us the possiblity to handle the call number parts in a different way on the book label (if desired).
   Having two <call_no> tags in the <parsed_call_number> section is not clear enough. It could mean that you have:
   - 852 $$k ... call number prefix / 852 $$h ... call number (classification part)
   - or 852 $$h ... call number (classification part) / 852 $$m ... call number suffix

   Thank you in advance!

   We are using the Alma “scan-in” API
   /almaws/v1/items?itembarcode={itembarcode}
   which redirects to
   /almaws/v1/bibs/{mmsid}/holdings/{holdingid}/items/{item_pid}
   to print book labels.

   Some sublibraries also use call number prefixes or suffixes in some cases.
   
   Please see the following example record:
   - Marc21 field 852 in the Holding record
   - XML output

   (1) Example: Call number with prefix 852 $$k
   852 8_ |b XHOG |c XGRY |h G-1234567 |k Präfix

   XML output:
   item/holdingdata/permanentcallnumber: Präfix G-1234567
   item/holdingdata/callnumber: Präfix G-1234567
   item/holdingdata/accession_number: G-1234567

   item/itemdata/parsedcallnumber:
   <parsedcallnumber>
   <callno/>
   <call_no>Präfix</call_no>
   <call_no>G-1234567</call_no>
   </parsed_call_number>

   (2) Example: Call number with… more

   20 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Alma APIs Multilingual Code-tables

   We’d like to request an enhancement to the Alma API that would allow PUT and POST requests to include translation updates. Currently, only GET requests support the lang parameter for retrieving localized data, while updates ignore these descriptions. Enabling translation updates via API would streamline content management across languages, making it easier to keep localized information current and consistent.

   Updating code tables for around 80 patron-facing letters in three different languages via the web UI is extremely time-consuming and inefficient. Allowing translation updates through the API would greatly improve this process, making Alma more effective for multilingual institutions.

   We’d also like to highlight an inconsistency: the addressFrom field, which represents an email address, is language-dependent in the current setup. Since email addresses are universal and not language-specific, it would make more sense for this field to remain constant across all languages.

   Allowing language-neutral fields like addressFrom to remain consistent would simplify multilingual management and avoid unnecessary duplication across language settings.

   We’d like to request an enhancement to the Alma API that would allow PUT and POST requests to include translation updates. Currently, only GET requests support the lang parameter for retrieving localized data, while updates ignore these descriptions. Enabling translation updates via API would streamline content management across languages, making it easier to keep localized information current and consistent.

   Updating code tables for around 80 patron-facing letters in three different languages via the web UI is extremely time-consuming and inefficient. Allowing translation updates through the API would greatly improve this process, making Alma more effective for multilingual institutions.

   We’d also… more

   20 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Accession number available by API

   Hello,
   To be able to develop several external tools (relabelling, cataloging, ...) we need to access the "Accession number" table by API (read and write).
   This would probably give many other clients oportunities in developing external tools for managing physical collections.
   Best regards.

   18 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Add export start/effective date to Bursar integration profile configuration settings

   When creating a new Bursar integration profile, we want to be able to limit the transactions being exported to only those generated after a specific date. This is in addition to ‘Time before export (days)’ setting. We've never used an integration profile to export fines/fees to be transferred to our bursar office and have instead used the API. We're now stuck in a situation where we can't switch to using an integration profile because without a start/effective date there's no way to prevent the exported files from creating double billing of transactions that have already been transferred to our bursar via API.

   When creating a new Bursar integration profile, we want to be able to limit the transactions being exported to only those generated after a specific date. This is in addition to ‘Time before export (days)’ setting. We've never used an integration profile to export fines/fees to be transferred to our bursar office and have instead used the API. We're now stuck in a situation where we can't switch to using an integration profile because without a start/effective date there's no way to prevent the exported files from creating double billing of transactions that have already been transferred to our bursar… more

   15 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Add ability to customize the data exported by Bursar integration profile using System = Other

   When creating an integration profile of type Bursar which uses a ‘System’ setting of ‘Other’ there should be more granular control over what data is included in the export.

   If a ‘System’ setting of ‘Other’ is selected, then a 'Data' tab should be made available which will allow you to select via checkbox what fines/fees and user data is included in the exported file. The data available should at minimum include, but not necessarily be limited to, what is accessible via API.

   15 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. bursar integration - option to export fine/fee credits even if minimum value > 0

   Currently in order for fine/fee credits to be exported in the bursar integration, the minimum value must be set to zero, which means Alma will export fines of any amount even if they are very small.
   We would like to be able to set a minimum value for the fine export, but still export credits. Ideally we'd like a checkbox to tell Alma to apply the minimum value amount to credits as well as to debits. For example if we set the minimum value to $5 and check a box to include credits, Alma would export any fines over $5, as well as any credits over $5.

   Currently in order for fine/fee credits to be exported in the bursar integration, the minimum value must be set to zero, which means Alma will export fines of any amount even if they are very small.
   We would like to be able to set a minimum value for the fine export, but still export credits. Ideally we'd like a checkbox to tell Alma to apply the minimum value amount to credits as well as to debits. For example if we set the minimum value to $5 and check a box to include credits, Alma would export any fines over $5,… more

   13 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. User note: prevent overwritten via API when the check box is set option

   We would like to add a functionality (check box) in the admin Alma user record UI that allows preventing a manually added USER NOTES field from being overwritten by the API when the check box is set.

   This functionality will allow Alma admins to store some manual information in a USER NOTES without being overwritten via API when a record is being updated automatically

   •  

   12 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Browzine : Journals with multiple sources

   Libraries who are using Browzine are exporting our journals holdings file using a Google Scholar XML schema. For titles that have multiple sources, Browzine will based on their own algorithm to determine one source to be made available to the users in the Browzine interface. According to Third Iron, this "choosing algorithm" is designed to pick the source that has the widest coverage. This is fine in most of the cases but if we want to override this "decision", we will need to write in to Third Iron.

   Suggestion: To consider having a designated field in the portfolio record for libraries to indicate as “preferred source in Browzine”? This would allow libraries to easily flag out titles that we want to be visible in Browzine.

   Thank you.

   Libraries who are using Browzine are exporting our journals holdings file using a Google Scholar XML schema. For titles that have multiple sources, Browzine will based on their own algorithm to determine one source to be made available to the users in the Browzine interface. According to Third Iron, this "choosing algorithm" is designed to pick the source that has the widest coverage. This is fine in most of the cases but if we want to override this "decision", we will need to write in to Third Iron.

   Suggestion: To consider having a designated field in the portfolio record for… more

   11 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Allow granularity in API limits

   The Universities of Wisconsin make extensive use of APIs, both Alma and Primo, in our consortium.

   We use APIs for our locally developed discovery environment, for reporting purposes, and for staff/business processes where Alma functionality does not meet our needs.

   However, all these uses of APIs are forced to contend with one set of limits. So if we hit our limit for whatever reason - a bot crawling our catalog, a call-intensive app used by our staff, etc., ALL of our API using applications suffer and/or fail.

   UW is a responsible user of APIs and has an experienced development group that engages in prudent practices to minimize API calls. But the developer network/API limits provide us no way to prioritize the API calls needed by staff over those needed by our discovery environment. If we hit the limits, whatever applications are using API calls at that time suffer.

   We would like Ex Libris to provide some "buckets" for API keys to allow us to segregate the keys used by our staff/business processes from those used by our patrons. Furthermore, we'd like to be able to prioritize buckets so that we could guarantee that the API keys used by our business processes "come first" over those used elsewhere.

   In doing so, we'd be able to ensure our business processes, which are often time sensitive and scheduled to run at particular times of the day, continue to run even if our catalog is being crawled by bots is otherwise experiencing heavy use.

   The Universities of Wisconsin make extensive use of APIs, both Alma and Primo, in our consortium.

   We use APIs for our locally developed discovery environment, for reporting purposes, and for staff/business processes where Alma functionality does not meet our needs.

   However, all these uses of APIs are forced to contend with one set of limits. So if we hit our limit for whatever reason - a bot crawling our catalog, a call-intensive app used by our staff, etc., ALL of our API using applications suffer and/or fail.

   UW is a responsible user of APIs and has an experienced development group… more

   10 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Two-Factor Authentication (2FA) for developer portal

    Currently login to the developer portal https://developers.exlibrisgroup.com/ requires username and password. If a user account associated with an organisation is compromised this gives the malicious actor access to use/create API keys to do anything they want in Alma.

    For example a malicious actor could create an API key which allows them to access all the user information stored in Alma.

    Access to manage API keys should be locked down with 2FA, password login is not sufficient.

    9 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Provide all User Profile data via API

    Please provide at least GET API access to user profile data (Config -> User Management -> Roles and Registration -> Profiles). This should be full data: for each profile, include full roles and parameters.

    Currently, there is no good way to export user profile data from Alma. It does not seem to be available in Analytics; it's not in any of the code or mapping tables available via "config" APIs.

    We can use the Alma UI to export each profile to Excel individually... but that is not practical at scale, and the role data we can extract from Excel is not directly applicable / compatible with what's needed for the "user_role" data in the "user" APIs.

    Having accurate and complete user profile data available via API would make it much easier and safer to manage our staff permissions programmatically.

    Please provide at least GET API access to user profile data (Config -> User Management -> Roles and Registration -> Profiles). This should be full data: for each profile, include full roles and parameters.

    Currently, there is no good way to export user profile data from Alma. It does not seem to be available in Analytics; it's not in any of the code or mapping tables available via "config" APIs.

    We can use the Alma UI to export each profile to Excel individually... but that is not practical at scale, and the role data we can extract from Excel is… more

    9 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add activation note to Get PO Line API

    In the Get PO Line API (https://developers.exlibrisgroup.com/alma/apis/docs/acq/R0VUIC9hbG1hd3MvdjEvYWNxL3BvLWxpbmVzL3twb19saW5lX2lkfQ==/) the receiving_note for print acquisitions is accessible. However its' electronic purchase counterpart, the activation note, is not in the Get PO line API response.

    Can this field be added?

    8 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Expand API access to all record fields across all record types

    Libraries frequently use API access to Alma records to complete a variety of tasks, provide services, and support special projects. Currently, the types of records and fields that are accessible via APIs are limited. For example, in bibliographic records, the 024 (UPC) field data is inaccessible via the API. Please Expand API access to all record fields across all record types.

    8 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Add support for System for Cross-domain Identity Management (SCIM) standard

    System for Cross-domain Identity Management (SCIM) is a standard for automating the exchange of user identity information between identity domains, or IT systems. Supporting this standard would allow for better automation and SIS integration for institutions using Alma.

    https://en.wikipedia.org/wiki/System_for_Cross-domain_Identity_Management

    7 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. API access to Item's edit history

    For rolling back changes in a batch of items, it would be extremely useful to have API access to the Item Changes that are reported in the History tab of each item record.

    7 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Import PO Approvals Job schedule more than 1 time a day

    Currently the Import PO approvals job will only run once a day. Can this be scheduled to run multiple times a day.

    We are using rialto which is supposed to be quick way of ordering but jobs are not sent to vender straight away as it has to wait for the job to run adding delays

    If this could be scheduled multiple times a day it would greatly improve the timeline

    6 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Institutions working in a Campus level generate a monthly Alma Collection Report with InCites

    Please allow institutions working in a Campus level to use the institution’s electronic holdings with InCites to generate a monthly report in Web of Science. Per Ex Libris tech support (case #07213024), the JRC Cloud App is not designed to work when an institution has campuses configured. These reports would provide institutions with multi-faceted collection development and utilization analyses for journal titles.
    Documentation: https://developers.exlibrisgroup.com/appcenter/journal-citation-reports-jcr/

    6 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Prevent GOBI API from matching activated CZ records in IZ

    Problem - The matching method used in the API will ink to the CZ bib records if it is in the IZ. The match methods are not flexible in the API integration profile when compared to something like import profiles that allow ignoring the record from the Community Zone and creating a local record.

    We would like the API to always create a local bib even if a matching CZ record exists in the IZ. Or, at least make this an optional setting.

    6 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Check box option to disable Alma from appending file names in publishing profiles

    We publish files to many third party vendors. Some vendor systems must have their files named with a certain convention and CANNOT process them if that filename convention is altered in any way.

    Alma publishing profiles are current configured to append "_new" to the end of files it publishes, even if you specify a file name already. We would like the option to either enable or disable each publishing profile from appending the filenames it sends. They can be enabled by default, or not, but the option would be helpful.

    Use case: We are publishing files of electronic holdings to OCLC because the current OCLC Data Sync profiles as they exist within Alma do not handle electronic materials (see https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/090Integrations_with_External_Systems/030Resource_Management/110Publishing_to_OCLC#Publishing_Electronic_Holdings_to_OCLC ). OCLC asks for a specific file naming convention, and that name cannot be altered. The profile adds "_new" to the end of the file name, which prevents their system from processing the file entirely. As a result, we have to either manually download these incredibly large files, change the file name, the put them on OCLC's server, or write a script to do this for us with no coders on staff.

    We publish files to many third party vendors. Some vendor systems must have their files named with a certain convention and CANNOT process them if that filename convention is altered in any way.

    Alma publishing profiles are current configured to append "_new" to the end of files it publishes, even if you specify a file name already. We would like the option to either enable or disable each publishing profile from appending the filenames it sends. They can be enabled by default, or not, but the option would be helpful.

    Use case: We are publishing files of electronic holdings to… more

    5 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add an API endpoint to send email via Alma

    Library Open Workflows support sending email using the Alma Mail node, but this uses an internal API that is not usable outside of LOW. It would be really useful if this could be made generally available so that other applications and scripts integrated with Alma could benefit from sending emails through the Alma mail setup instead of having to configure email separately via SMTP, etc with all the resulting spam-filtering issues.

    4 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating