There may be many reasons why you can suddenly find yourself faced with investigating tens of thousands of files.
Whatever the reason, you need an effective approach for getting your head around the mass of documents, and get to grip with what is important - your work. And you need to do that quickly.
Generally, there are three important approaches for initially investigating this data:
This article deals with the first of these approaches, with the other approaches being explored in subsequent articles. There will be a quick summary regarding each approach, and the reason why you would want to slice the data in these ways.
Additional articles will then explore the specific needs when investigating:
Data contained within a Windows system does not exist in a vacuum. Each document has been created, either by a user or a computer program, and has been stored in a specific location with a specific file name as a specific file type.
Generally, each user has their own methodology of why they save in the directories that they do. When working as a part of a team, there may be a shared methodology created, but often it is either not followed, or people’s interpretations of what it means can vary.
Part of the problem occurs when multiple people work on a project, as one person's file management may be quite different from another’s, and others may save their data in locations which you don't know about.
The problem is multiplied when people have their own individual workspaces (such as a unique "My Documents" folder), and then multiple versions of files are then saved in multiple locations. Also, users may be less systematic about directory structure methodology when they feel they are saving in "their" space, instead of in a communal system.
Therefore, when confronted with a mass of data for the first time, understanding what the filing structure is, and its rationale, is a must. Only then can you identify what might be important for you, and what documents should be investigated further.
Unfortunately, whilst it is relatively easy to navigate in Windows Explorer, it is not as useful for investigating filing structures for the first time.
Therefore, Windows Explorer, though a generally useful tool in navigating to specific folders and seeing the files in that folder, may not be best way to initially investigate new data.
In my experience, to avoid the above problems the best way is to have some way to export the filing structure out of Windows Explorer, so you can avoid the limitations therein. Ideally, you want it in a program in a structured format, so that you can:
Ideally, you would also want something that:
To solve these problems, we created the Filecats range of programs. You can export the names of files and folders from Windows Explorer to either Microsoft Excel or a standalone table with just a few clicks.
Whenever I receive files from an external source, on a memory stick or hard drive, the first thing I do is to create a catalog, so I can get my head around the data. It doesn’t take long, it saves me so much time, and I can become productive faster.
There is a free 7-day trial available, so you can see how much time you can save. Why not download it today?
The next in this series of articles looks at examining your new data, and seeing what files types are available.