268 results found
-
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 -
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…
24 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 -
Customize layout & Field Visibility in patron View/Edit Record
In the Patron View/Edit Record window the group of fields at the top cannot be arranged in any way but the default. It would be nice to be able to arrange these fields in a way that meets the needs and use of our staff. For example, I would like to be able to put all the editable fields in the first 1-2 columns, such as exp date, language, notice preference, patron type. Then all the uneditable fields (total checkouts, total renewals, circ active...) to the right of these columns. It would be nice to have a sort of drag…
2 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 -
Allow Create Lists to sort and export the normalized best author and best title fields
These two fields can be incorporated into searches performed within create lists but are not available among the fields that can be exported or used for sorting. Best title normalized is particularly helpful for data brought into a spreadsheet as the removal of special characters and diacritics can greatly improving sorts and searching.
These fields are available via SQL, where I make frequent use of them, but for most of our users Create Lists is the only option for extracting data from the system.
1 vote -
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 -
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 -
Set a maximum price allowed for the item price field
I'm blatantly copying this idea from a suggestion by Wes Osborn in the Polaris Idea Exchange (https://ideas.iii.com/forums/951742-ils-polaris/suggestions/46833076).
While creating item records, generally while following prompts in an item template, it is easy for staff to scan a value such as a barcode or ISBN into the price field by mistake, resulting in items that can incur bills in the billions of dollars if the issues are not caught. Additionally, it's easy to miss entering a decimal point and still wind up with charges exponentially higher than intended.
This could be mitigated by setting a maximum allow value for…
1 vote -
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…
11 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…
13 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 -
Add a Stat Group When Creating a Patron API Key for Vendors
This proposal suggests enhancing the Patron API key creation process by incorporating a Stat Group field, allowing staff to categorize API keys by vendor and track their usage using existing reporting tools. The proposed enhancement would modify the API key creation window to include an optional Stat Group field towards the bottom. If left blank, the default stat group (zero) would be assigned, maintaining current functionality. This change addresses a common issue where vendors do not implement the stat group provided by the library, often resulting in API-driven transactions being categorized under stat group 0. This leads to inaccurate or…
27 votesThe product team will review this idea for consideration for a future release.
-
Access to SAML logs
When using the LDAP authentication option, it was useful to be able to see the authentication logs to diagnose login issues. After switching to SAML authentication, access to the SAML logs is only available to Innovative support.
I propose granting customers access to the CAS Apereo application logs so that we can see SAML authentication issues. These logs may not be as detailed as the LDAP ones since the authentication is happening at the IdP but they might provide clues to further investigate authentication issues.
1 vote -
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…
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…6 votes -
innovative_footer
The Innovative_Footer token for webopac does not have any CSS styles or identifiers associated with it so that it can be controlled through stylesheets. The footer is inappropriately placed on our website due to this lack of control.
Propose adding identifiers to the underlying HTML code so that it can be styled properly. Replace its <span> tag with a <div> tag might be appropriate.
3 votes
- Don't see your idea?