Determining trusted file awareness via loosely connected events and file attributes
US-2024364713-A1 · Oct 31, 2024 · US
US10296596B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10296596-B2 |
| Application number | US-201113384465-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 26, 2011 |
| Priority date | May 27, 2010 |
| Publication date | May 21, 2019 |
| Grant date | May 21, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for characterizing data elements in an enterprise including ascertaining at least one of an access metric and a data identifier for each of a plurality of data elements and employing the at least one of an access metric and a data identifier to automatically apply a metatag to ones of the plurality of data elements.
Opening claim text (preview).
The invention claimed is: 1. A method for characterizing data elements, each of said data elements being accessible to users of an enterprise computer network in accordance with access permissions explicitly assigned by an assigned owner thereof, said method comprising: continuously maintaining a database of said access permissions explicitly assigned by said assigned owner; continuously maintaining a database of data identifiers associated with said plurality of data elements; specifying, by an administrator, at least one access permission explicitly assigned by said assigned owner and at least one data identifier; ascertaining which of said plurality of said data elements have both said at least one access permission explicitly assigned by said assigned owner and said at least one data identifier associated therewith; specifying, by an administrator, administrator defined metatags to be associated with each of said data elements ascertained to have both said at least one access permission explicitly assigned by said assigned owner and said at least one data identifier associated therewith; automatically applying a metatag from among said administrator defined metatags to ones of said plurality of data elements ascertained to have said at least one access permission explicitly assigned by said assigned owner and said at least one specific data identifier associated therewith; ascertaining an assigned owner for each one of said plurality of data elements ascertained to have said at least one access permission explicitly assigned by said assigned owner and said at least one data identifier associated therewith, said assigned owner having authority and accountability with respect to said one data element within said enterprise; and requiring said assigned owner to review and validate said metatags automatically applied to said ones of said plurality of data elements owned thereby. 2. The method for characterizing data elements in an enterprise according to claim 1 and wherein said automatically applying a metatag comprises automatically applying specific ones of a plurality of different metatags to specific ones of said plurality of data elements. 3. The method for characterizing data elements in an enterprise according to claim 1 and wherein said automatically applying a metatag comprises automatically applying to each one of said plurality of data elements a metatag previously applied to a parent folder thereof. 4. The method for characterizing data elements in an enterprise according to claim 1 and wherein said data identifier is one of file type, author, category and language. 5. The method for characterizing data elements in an enterprise according to claim 1 and wherein said automatically applying a metatag comprises automatically applying a metatag to ones of said plurality of data elements. 6. A system having a computer comprising a processor, a memory and a non-transitory, tangible computer-readable medium in which computer program instructions are stored, which instructions, when executed by said processor, cause the computer to characterize data elements, each of said data elements being accessible to users of an enterprise computer network in accordance with access permissions explicitly assigned by an assigned owner thereof, said system comprising: access metrics collection functionality operative to collect said access permissions explicitly assigned by said assigned owner thereof; metadata collection functionality operative to collect data identifiers associated with said plurality of data elements; metatag specification functionality operative to facilitate specifying, by an administrator, administrator defined metatags to be associated with each of said data elements having both at least one access metric permission explicitly assigned by said assigned owner and at least one data identifier associated therewith; metatag application functionality operative to utilize said access metrics collection functionality and said metadata collection functionality to ascertain which of said plurality of said data elements have both said at least one access permission explicitly assigned by said assigned owner and said at least one specific data identifier associated therewith and to automatically apply a metatag from among said administrator defined metatags to ones of said plurality of data elements ascertained to have said at least one access permission explicitly assigned by said assigned owner and said at least one data identifier associated therewith; and metatag owner validation functionality operative to ascertain an assigned owner of each one of said plurality of data elements ascertained to have said at least one access permission explicitly assigned by said assigned owner and said at least one data identifier associated therewith, said assigned owner having authority and accountability with respect to said one data element within said enterprise, and to require each of said assigned owners to review and validate said metatags automatically applied to said ones of said plurality of data elements owned thereby. 7. The system according to claim 6 and wherein said metatag application functionality is also operative to automatically apply specific ones of a plurality of different metatags to specific ones of said plurality of data elements. 8. The system according to claim 6 and wherein said metatag application functionality is also operative to automatically apply to each one of said plurality of data elements a metatag previously applied to a parent folder thereof. 9. The system according to claim 6 and wherein said data identifier is one of file type, author, category and language. 10. The system according to claim 6 and also comprising a metadata database which stores said metadata collected by said metadata collection functionality. 11. The system according to claim 6 and wherein said metatag application functionality is also operative to utilize said access metrics collection functionality and said metadata collection functionality to automatically employ said access metric and said data identifier to automatically apply a metatag to ones of said plurality of data elements. 12. The system according to claim 6 and wherein said metatag application functionality is also operative to utilize said access metrics collection functionality to automatically employ said access metric to automatically apply a metatag to ones of said plurality of data elements. 13. The system according to claim 6 and wherein said metatag application functionality is also operative to utilize said metadata collection functionality to automatically employ said data identifier to automatically apply a metatag to ones of said plurality of data elements.
with adaptation to user needs · CPC title
Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually · CPC title
File meta data generation · CPC title
Creation of semantic tools, e.g. ontology or thesauri · CPC title
Document management systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.