Methods and systems for managing data
View Patent ↗Systems and methods for managing data, such as metadata. In one exemplary method, metadata from files created by several different software applications are captured, and the captured metadata is searched. The type of information in metadata for one type of file differs from the type of information in metadata for another type of file. Other methods are described and data processing systems and machine readable media are also described.
1. A method, comprising:
storing, using one or more processing units, a plurality of data files and associated metadata objects, wherein the data files are associated with a plurality of applications within a system, wherein each metadata object includes a persistent identifier that uniquely identifies an associated data file, wherein each data file has a name, and wherein the persistent identifier remains the same when a file name is changed or when a data file is modified; and
receiving, using the one or more processing units, a notification associated with a data file, wherein the notification indicates deletion of an existing data file, creation of a new data file, or modification of an existing data file, wherein:
when the notification indicates deletion of an existing data file, a persistent identifier is used to identify an associated metadata object, and both the existing data file and the associated metadata object are deleted,
when the notification indicates creation of a new data file, a metadata object including a persistent identifier is generated and associated with the new data file, and one or more appropriate importers are determined based upon a file type of the new data file, wherein the one or more appropriate importers are used to import metadata from the associated data file, and
when the notification indicates modification of an existing data file, a persistent identifier is used to identify an associated metadata object, and one or more appropriate importers are determined based upon a file type of the existing data file, wherein the one or more appropriate importers are used to import metadata from the associated data file.
2. The method of claim 1 , wherein capture software exports a subset of the imported metadata to an application that created the data file.
3. The method of claim 1 , wherein capture software inserts a subset of the imported metadata into one or more blank fields maintained by an application that created the data file.
4. The method of claim 1 , wherein the associated metadata object is stored in a flat file format within a database.
5. A system, comprising:
one or more processors;
a computer-readable storage medium containing instructions configured to cause the one or more processors to perform operations, including:
storing a plurality of data files and associated metadata objects, wherein the data files are associated with a plurality of applications within a system, wherein each metadata object includes a persistent identifier that uniquely identifies an associated data file, wherein each data file has a name, and wherein the persistent identifier remains the same when a file name is changed or when a data file is modified; and
receiving a notification associated with a data file, wherein the notification indicates deletion of an existing data file, creation of a new data file, or modification of an existing data file, wherein:
when the notification indicates deletion of an existing data file, a persistent identifier is used to identify an associated metadata object, and both the existing data file and the associated metadata object are deleted,
when the notification indicates creation of a new data file, a metadata object including a persistent identifier is generated and associated with the new data file, and one or more appropriate importers are determined based upon a file type of the new data file, wherein the one or more appropriate importers are used to import metadata from the associated data file, and
when the notification indicates modification of an existing data file, a persistent identifier is used to identify an associated metadata object, and one or more appropriate importers are determined based upon a file type of the existing data file, wherein the one or more appropriate importers are used to import metadata from the associated data file.
6. The system of claim 5 , wherein capture software exports a subset of the imported metadata to an application that created the data file.
7. The system of claim 5 , wherein capture software inserts a subset of the imported metadata into one or more blank fields maintained by an application that created the data file.
8. The system of claim 5 , wherein the associated metadata object is stored in a flat file format within a database.
9. A computer-program product, tangibly embodied in a machine-readable storage medium, including instructions configured to cause a data processing apparatus to:
store a plurality of data files and associated metadata objects, wherein the data files are associated with a plurality of applications within a system, wherein each metadata object includes a persistent identifier that uniquely identifies an associated data file, wherein each data file has a name, and wherein the persistent identifier remains the same when a file name is changed or when a data file is modified; and
receive a notification associated with a data file, wherein the notification indicates deletion of an existing data file, creation of a new data file, or modification of an existing data file, wherein:
when the notification indicates deletion of an existing data file, a persistent identifier is used to identify an associated metadata object, and both the existing data file and the associated metadata object are deleted,
when the notification indicates creation of a new data file, a metadata object including a persistent identifier is generated and associated with the new data file, and one or more appropriate importers are determined based upon a file type of the new data file, wherein the one or more appropriate importers are used to import metadata from the associated data file, and
when the notification indicates modification of an existing data file, a persistent identifier is used to identify an associated metadata object, and one or more appropriate importers are determined based upon a file type of the existing data file, wherein the one or more appropriate importers are used to import metadata from the associated data file.
10. The computer-program product of claim 9 , wherein capture software exports a subset of the imported metadata to an application that created the data file.
11. The computer-program product of claim 9 , wherein capture software inserts a subset of the imported metadata into one or more blank fields maintained by an application that created the data file.
12. The computer-program product of claim 9 , wherein the associated metadata object is stored in a flat file format within a database.
13. A method, comprising:
storing, using one or more processing units, a plurality of data files and associated metadata objects, wherein the data files are associated with a plurality of applications within a system, wherein each metadata object includes a persistent identifier that uniquely identifies an associated data file, wherein each data file has a name, and wherein the persistent identifier remains the same when a file name is changed or when a data file is modified;
receiving, using the one or more processing units, a notification associated with a data file, wherein the notification indicates an action corresponding to the data file, and wherein the action is the deletion of an existing data file, the creation of a new data file, or the modification of an existing data file;
using, using the one or more processing units, the persistent identifier to identify an associated metadata object based upon the action;
determining, using the one or more processing units, one or more file types corresponding to the data file; and
determining, using the one or more processing units, one or more appropriate importers based upon the one or more file types corresponding to the data file when the action is the creation of a new data file or the modification of an existing file.
14. The method of claim 13 , wherein when the action is the deletion of an existing data file, the persistent identifier is used to identify a metadata object associated with the data file, and both the existing data file and the identified associated metadata object are deleted.
15. The method of claim 13 , wherein when the action is the creation of a new data file, a metadata object including a persistent identifier is generated and associated with the new data file, and the one or more appropriate importers are used to import metadata from the associated data file.
16. The method of claim 13 , wherein when the action is the modification of an existing data file, the persistent identifier is used to identify a metadata object associated with the data file, and the one or more appropriate importers are used to import metadata from the associated data file.
17. The method of claim 13 , wherein determining one or more appropriate importers includes selecting each importer based upon a determined file type.
18. The method of claim 13 , wherein capture software inserts a subset of the imported metadata into one or more blank fields maintained by an application that created the data file.
19. A system, comprising:
one or more processors;
a computer-readable storage medium containing instructions configured to cause the one or more processors to perform operations, including:
storing a plurality of data files and associated metadata objects, wherein the data files are associated with a plurality of applications within a system, wherein each metadata object includes a persistent identifier that uniquely identifies an associated data file, wherein each data file has a name, and wherein the persistent identifier remains the same when a file name is changed or when a data file is modified;
receiving a notification associated with a data file, wherein the notification indicates an action corresponding to the data file, and wherein the action is the deletion of an existing data file, the creation of a new data file, or the modification of an existing data file;
using the persistent identifier to identify an associated metadata object based upon the action;
determining one or more file types corresponding to the data file; and
determining one or more appropriate importers based upon the one or more file types corresponding to the data file when the action is the creation of a new data file or the modification of an existing file.
20. The system of claim 19 , wherein when the action is the deletion of an existing data file, the persistent identifier is used to identify a metadata object associated with the data file, and both the existing data file and the identified associated metadata object are deleted.
21. The system of claim 19 , wherein when the action is the creation of a new data file, a metadata object including a persistent identifier is generated and associated with the new data file, and the one or more appropriate importers are used to import metadata from the associated data file.
22. The system of claim 19 , wherein when the action is the modification of an existing data file, the persistent identifier is used to identify a metadata object associated with the data file, and the one or more appropriate importers are used to import metadata from the associated data file.
23. The system of claim 19 , wherein determining one or more appropriate importers includes selecting each importer based upon a determined file type.
24. The system of claim 19 , wherein capture software inserts a subset of the imported metadata into one or more blank fields maintained by an application that created the data file.
25. A computer-program product, tangibly embodied in a machine-readable storage medium, including instructions configured to cause a data processing apparatus to:
store a plurality of data files and associated metadata objects, wherein the data files are associated with a plurality of applications within a system, wherein each metadata object includes a persistent identifier that uniquely identifies an associated data file, wherein each data file has a name, and wherein the persistent identifier remains the same when a file name is changed or when a data file is modified;
receive a notification associated with a data file, wherein the notification indicates an action corresponding to the data file, and wherein the action is the deletion of an existing data file, the creation of a new data file, or the modification of an existing data file;
use the persistent identifier to identify an associated metadata object based upon the action;
determine one or more file types corresponding to the data file; and
determine one or more appropriate importers based upon the one or more file types corresponding to the data file when the action is the creation of a new data file or the modification of an existing file.
26. The computer-program product of claim 25 , wherein when the action is the deletion of an existing data file, the persistent identifier is used to identify a metadata object associated with the data file, and both the existing data file and the identified associated metadata object are deleted.
27. The computer-program product of claim 25 , wherein when the action is the creation of a new data file, a metadata object including a persistent identifier is generated and associated with the new data file, and the one or more appropriate importers are used to import metadata from the associated data file.
28. The computer-program product of claim 25 , wherein when the action is the modification of an existing data file, the persistent identifier is used to identify a metadata object associated with the data file, and the one or more appropriate importers are used to import metadata from the associated data file.
29. The computer-program product of claim 25 , wherein determining one or more appropriate importers includes selecting each importer based upon a determined file type.
30. The computer-program product of claim 25 , wherein capture software inserts a subset of the imported metadata into one or more blank fields maintained by an application that created the data file.