276 results found

1. Inter-library loan

   We use forms in Sierra for inter-library loans. We have, however, found that some users are too quick in submitting requests. I think it would be a good idea for ILL forms in Sierra to have additional functionality to slow user behaviour down and to allow for more accurate ILL requests:

   1. We have ILL conditions included as text below our ILL forms that would be better served as check boxes in the form e.g., "I understand I am responsible for copyright"; "I understand I am responsible for any replacement or repair fines".
   2. I also think if we could make certain fields mandatory on an optional basis it would help improve ILL workflows e.g., the ISSN/ISBN field.

   We use forms in Sierra for inter-library loans. We have, however, found that some users are too quick in submitting requests. I think it would be a good idea for ILL forms in Sierra to have additional functionality to slow user behaviour down and to allow for more accurate ILL requests:

   1. We have ILL conditions included as text below our ILL forms that would be better served as check boxes in the form e.g., "I understand I am responsible for copyright"; "I understand I am responsible for any replacement or repair fines".
   2. I also think if we could make certain… more
   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Allow changing of hard coded "collection agency" wording

   We would like to change the wording on our bills to patrons for long-overdue items from “COLECTIONS AGENCY REPORT CHARGE” to “MATERIALS RECOVERY SERVICE CHARGE,” but this is hard-coded. We use Unique Management, who describes themselves as a materials recovery service, and we try hard to always use that wording and not say "collection" or "collection agency." Some patrons have become alarmed by seeing "collection agency" on our bills for long-overdue items and in their accounts.

   13 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   The product team will review this idea for consideration for a future release.

3. Block particular bib records from running through a Headings Report, by use of a suppression code

   Considerable time would be saved if bib records suppressed from public display (by way of a suppression code) were not included in the Headings Report. These bib records are typically from electronic sets or batches that amount to hundreds of records, some with several headings for each record.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Sort ready for pickup holds by expiry date in checkout function

   Staff assisting any customers who cannot pickup all their ready holds at once, would benefit from seeing and sorting the expiry date of holds in the patron's holds list. This will assist with preventing their holds from expiring and being placed again.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

   An item's status and pickup expiration date are displayed in the status bar at the bottom of the Holds page as an item is highlighted/selected. While you can't sort by the expiration date, this information is displayed on screen for staff users.

5. /v6/patrons/{id}/holds/requests/form API endpoint should accept item record numbers as parameters in addition to bib record numbers

   The form endpoint is used to identify cases in which a patron must place a volume level hold or is restricted to an item's home library as a pickup location. Both of those involve item level specifics and yet the endpoint only works with bib records. This is an issue in particular with multi-location libraries/consortia who use the home pickup feature.

   As an example, a sample bib record has two attached items, one which uses the home pickup feature such that it may only be picked up at library A, and one that does not restrict pickup locations so may be picked up at libraries A, B, or C. Because the endpoint returns valid pickup locations for title level holds, it will always return the full list of locations and there is not a way for the end user to know that one of the items may only be picked up at library A.

   Allowing the endpoint to provide item level details would resolve that, though it would also mean testing out individual item records in advance of actually placing holds in all cases in order to see if this restriction is in place...which I don't love. So I'm open to alternative suggestions to fix this feature but this seemed like the smallest ask to me.

   The form endpoint is used to identify cases in which a patron must place a volume level hold or is restricted to an item's home library as a pickup location. Both of those involve item level specifics and yet the endpoint only works with bib records. This is an issue in particular with multi-location libraries/consortia who use the home pickup feature.

   As an example, a sample bib record has two attached items, one which uses the home pickup feature such that it may only be picked up at library A, and one that does not restrict pickup locations so may… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   UNDER REVIEW  ·  0 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Reinstate Manual Charge

   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.

   •  

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   UNDER REVIEW  ·  0 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Translate item status and OPAC message codes in Summary View

   Currently, it's possible to have item status and OPAC message codes displayed in the summary view. However, we'd like the option to display the full names of these statuses/messages rather than the codes to make things clearer for staff who don't have them memorized.

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Administration & APIs  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Provide full Branches table and full Location code list via Sierra REST API

   Today, Sierra’s REST API does not provide a reliable way to retrieve a complete list of location codes (and their names/labels) as defined in Sierra’s Branches table (SDA: Admin > Parameters > General > Branches). This creates friction for discovery-layer implementations and other third-party integrations that require an authoritative, up-to-date list of locations.

   Innovative Support shared that “it’s not possible to get a list of all locations using the REST API,” and that the closest option is the branches endpoint, which only returns locations that are linked to entries in the Branch Address table, not a full representation of the Branches table. Fiona (BiblioCommons) also confirmed the current Branches API is insufficient and has requested III improve it to return a full representation of the Branches table.

   Current behavior

   When calling:

   GET /v6/branches/?fields=%2C

   We receive only two branch entries and an API response showing:

   "total": 2 (implying only two branch records exist), even though our environment contains many more branch/location entries in the Branches table.

   The response includes a locations array, but only for locations linked to Branch Address table entries.

   Example (truncated):

   {
   "total": 2,
   "start": 0,
   "entries": [
   {
   "id": 1,
   "name": "Poudre River Public Library District",
   "locations": [
   { "code": "adult", "name": "Adult" },
   { "code": "afic", "name": "Adult - Fiction" },
   ...
   ]
   },
   {
   "id": 2,
   "name": "Interlibrary Loan"
   }
   ]
   }

   Desired behavior

   Provide a REST API mechanism to retrieve a complete, authoritative list of:

   All Branches table entries (not only Branch Address table entries that have names populated), and/or

   All location codes as defined in the Branches table, including their display names/labels and other relevant metadata used by integrations.

   Why this matters (impact and use cases)

   This enhancement would significantly improve Sierra interoperability with third-party vendor products and local applications by enabling real-time retrieval of location configuration data.

   Primary use case: Discovery layers

   BiblioCore, Aspen Discovery, and Vega Discover (and similar products) need accurate location codes and labels to support:

   facets and scoping

   branch/location-based availability display

   collection/location grouping rules

   pickup location logic

   suppression or “hidden” locations behavior where applicable

   Right now, when a library:

   adds a new location code,

   renames a location display label,

   retires/deprecates a location,

   …they typically must manually communicate those changes to the discovery vendor (often via spreadsheets/emails/tickets). That adds delay, introduces errors, and makes “near real-time” configuration synchronization impossible.

   Secondary use cases (beyond discovery)

   internal analytics/reporting tools that want to label circulation/hold data by location

   AMH/bin mapping, routing, or sorting optimization tooling

   self-check, RFID, or third-party circulation peripheral integrations

   custom staff apps and dashboards that need the live location dictionary for validation and display

   Proposed solution options

   Any one of these would solve the problem. More than one would be even better.

   Option A: Enhance /v6/branches to represent the full Branches table

   Return all branch/location records stored in the Branches table, not just those tied to Branch Address entries with names.

   Add a way to request “Branch Address fields” separately (since Branch Address and Branches table are distinct concepts in practice).

   Option B: Add a dedicated endpoint for locations

   For example:

   GET /v6/locations

   GET /v6/branches/locations

   Option C: Provide an “includeAll” style flag
   If III wants to preserve current default behavior, add something like:

   GET /v6/branches?includeAll=true

   GET /v6/branches?source=branchesTable vs source=branchAddressTable

   Improving access to the Branches table / locations dictionary via REST API would be a major interoperability win for Sierra. The main theme is discovery layer integration (BiblioCore, Aspen Discovery, Vega Discover), but the same capability would benefit many other integrations and local applications that need accurate, real-time location metadata.

   Today, Sierra’s REST API does not provide a reliable way to retrieve a complete list of location codes (and their names/labels) as defined in Sierra’s Branches table (SDA: Admin > Parameters > General > Branches). This creates friction for discovery-layer implementations and other third-party integrations that require an authoritative, up-to-date list of locations.

   Innovative Support shared that “it’s not possible to get a list of all locations using the REST API,” and that the closest option is the branches endpoint, which only returns locations that are linked to entries in the Branch Address table, not a full representation of the… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Ability to alter the Recommends Approval and Denial emails that go to patrons who submit a purchase request

   Problem: The text of emails sent when using the Approval and Denial notifications in Recommends cannot be currently altered. We would like to be able to provide more customer friendly email templates to patrons that allow us to explain why an item was denied or what the process is for items that are approved.

   Impact: Being able to communicate with our patrons at the outset of the process will save staff time by not having to have go back and forth with customers over email to explain processes and reasons for purchase requests. Additionally it will improve the customer's experience with the suggest a purchase process.

   Problem: The text of emails sent when using the Approval and Denial notifications in Recommends cannot be currently altered. We would like to be able to provide more customer friendly email templates to patrons that allow us to explain why an item was denied or what the process is for items that are approved.

   Impact: Being able to communicate with our patrons at the outset of the process will save staff time by not having to have go back and forth with customers over email to explain processes and reasons for purchase requests. Additionally it will improve the customer's experience… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to Have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

10. Add eReceipts as an option in LX Starter.

    The only option for eReceipts is plain text. It would be a fantastic feature to customers to be able to build a nice HTML email for them.

    9 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  1 comment  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Statistics - Saved Queries Should Retain Cross-Tab Selections

    Saved Queries in the SDA should function the same as they do in SierraWeb.

    In the SDA:

    If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record), and you create a saved Cross-Tab query based on the same record type, then the selection of the two fields in the Cross-Tab Field Selection panel will be retained when switching to another bibliographic review file in Sierra SDA.

    If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record), and you create a saved Cross-Tab query based on a different record type (e.g. item record), then the selection of the two fields in the Cross-Tab Field Selection panel won't be retained when switching to another item review file in Sierra SDA. Very frustrating. Have to remember the criteria you used and toggle to those 2 inputs again.

    SierraWeb:

    However, in Sierra Web, the selection of the two fields is always retained, regardless of the first record type.

    Saved Queries in the SDA should function the same as they do in SierraWeb.

    In the SDA:

    If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record), and you create a saved Cross-Tab query based on the same record type, then the selection of the two fields in the Cross-Tab Field Selection panel will be retained when switching to another bibliographic review file in Sierra SDA.

    If the first review file with search results in Sierra Create Lists is based on a specific record type (e.g., bibliographic record),… more

    •  

    •  

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  0 comments  ·  Reporting & Analytics  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Lock Commands in Rapid Update

    When using the Rapid Update function to update individual item records, you can select a specific field (or fields) and values to update. After setting up your desired fields to update, you then scan the item barcode, hit Enter twice, and return to the point to scan the following barcode. We have had multiple instances where staff accidentally insert an additional field to change after scanning a barcode. One example is if they accidentally hit the space bar instead of the Enter key. It then defaults to the Copy# field. If there were a way to lock the selected Commands in place, this would prevent staff from inadvertently inputting additional commands and prevent the errors that occur.

    This enhancement would help eliminate unnecessary errors using the Rapid Update Individual Items function. It would save the time and frustration of having to backtrack and fix errors that may occur due to an incorrect command being entered by accident. It would also ensure that items retain valuable information, such as Itypes, which directly affect circulation.

    When using the Rapid Update function to update individual item records, you can select a specific field (or fields) and values to update. After setting up your desired fields to update, you then scan the item barcode, hit Enter twice, and return to the point to scan the following barcode. We have had multiple instances where staff accidentally insert an additional field to change after scanning a barcode. One example is if they accidentally hit the space bar instead of the Enter key. It then defaults to the Copy# field. If there were a way to lock the selected Commands… more

    13 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    4 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

    The product team will review this idea for consideration for a future release.

13. System Option to Disable Transit Slip Printing by Default

    In our library, all in-transit items are put into a single bin at the check-in location to be picked up and run through a central sorter which separates them by destination. This workflow doesn't require the use of transit slips, so our staff are trained to choose not to print one when prompted at check-in.

    Having to choose "no" at check-in for each item can become onerous when staff are checking in many items, but currently the only alternative is to have the system automatically print a transit slip for every item — which would simply be a waste of paper for us. We'd like to have a system option to NOT print a transit slip by default so staff can page through multiple pop-ups efficiently. Ideally, this option would be controllable by the library in case we need to temporarily re-enable transit slips, e.g. if the sorter goes down.

    In our library, all in-transit items are put into a single bin at the check-in location to be picked up and run through a central sorter which separates them by destination. This workflow doesn't require the use of transit slips, so our staff are trained to choose not to print one when prompted at check-in.

    Having to choose "no" at check-in for each item can become onerous when staff are checking in many items, but currently the only alternative is to have the system automatically print a transit slip for every item — which would simply be a waste of… more

    16 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

    The product team will review this idea for consideration for a future release.

14. Add "Volume" as an option in "New Record Templates" in Admin Settings.

    For volume records, it would be helpful to have 'volume' listed as an option in Admin - Settings - New Record Templates (see attachment). When adding volume records, it would be helpful to have the desired 'volume' template appear in the same way our item record template appears. Currently we have to always select the volume template we want to use. All the other options are listed and it would be nice to have 'volume' listed as well.

    • 

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  0 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Auto- Update library card expiration dates

    When a new library card is created in a month, Sierra auto-populates the expiration date for the card as next month +3 years, but this has to be manually adjusted every month by the Circ supervisor. It would be nice if Sierra could automatically set the expiration date for library cards created every month.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Circulation, Access Services & Fulfillment  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Make the "New PINs do not match" message configurable in PIN reset flow

    In the PIN reset workflow, when a user enters a new PIN and confirms it with a different value, the message “New PINs do not match” is displayed. Currently, this string does not appear to be configurable via the messages.conf or messages_lang.conf files, and cannot be localized.

    This limits our ability to fully support non-English users and ensure a consistent and accessible user experience across the system.

    Suggested improvement:
    Allow the “New PINs do not match” message to be configured through messages.conf, using a key such as RESETPINSDONTMATCH, or by extending the functionality of the existing REQPINSDONTMATCH key to also apply in the reset flow.

    This change would improve internationalization, accessibility, and consistency for all users, particularly in multilingual environments.

    In the PIN reset workflow, when a user enters a new PIN and confirms it with a different value, the message “New PINs do not match” is displayed. Currently, this string does not appear to be configurable via the messages.conf or messages_lang.conf files, and cannot be localized.

    This limits our ability to fully support non-English users and ensure a consistent and accessible user experience across the system.

    Suggested improvement:
    Allow the “New PINs do not match” message to be configured through messages.conf, using a key such as RESETPINSDONTMATCH, or by extending the functionality of the existing REQ… more

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  1 comment  ·  Discovery & OPAC  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Improve/Standardize Information Available When Viewing Holds

    Library staff would like to be able to see more details on holds that have been placed, including how the hold was placed (Sierra Desktop vs. SierraWeb vs. Web vs. mobile app, etc.) and who placed the hold (Sierra login if not the patron).

    Right now, it is not consistent how holds information is displayed.

    If you view holds w/in a patron record (holds tab), you don't see when the hold was placed or how they placed it. However, if you View Cancelled Holds, you see the date/time it was placed, along with the date/time it was cancelled, along with the title, barcode and importantly for staff, what login and program was used to cancel the hold.

    If you go outside of the patron record and go view the Bib and view the holds, you DO see the date/time it was placed. However, you don't see how it was placed or by whom. This is information that would be helpful, when there are questions about a hold.

    Ideally the information you'd see about a hold would be consistent no matter how you're viewing it - from the bib level hold, item-level hold or in the patron record /holds.

    I supposed this could also fall under "Customer Relationship & Account Management."

    Library staff would like to be able to see more details on holds that have been placed, including how the hold was placed (Sierra Desktop vs. SierraWeb vs. Web vs. mobile app, etc.) and who placed the hold (Sierra login if not the patron).

    Right now, it is not consistent how holds information is displayed.

    If you view holds w/in a patron record (holds tab), you don't see when the hold was placed or how they placed it. However, if you View Cancelled Holds, you see the date/time it was placed, along with the date/time it was cancelled, along with… more

    36 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    6 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

    The product team will review this idea for consideration for a future release.

18. Support SRU (Search/Retrieve by URL) in addition to Z39.50

    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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  0 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Send To: Globally Purge Charges

    It would be great if the logic & momentum that introduced Send To - Rapid or Global Update in Sierra 6.3 & will soon allow the same shortcut to Delete Items could also be applied to Globally Purge Charges.

    The state of Ohio has a statute of limitations on debt collection that has us purging money owed longer than 5 years on a weekly basis. While this is bazonkers IMO, apparently it's also the law of the land, & it would make the process much more quick & convenient if we could select a file in Create List, navigate to Tools - Send To in the Sierra top menu, & choose Globally Purge Charges (along with either Rapid & Global Update & Delete Records).

    It would be great if the logic & momentum that introduced Send To - Rapid or Global Update in Sierra 6.3 & will soon allow the same shortcut to Delete Items could also be applied to Globally Purge Charges.

    The state of Ohio has a statute of limitations on debt collection that has us purging money owed longer than 5 years on a weekly basis. While this is bazonkers IMO, apparently it's also the law of the land, & it would make the process much more quick & convenient if we could select a file in Create List, navigate to… more

    •  

    •  

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    UNDER REVIEW  ·  0 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Revamp the Hours Open Parameter

    The Situation: Our library's room checkout suddenly shorted to a hard limit of 6:00pm. I discovered that last year's spring break hours were listed in the Hours Open table and last year spring break occurred earlier in March.

    The Problem: Entries in the Hours Open table do not include the year. If the year was included, hour checkout issue wouldn't have been an issue.

    Solution #1: Add the ability to include the year to Hours Open table. Default to the current year but have the ability to change the year.

    Solution #2: Revamp the Hours Open table. Modifying the Hours Open using a table is antiquated. Reprogram the option to include a graphical date picker. Include repeat options like: every Wednesday, the first of the month, monthly, yearly, etc.

    The Situation: Our library's room checkout suddenly shorted to a hard limit of 6:00pm. I discovered that last year's spring break hours were listed in the Hours Open table and last year spring break occurred earlier in March.

    The Problem: Entries in the Hours Open table do not include the year. If the year was included, hour checkout issue wouldn't have been an issue.

    Solution #1: Add the ability to include the year to Hours Open table. Default to the current year but have the ability to change the year.

    Solution #2: Revamp the Hours Open table. Modifying the Hours… more

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to Have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    UNDER REVIEW  ·  AdminMike Dicus (Product Manager, Innovative) responded

    The product team will review this idea for consideration for a future release.