NicoleLCoonen
commented
3 years ago Part 1 is halfway done. updateDB.php now resets an accessory's Device_Connection to 0 when a Release box is checked on updateForm.php. The next step is to create a report that pulls all accessories with a Device_Connection of 0 and add the recall functionality to that report. Also, the graveyard table now has the "Origin_Table" field, so I can take the next steps on part 3. Admittedly have not touched tablets yet.
This is more of a To Do list than one specific issue, but it all has to do with managing the stuff that used to fall through the cracks: monitors, tablets, External Drives and the like. These could each be their own issue, but it'll make more sense to me to keep them together in one issue that gets updated.
Periphery reassignment: I want to prevent office peripheries from being attached to public computers and make sure their user stays up-to-date, so the periphery will probably go into an available pool where an admin can perform reassignment rather than simply changing the Device Connection the way computers change their Port Connection.
Tablet reassignment: since these devices are inherently wireless, all admin will be done from the reports.php page and be based on assigned user. They will not appear on the map.
Graveyard integration: Since all devices in long-term storage will live under the same roof, I'll need a way to make sure they're added back to the correct table if they get recalled. I'm also distinguishing devices that are available and ready-to-go from those in long-term storage which may need updates, repairs, or reconfiguration before they can be useful.