Asset Management and TI News Audit

Search Functionality and Asset Management

Keyword-Based Searches

  • Searches are primarily keyword-based rather than folder-specific.

  • The goal is to find assets that fit a particular need or use case.

  • Expert opinions are considered when selecting appropriate assets.

Challenges with TI News Folder

  • TI News content audit: There's a need to determine the future process for handling TI News images, considering they're not currently audited.

  • Specific One-off Use Images: Many images are for specific events or pages with limited reuse potential (e.g., images with dates like "02/2021 power show").

  • Usage Tracking: It's difficult to know where tagged images are being used.

  • Video Thumbnails: Uncertainty exists regarding the ownership and potential future use of video thumbnails posted on pages.

Transition to TI.com

  • Technical articles and blogs are being migrated to TI.com.

  • The current directory structure is outdated and complex, posing maintenance challenges.

Asset Types and Ownership

  • Audit Scope: Willingness to audit equipment images, photos, and illustrations for company blogs.

  • Functional Assets: Block diagrams and screen captures are considered functional rather than creative assets and need a decision on ownership.

Orphan Pages

  • Assets allocated for one-of-a-kind purposes on orphan pages may become obsolete.

  • Unpublishing assets can reveal who is actively using them.

  • Many photographs in TI News either have better versions or duplicates in TI.com applications area.

Contextual Image Selection

  • Image selection is often preferential based on the expert and contextual relevance to the use case (e.g., factory setting depiction).

  • TI.com folder is generally considered more valuable, but determining asset placement can be challenging.

Image Sizes and Renditions

  • Image Sizes: TI News contains a multitude of random image sizes, unlike TI.com, which primarily uses 1280×7201280 \times 720 or 720×720720 \times 720 resolutions.

  • Lack of Renditions: TI News images were created without renditions, optimized and compressed for immediate use.

  • Open Bucket Approach: TI News served as an open bucket for engineers needing images for quick display, without strict standards.

  • Duplication: The absence of proper renditions led to file duplication with awkward naming conventions.

  • Audit Results: Previous audits of application folders revealed significant redundancy, with very few images being retained.

Archiving Considerations

  • The key question: Should unused assets be prevented from future use by archiving?

  • A sampled folder review reveals duplicates and one-off use images that don't align with current storytelling needs.

  • There needs to be a decision as to whether to archive images if they are not the way that TI wants to tell their story.

Folder Content Examples

  • One folder contains images with various non-standard dimensions (e.g., 559×614559 \times 614, 593×607593 \times 607).

  • Many images are outdated blog post illustrations with no new purpose.

Proposed Actions

  • Folder-Level Audit: Archive entire folders of migrated or bad content.

  • Asset-Level Audit: Conduct detailed audits of remaining folders to identify reusable assets.

  • Two new buckets: Photographic illustrations were carried on in 2024 when we decide we were just going to open two different buckets.

  • Technical Credibility and Style Audits: Images are typically audited for technical accuracy and stylistic relevance (on brand).

Search Limitations

  • TI News can't be cut off from search returns, requiring user training for better filtering.

  • Emphasis on using the applications folder due to continuous auditing.

Archiving Workflow

  • Document the location of all assets, even archived ones.

  • Archiving triggers alerts if a file is referenced elsewhere.

Thumbnail Usage

  • Thumbnails might be used in emails linking to pages but not directly on TI.com.

Next Steps

  • Discuss the plan with relevant teams (Devin, UX).

  • Kelly will pause archiving until input received.

  • Scott will review folders and identify assets for archiving/usability.