239 results found
-
Include hold pickup location and expiration date in cancellation notices sent to LX Starter
Our library recently started using LX Starter, which includes merge tags for the hold pickup location and expiration date in its template for hold cancellation notices. However, we've been told that Sierra doesn't pass this information to LX Starter and therefore this information can't be included in our cancellation emails. We would like to have this information added so we can provide additional information to our patrons about when and where their holds expired.
16 votesThe product team will review this idea for consideration for a future release.
-
Add the ability to create a review file from items in Global Update.
Sometimes I'm working in Global Update and am using the toggle feature or the limit tool. I then want to work with just those records. I don't want to remove the others from the review file, but rather copy the records I want to look at into a new review file so that I can work with them there.
15 votes -
Expand Window for Create List Export Criteria Display
When exporting from create list the pop-up window can be expanded, but the box displaying the criteria (chosen fields) cannot. We often export more fields than can be displayed within the box. It would be helpful to allow this box to show more of the criteria in a single view so that we can both check what is being exported and easily note what is included when attempting to add the same export to a different list. (We have already maxed out the number of saved exports.) Expanding the window provides an empty space underneath the section displaying the criteria.…
15 votes -
Make pop-up windows remember size and location
When creating a new bib record and using the insert drop-down box, the windows always open in the same place and the same size. If I change the location or size of the window, I have to do it EVERY TIME. This is very annoying. Let me set those parameters and make them permanent for my login.
15 votes -
A "full Payment History file" event should log an error to the Admin App's System Messages log
Today our Payment History file reached 9,999 records which is close enough to the 10k record capacity that the attached error message was displayed. Fortunately the staff member had the presence of mind to screen-capture this error dialog today so I could read its message verbatim, but this isn't always the case. It would be helpful for an error of this severity to be written to the System Messages log viewed using the web-based Sierra admin app.
Given the low variety of error messages written to that log, there must be all kinds of similar messages which are not logged,…
15 votes -
Add Character Map to Patron Record Creation/Editing Menu
Despite the constant threats to our funding & the fact that some seem to treat the notion of DEI as offensive, we continue to want our library to be seen as a welcoming & inclusive environment for our patrons.
We would like to be able to extend this to how their name is represented in Sierra & on notices/when seen in the catalog. We currently have a sort of crib sheet for staff to use to insert diacritic characters into patron names as needed, but think it would be helpful if they didn't have to navigate away from Sierra when…
15 votes -
Add multiple items to a review file from the Item Summary page
It's great to be able to add a single item to a review file from the item record page. It would be even better if we could add multiple items from the item summary page.
15 votesThe product team will review this idea for consideration for a future release.
-
Show number of copies on order per library
We are a Consortia of 51 libraries with 25 Acquisition's Units. We would like to see how many copies each library has ordered. This was available in Encore.(see screenshot) Vega does not show order records at all so we would like to see more detailed information in Sierra. Currently, you can only see that other libraries have ordered, not number of copies (see screenshot)
15 votesThe product team will review this idea for consideration for a future release.
-
Add the ability to transfer an item-level hold to the bib level
Please add the ability to transfer an item-level hold to the bib level. In our system, holds automatically attach to an available item. When the item that has captured the hold is unavailable for some reason (ie. the item has gone missing), there is no easy way to deal with the hold if there isn't another available item. You only see the option to transfer the hold to another specific item. If these are all circulating or unavailable and there is a list of holds at the bib level, you cannot currently transfer that item hold back to the bib…
14 votes -
Improving Hold Shelf Management in Sierra and IMMS
We at the Libraries of Malmö would like to suggest that Innovative and Lyngsoe develop an interaction between Sierra and IMMS to help clear hold shelves.
The issue: Currently, we have hold shelves at our libraries that are numbered between, for example 100 and 120. Each day we clear the holds that have expired the previous day. When we first implemented IMMS, we noted the shelf to clear down on a paper almanac and then wrote them off a week later.
However, we have since then coded a very simple application to keep track of this for us. The application…
14 votes -
Expand invoice record fields that can be exported from Create Lists
Create Lists allows staff to create review files of invoices, but a number of useful fields from the invoice cannot be exported from the system. Notably the subtotalamt, shippingamt and totaltaxamt fields, which can all be accessed via both SQL and the RestAPI, are missing from the export options.
We would like to see these added so that fuller invoice data could be exported into something like Excel for further accounts reporting and tracking.
14 votes -
Rearchitect iiirecord.record_metadata to provide improved audit trail accountability
It is sometimes helpful to see who created, updated or deleted a record. Catmaint provides a lot of detail but doesn't cover many record types. I propose the following solution, which doesn't have particularly burdensome storage requirements:
- Build a many-to-many table with an id primary key column, a timestamp, a code indicating the C-R-U-Uprevious-D record operation and foreign keys linking to record_metadata.id and to iii_user.id.
- Backfill this new table using the available timestamps in record_metadata, catmaint and any other table like catmaint which might provide record edit history.
- Rename record_metadata and drop its four *_gmt timestamp columns. Yes, this creates…
14 votes -
Increase Invoice Limit for Downloaded Invoices
The current cap of 99 invoices downloadable per day can impede & dictate staff workflows.
Because of this, our Acquisitions staff must also set limits with vendors like Baker & Taylor, as we can receive more than 99 in a day. It would be optimal if they could download at will up to invoice limit.
Not all shipments are dealt with sequentially, which further complicates matters.
14 votes -
Correct 0 date values in SQL views to NULL values
In circtrans and finespaid views (and maybe more views) there are several dates that are showing a value of 0 (which displays as 1969-12-31 due to UNIX date formatting).
Dates do not have a value of 0, they can however, have a value of NULL, which is already how things work with other dates in the system, like the bib record cataloguingdategmt.
This should be fixed for any dates in the system, not because anyone may or may not vote for it, but because it is both inaccurate and inconsistent.
I logged this as a ticket,…
14 votes -
allow libraries to customize options for "claim return" workflow
There are 3 options in the "claim return" workflow at checkin.
1) Checkin items (with no fines) and change status to missing.
2) Checkin items (with no fines) and change status to claims returned.
3) Leave items checked out (send overdue notices) and change status to claims returned.We always select #2, but we cannot stop staff from accidentally selecting #3. This is troublesome for us because in the #3 workflow customers get an email overdue notice when they have already told the library they have returned the item - and customers can be quite upset about this.
Is there…
13 votes -
Allow holds on multiple bibs at the same time from a review file
There are times staff need to place holds on multiple items that are in a review file (we are working on a collection and need to change something about a group of items) and it's time consuming to go item by item. It would be nice to place bulk item holds on items in a review file.
13 votes -
Improve search relevancy for titles with many adaptations
Our staff have found that when they search the staff catalog for classic titles with lots of adaptations many of the adaptations are ranked higher in the search results than the title they actually searched for. For example, a title search of our catalog for "Moby ****" yields "Ahab's Wife" as the top result, with other derivative works and commentaries all appearing before the first record for the novel itself (in our case, result number 24). We'd like to see the results weight matches on the work's own title (e.g., 245 field) higher than matches in other fields, such as…
13 votes -
Create a pop-up when you are about to overwrite a review file in create lists.
It is very easy to accidentally overwrite a review file in create lists. There should be a pop-up that asks if you want to overwrite the file so that you know you're doing it.
13 votes -
When receiving items, limit search results to orders available for receipt
It would be nice if there was a setting in the Receiving function to limit your search to only items available to be received. We search by PO and have to wade through loads of items already received and billed. This was available years and years ago on the old Horizon system.
13 votesThe product team will review this idea for consideration for a future release.
-
Options Group setting for showing Last Patron
In a consortial setting we have some libraries that would like to avoid showing last patron data for a item in an attempt to avoid retaining data that could be used to breach a patron's privacy.
13 votesThe product team will review this idea for consideration for a future release.
- Don't see your idea?