33 results found

1. 【NACSIS-CAT/ILL Cloud App】We would like to request that prefix matching search, similar to WebUIP, be implemented in the Cloud App as well.

   Unlike Western books, Japanese titles are not displayed word by word, so prefix matching search is frequently used.
   Therefore, it would be very helpful if prefix matching search could be enabled, as it is in WebUIP.

   The following three prefix matches are possible in WebUIP but not in the Cloud App. Could you please adjust the system to enable prefix matching search?
   (1) Cloud App “NACSIS-CAT/ILL” > Catalog > Book Bibliography
   (2) Cloud App “NACSIS-CAT/ILL” > Catalog > Journal Bibliography
   (3) Cloud App “NACSIS-CAT/ILL” > Catalog > Uniform Title Authority

   Thank you in advance.

   3 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  ·  Edit…  ·  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. Please add the feature „Chat between Institution Zones“ to the Metadata Editor

   Ex Libris should offer the option of creating a chat for each data record. This feature would facilitate communication between individual libraries regarding incorrect data records.
   Currently, communication concerning bibliographic records are sent by email via a mailing list. For a library that has many departments with numerous employees, it is difficult to develop a workflow for jointly processing these emails. In a chat, several people within an institution can communicate with each other without having to coordinate internally beforehand.
   But smaller libraries would also benefit from this chat function. When several emails are sent back and forth on a topic, it quickly becomes confusing.
   It is also more efficient and clearer if the communication about a data record can be found next to the data record itself.
   One way to integrate a chat function into individual records would be to add a “Chat between Institution Zones“ button to each record in the search view and/or in the Metadata Editor (see image Alma Chat 1.1 and Alma Chat 1.2).
   An editor should then open (a big window unlike the small window provided by the „Add Note“ option“), in which the written exchange between the libraries concerned can take place. One library sends a request to the other libraries, and the other libraries respond to it. The last library to respond, or the library that makes the final adjustments to the record, should change the status of the chat from “open” to “closed” This requires a drop-down menu within the chat editor (see image Alma Chat 2 + 3).
   All chats with the status „open“ in every Institution Zone should be searchable using the advanced search (see image Alma Chat 4). Chats with the status „closed“ could still be searched using the title or ID of the record via the simple search.

   Ex Libris should offer the option of creating a chat for each data record. This feature would facilitate communication between individual libraries regarding incorrect data records.
   Currently, communication concerning bibliographic records are sent by email via a mailing list. For a library that has many departments with numerous employees, it is difficult to develop a workflow for jointly processing these emails. In a chat, several people within an institution can communicate with each other without having to coordinate internally beforehand.
   But smaller libraries would also benefit from this chat function. When several emails are sent back and forth on a… more

   •  

   •  

   208 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…)
   14 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

3. Alma Split View Hides Main Menu, Affecting Cloud App Access

   After rolling out the new UI for the “All Titles Search” with split-view functionality, the main menu is no longer persistent. The menu (which contains location, notifications, cloud apps, etc.) disappears when entering split view.

   This is particularly problematic for institutions that frequently use cloud apps in their workflows—for example, when editing physical items. While cloud apps can be pinned before entering split view, this workaround is not satisfactory. Pinning apps adds unnecessary clicks and is easy to forget, resulting in frequent toggling in and out of split view.

   As a consequence, many staff members have stopped using cloud apps and instead revert to more manual and time-consuming options (often using Run a Job). In these cases, the new UI is not perceived as an improvement.

   To improve usability and maintain workflow efficiency, the main menu should remain visible in split view, similar to the Quick Links menu.

   After rolling out the new UI for the “All Titles Search” with split-view functionality, the main menu is no longer persistent. The menu (which contains location, notifications, cloud apps, etc.) disappears when entering split view.

   This is particularly problematic for institutions that frequently use cloud apps in their workflows—for example, when editing physical items. While cloud apps can be pinned before entering split view, this workaround is not satisfactory. Pinning apps adds unnecessary clicks and is easy to forget, resulting in frequent toggling in and out of split view.

   As a consequence, many staff members have stopped using cloud apps… more

   •  

   •  

   35 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

4. Multiple Logical Sets Attached to Logical Collections in Collection Discovery

   I would like to be able to create a Logical Collection in Collection Discovery that combines the results of at least two different logical sets.

   CASE EXAMPLE: I have been asked to create "New Book" collections for multiple departments that include both print books and ebooks. For the print books, the fields I need to query on are only available the creation of a Physical Titles search set. For the ebooks, the fields I need to query on are only in an Electronic Titles search set. Since I cannot merge the results into a single logical set, that means I need to create two different "New Book" collections for each department.

   I would like to be able to create a Logical Collection in Collection Discovery that combines the results of at least two different logical sets.

   CASE EXAMPLE: I have been asked to create "New Book" collections for multiple departments that include both print books and ebooks. For the print books, the fields I need to query on are only available the creation of a Physical Titles search set. For the ebooks, the fields I need to query on are only in an Electronic Titles search set. Since I cannot merge the results into a single logical set, that means I… 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  ·  Resource Management - General  ·  Edit…  ·  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. Make Existing Record Primary When Merging via Search Resources

   When merging records through Alma’s Search Resources, make the existing Alma record the Primary and the incoming external record the Secondary.

   Currently, when bringing in external records, Import and Integration Profiles treat the existing Alma record as Primary, but Search Resources makes the external record Primary. This inconsistency forces libraries to maintain two opposing sets of merge rules, depending on how the record enters Alma.

   Making the Alma record Primary in Search Resources would align the behavior with other workflows. This could be configurable or at least opt-in so libraries can adjust their merge rule settings in the External Search Resources configuration to coincide with the change.

   Benefits:
   Simplifies workflows by allowing a single set of merge rules.
   Reduces user confusion, since rule descriptions will match consistently across scenarios.
   Provides consistency in the Metadata Editor, where the record on the left will always be the Primary.

   When merging records through Alma’s Search Resources, make the existing Alma record the Primary and the incoming external record the Secondary.

   Currently, when bringing in external records, Import and Integration Profiles treat the existing Alma record as Primary, but Search Resources makes the external record Primary. This inconsistency forces libraries to maintain two opposing sets of merge rules, depending on how the record enters Alma.

   Making the Alma record Primary in Search Resources would align the behavior with other workflows. This could be configurable or at least opt-in so libraries can adjust their merge rule settings in the External Search… more

   8 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

6. Display of Collections in Collections Lobby in Primo VE

   Ability to only display digital collections in the Collections Lobby page of the Primo View, whose profile slot includes the collection’s local scope.
   Case number 08113340

   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  ·  Resource Management - General  ·  Edit…  ·  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. versions in new interface

   In the new interface it is no longer possible to see dates of changes other than the original creation date and who created the record plus the last edited date and who made that change. Please reinstate the ability to see more version change dates without editing the record so that users who do not have the Cataloguer role can see this information in view-only mode.

   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  ·  Resource Management - General  ·  Edit…  ·  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. Add the ability to enter a string of delimited values in bulk to Alma Advanced Search fields

   Currently adding fields and values to Alma Advanced Search is only possible one by one. This is a painfully slow and click-heavy activity when there are many parameters to be added. This also risks slowing down Alma UI when upwards of several hundred fields (as advised by Ex Libris Support).
   It is proposed to support many values to be copy and pasted in to a single field by a string with separator, such as an OR Boolean or semi-colon representing the OR.

   Use case: We use a logical set to fuel our Collection Discovery collection titled “Aboriginal and Torres Strait Islander authors”. We’re now in the process of shifting this from a curated collection by manual addition of a bibliographic local field to a single work for the author to a comprehensive collection for all works we hold by the Authority IDs for the identified authors. We have already contributed more than 70 new LCNAMES Authorities via NACO membership as part of this work supporting recognition of First Nations peoples and for our faculty to indigenise their curriculum by ease of ability to find our related holdings in Primo by Collection facet and collection. However, Alma makes this process difficult in our logical set in having to one by one add the Authority IDs. Ex Libris confirmed there is no current functionality to meet this need.

   Example string for Authority ID contains phrase no2025050743 OR no2025048340 OR no2025018153 OR no2025013888 OR no00089878 OR no2025019805 OR no2025026097 OR no2025018142 OR no2025018141 OR no2025061608 OR no2025019804 OR no2025020415 OR no2025030597 OR n93058348 OR no2025034631 OR no2025022265

   See screenshot attached for the current situation and improvement option suggestions.

   Currently adding fields and values to Alma Advanced Search is only possible one by one. This is a painfully slow and click-heavy activity when there are many parameters to be added. This also risks slowing down Alma UI when upwards of several hundred fields (as advised by Ex Libris Support).
   It is proposed to support many values to be copy and pasted in to a single field by a string with separator, such as an OR Boolean or semi-colon representing the OR.

   Use case: We use a logical set to fuel our Collection Discovery collection titled “Aboriginal and Torres Strait… 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  ·  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

9. Enable local extensions on MARC 79X and 89X

   OCLC Bibliographic Formats and Standards sets out tags 79X (790-799) and 89X (896-899) as valid for local uses. These ranges should be available for network zone members to use as well. Adopting these ranges will allow catalogers to directly adapt records from WorldCat into a network and add local extensions without having to remap from the OCLC-supported field to a field in Alma, such as a 9XX.

   Catalogers primarily use these fields to enter details such as authors with local affiliations (e.g., current faculty members), dissertation advisors or members of dissertation committees, and the college within the institution supervising the dissertation. These are locally-relevant data that are not always relevant in the universal, shared record. Allowing their inclusion enables a network member to highlight what makes the record and information valuable to the institution.

   Moreover, the use of a local extension for this data helps protect the data from removal by other network members, and the data are protected if the network record is overlaid by a WorldCat record that doesn't retain that data.

   OCLC Bibliographic Formats and Standards sets out tags 79X (790-799) and 89X (896-899) as valid for local uses. These ranges should be available for network zone members to use as well. Adopting these ranges will allow catalogers to directly adapt records from WorldCat into a network and add local extensions without having to remap from the OCLC-supported field to a field in Alma, such as a 9XX.

   Catalogers primarily use these fields to enter details such as authors with local affiliations (e.g., current faculty members), dissertation advisors or members of dissertation committees, and the college within the institution supervising the… more

   8 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

10. MD editor save marc tags chronologically

    Upon save any MARC tags that are in the wrong chronological order are saved in the correct order.

    13 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…)
    1 comment  ·  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

11. Add Option to Handle Multi-Matches Automatically Based on Brief Level

    Alma’s import profile functionality currently includes the option "Do not override/merge a record with lower brief version", which ensures that an incoming record is not loaded if its brief level is lower than that of the matched record in Alma.

    We would like to see this functionality extended to enable handling multi-matches automatically. Currently, when an incoming record matches multiple existing records in Alma, the import process still flags this as an multi-match issue, even if all matched records in Alma have a higher brief level than the incoming record. These cases must then be reviewed and resolved manually by staff, despite the fact that the incoming record can be rejected automatically based on its brief level.

    To support this, a checkbox like "Discard lower brief level record automatically" could be added to the "Automatic Multi-Match Handling" section under the "Match Profile" tab in an import profile. This would reduce the number of manual staff interventions and increase efficiency in working with Alma for metadata specialists.

    Alma’s import profile functionality currently includes the option "Do not override/merge a record with lower brief version", which ensures that an incoming record is not loaded if its brief level is lower than that of the matched record in Alma.

    We would like to see this functionality extended to enable handling multi-matches automatically. Currently, when an incoming record matches multiple existing records in Alma, the import process still flags this as an multi-match issue, even if all matched records in Alma have a higher brief level than the incoming record. These cases must then be reviewed and resolved manually by… more

    10 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…)
    1 comment  ·  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

12. Change the order of the dropdown menu for 'Run a Job'

    It would save a lot of time and extra clicks if the first option in the dropdown menu for 'Run a job' was switched to 'Name', rather than 'Description'.

    7 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

13. Manage Sets without Repository Manager permissions

    It would be nice if we could update and manage repository sets without needing the Repository Manager role. Without it, staff can create sets and run queries, but they can't update any sets that weren't personally created by them, making it so that managers are having to make small updates that could easily be made by staff.

    7 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…)
    1 comment  ·  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

14. Add extra filter operators to date fields in title search

    Add the following filter operators to all titles search:
    -Is within last (days)
    -Is older than (days)
    -Is within next (days)

    to filters in all titles search such as MMS creation date (title) and modification date (title).

    These filters are already available in user search.

    •  

    3 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  ·  Edit…  ·  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. Manage Deleted Repository--ability to select and restore a group of records

    Manage Deleted Repository is a helpful feature helps us restore records that were mistakenly deleted. However, it only allows us to restore records one at a time by clicking a "Restore" button next to each record. This is not workable when a large number of records need to be restored. We need functionality that will allow us to select and restore groups of records.

    The Restoring Records Removed or Changed by Jobs functionality (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/070Managing_Jobs/020Manual_Jobs_on_Defined_Sets#Restoring_Records_Removed_or_Changed_by_Jobs) does not sufficiently address this need, as it can only restore repository content deleted by a job, not records deleted manually. Also, even in cases where records were mistakenly deleted by a job, it is possible that much of the rest of the job was correct (such as a CZ sync job) so we do not want to restore the whole job; we want to restore just some of the deleted repository content.

    This Idea suggests that, in the Manage Deleted Repository, there should be checkboxes, like in the Community Zone Updates Task List and the Authority Control Task List, that allow us to select individual items or select all items on the page. There should also be options to Restore Selected or Restore All. I have attached a mockup (based on CZ Updates Task List and Authority Control Task List) showing how this would look. For example, in the interface shown in the mockup, I could:

    1) Check individual checkboxes next to records 1, 2, and 3 and then click "Restore Selected" to restore the 3 pieces of content.
    2) Check the "Select All" button to select all 50 records on the page and then click "Restore Selected" to restore all 50 pieces of content.
    3) Select "Restore All" to restore all 305 pieces of content retrieved by my current search criteria.

    Manage Deleted Repository is a helpful feature helps us restore records that were mistakenly deleted. However, it only allows us to restore records one at a time by clicking a "Restore" button next to each record. This is not workable when a large number of records need to be restored. We need functionality that will allow us to select and restore groups of records.

    The Restoring Records Removed or Changed by Jobs functionality (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/070Managing_Jobs/020Manual_Jobs_on_Defined_Sets#Restoring_Records_Removed_or_Changed_by_Jobs) does not sufficiently address this need, as it can only restore repository content deleted by a job, not records deleted manually. Also, even in… more

    •  

    53 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

16. Display all 035$a values for the Record Number column in Table view of Titles UI

    In the new titles search UI, the Record Number field lists only the first listed 035$a value of the record, followed by "and others." This is true for both the record view, where keeping data compact makes sense, and on the table view where one might expect to see more values for repeating data fields.

    If the table view showed all of the 035$a values in the record number column, this would increase the utility of this view, as it would allow staff to recognize OCLC and other system numbers among the list without requiring a click and scroll through each individual record. This would also restore functionality lost in the previous UI, where staff could click an option on the record screen to view the list of other record numbers.

    In the new titles search UI, the Record Number field lists only the first listed 035$a value of the record, followed by "and others." This is true for both the record view, where keeping data compact makes sense, and on the table view where one might expect to see more values for repeating data fields.

    If the table view showed all of the 035$a values in the record number column, this would increase the utility of this view, as it would allow staff to recognize OCLC and other system numbers among the list without requiring a click and scroll through… more

    •  

    12 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

17. Collection - report who added title and when

    When adding titles to Collections (Resources\Manage Collections) it would be helpful if it reported who and when a title was added to the collection. Report of this via Analytics would be preferable but displaying in Alma would be a start.

    3 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  ·  Edit…  ·  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. New title search - include subfield t in Names section

    we would like to see subfield t in the names section of the new titles search. This subfield shows when it is present in field 600 but not in 700. This would be very useful when searching for Author/title

    • 

    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…)
    1 comment  ·  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

19. Support Processing System Control Number (035) Updates in Imported Authority Record Updates

    Currently, Alma's authority-control jobs do not process updates to MARC21 authority tag 035 (System Control Number) when the update occurs via an authority import profile as the update of an existing record, i.e. there is a match between the existing authority record in Alma and the incoming authority record via the authority import profile. In contrast, the update is processed when there is no match with an existing record, i.e. the record is new to Alma, or, when the authority record has been updated manually via the MDE.

    This was clarified by Ex Libris in a support ticket (case 07255325). According to that explanation, the workflow for updating automatically bibliographic records based on updated authority records (in case of ID-based authority linking and local authority records) - https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Metadata_Management/060Working_with_Authority_Records#Updating_the_Authority_Record_ID_Automatically_in_Bibliographic_Records - only applies when the imported record is new to Alma, but not when an update to an existing authority record is concerned.

    This is a severe limitation of the current design in Alma that prevents the automatic handling of authority record merges, which involve, in the authority record, the addition of 035 $z (canceled system control number) and in the bib record the replacement of $0 in authority-controlled fields and the update of those authority-controlled fields based on the updated $0.

    One possible workaround is to manually modify tag 035 in the authority record after the imported authority record update, e.g. by adding "035 $a0", so that authority-control jobs will process the tag anew. An alternative workaround is to delete the existing authority record in Alma before the import, allowing the updated record to be treated as new and processed by Alma's authority-control jobs. However, both workarounds require manual intervention, which undermines the idea of library automation.

    We request that Alma processes updates to tag 035 even when the incoming authority record is an update rather than a new record. This enhancement reduces the need for manual intervention and improves the efficiency of authority control in Alma.

    Currently, Alma's authority-control jobs do not process updates to MARC21 authority tag 035 (System Control Number) when the update occurs via an authority import profile as the update of an existing record, i.e. there is a match between the existing authority record in Alma and the incoming authority record via the authority import profile. In contrast, the update is processed when there is no match with an existing record, i.e. the record is new to Alma, or, when the authority record has been updated manually via the MDE.

    This was clarified by Ex Libris in a support ticket (case 07255325).… more

    11 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

20. Add filters and columns to import profiles screens for zone, protocol, scheduling, status

    The Import Profiles screen has few options for narrowing the list of profiles if one isn't certain of the profile name, or if descriptions are too similar. Please add filters and columns to the display screen--preferably sortable columns--for fields that distinguish the zone, scheduling, and status for import profiles.

    Priority 1, Zone: Users should be able to clearly see whether an import profile is using the network zone or the institution zone for an import profile, as this affects the workflow and processing of records being imported.

    Priority 2, Status: While the Active/Inactive status of a profile may be useful for limiting what appears on the Import screen (Resources > Import > Import), when viewing the profiles via Manage Import Profiles, users will want to limit or sort based on whether a profile is active or inactive.

    Priority 3, Scheduling: When viewing the Manage Import Profiles screen, it should be clear to users whether an import profile is scheduled to run regularly or is used on demand only. At minimum, display scheduler status of active or inactive. Preferably, if scheduling is active, display the scheduled day and time.

    Priority 4, Protocol: When viewing the Manage Import Profiles screen, it should be clear to users whether an import profile is configured for upload from the user desktop or from an FTP server. A column display should indicate FTP, upload, or OAI.

    The Import Profiles screen has few options for narrowing the list of profiles if one isn't certain of the profile name, or if descriptions are too similar. Please add filters and columns to the display screen--preferably sortable columns--for fields that distinguish the zone, scheduling, and status for import profiles.

    Priority 1, Zone: Users should be able to clearly see whether an import profile is using the network zone or the institution zone for an import profile, as this affects the workflow and processing of records being imported.

    Priority 2, Status: While the Active/Inactive status of a profile may be useful… more

    4 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…)
    1 comment  ·  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