Method and system for using file systems for content management
First Claim
Patent Images
1. A file system for a network attached storage arrangement, for creating and managing content, comprising:
- said file system being independent of an operating system residing on a computer;
a plurality of directories having base files containing data about which information is not known;
a repository of metadata separate from data in the base files, and containing identifying information about the data in the base files; and
phantom files comprising files containing collections of content segments in the form of pointers to segments within at least one of other files and phantom files, said phantom files designated by names and associated attributes without specifying a path name to the at least one of other files and phantom files, and said designations of names and associated attributes having been created by at least one user of the system.
9 Assignments
0 Petitions
Accused Products
Abstract
A file system and method serves to create and manage content. The file system includes at least one directory having at least one file containing data, but about which at least one file has no information. A repository of metadata provides information about the data in the files. Phantom files are created which are designated by names and associated attributes, point to data in base files, without specifying a path name to the base files.
-
Citations
21 Claims
-
1. A file system for a network attached storage arrangement, for creating and managing content, comprising:
-
said file system being independent of an operating system residing on a computer;
a plurality of directories having base files containing data about which information is not known;
a repository of metadata separate from data in the base files, and containing identifying information about the data in the base files; and
phantom files comprising files containing collections of content segments in the form of pointers to segments within at least one of other files and phantom files, said phantom files designated by names and associated attributes without specifying a path name to the at least one of other files and phantom files, and said designations of names and associated attributes having been created by at least one user of the system. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 21)
-
-
12. A method of managing content in an existing file system in a network attached storage arrangement, said file system being independent of an operating system running on a computer, and having a plurality of directories having base files containing data about which information is not known, the method comprising:
-
creating a repository of metadata separate from data in the base files, and containing identifying information about the data in the base files; and
creating phantom files comprising files containing collections of content segments in the form of pointers to segments within at least one base of other files and phantom files, and designating the phantom files with names and associated attributes without specifying a path name to the base files, with said designation of names and associated attributes being created by at least one user of the system. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20)
manually defining contents in base files through the use of said interface;
checking for inconsistencies in the content; and
storing all the attributes of the existing content along with location of the content in a repository.
-
-
17. The method of claim 12, wherein said creation of phantom files is conducted by at least one of:
-
splitting an existing file along content boundaries;
combining contents of an existing file into a phantom file;
splitting or combining contents of phantom files;
defining a filter to work on content;
mirroring an existing file; and
versioning an existing file.
-
-
18. The method of claim 12, for comprising defining the attributes of class, type, subtype, size and name for each file created.
-
19. The method of claim 12 further comprising locking a base file or a phantom file from users when one user is operating on the base file or phantom file.
-
20. The method of claim 12, wherein the phantom files point to segments of data from base files, with said segments of data defined for use by users accessing the phantom files.
Specification