1691 results found

1. Notes Tabs not in Analytics

   We would like to be able to retrieve all the details in the Notes Tabs for Borrowing and Lending requests via Analytics. Currently, only the Request Note is retrievable.

   •  

   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…)
   2 comments  ·  Analytics  ·  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. Waitlist functionality for short-term loans

   It would be helpful to have a waitlist functionality for short-term loans (i.e. for reserve items). This would allow patrons to put their name on a list to be next in line once a short-term loan item has been returned. Alma would send an email/text to the patron when the item is returned telling the patron they have a specific window of time (e.g. 5 minutes, configurable by the institution) to check out the item. During that window of time no other patrons can check it out. After the window of time has expired the next person on the waitlist receives an email/text from Alma saying they can now check out the item.

   For the circulation desk operator it would be helpful to have a waitlist page in Alma that displays which items are currently on the waitlist, how much time is left in each one before the window of time expires. This will help operators to know at a glance where all the waitlisted items are in the waitlist process. This waitlist system is different from a booking request because the waitlist does not require a patron to select the date and time of when they want an item. Instead, it is simply a list of names of patrons who want to be next in line when an item arrives. The waitlist functionality would only be available when an item is checked out; a patron can't put their name on the waitlist if the item is on the shelf.

   Ideally the waitlist function could be done by both staff and patrons, but this should be up to the Alma institution. The institution can decide whether to turn waitlist function on at all. If they turn it on, it will at a minimum be administered by staff. Additionally, they can decide to turn on a patron-facing side that allows patrons to add their names to the waitlist. Ex Libris has also developed an embargo period on loans, which means items can't be checked out to the same patron within a specified window of time. This is very helpful, but it is not the same thing as a waitlist functionality. We need a system that will let patrons get in line for a loan.

   It would be helpful to have a waitlist functionality for short-term loans (i.e. for reserve items). This would allow patrons to put their name on a list to be next in line once a short-term loan item has been returned. Alma would send an email/text to the patron when the item is returned telling the patron they have a specific window of time (e.g. 5 minutes, configurable by the institution) to check out the item. During that window of time no other patrons can check it out. After the window of time has expired the next person on the waitlist… more

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

3. don't mark zero usage SUSHI reports as invalid

   When SUSHI harvests a report that has no usage for the selected dates, it is labeled as invalid. This is misleading. As long as all the correct headings for the report are in place, the report should be considered valid.

   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…)
   2 comments  ·  Acquisitions - 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. More information on Process Type Transit

   In 'Item history', you can see when an item was checked in and out of transit, but not for whom or whereto. If something goes wrong with the transit, you can't get any information about the inactive/completed request.

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

5. Add publication date and subject fields to 'Portfolio Details for Consortia Members' analytics table

   The bibliographic publication date and subject fields would be very useful additions to the 'Portfolio Details for Consortia Members' analytics table. Please include these fields.

   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…)
   2 comments  ·  Analytics  ·  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. XML Expansion for "Ful Resource Request Slip Letter" with Data about Reshelving Status and about Expected Date when Item will be Reshelved

   For fetching requested media at the stacks we are making use of the "Ful Resource Request Slip Letter" in printed form which we customized according to our needs.

   Unfortunately, the data fields that contain

   • the information that the requested item might currently not be at the stacks because it has just been returned and is therefore very likely on its way back to the stacks (Status = awaiting_reshelving)
   • and the information when the requested item is expected to be reshelved ("reshelving_time")

   are not provided in the XML data of the "Full Resource Request Slip Letter".

   This information, when be presented on the "Ful Resource Request Slip Letter" printout, would be very helpful, as in our case it will avoid unnecessary walks through the shelves at the stacks.

   The data fields we need for the printout are available in Alma. They can be viewed in Alma and as well as in PrimoVE and can be accessed via the Alma API. The generation of this data is based on the library's "Time to reshelving (hours)" settings. (see attached file: LibrarySettingsTimeToReshelve.gif)

   You can find the information concerning the fields "awaitingreshelving" and "reshelvingtime":

   • via Alma API: when quering via Bibs API in the fields "awaitingreshelving" and "reshelvingtime". (see attached files (BibsApiRequest.txt + BibsApiResponseJson.txt))
   • in Alma System: when displaying information on item level you can find the information in the column "Status" (see attached file: InformationDisplayedInAlma.gif)
   • in PrimoVE System: the information can be found in "Status:" of the single item (see attached file: InformationDisplayedInPrimoVE.gif)

   We would be very happy about the inclusion of the two data fields into the XML data structure of the "Ful Resource Request Slip Letter".

   Thank you

   For fetching requested media at the stacks we are making use of the "Ful Resource Request Slip Letter" in printed form which we customized according to our needs.

   Unfortunately, the data fields that contain

   • the information that the requested item might currently not be at the stacks because it has just been returned and is therefore very likely on its way back to the stacks (Status = awaiting_reshelving)
   • and the information when the requested item is expected to be reshelved ("reshelving_time")

   are not provided in the XML data of the "Full Resource Request Slip Letter".

   This information, when be presented… more

   •  

   •  

   • 

   • 

   •  

   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  ·  Fulfillment - Requests  ·  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. Add User Note Creation Date and Creator as query-able fields in Anayltics

   Please make it so that we can create analysis in analytics that display the creation date and creators of user notes. Both fields would be very useful filters for us.

   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…)
   2 comments  ·  Analytics  ·  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. Customize display of fields in Alma Article request form

   We would like to display the fields in the Alma article request form in the following order: Journal name, year, volume, issue, pages, article title, article author, and issn - and not in the order these fields are currently hard-coded (e.g. author initials splits volume and issue, and publication date is at the end of the form)

   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…)
   4 comments  ·  Resource Sharing  ·  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. Description Templates -- Create reference table for months and seasons

   Hi,

   I'm wondering if it would be possible to create some sort of reference table for the months and seasons. This would be for use in the description templates. Then we could use MM, MON, and MONTH (for example), to indicate whether the two digit code in the particular Chron field should be displayed numerically, as the standard abbreviation, or spelled out.

   Having such a table would mean that for each type of pattern a single template could take the place of the 12 or 16 we have to create now.

   This would be much more efficient right off the bat and would also provide a cleaner/shorter list of templates to arrow up/down through to get a new rule in the right place, so would save a ton of time there as well. (SEE ALSO: "Add ability to reorder Description Template Setup Rules using drag and drop")

   Hi,

   I'm wondering if it would be possible to create some sort of reference table for the months and seasons. This would be for use in the description templates. Then we could use MM, MON, and MONTH (for example), to indicate whether the two digit code in the particular Chron field should be displayed numerically, as the standard abbreviation, or spelled out.

   Having such a table would mean that for each type of pattern a single template could take the place of the 12 or 16 we have to create now.

   This would be much more efficient right off the… 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…)
   5 comments  ·  Other  ·  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. Store information about request history

    It is currently not possible to see whether an item has previously been requested, only that it's checked out. I want (often) to be able to tell: how many times throughout the history of this item has it been requested and in what way (page from shelf, recall, something else). It's super weird to me that this isn't present in the fulfillment history at least, and probably in analytics.

    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…)
    2 comments  ·  Fulfillment - Requests  ·  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. Allow staff to override auto return when a borrowing request is received after needed by date has passed or request has been cancelled

    When a borrowing library receives a resource sharing item after the request's needed by date has passed, Alma automatically updates the request to returned without displaying any alert. This causes a substantial amount of confusion for staff. We would like Alma to display an alert when a resource sharing item is being automatically returned to the lender because it was received after the request's needed by date. We would also like the opportunity to override this automatic return so users can have the option of using the item.

    Likewise, Alma automatically updates borrowing reqeusts to returned when they've been cancelled by the user after the lending library has already shipped the item. Alma does provide an alert when this happens, which is helpful. We would like the option to override this automatic return too.

    When a borrowing library receives a resource sharing item after the request's needed by date has passed, Alma automatically updates the request to returned without displaying any alert. This causes a substantial amount of confusion for staff. We would like Alma to display an alert when a resource sharing item is being automatically returned to the lender because it was received after the request's needed by date. We would also like the opportunity to override this automatic return so users can have the option of using the item.

    Likewise, Alma automatically updates borrowing reqeusts to returned when they've been cancelled… 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…)
    3 comments  ·  Resource Sharing  ·  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. 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

13. Add function to monitor broken display logic rules

    When the name of a collection/interface/service used in a rule changes the rule quietly breaks. The only way in Alma to find out it's broken is to open the specific rule in edit mode, where it says "not listed" next to the changed collection/interface/service. There is no indication in the list of rules and you are not notified when a rule breaks. We have a long list of rules in use so it's difficult to keep track of the broken rules. It would be useful to be notified when a rule breaks or to have a way of monitoring broken display logic rules better.

    When the name of a collection/interface/service used in a rule changes the rule quietly breaks. The only way in Alma to find out it's broken is to open the specific rule in edit mode, where it says "not listed" next to the changed collection/interface/service. There is no indication in the list of rules and you are not notified when a rule breaks. We have a long list of rules in use so it's difficult to keep track of the broken rules. It would be useful to be notified when a rule breaks or to have a way of monitoring broken… 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  ·  Other  ·  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. Location color schemes

    I would like to make it an option to change the color scheme of the ALMA top ribbon/possibly sidebar to differentiate locations especially between Main Circulation Desk and Acquisitions, of which I have to switch regularly. This would save me time spent on correcting errors due to being in the wrong location for a particular procedure.

    52 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  ·  Other  ·  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. Establishment of stronger passwords for the creation of internal ALMA/Primo users

    As an universities consortium from Galicia, CISUG, we are representing three member universities. Our univesrities have a security problem in the management the keys for internal users in Alma.

    Alma's internal authentication system allows the user can create complex passwords, but this should be a requirement, not the user's responsibility as to whether they are secure or not.

    Our request is that:

    1.  ALMA enforce passwords to be at least 8 characters long, and allow the system administrator to increase that minimum. 
       

    2.  ALMA allows to force mixed case, numbers, and special characters to créate paswords. 
       

    3.  Alma checks that the password is not composed of user data (e.g. name, surname, email, etc.) that can be easily guessed or obtained. 
       

    4.  Alma checks that the password is not the same as any of the last passwords used, nor is it formed by a concatenation of them.. 
       

    5.  Alma validates the new password against a “blacklist” of passwords that are unacceptable due to being widely used, deductible or compromised (e.g. “aaaaaaaa”, “1234abcd”, etc.). 
       

    In addition, Alma shall audit the password validation process and:

    1.  Limit the number of unsuccessful access attempts, applying an incremental delay after several failed attempts (e.g. 1 minute delay after 3 failed attempts and +10 minutes for the following ones) to make it more difficult to use bot attacks.  
       

    2.  It must be able to block the system in case of reaching a set number (e.g. blocking the user after 10 failed attempts).  
       

    And as additional methods to ensure security:

    1.  Alma shall allow to automate a forced process of periodic password change (for example yearly, semi-annually, etc).  
       

    2.  Alma shall have a mechanism that allows the administrator to request a change of passwords if there is evidence that they have been compromised.  
       

    We understand that it is more complex, we believe it would be advisable that Alma allow the user to have a security method of authentication based on two-factor authentication (2FA), as offered today by most information systems (Google, Microsoft, etc.).

    With the implementation of these requirements, users would have their personal data more secure (both in terms of access to the system itself, as well as in anticipation of it serving as an entry vector for other tools), and the institutions would thus comply with the precepts of the ENS Spanish "National Security Scheme" in terms of minimum cybersecurity requirements.

    As an universities consortium from Galicia, CISUG, we are representing three member universities. Our univesrities have a security problem in the management the keys for internal users in Alma.

    Alma's internal authentication system allows the user can create complex passwords, but this should be a requirement, not the user's responsibility as to whether they are secure or not.

    Our request is that:

    1.  ALMA enforce passwords to be at least 8 characters long, and allow the system administrator to increase that minimum. 
       

    2.  ALMA allows to force mixed case, numbers, and special characters to créate paswords. 
       

    3.  Alma checks that the password is

       … more
    52 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  ·  Other  ·  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. Move requests and temporary locations - option to flag for processing, etc.

    At present the item move requests sometimes work too seamlessly. Especially for items that are onloan when the request are made (or the item is restored to its permanent location). This is an issue when the items need manual intervention, e.g. relabelling. Items go through the process without being flagged unless another process is used, e.g. a work order or fulfillment note.

    It should be possible to flag items for manual intervention when they arrive at their new or original location. A message on the lines of 'Move Request: check labels etc.,' in the manner of a fulfillment note.

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

17. FUND / Ledger facet missing from PO Line user interface

    All PO Lines has multiple facets but FUND or Ledger is not one of them.

    Funds, both allocated & summary, are fundamental to purchasing and we'd like to be able to filter the PO Line display by these variables.

    Please add a facet in the All PO Lines user interface for FUND.

    52 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  ·  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

18. Option to set return time to 15 minutes before closing

    We issue equipment such as laptops to students. These must be returned before the library closes.
    
    In the current TOUs it is only possible to set the due time to closing time. However, we really need to check all equipment is back, and therefore would like to set the due time to 15 mins (or 30mins) before closing.

    We would also do this for short loans, as these require being returned before the library shuts. Otherwise the student will receive fines.

    Changing the closing time of the library would be too confusing for everyone

    51 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  ·  Fulfillment - Loans  ·  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. Common link between a POL and a License (for updating collections)

    A POL has a licence connected to it. It would be great if when adding that POL to an Alma Collection, that the connecting licence would be automatically added to the collection as well. And working in reverse, when adding a licence to an Alma collection, it would be nice if the POL connected to the licence was automatically added to the collection as well (thus saving time adding two things to a collection, when they are already related).

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

20. Make Push Selected to MDE button available for Itemized Sets

    'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep the 'Remove Selected' button at the same time?
    This issue was raised originally with ExLibris via incident #00954718 and we were advised this is not current functionality.
    We appreciate your support for this idea!

    'Push Selected to MDE' (pushing records in bulk to Metadata Editor) is not available for Itemized sets, but it is available for Logical sets in the current Alma implementation. While the option to Push Selected to MDE is plainly visible in the Logical Set Results view (please see the attached screenshots), it is replaced by the 'Remove Selected' button in the Itemized Sets Members’ view. We would be very interested in having the Push Selected to MDE available for both Logical and Itemized sets. Is it possible to add the 'Push Selected to MDE' to he Itemized view and keep… more

    • 

    51 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