281 results found
-
Add fund code field to item record
We need the ability to report on items based on the fund used to purchase them. Recently, I was asked to create a list of items added to the database using a specific fund code. This cannot currently be done in Create Lists because there is no common field that links item records to their associated order records.
Create Lists also does not allow us to pivot from an item record to its attached order record, or vice versa. This creates a significant reporting gap.
This functionality is important because a single bibliographic record can have multiple items purchased using…
1 vote -
Charge type on fines tab needs to specify if it is a damaged item
We would like “replacement” changed to a term that reflects the actual item status. Currently, “replacement” is used for both long-overdue and damaged items that have been billed. To determine whether a billed item is damaged or simply overdue, staff must open the item record and check for a damage note.
1 vote -
Keep Bib Information for Deleted Records (for Reading History)
Unlike Polaris, when a record is deleted in Sierra, all information is deleted from the system. Unfortunately, this means that Sierra libraries would not be able to take advantage of the Vega Enhancement to "Display Deleted Titles in Reading History." Thus patrons only see "Resource is not available" in their Reading History.
Patrons opt in to keep their reading history assuming that the data will be there when they look for it. They don't understand why there is no record of it, think something is broken with the system.
4 votes -
Track Patron Renewal
Please add the ability to report on patron record renewals. We currently use the Created Date field to track the number of new library cards issued. However, there is no reliable way to determine how many patron records have been renewed. While the Last Updated date changes whenever a patron record is modified, it is triggered by many different types of updates, making it impossible to distinguish renewals from routine record maintenance.
Having the ability to track patron renewals would provide valuable statistics for monthly reporting to our Board of Control and Parish (County for the rest of you...) administration.…
3 votes -
Choose Priority between Item-level holds queue and bib-level holds queue
More control over choosing priority between the item-level holds queue and the bibliographic-level holds manually so that the Processing department can pull back specific items on popular, high-volume holds with more ease.
2 votes -
Add ability to attach new volume from Serials Checkin function
We'd like the ability to attach a volume record directly from the Serials Check-in module. Currently, because this functionality is not available within Serials Check-in, staff must rely on workarounds and switch to other functions to complete the task. Adding this capability would streamline workflows, save time, and make the Serials module more efficient and useful.
3 votes -
Customise font size and other details in Sierra pop-up messages
We'd like the ability to customise the display of Sierra popup messages, specifically we'd like the ability to increase the font size for key information (for example, the pickup location or destination) so it stands out more clearly. We would also like the option to hide the call number, as it is not used by our library.
3 votes -
Extend data retention of accounting transactions in SierraDNA
The accounting transaction tables in SierraDNA allow you to query information you would normally only have access to via a retained posting register. However, it is hardcoded to only retain information for 2 weeks, which isn't enough time to do anything meaningful with that data.
Ideally I'd like to see data for a full fiscal year but if there needs to be a limit for whatever reason, maybe tie it to the related payment history file.
3 votes -
MARC Tags - Exporting
When exporting MARC tags, export should have all the subfields marked. Now that I try to export say 041, I can´t see if the language code is in a, b or d... And this would be important to know as it is not the same to have say |a fin |h eng and |a fin |a eng.
This is a re-share of an expired idea that seemed to garner some attention its first time around.
1 vote -
Improve item title display on patron-facing devices by adjusting SIP2 parameters
Skip certain MARC subfields when preparing data for SIP2 connection.
Specifically:
When Sierra needs to send information to display an item title on a patron-facing device (automated materials handler, self-checkout kiosk, etc.) via SIP2, it currently appears to concatenate all occupied subfields of MARC field 245 and remove the delimiters. This means that certain information not intended to be patron-facing can end up appearing in the title the patron sees on screen (e.g. "880-01 Desu nôto 2..." appearing instead of just "Desu nôto 2...", where "880-01" is not actually part of the title, but rather a reference to another field…1 vote -
Create an API endpoint that delivers language translations to Vega
We maintain English and Te Reo Māori names for library branches and item locations in the Sierra branches table. Making these available through an API would allow Vega to display the correct names automatically, and provide a consistent bilingual experience. This would also remove the need to manage translations separately in Vega Admin.
4 votes -
PIN limitations in Sierra: PIN_ALPHA_NUM should accept special characters
PINALPHANUM does not accept special characters.
If Vega Discover continues to be limited by wwwoptions for PIN creation, this option should accept special characters.
PIN Best Practice: The strongest defense combines a long length (12+ characters) with a true random mix of letters, numbers, and symbols.
Length vs. Complexity: Recent security guidelines emphasize that making a password longer (like using a multi-word passphrase) is often more effective than adding a single symbol to a short word. That said, library users do use special characters and want them included in their library PIN.
Adding symbols increases the character set…
13 votes -
Make Additional PCODEs Available
Libraries are increasingly looking at ways to gather metrics on patrons without identifying them. Data on age, gender, race, or all manner of characteristics might be collected, depending on the library.
I'd like to see Sierra be more accommodating in what it can collect & store on a patron's record, with the introduction of one or more additional PCODEs that can be used to store a significant amount of fixed field codes.
For example, we partner with schools in our service area & offer not only educator cards, but do an upload of student data. Having schools within our service…
10 votes -
Add ability to query empty review files to the reviewFiles API
This idea is a bit of an addendum to Bob Gaydos' idea to create an endpoint that allows writing to review files (https://ideas.iii.com/forums/951745-ils-sierra/suggestions/50308716).
The current API cannot provide a list of empty files. That information would be incredibly helpful in conjunction with the other idea so that you may programmatically identify an available review file of sufficient size for your needs. Beyond that, it may be useful to use the API to write an alert mechanism for when your system may be running low on available files.
It is possible to explore this information via SQL, but the…
9 votes -
Create expanded RestAPI endpoint for patrons/validate that exposes a limited set of patron fields
We have many vendors who have a need to check data in a few patron record fields as part of their authentication process. Fields such a ptype, home library, the expiration date, etc...are necessary to confirm that a patron is affiliated with the institution subscribing to that vendor's resource and that their card remains in good standing are necessary to provide. However, doing so currently requires providing the patron read permission, which also exposes a variety of additional sensitive data that these vendors should not have access to for their needs (PII, checkouts, fines, reading history, etc.)
The lesser patron…
11 votes -
Allow users to freeze a hold even when an available item could be used to fill that hold.
If a library's circulation or OPAC rules allow a customer to place a bib or item hold, the customer should also be able to freeze that hold at any time. This functionality is available in Polaris, but not Sierra.
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 the item immediately.
Allowing holds to be frozen…
19 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 -
Add Unique Control Numbers to Predefined Charges Table
Please add a unique, control number (ID) to predefined charges table in Sierra. This control number should be exported in the Fines Paid report. Currently, libraries waste significant administrative hours manually reconciling monthly, quarterly, and annual revenue because edited descriptions break automated data sorting (like Excel Pivot Tables).
The Problem:
To balance monthly revenue, libraries must sum payments by the type of predefined charge (e.g., photocopy charges, replacement cards, damaged books, donations).
Because Sierra lacks a dedicated, un-editable control number for predefined charges, we are forced to hardcode budget codes directly into the text description fields:
• 3323 Library Mug…3 votes -
REST API-compatible Time to Holdshelf/Time to Reshelve
Our library has deprecated the classic WebPAC in favor of a REST API-based custom discovery layer, but the Time to Holdshelf/Time to Reshelve temporary status message we've configured isn't included in the API response. It would reduce frustration for staff and patrons if we could implement a delay before items appear to be on the shelf when patrons check our website or mobile app.
Please add the temporary status to the REST API response.
7 votes -
Sierra Patron Address info updates
The Sierra Patron Record is able to be communicated to Vega Discover in such a way that differentiates the following fields:
Street Address Line 1
Street Address Line 2
City
State
Postal Code
Country
Discover does not parse Sierra addresses correctly.
1) New Discover registrations do not parse correctly in Sierra.
2) Existing registrations in Sierra do not parse correctly in Discover.This was the comment by Innovative Staff on this topic:
Discover does have difficulty with parsing Sierra patron addresses, and this is not changing in the July release. For libraries who do allow patrons to edit their own…5 votes
- Don't see your idea?