123 results found

1. 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

   •  

   48 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

2. 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

   •  

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

3. Add a job for adding Repository search labels

   please create a job to add Repository search labels for titles and holdings based on a set. This would be a convenient solution for managing large numbers of records in the new UI and the addition to bulk labeling.

   30 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

4. 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

5. convert bib. records to sub collections in bulk

   We discovered in Alma the possibility of creating collections of archival materials, which gives us the opportunity to create a hierarchy of collections and subcollections. Visually it also looks good. We do not yet have DIGITAL ALMA, we cannot load materials themselves, but a reader receives comprehensive and detailed information about library collections.
   At the same time, we encountered a problem: we have collections with dozens of subcollections, and each subcollection needs to be edited separately. It takes precious time and a feeling of wasting energy on creating records of subcollections, when we have their bibliographic records ready with all the information.
   An option of creating subfields in bulk for the number of bibliographic records, just as there is the possibility of loading bibliographic records for a specific collection.

   We discovered in Alma the possibility of creating collections of archival materials, which gives us the opportunity to create a hierarchy of collections and subcollections. Visually it also looks good. We do not yet have DIGITAL ALMA, we cannot load materials themselves, but a reader receives comprehensive and detailed information about library collections.
   At the same time, we encountered a problem: we have collections with dozens of subcollections, and each subcollection needs to be edited separately. It takes precious time and a feeling of wasting energy on creating records of subcollections, when we have their bibliographic records ready with all… 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

6. Add ability to abort jobs when they are for information only, such as when exporting data or running overlap analysis

   Currently it is more common than not for jobs in Alma to be missing an option to Abort them under Monitor Jobs > Running.
   This is a highly frustrating situation where the only option is to open a Support case to request for the job to be aborted, and wait days for response.
   In the meantime, staff work is completely halted for this while we wait for Support.

   It is understandable that the Abort option is not present in cases where there could be negative impact on records, such as initiating an job update to change the records.
   But it is not reasonable to not have an Abort option when the jobs are for scenarios such as an export from the CZ Update Task List and by Overlap and Collection Analysis.
   In such workflows, the jobs may stall when extremely large, and with an Abort option the user could start again with a smaller export or smaller data set comparison.
   But instead right now we have stuck Overlap job for 3 days and have had cases when the CZ export was running for several weeks.

   This request would save on both library staff time and Support analyst time, to give control to the library to abort such information-only jobs in no-impact scenarios when the jobs are clearly stalled, and ensure that library work can continue.

   Currently it is more common than not for jobs in Alma to be missing an option to Abort them under Monitor Jobs > Running.
   This is a highly frustrating situation where the only option is to open a Support case to request for the job to be aborted, and wait days for response.
   In the meantime, staff work is completely halted for this while we wait for Support.

   It is understandable that the Abort option is not present in cases where there could be negative impact on records, such as initiating an job update to change the records.
   But it… 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

7. 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

   • 

   75 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

8. 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

9. Searchability for MARC 361

   We would like to be able to search MARC-361 in Alma, if possible also specifically in subfields of the 361.

   https://www.loc.gov/marc/bibliographic/bd361.html
   https://www.loc.gov/marc/holdings/hd361.html

   107 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

10. 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

11. Add MMS to title list search options in Collection Resource Editor

    When searching the list of titles assigned to a collection, users can only search by title or publisher. It would be helpful if there was also the option to search by MMS ID since this allows for more precise retrieval. See screenshot: https://app.screencast.com/sCZbTHJ39CcHE

    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

12. Sorting results of non-English external searches performed through SRU.

    When performing external searches via SRU in languages other than English, the results are first sorted in English before being sorted in the respective language. We request that the results be sorted in the search language first.

    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

13. Adding Facets to Alma's internal All Titles, Physical Titles, and Physical Items searches

    Currently, a search within Alma allows for a limited number of facets to filter a user's search when searching "All Titles", "Physical Titles", and "Physical Items". These only include the following facets: "Material Type", "Resource Type", "Language", and "Publication Year."

    In contrast, Primo VE's public search has many more configurable options that include "Location", "Creation Date", "Collection", "Availability/Peer Review", etc. It seems odd that Alma would be unable to also use some of these options since they're configured within Alma. At the very least, having "Location" added as a facet would be helpful for seeing where items are in a library's holdings at a glance, but increased configuration options to match Primo's capabilities would be logical.

    Currently, a search within Alma allows for a limited number of facets to filter a user's search when searching "All Titles", "Physical Titles", and "Physical Items". These only include the following facets: "Material Type", "Resource Type", "Language", and "Publication Year."

    In contrast, Primo VE's public search has many more configurable options that include "Location", "Creation Date", "Collection", "Availability/Peer Review", etc. It seems odd that Alma would be unable to also use some of these options since they're configured within Alma. At the very least, having "Location" added as a facet would be helpful for seeing where items are in a… more

    22 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

14. Additional "Suppress from FRBR/dedup" option and display

    When viewing a bib record, the pop-out information to the side of the screen lists whether or not the bib is suppressed from discovery and suppressed from search. It would be helpful if this info also contained whether the bib was suppressed from FRBR/dedup.

    Additionally, when you edit a bib record, you can select "Suppress from Discovery" and "Suppress from External Search" under the Record Actions dropdown menu. It would be helpful if there was also a "Suppress from FRBR/dedup" here.

    •  

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

15. Display Number of Records in Set Information Section

    It would be extremely beneficial to have the ability to view the number of records in a set directly within the Set Information Section, without the need to click through to the content.

    Specifically, adding a line such as “Number of Records: ####” in the Set Information Section would streamline the process of sorting through sets. For example, when managing multiple sets of items for withdrawal, it would allow me (or my students) to quickly ascertain the number of remaining items without the need to navigate into each set, view the content, and then return to the previous screen.

    This enhancement would significantly improve the efficiency of managing record sets.

    It would be extremely beneficial to have the ability to view the number of records in a set directly within the Set Information Section, without the need to click through to the content.

    Specifically, adding a line such as “Number of Records: ####” in the Set Information Section would streamline the process of sorting through sets. For example, when managing multiple sets of items for withdrawal, it would allow me (or my students) to quickly ascertain the number of remaining items without the need to navigate into each set, view the content, and then return to the previous screen.

    This… 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

16. Improve the efficiency and accuracy of Check call no.

    In the Aleph environment, when a cataloger presses F3 in the MARC tag of call number (050), they can see "all" similar call numbers. This helps them to decide the call number for the record they are working on. The system does not differentiate whether these are physical or electronic resources, or whether they have holdings. However, in the Alma environment, when in the same call number (050) MARC tag, it is not possible to see "all" call numbers of records in the system, especially not for electronic resources. This significantly increases the difficulty for catalogers in deciding the call number. Even for electronic resources, we hope that each call number is unique. Can we see "all" call numbers, regardless of whether they are physical or electronic, at once?

    In the Aleph environment, when a cataloger presses F3 in the MARC tag of call number (050), they can see "all" similar call numbers. This helps them to decide the call number for the record they are working on. The system does not differentiate whether these are physical or electronic resources, or whether they have holdings. However, in the Alma environment, when in the same call number (050) MARC tag, it is not possible to see "all" call numbers of records in the system, especially not for electronic resources. This significantly increases the difficulty for catalogers in deciding the call… 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…)
    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. Improve "Select all" search results selection

    When running a search within Alma, we have the option to "Select All", at which point we can accomplish various tasks like "Push selected to MDE" (for a Physical Titles search), "Add to Itemized Set" and "Create Itemized Set" (for a Physical Items search), etc.

    However, when clicking "Select All", this only selects the results on that page of results, which is capped at 50. If you create a search with many pages of results, you would have to take action on each page individually. Clicking "Select All" should actually select all results, not just the results on that page--or at least we should have an additional option that would specifically select results visible on that page.

    When running a search within Alma, we have the option to "Select All", at which point we can accomplish various tasks like "Push selected to MDE" (for a Physical Titles search), "Add to Itemized Set" and "Create Itemized Set" (for a Physical Items search), etc.

    However, when clicking "Select All", this only selects the results on that page of results, which is capped at 50. If you create a search with many pages of results, you would have to take action on each page individually. Clicking "Select All" should actually select all results, not just the results on that page--or… more

    50 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

18. Add permission to remove items from sets to more Alma roles

    Several of our cataloging workflows are based on multiple catalogers working off of a public Alma set of items to be cataloged. After they catalog an item, they remove it from the set. The ability to remove records from sets created by others requires the Repository Manager role. Currently we have to add the Repository Manager role to catalogers to get the "remove from others' sets" functionality, and we don't want to grant the other advanced permissions along with that role.
    Please add the ability to remove items from sets created by others to additional Alma roles that are lower than Repository Manager. It seems appropriate to be added to the Cataloger Extended role.

    (We're aware of the Cataloger "Manage sets" permission to "release" instead of "remove" items from sets in the MDE, but that won't work for this workflow. Our sets are itemized and larger than 200 items so cannot be sent to MDE for item release. Also, this functionality does not give the ability for multiple catalogers to remove items from a public list.)

    Several of our cataloging workflows are based on multiple catalogers working off of a public Alma set of items to be cataloged. After they catalog an item, they remove it from the set. The ability to remove records from sets created by others requires the Repository Manager role. Currently we have to add the Repository Manager role to catalogers to get the "remove from others' sets" functionality, and we don't want to grant the other advanced permissions along with that role.
    Please add the ability to remove items from sets created by others to additional Alma roles that are lower… more

    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

19. Display of the 1,000 most recent linked data records in Alma and Primo

    It is not possible to display all linked data records since the number is limited to 1’000. For better user convenience, at least the 1’000 most recent records should be displayed and not the 1’000 oldest or randomly selected records.
    Especially in the case of journals and monographic series that have been published for a long time, 1,000 linked records are not uncommon and the most recent ones are usually of interest.

    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

20. No relation "Replaces/Replaced by" between records due to entry of invalid ISBN (020 $z)

    If there are two records in Alma, one that has 020 $a u and another that has 020 $a v and 020 $z u, the both records will be related by the system with the relation: Replaces/Replaced by. The 020 $z is understood as a "cancelled" ISBN and therefore included in the job that calculates the relations.

    In the vast majority of cases we know 020 $z is a false/invalid ISBN: a publisher mistakenly(!) uses the same ISBN in two different resources that have nothing to do with each other. However, according to the international rules for describing resources, the erroneously printed ISBN information must also be recorded in the catalogue record (MARC field 020 $z) so that the resource can be searched using all the information it contains.

    Linking these two works is completely senseless from our point of view as the resources have nothing to do with each other. Furthermore it is confusing for our users - especially regarding the relationship: Replaces/Replaced by.

    We have no examples to support your view of 020 $z for "cancelled" ISBNs and we therefore ask you to remove 020 $z from the relation keys.

    If there are two records in Alma, one that has 020 $a u and another that has 020 $a v and 020 $z u, the both records will be related by the system with the relation: Replaces/Replaced by. The 020 $z is understood as a "cancelled" ISBN and therefore included in the job that calculates the relations.

    In the vast majority of cases we know 020 $z is a false/invalid ISBN: a publisher mistakenly(!) uses the same ISBN in two different resources that have nothing to do with each other. However, according to the international rules for describing resources, the… more

    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