| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | ReqID | Title | Description | ComplexityPoints assigned in earlier years | TotalVotes | CSU Ranking | ||||||||||||||||||||
2 | 8373 | Ability to schedule manual jobs | Ability to schedule manual jobs -- Ideas Exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/32970643-ability-to-schedule-manual-jobs-on-a-regular-basis This would be very useful e.g. for scheduling a Suppress Bib Records job or a Normalization job on Sets of Bib records, or a Change Portfolio Information job (including deactivation for expiring licenses) on a Set of Portfolios. At present any such jobs have to be run manually and are therefore restricted to staff availability; it would be great to be able to schedule these in advance, whether they need to be run regularly (repeated) or just as a one-off job that can run outside normal working hours or when a staff member is on leave and cannot run it 'in-person'. | 1405 | 3 | |||||||||||||||||||||
3 | 8415 | Allow institutions to export and import all configurations from Alma | Ex Libris has the policy of forcing a refresh of the sandbox for all customers on the premium sandbox twice a year. This presents a significant challenge for institutions that use the sandbox actively, because it means that before every refresh, we have to go through the largely manual process of exporting all configurations out of the sandbox so we can keep record of them. Then if we want to recreate the old configurations, we have to do this manually. Ex Libris offers no way to export or import these configurations in bulk. This policy change reduces the value of the premium sandbox for customers who were already using it with the old policy, when we could request refreshes when we wanted. We would like Ex Libris to make it possible to export all configurations in bulk, and then reimport these configurations after the refresh. Ideally these would be exportable in bulk, and then you could pick and choose which configurations to reimport. | 1264 | ||||||||||||||||||||||
4 | 8400 | Add Physical Item Details for Course Reserves subject area in Analytics | It should be possible in Analytics to make a list of the physical items that are on reserve. Libraries need to be able to create reports that contain the name of the course and the instructor (and the name of the reading list), along with the item barcodes for the physical items on reserve for those courses. However, the Course Reserves analytics area does not currently contain the “Physical Item Details” subsection, and the “Citation Metadata Details” section’s barcode field is typically blank. Libraries would also like to gather usage statistics for on-reserve items. The Citation Number of Loans field already available in the Course Reserves analytics area counts all the uses for a given bibliographic record, even if one or more of the items is not on reserves. Teaching faculty who use reserves for their courses want accurate statistics of reserve item usage. See also Idea Exchange item: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/20364817-need-a-physical-items-folder-in-the-course-reserve | 1244 | ||||||||||||||||||||||
5 | 8197 | Ensure email is delivered with DKIM protocols | DKIM (Domain Keys Identified Mail) is an email authentication technique that allows the receiver to check that an email was indeed sent and authorized by the owner of that domain. Currently ExLibris does not issue DKIM keys to allow the implementation of this protocol. Increasingly, emails sent by Alma from institutions using their own domains are at risk of getting caught in spam filters and not being delivered. | 1223 | ||||||||||||||||||||||
6 | 7685 | Ability to edit barcode after receiving borrowing request | Sometimes after receiving a borrowing request, we have a need to change the barcode. This could be because the wrong barcode was scanned in, the barcode is not responsive or another reason. However, there is currently no way to change the barcode in the borrowing request record. Staff can update the item barcode (and we do) however this doesn't affect the original barcode that was scanned in against the borrowing request. We therefore have to add a lot of physical and electronic notes to the front desk staff and to the staff who will be returning the item to the partner library explaining which barcode to issue the book on etc. | 1220 | ||||||||||||||||||||||
7 | 7877 | Enable viewing of Requests history in Alma | Currently, within a patron record in Alma, it's possible to view current and previous activity for Loans, Returns, and Fines and Fees. However, within Requests, it's only possible to view current requests. It would be incredibly useful for Alma users to be able to view historical requests as well, this to assist with any request queries. The ability to view request history in Alma Analytics has been very welcome and useful for reporting. However, for troubleshooting purposes, it would be much better to be able to use live Alma straight away, rather than having to wait until Alma data refreshes into Analytics. | 25 | 1199 | 4 | ||||||||||||||||||||
8 | 8212 | PO Line: missing identifiers ISBN/ISSN/ISMN etc. | Please list all identifiers in the PO Line. See the following examples: Data in the bibliographic record --> data in the PO Line XML file Example 1: 020 __ |a 9783702404727 024 2_ |a M008027376 --> PO Line - XML: only content of 020 <identifier>9783702404727</identifier> <identifier_type>ISBN</identifier_type> Example 2: 024 3_ |a 730099129329 028 52 |a 8.551293 --> PO Line - XML: empty identifier <identifier></identifier> <identifier_type></identifier_type> Example 3: 020 __ |a 0415462444 (pbk.) |c £24.99 020 __ |a 9780415462440 (pbk.) |c £24.99 020 __ |a 0415462436 (hbk.) |c £70.00 020 __ |a 9780415462433 (hbk.) |c £70.00 --> PO Line - XML: only content of first 020 <identifier>0415462444 (pbk.)</identifier> <identifier_type>ISBN</identifier_type> Status quo in Alma: (1) The bibliographic information in a PO Line includes only one ISBN (Marc21 field 020) or ISSN (Marc21 field 022). If a record includes more than one ISBN (or ISSN), this information is missing in the order letter. (2) In case of other materials than books and journals - without ISBN or ISSN - identifiers like ISMN and EAN (Marc21 024) or other publisher numbers (Marc21 field 028) are skipped --> the <identifier> field in the XML file is empty. To give our vendors the best bibliographic information when ordering items via Alma, it is important to have all these identifiers within the XML file: - please provide us all 020 / 022 entries, not only the first ISBN or ISSN - please include also 024 and 028 to the XML file (it is possible, that a record has both: 020 and 024 or 028, etc.) Thank you in advance! P.S.: See also idea|exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46228312-po-line-missing-identifiers-isbn-issn-ismn-etc | 1175 | ||||||||||||||||||||||
9 | 8345 | Allow auto renewal to restart after blocks removed | Currently we receive reports of users that are to be blocked due to late payment of fees. Once the blocks are removed or made inactive auto renewal rules do not allow the automatic renewal process to restart | 1140 | ||||||||||||||||||||||
10 | 7283 | Run "Bulk change due date" process on an itemized set of users | Add to the "Bulk change due date" process the option to run on a predefined set of users. | 1128 | ||||||||||||||||||||||
11 | 8125 | Display user's loan due date in borrowing request screen | When a user who has an interlibrary loan requests a renewal of the item, staff need to check both the due date that the partner library has set, and the current due date of the loan on the user's record. This is because we can sometimes extend the due date of the loan without requesting a renewal from the partner library, since the loan due date will still be within the due date that the partner has given us. To do this check, staff need to view the borrowing request (to see the partner library's due date) as well as the user's record to check the current due back date. To make this process quicker and simpler, we would like user's loan due date for the item attached to the borrowing request, to display in the borrowing request screen. | 1115 | ||||||||||||||||||||||
12 | 8048 | Add Option to Toggle User Record Type | Add a simple toggle option for a user record to easily switch Record Types between Staff and Public. While there are more complicated ways to deal with it, if a user record is accidentally created and assigned the wrong Record Type there is no easy mechanism to change it, like we can when toggling an account between Internal and External. | 1110 | ||||||||||||||||||||||
13 | 8123 | Ability to re-open a completed borrowing request | Sometimes borrowing requests go to Complete status when triggered by a particular workflow. However, sometimes further action needs to be taken. For example, Attachments need to be added, or a Request Note updated. The inability to edit the request or move the request manually to another status can be frustrating and leads to unnecessary workarounds. Could Completed requests have a 'Re-open' functionality in a similar way that Cancelled requests can be reactivated. | 1105 | ||||||||||||||||||||||
14 | 8401 | User Purge should not delete users with active requests | The Alma User Purge job currently deletes users with active requests. When deleting linked user records in a fulfillment network, sometimes the only activity that a linked user record currently has is an active request (a request that is in the pick-from-shelf queue, in transit for hold, or on the active hold shelf); the requested item may be committed for the patron’s use, but not yet checked out to their account. | 1100 | ||||||||||||||||||||||
15 | 7932 | Enable users to personalise Alma interface for accessibility | Alma has limited inbuilt, customisable accessibility options. Previously, members of Library staff were using third-party browser extensions to improve the accessibility of Alma. However, for security reasons, these are no longer available to us. Consequently, we have colleagues for whom Alma is not accessible. Ideally, accessibility features would be made fully and easily configurable within Alma, enabling individual users to adjust their own view of the system to their unique needs. Elements including background and text colour, font, and text size would be fully adjustable in all areas of Alma. Also, we would like to see the Alma user community consulted about this issue, as we can only speak for the needs of our own staff. In addition, the ability to select a 'dark mode', with a darker coloured background and lighter coloured text would be helpful for users to reduce eye strain. This would also have environmental benefits due to reducing monitor power consumption; if fewer pixels are active, they draw less power. | 1096 | ||||||||||||||||||||||
16 | 6669 | Editing items via Receiving, Save & Receive items | From the Receive Items List, add options to edit description, enum, and chron. Currently only the barcode is editable here. This will greatly improve productivity. Furthermore, when staff need to edit additional item fields during receiving, they need to be able to go to the Physical Item Editor and then Save & Receive. Currently they can only Save from the Physical Item Editor, meaning the Receipt of an Item and the Editing of an Item are two disparate workflows, even though staff need to do them at the same time. Without this feature, working with continuous items is time-consuming, awkward, and requires many extra keystrokes/mousing. | 20 | 1033 | |||||||||||||||||||||
17 | 8338 | Make an easy way for items to be removed from 'in transit' status | We continue to have items change to 'in transit' status and we don't know why and Ex Libris cases are at a dead end. We think it is a simple error of our students checking an item in or out of the wrong library but this is human error. We have changes our transit tables several times but the error continues to occur. Can we please get a feature to change an item out of 'in transit' status? | 946 | 1 | |||||||||||||||||||||
18 | 8396 | Special characters option in Metadata Editor | We would like a special character option within the Metadata Editor, so as to be able to enter diacritics/special characters from there, like with Voyager. The other methods (copy and paste, pulling up operating system character maps, and downloading browser add-ons) are fussy. | 922 | ||||||||||||||||||||||
19 | 7674 | Allow User to Customize how many Issues are Predicted | Currently, Alma’s 853 Predictive Patterns, and the ‘Open Predicted Items’ function are only capable of predicting an entire year’s worth of serial issues at one time. NERS 7721, submitted by Hong Kong Polytechnic University, was merged into this request. | 864 | ||||||||||||||||||||||
20 | 6666 | Import Profiles: more mapping options (Material Type, Acq Method, E-Collection) | We need additional mapping options in Import Profiles. We need the ability to map to Electronic Collection, Material Type, and Acquisition method, based on field/subfield values in the input file. For example, we have several EOD profiles for Casalini, when we could have 1 if these values could be mapped. We have several because we load different material types (Books, DVDs, etc.) and have multiple Acq Methods, such as Approval, Purchase at Vendor System, etc. Similarly, for Import Profiles that load Portfolios, you cannot map to Collection. You have to have a separate profile for each Electronic Collection for which you want to load portfolios. These greatly increases the number of profiles we need to maintain. If we could map to Electronic Collection from a field/subfield value in the input file, we would need to maintain significantly fewer profiles. | 856 | ||||||||||||||||||||||
21 | 6907 | Enable to upload controlled vocabulary lists in Excel format | Currently the only way to create a new controlled vocabulary list (to use in fields with per-defined values) in Alma is by adding the values manually, one by one. Usually the controlled vocabulary lists are added in implementation by the migration teams, but after Go Live, there is no way to do that neither by the institution nor by the support. | 846 | ||||||||||||||||||||||
22 | 8335 | The link resolver should be able to calculate the availability of volume or issue in a book serial | What is the problem: At present, the LinkResolver cannot calculate the availability of print holdings to determine whether a particular issue is available in those holdings. The LinkResolver matches your local inventory based on the ISBN, so the resource sharing options are being hidden due to the matched inventory, even though this particular volume is not available in your physical holdings. For instance, if an institution has the ISBNs for non-held volumes cataloged in the 020 field, the link resolver will match CDI records or OpenURLs containing the ISBN for these volumes even if the library does not have holdings. These records are likely to be autoloaded from OCLC for the entire serial. What is expected: The link resolver can calculate the availability of print holdings to determine whether a particular issue is available in those holdings. For example, if the request is for an article in volume 6, the link resolver will check the availability of volume 6 in the decision-making of a match. | 844 | ||||||||||||||||||||||
23 | 8169 | Add more local params for bibliographic records in Alma Analytics | Currently there is the option to add 10 Local Params in Bibliographic Details, by request to Ex Libris. Ex Libris has stated previously that they will not add more until they see that many sites use up the existing 10. This approach ignores that it is good practice to keep such configuration options in reserve for future use when really needed, given the out-of-the-box fields may not suit requirements. The option to change field mapping of Local Params over time is not acceptable as the varying field data remains in Analytics forever with Deleted records, causing a mess of different field mappings. This submission is to add another 10 Local Params to Bibliographic Details in Alma Analytics, across all subject area with this Shared Dimension, for a total of 20. | 817 | ||||||||||||||||||||||
24 | 8377 | Optimisation of reminders and overdue letters (anti-phishing) | The reminders and reminder letters sent to patrons currently often end up in upstream spam filters of the mail providers. If this is not the case, we regularly receive feedback that they considered some of the automated notifications to be spam or phishing mails. We would like to be able to optimise the automated notifications so that they are less automatically classified as spam according to today's standards. Ideally, Alma would already take common standards into account. See also Idea Exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46247398-optimisation-of-reminders-and-overdue-letters-ant | 808 | ||||||||||||||||||||||
25 | 8374 | Add warning for active title-level-requests when relinking or deleting holding records or items | When relinking holdings and items to new bib records or deleting holdings or items, requests can get lost. This is the case if they are on the titel level instead of on the item level. (Cf. https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Physical_Resource_Management/015_Managing_Physical_Resources#Relinking_Items_to_Another_Bibliographic_Record) See also Idea Exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/43962321-add-warning-for-active-title-level-requests-when-r | 756 | ||||||||||||||||||||||
26 | 8371 | Bursar integration: Additional fee statuses in Alma & Allow fee status change with job Import from Bursar | Currently only the fee statuses “open”, “transferred” and “closed” exist in Alma. The status "transferred" means that the fee was exported to the external Bursar system. When the fee is imported back to Alma, it is automatically Closed. For staff it is not possible to tell if the closed fee was paid, waived, unpaid etc. without consulting the 3rd party Bursar system. To give librarians and end users more transparency about the (invoice) status of a fee, we would need more differentiated fee statuses. Also, we need to be able to set this status when importing the fees back to Alma using the job Import from Bursar. The optimal development would be: 1. Have the possibility to configure ourselves in Alma which fee statuses we want to use and to have the possibility to add additional fee statuses. 2. The Import from Bursar job must be able to set this status based on a field in the import XML file. If the #1 is not possible, it would be good to have the following additional fee statuses implemented: invoiced unpaid partial payment paid/closed storno write-off transferred to the debt collection e-mail not deliverable | 730 | ||||||||||||||||||||||
27 | 8378 | Add library code to Resource Sharing Shipping Slip Letter | With Rapido, our smaller libraries are receiving more courier requests from all over the country, and they don't have all of these library codes memorized. The library codes are not available on the Resource Sharing Shipping Slip Letter, but are used by our courier service provider as an identifier for shipping to correctly route the documents. Currently, the code must be looked up by hand if you do not know it. Therefore, we would like to print the library codes on the Resource Sharing Shipping Slip Letter. However, this field is not included in the letter data (XML/XSL). We ask that this field be made available in the letter templates. It would greatly facilitate the work of our colleagues if this does not have to be looked up by hand. See also Idea Exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46260616-add-library-code-to-resource-sharing-shipping-slip | 718 | ||||||||||||||||||||||
28 | 7306 | Send Courtesy Notices when Patron Loans are Auto-Renewed | When loans are successfully auto-renewed in the system, the patron does not receive an email notifying them that the loan has been renewed. Therefore, it is possible after a while that the patron forgets they have the item. We would like the option to have a notice to go to the patron when an item is auto-renewed, and have a letter that is customizable for this purpose so that we could expand our use of auto-renewals. | 30 | 711 | |||||||||||||||||||||
29 | 8343 | Digital Representations: shareDigitalResources | When the customer parameter shareDigitalResources is enabled, which is useful to allow freely available digital representations (for digital objects stored in Alma or in a remote digital repository) to be available to all institutions, records loaded from external data sources via discovery import profiles are also impacted by this. Ex Libris explained that this is by design as these records from external sources are considered as digital objects. This leads to the following problem in Primo: As soon an IZ enables this parameter, its records from external data sources are included in the search results of local search scopes made in other IZs local views. Generally all external data sources which are shared with the network, should be part of the results for searches within the Discovery-Network-scope and not be part of the My-Institution-scope of an IZ which has no corresponding import profiles configured in their IZ Alma. (see details in SF 00992268). An enhancement should allow the flexibility to define which resources are impacted by the customer parameter shareDigitalResources and which are not, such as the resources from external data sources. | 710 | ||||||||||||||||||||||
30 | 8352 | Label distribution per row (VE/BO) | In consortial environment there is the option to distibute labels from the Network to the Institutions. At the moment the distribution is only possible per table. In case a table is updated by functionality, the distribution deletes the displayed labels. We would like to have the option to distribute labels per row: this would give the possibility to the Institutions to receive the updates from the Network avoiding overwriting issues and increase the possibility to distribute a label in case a table has been customized locally. Example 1 Adapting labels tables which are partially customized by the IZs In our consortium we have the following customized tables: Error message labels, Facet Labels, Header/Footer Tile labels, Database search labels, Basic search Pre-Filters labels. The distribution from the NZ cannot take place when labels belonging to these tables need to be readapted: the entire tables are marked as "customized" and the changes are not retrieved from the NZ unless the overriding mode is used (but not possible to use this solution because it will override the locally customized labels). Use case: Adapting labels of the table "facets.facet.facet_library" Description: The "facets.facet.facet_library" belonging to the Facet Labels table was readapted to display the IZ name for each IZ in the facets. The label "facets.facet.facet_creator" needed to be changed for the German and French UI in all IZs manually: the Facet Labels table is marked as "customized" and couldn't retrieve this label change. It is not possible to override the table from the NZ as this would have removed also the customized label "facets.facet.facet_library". Example 2: Adapting labels tables where there is an overriding issue In our consortium we have the following customized tables, updated by functionality: Advanced Search index fields labels, User Login Labels, View Labels. These tables cannot be distributed because the distribution would cause an overriding issue (also described in BC) Use case: Adapting labels of the table "search-advanced.scope.option.nui.advanced.index.creator" Description: The "search-advanced.scope.option.nui.advanced.index.creator" label was readapted by the discovery admin of the NZ for the French and German interfaces in the NZ. The distribution caused an overriding issue and the local fields configured in the Advanced Search of the local views of the IZs were overwritten with the local fields codes. | 710 | ||||||||||||||||||||||
31 | 8353 | Distribute "configure views" settings via NZ (VE/BO) | It would be very useful to have the possibility to distribute the settings available via Configure views, especially for the General, Brief Record and Full Record services tabs. | 710 | ||||||||||||||||||||||
32 | 8372 | Activation of e-resources in the Network Zone based on IMGs | E-Resources in the NZ can be activated only for the whole IZ or every member of the network. IMG-specific or library-specific activations cannot be made from the NZ and can only be made on IZ-level. For us as a consortia with centrally purchased licenses it is important to make IMG-specific activations via the NZ so that we can activate for specific IMG and also configure different proxies per IMG if necessary. | 710 | ||||||||||||||||||||||
33 | 8376 | Display all related records instead of 500 | When looking for related records (Brief results list > Other > Related records), only 500 titles are displayed. Especially when working with series/journals with many issues, monographs, or analytical records, having all related records would simplify the daily work. See also Idea Exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44564328-display-all-related-records-instead-of-500 | 710 | ||||||||||||||||||||||
34 | 8178 | Display loan statistics for physical items at an earlier point in a search | In an All Titles/Physical Titles search, display the figures for numbers of loans for each item on the “List of items” page. From this page it currently takes three more clicks in each item record to see this information in the history, and it means coming out of each item record and into the next one to compare copies. In a Physical Items search, display this information in the search result. | 683 | ||||||||||||||||||||||
35 | 6670 | Preferred term correction: flip headings that change tag number | Alma authority control does not handle cases where the bib heading is linked to an authority via a cross-reference, but the preferred and non-preferred terms are in different fields, e.g. preferred term is in authority field 130 and cross-reference in authority is in 410. Alma should be able to handle this scenario. Currently when the bib heading matches the authority cross-reference, Alma won't correct these and instead puts them on this report: Preferred Term Correction - Bib Heading found no authorized term. This is a common scenario and the lack of this feature is a significant gap in the Alma authority control process. Handling these manually would require an unsustainable amount of effort by staff, because they can only be corrected through complicated norm rules, and it is not feasible to write a norm rule for every relevant heading and run jobs to update records. // Example bib heading that Alma won't correct: 110/2_ $$a Allied and Associated Powers (1914-1920). $$t Treaties, etc. $$g Germany, $$d 1919 June 28. The authority record that this heading links to (via its cross-reference) 130/0 $$a Treaty of Versailles $$d (1919 June 28) 410/2$$a Allied and Associated Powers (1914-1920). $$t Treaties, etc. $$g Germany, $$d 1919 June 28. The bib heading in 110 links to the authority via the cross-reference in the 410, but because the preferred term in the authority is in 130 (and not 110), Alma will not flip the heading. // This is also in Ideas Exchange with about 180 votes: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/36030319-preferred-term-correction-should-flip-headings-tha | 553 | ||||||||||||||||||||||
36 | 7608 | Enable User Administrator role with "login/view as user" function | To assist with account troubleshooting and role management, we would like an enhancement that would allow staff with the 'User Administrator' role to be able to login as another staff user. When troubleshooting user account issues, admins would be able to log into Alma as the user experiencing the problem. Many systems offer this type of feature to allow administrators the ability to troubleshoot when confirming workflows and privileges when new roles, scopes, and parameters are added. | 546 | ||||||||||||||||||||||
37 | 7065 | Received Items List - enhance functionality | Please add the ability to view Material type as a column, add a button to Open Predicted Items, and add a button to Withdraw items to the Received Items List in Acquisitions > Receive. Include a popup for the receiving note, similar to what exists for fulfillment notes (for an example, see Salesforce Case #00058981). Use case for Open Predicted Items (added from 6668): A user is responsible for receiving issues of print serials. While doing so via the Receiving List, they need to create additional predicted items for a title. They navigate to the List of Items for the correct holding associated with that title using a Repository Search, then use the Open Predicted Items function. They then need to navigate back to the Receiving List to continue their work until needing to create additional predicted items for another title. | 531 | ||||||||||||||||||||||
38 | 8384 | Maximum renewal date | It would be very helpful if staff and patrons could see the maximum time a borrowed item can still be borrowed, including all renewals. (Output both in Alma UI and via Alma API (to display e.g. in the catalog/patron account)). | 522 | ||||||||||||||||||||||
39 | 8392 | location type "unavailable" should lead to availability status "unavailable" in Alma and Primo | We need the possibility to show items as unavailable in Primo without creating requests (work orders) for them. Our use cases are - items which have been restituted (via a provenance research project) and are no longer in the library - items which are blocked for usage for years - items which are not usable for certain reasons All of these have to be shown in the discovery interface, although users won't get them for a long time or at all. Now, all of these items have a "green" availability status in Primo and we struggle to put information about the non-availability on several places in the holdings display so that users know that they won't get it. When using work orders to achieve "red" availability status, users are confused about the fact that the item is "in process" and there is a request for it. See also ideas/exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46262368-make-location-type-unavailable-functional-items | 520 | ||||||||||||||||||||||
40 | 8117 | Ability to arrange order of portfolios from within a title | Give us the ability to arrange the order of portfolios from within a title. For example, adding 6 portfolios to the same title with public notes containing session numbers in the order of session 6,5,4,3,2,1 would end up in the order of session 1,2,4,3,6,5. Currently, we do not have the ability to arrange the order of portfolios as they appear in Primo VE. | 488 | ||||||||||||||||||||||
41 | 8136 | Alma Collections : add ability to include NZ titles in IZ Alma Collections | Currently when a library creates a collection in Alma they can add titles from their Institution Zone (IZ) to the collection but they are unable to include any NZ-managed inventory in that local collection. | 471 | 6 | |||||||||||||||||||||
42 | 8140 | Add facet "held by" in search result screen at Network Zone level | Add a facet "held by" in search result screen at Network Zone level. | 453 | ||||||||||||||||||||||
43 | 8325 | Purchase requests - A new workflow in Alma | The target is to split the action "Approve and Order" in two distinct actions: one for "Approve" and one for "Order". This requirement arises because in our library the operator that approves is different from the operator that orders: usually they are two different persons. Here is the new workflow we propose: 1. the user enters the purchase request through the Primo online form; 2. at the acquisition office, the purchase requests manager assigns the request to an operator with a specific “approver role”; 3. the approver operator evaluates the opportunity of the purchase: * if not, he/she rejects the request; * otherwise, he/she clicks on a new button called "Approve": the order is not created, the request status is set to Approved, and the purchase request is moved to the "Unassigned" tab; 4. the purchase requests manager assigns the purchase request with the Approved status to an operator with the specific “purchaser role”; 5. the purchaser operator completes the request and orders the material by clicking on a new button called "Order"; the purchase request status is set to the new value "Ordered". For this new workflow, it is necessary to add an new role to the existing ones: * the "purchase request approver operator": this role permits only to approve or reject the purchase request, without the ability to select vendor and fund, and to order. The two current roles, the "purchase request operator" and the "purchase requests manager" remain as they are. Moreover, for this new workflow it is necessary to add a new status to the existing ones: * "Ordered", which will be subsequent to the Approved status. The two current statuses, "In review" and "Approved", remain. | 429 | ||||||||||||||||||||||
44 | 7690 | Add an optional note to patron when rejecting a purchase request | We would like to have a new free field text in the popup when rejecting a purchase request. This field would include a note to the requester, explaining the reject reason. This could be used by the library in several ways: providing a link to the Primo record for items already available, giving a link to an Open Access version that would not be in Primo, providing the requester with any personalized or detailed information about why the item cannot be purchased (out of print an very hard to find, etc.). | 392 | ||||||||||||||||||||||
45 | 8155 | Improved Public Access Model functionality | The porfolio Public Access Model field shows the number of simultaneous users who can access a book and displays to end users in Primo. However, it is only configurable at the portfolio level, it is not included in Alma Analytics, it cannot be modified using the Portfolio Loader or Change Electronic Portfolio Information Job, and it is not included in the portfolio Extended Export. The following improvements would allow libraries to populate this field and display it to end users for all ebooks in Alma: 1) configurability of Public Access Model at the collection level (and inheritance by portfolios); 2) reporting of Public Access Model at the portfolio and electronic collection level in Analytics; 3) modifiability of Public Access Model using the Portfolio Loader, Change Portfolio Information job, and Change Electronic Collection Information job; and 4) inclusion of portfolio Public Access Model in Extended Export of portfolios. | 377 | ||||||||||||||||||||||
46 | 8168 | Add more options for staff to manage Lost items | Alma currently has very few options in allowing staff management of Lost items, primarily only to make them Found one by one. This is often not an acceptable option, such as when the patron still has the item and wishes to keep it, or when there are many dozens or even hundreds of Lost items needing to be made Found. This submission is to give staff the ability to better respond to patron queries for Lost resources by allowing use of Renew and Change Due Date in a user account to be successful rather than returning an error, for both individual and the existing bulk selection options in a user account, and the ability to select multiple items to change in bulk from Lost to Found, when this is a suitable option for the scenario. To support this functionality, there should also be the ability to configure options around refund of associated charges. These options are needed to empower Library staff with the discretionary ability to to step in to Alma automation to make a great patron experience, when the human-to-human staff and patron interaction deems it necessary. See also Idea Exchange entry with 127 votes as at 17th January 2023: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/19953931-allow-staff-level-renewing-of-items-marked-as-los | 372 | ||||||||||||||||||||||
47 | 8285 | Add option to remove deleted License records in Alma | There is a 'Delete' licence option within the licence area, but it still leave the licence on the system. We want the ability to remove them from the system as they are no longer required and there is a need to retain them. | 372 | ||||||||||||||||||||||
48 | 6663 | Scan in Items... Status / Done selections need to be sticky | The Scan in Items... Status field value is not sticky. This is a productivity issue and also leads to errors. Generally a given staff member frequently chooses a single value repeatedly, but the system always defaults to the first value in the list (alphabetically) and they have to change it every time. The same is true for the Done option. The last used option should stick. Use Case: I am a staff member in Acquisitions technical services. I am an original cataloger and my workflow involves cataloging a piece, and then updating the status of the work order to "Shelf Prep." From the Metadata Editor, I complete my cataloging, save and release the bib record, then go to Scan In Items, change the status from the default value (first alphabetically) of "Cataloging" to "Shelf Prep," then Scan in the barcode. Now I work on my next bib record, finish cataloging in the MDE, save and release record, go to the Scan in Items screen, and now I have to re-select the status of "Shelf Prep" and scan in the item. I have to re-select this status all day long as I go about my cataloging work. | 371 | ||||||||||||||||||||||
49 | 8339 | Login Override | We would like to have login override functionality on Alma accounts. For example, if a student worker with limited permissions attempts to check out a non-circulating item to a patron and gets a block message preventing the checkout, a supervisor would enter their login credentials on that block screen to allow the checkout instead of having the student log all the way out and the supervisor log in on their account. This would save time in regards to supervisors checking items out and performing other functions at the circulation desk. | 365 | ||||||||||||||||||||||
50 | 6261 | Enable configuring VAT at the purchase order line level | Libraries should be able to enable configuring VAT on the purchase order line level so that it can be taken into account for encumbrance calculation. | 354 | ||||||||||||||||||||||
51 | 8369 | MARC Field Numbers in Analytics | For Bibliographic Details in Analytics, list the corresponding MARC number for a field in addition to the description of a field (for example, "author" could instead say "author (100)" or "title" could instead say "title (245)" to indicate the MARC number for that field.). | 349 | 2 | |||||||||||||||||||||
52 | 8071 | Improve functionality with one-time orders when invoice line total price is lower than the PO Line total price | For one-time orders, if the invoice line total price loaded via EDI is lower than the PO Line total price, Alma does not update the order and invoice correctly. Alma does not release the remaining encumbrance, nor does it update the Invoice Status to Fully Invoiced and the POL status to Closed. You can run three Alma jobs to release the encumbrance and fix the statuses, but we believe 1) Alma should do this automatically instead of requiring customers to run jobs or 2) Ex Libris should offer the ability to release the encumbrance just like it does now with continuous orders. | 346 | ||||||||||||||||||||||
53 | 8275 | Send borrowers an email when they place a request | It would be good if, when someone places a request on Primo, they could be sent an email receipt to confirm what they have requested. The email could also be edited to include important information eg library opening times for collecting requests. | 333 | 5 | |||||||||||||||||||||
54 | 8118 | Add AIATSIS thesauri to the CZ subject authority files | AIATSIS thesauri made available in the Community Zone authority files for 6XX subject fields. | 320 | ||||||||||||||||||||||
55 | 7952 | Make all Analytics default column headers for identifiers work for set creation in Alma | The ability to create an itemized set from Analytics requires that the Analytics report column header for the identifier used in set creation match Alma's expected column headers. We have identified 4 cases where the default column header in Analytics does not match Alma's expected value for the relevant identifier, making set creation from Analytics impossible without manually editing the Analytics column header to match a value accepted by Alma. The 4 cases are: --For creating All Titles, Physical Titles, and Electronic Titles sets, Alma expects "OCLC number," but Analytics uses the column header "OCLC Control Number (035$a) --For creating All Titles, Physical Titles, and Electronic Titles sets, Alma expects "035 field," but Analytics uses the column header "Network Number" --For creating Physical Items sets, Alma expects "Item Id," but Analytics uses the column header "Physical item Id" --For creating Electronic Collections sets, Alma expects "PID," but Analytics uses the column header "Electronic Collection ID" Alma should accept Analytics default column headers for identifier columns that can be used for set creation. Also, Analytics default column headers should not be changed without also updating acceptable column headers for Alma set creation. | 316 | ||||||||||||||||||||||
56 | 8180 | Add barcode to Pick From Shelf options | The display of fields on the Pick From Shelf list is customizable, but the barcode of the material to be picked up is not available as an option. It would be helpful if it could be included, as staff may want to use it to verify the correct item. It is already available in the Alma Mobile version, and in the Print Slip Report (several barcodes are reported in case of multiple items), and would be a natural option in the Alma list also. | 313 | ||||||||||||||||||||||
57 | 6221 | Free text communications with patrons | We would like to be able to send a patron an email (free text /template) straight from his account, and have it added to his attachments immediately. | 35 | 312 | |||||||||||||||||||||
58 | 8318 | Attach POLs to electronic inventory regardless of Purchase Order Line Type | It should be possible to link any purchase order line, regardless of POL Type, to either electronic collections or portfolios. This would be useful in situations where purchase order lines have migrated with the wrong POL Type, for access service POLs, or where online access is included with a print subscription. Idea has been previously submitted to the Ideas Exchange https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/10634154-allow-linking-po-lines-to-electronic-inventory-reg | 312 | ||||||||||||||||||||||
59 | 7782 | Add Related Record MARC fields to Analytics | We propose that the 76X thru 78X Marc fields, associated data and UNIMARC fields 461 and 462 be indexed in Analytics to facilitate full reporting. https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/40308811-add-related-record-marc-fields-76x-thru-78x-to-ana | 287 | ||||||||||||||||||||||
60 | 8412 | Improve means for purchase order claiming | We propose additional mechanisms for claiming purchase orders. Currently Alma automatically sends one claim to orders where the expected dates are expired. Unfortunately, there is no means to send additional claims to a selected number of orders. Instead, for additional claiming each purchase order where the delivery is late has to be claimed manually and one by one. We propose that claiming purchase orders in future is applicable to a selection of orders (done via the new UI). In addition, we propose a mechanism for automatic claiming in analogy to the “Fines/Fees notification Profiles” (see User Management -> Patron Charges): By specifying conditions for claiming (e. g. in relation to supplier, material type, grace periods) Alma is told when to send purchase order claims automatically. | 285 | ||||||||||||||||||||||
61 | 8385 | Support full SIP2 protocol | The SIP2 protocol is used for the communication between selfchecks and Alma Please find documentation here : https://developers.exlibrisgroup.com/wp-content/uploads/2020/01/3M-Standard-Interchange-Protocol-Version-2.00.pdf Unfortunately, Ex Libris does not support all fields that are available in the protocol (marked as 'not supported' in this document): https://developers.exlibrisgroup.com/alma/integrations/selfcheck/sip2/ Please make the whole SIP2 protocol available for Alma. For example, for Patron Information Response (64), Unavailable HoldsCount and anavailableHoldItems CD are not supported. It is not possible to distinguish between holds that are available (on Hold Shelf) and those that are not yet available (in process) | 270 | ||||||||||||||||||||||
62 | 7768 | Remove set from collection | Just as there is an option now to add a set of titles to collection, there should be the opposite function - remove set of records from collection. | 247 | ||||||||||||||||||||||
63 | 8171 | Include "Next Year" in subscription date range options (Add Invoice Line screen) | Many of the invoices that institutions process are for serials subscriptions for the following calendar year. It would be helpful to many institutions to have the option to select a date range of “Next Year” in the Subscription dates range field when in the Add Invoice Line screen (calendar pop-up). This option would significantly reduce the number of clicks and time currently required to change the date range to the coming year in this screen. Tech Requirements: Keep existing date range filter options but add Next Year as another option. Next Year would start 1/1/[NEXTCALENDARYEAR] and end 12/31/[NEXTCALENDARYEAR]. | 244 | ||||||||||||||||||||||
64 | 8390 | "Undo" option for Resource Sharing requests | Many times, our library staff accidentally choose an unintended Resource Sharing status from the More Actions menu. They either realize the error too late, or they instantly regret the results of the status change. Currently, there is no good way to undo this type of unintended status update for both partners. Manually changing the status only changes it on your end, not the partner's end, which throws off the entire workflow. This usually ends up forcing the partners to create brand new requests in order to finish circulating the material, which is more work for everyone involved. We would love an "undo last action" option in the More Actions menu. This would allow for easier and faster workflow correction of Resource Sharing requests for both partners. | 242 | ||||||||||||||||||||||
65 | 8277 | Have the ability to activate an audible signal to indicate that loans and returns have been correctly done | Due to long response times, librarians regularly make the mistake of scanning an item when the previous loan or return has not yet been recorded. In order to avoid these errors, it would be useful to be able to activate an audible signal when a loan or return is registered. | 241 | ||||||||||||||||||||||
66 | 8189 | Enable bulk due date changes based on a set of items | Fulfillment / Advanced Tools – loans / Bulk change due dates The filters in Bulk change due dates are very large and most of the time we can’t use this functionality, often we've got exceptions. We'd like to use it based on a set of items more specific | 234 | ||||||||||||||||||||||
67 | 8311 | Prioritizing Digitization requests over Hold and Booking requests for processing | All digitization requests should automatically be set to a higher priority than hold and booking requests. For example, we have a book with 3 hold requests, and then someone places a digitization request. It would make sense to quickly handle the digitization request before loaning the book to each of the patrons with hold requests. We know we can manually change the priority of requests, but we would appreciate an automatic process to do this for all digitization requests by default. | 231 | ||||||||||||||||||||||
68 | 6979 | Fix gaps in Subject Browse (LCSH vs. LCNAME subjects) | The separation of subjects into these 2 separate browses is very problematic: LCSH vs. "LC name authority records for 651". Staff must check each browse separately to find all headings. This affects Primo VE customers as well, where the incomplete Subject Browse is a serious patron facing issue. For example, you have to use the LCSH browse to find "Michigan--Antiquities", but you have to use a different browse ("LC names for 651") to find "Michigan--Antiquities--Bibliography." There should be a single subject browse that contains both LCSH and LC names for 651. Geographic headings in "LC Names 651" are used as subjects and need to be in the same browse as LCSH terms. The fact that they are controlled by separate vocabularies is incidental for discovery and database management purposes. In LC practice, some subdivided geographic headings are established LCSH authorities, not LC Name authorities. Only the un-subdivided name is included in LC Names. Subdivided names are included in LCSH. (For an easier to read version of this request please see: https://docs.google.com/document/d/1spu9GJqeT1SOS45rlyy5qGe8Lg799rbbbPvZp4e_ucw/edit?usp=sharing). FULLER EXAMPLE: In LCSH browse you see: Michigan--Antiquities; Michigan--Biography; Michigan--Guidebooks; But in LC Names for 651 you see: Michigan; Michigan--Antiquities--Bibliography; Michigan--Antiquities--Periodicals; Michigan--Gazeteers; What you should see is a single browse: Michigan; Michigan--Antiquities; Michigan--Antiquities--Bibliography; Michigan--Antiquities--Periodicals; Michigan--Biography; Michigan--Gazeteers; Michigan--Guidebooks; MORE BACKGROUND There is a list of “free-floating subdivisions” that can be used under place names in the Subject Headings Manual, H 1140. Most of these are not established in LCSH under individual places, unless a further subdivision that is specific to a place needs to be established. For example, $x Abstracting and indexing is a valid subdivision in the list, but United States—Abstracting and indexing is not in LCSH. On the other hand, $x History is a free floating subdivision, but United States—History is in LCSH because it is needed as part of the structure to add specific subdivisions, e.g. United States—History—Civil War, 1861-1865. Sometimes a heading is in LCSH because cross references are needed for that combination. For example, $x National Guard is a free floating subdivision, but United States—National Guard is in LCSH because it has references from National Guard (United States) and United States—Organized militia, 1903-1916. | 230 | ||||||||||||||||||||||
69 | 8402 | User Purge should be made AFN aware and not allow the deletion of a user record from the user's home institution's IZ when the user has active transactions or fines/fees at another AFN institution | The Alma User Purge job is not AFN-aware. It will allow the deletion of a user record from the user's home Institution Zone (IZ) even when the user has active transactions or fines/fees at another AFN institution in the network. These "orphaned" linked user records are confusing for both users and library staff and are not a best practice for user record management. | 222 | ||||||||||||||||||||||
70 | 8375 | Allow sorting of itemized set members similarly to logical set results | In Manage Sets, enable sorting the members of itemized record sets by title, creator, and publication date, similar to the criteria available for sorting results of logical sets. Currently our only option for sorting the members of an itemized set is by exporting to Excel and manipulating the resulting spreadsheet, which doesn't allow for clean sorting by the same criteria. We have to have some options available to sort the "members" of an itemized set. Title, call number, location, and status are just a few of the options that could be extremely helpful. The members of a set aren't even in the same order as they were on the file used to create the set. This makes it hard to find records! See also Idea Exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/19702903-allow-sorting-of-itemized-set-members-similarly-to | 210 | ||||||||||||||||||||||
71 | 8387 | Remember user’s last selection for “Handling bibliographic records without inventory” | We would like to see Alma remember the user’s previous selection for “Handling bibliographic records without inventory,” when deleting a portfolio, similarly to the way it remembers recent searches. For staff members who perform the same steps repeatedly, this change would save two clicks every time they delete a portfolio – which, for an electronic resource manager, can be hundreds of times in a given project. Replication Steps: Portfolio list > Ellipsis > Delete > Delete confirmation “Handling bibliographic records without inventory” > Delete bibliographic record(s) > Confirm (screenshots attached) | 210 | ||||||||||||||||||||||
72 | 8276 | Improvement usability of the Fulfillment Units and Loan Limits pages | Some of the administration menus are particularly painful to update, due to a lack of ergonomics. This is the case of the Fulfillmen Units page and the Loan Limits page. Instead of an arrow navigation, on which you have to click every time, it would be very useful to have a navigation by click and drag. | 188 | ||||||||||||||||||||||
73 | 8148 | Name/Title Browse Searches for authorized headings | (This was on the Primo 2022 ballot and rejected by ExL as most of the development is in Alma, with a note to submit through Alma NERS). As frequent Primo users searching for known music items, the Alma Music Users Group would like to propose that Ex Libris create a left-anchored browse search for name/title entries found in bibliographic records. An alphabetical left-anchored browse search is particularly helpful for known-item searches that are often used for music materials and prolific literary authors. Currently, Primo provides browse search options for names (name portion only ($a,$q,$d)) and name/title headings used as subjects. For prolific authors, it is not unusual to find thousands of name/title headings lumped under the composers or authors name, with “20+ records” displayed adjacent to the heading. The Primo Browse Search options should include an alphabetical left-anchored “browse” listing for all name/title headings found in bibliographic records. The left-anchored browse name/title index search for authorized access points should include the subfields from the 700 name portion of the heading, as well as subfields from the 700 title portion of the heading ($t, $f, $m, $n, $r, $l, $k, $p, $o, $s), displayed in the order in which the fields are transcribed in the bibliographic authorized heading. The browse name/title index should also include the name/title information from the 100/240 fields, including the subfields from the 240 ($f, $m, $n, $r, $l, $k, $p, $o, $s), displayed in the order in which the fields are transcribed in the bibliographic authorized heading. In the event that the 100/240 combination cannot be included as the left-anchored browse search is developed, it is critical that these fields are added as soon as possible. Ideally, the browse indexes would display 4XX and 5XX cross-references and public notes such as the 680 found in authority records. Associated name and title strings must be kept together for both indexing and display. The cross-references are critical in helping the user to find items known by various titles in various languages. The 4xx and 5xx displays should be linked to redirect the patron to the appropriate section in the index. Benefit: Without a left-anchored browse search, there are too many false drops and omissions when searching for materials by prolific authors and composers. The left-anchored browse results in a more focused and complete search result, helping the user to quickly find all items with the same authorized access point. Attached is an optimal name/title display for the composer Georges Bizet. Also attached is a full list of MARC fields and subfields to be included. Ex Libris rejection statement from Primo 2022 ballot : “As most of the development here is in Alma - Alma will require rebuilding the Browse index to answer the specific needs here. Discussion with the technical people this enhancement is very complex and require new infrastructure for Browse, it is not just simply extending the Browse functionality as today. While our agreements states NERS is treated according to "Product of entry", since this is extreme example that may take more then 100 days and the business logic is more librarian oriented therefore we suggest this will be rejected from the Primo NERS and potentially will be brought up in the future in the ALMA NERS.” | 187 | ||||||||||||||||||||||
74 | 6983 | Anonymize loans for a single patron and allow him to do it himself from his account | We need to have an option in the patron services page to allow our staff to anonymize a patron’s inactive loans, if he ask to. We would like also that the patron could do it himself from his Primo account. This option should exist at the institution zone level and every institution could choose if activate it or not. | 40 | 184 | |||||||||||||||||||||
75 | 8078 | Change the scan in screen to show the same information as the return item screen | The information in the return items screen is very helpful. When staff scan an item on the return item screen and it should be scanned in and put on the hold shelf, it tells them where to route it and who the item is for. Right now our staff use return items for everything to make sure they don’t miss anything and it does create more work. | 184 | ||||||||||||||||||||||
76 | 8183 | Worldshare OCLC ILL Interactivity with Alma | Please offer API interactivity with Worldshare OCLC ILL (Interlibrary Loan) that goes both ways from Alma to OCLC Worldshare as well as OCLC Worldshare ILL to Alma. This would make thing so much easier for our staff! | 181 | ||||||||||||||||||||||
77 | 8357 | Send notification to accounts that are about to expire | We would like to inform users before auto renewal fails that there accounts are about to expire | 180 | ||||||||||||||||||||||
78 | 8327 | Scheduled analytics reports will not send when the reports return no results | Currently, emails are sent even if there are no results in the Analytics report. When using Analytics reports for data checking flow, there is no need to check if there are no results. Therefore, it would be useful to have an option to not send a report if there are no results. Alma should be able to identify the "no results", and stop sending us the empty reports. Bottom line, we do not want to receive analytics reports that are empty. Idea exchange: Scheduled analytics reports will not send when the reports return no results https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/36963247-scheduled-analytics-reports-will-not-send-when-the | 171 | ||||||||||||||||||||||
79 | 8399 | Add an index for OCLC Control Number 035z to the Bibliographic IDs dimension of the Titles subject area of analytics | Add a new Bibliographic ID field for OCLC Control Number 035z to display each OCN one row per MMS ID. This should allow each 035z value found in a bibliographic record to match directly with an MMS ID, and be retrieved as a separate row in results, similar to the "OCLC Control Number single (035a)" attribute. See also: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46082857-add-a-new-bibliographic-id-field-for-oclc-control | 171 | ||||||||||||||||||||||
80 | 8416 | Mark unsaved cataloging records in MDE | Records listed in the navigation pane of the MDE are assigned tags such as ‘Pushed’, ‘New’ or ‘Draft’. The ‘Draft’ tag is assigned upon using the ‘Save as draft’ function and in some other scenarios. It is not assigned consistently upon editing a record. We suggest to add a tag which will appear upon any change made to a record to mark unsaved modifications. | 170 | ||||||||||||||||||||||
81 | 7785 | Link an order to existing inventory directly from a POL | Creating an order for a title which already has inventory requires too many steps, as well as too much navigation. For example, when placing a new continuous order for a physical title that already has a holding (such as when a vendor changes), an operator must perform 7 seven separate steps (below). This reduces productivity and requires too much mousing and clicking. We would like staff to be able to associate a POL with existing inventory directly from a POL via the ability to search and link a holding, item, or portfolio, as appropriate for the order type. 1) Create a POL using Assign Inventory Manually 2) Fill in the order details 3) Save 4) Navigate from the POL to the existing holding 5) Associate the holding with the POL 6) Navigate back to the POL 7) Use Save & Continue or Order Now | 168 | ||||||||||||||||||||||
82 | 7781 | Postponement of the Due Date when the library is closed | We would like, when the library is closed, that a TOU allow loans to be postponed for as many days as there are closed days. https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44581662-postponement-of-the-due-date-when-the-library-is-c" | 167 | ||||||||||||||||||||||
83 | 8332 | Add an option to create invoices from template | It would be beneficial if there could be an option to configure predefined templates for creation of invoices | 162 | ||||||||||||||||||||||
84 | 8344 | Add 'Row Count' as a field to Alma Analytics | Currently, if we want to count the number of rows in Alma Analytics report, we have to change the formula in a different field to create one that will carry out the function (https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/How_do_I_display_the_total_number_of_rows_in_an_Analytics_report%3F). It would save staff time and be more straightforward for newer users if a 'Row Count' field existed in all Analytics subject areas that could be dragged and dropped into reports. | 162 | ||||||||||||||||||||||
85 | 6905 | Add MMS ID to any Export URL report | When running the Export URLs job there is an option to export URLs from the bibliographic record, from digital representation or from the portfolios. When choosing to export URLs from set of electronic portfolios, the report contains only the Portfolio ID and the URL. | 159 | ||||||||||||||||||||||
86 | 7766 | Ability to duplicate invoice | It would be very useful to be able to copy an invoice and then edit it (invoice #s, dates, prices, funds, etc.), rather than having to rebuild the same invoice in the next fiscal year, or the following month/quarter, for the same exact titles. This would be great for lengthy invoices or standing orders that you receive frequently. For example, we have a vendor that sends monthly invoices for the same 5 serials, so a new invoice has to be created manually by staff each month. A duplication feature would enhance productivity in the acquisitions workflow, and would be an ergonomic improvement since less data would need to be added manually through clicking and typing. Justification: There is an existing feature to export and then import an invoice, but that process is cumbersome and is not a time-saver for shorter invoices. The exported invoice contains much of the relevant information, but not in the proper format. There is overall data cleanup needed in the form of removing numerous columns from the export file, and to do things like separate POLs from their statuses, as well as the fact that the export includes fund names but not codes which requires knitting in data from Analytics to include the codes needed in the Import Invoice through file. While import/export process can save time on invoices over 25 lines, it is not worthwhile for briefer invoices. | 145 | ||||||||||||||||||||||
87 | 8116 | Provide Search Filters for Language of Cataloging and Format in Search External Resources and Display the Source of Cataloging and the number of holdings in OCLC in the results | This enhancement corresponds to the “search filters and better results display in the ‘search external resources’ function” idea on the Ideas Exchange (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/34322349-search-filters-and-better-results-display-in-the). Copy catalogers would like to be able to search by language of cataloging and format to filter out irrelevant records when searching “Search External Resources.” It would also be helpful to display the source of cataloging and the number of holdings in OCLC in the search results for catalogers to identify the best record. | 136 | ||||||||||||||||||||||
88 | 8315 | Follow NACO rules when linking bib headings (reduce number of "ambiguous" headings in ACTL reports) | When linking bib headings, Alma does not follow NACO comparison rules when checking for ambiguous headings. This results in numerous headings not linking at all, and being reported as ambiguous. This reduces the utility of Alma's authority control process, because there are too many headings to link manually. Alms should follow the authority file comparison rules at: https://www.loc.gov/aba/pcc/naco/normrule-2.html. Examples of headings that Alma won't link because they are "ambiguous:" 1) Peabody Essex Museum vs. Peabody & Essex Museum -- 2) Ciné+ (France) vs. Cine France -- 3) Mohammad, Ali vs. Mohammad Ali (a cross-reference in the authority record for Ali, Mohammad) -- 4) McFarland & Company vs. McFarland Company (cross-reference in authority record for J. Horace McFarland Company). | 135 | ||||||||||||||||||||||
89 | 8389 | Update the POL renewal fields in batch for every POL on a PO | Update the POL renewal fields in batch for every POL on a PO, as described in this IdeaExchange : https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/40381435-update-the-subscription-dates-range-in-batch-for-e | 131 | ||||||||||||||||||||||
90 | 8135 | Improve Shelf Report | Shelf report within Alma is a great inventory tool but has limitations. 1. Shelf report checks against permanent location and ignores temporary locations. 2. Shelf report is limited to one location. These limitations cause problems which make the inventory process less productive and more time consuming. 1. Because the shelf report checks against permanent location instead of current location, all items that are in a temporary location appear missing when the permanent location is checked. If a display shelf is scanned, all items will error with "not part of the range/set." 2. It is often necessary to scan more than one location at a time. For example, if there are reference items located within the general collection or if multiple floors are scanned at one time. This limitation also makes using many sets that include more than one location difficult. Requests: 1. Give the user the option to check against Permanent Location, Temporary Location, or Current Location when using the Shelf Report tool. 2. Allow users to select multiple locations when using the range and set option within Shelf Report. | 128 | ||||||||||||||||||||||
91 | 7286 | Restart Automatic renewal if users' expiration date was extended | When Automatic loan renewal stops due to user expiry date, manual action is needed to resume it in case the expiry date is extended | 127 | ||||||||||||||||||||||
92 | 7764 | Possibility to change the due dates at the time of the loan | The staff should be able to override the item policy and set a different due date when scanning items for loan. Currently this may be done manually for each item, but in situations where all items being loaned need to have the due date changed it would be great to have the option to set the due date for the loan session, rather than individually. | 126 | ||||||||||||||||||||||
93 | 8349 | Allow different letters to be sent dependant on auto renewal failure | When auto renewal fails the letter that goes out does not allow specification of the reason. We would like to send different letters if it was due to a request, expiry date of user or maximum renewal time reached. | 126 | ||||||||||||||||||||||
94 | 7066 | Reminders - enhance functionality | This area of Alma is incredibly useful, but could use some enhancements to make it better. If it behaved more like the E-Activation task list it would become much more valuable and popular. 1. Showing up on the homepage Task List/sends emails (most important); 2. Ability to assign the tasks; 3. The ability to filter by type or status better; 4. More useful filtering of due dates. | 123 | ||||||||||||||||||||||
95 | 8075 | Improve Alma Resource Sharing handling of items locally held | When requests come in that are Resource Sharing, and we happen to own it physically, there is not an easy way to lend the item. Instead the rota is rightfully designed to skip us (so we won’t hit ourselves) and then go on down to partner of last resort. As an enhancement, we would want the system to pull it out as local holding, and have a way to easily convert it back to a local hold. | 121 | ||||||||||||||||||||||
96 | 8142 | Enhance Item Request | When a user requests an item and there are multiple copies of this item available, Alma considers many criteria (availability, policies and fulfillment units, pickup location, and remote storage configuration) when choosing which item to provide the user. Currently, it is not possible to manage this prioritization. We would like to see more control over how an item is prioritized, including the ability to choose remote storage as a priority preference. In our situation, we have an ASRS which is considered a remote storage location. It would be our preference that when a user requests an item, the automated system would retrieve that item instead of the item going to the pick queue for employees to manually pick from shelf out of the browsable collection. While this enhancement offers a vital change to locations with robotic storage, it also gives all libraries more control over item requests to fit the needs of individual libraries. | 121 | ||||||||||||||||||||||
97 | 6242 | Add ORCID ID to CZ Authorities vocabularies search | Field 0247 $$a XXXX-XXXX-XXXX-XXXX $$2 orcid used in authority records and is currently not searchable in CZ authority vocabularies. | 119 | ||||||||||||||||||||||
98 | 8364 | Funds' Initial Allocated Amount & Transfers | For a complete picture of the initial allocations and amounts transferred, we require in Alma the Initial Allocation and Transfers to display as separate entries under Funds and Ledgers -- Summary tab -- Reports section as part the Display Report and the Balance Type table together with the Allocated Balance (already displaying). | 117 | ||||||||||||||||||||||
99 | 8326 | Adding a parser parameter to portfolios using an import profile | When creating portfolios using an import profile, a static URL is the only URL you can use. If parser parameters are applied to the service of the e-collection, we would like the ability to provide a parser parameter value in the MARC record to add to the portfolio during import. This would be an option in the inventory tab of import profiles to select either static URL or parser parameter. If parser parameter is selected, the user can provide the mapping for the MARC field and subfield like they do currently for static URLs. This change would decrease the amount of duplicate bibliographic records found for Network Zone users. It would also allow all institutions to take advantage of mass URL updates when parser parameters change like we see in Community Zone e-collections. | 116 | ||||||||||||||||||||||
100 | 7299 | Improve Authority Control reporting on partially matched BIB headings in Alma and in analytics | We would like to have an ability to identify our partially linked headings in order to better prioritize authority control work. | 114 |