Metadata Editor App Challenge Wireframe Design Challenge

Welcome to the Metadata Editor App Wireframe Design Challenge! In this challenge, we are looking to design a wireframe for an application where data users can create, delete, and edit existing tags that represent metadata for the many hundreds of databases, tables, and views over dozens of platforms.

Challenge Objectives
The goal of this challenge is to design a wireframe for a web application specifically used for desktop browsers, to be deployed on a cloud platform (Microsoft Azure or Amazon AWS).

• Wireframe design
• 6-7 screens
• Desktop browsers

Round 1

Submit your initial wireframe design/concept for checkpoint review:

• Dataset to Tag Association/Management User interface
• Data model changes or additions
• Search & Filter to find specific tags or tag to dataset affiliations
• Editing and Saving Field Changes

[Review, Checkpoint Feedback Collated & Shared with Designers]

 

Round 2

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

• Dashboard
• Admin/User Dashboard
• Dataset to Tag Association/Management User interface
• Datasets Association/Management (Management of Tags, not so much Datasets)
• Search & Filter to find specific tags or datasets
• Editing and Saving Field Changes
• Version control on tags

Problem statement

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 becomes nearly impossible.

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

Current Assets
A data model has been created to handle the tags, however there is no application available to manage creation, update, versioning, and deletion of tags. This model can be enhanced if the design calls for it. (see attached files for a clearer image)



Data Stewards need to be able to find tags 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 search may either be for the tags themselves or the datasets they are connected to.

Filters & search parameters include but are not limited to:
1. TagTypeName
2. CreateDate
3. UpdateDate
4. UpdateBy
5. ServerName
6. Version
7. SourceSystem
8. ColumnName
9. ObjectDateCreated
10. ObjectDateUpdated

Screen Requirements

The following screens include but not limited to:

1. Landing page

• 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
• Save Searches
• Top Tags
• Number of Assets
• Annotated Assets
• Number of Users
• Number of Publishers

3. Datasets Association/Management (Management of Tags, not so much Datasets)

• Tags the user has edited/created
• Full list of tag types and values
• List of deleted tags
• List of changes by user
• Saved Searches
• Number of Dataset Assets
• Number of Annotated Dataset Assets for a selected tag

4. Search & Filter to find specific tags or datasets

• This page 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

5. Editing and Saving Field Changes

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

6. Version control on tags

• This screen will allow users to manage version control whenever there’s an update with a particular tag

Target Device

• You should plan your experience for Web/Desktop size 

Target Users

• Data Stewards and Data Governance officers

Tools 

• We are asking to work with Axure: http://www.axure.com/
• You can also work with static images but you must include a fully navigable prototype in HTML.
• If you are designing in Adobe XD, Photoshop or Sketch then it is mandatory that you create the flow using MarvelApp as we are expecting to see a clickable wireframe in this challenge. Feel free to request a Marvel App on forums or email jamesmarquez@gmail.com for that. 
• Note: do not use colors in your wireframes, if you use a design tool! Keep it simple – black and white, as we are focusing on the UX here, not the UI.

Stock Photography and Icons

• Topcoder icons are allowed as per Topcoder rules.
• Topcoder photos are allowed as per Topcoder rules.

Judging Criteria

• User Experience of the application
• Completeness and accuracy of your wireframes
• How well your wireframes provide a consistent user flow

Final Deliverables

1. Source.zip – All original source files.
All source files of all graphics created in Axure(.rp) or any design tool

2. Submission.zip – PNG/JPG files
Submit JPG/PNG image files based on the Challenge submission requirements stated above.

3. Preview.png – Your preview image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72 dpi and place a screenshot of your submission within it.

4. Declarations.txt – All your declarations and notes
This file must contain your notes if any, fonts used, links to the stock images and icons used and the link to your Marvel project