288 results found
-
Data Exchange > Send PRINT FILE using FTS - Include Login Column
I am often having to clean up/delete files that have been saved/"printed" via FTS File Exchange to Data Exchange (send print files out). I sort by date, clear old ones, but some I am hesitant, may still be needed. It would help immensely if the system identified the login associated with this printed file. Then I'd know who to ask/who owns this file (and who isn't deleting their old files). The login column is used elsewhere in the system (Create Lists, etc.), so would ensure consistency.
3 votes -
The patron selfreg form should record the origin IP in the patron record
To inform the blocking of IP ranges from which bad actors are abusing the /selfreg form, record the origin IP in a varfield or new fixed field on the patron record.
If a varfield, the default of an x-Note would suffice, but make this varfield tag customizable via one of the administrative interfaces. Historically speaking, Admin Corner would have been the go-to place to make this customization.
9 votes -
More universal accessibility features
Improving universal accessibility features for users/employees with diverse accessibility needs.
For example, for employees with visual impairments :
- High contrast mode and adjustable font size. Currently, users can change text color and size, but increasing the font size often causes content to be hidden, as the window does not automatically adjust. Users must manually resize the window each time. A responsive layout would greatly improve usability.Other potential improvements could include : screen reader compatibility, customizable keyboard navigation, text descriptions for icons, etc.
Even just the high contrast would help a lot. Additionally, it would be helpful if users…
26 votes -
Add an API endpoint which permits writing to review files
Currently, when a query is beyond the capabilities of Create Lists, it is usually possible to use a SQL query with Python to produce a report. Such a report might list record numbers of bibs/items/orders/patrons/etc which bear further examination and correction by library staff, but staff must copy record numbers or barcodes in the report and paste them into the SDA to pull up the records in question. It would be much easier if an API endpoint permitted those record numbers to be written to a review file so staff can go through them one-by-one in the SDA.
Another use…
13 votes -
Warning at Hold Placement for Homebound Patrons
Description:
Sierra’s “Check Reading History During Homebound Checkout” feature is very helpful, but many homebound materials in our workflow are supplied through holds from other branches. At the hold placement stage, no warning is shown if the patron has previously borrowed the same title, which leads to unnecessary requests and inter-branch transfers.Requested enhancement:
Add an option to display a warning when a hold is placed for a homebound patron if their Reading History shows a previous checkout of the same item or another item attached to the same bibliographic record.Benefits:
- Avoids unnecessary item movement
- Saves staff…8 votes -
Add "mark damaged items" workflow to checkin
Staff need an easy way to make an item "damaged" when performing check-in. The current damaged workflow requires staff to be in the patron account.
All of our libraries have book drops, and every day, damaged items are returned. It doesn't make sense for library staff to stop their process, review the item record, and then review the patron account details in order to mark an item as damaged.
Can the "Mark Damaged Items" button that appears in the checkout function (checked out items) screen be added to the check-in window. I have attached an image where we would like…
25 votes -
Make Vendor Payment Info More Readily Accessible
The vendor payment address should be accessible at invoice payment function. Currently, the invoicing function needs to be closed & address information accessed at order record, vendor, etc.
2 votes -
Improve patron address parser to better map data to the patron_record_address table
Sierra has a mechanism for parsing the free text entered into patron address fields in the client into separate fields for elements such as city/state/postal code that exist in the patronrecordaddress table. Those distinct fields may then be searched in create lists or utilized in SQL queries. However, the algorithm used to parse out those data points is extremely rigid in terms of the data it expects to see and is quite prone to mapping data incorrectly if an address entered into a patron record does not conform to those guidelines.
For one common example in our system…
28 votes -
macros
Add additional macro modifiers in Sierra.
The 6.3 update removed the Control + F1 modifier macro. Can we consider adding more modifiers such as left/right control, left/right alt, and left/right shift keys?
Thank you!
3 votes -
Allow users to freeze a hold even when an available item could be used to fill that hold.
Sierra libraries cannot freeze a hold in Vega Discover (and likely other third-party catalogues) if an available item could fill that hold. Innovative has confirmed that this limitation is caused by Sierra, and that Sierra's hold-freezing behavior must be changed before Vega Discover can support this functionality.
Currently, customers cannot freeze a bib-level hold if there is an available item that could fill the request. This prevents customers from managing their holds the way they want. In many cases, they do not know an appropriate "Not Needed Before" date, but they do know that they are not ready to receive…
1 vote -
Improve clear hold functions for integrated systems
When a hold has been cleared or is defunct, the information Sierra provides integrated systems (IMMS for our example) over API is not consistent. In particular, when clear holds is run in Sierra. During clear holds, the item status either remains at ! On holdshelf or changes to another item status. When it remains as !, IMMS sees the hold is still active and does not instruct staff to clear the item from the hold shelf. Daily and weekly processes are needed to update the item records for IMMS to recognise the changes.
Can the clear hold function in Sierra…
16 votes -
Create RestAPI with a Patron Validate role that updates the “last circ activity date” in patron record
Our library wants to provide the patron validate role to our vendors.
But, we do not want to give the vendors any read or write roles.We do this now with several vendors, but the authentication does not update the "last circ activity" field in the patron record.
Is it possible to add a new permission that would only allow authentication but update the "last circ activity" field in the patron record.
Why add this feature?
Our library purges patron that don't circulate for X number of years. We don't want to delete patrons that are actively using our eVendor…28 votesSelected for the Sierra 6.7 release by MEEP enhancement process
-
Translate item status and OPAC message codes in Summary View
Currently, it's possible to have item status and OPAC message codes displayed in the summary view. However, we'd like the option to display the full names of these statuses/messages rather than the codes to make things clearer for staff who don't have them memorized.
6 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 -
Generate a Hold Cancellation notice when clearing Expired/Defunct Holds
Currently, only when you cancel a hold from either the Hold tab or the Hold queue do you get the option to generate a hold cancellation notice. When a defunct hold is cleared from the holdshelf (clear expired holds), we would like to see a prompt to send a hold cancellation notice(s), just as we do when cancelling holds outside of the clear holdshelf process. All those that get cleared could use the same “drop hold” message in the text of circulation notices (explaining your hold has been cancelled because it’s expired/hold pickup by date has passed). These would be…
14 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 'Previous' button to Receiving
Staff are really appreciating the addition of a 'Previous' button to the record creation process which allows them to back up and fix a mistake without having to go all the way through the process before returning to make a correction. Staff would like to see similar functionality within the Receiving process. We receive using the process that combines creating the item with receiving.
Currently, for receiving an item, it will prompt you through the boxes to fill in the required information. As you proceed through, if you make a mistake or skip something you have to cancel and start…
14 votes -
Use a suppression code to block particular bib records from running through a Headings Report
Considerable time would be saved if bib records suppressed from public display (by way of a suppression code) were not included in the Headings Report. These bib records are typically from electronic sets or batches that amount to hundreds of records, some with several headings for each record.
8 votes -
Add the ability to search for more fields for volumes in create lists other than just holds.
The only option in create lists for volumes is to find holds. It would be helpful to be able to search for volumes that 'match' or 'has' variable fields. Then we could search for volumes that say 2024, for example. It would also be helpful to have this in Global Update as well when toggling to variable fields.
2 votes -
Include authorities in the Search/Holds module
It'd be great if authority records and cross references were included under the Search/Holds module and be the same as what staff encounter with the Catalog module. Right now it is different. In our system, staff often use Sierra to place holds with the public on their behalf. It would be great if authorities were available in the Search/Holds module results display so that staff could benefit from the information.
If a staffer did an author search and they had a pen name (Robb, J.D.) then they'd be redirected to see the other author's name (Roberts, Nora).... Or they may…20 votes
- Don't see your idea?