Skip to content
Innovative Idea Exchange

ILS - Sierra

JUMP TO ANOTHER FORUM

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

264 results found

  1. Problem:

    Currently, the "Prioritize Paging Open Locations First" feature and the "Prioritize Hold Fulfillment at the Pickup Location" feature for Title Priority Paging are incompatible. When you have both turned on, pages will skip closed locations and page at an open location, but will not allow the hold to be filled because there is a copy available at the hold pickup location. However, the hold pickup location is not paged for that item since paging skipped that location, so they don't see that patrons are waiting. This causes staff confusion and also impacts how quickly a patron can receive their…

    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)
  2. We would like to be able to reinstate manual charges, whether they're for the collection agency fee, or something like a damaged container or replacement power cable. The reason why we cannot currently reinstate this particular charge type is not stated in documentation & while I may have known at one point, memory fades as we age. Being able to simply reinstate a manual charge would simplify & expedite workflows, whereas now, we have to make like Hall & Oates.

    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)
  3. Our consortium would like to request a feature enhancement in Sierra that allows ability to transfer volume-level holds to bib-level holds.

    Currently, when we need to move records from a multi-volume bibliographic record (with volume records) to a monographic bibliographic record (without volume records), we must manually add or copy each volume-level hold to the bib-level record and then remove the original volume-level hold. This is a very tedious and time-consuming process, especially within a consortium of more than 100 libraries.

    A streamlined method to transfer holds between volume and bibliographic levels would save staff time, reduce errors, and improve…

    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)
  4. Sometimes I'm working in Global Update and am using the toggle feature or the limit tool. I then want to work with just those records. I don't want to remove the others from the review file, but rather copy the records I want to look at into a new review file so that I can work with them there.

    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)
  5. We use the Repeated Bills feature, where after the bill is sent day 30, we send a repeat bill (#2) on day 40 and a final repeat bill (#3) on day 50. Unfortunately, when you run the Notice job for Repeated Bills, there is no way to tell whether the repeat being sent is for day 40 (#2) or day 50 (#3) except if you scroll through all of them and do the math as it pertains to the item status date. Staff haven't been doing that regularly. Ideally, there would be a column that showed you what # of…

    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. When exporting from create list the pop-up window can be expanded, but the box displaying the criteria (chosen fields) cannot. We often export more fields than can be displayed within the box. It would be helpful to allow this box to show more of the criteria in a single view so that we can both check what is being exported and easily note what is included when attempting to add the same export to a different list. (We have already maxed out the number of saved exports.) Expanding the window provides an empty space underneath the section displaying the criteria.…

    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)
  7. To inform the blocking of IP ranges from which bad actors are abusing the /selfreg form, record the origin IP in a varfield or new fixed field on the patron record.

    If a varfield, the default of an x-Note would suffice, but make this varfield tag customizable via one of the administrative interfaces. Historically speaking, Admin Corner would have been the go-to place to make this customization.

    7 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. It can be useful to check the number of users in each group currently logged in to Sierra. In our case, there is a self-checkout group that should have a specific number of logged-in users throughout the day that requires monitoring.

    The number of users in each group logged in to Sierra over the course of the day is available by SSH (in Admin Corner, "Number of INNOVATIVE users by hour").

    Monitoring this information in an automated way is not straightforward. Admin corner can send an email, but only from an interactive SSH session. It is possible to automate an…

    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)
  9. Idea: update the expected format requirements for the email variable-length field to account for modern, non-standard email domains.

    Relevance: The prevalence of non-standard email domains is growing. Currently, Sierra accepts some non-standard formats, like .me, but rejects others like .health. This prevents the saving of the patron record and requires that the patron provide another email or change their notice preference.

    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)
  10. Sierra supports Z39.50 but not SRU. Remote search and import/overlay of records from SRU-only sources seems to be increasingly important. We have begun to encounter potential partners who are no longer able to offer Z39.50 access because their systems only support SRU; likewise, we would like to be able to offer SRU ourselves to maximize interoperability.

    GPL-licensed software is available to add SRU support to Z39.50-capable systems such as Sierra (for example, CQL-Java, yazproxy and metaproxy):

    https://www.loc.gov/standards/sru/
    https://www.indexdata.com/resources/software/cql-java/
    https://www.indexdata.com/resources/software/yazproxy/
    https://www.indexdata.com/resources/software/metaproxy/

    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)
  11. Idea: add a limiting feature to Globally Purge Charges that allows for choosing which fines to clear by itype.

    We use itypes to delineate lending in addition to the location code. With libraries transitioning to fines-free policies and seeking to waive existing overdue fines for patrons on some items (but not all), the current function structure complicates matters, as it only allows for limiting by location code, rather than by item type. There are ways to work around it but they are cumbersome.

    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)
  12. When creating a new bib record and using the insert drop-down box, the windows always open in the same place and the same size. If I change the location or size of the window, I have to do it EVERY TIME. This is very annoying. Let me set those parameters and make them permanent for my login.

    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)
  13. With the increase in bot attacks causing DOSS downtime, it is important to be on top of server security. The Apache module "modsecurity" has been around for over 20 years and there is an active community creating rules (https://coreruleset.org/) to block bot attacks. I think that Innovative should include modsecurity in their Apache build and actively support or provide the option to its customers to include rules to increase server security.

    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. When pulling Low Circulation (or High) reports (Collection Tools > Maintenance), would like to include the Series Title (if applicable) in the displayed (and exported) report. We run into titles that have low circs, but if we see it's in a series, we normally don't weed it, because the series should remain complete. Thus we are stuck using Create Lists for this type of information (either exporting the report as a review file and then exporting fields THAT way or simply starting with Create Lists from the get-go). It would be more convenient if it was included in Decision Center.

    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)
  15. Block particular bib records from having their URLs checked by use of a suppression code

    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)
  16. Sierra uses a particular Load Table to determine how bibliographic records are overlaid when new records loaded via Remote Search (i.e., downloaded from another library catalogue using Z39.50)

    According to Sierra's documentation the default Load Table is "m2btab.b", but Innovative can configure Sierra to use another one if desired.

    We have found that certain projects call for different Load Tables because different sets of fields should be retained, discarded, or inserted. It is possible to change to a different Load Table for remote search temporarily (or modify the current Load Table), but that would affect all cataloguers for the duration…

    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)
  17. Create Lists allows staff to create review files of invoices, but a number of useful fields from the invoice cannot be exported from the system. Notably the subtotalamt, shippingamt and totaltaxamt fields, which can all be accessed via both SQL and the RestAPI, are missing from the export options.

    We would like to see these added so that fuller invoice data could be exported into something like Excel for further accounts reporting and tracking.

    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)
  18. Our staff have found that when they search the staff catalog for classic titles with lots of adaptations many of the adaptations are ranked higher in the search results than the title they actually searched for. For example, a title search of our catalog for "Moby ****" yields "Ahab's Wife" as the top result, with other derivative works and commentaries all appearing before the first record for the novel itself (in our case, result number 24). We'd like to see the results weight matches on the work's own title (e.g., 245 field) higher than matches in other fields, such as…

    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)
  19. When checking in an item over Sierra, it would be helpful to have an extra column added for item status. e.g. Available, In Transit or On Holdshelf. This would add more transparency when processing items (especially if we are interrupted mid-scan), allow for double checking items are placed in the right pile, and help with training new staff who may want to have more visibility around the different journeys an item can take once returned. Added bonus: If it can show the additional sorting groups available in IMMS, this will assist staff even more.

    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. Currently, when a query is beyond the capabilities of Create Lists, it is usually possible to use a SQL query with Python to produce a report. Such a report might list record numbers of bibs/items/orders/patrons/etc which bear further examination and correction by library staff, but staff must copy record numbers or barcodes in the report and paste them into the SDA to pull up the records in question. It would be much easier if an API endpoint permitted those record numbers to be written to a review file so staff can go through them one-by-one in the SDA.

    Another use…

    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)
← Previous 1 3 4 5 13 14
  • Don't see your idea?