Determining file ownership of active and inactive files based on file access history

1. A non-transitory computer-readable storage medium having stored thereon computer-executable instructions that, when executed by a computer system, cause the computer system to perform a method, the method comprising:

identifying a first plurality of access events previously performed on a file, wherein said file is associated with a directory of related files;

identifying a second plurality of access events previously performed on said related files within said directory, wherein access events in said first and second plurality of access events occur within a time period;

determining a pool of users that have accessed the file and the related files within said directory within said time period;

determining a type of each of the first plurality of access events and the second plurality of access events, the type of each of the first plurality of access events indicating an operation performed on the file and the type of each of the second plurality of access events indicating an operation performed on the related files; and

selecting a user from said pool of users as an inferred owner of said file based on access metrics related to said first and second plurality of access events and the determined type of each of the first plurality of access events and the second plurality of access events.

2. The non-transitory computer-readable storage medium of claim 1 , further comprising:

determining whether the file is active or inactive based on the first plurality of access events, wherein when it is determined that the file is active, selecting the user comprises:

limiting relevant access events to said first plurality of access events;

filtering said pool of users to users accessing said file; and

selecting said user having the most accesses of said file within said time period.

3. The non-transitory computer-readable storage medium of claim 1 , further comprising:

determining whether the file is active or inactive based on the first plurality of access events, wherein when it is determined that the file is inactive, selecting the user comprises:

determining one or more related files that are active;

for each related file, determining a corresponding inferred owner having the most accesses, wherein a pool of related owners comprises one or more inferred owners of related files; and

selecting said user from said pool of related owners having the most accesses of said related files.

4. The non-transitory computer-readable storage medium of claim 3 , said method further comprising:

determining a file type for said file; and

filtering said related files by file type, wherein said pool of related owners comprises one or more corresponding inferred owners of related files comprising said file type.

5. The non-transitory computer-readable storage medium of claim 3 , said method further comprising:

determining a file type for said file;

determining a content grouping for said file, wherein said content grouping is associated with said file type; and

filtering said related files by said content grouping and said file type, wherein said pool of related owners comprises one or more corresponding inferred owners of related files comprising said file type and said content grouping.

6. The non-transitory computer-readable storage medium of claim 1 , said method further comprising:

weighting a first type of access event more than a second type of access event in said access metrics.

7. The non-transitory computer-readable storage medium of claim 1 , wherein the type of said first plurality of access events and the type of said second plurality of access events includes at least one of:

a read event;

a write event;

a delete event;

a rename event;

a copy event;

a create event; and

a configuration change event.

8. The non-transitory computer-readable storage medium of claim 1 , said method further comprising:

selecting a list of top users from said pool of users; and

presenting said list for selection of a user as said inferred owner.

9. A computer system comprising:

a processor; and

memory coupled to said processor and having stored therein instructions that, when executed by said computer system, causes said computer to execute a method, the method comprising:

identifying a first plurality of access events previously performed on a file, wherein said file is associated with a directory of related files;

identifying a second plurality of access events previously performed on said related files within said directory, wherein access events in said first and second plurality of access events occur within a time period;

determining a pool of users that have accessed the file and the related files within said directory within said time period;

determining a type of each of the first plurality of access events and the second plurality of access events, the type of each of the first plurality of access events indicating an operation performed on the file and the type of each of the second plurality of access events indicating an operation performed on the related files; and

selecting a user from said pool of users as an inferred owner of said file based on access metrics related to said first and second plurality of access events and the determined type of each of the first plurality of access events and the second plurality of access events.

10. The computer system of claim 9 , further comprising:

determining whether the file is active or inactive based on the first plurality of access events, wherein when it is determined that the file is active, selecting the user comprises:

limiting relevant access events to said first plurality of access events;

filtering said pool of users to users accessing said file; and

selecting said user having the most accesses of said file within said time period.

11. The computer system of claim 9 , further comprising:

determining whether the file is active or inactive based on the first plurality of access events, wherein when it is determined that the file is inactive, selecting the user comprises:

determining one or more related files that are active;

for each related file, determining a corresponding inferred owner having the most accesses, wherein a pool of related owners comprises one or more inferred owners of related files; and

selecting said user from said pool of related owners having the most accesses of said related files.

12. The computer system of claim 11 , said method further comprising:

determining a file type for said file; and

filtering said related files by said file type, wherein said pool of related owners comprises one or more corresponding inferred owners of related files comprising said file type.

13. The computer system of claim 11 , said method further comprising:

determining a file type for said file;

determining a content grouping for said file, wherein said content grouping is associated with said file type; and

filtering said related files by said content grouping and said file type, wherein said pool of related owners comprises one or more corresponding inferred owners of related files comprising said file type and said content grouping.

14. The computer system of claim 9 , said method further comprising:

weighting a first type of access event more than a second type of access event in said access metrics.

15. The computer system of claim 9 , wherein the type of said first plurality of access events and the type of said second plurality of access events includes at least one of:

a read event;

a write event;

a delete event;

a rename event;

a copy event;

a create event; and

a configuration change event.

16. The computer system of claim 9 , said method further comprising:

selecting a list of top users from said pool of users; and

presenting said list for selection of a user as said inferred owner.

17. A computer implemented method for file management, comprising:

identifying a first plurality of access events previously performed on a file, wherein said file is associated with a directory of related files;

identifying a second plurality of access events previously performed on said related files within said directory, wherein access events in said first and second plurality of access events occur within a time period;

determining a pool of users that have accessed the file and the related files within said directory within said time period;

determining a type of each of the first plurality of access events and the second plurality of access events, the type of each of the first plurality of access events indicating an operation performed on the file and the type of each of the second plurality of access events indicating an operation performed on the related files; and

selecting a user from said pool of users as an inferred owner of said file based on access metrics related to said first and second plurality of access events and the determined type of each of the first plurality of access events and the second plurality of access events.

18. The method of claim 17 , further comprising:

determining whether the file is active or inactive based on the first plurality of access events, wherein when it is determined that the file is active, selecting the user comprises:

limiting relevant access events to said first plurality of access events;

filtering said pool of users to users accessing said file; and

selecting said user having the most accesses of said file within said time period.

19. The method of claim 17 , further comprising:

determining whether the file is active or inactive based on the first plurality of access events, wherein when it is determined that the file is inactive, selecting the user comprises:

determining one or more related files that are active;

for each related file, determining a corresponding inferred owner having the most accesses, wherein a pool of related owners comprises one or more inferred owners of related files; and

selecting said user from said pool of related owners having the most accesses of said related files.

20. The method of claim 17 , further comprising:

determining a file type for said file; and

filtering said related files by said file type, wherein said pool of related owners comprises one or more corresponding inferred owners of related files comprising said file type.