Universal content traceability
First Claim
1. A method implemented in a non-transitory machine-readable storage medium and processed by one or more processors configured to perform the method, comprising:
- identifying a piece of content;
assigning one or more content identifiers to the piece of content;
generating a unique instance identifier for the piece of content, the unique instance identifier unique to a particular copy of the piece of content and the one or more content identifiers are assigned to all copies of the piece of content, the unique instance identifier constructed based on a pathname for the particular copy of the piece of content and the pathname including an inode for the particular copy of the piece of content;
providing content metadata and instance metadata to the piece of content; and
recording the one or more content identifiers, the instance identifier, the content metadata, and the instance metadata in a database for subsequent traceability of the piece of content, wherein a total number of backlinks for any given piece of content is used for ranking that given piece of content, and when an imported different piece of content from an external system is detected performing a search and identifying a percentage of content matches for search results from the search as ancestors for the different piece of content, each ancestor identified as an unconfirmed ancestor to the different piece of content.
8 Assignments
0 Petitions
Accused Products
Abstract
Techniques for universal content traceability are presented. A piece of content is tagged with one or more content identifiers and with a unique instance identifier. The content also is tagged with content and instance-level metadata. The tagged information is maintained with the document and separately from the document in a centralized or distributed database system or table. As operations are performed on the content, the tagged information may be updated as necessary. The content can then use the tagged information in connection with the database to trace its origins and history during its lifecycle.
-
Citations
20 Claims
-
1. A method implemented in a non-transitory machine-readable storage medium and processed by one or more processors configured to perform the method, comprising:
-
identifying a piece of content; assigning one or more content identifiers to the piece of content; generating a unique instance identifier for the piece of content, the unique instance identifier unique to a particular copy of the piece of content and the one or more content identifiers are assigned to all copies of the piece of content, the unique instance identifier constructed based on a pathname for the particular copy of the piece of content and the pathname including an inode for the particular copy of the piece of content; providing content metadata and instance metadata to the piece of content; and recording the one or more content identifiers, the instance identifier, the content metadata, and the instance metadata in a database for subsequent traceability of the piece of content, wherein a total number of backlinks for any given piece of content is used for ranking that given piece of content, and when an imported different piece of content from an external system is detected performing a search and identifying a percentage of content matches for search results from the search as ancestors for the different piece of content, each ancestor identified as an unconfirmed ancestor to the different piece of content. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A method implemented in a non-transitory machine-readable storage medium and processed by one or more processors configured to perform the method, comprising:
-
presenting a content traceability interface to a user; receiving, via the interface and from the user, a file having a piece of content; resolving one or more content identifiers and a unique instance identifier for the piece of content having a particular inode, and wherein resolving further includes identifying when the file is received as an imported file from an external system and performing a search identifying a percentage of file matches for search results from the search as ancestors for the imported file, each ancestor identified as an unconfirmed ancestor to the imported file; accessing a database using the one or more content identifiers and the instance identifier; and providing, via the interface, one or more tracing maps for the piece of content to the user and automatically creating a versioning system for the piece of content based on the unique instance identifier, and wherein each piece of content is ranked based at least in part on a total number of backlinks associated with that piece of content. - View Dependent Claims (12, 13, 14, 15, 16, 17)
-
-
18. A multi-processor implemented system, comprising:
-
a server machine having multiple processors; and the server machine configured with and to execute a server agent and to interact with one or more client agents executing on one or more client machines; the server agent configured to interact with each client agent to supply each piece of content being manipulated on a particular client machine with one or more content identifiers, a unique instance identifier, content metadata, and instance metadata, and the server agent further configured to maintain a database to link the content identifiers and instance identifiers to other pieces of content managed in the database to create traceability for content using inodes of the identifiers and pathnames for the identifiers, the instance identifiers used for automatically creating a versioning system for each piece of content, each piece of content is ranked based at least in part on a total number of backlinks associated with that piece of content, and wherein the server agent further configured to search an external system when a particular piece of content is identified as an imported piece of content to identify a percentage of content matches for search results from the search as ancestors for the imported piece of content, each ancestor identified as an unconfirmed ancestor to the imported piece of content. - View Dependent Claims (19, 20)
-
Specification