You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@senssoft.apache.org by "Joshua Poore (JIRA)" <ji...@apache.org> on 2018/04/16 18:00:00 UTC
[jira] [Updated] (SENSSOFT-291) Improve UserALE.js Field Structure
for Easier Querying/Make Intuitive
[ https://issues.apache.org/jira/browse/SENSSOFT-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Poore updated SENSSOFT-291:
----------------------------------
Fix Version/s: (was: UserALE.js 1.1.0)
UserALE.js 1.2.0
> Improve UserALE.js Field Structure for Easier Querying/Make Intuitive
> ---------------------------------------------------------------------
>
> Key: SENSSOFT-291
> URL: https://issues.apache.org/jira/browse/SENSSOFT-291
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
> Reporter: Joshua Poore
> Assignee: Alex Ford
> Priority: Major
> Fix For: UserALE.js 1.2.0
>
> Original Estimate: 2m
> Remaining Estimate: 2m
>
> As the scope of information that UserALE.js collects has increased, we find that our schema for indexing this data has not similarly scaled intelligently. A key example is that pageUrl is a property of both raw/interval logs and tab tracking logs, however pageUrl is not indexed the same way. This makes for difficult querying after data is collected. Moreover, legacy field names, e.g., type should be re-labeled to be more intuitive (userEventClass)
> DoD: meet with Data Science friends to explore pain points in pulling data together from UserALE.js explore standardizing field names across different datasources.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)