Settings and activity
130 results found
-
30 votes
Nicole Turzillo
supported this idea
·
-
27 votesNicole Turzillo
supported this idea
·
-
8 votesNicole Turzillo
supported this idea
·
-
25 votesNicole Turzillo
supported this idea
·
An error occurred while saving the comment -
42 votesNicole Turzillo
supported this idea
·
-
44 votesNicole Turzillo
supported this idea
·
-
19 votes
An error occurred while saving the comment Nicole Turzillo
commented
We currently use various test sites for homepage, custom header, and footer testing. Patrons should not be able to select "Turzillo" as the default catalog, but I still need access to this Collection Site for testing.
A proposed solution is to add a Public/Private toggle when creating Collection Sites or Kiosks. Marking a site as "Private" would automatically hide and suppress it from all patron-facing areas.
Nicole Turzillo
supported this idea
·
-
20 votesNicole Turzillo
supported this idea
·
-
28 votesNicole Turzillo
supported this idea
·
-
56 votesNicole Turzillo
supported this idea
·
-
48 votes
An error occurred while saving the comment Nicole Turzillo
commented
Vega Discover currently lacks username support, restricting account flexibility for roughly 60,000 active patrons who rely on this feature.
Nicole Turzillo
supported this idea
·
-
23 votesNicole Turzillo
supported this idea
·
-
18 votesNicole Turzillo
supported this idea
·
-
25 votesNicole Turzillo
supported this idea
·
-
15 votesNicole Turzillo
shared this idea
·
An error occurred while saving the comment Nicole Turzillo
commented
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.
-
13 votesNicole Turzillo
shared this idea
·
-
31 votesNicole Turzillo
supported this idea
·
-
12 votesNicole Turzillo
shared this idea
·
-
26 votesNicole Turzillo
supported this idea
·
-
57 votesNicole Turzillo
supported this idea
·
In Sierra's invoicing function, when selecting an order record already paid, a pop-up box appears with a warning message stating, "ITEM ALREADY PAID FOR." Currently, the only option available is to click "OK," which immediately proceeds to the next step of entering the item's price on that paid order record. However, adding a button labeled "CANCEL" in the warning pop-up box would be beneficial to prevent staff from inadvertently continuing to pay for the item on the wrong record. Clicking "CANCEL" should close the warning pop-up without proceeding further, returning the user to the search results list. The "CANCEL" option prevents inadvertent payments on the wrong order records, reducing errors in fund allocation and duplicate payments. It improves the user experience for all staff members, especially those new to invoicing, by providing a clear option to cancel erroneous actions. Staff members could correct their mistakes immediately, reducing the likelihood of paying for items on the wrong record. It saves time and effort that would otherwise be spent rectifying mistakes, such as reversing payments. Enhances overall efficiency in invoicing, contributing to smoother operations in a multi-branch library environment with numerous fund codes and multiple copies of items.