Look at it from this way, its probably more work to go back and delete entries that really don't take up much disk. Heck, collecting is easy, setting up periodic purges, archives, and such, usually gets pushed to another phase.... which may never come.
another side is, its both good and bad. You can see patterns and alert to changes. You could also use it to prove someone wasn't where others claim and so on. If your really creative you can mine it and try to figure out why so many students are making trips that take time and minimize it to put more time to learning than traveling. Like we route packages in shipping companies, load the truck properly for the route, get students into a route that minimizes travel from class to class
>setting up periodic purges, archives, and such, usually gets pushed to another phase.... which may never come.
Isn't that where security compliance programs come into play? I think someone doing their due diligence in asking, "What is the business justification for storing building access logs indefinitely" would have been able to create a procedure for addressing the storage of these types of things.
another side is, its both good and bad. You can see patterns and alert to changes. You could also use it to prove someone wasn't where others claim and so on. If your really creative you can mine it and try to figure out why so many students are making trips that take time and minimize it to put more time to learning than traveling. Like we route packages in shipping companies, load the truck properly for the route, get students into a route that minimizes travel from class to class