Metadata Editor App UI Design Challenge

Make my large number of tags manageable in bulk.

Welcome to the Metadata Editor App UI Design Challenge! Design a User Interface based on the provided wireframe and with great user experience in mind.

In this challenge, we are looking for an application where data users can view and edit existing metadata fields. The database is a relational database, similar to what sits on the backend of classifieds websites such as Craigslist/Gumtree. Administrators need to be able to find items within the database using a search function along with filters to narrow down relevant results. Results are then selected, with the metadata editor opened up to make changes to the assigned tags - the functions incorporated into the metadata editor should be the primary focus of the challenge.

 

Challenge Objectives

• UI design for 6-10 screens/features plus variations (see wireframes)

• Desktop format

• Explore presentation of the content and functionality provided on wireframes.

Round 1

Submit your initial designs and concepts for checkpoint review:

1. Landing/Welcome screen

2. Admin/User Dashboard 

3. Datasets Association/Management

6. Search & Filter to find specific tags or datasets

7. Editing and Saving Field Changes

Round 2

Submit your final designs for round 2 and checkpoint updates as per feedback:

1. Landing/Welcome screen

2. Admin/User Dashboard 

3. Datasets Association/Management

4. Tags Management

5. Activity Logs

6. Search & Filter to find specific tags or datasets

7. Editing and Saving Field Changes

8. Version control on tags

Application Overview

Currently, metadata tags are applied to datasets through Azure Data Catalog. While there are less than 15 tag types at this time, the large number of datasets means that the number of tags quickly becomes unmanageable. Updating the definitions is not feasible, and monitoring gaps become nearly impossible.
 

Target Users

• Data Stewards and Data Governance officers

 

Example Workflows

1. Apply a new tag type called “Privacy” with a value “True” to all datasets containing the word “Employee”.

2. Update the tag “Security Level” to change any Value reading “PrtractedA” to “Protected A”.

3. Delete a tag type called “TEST” from all systems.

4. Review any tag types implemented by a specific user

5. Review all datasets without tags

6. Review all datasets missing a particular tag type

 

Screens / Features Requirements

Please design the primary screens listed below and included in the wireframes. Also include the variations shown with functionality in the wireframes.

Please do not copy the layout and style shown in the wireframes. We are looking for unique creative designs.

 

1. Landing/Welcome screen

• Warning message if user is not in recognized cloud RBAC (Role Based Access Control)

• “Hello [User Type]” 

• User Types: Read Only > Limited Admin > Super Admin > Unrecognised (Warning Message)

• Note that login screen is not required as the admin would be accessing the app through their Azure dashboard RBAC

2. Admin/User Dashboard 

The dashboard will show Metadata Search Activities usually with the following fields:My Assets

• Pinned Assets

• Un-Annotated Assets

• Search (Quick Search, Advance Search, and Save Searches)

• Asset Overview

• Access Overview

• Recent Activities

3. Datasets Association/Management (management of Tags as part of Datasets)

• Filter (Filters, Saved Filters, and Save/Clear Filter)

• List of Assets (List Assets, Annotated Assets, and Un-annotated Assets)

• Tag Editor

4. Tags Management

• Filter (Filters, Saved Filters, and Save/Clear Filter)

• List of Tags (All Tags, Active Tags, and Deleted Tags with restore functionality)

• Bulk Edit Tag

• Bulk Data Asset Association

• Bulk Delete Tag

• Create New Tag

• Edit Single Tag

• Delete Single Tag

• Tag Details

• Single Tag Data Association

• Version Control

• Tag Log Management

5. Activity Logs

• Filter (Filters, Saved Filters, and Save/Clear Filter)

• Activity List (All, My Activities, Other User Activities)

 

Additional Functional Areas:

6. Search & Filter to find specific tags or datasets

• This screen should include the ability to find tags or datasets

• The user should be able to select multiple results for editing/updating the tags

• See the provided draft screen in the forum for added info

7. Editing and Saving Field Changes

• This screen is connected to the Search & Filter screen (this can be a separate screen or combine it with the Search & Filter)

8. Version control on tags

• This area allows users to manage version control whenever there’s an update with a particular tag

Branding Guidelines

• There’s no required branding guidelines, creative freedom is upon yours.

 

Design Assets

• Wireframe in MarvelApp https://marvelapp.com/6434i9e
   

Target Device

• Web/Desktop: 1366px width with height adjusted accordingly

 

Final Deliverables

• All original source files.

• All original source files of the submitted design. Files should be created in Adobe Photoshop, Illustrator, XD, or Sketch!

• Marvel Prototype

  • We need you to upload your screens to Marvel App.

  • Please send your marvel app request to jamesmarquez@gmail.com (challenge copilot)

  • You MUST include your Marvel app URL as a text file in your final submission labeled “MarvelApp URL” (in your marvel app prototype, click on share and then copy the link).