25 results found

1. Sierra 6.2 - Bulk Item level holds on same bib record

   Often times when items are moving from one call number to another, holds are placed on the items that are checked out in order to capture these items when they are returned so that any cataloging work can be done.

   The idea is to have an option to have some way that multiple item level holds can be placed on one bib record at the same time.

   Idea Value
   The value of this idea is staff time. By having to place individual holds on each item, this can take a long time when there are multiple copies of an item that needs to have a hold placed.

   Often times when items are moving from one call number to another, holds are placed on the items that are checked out in order to capture these items when they are returned so that any cataloging work can be done.

   The idea is to have an option to have some way that multiple item level holds can be placed on one bib record at the same time.

   Idea Value
   The value of this idea is staff time. By having to place individual holds on each item, this can take a long time when there are multiple copies of an item… more

   34 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  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This idea has been included in Sierra 6.2.

2. Sierra 6.1 - Protect Global Updates on Server from accidental overwrite

   In the Global Update function, "File" > "Save (Server)" should prompt the user to confirm if they attempt to overwrite an existing search.

   Write-protection of specific saved global updates on the sever would provide additional assurance against data loss for very important/complex items.

   Idea Value
   This would mitigate the risk of accidental data loss due to user error. Sophisticated searches may be saved to the server, the loss of which may require substantial work to recreate accurately.

   As of Sierra 5.4, if a user working with an unsaved session accidentally selects "Save (Sever)" rather than "Load (Sever)", the "Save as..." dialog appears. If an existing update file is selected, it will be overwritten without a confirmation prompt.

   This behaviour makes sense after a set of saved parameters have been loaded but appears to be problematic at the start of a global update session.

   In particular, if the user makes this error immediately after accessing Global Update, the saved search is overwritten with a blank search (ask me how I know!); and in general, because Sierra does not prompt to confirm overwrite of a saved global update with an empty one having no parameters, it is easy to wipe out existing saves.

   The SDA UI could also potentially be tweaked to mitigate risk of this error by changing the order of entries in the "File" menu.

   Current state (grouped by Local/Sever, with "Save (Server)" and "Load (Server)" adjacent):Save (Local)Load (Local)Save (Sever)Load (Sever)Save as (Sever)

   Proposed state (grouped by Load/Save with separator between them):Load (Local)Load (Sever)-----------------Save (Local)Save (Sever)Save as (Sever)

   In the Global Update function, "File" > "Save (Server)" should prompt the user to confirm if they attempt to overwrite an existing search.

   Write-protection of specific saved global updates on the sever would provide additional assurance against data loss for very important/complex items.

   Idea Value
   This would mitigate the risk of accidental data loss due to user error. Sophisticated searches may be saved to the server, the loss of which may require substantial work to recreate accurately.

   As of Sierra 5.4, if a user working with an unsaved session accidentally selects "Save (Sever)" rather than "Load (Sever)", the "Save as..."… more

   17 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 →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   This feature has been included in Sierra 6.1.

3. Sierra 6.3 - Backup Load Profiles using Sierra Desktop Put PC, don't require FTP

   Even if III isn't able to provide a full-fledged editing interface for Load Profiles, add a mode in which we can view Load Profiles and Put PC to back them up. That's so much easier than having to setup FTP to the site, which our IT prohibited when I first gave up on it. This should apply to both m2btabs and m2bmaps.

   Idea Value
   Make it possible to backup load profiles on PC, which would enable much easier documentation of the variety of load tables and maps, and the load profile menu.

   23 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  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   Implemented in Sierra 6.3

4. Sierra 6.3 - Reduce time for Patron record payment lock

   The patron record payment lock time should be reduced or have the ability to be overridden. Four hours is an excessive amount of time for a record to be locked. If a patron record is open for more than, say, 15 minutes (or even 5 minutes), the other session is probably not in the midst of making a payment.

   Idea Value
   Patron record locks are unexpected and embarrassing for staff that encounter them when the patron is in front of them wanting to pay or have a fine, fee, or other charge paid or waived. The patron is confused and possibly angry that staff not only cannot help them immediately, they cannot help them for hours. Even under the best circumstances, staff have to add a tickler for themselves to come back to the account, often the next day.

   The patron record payment lock time should be reduced or have the ability to be overridden. Four hours is an excessive amount of time for a record to be locked. If a patron record is open for more than, say, 15 minutes (or even 5 minutes), the other session is probably not in the midst of making a payment.

   Idea Value
   Patron record locks are unexpected and embarrassing for staff that encounter them when the patron is in front of them wanting to pay or have a fine, fee, or other charge paid or waived. The patron is confused and… more

   37 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

   5 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   Implemented in Sierra 6.3

5. Sierra 6.3 - Better Load Table Editing Platform

   The Load Tables are a critical point for any data management of a library. While many functions and features have been migrated from character-based system access to web access or within the SDA, this feature has not changed. Programming with what seems like a unix-based editor reminds me of the "dark ages" of programming.

   Idea Value
   Many times the syntactical error or omission of a line in my load table editing sessions happen because of the UNIX-like environment where editing takes place. Increased modernization of the editor would streamline the process.

   33 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  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →
   COMPLETED  ·  AdminMike Dicus (Product Manager, Innovative) responded

   Implemented in Sierra 6.3