11 results found

1. Revert the changes made to Job: Update PO Lines Information Advanced

   This really pertains to Admin >> Run a Job, but please revert the change you made to the Job: Update PO Lines Information Advanced. Currently, the job will NOT run if there are invoices on the PO. Before this change was made it did not matter.
   It does not matter to the library because the terms of a continuous order can and do change (it was a subscription, now it is offered as a continuation order), how a library chooses to catalog an item can and does change (a title was a serial, then it became a monographic series) So we need to change the PO line type. That there are invoices on the PO is irrelevant - the order is continuing, we just need to change the order type. So now it is impossible to change a PO from type: Physical standing order non-monograph to type: Print Book standing order for an active order. Instead, to make this change, I have to close the existing PO AND create a new PO and send the new PO line /PO information to the vendor even though the order continues.
   The old job was very useful because a lot of our serial POs were imported into Alma with the wrong PO line type and we are still cleaning them up. So we need this job to do what it used to do.

   This really pertains to Admin >> Run a Job, but please revert the change you made to the Job: Update PO Lines Information Advanced. Currently, the job will NOT run if there are invoices on the PO. Before this change was made it did not matter.
   It does not matter to the library because the terms of a continuous order can and do change (it was a subscription, now it is offered as a continuation order), how a library chooses to catalog an item can and does change (a title was a serial, then it became a monographic series) So… more

   1 vote

   Vote 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  ·  Acquisition - PO & POLine  ·  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
   Under Review  ·  AdminZohar Shemesh (zohar.shemesh@exlibrisgroup.com, Ex Libris) responded

   Dear Community,

   We plan to enhance the “Update PO Lines Information - Advanced” job as follows:

   (1) When PO lines have linked invoices while changing their type cross inventory and/or cross continuity, they will not be skipped in this job when the invoice is in status "In Review" / "Closed".

   When invoice status is “Waiting for Approval” / “Ready to be Paid” / “Waiting for Payment”, the PO line will be skipped. This is because these statuses mean that the invoice is being progressed. “Ready to be Paid” / “Waiting for Payment” are statuses that are used for integration with finance system, changing the invoice while it is still in progress might cause issues.

   (2) When the PO line type change is not consistent with the PO packaging rules, and the PO line is part of a PO, it will be moved out of the PO and set back to “In Review”. Cancellation letter will be sent when relevant.

   The following PO line type changes were supported before February 2025 release development, and used to change the PO line type and keep it in the PO:

   1. ‘Generic’ inventory format to ‘Physical’ / ‘Electronic’ / ‘Digital’ and vice versa > we will keep these PO lines in their PO.
   2. ‘Electronic’ (Portfolios) inventory format to ‘Electronic’ (Collections) and vice versa > we will keep these PO lines in their PO.
   3. ‘Standing Order’ continuity type to ‘Subscription’ > we will now move the PO line out of the PO as this is not consistent with the packaging rules.

    

   To sum up:

   > An invoice linked with the PO line will cause it to be skipped in the job only when the invoice is in status “Waiting for Approval” / “Ready to be Paid” / “Waiting for Payment”

   > The PO behavior for PO line type changes that were supported before February 2025 release will be changed, except for a change of continuity type from “Standing Order” to “subscription.”

   
   

   Regarding the example in the current Idea Exchange –

   “Physical - Standing Order Non-Monograph” has the continuity type Continuous

   “Print Book - Standing Order” has the continuity type Standing Order

   And therefore, in case of such change, the PO line will be moved out of the PO.

   
   

   Please find attached a design document.

   
   

   Thanks,

   Zohar Shemesh

   Alma Product Team

   Dear Community,

   We plan to enhance the “Update PO Lines Information - Advanced” job as follows:

   (1) When PO lines have linked invoices while changing their type cross inventory and/or cross continuity, they will not be skipped in this job when the invoice is in status "In Review" / "Closed".

   When invoice status is “Waiting for Approval” / “Ready to be Paid” / “Waiting for Payment”, the PO line will be skipped. This is because these statuses mean that the invoice is being progressed. “Ready to be Paid” / “Waiting for Payment” are statuses that are used for integration with finance system, changing the invoice while it is still in progress might cause issues.

   (2) When the PO line type change is not consistent with the PO packaging rules, and the PO line is part of a PO, it will be moved out of the PO and set back to… more

2. NR - Normalization rules editor -- fix display to ltr + use monospaced font

   1.
   Currently there's a problem with the NR editor when there are too many rtl characters (Hebrew, Arabic, etc.) in the NR, the whole display changes to rtl. This renders the NR unintelligible and makes editing it in Alma impossible -- you have to edit it outside Alma

   We would like the direction of the NR editor to be fixed to ltr regardless of the composition of the characters used

   2.
   We would like to have the NR editor use a monospaced font. This would make the code neater and easier to read

   •  

   24 votes

   Vote 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  ·  Metadata Management  ·  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
   Under Review  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello everyone,

   I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed to handle complex normalization tasks and offers the flexibility of a full programming language, enabling advanced data manipulation. It will complement our existing normalization rules based on DROOLS, preserving all of its current capabilities. 

   Would the addition of this new type of normalization rule address the requirement outlined in this idea?

3. Issue with Embargoed Bibliographic Record Display in Primo

   Current situation:
   Despite configuring an embargo on a digital file, the bibliographic record continues to show up in Primo. In an effort to resolve the issue, we suppress the bib record, but even after the embargo has expired after two years, the record is not visible in Primo.

   Desired outcome:

   If an embargo is in place, it can affect whether the bibliographic record is suppressed or not. Alternatively, when the embargo period ends, the library may receive a notification to prompt staff to manually remove the suppressed status. The desired outcome is to ensure that the bibliographic record is either suppressed or unsuppressed depending on the embargo status, and that staff are notified to make any necessary updates at the end of the embargo period.

   We would greatly appreciate it if you could provide a suitable solution to ensure that the record is displayed in Primo after the embargo has expired.

   Current situation:
   Despite configuring an embargo on a digital file, the bibliographic record continues to show up in Primo. In an effort to resolve the issue, we suppress the bib record, but even after the embargo has expired after two years, the record is not visible in Primo.

   Desired outcome:

   If an embargo is in place, it can affect whether the bibliographic record is suppressed or not. Alternatively, when the embargo period ends, the library may receive a notification to prompt staff to manually remove the suppressed status. The desired outcome is to ensure that the bibliographic record is either… more

   39 votes

   Vote 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…)
   Under Review  ·  0 comments  ·  Resource Management - Digital  ·  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. Create a way to distinguish volumes for a single title

   There is a title in Gale resources, Encyclopedia of African-American culture and history : the Black experience in the Americas, that has several portfolios available. Each portfolio links to a different volume in Gale. Each portfolio has unique linking but if you see the title in Primo, you will see only the title listed, many times. I had to add a volume note to each portfolio so users could tell each title apart. This was not the only title I've found that is like this. Ex Libris stated there is no way to add the volume to the title. It was a lot of work tracking down the volume numbers. It would be nice if there was a way to display a volume number for issues similar to this.

   There is a title in Gale resources, Encyclopedia of African-American culture and history : the Black experience in the Americas, that has several portfolios available. Each portfolio links to a different volume in Gale. Each portfolio has unique linking but if you see the title in Primo, you will see only the title listed, many times. I had to add a volume note to each portfolio so users could tell each title apart. This was not the only title I've found that is like this. Ex Libris stated there is no way to add the volume to the title. It… more

   250 votes

   Vote 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…)
   3 comments  ·  Resource Management - Electronic  ·  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
   Under Review  ·  AdminTamar Ganor (Admin, Ex Libris) responded

   Hello,

   This will require some development, since currently there is no automated way to identify the relevant information and add it to the portfolios.

   We will look into the development options we have, and will update once we have a timeline.

   Kind regards,

   Tamar Ganor

   Content Product Manager

5. Position sensitive NRs (Normalization Rules) - ISBD punctuation

   ISBD punctuation is determined by the following subfield.
   For example:
   In 245 the subfield preceding $$b must end in one of the following:
   1. space + colon
   2. space + semicolon
   3. space + Arabic semicolon (if your cataloging language is Arabic)
   4. space + equal sign

   The NR syntax currently does not offer any straightforward solution for correcting ISBD punctuation.

   We request the development of an NR function that will suffix the subfield with a string based on the subfield that follows it, including the case in which a subfield is the last one.

   I think it would be best if the user could specify the string themselves.

   I prefer marking each subfield and fix the punctuation using other functions. ex. adding "_b_" before $$b, "_c_" before $$c, "_last_" at the end of the last subfield etc. to all 24X fields.
   Others might prefer to have a specific string based on the order, such as " /" before $$c in 245 if it doesn't exist.

   In any case, please consider developing this function.

   ISBD punctuation is determined by the following subfield.
   For example:
   In 245 the subfield preceding $$b must end in one of the following:
   1. space + colon
   2. space + semicolon
   3. space + Arabic semicolon (if your cataloging language is Arabic)
   4. space + equal sign

   The NR syntax currently does not offer any straightforward solution for correcting ISBD punctuation.

   We request the development of an NR function that will suffix the subfield with a string based on the subfield that follows it, including the case in which a subfield is the last one.

   I think it would be… more

   76 votes

   Vote 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…)
   3 comments  ·  Metadata Management  ·  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
   Under Review  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello everyone,

   I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.

   Would the addition of this new type of normalization rule meet the requirements outlined in this idea?

6. Suggestions for Normalization Rules (NR) functions

   Hello,

   Please see the attached file.
   We would appreciate it if the suggested Normalization Rules functions would be developed in Alma.

   Thanks

   • 

   218 votes

   Vote 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…)
   6 comments  ·  Metadata Management  ·  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
   Under Review  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello everyone,

   I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.

   Would the addition of this new type of normalization rule meet the requirements outlined in this idea?

7. Better management of serial prediction when publication frequency changes

   Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.

   It would save a lot of time if Alma could change the description (number, date, …) only for the items that are impacted by a new publication during the year. We would just have to fill the « Next prediction item’s information » with the new frequency.
   This enhancement would save a lot of time to catalogers.

   Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.

   It would save a lot of time if… more

   414 votes

   Vote 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…)
   Under Review  ·  10 comments  ·  Resource Management - Physical  ·  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. Create a "natural language" editor to create Normalization rules

   The process for creating Normalization rules is unnecessarily complex and difficult, particularly for those of us who are not familiar with Drools logic. Our previous LSP had an intuitive interface which made creating rules to change details in MARC records much less time consuming. Ex Libris would do well to create such an interface.

   16 votes

   Vote 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…)
   Under Review  ·  2 comments  ·  Metadata Management  ·  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. Full PCRE Regular Expressions in Normalization rules

   Supporting full PCRE regular expressions would make Normalization rules so powerful. Allow capturing data in one place and re-using it somewhere else, checking for substrings, etc.

   28 votes

   Vote 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  ·  Resource Management - General  ·  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
   Under Review  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello everyone,

   I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.

   Would the addition of this new type of normalization rule meet the requirements outlined in this idea?

10. Allow **** or Python plugins for normalization rules

    The Drools framework in place for normalization rules is very limited compared to real programming script languages like **** or Python. Live would be way easier, much more efficient and some things impossible with Drools would be possible with **** (like in SFX parsers) or Python for those who can use these languages.

    54 votes

    Vote 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…)
    3 comments  ·  Resource Management - General  ·  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
    Under Review  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello everyone,

    I’d like to share our plans to introduce support for XSL (Extensible Stylesheet Language) normalization rules. This new feature is designed for handling complex normalization tasks. It offers the flexibility of a full programming language, enabling advanced data manipulation. This will complement our existing normalization rules based on DROOLS, maintaining all of its current capabilities.

    Would the addition of this new type of normalization rule meet the requirements outlined in this idea?

11. Show Pickup location in the tables "Requests" and "Loans" in Patron Services

    It would be helpful ig the information “Pickup location” could be added as a column in the tables “Requests” and “Loans” in the “Patron services” in order to see the destination chosen by the Patron. Furthermore, the "Pickup location" should be displayed in Primo in the patron’s account - also in the "Loans" not only in the "Requests".

    321 votes

    Vote 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…)
    Under Review  ·  7 comments  ·  Fulfillment - General  ·  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