Challenge Summary
Welcome to "Quartz - Log Digitization App Wireframe Refinement Challenge". Previously, we've completed a wireframe challenge to create an initial workflow for our Log Digitization app, and now we are looking for your creative skills to refine the wireframe for the Log Digitization application based on new list request that we received so the app can meet our expectation.
We are looking for your ideas and the best UX and workflow around the app. Ask any questions in the forum, and have fun!
2) Any comments about your wireframe for the Client
2) Any comments about your wireframe for the Client
We are looking for your ideas and the best UX and workflow around the app. Ask any questions in the forum, and have fun!
Round 1
1) All the requested items2) Any comments about your wireframe for the Client
Round 2
1) All requested items with client checkpoint feedback applied2) Any comments about your wireframe for the Client
Background Overview
Converting paper records into digital format can be challenging, particularly when the records have various types of data, each with their own important meaning. The client has several paper logs, utilizing various types of graphed data, as well as textual annotations, and in some cases other markings.
The long-term goal is to digitize as much of the contained data as possible. Manually re-entering all data by hand is cost and time prohibitive (to say nothing of error-prone, or other issues). However, the mixed-format data does not necessarily lend itself well to fully unassisted automated approaches either (data is quite mixed, has complex representation, and in cases is not very high fidelity.)
The client's expectation is that part of the processing will involve human-assisted work (think Mechanical Turk), while some of the more mundane and straightforward things like OCR will be almost entirely automated.
In this project, we are looking to create a new "Log Digitization" application that will be able to:
1. Classify a log file (Large image format - TIFF) into a group with similar log files (These log files are scanned of the mud log files).
2. Break the log file into pieces by cropping the image into sections
3. Have users enter some metadata about the various sections.
4. Develop an algorithm/process that will capture data from the log files and store it in a structured format. We're hoping to maximize the use of OCR and the automated mechanism to retrieve info but given state of the art, it might be necessary to use Mechanical Turk or other human intervention to retrieve data from some of the files or some specific sections of the files.
5. Allow users to pull reports about the information retrieved.
In our initial Wireframe (check attachment) we're focusing on the "Template Creator" application. that focused on steps 2 and 3 in the Log Digitization process that mentioned above. We are now want to focus on the rest of the steps 1 to 5.
Data Extraction Flow (Partially Implemented in Existing Wireframes)
- Upload 1 or more Log Files.
- The user assigns Template Type (not completed yet)
- User clicks process button.
- Images are preprocessed to straighten the images and remove borders to make them as consistent as possible. This would be a backend process with a simple status provided to users.
- The system applies a template based on user selection in step 2 above.
- The system extracts information using the template guidance.
- System load extracted data into a database.
- The user can review data extracted manually in the tool on log file at a time.
- The user can extract reports about data collected by the tool.
Template Creation Workflow
- User review log files to be processed and select a template to create for commonly used formats.
- The user defines the sections of the document to process. Different sections may need to be processed in different ways -- Header information, Mud Gas curves, Depth Sections, Geological Notes, Drill Speed, etc.
- After high-level sections of each template are defined. The users add more detail on how to process the individual sections -- field level (Operator) or curve level details and scales.
- Templates creators can perform two types of auditing on their templates:
-- Page Level - borders of the sections are reviewing against the images of the actual logs files.
-- Section Level - individual sections are shown along with the data retrieved from a particular log file.
Challenge Goal
Updates the initial wireframe to match the latest request provided so it can meet our expectation on how the app should work and make the refinement request defined below.
Challenge Forum
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
Flow and UX Consideration
- Focus on the refinement request
- Do not break any functionality that already existed in the wireframes
- Worked on General navigation between all required screens and functionalities
- Easy and intuitive use for tech and non-tech users.
- The target device for this application is Web.
- We are looking for your ideas here!
Wireframe Expectations
- You must create traditional wireframe call-outs and notes
- Provide us with your interaction and click-path thoughts and suggestions
- The application must be very easy to use and intuitive. Keep that in mind when creating your solution for the layout and flow information
Refinement Request
1) Use the 1st Place submission (254709) as your base submission and 2nd (254843) and 3rd (254842) place as references.
2) We like the 1st place because it has a nice detail on Creation of Templates and Section Details. Nice side by side audit option. And good file upload capability.
3) We need to set up the app to handle both the Current Process Log File Workflow and the Template Creation Workflow (see new proposed for those workflows above)
4) In the Log File list view (Dashboard), we need to provide a feature where the user can be able to initiate the next step in the processing - Deskewing the images or starting the content extraction process. Right now it’s only showing the file status.
5) We need a way where the user can load more than one file at a time into the system.
6) So, in step 1 after the user uploads a file, we'll need to assign Template Type to the file (for the time being). Perhaps on the Log File list view, we should allow users to update the template type too.
7) The winning wireframe starts to implement a wizard-like template creation process but doesn't really follow through with the wizard on step 2 or 3 of the process. We think the Wizard-like process is a good idea. Actually, the workspace and workflow of the 2nd place winner are a bit better for the action create new template (and edit template) functionality. We want to incorporate this more visual approach into the winning wireframe.
8) On the Process Area breakup screen, we're going to need more details about each of the sections displayed. We should show details about each section defined -- a name and a bounding box (Top Left Corner X, Top Left Corner Y, Bottom Right Corner X, Bottom Right Corner Y)
9) We have a good start on the Process Area Definition Screen. However, we need to allow users to rotate the Section so that they can see what they're doing and designate the extraction fields horizontally.
10) The content audit page of our winning solutions is pretty powerful. Like the ability to choose a sample log file and see how it was processed with the template. The current list, however, takes up a lot of real estate on the screen. We need to optimize it. Also, users are going to want to simply iterate through the files processed by this template with an arrow like or next/previous type of control, I think we should add an "All Content" area to the "Select area to audit" drop-down. When this is selected we'll want to view all structured data extracted from the image. The Content Mapping feature is a good way of displaying the extracted information for a given log file. One of the solutions highlighted each Process Area with a different color. We need to implement this features.
11) We need to develop some reporting screens which allow users to view extracted content without referring to the original images. It would be nice to be able to aggregate this by template-type but users might want to see the data extracted from individual files as well. We can start with the header sections and depth sections to start with. Header sections have data like well name, company, depth logging start, depth logging ended. etc.. Depth sections will have a depth value and a y-pixel coordinate. The field names for each template type will be a little different. So there is a level of indirection here. Behind the scenes, there will be a database with three columns, section name, field name, and the field value. We won't know the exact field names until we define them in the templates. They'll be a little different for each template defined.
Documentation
Google Drive: View it from this Link
- All Winning Wireframes (From Previous challenge)
- Sample Log Image files (For references)
- Log Digitization Ideation 1.0.doc - Specification Document (For References)
New to Axure RP, get started right away!!
- Here are some quick tutorials to help you get started http://www.axure.com/support
Screen Size
- Desktop: 1366px(w) & height up to your design
Target Audience
- Geologist and IT staff at an Oil and Gas Exploration company.
Judging Criteria
- User experience and information architecture
- Expanding upon and creating unique features for the provided concepts
- Visual-driven, clear, concise, and meaningful data display
- Capture all the required fields on every page
- Completeness and accuracy of your wireframes
- How well your wireframes provide a consistent user flow
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
- Wireframes should be clickable and can be opened in all major browser without issue (HTML/CSS/JS).
- IMPORTANT! Make sure all the content is listed and the pages are linked together to show page flow.
- Keep your source files out from this submission folder.
Source Files
- All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file
- You can build the wireframes using Plain HTML/CSS/JS or you can generate from the Axure application. Another option is using Sketch with Black/White theme (needs to be clickable).
Final Fixes
As part of the final fixes phase, you may be asked to modify content or user click paths.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.