Settings and activity
203 results found
-
25 votes
Nicole Turzillo
supported this idea
·
-
13 votesNicole Turzillo
shared this idea
·
An error occurred while saving the comment -
11 votesNicole Turzillo
shared this idea
·
-
25 votesNicole Turzillo
supported this idea
·
-
8 votesNicole Turzillo
shared this idea
·
-
24 votesNicole Turzillo
supported this idea
·
-
54 votesNicole Turzillo
supported this idea
·
-
5 votesNicole Turzillo
supported this idea
·
-
51 votes
An error occurred while saving the comment Nicole Turzillo
commented
This is a high-priority request for our libraries. Because the system does not ingest and display traditional order records, we urgently need a mechanism to show that an item is on order and available for patrons to place on hold.
Nicole Turzillo
supported this idea
·
-
20 votesNicole Turzillo
supported this idea
·
-
23 votesNicole Turzillo
supported this idea
·
-
19 votesNicole Turzillo
supported this idea
·
-
18 votesNicole Turzillo
supported this idea
·
-
12 votesNicole Turzillo
supported this idea
·
-
26 votes
An error occurred while saving the comment Nicole Turzillo
commented
Since we use shared logins, we would love to see 'session-based' accessibility toggles. This would allow a staff member to enable high contrast or font scaling for their shift without permanently changing the default display for everyone else.
Nicole Turzillo
supported this idea
·
-
30 votes
An error occurred while saving the comment Nicole Turzillo
commented
This would be a massive quality-of-life improvement. We frequently encounter issues where the holdshelf is cleared for the entire county—an error that occurs far more often than it should. Only a few System Admins can technically retrieve this data; they aren't always available, especially when these errors occur on weekends. Having this accessible at the staff level would reduce a lot of Saturday-morning stress.
Nicole Turzillo
supported this idea
·
-
12 votesNicole Turzillo
supported this idea
·
-
24 votesNicole Turzillo
shared this idea
·
-
47 votesNicole Turzillo
supported this idea
·
-
25 votesNicole Turzillo
supported this idea
·
Currently, when a record is deleted in Sierra, the system captures the date via the deletion_date_gmt, 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.