Skip to content
Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

51 results found

  1. It is better to provide the option to delete the identity providers and modify the name of the identity provider by the administrator during SAML configuration.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Sometimes we want to update a patron record and blank out a date in the expiry date field for a continuing staff member.

    The patron API cannot do this - blank values are rejected as invalid JSON e.g.

    {"expirationDate": " - - "}
    {"expirationDate": ""}
    {"expirationDate": "--"}
    {"expirationDate": "null"}

    All we can do is add a date, and for continuing staff we can only use the maximum possible date of 18 Jan 2038.

    Enhance the API to accept a blank value in expiry date.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Several years ago we adopted context logins. We have established that a 1 tier login will not work for us.

    CURRENT STATE : Our Regional Library consists of 39 branches in almost as many cities. To distinguish the branch of our Sierra users we currently use a two-tiered login. This login process allows us to continue to use generic branch accounts while meeting our obligations to protect customer information. The two-tiered login allows us to collect branch-specific data and apply unique user settings, options, and settings.

    The drawback is that our staff must login twice and it may pose an…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. As ILS administrators of a large consortium, we would like the RFID Server Options Table to have an additional field/column to add notes (library name, dates, staff initials). When one of our member libraries needs to change RFID entries, we sort through nearly 200 lines to determine which one needs updating. Many entries use IPs without identifying library information. We must read through old library correspondence to discern which IPs belong to the library. This task takes up valuable time when we are trying to assist a library with troubleshooting or adding and removing entries.

    An additional free-text field to…

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Many libraries are creating individual logins for each staff member. Staff needs the ability to change their password in case they forget it. At this point, they need to be logged into the SDA to change their password which doesn't help if they can't remember it.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. There is currently no way to update the status of a hold in the API.

    It would be very useful to change the status from

    "status": {
    "code": "0",
    "name": "on hold."
    },

    to

    "status": {
    "code": "i",
    "name": "Requested item ready for pickup."
    },

    Enhancement to be integrated into https://ideas.iii.com/forums/951745-ils-sierra/suggestions/47618129-it-s-about-time-to-make-holds-apis-first-class-cit ?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. The ability to create custom print templates is an essential component of many parts of the system. LX Starter is a viable replacement for the templates used for notices but not for the printing of things like due slips, spine labels, and hold slips that must remain within the SDA to support daily workflows.

    Print templates are designed in a third party software called Jaspersoft Studio, but Sierra's documentation lists version 6.0 as being the last supported version of that software. However, that version is roughly 10 years old and the installer only seems to exist as an old link…

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Idea Description
    This idea is based in part on one submitted back in 2019 by Andy Helck.  Create an endpoint that will provide the list of records included in a specified review file from Create Lists.  I essentially envision this as the API version of the bool_set SQL table.

    Idea Value
    This would provide outside systems the means of retrieving lists of titles that staff maintain within create lists and can provide a means for services to access data without having to work out how to create Json queries.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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,…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Idea Description

    Automatically clear the jarcache directory in the Sierra Desktop App installation files after an upgrade or provide an option in the SDA settings to enable this.

    Idea Value

    The jarcache directory is updated the first time the SDA is launched after a Sierra upgrade.  After several upgrades the directory becomes bloated with old .jar files. It makes sense for the jarcache directory to be cleared as part of the first launch of the SDA post upgrade. This will ensure a fresh set of jar files.

    23 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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…

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Could we have an enhancement option to create a Sierra user administrator account that has access to all accounting units? I am the only system administrator and cataloger for a library system with multiple accounting units and I would very much appreciate the ability to do everything I need to from one log-in (managing/creating new check-in records, for example).

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Objective: Allow Libraries to assign granularity to API role permissions.

    When Libraries give a 3rd party vendor read access, we want to be able to restrict the endpoints associated with the role. In addition, we want to restrict the fields that can be returned. Ideally, the implementation of the requested features below will provide an interface to the Innovative clients where the vendor access will be managed.

    There are endpoint and field restriction examples below to show how assigning granularity to API role permissions would allow libraries to improve access management.

    Endpoint restriction example:
    We would like to be able…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. We would like to see more specific permissions on items records to allow staff who don't have access to edit entire item records to be able to do basic things like add and delete item messages or change the status of the item.

    Frontline staff are discovering outdated item messages or finding that items are missing, and it's inefficient for them to have to contact someone else to change the status of the item, or delete an item message attached to it.

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?