288 results found

1. Extend data retention of accounting transactions in SierraDNA

   The accounting transaction tables in SierraDNA allow you to query information you would normally only have access to via a retained posting register. However, it is hardcoded to only retain information for 2 weeks, which isn't enough time to do anything meaningful with that data.

   Ideally I'd like to see data for a full fiscal year but if there needs to be a limit for whatever reason, maybe tie it to the related payment history file.

   8 votes

   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

   3 comments  ·  Acquisitions, Serials & Inventory 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. 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

   43 votes

   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

   UNDER REVIEW  ·  4 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

3. Track User, Time, and Process for Deleted Records

   Currently, when a record is deleted in Sierra, the system captures the date via the deletiondategmt, but it doesn't track the exact time, the specific Sierra user, or the process used to delete it. We would like to see this metadata enhanced to include the Sierra user, a timestamp, and the function or process used (Delete Records, API, etc.), with the date.

   Tracking these details is critical for consortium management, system auditing, and data integrity. Having this information readily available would significantly improve our ability to handle targeted staff training when records are deleted in error, investigate the root cause of accidental bulk deletions, and maintain a clear, efficient audit trail.

   Currently, when a record is deleted in Sierra, the system captures the date via the deletiondategmt, but it doesn't track the exact time, the specific Sierra user, or the process used to delete it. We would like to see this metadata enhanced to include the Sierra user, a timestamp, and the function or process used (Delete Records, API, etc.), with the date.

   Tracking these details is critical for consortium management, system auditing, and data integrity. Having this information readily available would significantly improve our ability to handle targeted staff training when records are deleted in error, investigate the… more

   14 votes

   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

   UNDER REVIEW  ·  1 comment  ·  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

4. check in claimed returned workflow - item location should reflect where item was made claimed returned

   For libraries with floating collections, the branch where an item is marked Claimed Returned may not be reflected in the item record. This is because none of the three Claimed Returned options update the item's location.

   Example

   An item is checked out from Location A.

   The patron reports returning it to Location B, and staff mark it Claimed Returned at Location B.
   The item record still shows Location A.

   When marking an item Claimed Returned, staff have three options:

   1.Add a Claimed Returned note to both the item and patron records.
   2.Remove the checkout link between the patron and the item (equivalent to clearing the checkout without charging a fine). Staff can manually apply a charge if needed.
   3.Mark the item as Missing (Status = 'm') and cancel any outstanding holds.

   Important: In option 2, the item is not actually checked in. The system simply removes the connection between the patron and the item, so no check-in transaction occurs and the item's location is not updated.

   Why this matters

   Libraries with floating collections allow patrons to return items to any branch. If a patron returns an item to a different branch than where it was checked out and staff later mark it Claimed Returned, the item record continues to show the original checkout location. As a result, staff have no indication of the branch where the item was reportedly returned, making the item much more difficult to locate.

   For libraries with floating collections, the branch where an item is marked Claimed Returned may not be reflected in the item record. This is because none of the three Claimed Returned options update the item's location.

   Example

   An item is checked out from Location A.

   The patron reports returning it to Location B, and staff mark it Claimed Returned at Location B.
   The item record still shows Location A.

   When marking an item Claimed Returned, staff have three options:

   1.Add a Claimed Returned note to both the item and patron records.
   2.Remove the checkout link between the patron and the… more

   8 votes

   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

   UNDER REVIEW  ·  3 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

5. Overlay matching should evaluate all repeatable subfields (e.g., every $a in the 019), not just the first occurrence

   When a load table's overlay match point targets a repeatable field such as the 019 (OCLC number cross-reference), the load process only compares the first subfield occurrence against Sierra's index. Although Sierra correctly indexes every $a in the 019 individually, the overlay-match routine stops after the first $a. Any additional OCLC numbers stored in the second, third, or subsequent $a subfields are ignored when determining whether an incoming record should overlay an existing one.

   As a result, records that should match an existing bib overlay as new duplicates instead, because the matching value lives in a $a other than the first.

   Use case:
   OCLC regularly merges master records and moves superseded control numbers into the 019 field. A single existing bib may legitimately carry several OCLC numbers — one current number in the 035/001 and one or more prior numbers in repeating 019 $a subfields. When we receive an incoming record whose control number matches any of those values, we want it to overlay the existing record rather than create a duplicate. Today that only works if the match happens to fall on the first 019 $a.

   Libraries running lean cataloging operations — including those that have lost cataloger positions and rely more heavily on automated overlay logic — are especially exposed to the duplicate records this creates.

   Requested behavior:
   When an overlay match point (@ov_tag) references a repeatable field, the load process should iterate through all subfield occurrences of that field and test each against the corresponding Sierra index. A match on any occurrence should trigger overlay, consistent with how Sierra already indexes each occurrence.

   Impact if implemented:
   Fewer duplicate bib records, less manual dedup/cleanup, and overlay behavior that matches the indexing Sierra already performs — a meaningful gain for libraries with reduced cataloging staff.

   When a load table's overlay match point targets a repeatable field such as the 019 (OCLC number cross-reference), the load process only compares the first subfield occurrence against Sierra's index. Although Sierra correctly indexes every $a in the 019 individually, the overlay-match routine stops after the first $a. Any additional OCLC numbers stored in the second, third, or subsequent $a subfields are ignored when determining whether an incoming record should overlay an existing one.

   As a result, records that should match an existing bib overlay as new duplicates instead, because the matching value lives in a $a other than the… more

   9 votes

   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

   UNDER REVIEW  ·  2 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

6. Track Patron Renewal

   Please add the ability to report on patron record renewals. We currently use the Created Date field to track the number of new library cards issued. However, there is no reliable way to determine how many patron records have been renewed. While the Last Updated date changes whenever a patron record is modified, it is triggered by many different types of updates, making it impossible to distinguish renewals from routine record maintenance.

   Having the ability to track patron renewals would provide valuable statistics for monthly reporting to our Board of Control and Parish (County for the rest of you...) administration. It would be especially beneficial during Library Card Sign-Up Month in September, when libraries often report both new registrations and renewed library cards as measures of community engagement.

   Consider adding a field that records when the patron's Expiration Date is changed (for example, Expiration Date Last Changed) or another dedicated Renewal Date field. This would allow libraries to accurately identify and report patron renewals over any given date range without relying on unrelated record updates.

   Please add the ability to report on patron record renewals. We currently use the Created Date field to track the number of new library cards issued. However, there is no reliable way to determine how many patron records have been renewed. While the Last Updated date changes whenever a patron record is modified, it is triggered by many different types of updates, making it impossible to distinguish renewals from routine record maintenance.

   Having the ability to track patron renewals would provide valuable statistics for monthly reporting to our Board of Control and Parish (County for the rest of you...) administration.… more

   9 votes

   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  ·  Customer Relationship & Account 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

7. Automatically add date/timestamp to Notes and Messages

   It would be helpful if the system automatically added a date/timestamp to Notes and Messages added to Patron and Item records by staff. Currently, we ask our staff to always add thier initials and date to notes and messages when adding them but it doesn't always happen. There are also inconsistnecies in how these are added and no easy way to search for them. We also find that notes/messages are not always removed after they are addressed.

   If we had an accurate way to determine the date a note/message was added, it would be possible to develop a retention policy and procedures for record cleanup.

   I would like to see a system generated date/timestamp appended to each note/message which can also be searched so that you could search for Notes/Messages added to patron records before a certian date in order to identify Notes/Messages that could be cleaned up in Global update if they are no longer useful.

   It would be helpful if the system automatically added a date/timestamp to Notes and Messages added to Patron and Item records by staff. Currently, we ask our staff to always add thier initials and date to notes and messages when adding them but it doesn't always happen. There are also inconsistnecies in how these are added and no easy way to search for them. We also find that notes/messages are not always removed after they are addressed.

   If we had an accurate way to determine the date a note/message was added, it would be possible to develop a retention policy… more

   79 votes

   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

   8 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
   PLANNED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   Planned for the Sierra May 2027 release (v7.1)

8. Charge type on fines tab needs to specify if it is a damaged item

   We would like “replacement” changed to a term that reflects the actual item status. Currently, “replacement” is used for both long-overdue and damaged items that have been billed. To determine whether a billed item is damaged or simply overdue, staff must open the item record and check for a damage note.

   7 votes

   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

   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

9. Add ability to query empty review files to the reviewFiles API

   This idea is a bit of an addendum to Bob Gaydos' idea to create an endpoint that allows writing to review files (https://ideas.iii.com/forums/951745-ils-sierra/suggestions/50308716).

   The current API cannot provide a list of empty files. That information would be incredibly helpful in conjunction with the other idea so that you may programmatically identify an available review file of sufficient size for your needs. Beyond that, it may be useful to use the API to write an alert mechanism for when your system may be running low on available files.

   It is possible to explore this information via SQL, but the permissions are so much more granular with the APIs so there is an advantage to being able to set up an API key with access for these tasks that would not have access permissions for other more sensitive parts of the system.

   This idea is a bit of an addendum to Bob Gaydos' idea to create an endpoint that allows writing to review files (https://ideas.iii.com/forums/951745-ils-sierra/suggestions/50308716).

   The current API cannot provide a list of empty files. That information would be incredibly helpful in conjunction with the other idea so that you may programmatically identify an available review file of sufficient size for your needs. Beyond that, it may be useful to use the API to write an alert mechanism for when your system may be running low on available files.

   It is possible to explore this information via SQL, but the… more

   9 votes

   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

   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

10. Recycling Bin Feature for Clear Expired Holds & Holdshelf & Notices

    We will periodically have situations, as we did this morning, where staff move to print their holdshelf report & for one reason or another (today's was some manner of technical issues with their printer), the content of the report is lost.

    We can sometimes salvage this data from the back end by looking for holds cleared on the day by the login responsible, but it would be much easier if there were some sort of Recycling Bin style feature, where "cleared" files like the holdshelf report or paging lists were stored until the user logs out, giving them another chance to print them without the need to reach out to central support.

    We will periodically have situations, as we did this morning, where staff move to print their holdshelf report & for one reason or another (today's was some manner of technical issues with their printer), the content of the report is lost.

    We can sometimes salvage this data from the back end by looking for holds cleared on the day by the login responsible, but it would be much easier if there were some sort of Recycling Bin style feature, where "cleared" files like the holdshelf report or paging lists were stored until the user logs out, giving them another chance… more

    •  

    40 votes

    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

    UNDER REVIEW  ·  4 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

11. Allow Patrons to Opt-out of Certain Circulation Notices

    Many libraries offer mail delivery services for patrons who are unable to visit in person. Currently, when items become available, these patrons receive a standard "ready for pickup" notification, even though their materials will be mailed to them. This creates unnecessary confusion and may lead patrons to believe they need to come to the library.

    Providing the option to customize or opt out of specific notifications, such as "Ready for Pickup" alerts for patrons enrolled in mail delivery, would greatly improve clarity and enhance the user experience.

    12 votes

    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

    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

12. MARC Tags - Exporting

    When exporting MARC tags, export should have all the subfields marked. Now that I try to export say 041, I can´t see if the language code is in a, b or d... And this would be important to know as it is not the same to have say |a fin |h eng and |a fin |a eng.

    This is a re-share of an expired idea that seemed to garner some attention its first time around.

    8 votes

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

13. Allow Create Lists to sort and export the normalized best author and best title fields

    These two fields can be incorporated into searches performed within create lists but are not available among the fields that can be exported or used for sorting. Best title normalized is particularly helpful for data brought into a spreadsheet as the removal of special characters and diacritics can greatly improving sorts and searching.

    These fields are available via SQL, where I make frequent use of them, but for most of our users Create Lists is the only option for extracting data from the system.

    9 votes

    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

    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

14. Copy/paste multiple MARC fields simultaneously

    When creating a new record for a material, it's sometimes necessary to copy part, but not all, of an existing record. However, there is currently no way to copy/paste multiple MARC fields simultaneously, despite the fact that you can perform similar operations on multiple MARC fields simultaneously like deleting them. This would be especially helpful when needing to copy/paste 336, 337, and 338 as well as various subject fields.

    15 votes

    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

    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. Export RFID Pad Server Settings

    At my library, the installation of RFID equipment & the entry of the required IPs in Sierra are handled by two different departments. Typically, I'll see a ticket that a new PC/RFID pad has been added & receive a request that the IP be added to Sierra.

    In addition to the RFID Pad Server Settings table in Sierra, we maintain a separate spreadsheet of assigned IPs, machine names & information on when & whom the request came from to add or replace them.

    While adding & replacing more than 20 IPs this morning, it dawned on me that this process, or at least a periodic check to make sure that only valid/in use IPs are included in the table & that what's in the table matches other records that we keep (like that spreadsheet) would be improved if we could export what's in the table to more easily compare what's recorded elsewhere.

    At my library, the installation of RFID equipment & the entry of the required IPs in Sierra are handled by two different departments. Typically, I'll see a ticket that a new PC/RFID pad has been added & receive a request that the IP be added to Sierra.

    In addition to the RFID Pad Server Settings table in Sierra, we maintain a separate spreadsheet of assigned IPs, machine names & information on when & whom the request came from to add or replace them.

    While adding & replacing more than 20 IPs this morning, it dawned on me that this process,… more

    •  

    4 votes

    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

    2 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

16. Add ability to attach new volume from Serials Checkin function

    We'd like the ability to attach a volume record directly from the Serials Check-in module. Currently, because this functionality is not available within Serials Check-in, staff must rely on workarounds and switch to other functions to complete the task. Adding this capability would streamline workflows, save time, and make the Serials module more efficient and useful.

    6 votes

    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

    1 comment  ·  Acquisitions, Serials & Inventory 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

17. Customise font size and other details in Sierra pop-up messages

    We'd like the ability to customise the display of Sierra popup messages, specifically we'd like the ability to increase the font size for key information (for example, the pickup location or destination) so it stands out more clearly. We would also like the option to hide the call number, as it is not used by our library.

    7 votes

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

18. Automatically email Manage Holds results to library staff

    Have the results of Manage Holds automatically on a regular schedule (ie. each morning).

    This would let staff pick holds even if they don't have Sierra open or available. The automated emails could be set up within the Manage Holds function itself, or could be accomplished if Scheduler worked with Manage Holds (right now Scheduler only works with Create Lists and Data Exchange).

    6 votes

    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  ·  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. Add Export Options to Sierra

    There are various reports/files in Sierra that should be exportable to Excel or CSV for manipulation/analysis purposes, similar to our ability to export fines paid or statistical reports from the Statistics function. Candidates include Circulation Overrides (printable view puts each override on 2 lines) and other System Files (from admin app), Group Call Numbers (from Sierra 6.6), and really any sort of table or parameter that consists of columns/rows (branch table, patron type, etc.). This would save the effort of copying/pasting and attempting to fix in Excel.

    •  

    13 votes

    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

    UNDER REVIEW  ·  2 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

20. Send patron expiration date in SIP2 response

    Our library uses automated lockers to lend laptops to patrons for in-house use. We'd like to block patrons whose cards have expired from borrowing until they come to the desk and renew, while still allowing borrowing for patrons blocked for overdues since these items won't be leaving the library. Our vendor is able to accommodate this for other customers because their ILS sends the patron expiration date in the BW field in the 24 response. Sierra's response only indicates the block in the first position of the patron status element, which includes blocks for all reasons, not just account expiration. We would like Sierra to also send the expiration date in the 24 and 64 responses so we can distinguish expired accounts from other blocks.

    Our library uses automated lockers to lend laptops to patrons for in-house use. We'd like to block patrons whose cards have expired from borrowing until they come to the desk and renew, while still allowing borrowing for patrons blocked for overdues since these items won't be leaving the library. Our vendor is able to accommodate this for other customers because their ILS sends the patron expiration date in the BW field in the 24 response. Sierra's response only indicates the block in the first position of the patron status element, which includes blocks for all reasons, not just account expiration.… more

    8 votes

    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

    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