Portfolio > Unity Data Platform > Information Architecture
Embedded Files
Design Navigation and Information Architecture
1/4 Sorting Navigation
To solve the navigation design, I had multiple session with my project management team, additionally did a card sorting exercise with the sponsor's users (QA | System Administrator) and documentation team to understand the depth of the navigation design and consolidating the labelling system. It was all about Metadata and how it is linked with different sections.
How many times users are going to visit different sections based on their journey?
Home many time users will like to automate queries and rules and how many time they want the GUI experience?
How the advanced users will be navigating through the design and how they will study the Metadata?
2/4 Mapping Requirements
The basic requirements for the navigation were focused on the user navigating to the following sections
The Getting Started sections where users land after login.
The Configure sections where the metadata and the schema for all the ingested tables are imported. The Ingested data resides where the user will create the job queues to persist the data in the Dataware house.
The Monitor interface will help to review the jobs queues and errors, for ingested and export job.
The Manage section will help to export the unified and filter data to be plugged in with the Marketing software for giving specific query results for a specific customer or business.
The Card Sorting exercise helped me to connect the related modules for the Application.
3/4 Structuring Metadata
To solve the Information Architecture design, I had multiple session with my project management team studying the JSON structure and also focusing on how the OBJECTS and ARRAYS are being pulled in the Queries and how they will form the structure of the page layout.
Some challenges which I started discovering were the intensity of the OBJECTS and ARRAYS a user can deal with once the data is ingested. Then we have rules to group by sort by which have their own Metadata.
Understanding JSON helped me building up the basic skeleton of the application.
4/4 Final Design & Challenges
With the card sorting exercise and understanding the JSON structure, I was able to design a workable navigation system that was good enough to perform the functions for Ingest, Master and Explore data mapping the metadata for tables.
However, there were some challenges that still persist, like segregating the navigation labels for Ingest, Master and Explore, due to the Rules API which was were interdependent on the MasterTable page, which made Ingestion called Jobs.
Portfolio > Unity Data Platform > Information Architecture
Page updated
Google Sites
Report abuse