47 results found
-
Add "permanent location" field in item record and function to change to it
We have shelves for new materials, and item location codes for these ("new mysteries," "new fiction," "new DVDs," and lots more). Moving items from the new shelves to the regular shelves is a chore, both in handling materials and in knowing (and selecting) what location to change them to. It would be great if you could just get into a function in Sierra that would change the current item location (the "new" one in my example) to the permanent item location (a new field that would be added with this idea, which would catalogers would populate when the item was…
3 votes -
Create a pop-up when you are about to overwrite a review file in create lists.
It is very easy to accidentally overwrite a review file in create lists. There should be a pop-up that asks if you want to overwrite the file so that you know you're doing it.
4 votes -
Include authorities in the Search/Holds module
It'd be great if authority records and cross references were included under the Search/Holds module and be the same as what staff encounter with the Catalog module. Right now it is different. In our system, staff often use Sierra to place holds with the public on their behalf. It would be great if authorities were available in the Search/Holds module results display so that staff could benefit from the information.
If a staffer did an author search and they had a pen name (Robb, J.D.) then they'd be redirected to see the other author's name (Roberts, Nora).... Or they may…7 votes -
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.
5 votes -
TODAY Command
Similar to the keyboard codes (ex. %ENTER%), it would be useful to have a command code for today's date. In item records, we input the current date in a 995 field using a macro but must update our date macro each day. Being able to have a command for the current date would save time and lead to fewer errors when users forget to change the date.
2 votesThe product team will review this idea for consideration for a future release.
-
Record History for bib records does not capture elevated credentials
Currently the Record History report for Bib Records in Sierra contains a list of record changes, the login that made a change, and when it was changed.
However, if the change to a bib record was attempted with a login without the required permissions, Sierra will ask for a login with elevated permissions and allow the user make a change once logged in. In this case, the Record history will record the first login (without required permissions), instead of the elevated login needed to make the change.
Problem: Record History report for Bib Records Record History report for Bib Records…
5 votesThe product team will review this idea for consideration for a future release.
-
Add multiple items to a review file from the Item Summary page
It's great to be able to add a single item to a review file from the item record page. It would be even better if we could add multiple items from the item summary page.
6 votesThe product team will review this idea for consideration for a future release.
-
Passing the UPC Code
When an item lacks an ISBN in the 020 field (DVDs and CDs only generally have UPCs in the 024 field) the cover image is very much hit or miss. Syndetics has been contacted, however, it appears that Sierra needs to "pass the UPC code” in order for this to work. This addition would be helpful.
13 votesThe product team will review this idea for consideration for a future release.
-
Add an Option to restrict Bibliographic Records within the Sierra System ( specific permission)
Problem:
In the current version of the Sierra system, restricted or sensitive bibliographic records can only be suppressed from the public catalog but remain visible and accessible to catalogers within the system. This visibility creates the risk of accidental editing, publishing, or mishandling of these records, particularly:- Restricted Records: Some records are sensitive or confidential and should not be visible to all catalogers.
Records Under Review: Records undergoing auditing or verification need protection from edits until the review is completed.
Recommendation:
Introduce a feature that allows the System Administrator or Cataloging Supervisor to hide specific bibliographic records within the Sierra…
10 votesThe product team will review this idea for consideration for a future release.
-
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…
13 votesThe product team will review this idea for consideration for a future release.
-
Persistent Column Resizing in Summary Tab
Persistent Column Resizing in Summary Tab:
Currently, users can resize columns in the Summary Tab (Orders, Items, and Holdings) during a session. However, these adjustments are not retained after the session ends, requiring users to reapply their preferred column sizes each time they log in.
I propose an enhancement to allow users to permanently save column resizing preferences across sessions. This feature would greatly improve usability and efficiency by enabling a more customized and consistent interface tailored to individual workflows.
This enhancement would benefit users who frequently manage data within the Summary Tab by reducing repetitive actions and ensuring a…
7 votesThe product team will review this idea for consideration for a future release.
-
Fix "Tile Vertically" so the bottom of the records don't get hidden behind the taskbar on Windows 11.
In Sierra, on Windows 11, when you click "Tile Vertically" so you can see multiple records at the same time, it makes the windows too long, so that the bottom of the windows get hidden behind the taskbar if it is locked. It does not do this if you maximize a record window, or if you use snap. It only seems to be the "Tile Vertically" function.
We use this function a lot to compare records for deduplication, and it is really annoying to have to manually resize windows so you can see the whole thing.
16 votesThe product team will review this idea for consideration for a future release.
-
Limit ISBN matching to 13 digits
When matching on an ISBN for record loading, it should be possible to limit the match to the first 13 (or 10) digits. There are often extraneous data in 020 subfield |a. There are now other subfields where that is supposed to go, but it frequently ends up in |a anyway, and then your record loading won't match.
7 votesThe product team will review this idea for consideration for a future release.
-
Improve diacritics in sierra to search Arabic and other Semitic langauges
Improve diacritic searching in Sierra to include Semitic languages, especially Arabic! We have a fair number of Arabic books in out collections, and a large Arabic community, but Sierra support for Arabic characters does not seem complete. We often find that Arabic letters in Sierra is replaced by a white square, which seems to mean that the character is not supported. The names appear fine in Vega but the non supported letters do not seem to be indexed in the search results. This is an important language for members of our community and support for it is important in our…
7 votesThe product team will review this idea for consideration for a future release.
-
Add ability to suppress a subfield in the 1xx
Add the ability to suppress subfield 1 in the 1xx field so it will not show in Sierra. This way it can be unsuppressed when the library starts using linked data.
18 votesThe product team will review this idea for consideration for a future release.
-
Move to Bottom of Group - use marc field instead of field name
Our catalogers would like the option when choosing a field and selecting "Move to Bottom of Group" that it could go to the bottom of the list of numbered tags it is part of instead of the field name of tags. An example is moving a 5xx field to the bottom of a list of other 5xx fields, and not to the bottom of the record if there is an 852 (also a note) field.
10 votesThe product team will review this idea for consideration for a future release.
-
OAI-PMH service - suppressed records
As a default suppressed records are not included in the harvest stream. This becomes an issue when a harvested record later becomes suppressed in Sierra as the harvester does not know to remove it from its listings as its omission from the stream does not allow for identification of its suppressed state. I would recommend that the option to include suppressed records should be configurable as a harvest stream level, giving the library the ability to configure the inclusion/exclusion dependent on their business rules.
9 votesThe product team will review this idea for consideration for a future release.
-
Don't allow Scheduler to save passwords it can't use
I just learned that Scheduler Output MARC records can't send an FTP password that includes the characters [{}"/
It will let me save a task with such a password and spend months trying to figure out what's wrong. If it can't deal with a particular password, it should give an error saying what's wrong with the password.
8 votesThe product team will review this idea for consideration for a future release.
-
Increase Max Size of Item Code 1 Field
The Item Code 1 field was going to solve all my statistical issues. I thought it had 5 characters and each character could be 0-9 which meant I could assign a meaning to each character. For example, the first character indicates agency (1 for CPL, 2 for ADL, 3 for BKM) and the second character indicates audience (1 for adult, 2 for young adult, 3 for juvenile, 4 for other) and the third character, format, etc. HOWEVER it turns out that the largest number this field can hold is 32767 which is weirdly random and very limiting when you want…
6 votesThe product team will review this idea for consideration for a future release.
-
Make it possible to search for records lacking a MARC field in Create Lists
I recently wanted to run a search for all records that matched certain criteria and did not have an 856 field. However, Create Lists does not currently have a "lacks field" option. It would be very helpful to be able to search for records that do not have certain fields.
21 votesThe product team will review this idea for consideration for a future release.
- Don't see your idea?