245 results found
-
Fix truncated Z39.50 server names in SDA
Z39.50 database display names are limited to 50 characters in Admin Corner, but the contents of this field is truncated (at some length < 50) when displayed in the "Selected Databases" dialog in Sierra.
The 50 char limit may seem generous, but for multilingual organizations (and/or multilingual databases or those that just have long names!) it can already be a challenge to abbreviate the database name in each language to fit while still retaining sufficient information. Truncation of this field further reduces the functional length of the database name.
As-is, the "Selected Databases" dialog can be dragged wider by the…
2 votes -
globally update bibliographic records with multiple branch codes
We would like to be able to globally add an additional bibliographic branch code to a subset of bibliographic records harvested through "create lists." This is because currently (Sierra 6.1), it is possible to change a bibliographic branch code, but not add additional ones while retaining the original branch.
The reason is that we have records for electronic resources that should display under a relatively new scope set up for a new branch. With only the original branch in the bibliographic record, it is necessary to view the entire collection (or the original branch) to access the item in the…3 votes -
Add alt tags to improve accessibility
A lot of alt tags appear empty by default and other accessibility issues seem to be outstanding. These two are examples that cannot be corrected by admins.
Add relevant tags to improve the accessibility of the search results page briefcit.html. The search box form has no labels that can be read by screenreaders:
Element Location: #searcharg
<input type="text" name="searcharg" id="searcharg" size="30" onchange="return searchtoolSubmitAction()" maxlength="75" value="[search term]">
The search history select element has no accessible name:
Element Location: .navigationRow[align="center"]:nth-child(5) > form > select[name="HISTORY"][onchange="onSelectChange(this, '')"]
<select name="HISTORY" onchange="onSelectChange(this, '')">
3 votes -
SAML matchpoint with patron variable field
We implemented Patron SAML and uses a patron variable field to be the matchpoint. This field contains the patron's email address. Our IdP accepts dots, dash and underscores in patrons' email address. Due to Sierra indexing rules where symbols (including dots, dash and underscores) will be dropped, different patrons with the same letters in their email address but have different symbols in different positions won't be able to authenticate through Patron SAML.
e.g. Patron A's email = abc.def@test.com, Patron B's email = abc_dec@test.com . Both will fail authentication as Sierra will use abcdef@test.com and return both patron records.3 votes -
Improve/Standardize Information Available When Viewing Holds
Library staff would like to be able to see more details on holds that have been placed, including how the hold was placed (Sierra Desktop vs. SierraWeb vs. Web vs. mobile app, etc.) and who placed the hold (Sierra login if not the patron).
Right now, it is not consistent how holds information is displayed.
If you view holds w/in a patron record (holds tab), you don't see when the hold was placed or how they placed it. However, if you View Cancelled Holds, you see the date/time it was placed, along with the date/time it was cancelled, along with…
28 votes -
Hold Pickup Reminder/Courtesy Notice
Idea: Create an additional notice type, Hold Pickup Reminder/Courtesy, that can be configured to send a reminder notice to patrons that they have a hold ready for pickup that is about to expire, similar to the courtesy notice for checked-out items.
Relevance: When you place an order for pickup at most other businesses, you are sent a reminder email before the pickup deadline that the item is ready for pickup. Libraries would benefit from a similar option, especially those that use hold pickup lockers where there is limited space for holds. This way, if a patron decides they don't want…
20 votes -
New Skins for Sierra
Can we get some new skins to choose from for the SDA/Sierra Web?
There are currently two: Half Dome & Glacier Point.
We currently use colors to differentiate between our Production instance of Sierra & our Test version. However, we also have a Training database.
Variety is the spice of life! How about a rose-colored skin, a powder blue, or a "Millennium Green" as an homage to the Millennium database?
16 votes -
Make OpenAPI definition document (previously known as Swagger specification) available for Sierra's APIs
There SHOULD be an OpenAPI definition document available for Sierra's APIs via Swagger, but currently, there is not.
The OpenAPI definition document (https://swagger.io/specification/) is a standardized format for describing the structure and behavior of an API. It is a machine-readable document, usually written in JSON or YAML, that provides a comprehensive blueprint of an API's endpoints, operations, input/output parameters, response formats, authentication methods, and other essential details.
For comparison, here is an example for the Polaris API / Swagger install (on an iii training server):
https://polaris-training.polarislibrary.com/PAPIService/swagger/v1/swagger.jsonBenefits of an OpenAPI Definition Document:
…* Standardization: Provides a consistent format28 votes -
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)
12 votes -
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.
13 votes -
Disable Reprint bills button In Sierra
We can’t use this button because we don’t use print templates for our bills.
We would prefer them to look pretty with Print Templates instead of the plain text we currently have. To avoid staff confusion, it would be great if this we had the ability to disable/grey out this button.3 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Transit/Hold Slip Printing Via Mobile Worklists
We've begun testing the current version of Mobile Worklists at a handful of branches. While it can clearly speed up the process of holds management by trapping items pulled from the shelves or updating the status of those items not found to missing, a second check-in is required to generate a hold or transit slip, creating an extra step for staff.
We'd like slips to print to a networked printer as items are checked in via the app.
2 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Expand to different order statuses for the Sierra REST API
The Sierra REST API does not return the order record for the bib if the order status is "a" (fully paid). It will only return information if it's "on order".
Patrons are unable to place holds on new materials using Innovative Mobile for bibs with paid order records that do not yet have items attached.
3 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Update "last checkin" field even if item wasn't checked out
Update the "last checkin" field every time an item is checked in. Now, when you check in an item, the "last checkin" field is not updated if the item is not checked out. I don't know of any reason to not update it. When I look at an item record, I want to know the last date that the item was seen; this can be useful in tracking down items that seem to be missing, or coming up with a list of items that might be missing.
6 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Order Status rapid update
Rapid or global update to update all Order Status at once.
6 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Create a way for staff to add messages to other library's items outside of scope restrictions
The problem that's prompting this suggestion:
I work at Gondor Library. An item arrives from Rohan Library (outside of scope) to fulfill a hold for my Gondor patron. But staff notices it has damage that has NOT been noted in the record (or on the physical object).Gondor staff have two choices.
a) the damage is extensive enough that we decide to not fulfill the hold and send it back to the owning library, Rohan.
b) we use our judgement to decide whether the Rohan book's damage is minor enough to fulfill the hold.
For example, only light stains on…17 votes -
Notice Count Should Be A Count Of Notices Not Items
Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead see the Notice History feature, which shows the number of items for which notices are sent.
I think it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Provide indicator/warning when an order record has already been sent to a vendor
In the print/send orders function, it can be easy to accidentally upload an order to a vendor multiple times. As a means to mitigate this error I propose a two part feature.
As a first step, the system should provide some indication when viewing the orders to ftp queue if an order has already been ftp'd once. I could see two methods for accomplishing this. 1) Add a column to the queue display for sent date, taking the most recent date present that has been appended to the ISBN pick field in a record from having been previously sent. 2)…
25 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Reading History via API
At this time it is apparently possible to retrieve the patrons Reading History via REST API sorted by date (oldest first or newest first). The most requested API enhancement request for us is to be able to retrieve the patrons Reading History via REST API sorted by Title. Another enhancement request is to be able to retrieve the patrons Reading History via REST API sorted by Author. This would be useful since users may have hundreds of items in the reading history.
6 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Increase Sierra Username Character Limit
We need to increase the number of characters allowed for the username - currently a maximum of 12. We prefer to keep our Sierra usernames the same as a user's network login name (one less thing to remember). Anything over 12 characters forces us to make a different Sierra username that fits within the Sierra parameters.
9 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
- Don't see your idea?