<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Chuck Diewald on Medium]]></title>
        <description><![CDATA[Stories by Chuck Diewald on Medium]]></description>
        <link>https://medium.com/@chuck.diewald?source=rss-ffbc03d9c386------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*xytjAf7lz9jv4jyp.</url>
            <title>Stories by Chuck Diewald on Medium</title>
            <link>https://medium.com/@chuck.diewald?source=rss-ffbc03d9c386------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:46:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chuck.diewald/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Real-time Analytics: More Accessible Than You Think]]></title>
            <link>https://medium.com/aptitive/real-time-analytics-more-accessible-than-you-think-44d0d4de32f5?source=rss-ffbc03d9c386------2</link>
            <guid isPermaLink="false">https://medium.com/p/44d0d4de32f5</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[looker]]></category>
            <category><![CDATA[real-time-analytics]]></category>
            <category><![CDATA[snowflake]]></category>
            <dc:creator><![CDATA[Chuck Diewald]]></dc:creator>
            <pubDate>Mon, 16 Jul 2018 21:13:43 GMT</pubDate>
            <atom:updated>2018-08-06T21:27:10.623Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VAWK-bTdnGs2i4_2EfKSsw.png" /></figure><p>In today’s fast-paced data-driven world, quicker access to actionable insights is critical and, most importantly, achievable — no matter what business you are in. Gone are the days when cost or complexity kept real-time analytics data visibility out of reach. Inexpensive data storage solutions, event-driven ELT, and modern analytics platforms make this possible with significantly lower upfront investment and faster development than in years past. These platforms additionally enable you to scale up or down to fit your unique circumstances.</p><p>Last month, Aptitive hosted its inaugural (data) Science Fair. Together with our sponsors we showcased the latest and greatest in data technology, from <a href="https://www.aptitive.com/iot-business-solutions/">coffee makers controlled by Tweets</a> to virtual reality analytics. While attendees navigated the fair, they texted the event host, <a href="https://www.aptitive.com/data-science-fair/chatbot-rima/">Chatbot Rima</a>, to earn points for interacting with booths. To compliment this, we built a <a href="https://looker.com/">Looker</a> dashboard that prominently displayed the top rankings of all the attendees as well as the most visited booths:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JhvvHngMnmxqirnXv4-fPQ.png" /></figure><p>Information about actual interactions taking place at the event were being visualized on the dashboard as they happened. The scoreboard added an extra element of competitive excitement to the event, but it also demonstrated the power and simplicity of real-time analytics. Built on top of massively scalable technologies such as a Snowflake data warehouse and an <a href="https://www.alooma.com/">Alooma</a> Data Pipeline, the same dashboard could have been easily adjusted to show a similar real-time scoreboard suited for events as large as the World Cup.</p><p>(To learn more about the data pipeline and underlying architecture behind the (data) Science Fair scoreboard, read our other <a href="https://www.aptitive.com/what-cloud-architecture-project-means-for-your-business/">blog post here</a></p><p>Aptitive has implemented similar solutions for clients ranging in size from fewer than 20 employees to over 10,000. In every case, whether it was reduced costs or quicker decision-making, there was an almost immediate benefit for the stakeholders. The (data) Science Fair scoreboard is only one example of how to analyze and present streaming data. From showing health care providers real-time patient vitals, to displaying interactions as they occur on an e-commerce website, or visualizing assembly line operations in facilities around the world, these analytics can apply to nearly every use case imaginable. Our scoreboard was simply a fun way to demonstrate how few barriers lie between your company and the ability to gain actionable insights from real-time data analytics.</p><p><a href="https://www.aptitive.com/contact/">Contact us</a> if you’re interested in learning more about empowering faster and more effective decision-making leveraging real-time analytics.</p><p>This post was originally published on <a href="https://aptitive.com/">Aptitive.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44d0d4de32f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aptitive/real-time-analytics-more-accessible-than-you-think-44d0d4de32f5">Real-time Analytics: More Accessible Than You Think</a> was originally published in <a href="https://medium.com/aptitive">Aptitive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Preparation Tools — The new silver bullet?]]></title>
            <link>https://medium.com/aptitive/data-preparation-tools-the-new-silver-bullet-df9977f05cce?source=rss-ffbc03d9c386------2</link>
            <guid isPermaLink="false">https://medium.com/p/df9977f05cce</guid>
            <category><![CDATA[data-preparation]]></category>
            <category><![CDATA[paxata]]></category>
            <category><![CDATA[tools]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[governance]]></category>
            <dc:creator><![CDATA[Chuck Diewald]]></dc:creator>
            <pubDate>Tue, 08 May 2018 21:06:06 GMT</pubDate>
            <atom:updated>2018-06-12T15:55:54.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e80zwfPc90StvA0Ta4iKZA.jpeg" /></figure><p>Bad data has plagued IT and Analytics for decades. Even with new visualization tools, predictive analytics, ETL, and cloud computing, every organization needs to clean up and transform their data so their reports, analysis, and dashboards work correctly. This need for cleaning up bad data has led to a new breed of tools for Data Preparation.</p><p>Many vendors are releasing products and enhancements into the Data Preparation space recently, including:</p><ul><li>Datameer</li><li>Google</li><li>Microsoft</li><li>Paxata</li><li>Tableau</li><li>Trifacta</li></ul><h3>Pros and Cons of Data Prep Tools</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IchtjMwRjRW6AF1gOjU3bQ.png" /></figure><p>Data Prep tools allow the analyst faster turnaround and speed to market since other teams are not required for development. They also allow the user to do quick data discovery and improve bad data by applying some simple rules. For up-front analysis and departmental analytics in environments with limited IT resources, or a quick Proof-of-Concept (POC), Data Prep tools can achieve strong business results and greatly reduce time-to-market.</p><h3>Use Cases for Data Prep Tools</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rhXnRHVQY8lB1Cslre-0eg.png" /></figure><p>One of the best use cases for a data prep tool is for data discovery. The tools can analyze large volumes of data and look for patterns and distribution of values to identify outliers and missing values. Beyond that, the data prep tools can apply rules to fix the bad data so the subsequent analysis and reports yield correct results.</p><p>Data Prep tools are not a panacea, and like many new methods, tools, and procedures have some negative fit use cases as well. The biggest challenge to a self-service Data Prep tool is the governance, standardization, and enterprise use of the data. For effective use of these tools beyond the departmental use or POC, strong governance is needed to keep the data under control. Otherwise, the tools could hinder the overall data efforts and impede progress by allowing multiple values and interpretations of the data when depending on the user of the data prep tool.</p><p>Another challenge when using a data prep tool is to ensure setting of expectations when using it on a project. After the quick POC development, the project stakeholders need to understand the additional work required to implement a full, robust implementation.</p><p>A full description of data governance for data prep tools (to be included in more detail in a future blog) includes:</p><ul><li>Multiple environments with stronger governance as things move from development to production</li><li>Change control (with reviews before code is promoted to the next environment)</li><li>Governance committee with representation from business, technical, data teams</li><li>Processes and Standards to support the strategy</li><li>Clear articulation of how the data prep tools will be used and controlled<br>Roles and Responsibilities of stakeholders clearly defined</li><li>Data Architecture, Design, Dictionary well defined and documented (including data prep transformation rules) to help achieve consistent results</li><li>Leveraging the audit and governance capabilities of the data prep tool</li></ul><p>With the power and reduced dependence on others comes the responsibility to use this type of tool wisely. A data prep tool in the wrong hands, lacking governance could create more trouble with the data than the business benefits provided.</p><p>Aptitive helps organizations transform data into actionable, valuable, and accessible intelligence. For more information visit <a href="http://www.aptitive.com/?utm_source=Medium-Data-Preparation-Blog&amp;utm_campaign=Medium">www.aptitive.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df9977f05cce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aptitive/data-preparation-tools-the-new-silver-bullet-df9977f05cce">Data Preparation Tools — The new silver bullet?</a> was originally published in <a href="https://medium.com/aptitive">Aptitive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dimensional modeling with Dimension Maps]]></title>
            <link>https://medium.com/aptitive/dimensional-modeling-with-dimension-maps-b3d1272e4b39?source=rss-ffbc03d9c386------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3d1272e4b39</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[diimensional-modeling]]></category>
            <category><![CDATA[data-warehouse]]></category>
            <category><![CDATA[data-architecture]]></category>
            <category><![CDATA[dimension-map]]></category>
            <dc:creator><![CDATA[Chuck Diewald]]></dc:creator>
            <pubDate>Fri, 23 Jun 2017 18:44:37 GMT</pubDate>
            <atom:updated>2017-06-23T18:44:37.590Z</atom:updated>
            <content:encoded><![CDATA[<p>Traditional data modeling uses “bubble diagrams” for high-level conceptual data models, and then logical and physical Entity Relationship diagrams (ERD.) However, there’s another type of data modeling that’s less ubiquitous, but very powerful for dimensional data structures such as a data warehouse. This model is called a dimensional fact model, conceptual dimensional model, or (as I like to call it) a dimension map.</p><p>Dimension maps are very easy for business users to understand, and they don’t have symbols and arrows like an ERD that tend to confuse users. The dimension map provides more context than a conceptual data model, including the dimensional hierarchies and the delineation between facts and dimensions.</p><p>Consider the example below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/1*4ut1W2V3IaHxlO294uuz9Q.png" /><figcaption>Sample Dimension Map</figcaption></figure><p>The dimension map shows the target data structure for new data warehouse. The blue dots are dimensions, and the orange circles are facts. In complex models, the measures for a fact can be indicated with a callout. (Some people like to use rectangles for their facts, and include the measures in the rectangle.)</p><p>The dimension map represents that target data structure needed to support visualizations and reports as well as the interactions (or relationships) between the dimensions and facts.</p><p>The lines connecting the dimensions and facts represent the relationships between the data. Dimensional hierarchies (such as geography) are shown by lines connecting the higher level dimensions to the more detailed dimensions (e.g. Country to State.) In the case of the Geography, only country, state, and county are available for searching within a geography. If different levels are required (e.g. city), these need to be identified now, and included (or excluded from if not required) on the dimension map.</p><p>The dimension map shows that the target data structure will support searching by the dimensions shown on the map (blue dots — Customer, Item, Vendor….) and measures will be stored for the fact (orange circles –Orders.)</p><p>I’ve found dimension maps very effective at conveying a proposed data structure of a new system and showing the way the data will be stored and accessed. In data workshops, the participants understand the model and the impact of dimensions that aren’t included in a hierarchy. While the data architect will probably still end up doing an ERD for his logical and physical models, and generating the DDL from the modeling tool, the dimension map is a great way to start the process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3d1272e4b39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aptitive/dimensional-modeling-with-dimension-maps-b3d1272e4b39">Dimensional modeling with Dimension Maps</a> was originally published in <a href="https://medium.com/aptitive">Aptitive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Importing a project plan with subtasks from Excel into JIRA]]></title>
            <link>https://medium.com/aptitive/importing-a-project-plan-with-subtasks-from-excel-into-jira-25ae852008e6?source=rss-ffbc03d9c386------2</link>
            <guid isPermaLink="false">https://medium.com/p/25ae852008e6</guid>
            <category><![CDATA[import]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[project-planning]]></category>
            <category><![CDATA[jira]]></category>
            <dc:creator><![CDATA[Chuck Diewald]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 03:34:36 GMT</pubDate>
            <atom:updated>2017-06-16T12:42:19.714Z</atom:updated>
            <content:encoded><![CDATA[<p>Most of my recent projects have used the cloud issue tracking Jira. It’s great for prioritizing issues, and understanding what can be included in the next release. In the past, I used other tools to manage the project plan due to corporate standards. Jira has some good task tracking capabilities, and for small teams on agile projects is useful tool for project planning and tracking. The Jira cloud service can be set up for a project in just a few minutes, and it’s only $10/month for up to 10 users. The challenge is to get a 300–400 line detailed task/project plan into Jira without massive manual effort. It is far easier to import the plan from the project estimating spreadsheet than to manually enter all the tasks in Jira. I found that it wasn’t easy or straightforward (until I experimented and researched enough for it to make sense.) Based upon this experience, I wanted to write up this blog entry to share my results with other who may be having the same challenges. Here are a few tips to help you import a project plan with subtasks from Excel into Jira.</p><h3>Jira doesn’t need many fields to create a plan</h3><p>Jira can import many fields, and most of them were not in my planning spreadsheet. I exported a small plan from Jira with all fields that I entered using the Jira web pages, and was concerned about the number of fields present. Luckily, most of these can be omitted for the import.</p><p>I reduced the fields to:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*jbYX7mf4-CVMlSK6AVbzlQ.png" /></figure><p>The Jira documentation describes each field. I’ve summarized the fields I used along with some comments on each field:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kyCRuiFvtxxpXur0PB67fg.png" /></figure><h3>Standard CSV Import is not the same thing as admin CSV Import</h3><p>Jira has two ways to import CSV files, and only one of them works for importing subtasks.</p><h3>Import Issues from CSV (on … menu on issue screen)</h3><p>This option didn’t work for me for subtasks. (For example, Original Estimate and Remaining Estimate fields were not imported correctly.) It looks very similar to the administration function below, so be careful.</p><h3>Administration &gt; System &gt; External System Import &gt; CSV</h3><p>Select this import by first selecting Jira administration (from the gear menu), then system, the external system import, then CSV as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/145/1*oSdLjM0hYTuyks0M-lhxbw.png" /><figcaption>Bring up the Jira administration menu from the Gear icon</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/116/1*tMC6nsEULERYwT67PfxzLg.png" /><figcaption>Select External System Import</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/222/1*QV0EThofDOVyuYZQjsmgjQ.png" /><figcaption>Chose CSV on the import Wizard.</figcaption></figure><p>This option worked as expected, as long as the input file was set up correctly.</p><p>Below are some things to keep in mind when importing:</p><p>1. Consistent column headings help.</p><p>2. Choose your issue key carefully if you want to keep things in a hierarchy.</p><p>I experimented with various numbering schemes with the import and had success with project abbreviation (SR1) with a dash separator (-) and an issue key starting with 1000, incrementing each issue by 100, and each subtask by 1 so I could have up to 99 subtasks under each task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ntbm4vCweC7GWLMazu0R0Q.png" /></figure><p>3. Issue ID and Parent ID required in the source spreadsheet</p><p>The Issue ID and Parent ID fields are used by the import process to establish the hierarchy of task to subtask. I started with an Issue ID of 10000, and incremented each line in my source spreadsheet by 1. The Parent ID is null for tasks, and the Issue ID of the task for subtasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DhDjZ0DMPqjjVOLBT8xgQw.png" /></figure><p>4. Issue id and Parent id are renumbered during the import</p><p>The numbers entered for Issue ID and Parent ID are renumbered during the import to start with 1 greater than the last number used (even if it was deleted.)</p><p>5. Original Estimate and Remaining Estimate are in seconds</p><p>This is different than it shows on my screen. For example, a 1-hour task should be 3600 seconds on the source spreadsheet.</p><p>6. Mapping the CSV fields to Jira fields</p><p>The first line of the CSV file has the field headings. The mapping of fields was easy since the field names in the source are nearly identical to the Jira Field. The order of the fields may not be the same as in your source CSV file, but that doesn’t matter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/366/1*aOtJrv7BwsikGrbColSLsw.png" /><figcaption>Jira Import Field Mapping</figcaption></figure><h3>Mass-Delete</h3><p>When working on the initial import, I needed to delete all the issues (tasks) imported in a prior test (repeatedly.) The Bulk Change function (available on the issues search … menu) has the capability to delete all the issues. Click on Bulk change all issues (313 in my example)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/206/1*fpscP3QD6e7E4_l2PUZjQA.png" /></figure><p>When prompted for choose issues, click on the box under the next button to select all the issues. Then click on the next button. For the operation select “Delete Issues” and then follow the confirmation prompts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/161/1*bbqKAjMG3CBctgmJO67yBw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25ae852008e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aptitive/importing-a-project-plan-with-subtasks-from-excel-into-jira-25ae852008e6">Importing a project plan with subtasks from Excel into JIRA</a> was originally published in <a href="https://medium.com/aptitive">Aptitive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>