Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Equipment Record Mass-Update Enhancement #1360

Open
UCDFeedbackBot opened this issue Jun 5, 2024 · 0 comments
Open

Equipment Record Mass-Update Enhancement #1360

UCDFeedbackBot opened this issue Jun 5, 2024 · 0 comments
Labels

Comments

@UCDFeedbackBot
Copy link

UCDFeedbackBot commented Jun 5, 2024

It can be common to queue equipment disposals to Surplus in large batches. However, noting that an item is disposed of in PEAKS is a manual task that must be done by modifying each individual equipment record. Currently, there is no way to perform any sort of mass update on existing equipment records in PEAKS. This can be a hassle when one sends, say, 50+ items to Aggie Surplus.

I propose that a mass-update feature be added, which would allow equipment managers to update multiple equipment records simultaneously. The proposed feature would allow users with the Equip Master or Departmental Admin roles to upload a .csv with rows containing equipment serial numbers and disposal dates; PEAKS would then iterate through the rows to modify each equipment record in the following manner:

Revoke any existing assignment
Add the tag value "Disposed"
Do something like adding "{newline} Sent to Surplus on %date%" to the Notes field

Ideally, the third item would not add a new string to the Notes field, but instead add a new Attribute entry with the “Disposal Date” key (see my previous enhancement request and date value pulled from the .csv.

Thanks much for considering this!


Votes: 2
Author: cfsiever
Voters: cfsiever,ez061101

@ucdavis ucdavis deleted a comment from UCDFeedbackBot Jun 6, 2024
@ucdavis ucdavis deleted a comment from UCDFeedbackBot Jun 6, 2024
@ucdavis ucdavis deleted a comment from UCDFeedbackBot Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant