268 results found
-
Create a different template for repeat bills
Add the ability to create a template specifically for repeated bills. This would allow us to send a different message for a reminder bill than what we sent in the original bill. This is would be similar to how we are able to create different templates for 1st, 2nd, 3rd etc Overdue Notices.
23 votes -
Include items checked in via selfcheck in Homebound Patron Reports
Sierras Homebound Patron Report currently excludes items that are checked in via selfcheck (SIP2). Since almost all check-ins in our libraries are done through selfcheck machines, the report provides an incomplete history and is not usable for tracking items checked in for homebound patrons.
Please update the report logic so that all check-in methods, including selfcheck check-ins, are included. This would ensure accurate reading history and make the module much more useful for libraries that rely on automated check-in workflows.
4 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 -
Batch Check-In Should Not Update Circactive Date
Batch check-in is a necessary component of debt write-off and system maintenance. Running this process updates the patron account circulation activity date (CIRCACTIVE) even though this is a system-generated process and not initiated by the patron.
We use the CIRCACTIVE date when reporting on card usage, and as an indicator of when to delete inactive cards. Because the date is updated through batch check-in, we have to do a lot of clean-up work to understand actual patron usage and behavior.
Ideally, batch check-in should not update CIRCACTIVE. It would be fine for the account UPDATED date to be updated.
This…
25 votesThe product team will review this idea for consideration for a future release.
-
Remove leading diacritic from normalised author fields
Sierra currently removes any leading apostrophe for example from the normalised author fields on bibs. For example, normAuthor over API. Other diacritics such as ʻokina (ʻ) is not removed from normalised fields. Because of this, any systems that use norm fields over API are not alphabetising the author correctly.
It would be great if Sierra could remove the ʻokina (ʻ) from the normalised author fields. Specifically normAuthor.
2 votes -
Create Lists - Saved Searches - Ability to Rename, Show Creator, Last Used
We repeatedly run up against our limit of saved searches in Create Lists. There are probably saved queries created long ago that no one is using/needs. I was hoping to assign staff to review the queries and put their initials in the saved search name, but when you go to Edit, you can only edit the query, not the query name (like you can a review file). Ideally it would work like the review files themselves, when you can see who last ran the list (initials, date and time). And perhaps apply the "Own" option. This would really help to…
45 votesThe product team will review this idea for consideration for a future release.
-
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…
8 votes -
Block particular bib records from having their URLs checked by use of a suppression code
Block particular bib records from having their URLs checked by use of a suppression code
5 votes -
add location column in Count Use function
Under the count use function, is it possible to add a location column? Currently, we have Title / Barcode / Count / Status. This way, when staff collects used but not checked out items and counts their usage, they can also see - at a glance - if the item belongs to a different floor/location and can separate it on the spot.
This added information will save staff time and minimize the chance of something being misplaced.
9 votes -
Support SRU (Search/Retrieve by URL) in addition to Z39.50
Sierra supports Z39.50 but not SRU. Remote search and import/overlay of records from SRU-only sources seems to be increasingly important. We have begun to encounter potential partners who are no longer able to offer Z39.50 access because their systems only support SRU; likewise, we would like to be able to offer SRU ourselves to maximize interoperability.
GPL-licensed software is available to add SRU support to Z39.50-capable systems such as Sierra (for example, CQL-Java, yazproxy and metaproxy):
https://www.loc.gov/standards/sru/
https://www.indexdata.com/resources/software/cql-java/
https://www.indexdata.com/resources/software/yazproxy/
https://www.indexdata.com/resources/software/metaproxy/4 votes -
Allow holds on bibs when holdable items are on order
We have a non-holdable lucky day collection whose items are on the same bib as our regular, holdable copies of those titles. Sierra allows patrons to place holds on titles that are on order, but sometimes the non-holdable copies are the first to arrive -- at which point, Sierra sees that all items on the record are non-holdable, and stops allowing holds until the first holdable copies come in.
Innovative recommended splitting nonholdable items onto a separate bib record, which seems liable to clutter up the catalog; moreover, some of these items are likely to be moved into our regular…
34 votesThe product team will review this idea for consideration for a future release.
-
Globally purge charges by itype
Idea: add a limiting feature to Globally Purge Charges that allows for choosing which fines to clear by itype.
We use itypes to delineate lending in addition to the location code. With libraries transitioning to fines-free policies and seeking to waive existing overdue fines for patrons on some items (but not all), the current function structure complicates matters, as it only allows for limiting by location code, rather than by item type. There are ways to work around it but they are cumbersome.
5 votes -
Offer the ability to retain a patron's receipt preference at checkout
At checkout, Circulation Staff must ask patrons at the end of each checkout if they want a printed receipt, email receipt, both, or none, or place a pop-up message on their account. It would be great if there were a way to retain each patron's receipt preference so that upon closing out the patron's record, the preferred receipt would be sent, print, both, or no receipt would be given.
38 votesThe product team will review this idea for consideration for a future release.
-
Send to: Notices
It would be great if the logic & momentum that introduced Send To - Rapid or Global Update in Sierra 6.3 & will soon allow the same shortcut to Delete Items could also be applied to the Notices function.
I had submitted a similar request that the shortcut be added to Globally Purge Charges & am wondering if this might be combined into one request or if it's easier to introduce them one at a time?
Use case: each week, Cincinnati generates a list of customers sent a statement of charges (bill notice) via Create Lists. This list is then…
6 votes -
Insert/Update Location Codes from a CSV file
Develop a utility to add new location codes to the so-called Branches table using a CSV file as input. Optionally permit updates (overlays) of existing location code entries so that the branch_code_num, name and/or is_public columns may be reassigned values in this way.
Our library has very granular location codes which describe branch (or collection subset of a branch such as a display area), audience, format and genre, loosely speaking. This amounts to 220-250 location codes per branch (or collection subset). We currently have over 5,000 distinct location codes in our Sierra database, and every time a new branch is…
11 votes -
Disallow cancellation of holds by Pickup Location, Loan Rule or Stat Group
It would be helpful to have the ability to prevent a hold from being canceled based on its pickup location.
We have holds pickup lockers installed in three locations and are finding that if the lockers contain an item which has since had its hold canceled, the lockers will send a CheckIn SIP transaction to Sierra for that item, resulting in the item being [logically] used to fulfill someone else's hold [while physically still housed in a locker]. For popular new releases, this is happening more frequently than one might imagine. The ability to disallow the cancellation of holds at…
10 votes -
Improve server security by supporting Apache module mod_security
With the increase in bot attacks causing DOSS downtime, it is important to be on top of server security. The Apache module "modsecurity" has been around for over 20 years and there is an active community creating rules (https://coreruleset.org/) to block bot attacks. I think that Innovative should include modsecurity in their Apache build and actively support or provide the option to its customers to include rules to increase server security.
4 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.
15 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.
14 votesThe product team will review this idea for consideration for a future release.
-
2038 issue
We use the patron's 18th birthday as their youth card expiration date. Due to the Year 2038 issue we have been unable to add the correct date for several years now. We would really like to be able to have (any/all) date fields updated so we can begin to record accurate future dates again.
29 votesThis will be implemented in Sierra in 2027.
- Don't see your idea?