70 results found
-
Separate summary view property for each of the search functions
When a Sierra SDA login is first created the system utilizes individual summary view properties for the various search functions. By default in cataloging if you open up the summary view of a record you see item records, in search/holds you see holds, in place orders you see orders and in serials checkin you see checkin records.
If you opt to change that setting however from the record view properties menu (say to change this to view all) it can impact all 4 search functions. It would be better to split this menu out, so that the setting for each…
15 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
It's about time to make Holds APIs first-class citizens
Idea Description
It would be far nicer to have the ability to work with hold data directly--in contrast to having to retrieve hold data via the patron APIs. For example: currently, in order to (reasonably) find the "pickupByDate" values for holds with status "(Bib, Volume, Item) hold ready for pickup" you would have to use a combination of the Sierra SQL feature (to first find all the patron record numbers possessing such a hold) and then filter all the holds for the list of patrons (from the previous step) having the "pickupByDate" key in the response object. Once you have the holds,…15 votes -
Connect Global Update with Scheduler
We complete many repetitive tasks in cataloging and patron record management each day. This entails using Create Lists to generate the list, and then using Global Update to perform the same set of edits each time. We need Scheduler to be able to connect into Global Update to perform those tasks automatically.
This may require enhancement of Global Update to save the Command Input, or it might mean adding the Command Input choices to Scheduler.
Example:
Scheduler runs an updated Create List using a saved search query to identify items that need their suppression code updated.
It then uses a…22 votes -
Dark contrast display option for the SDA
We see the Sierra 6.0 Release Notes features new Accessibility improvements in the SDA. It is unclear if this includes a high contrast display option which staff recommend to support use of the software by many different types of staff.
14 votes -
Expand Locations field for bibs, holdings, and orders API responses
Currently, the bibs, holdings, and orders APIs do not return the expanded Locations fields for records with multi locations. The multi location value that is returned is useless without the expanded values.
6 votes -
Allow the "remember me" in Sierra Desktop App login screen to remember passwords as well as username (as previous versions of Sierra did)
Previous versions of Sierra (version 5 and below) allowed the saving of usernames and passwords in the Sierra desktop app login screen. Since upgrading to 6 this functionally has been lost.
9 votes -
assign 1st and 2nd tier timeout permissions (for those using context logins) : SDA and Sierra Web
In the SDA OR Sierra Web, the Sierra 2-tier login workflow allows administrators to set a "time-out" setting to the 2nd tier (personalized) login. This setting determines if the session will time out or close after a specific amount of time.
This is an excellent workflow except that there is no setting to manage 1st tier inactivity. This means at the end of the day we have many Sierra licenses that remain open and the Library must manually force close the desktop applications using the "restart a process" in Admin Corner.
Please configure context logins so that Libraries can determine…
4 votes -
MFT support in data exchange
Prior to Sierra 6.0 and the introduction of MFT, it was possible to use FTP to transfer files though data exchange within Sierra. This is no longer possible as MFT is not supported in data exchange.
Please add support for MFT in data exchange in the same way as support for MFT has been added in scheduler.11 votes -
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,…
13 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?