FORM 2
THE PATENTS ACT, 1970 (39 of 1970)
& THE PATENTS RULES, 2003
COMPLETE SPECIFICATION
[See section 10, Rule 13]
A METHOD AND SYSTEM FOR DIRECTORY MANAGEMENT;


LIMITED, A COMPANY INCORPORATED IN MARCH 1999 UNDER THE COMPANIES ACT,
THE INFORMATION COMPANY PRIVATE 1956, HAVING REGISTERED ADDRESS, ROW
HOUSE 6, OM DWARKANATH SOCIETY, SECTOR 19A, NERUL, NAVI MUMBAI 400706, INDIARAUL6442
THE FOLLOWING SPECIFICATION
PARTICULARLY DESCRIBES THE INVENTION AND THE MANNER IN WHICH IT IS TO BE performed

FIELD OF INVENTION
The present invention relates to the management of files and folders in a computer or network of computers, the enhancement of directory management systems, for example, of (but not restricted to) Microsoft Windows Explorer, and of directory management systems in various operating systems used on computers and networks of computers.
BACKGROUND ART
The information in computers (and hence in networks of computers) is stored in the storage devices of the computers, in the form of hard disks, floppy disks, tape drives, USB drives and other such storage devices. The information is physically stored in digital form {for example, in hard disks, information is stored in different ^clusters' or areas of the devices), and cannot be seen by the user. To enable the user to retrieve information, the operating systems of computers use a method and system variously called a file management system or directory management system, which on the Microsoft Windows platform, for example, is called the Windows Explorer, and is known by various other names in various non-Microsoft systems, which we will hereinafter refer to as a "directory management system".
The directory management system helps users organize their files into folders, which can be divided into sub-folders, and sub-sub-folders, up to several lower levels, and all these are contained in 'partitions' (also known as 'directories') of the computer hard disk (or other storage device), and a computer may have one or more hard disks or other storage devices. The
2

directories are usually structured in hierarchical form, or in 'tree' structures.
The directory management structure enables users to perform various actions on the files that contain information or computer instructions - including: create, name, rename, open, copy, paste, move and delete, besides sorting the file and folder lists by different columns (e.g., alphabetically by file name, by last modification date, by file size, by file format) to make it easier to find a file or folder. The directory structure is replicated in *browse' windows that open in individual applications on the computer (e.g., MS Word, or Adobe Photoshop) when a user wishes to locate a file to open or to save a file. The file lists in the directories may also show previews of images or the first slide of a presentation or animation in a *thumbnail' size.
However, the functionality of the directory management system ends there. Among the limitations of the Windows Explorer, for example, is the fact that the user can only see the lists of sub-folders or files in a folder one folder at a time.
Some software products have been launched in the recent past, which enhance the display properties of the directory management system by allowing users to open more than one pane in a single window to see the contents of several folders at the same time. Some products also now allow users to display the contents of several folders in one single 'flat' list. However, neither the original Microsoft Windows Explorer nor the other systems that seek to enhance the display properties of Windows Explorer, or of other directory management systems on operating platforms such as Linux, enable users to see a
3

description of the contents of the files or their characteristics without opening the files.
Currently only audio and video players have a very primitive system of tagging, which manifests itself in the form of "play lists". These function essentially as lists of selected files that a user may wish to play at a time, and resemble batch files that can be run at a single command. Microsoft uses an XML file to store such play lists. Users have no means to manage the tags, or to arrange them in a hierarchy for easier management.
Operating systems also store metadata, that is, data about data (for example, when a file was created or modified and by who, the size of the file, the number of words or characters used, the file format, and so on) . Microsoft Windows, for example, uses a method known as file handling to store such data.
OBJECT OF THE INVENTION:
The object of the present invention is to provide a method and system for managing the information contents of a computer or network of computers through an enhancement of the power of the directory management system by enabling users to superimpose a hierarchy of tags on top of the directory management system, to share, import and export the hierarchy of tags between computers. The method is defined particularly for selecting individual references from search engine result lists and saving them along with bookmarks, labels and comments. The system automatically generate reports of work done in the computer or network of computers, including creation, modification, copying, moving and deletion of files

and folders. The method and system reduces the clutter of information while ensuring that the system is automatically backed up in different modes and with complete flexibility to back up.
BRIEF DESCRIPTION OF THE DRAWINGS:
Reference will be made to embodiments of the invention, examples of which may be illustrated in the accompanying figures. These figures are intended to be illustrative, not limiting. Although the invention is generally described in the context of these embodiments, it should be understood that it is not intended to limit the scope of the invention to these particular embodiments.
Figure 1 gives a bird's eye-view of the process, in which 101 describes the application embodying the method and system of the current invention.
Figure 2 describes the modules of the application, including managing files and folders 201, synchronization 202 (details in figures 14 and 15), backup 203 (figures 16 to 20), report generation 204 (details in figure 21), and managing descriptors 205 (details in figures 22 and 23).
Figure 3 describes how to get a display of files, folders, emails, and attached comments and descriptors.
Figure 4 shows how, the user is enabled to see previews of certain types of files.
Figure 5 indicates that the details of the selected items, including metadata and descriptors along with a preview of the files or folders in the side panel; if the number
5

exceeds the limit, the application displays only the list of files and folders in the side panel 505, without metadata, descriptors or preview.
Figure 6 explains the process of attaching/detaching labels to files, folders and emails.
Figure 7 explains the process of attaching/detaching bookmarks to files, folders and emails.
Figure 8 explains the process of attaching/detaching priorities to files, folders and emails.
Figure 9 explains the process of attaching/detaching groups to files, folders and emails.
Figure 10 explains the process of writing, reading and deleting comments to files, folders and emails.
Figure 11 explains the process of finding duplicates.
Figure 12 illustrates the process of e-mailing selected files or folders as attachments.
Figure 13 explains the process of printing data directly or in Excel/CSV format.
Figure 14 explains the process of synchronization, which helps users synchronize their descriptors as well as their files and folders.
Figure 15 continues from decision box 1403 where option "No" (meaning select sync both ways) leads to 1501.
Figure 16 explains the process of backup and restore.
Figure 17 explains the process of full backup.
6

Figure 18 represents the case of incremental backup.
Figure 19 explains the process of application database back up.
Figure 20 shows the process of restoring the data created within the application in case of a hard disk crash or re¬installation of the application, or when a user wishes to revert to an earlier state of the data.
Figure 21 represents the process of ^report' generation, which logs all actions taken in pre-determined areas of the system, including creation, modification, renaming, moving, and deleting files and folders.
Figure 22 shows the ^descriptor management' process. The user can export descriptors 2201 or import descriptors 2202 {details in figure 23).
Figure 23 continues with the ^descriptor management' process at the receiver end, where the user can select 2301 one of several imported XML files containing hierarchies of descriptors, and get a display of a "tree view" of the descriptor hierarchy 2302.
Figure 24 explains the option of "limiting the network authorization of the application" to the machines on which it is installed so that the user organization can retain control of how the application is used within its local network.
BRIEF DESCRIPTION OF INVENTION:
The current invention, herewith "Organyze", may increase the power of the directory management system by adding several
7

functionalities, which currently may not be available in other systems, in order to help the user manage his files and folders better, streamline work and work more productively by being able to see detailed descriptions of the contents of files or their properties {for example, has an image file been purchased, and what are the terms of the purchase? Or has a report document been approved by the department head? Or has this file been forwarded to a colleague, and what are her comments on the charts in the file?).
The present invention, i.e., Organyze, may be able to build this power by using an SQL database-driven method and system, which may provide a wide range of ways in which to enhance directory management systems and also may give users considerable flexibility in such use. It may use "descriptors" of various kinds, including bookmarks (indicating relevance or importance)/ labels (describing the content), priorities (specifying the urgency or level of importance of the file, folder or email), groups (indicating the group in the organization for whom the file or folder would be of interest), and comments {multiple comments by one or more persons stating their views on the contents or other characteristics of the file) .
Not only can an individual user create and attach descriptors to his files and folders, the user can import hierarchies of descriptors from other users. Thus, for example, a user organization can create a central labeling system, which, say, follows a standard industrial classification system; then the user can import such a central labeling system and use elements of it in his own personal labeling system. A user who has developed an effective labeling system can export it to
8

others in the organization on request, allowing more people to use the system created by someone who is more expert than them or has devoted more time to it than they have.
The present invention, i.e., Organyze, has also configured backup and synchronization processes in such a way that the descriptors may be maintained in the database, and can be restored even if the user's hard disk crashes or gets corrupted. In other words, not only do the files and folders get backed up, but so also do the descriptors and their links to the files and folders. This method and system may be different from other backup and synchronization methods and systems as it maintains copies of files and folders, plus a mapping of the paths of the files and folders in the directory system, and the links between the descriptors and the paths {which manifest themselves as ^attachments' to the files and folders).
The present invention, i.e., Organyze, may enable users to get reports of activity in their systems, in terms of files or folders created, modified, opened, renamed, moved, deleted, helping them in two ways - one, refreshing their memories about the files they had worked on, say, a week ago, and thus helping them retrieve files more easily; and two, allowing designated and authorized persons in the organization to see the work done by others on their machines in the local network.
Described herein are the various embodiments of the present invention, Organyze, which includes a method and a system for managing the information contents of a computer or network of computers through an enhancement of the power of the directory management system by enabling users to superimpose hierarchies
9

of descriptors on top of the directory management system, to share, import and export the hierarchies of descriptors between computers, a method and system for automatically generating reports of work done in the system, including creation, modification and deletion of files and folders in one or more machines, and methods and systems of management to synchronize files and folders between machines and to automatically back up information in different modes and with complete flexibility to back up different sections of the information in different places - on the same machine, on other machines, or at an external site, and in different configurations of types of formats to be back up and the numbers of versions to be retained, and including the various hierarchies of descriptors as well as files and folders and the database that stores the application data.
An exemplary embodiment of the present invention may be illustrated in the accompanying figures. These figures are intended to be illustrative, not limiting. Although the invention is generally described in the context of these embodiments, it should be understood that it is not intended to limit the scope of the invention to these particular embodiments.
Figure 1 gives a bird's eye-view of the process, in which 101 describes the application embodying the method and system of the current invention. The application uses an SQL database 102, and applies to an email management system 103 and the directory management system 104, both of which work with the help of the operating system 105 used to run the computer. The application is used by users of individual computers 107 or networks of computer users 106,
10

and can be used to transfer information to remotely situated computers or networks of computers 109 through a file transfer protocol 108, with the option of limiting the authorization of the application in the network 110 to restrict the use of the application to the machine on which it is installed (details in figure 24).
Figure 2 describes the modules of the application, including managing files and folders 201, synchronization 202 (details in figures 14 and 15), backup 203 (figures 16 to 20), report generation 204 (details in figure 21), and managing descriptors 205 (details in figures 22 and 23) . The file and folder management is done by generating displays (details in figure 3), of the list of contents of one or more folders, including flat, cross-folder, cross-directory, cross-drive, cross-computer lists 206 of files, folders and emails or calling the lists in a Windows Explorer (or similar) 207 pane in the same window, and enhancing the usability of such lists by enabling users to see file previews 208 (details in figure 4) and file details 209 (details in figure 5), attach/detach labels 210 (details in figure 6) , attach/detach bookmarks 211 (details in figure 7) , attach/detach priorities 212 (details in figure 8), attach/detach groups 213 (details in figure 9), write/read/delete comments 214 (details in figure 10) , find duplicate files 215 (details in figure 11), forward or email selected files or folders as attachments 216 (details in figure 12), and print or export 217 (details in figure 13) the lists of files and folders to a spreadsheet or comma separated value (CSV) or similar spreadsheet-readable file, or in a word-processor, PDF or other such file, along with the paths of the files and folders in order to help
11

users to separately maintain lists for sorting, commenting or other (e.g., 'housekeeping' ) purposes.
Figure 3 describes how to get a display of cross-folder, cross-directory, cross-drive, cross-computer lists 'A' of files, folders and emails through browsing and selecting 301, by choosing folder paths 305, one or more folders in one or more directories or drives or computers, and displaying the lists of files in the selected folders and, if desired, files or folders with comments 302 attached, or selecting bookmarks, priorities, groups or labels 303, or emails 304, selecting filters 306 in the case of files, folders and comments, selecting the option 307 whether to do a keyword search 308, verifying 309 whether the process involves emails and displaying flat lists of the results as email lists 311.
While selecting the folders and sub-folders from one or more folders, directories, drives or computers, the application offers the choice 310 of displaying only the folders or only the files in the selected folders. In case the user opts to see display of folders, the application also offers the choice 312 of including all sub-folders and sub-sub-folders or only displaying the list of sub-folders in the root of the selected folder, and then displaying a list 313 of all the selected folders and sub-folders in them, or displaying a list 314 of only the root of the selected folders. Similarly, if the user opts to see the display of a list of files in the selection, the application offers the choice 315 to display 316 the complete list of files in all the sub-folders inside the
12

selected folders, or display 317 only the files in the roots of the selected folders.
Figure 4 shows how, on getting the list of files or folders in the display, as a result of the process described in the previous paragraph, the user is enabled to see previews of certain types of files, for which the application checks 401 whether the file is of a certain format amenable to previewing; if it is not, it indicates 403 the inability to display a preview; if it is amenable, then it checks 402 whether the format is an image or animation, in which case, it displays 404 a preview of the image or the first slide/frame of the animation; otherwise, it checks 405 if the format is a text, PDF or other similar format; if it is, it displays the first 300 characters of the contents of the file; if for any reason it cannot do so, it displays 403 a message indicating inability to display a preview.
Figure 5 indicates that when the user selects 501 one or more files or folders in the list of files or folders displayed, the details of that file or folder, including its meta data, such as file size, format, dates of creation and modification, etc. are displayed in a panel on the side, along with descriptor information added by the user, including bookmark, priority, group, labels and comments. The application checks 502 if the number of items selected is one or more than one; if it is one, it displays the details 503, including metadata and descriptors, along with a preview of the file. Alternatively, the application checks 504 if the number of items selected is up to a certain (preferably small) limit, and if it is, it displays 503 the details of the selected items, including metadata
13

and descriptors along with a preview of the files or folders in the side panel; if the number exceeds the limit, the application displays only the list of files and folders in the side panel 505, without metadata, descriptors or preview. The user can then opt 506 to click on one of the items in the panel to expand its details in the side panel 507, or opt to see the details {including metadata, descriptors and previews) of all the selected files or folders in a new window 508.
Figure 6 explains the process of attaching/detaching labels to files, folders and emails. It requires the user to select 601 one or more files., folders or emails displayed in the list acquired as described in the figures above, and then decide 602 to attach a label by selecting a label from a hierarchy of labels already created by the user or by a central administrator or imported by the user from another user; the user can check 603 if a desired label does or does not exist in the available hierarchy of labels, and may create a new label or import one through the method of managing labels 604 explained below in the method to manage descriptors of various types. When the user selects 605 a label to "attach" it to the selected files, folders or emails, the application checks 606 whether the selection is an email or not; if it is an email, then it gets the unique ID 608 of the email and stores it 609 along with the label ID in the database; if the selection is a folder or file, it gets their paths 607, then checks 610 whether the selection is one or more folders or files, and then stores 611 & 612 the folder or file path and the label ID in the database. Conversely, if the user chooses to detach 613 a label from a selection of files, folders or emails, he
14

selects 614 the label, and the application removes the selected entries from the database.
Figure 7 explains the process of attaching/detaching bookmarks to files, folders and emails. It requires the user to select 701 one or more files, folders or emails displayed in the list acquired as described in the figures above, and then opt to bookmark it 702; then the application checks 703 whether the selection is an email or not; if it is an email, then it gets the unique ID 704 of the email and stores it 706 in the database; if the selection is one or more folders or files, it gets their paths 705, then checks 707 whether the selection is a folder or file, and then stores 708 & 709 the folder or file path in the database. Conversely, if the user chooses to detach (un-bookmark) 710 a selection of files, folders or emails, the application removes 711 the selected entries from the database.
Figure 8 explains the process of attaching/detaching priorities to files, folders and emails. Priorities are means of specifying the urgency or level of importance of files, folders or emails, and could be displayed as numbers or colors or by textual description; in an organization, there could be centrally- or departmentally-determined priorities and individual user-determined priorities. The process requires the user to select 801 one or more files, folders or emails displayed in the list acquired as described in the figures above, and then opt to attach 802 a priority by selecting a priority tag from a list of priorities already created by the user or by a central or departmental administrator or imported by the user from
15

another user; if the user wishes 803 to attach a priority that does not exist in the available list of priorities, then he may create a new priority or import one through the method of managing priorities 804 (explained below in the method to manage descriptors of various types in figures 22 and 23} .
When the user selects 805 a priority to "attach" it to the selected files, folders or emails, the application checks 806 whether the selection is an email or not; if it is an email, then it gets the unique ID 808 of the email and stores it 809 along with the priority ID in the database; if the selection is one or more folders or files, it gets their paths 807, then checks 810 whether the selection is a folder or file, and then stores 811 & 812 the folder or file paths and the priority ID in the database. Conversely, if the user chooses to detach 813 a priority from a selection of files, folders or emails, he selects 814 the relevant priority tag, and the application removes the selected entries from the database.
Figure 9 explains the process of attaching/detaching groups to files, folders and emails. The group descriptor names the group (e.g., finance, or marketing or logistics departments, or informal groups, such as employees interested in community welfare or sports activities) in the organization for whom the file or folder would be of interest. It requires the user to select 901 one or more files, folders or emails displayed in the list acquired as described in the figures above, and then opt to attach 902 a group by selecting a group tag from a hierarchy of groups already created by the user or by a central administrator
16

or imported by the user from another user; the user can check 903 a desired group does or does not exist in the available hierarchy of groups, then he may create a new group or import one through the method of managing group 904 explained below in the method to manage descriptors of various types (explained below in the method to manage descriptors of various types in figures 22 and 23) .
When the user selects 905 a group to "attach" it to the selected files, folders or emails, the application checks 906 whether the selection is an email or not; if it is an email, then it gets the unique ID 908 of the email and stores it 909 along with the group ID in the database; if the selection is one or more folders or files, it gets their paths 907, then checks 910 whether the selection is a folder or file, and then stores 911 & 912 the folder or file path and the group ID in the database. Conversely, if the user chooses the detach 913 a group from a selection of files, folders or emails, he selects 914 the relevant group tag, and the application removes 915 the selected entries from the database.
Figure 10 explains the process of writing, reading and deleting comments to files, folders and emails. It requires the user to select 1001 one or more files, folders or emails displayed in the list acquired as described in the figures above, and then writing 1002 a comment in a space provided by the application, which then inputs 1003 the comment data in a table, checks 1004 whether the selection is emails or folders and files; if it is an email, then it gets 1005 the unique ID of the email and stores 1007 the unique ID and the comment in the database; if it is folders
17

or files, then it gets 1006 the folder or file paths, and, after checking 1008 whether it is folders or files, stores the folder or file paths 1009 & 1010 in the database along with the comment. If the user wishes to delete a comment 1011, he selects 1012 the comment, and the application removes 1013 the comment from the database or disables the display of the comment. If the user wishes to read 1014 a comment, he selects 1001 the folder, file or email from the displayed list and the application gets 1015 the comment from the database, and displays 1016 the comment for the user to see.
Figure 11 explains the process of finding duplicates. 1101 checks if the listed item is a file, if yes, it checks file size 1103. If not (that is, for example, if it is a folder) it does not do any comparison 1102. If the file sizes are the same, it checks if the formats too are the same 1104. If the formats are the same, then it compares the bytes (contents) in the similar-sized and similar-format files 1106. If the file bytes (contents of the files) are the same 1107, it marks them as duplicates 1108 or else 'not duplicate' 1109 is displayed. If the file formats are not the same 1104 or size not same 1103, there is no possibility of duplication 1105.
Figure 12 illustrates the process of e-mailing selected files or folders as attachments. If it is not a file 1201, i.e., it is a folder; the application sends it in a compressed (e.g. *zip'} format 1202. Alternatively, if it is a file, the user has the option 1203 to compress 1204 or not to compress the selection before e-mailing it 1205 with or without compressing.
18

Figure 13 explains the process of printing data directly or in Excel/CSV format. 1301 allows the user to print directly in the displayed format; 1302 allows the user to export it in Excel/CSV format (including list of files and folder path) 1303, and print 1304 or save 1305 in the selected format.
Figure 14 explains the process of synchronization, which helps users synchronize their descriptors as well as their files and folders. It requires the user to select 1401 source folder, and then 1402 destination folder. The user must specify if he wants synchronization 1403 to occur one¬way (only from the user's machine to another machine) or both ways (explained in figure 15). If the user selects one-way, he has an option 14 04 to sync or not sync selected formats (viz. document file, excel file etc). If the option is chosen to sync/not sync selected formats 1404, the user has the option to choose at least one or more formats 1406 to sync or choose at least one or more formats to not sync 1407. Alternatively, the program will sync all formats 1405.
Figure 15 continues from decision box 14 03 where option "No" (meaning select sync both ways) leads to 1501. The user has the option 1501 to sync or not sync selected formats (viz. document file, excel file etc). If the option is chosen to sync/not sync selected formats 1503, the user has the option to choose at least one or more formats 1504 to sync or choose at least one or more formats to not sync 1507. Alternatively, the program will sync all formats 1502.
19

Figure 16 explains the process of backup and restore. The user has the option to select folder and file backup 1601, application database backup 1602 (details in figure 19) and application data restore 1603 (details in figure 20) . The folder and file backup 1601 gives the user the option of managing the backup 1604 and run backup 1608. Managing backup can be done in two ways - by adding a backup list 1605 (by which the user selects the folders that need to be backed up) and editing the backup list 1606. If for any reason backup does not happen, the user will get a backup error report 1607. Running backup can be done in two ways -by running manual backup 1609 and running an automatic backup 1610. In case of manual backup, the user can select 1613 a configured backup list to go for full backup or incremental backup (details in figures 17 and 18). If the user selects automatic backup 1610 the application gets configured list from the database to begin at scheduled time 1612 to run full or incremental backup 1613.
Figure 16 explains the process of backup and restore. The user has the option of backing up selected files and folders in a compressed (zipped) format or backing them up in their original, uncompressed format 1701. If the compress option is selected the application creates a folder with the current date 1702 and send it to the destination 1703. Alternatively, the application uses the original format to create a folder with the current date and time 1704 and copy all files and folders to the destination 1705. The application checks if the backup is configured for the user's machine, in an external device, in another machine in the local network, or to a remote location. If the backup location is a remote storage device
20

170 6, the application gets the relevant FTP (file transfer
protocol} information from the database 1707 to make an FTP
connection and upload the backed-up data 1708. For either
destination choice - local or remote - the application
checks the number of backup copies 1709, and deletes the
oldest version if the number of backup copies exceeds the
configuration.
Figure 18 represents the case of incremental backup. The application checks 1801 whether a fil§ already exists and is already fully updated; if it is, then the application does not replace it 1802; if (as when the user creates a new file or modifies an existing file after the last backup}, the application copies or replaces the file 1805, after copying the existing backup file to a "backup version folder" 1804 if the user has configured the folder in which the original file is located for versioning 1803. The application checks 1806 whether the backup location is a remote storage device; if it is, the application gets FTP information 1807 from the database to create an FTP connection to the remote server and upload back up data 1808. In both cases (backing up locally or in remote location} the application checks the desired number of back copies, and if the number reached with the latest backup exceeds that number, then it deletes the oldest version 1809.
Figure 19 explains the process of application database back up. The user can run a manual backup 1901 or an automatic backup 1902; for the manual backup, the user can select the destination path 1903. In case of automatic backup 1902, the application gets a configured list from the database
21

and begins backup at a scheduled time 1904. In both cases (manual and automatic), the backup data is stored in an XML file 1905.
Figure 20 shows the process of restoring the data created within the application {e.g., backup and other configurations, file paths, reports, labels, bookmarks, groups, etc) in case of a hard disk crash or re¬installation of the application, or when a user wishes to revert to an earlier state of the data. Assuming that the user has backed up the data in a place other than the application folder, preferably on another disk or machine, the user can select 2001 the backup file, which is in XML format; then, if the application finds 2002 application data in the database, it deletes this existing data 2003 and enters 2004 data from the XML file in the application database, which it does even when it does not find existing application data in the application database.
In case of renaming of the partitions of the drives in the process of replacement of crashed drives or as a result of upgrading to new drives, if the application finds 2005 a mismatch between stored file/folder paths attached to descriptors and actual locations of folders/files, then it displays 2006 the stored paths in a dialog box, allowing the user to modify 2007 the paths. When the user selects and modifies a root path saved in the database, all child/subordinate paths get automatically modified to match the change. The application then restarts 2008, which it also does when it does not find a mismatch between the stored paths of descriptors and the actual locations of the folders/files.
22

Figure 21 represents the process of report' generation, which logs all actions taken in pre-determined areas of the system, including creation, modification, renaming, moving, and deleting files and folders. The user can determine the sources (machines, drives, directories, folders, etc.) 2101 in relation to which reports should be generated, and can see a "ticker" 2102 continuously displaying the actions in the selected sources as they happen, or directly view a viewable, exportable and printable report 2103.
To add sources 2101, the user can select the folder path 2104 and save the source 2105. The ticker 2102 option continuously alerts the user as 2106 files are modified, renamed, moved or deleted in a ticker window 2107. To view reports 2103, the user can select 2108 the sources for which reports are required, and criteria for reporting (e.g., modified or deleted files, or renamed folders, etc.) 2109 and the date range for the report's coverage 2110. If the user selects one or more file types 2111, the report will show only the selected file types 2112, or else it will display reports related to all files in the selection 2113.
Figure 22 shows the 'descriptor management' process. The user can export descriptors 2201 or import descriptors 22 02 (details in figure 23). If the user chooses to export descriptors, he can select a destination path 2203; then the application fetches the descriptors from the database 2204, and generates an XML file containing the hierarchy of descriptors 2205 at the destination.
Figure 2 3 continues with the descriptor management' process at the receiver end, where the user can select 2301
23

one of several imported XML files containing hierarchies of descriptors, and get a display of a "tree view" of the descriptor hierarchy 2302. The user has the option of dragging and dropping 2303 or selecting and transferring the desired descriptors 2304 to his own hierarchy of descriptors. In both cases, the application checks 2305 whether a descriptor already exists at the same hierarchical level in the user's system; if it does, the application will not copy the descriptor 2306, else it will copy the descriptor 2307.
Figure 24 explains the option of "limiting the network authorization of the application" to the machines on which it is installed so that the user organization can retain control of how the application is used within its local network. The authorization limitation method works in such a way that, for example, in managing files and folders 2401, the application checks 2404 whether it has limited network authorization; if it is limited, then the user can only access files and folders on machines other than his own but not attach descriptors to them 2405; if it is not, he can attach descriptors to files and folders on other machines 2406 which the application is authorized to include.
Similarly, for the purpose of backup 2402, the application checks 2407 whether it has limited network authorization; if it is limited, then the user can back up from his local machine to network machines but cannot back up files or folders residing in other machines 2408; if it is not, he can back up files or folders residing in other machines 2409.
24

Similarly, for the purpose of generating reports 2403, the application checks 2410 whether it has limited network authorization; if it is limited, then the user can generate reports only from his local machine and not from other machines 2411, if it is not, he can generate reports related to files or folders residing in other machines 2412.