This naming convention and tracking system for image files, designed specifically for the Digital Academy, will streamline organization, improve searchability, and ensure traceability. By adopting this structured approach, authors can quickly locate specific images and understand their context within demonstrations. Furthermore, tracking the use of each image across multiple demos will allow updates to be automatically reflected, maintaining consistency and saving time.
Context
Digital walkthroughs rely heavily on screenshots to demonstrate various features. Authors upload these screenshots to an asset manager and integrate them into the walkthroughs, often adding clickable hotspots for interactivity. If an image in the asset manager is updated, it automatically updates in all demos using that image.
A critical aspect of managing these assets involves:
Ensuring updated images are reflected across all demos that use them.
Having an efficient way to find specific images among the uploaded assets.
Tracking where each image is used across multiple digital walkthroughs.
Without a sound naming convention, there's no easy way to find specific images in the asset manager, as the system doesn't track which digital walkthroughs use which images.
Key Requirements
To address these challenges, the system requires:
A robust naming convention that makes image files easily identifiable and searchable within the asset manager.
A method to track image usage across various digital walkthroughs.
Naming Convention for Image Files
The following naming convention is proposed for all image files in the Digital Academy:
Format:
[FeatureName]_[TransactionType]_[Description]_[Version].png
Breakdown:
[FeatureName]: The name of the digital banking feature, such as "MobileApp" or "OnlineTransfer."
[TransactionType]: If applicable, specify the type of transaction being demonstrated, e.g., "FundsTransfer," "BillPayment," or "AccountBalance."
[Description]: A short, clear description of the image’s content, such as "LoginScreen" or "TransactionConfirmation."
[Version]: A version number to track updates (e.g., "v01").
Example:
MobileApp_FundsTransfer_LoginScreen_v01.png
This format helps users easily locate images based on the banking feature, transaction type, and image content.
Additional Considerations:
Security: Ensure that the file names do not include customer-specific information to maintain security. The naming convention should only focus on generic descriptions like features and transaction types.
Version Control: Using version numbers is crucial, particularly in digital banking, where apps are frequently updated, and compliance with regulations requires multiple versions of the same image across different demos.
Tracking Image Usage in Digital Walkthroughs
Tracking which images are used in each walkthrough is essential for maintaining consistency across demos and managing updates. A tracking system, such as a spreadsheet, can be used to record the relevant details about each image.
Suggested Columns for the Tracking Spreadsheet:
Image File Name: Follows the naming convention for easy identification.
Walkthrough Name: Specifies the digital walkthrough(s) where the image is used.
Description: Provides a short description of the image content.
Last Updated: Indicates the date when the image was last updated.
Used in Demos: Lists all demos or demo versions that incorporate the image.
This tracking approach will ensure that all demos using the same images remain up-to-date when the source image is updated, maintaining uniformity across multiple versions.