Skip to content
Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

241 results found

  1. We're currently dealing with a known issue in Sierra 6.2, where volume holds aren't being added to paging lists. Having discovered it on our end fairly recently, we've asked staff to continue running their paging lists for other items, but use the Manage Holds function to find & fill volume requests.

    The problem is that the current search retrieves such a high number of items. And while the search results display counts of the title number of holds, & the total number of bib, volume, & item level holds, you cannot currently limit them & make the Manage Holds report…

    3 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)
  2. We are looking at maximizing the potential for RFID as it relates to inventory & using Mobile Worklists to do so. I know that the scanning of individual tags to update the inventory date was introduced in 11/23 for MW 4.6, but this would mean having the capacity to scan tagged items in batch determined by the capacity of the tag reader with a wand or device like the one pictured, & have their inventory dates updated directly, rather than having the scans stored to an SD card & then uploaded/updated via Rapid Update.

    3 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. Sierra patron records should include a patron pronouns field, so that library staff can record customers' stated preferred pronouns and use the correct language in conversations and communications with customers. The field should be able to display in the Brief patron display. This step would help to support inclusion, wellbeing, and belonging in libraries.

    3 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. When using Manage Holds, information about any recalls that have been issued for items on hold is not displayed.

    This information can be found by consulting the item record (right click, "Edit item", then open the item) and checking for a "Recall Date" value, but it would be very helpful for us if this information could be included directly in the Manage Holds results. For example, the "Hold Status" column could include indication of recalls to provide a fuller picture of the situation at a glance.

    This idea could be incorporated in work on the following related suggestion:
    https://ideas.iii.com/forums/951745-ils-sierra/suggestions/48633872-improve-standardize-information-available-when-vie

    3 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. Currently, authentication using the NCIP protocol does not update the CIRCACTIVE attribute in the patron account. We use this protocol to authenticate to a statewide ILL service and we'd like to know when cards are being used in this union catalog and not just our own.

    We use CIRCACTIVE to determine which cards are being used and which ones aren't. This is useful for statistical purposes, but is also linked to our patron database purge process.

    3 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. The Item Code 1 field was going to solve all my statistical issues. I thought it had 5 characters and each character could be 0-9 which meant I could assign a meaning to each character. For example, the first character indicates agency (1 for CPL, 2 for ADL, 3 for BKM) and the second character indicates audience (1 for adult, 2 for young adult, 3 for juvenile, 4 for other) and the third character, format, etc. HOWEVER it turns out that the largest number this field can hold is 32767 which is weirdly random and very limiting when you want…

    3 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. One of the nicest features in Decision Center is the title details screen, which you can access by clicking on a title in the handful of reports that include title entries such as the Popular Titles Report.

    However, if you're logged in and happen to know the URL structure for those pages (https://[your Decision Center URL]/report/titleDetails/[bibnumber]) you can actually pull up the information for any title in your database directly.

    I'd like to see a means for navigating to that screen more directly and just expose this awesome feature of the platform that already exists. I envision a simple page…

    3 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. 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

    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. 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

    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. 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

    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. 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 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. 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 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 recently started using NCIP authentication for our new ILL service. We learned after implementation that NCIP login is blocked for any of the reasons in the Patron Block Table. This makes sense when the block is for an expired card, or for fees over the threshold. This makes less sense when they have reached their maximum holds in Sierra.

    What we're seeing is that patrons cannot log into the system at all when any of the block parameters are true. We would like to be able to enforce certain blocks but not others for account login.

    We can increase…

    3 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. The element PatronName in the Item Paging Slip & Item Paging List Data library be broken up into Patronfirstname and patronlast_name elements like in the hold/transit slip data libraries.

    3 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. When staff opens a patron's record, add a shortcut feature that allows them to print out patron barcodes. This will really help when someone comes in and don't have their library card with them, so wants to get their barcode information

    3 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. Collection and circulation analytics would improve if we could import Create Lists item/bib search results into Decision Center.

    If so, Decision Center could aggregate Create Lists results (searches based on authorities, orders, or hold/patron circulation behaviours) to provide circulation and collection statistics.

    Our libraries would be satisfied for this import to display the fields that are in the “high”/ “low” circulation weeding reports.

    We understand that the aggregated statistics in Decision Center are generated the night before.

    3 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. 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.

    3 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. We have a floating collection and use Decision Center to manage our collection. We need to know what is on the shelf OR not on the shelf at multiple sites. To do this, we use excel pivot tables to manipulate the "low circulation weeding reports". I have attached the workflow and the result.

    After pivoting the "low circulation weeding reports" (searching for items that have circulated less than 300 times in 1 month at multiple branches) our result includes everything on the shelf at multiple branches. The pivot table allows us to identify which titles are at a branch AND…

    3 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. Support team told us Sierra isn't designed to supply hold request date for cancellation notices. Please consider add it. thanks

    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)
  20. Freezing (for patrons) and NNB (for staff) should be combined to one unified functionality so that frozen holds could be managed by patrons (WebPAC/Encore/Vega and third-party solutions using REST) AND by staff (Sierra Circulation). There are a few related ideas (and I commented them) but I think the main problem is that the function is not the same for patrons and staff. So I'd probably like first to remove NNB and replace it with just freeze/unfreeze on Sierra side too. (After that think about the additional options such as thaw date and freeze even if items available.)

    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)
  • Don't see your idea?