Problem

Right now there's very little metadata for differentiating multiple saved objects from one another. Some metadata which would be useful would be:

• ID (when we have one that's different from Name) Save/rename flow fix #9087
• Date created Add created_at metadata to saved objects #9376
• Date last modified Add date last modified metadata to saved objects #9377
• Date last viewed [Saved Objects] Report usage and last used date #125795
• Package name (when installed by EPM)
• Managed by (Ingest manager, Beats, etc.)
• Owner (dependent upon some kind of identity system)

The lack of this metadata relates significant UI/UX improvements, e.g. adding overview tables for Dashboard and Visualize (#9605), and improved management of saved objects in Management (#125795).

Solution

Because this kind of metadata can apply to any type of document, I think this should ultimately be the role of some kind of future object model that automatically tracks this metadata (per @spalger's idea).

If we implement any kind of solution in the interim, we should keep this in mind and have a plan for migrating to this kind of system later on.