51 results found
-
Allow sorting options for API Results
An example of this is the Items/GET API appears to sort the results based on catalog date/item id of the item. It would be nice to specify a different sort parameter that would allow the current sort or a new sort which would return them in the same sorting specified in the Cataloging function in Sierra.
This might be nice for other APIs as well.
5 votes -
Make API loader allow bad MARC
One of the major advantages of Sierra is it's flexibility. Particularly the Sierra fixed fields. Sierra allows those fixed fields to be used in non-standard ways, but the API loader does not have that flexibility. If you try to load records with unexpected data with the API, the load will fail. The API MARC loader does not have to validate MARC. Sierra has never really validated MARC. Don't start now. The API should allow the same weird non-standard data as the rest of Sierra.
7 votesThe product manager will review this idea for possible inclusion in a future release.
-
Correct 0 date values in SQL views to NULL values
In circtrans and finespaid views (and maybe more views) there are several dates that are showing a value of 0 (which displays as 1969-12-31 due to UNIX date formatting).
Dates do not have a value of 0, they can however, have a value of NULL, which is already how things work with other dates in the system, like the bib record cataloguingdategmt.
This should be fixed for any dates in the system, not because anyone may or may not vote for it, but because it is both inaccurate and inconsistent.
I logged this as a ticket,…
12 votes -
Manage Reading History through RESTAPI
Currently patrons can opt in and out of Reading History our public catalog (Bibliocore) but we get many requests from patrons who want to manage that reading history by removing items from Reading History but the RESTAPI doesn't allow users to do that, they have to log into their accounts on WebPac in order to manage the titles in that history. We would like to see full Reading History management currently available in WebPac added to the RESTAPI.
8 votes -
Edit Username in Admin App
Once a user is created in the admin app, you are not able to update the username. You may update the password, permissions, etc., but not the username itself.
All of our clerk-level positions are part-time, so there is a lot of turnover. Each time an employee leaves, his/her account must be deleted and a new one created for the replacement. When the new account is created, you then must import all of the permissions, options, locations served, etc., of a comparable employee for the same location.
Ideally, we would simply be able to edit the username and password and…
58 votes -
Make Review Files in Admin App Consistent w/SDA & Sierra Web
In Sierra - SDA and Web - you can sort review files in Create Lists by the column header, i.e., file #, current records, max records, type, status, login and created.
In the Admin App (BACK END MANAGEMENT > Review Files), the only columns displaying are file # (which doesn't appear to match the file # in the SDA/Sierra Web), number of records (= max records), current and name. Sorting by column is not an option.
The display, labeling and function for managing review files should be consistent.
Idea Value
When managing review files in the admin app, particularly when…21 votes -
Add "Back" option vs. just "Next" or "Cancel" in Record Creation screen
When you create (a) new item(s) while cataloging -- or create any records actually! -- the pop-up that guides you to enter the data step-by-step should have a back button. Currently, if you make a mistake and click Next you either have to cancel and start over or keep going and fix the mistake on each item record individually after saved/completed. It can be quite tedious when you are adding multiple items at once.
Idea Value
Save time! What would just take a few clicks/seconds to fix can sometimes mean a lot more time, especially if you Cancel and have…
54 votesThis idea has been selected to include in Sierra 6.4
-
Increase Character Limits for Data Fields
The Notice Type data field in the Text of Circulation Notices table is a mere 20 characters long. As we've had to create a number of new notices for temporary changes in operating hours, policies, etc., due to COVID, we'd like to make the description a bit more descriptive than 20 characters allows.
Also, because you cannot delete any of the old/test notice types, you already have to use up some of the characters to note that it's old/test/not used.
This runs along the same lines as Loan rules: increase the limit beyond 20 characters to loan rule names. This…
8 votes -
Upgrade OpenSSH version
Currently INN-Reach and Sierra servers are bundled with OpenSSH 7.1, which is over 7 years old as of this writing. There is a sorting bug (https://bugzilla.mindrot.org/show_bug.cgi?id=2694) that impacts the Scheduler functionality that would be fixed by upgrading to at least OpenSSH 7.6. Also assume that multiple security vulnerabilities exist in 7.1.
12 votes -
Make Sierra User Profile Imports Additive, at least Optionally
In the Sierra web-based admin utility, in Authorizations and Authentication Admin, when importing permissions from one Sierra user to another, the "donor" settings overwrite those of the recipient user. I propose adding a checkbox to allow these to be imported in an additive manner.
Idea Value
Recently two of my coworkers in Technical Services and Collection Development received promotions and shifted into different roles. When using the feature to assign the permissions of users similar to the new roles, old but still valid permissions were lost due to the way the feature overwrites the recipient permissions with those of the…35 votes -
Alerts for when indexing stops
Currently there are no alerts when indexing stops working. We would like to see some put in place.
We recently had our keyword indexing stop working. It wasn't completely obvious to us for few months that there was a problem with indexing as it didn't seem to be every record.
Idea Value
Having an alert to III would save time troubleshooting if it's a metadata problem and raising tickets for something that could have an alert on it.37 votes
- Don't see your idea?