[jira] [Updated] (SENSSOFT-230) Discover requirements for accrediting plugin through Firefox
[ https://issues.apache.org/jira/browse/SENSSOFT-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard updated SENSSOFT-230: Remaining Estimate: 1m Original Estimate: 1m > Discover requirements for accrediting plugin through Firefox > > > Key: SENSSOFT-230 > URL: https://issues.apache.org/jira/browse/SENSSOFT-230 > Project: SensSoft > Issue Type: Improvement > Components: UserALE.js >Affects Versions: UserALE.js 0.2.0 >Reporter: Joshua Poore >Assignee: Rob Foley > Original Estimate: 1m > Remaining Estimate: 1m > > We need: > 1. FF policies > 2. FF procedural steps for submitting plugin > 3. FF required documentation > 4. Technical requirements -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-233) D3 Sankey Not Redrawing Correctly
[ https://issues.apache.org/jira/browse/SENSSOFT-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard updated SENSSOFT-233: Remaining Estimate: 8h Original Estimate: 8h > D3 Sankey Not Redrawing Correctly > - > > Key: SENSSOFT-233 > URL: https://issues.apache.org/jira/browse/SENSSOFT-233 > Project: SensSoft > Issue Type: Bug > Components: TAP >Affects Versions: Tap 0.1.0 >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Original Estimate: 8h > Remaining Estimate: 8h > > When trying to use the update on filter functionality and transition, > artifacts persist and are not erased, even though they should be gone. > It has to do with these two functions: > * D3’s .exit() is not selecting the right things after the data is passed to > the nodes/rectangles/links > * D3’s remove() function not removing everything that is selected, even > though it should -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-221) Elasticsearch 5.x does not support microseconds
[ https://issues.apache.org/jira/browse/SENSSOFT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard updated SENSSOFT-221: Sprint: (was: Sprint 12) > Elasticsearch 5.x does not support microseconds > --- > > Key: SENSSOFT-221 > URL: https://issues.apache.org/jira/browse/SENSSOFT-221 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 0.2.0 >Reporter: Michelle Beard >Assignee: Michelle Beard > Fix For: UserALE.js 0.2.0 > > > In order to do accurate sequence analysis, it is imperative that the > clientTime generated by userALE is set to microseconds. Unfortunately, > Elasticsearch only supports up to milliseconds. This impacts how sorting is > done at the clientTime level. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Beard updated SENSSOFT-203:
Remaining Estimate: 4h (was: 2h)
Original Estimate: 4h (was: 2h)
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENSSOFT-221) Elasticsearch 5.x does not support microseconds
[ https://issues.apache.org/jira/browse/SENSSOFT-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard updated SENSSOFT-221: Sprint: Sprint 12 > Elasticsearch 5.x does not support microseconds > --- > > Key: SENSSOFT-221 > URL: https://issues.apache.org/jira/browse/SENSSOFT-221 > Project: SensSoft > Issue Type: Bug > Components: UserALE.js >Affects Versions: UserALE.js 0.2.0 >Reporter: Michelle Beard >Assignee: Michelle Beard > Fix For: UserALE.js 0.2.0 > > > In order to do accurate sequence analysis, it is imperative that the > clientTime generated by userALE is set to microseconds. Unfortunately, > Elasticsearch only supports up to milliseconds. This impacts how sorting is > done at the clientTime level. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-229) Fix Histogram Dataset from Distill
[
https://issues.apache.org/jira/browse/SENSSOFT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michelle Beard updated SENSSOFT-229:
Remaining Estimate: 2h
Original Estimate: 2h
> Fix Histogram Dataset from Distill
> --
>
> Key: SENSSOFT-229
> URL: https://issues.apache.org/jira/browse/SENSSOFT-229
> Project: SensSoft
> Issue Type: Task
> Components: TAP
>Affects Versions: Tap 0.1.0
>Reporter: Arthi Vezhavendan
>Assignee: Arthi Vezhavendan
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Fix the histogram dataset created on Distill's end so that it correlates with
> Sankey. This should allow for better filtering between sankey and the
> histograms.
> The main keys the histogram needs are:
> * target
> * path
> * path length
> * an array of the "type" of interaction done on that target
> * an array of the counts correlated with those above type
> For example:
> {code:javascript}
> {"histogram": [
> {"target": "#document",
> "path":"#document home",
> "path-length": 2,
> "types": ["focus", "blur", "resize"]
> "counts": [4, 5, 6]},
> {"target": "#div1",
> "path":"#div1 document home",
> "path-length": 3,
> "types": ["focus", "blur", "resize"]
> "counts": [1, 2, 3]},
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENSSOFT-230) Discover requirements for accrediting plugin through Firefox
[ https://issues.apache.org/jira/browse/SENSSOFT-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard updated SENSSOFT-230: Remaining Estimate: 1h (was: 1m) Original Estimate: 1h (was: 1m) > Discover requirements for accrediting plugin through Firefox > > > Key: SENSSOFT-230 > URL: https://issues.apache.org/jira/browse/SENSSOFT-230 > Project: SensSoft > Issue Type: Improvement > Components: UserALE.js >Affects Versions: UserALE.js 0.2.0 >Reporter: Joshua Poore >Assignee: Rob Foley > Original Estimate: 1h > Remaining Estimate: 1h > > We need: > 1. FF policies > 2. FF procedural steps for submitting plugin > 3. FF required documentation > 4. Technical requirements -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SENSSOFT-234) Sankey result returns loops/cycles
Michelle Beard created SENSSOFT-234: --- Summary: Sankey result returns loops/cycles Key: SENSSOFT-234 URL: https://issues.apache.org/jira/browse/SENSSOFT-234 Project: SensSoft Issue Type: Bug Components: Distill Affects Versions: Distill 0.1.0 Reporter: Michelle Beard Assignee: Michelle Beard Fix For: Distill 0.1.0 Distill's sankey generation returns cycles. Need to ensure that visited nodes receive new ids. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135508#comment-16135508
]
Michelle Beard commented on SENSSOFT-203:
-
SENSSOFT-186: KEYS
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135512#comment-16135512
]
Michelle Beard commented on SENSSOFT-203:
-
Updated README, package.json, and added NOTICE and DISCLAIMER file.
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135510#comment-16135510
]
Michelle Beard commented on SENSSOFT-203:
-
SENSSOFT-27: NPM
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135517#comment-16135517
]
Lewis John McGibbney commented on SENSSOFT-203:
---
Hi [~msbeard] is this finished now?
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SENSSOFT-235) Creat DOAP for UserALE.js
Michelle Beard created SENSSOFT-235: --- Summary: Creat DOAP for UserALE.js Key: SENSSOFT-235 URL: https://issues.apache.org/jira/browse/SENSSOFT-235 Project: SensSoft Issue Type: Task Components: UserALE.js Affects Versions: UserALE.js 0.1.0 Reporter: Michelle Beard Assignee: Michelle Beard Fix For: UserALE.js 0.1.0 We should probably generate a Description of a Project (DOAP) file for every SensSoft project... however this is not a blocker for a release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135530#comment-16135530
]
Michelle Beard commented on SENSSOFT-203:
-
Fixed [1], [3], [4], [5], [7] and pushed to master.
[2]: SENSSOFT-27
[6]: SENSSOFT-186
[8]: SENSSOFT-235
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SENSSOFT-186) [RELEASE PROC] Sign UserALE Release
[ https://issues.apache.org/jira/browse/SENSSOFT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard updated SENSSOFT-186: Sprint: Sprint 12 > [RELEASE PROC] Sign UserALE Release > --- > > Key: SENSSOFT-186 > URL: https://issues.apache.org/jira/browse/SENSSOFT-186 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Michelle Beard >Assignee: Michelle Beard > Fix For: UserALE.js 0.1.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > Every artifact distributed by the Apache Software Foundation must be > accompanied by one file containing an OpenPGP compatible ASCII armored > detached signature and another file containing an MD5 checksum. The names of > these files must be formed by adding to the name of the artifact the > following suffixes: > the signature by suffixing .asc > the checksum by suffixing .md5 > An SHA checksum should also be created and must be suffixed .sha. > Release managers must not store private keys used to sign Apache releases on > ASF hardware. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-213) Update UserALE.js deployment Instructions
[ https://issues.apache.org/jira/browse/SENSSOFT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard updated SENSSOFT-213: Sprint: Sprint 10, Sprint 12 (was: Sprint 10) > Update UserALE.js deployment Instructions > - > > Key: SENSSOFT-213 > URL: https://issues.apache.org/jira/browse/SENSSOFT-213 > Project: SensSoft > Issue Type: Improvement > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Michelle Beard >Assignee: Rob Foley > Fix For: UserALE.js 0.1.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > Currently, we need to update some files in userale.js so we are no longer > dependent on our draper GH pages for building, deploying userale, and the > script tag. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-27) [RELEASE PROC] NPM Package for UserALE.js
[ https://issues.apache.org/jira/browse/SENSSOFT-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard updated SENSSOFT-27: --- Sprint: Sprint 12 > [RELEASE PROC] NPM Package for UserALE.js > - > > Key: SENSSOFT-27 > URL: https://issues.apache.org/jira/browse/SENSSOFT-27 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Critical > Fix For: UserALE.js 0.1.0 > > Original Estimate: 5h > Remaining Estimate: 5h > > Enable Userale.js to be used and distributed as a NPM package. Release over > NPM, Bower, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SENSSOFT-235) Creat DOAP for UserALE.js
[ https://issues.apache.org/jira/browse/SENSSOFT-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard resolved SENSSOFT-235. - Resolution: Fixed [~lewismc] - Done. Pushed to master. > Creat DOAP for UserALE.js > - > > Key: SENSSOFT-235 > URL: https://issues.apache.org/jira/browse/SENSSOFT-235 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Michelle Beard >Assignee: Michelle Beard > Fix For: UserALE.js 0.1.0 > > > We should probably generate a Description of a Project (DOAP) file for every > SensSoft project... however this is not a blocker for a release. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SENSSOFT-186) [RELEASE PROC] Sign UserALE Release
[ https://issues.apache.org/jira/browse/SENSSOFT-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard resolved SENSSOFT-186. - Resolution: Fixed Added public signing key to https://github.com/apache/incubator-senssoft > [RELEASE PROC] Sign UserALE Release > --- > > Key: SENSSOFT-186 > URL: https://issues.apache.org/jira/browse/SENSSOFT-186 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Michelle Beard >Assignee: Michelle Beard > Fix For: UserALE.js 0.1.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > Every artifact distributed by the Apache Software Foundation must be > accompanied by one file containing an OpenPGP compatible ASCII armored > detached signature and another file containing an MD5 checksum. The names of > these files must be formed by adding to the name of the artifact the > following suffixes: > the signature by suffixing .asc > the checksum by suffixing .md5 > An SHA checksum should also be created and must be suffixed .sha. > Release managers must not store private keys used to sign Apache releases on > ASF hardware. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SENSSOFT-27) [RELEASE PROC] NPM Package for UserALE.js
[ https://issues.apache.org/jira/browse/SENSSOFT-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135575#comment-16135575 ] Michelle Beard edited comment on SENSSOFT-27 at 8/21/17 6:38 PM: - [~rf], Need instructions on how to push software to npm. was (Author: msbeard): Need instructions on how to push software to npm. > [RELEASE PROC] NPM Package for UserALE.js > - > > Key: SENSSOFT-27 > URL: https://issues.apache.org/jira/browse/SENSSOFT-27 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Joshua Poore >Assignee: Joshua Poore >Priority: Critical > Fix For: UserALE.js 0.1.0 > > Original Estimate: 5h > Remaining Estimate: 5h > > Enable Userale.js to be used and distributed as a NPM package. Release over > NPM, Bower, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135578#comment-16135578
]
Michelle Beard commented on SENSSOFT-203:
-
[~lewismc]: Just need to document process to release software through NPM. That
should be the last of it.
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135631#comment-16135631
]
Lewis John McGibbney commented on SENSSOFT-203:
---
Absolutely fantastic.
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SENSSOFT-27) [RELEASE PROC] NPM Package for UserALE.js
[ https://issues.apache.org/jira/browse/SENSSOFT-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard reassigned SENSSOFT-27: -- Assignee: Rob Foley (was: Joshua Poore) > [RELEASE PROC] NPM Package for UserALE.js > - > > Key: SENSSOFT-27 > URL: https://issues.apache.org/jira/browse/SENSSOFT-27 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Critical > Fix For: UserALE.js 0.1.0 > > Original Estimate: 5h > Remaining Estimate: 5h > > Enable Userale.js to be used and distributed as a NPM package. Release over > NPM, Bower, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SENSSOFT-27) [RELEASE PROC] NPM Package for UserALE.js
[ https://issues.apache.org/jira/browse/SENSSOFT-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michelle Beard resolved SENSSOFT-27. Resolution: Fixed This is done. We created a npm user and documented the process on Confluence in our release procedures document. > [RELEASE PROC] NPM Package for UserALE.js > - > > Key: SENSSOFT-27 > URL: https://issues.apache.org/jira/browse/SENSSOFT-27 > Project: SensSoft > Issue Type: Task > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Joshua Poore >Assignee: Rob Foley >Priority: Critical > Fix For: UserALE.js 0.1.0 > > Original Estimate: 5h > Remaining Estimate: 5h > > Enable Userale.js to be used and distributed as a NPM package. Release over > NPM, Bower, etc. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENSSOFT-203) Address UserALE.js feedback from lewismc
[
https://issues.apache.org/jira/browse/SENSSOFT-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135739#comment-16135739
]
Michelle Beard commented on SENSSOFT-203:
-
Waiting on final verdict by Lewis to proceed with official release of
UserALE.js.
> Address UserALE.js feedback from lewismc
>
>
> Key: SENSSOFT-203
> URL: https://issues.apache.org/jira/browse/SENSSOFT-203
> Project: SensSoft
> Issue Type: Task
> Components: UserALE.js
>Affects Versions: UserALE.js 0.1.0
>Reporter: Lewis John McGibbney
>Assignee: Michelle Beard
>Priority: Blocker
> Fix For: UserALE.js 0.1.0
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Hi Folks,
> This is straight from my identical feedback on the dev@ list. Excellent work
> on UserALE.js it is looking very good.
> Lewis
> Some initial questions/feedback/observations
> # The README [0] needs to be updated in several places, this will be obvious
> when you read the README. This will need to be updated.
> # Is the intention to host UserALE.js on some CDN somewhere? I see from [1]
> that the intention is to release the code to NPM and/or Bower... is this work
> in progress (I think it definitely is) and if so is it documented somewhere?
> # It might be worth providing a more detailed description at [2]
> # I would make sure that the JIRA Release Notes [3] are copied over to the
> CHANGELOG.md file [4]. Additionally, I would structure it after the following
> example [5] where essentially the JIRA release report is copied and pasted in
> there, this tends to render nicely in Markdown. Additionally, it looks better
> if the release manager provides a short link to the release report. This can
> be obtained using the URL shortening service at [6].
> # Please make sure to add a DISCLAIMER, a sample can be seen at [7]
> # We need to produce a KEYS file for all SensSoft developers who wish to act
> as release manager and sign release artifacts. They KEYS file can live
> anywhere within/across the SensSoft repositories. An example can be found at
> [8].
> # We need to generate a NOTICE file which essentially details usage and
> appropriate attribution of dependencies consumed within UserALE.js. An
> example can be seen at [9].
> # We should probably generate a Description of a Project (DOAP) file for
> every SensSoft project... however this is not a blocker for a release.
> I think the above represents a minimum degree of feedback that I would like
> to see addressed before we attempt to generate a release candidate for
> UserALE.js.
> If there are ANY questions, please let me know.
> I've raised a JIRA issue for this at [10] which will enable someone(s) to
> track and address the issues.
> Thanks
> [0] https://github.com/apache/incubator-senssoft-useralejs
> [1]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/README.md
> [2]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/package.json#L4
> [3]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320621&version=12339748
> [4]
> https://github.com/apache/incubator-senssoft-useralejs/blob/master/CHANGELOG.md
> [5]
> https://raw.githubusercontent.com/apache/incubator-joshua/master/CHANGES.md
> [6] https://s.apache.org/
> [7] https://github.com/apache/incubator-joshua/blob/master/DISCLAIMER.txt
> [8] https://github.com/apache/incubator-joshua/blob/master/KEYS
> [9] https://github.com/apache/incubator-joshua/blob/master/NOTICE.txt
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SENSSOFT-236) Fix Event-Based Selectors for Sankey
Joshua Poore created SENSSOFT-236: - Summary: Fix Event-Based Selectors for Sankey Key: SENSSOFT-236 URL: https://issues.apache.org/jira/browse/SENSSOFT-236 Project: SensSoft Issue Type: Bug Components: TAP Affects Versions: Tap 0.1.0 Environment: JavaScript, D3, React.js Reporter: Joshua Poore Assignee: Joshua Poore Fix For: Tap 0.1.0 Need to fix event based filters to select appropriate data streams for sequential visualization. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-202) Basic Layout for Sankey Diagram
[ https://issues.apache.org/jira/browse/SENSSOFT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-202: -- Sprint: Sprint 8, Sprint 9, Sprint 10, Sprint 11 (was: Sprint 8, Sprint 9, Sprint 10, Sprint 11, Sprint 12) > Basic Layout for Sankey Diagram > --- > > Key: SENSSOFT-202 > URL: https://issues.apache.org/jira/browse/SENSSOFT-202 > Project: SensSoft > Issue Type: Task >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > Design the basic sankey diagram that can then be converted to fit the TAP > demo site. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-236) Fix Event-Based Selectors for Sankey
[ https://issues.apache.org/jira/browse/SENSSOFT-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-236: -- Sprint: Sprint 12 > Fix Event-Based Selectors for Sankey > > > Key: SENSSOFT-236 > URL: https://issues.apache.org/jira/browse/SENSSOFT-236 > Project: SensSoft > Issue Type: Bug > Components: TAP >Affects Versions: Tap 0.1.0 > Environment: JavaScript, D3, React.js >Reporter: Joshua Poore >Assignee: Joshua Poore > Fix For: Tap 0.1.0 > > > Need to fix event based filters to select appropriate data streams for > sequential visualization. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-213) Update UserALE.js deployment Instructions
[ https://issues.apache.org/jira/browse/SENSSOFT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-213: -- Sprint: Sprint 10 (was: Sprint 10, Sprint 12) > Update UserALE.js deployment Instructions > - > > Key: SENSSOFT-213 > URL: https://issues.apache.org/jira/browse/SENSSOFT-213 > Project: SensSoft > Issue Type: Improvement > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Michelle Beard >Assignee: Rob Foley > Fix For: UserALE.js 0.1.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > Currently, we need to update some files in userale.js so we are no longer > dependent on our draper GH pages for building, deploying userale, and the > script tag. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-202) Basic Layout for Sankey Diagram
[ https://issues.apache.org/jira/browse/SENSSOFT-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-202: -- Sprint: Sprint 8, Sprint 9, Sprint 10, Sprint 11, Sprint 13 (was: Sprint 8, Sprint 9, Sprint 10, Sprint 11) > Basic Layout for Sankey Diagram > --- > > Key: SENSSOFT-202 > URL: https://issues.apache.org/jira/browse/SENSSOFT-202 > Project: SensSoft > Issue Type: Task >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > Design the basic sankey diagram that can then be converted to fit the TAP > demo site. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-213) Update UserALE.js deployment Instructions
[ https://issues.apache.org/jira/browse/SENSSOFT-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-213: -- Sprint: Sprint 10, Sprint 13 (was: Sprint 10) > Update UserALE.js deployment Instructions > - > > Key: SENSSOFT-213 > URL: https://issues.apache.org/jira/browse/SENSSOFT-213 > Project: SensSoft > Issue Type: Improvement > Components: UserALE.js >Affects Versions: UserALE.js 0.1.0 >Reporter: Michelle Beard >Assignee: Rob Foley > Fix For: UserALE.js 0.1.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > Currently, we need to update some files in userale.js so we are no longer > dependent on our draper GH pages for building, deploying userale, and the > script tag. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-210) Integrate SankeyPlot with Demo Site
[ https://issues.apache.org/jira/browse/SENSSOFT-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore updated SENSSOFT-210: -- Sprint: Sprint 9, Sprint 10, Sprint 11, Sprint 13 (was: Sprint 9, Sprint 10, Sprint 11, Sprint 12) > Integrate SankeyPlot with Demo Site > --- > > Key: SENSSOFT-210 > URL: https://issues.apache.org/jira/browse/SENSSOFT-210 > Project: SensSoft > Issue Type: Task > Components: TAP >Affects Versions: Tap 0.1.0 >Reporter: Arthi Vezhavendan >Assignee: Arthi Vezhavendan > Fix For: Tap 0.1.0 > > Original Estimate: 10h > Remaining Estimate: 10h > > Integrate the sankey plot with live logs from the demo site. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SENSSOFT-229) Fix Histogram Dataset from Distill
[
https://issues.apache.org/jira/browse/SENSSOFT-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua Poore updated SENSSOFT-229:
--
Sprint: Sprint 13 (was: Sprint 12)
> Fix Histogram Dataset from Distill
> --
>
> Key: SENSSOFT-229
> URL: https://issues.apache.org/jira/browse/SENSSOFT-229
> Project: SensSoft
> Issue Type: Task
> Components: TAP
>Affects Versions: Tap 0.1.0
>Reporter: Arthi Vezhavendan
>Assignee: Arthi Vezhavendan
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Fix the histogram dataset created on Distill's end so that it correlates with
> Sankey. This should allow for better filtering between sankey and the
> histograms.
> The main keys the histogram needs are:
> * target
> * path
> * path length
> * an array of the "type" of interaction done on that target
> * an array of the counts correlated with those above type
> For example:
> {code:javascript}
> {"histogram": [
> {"target": "#document",
> "path":"#document home",
> "path-length": 2,
> "types": ["focus", "blur", "resize"]
> "counts": [4, 5, 6]},
> {"target": "#div1",
> "path":"#div1 document home",
> "path-length": 3,
> "types": ["focus", "blur", "resize"]
> "counts": [1, 2, 3]},
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SENSSOFT-233) D3 Sankey Not Redrawing Correctly
[ https://issues.apache.org/jira/browse/SENSSOFT-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reassigned SENSSOFT-233: - Assignee: Ryan Brill (was: Arthi Vezhavendan) > D3 Sankey Not Redrawing Correctly > - > > Key: SENSSOFT-233 > URL: https://issues.apache.org/jira/browse/SENSSOFT-233 > Project: SensSoft > Issue Type: Bug > Components: TAP >Affects Versions: Tap 0.1.0 >Reporter: Arthi Vezhavendan >Assignee: Ryan Brill > Original Estimate: 8h > Remaining Estimate: 8h > > When trying to use the update on filter functionality and transition, > artifacts persist and are not erased, even though they should be gone. > It has to do with these two functions: > * D3’s .exit() is not selecting the right things after the data is passed to > the nodes/rectangles/links > * D3’s remove() function not removing everything that is selected, even > though it should -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SENSSOFT-236) Fix Event-Based Selectors for Sankey
[ https://issues.apache.org/jira/browse/SENSSOFT-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Poore reassigned SENSSOFT-236: - Assignee: Ryan Brill (was: Joshua Poore) > Fix Event-Based Selectors for Sankey > > > Key: SENSSOFT-236 > URL: https://issues.apache.org/jira/browse/SENSSOFT-236 > Project: SensSoft > Issue Type: Bug > Components: TAP >Affects Versions: Tap 0.1.0 > Environment: JavaScript, D3, React.js >Reporter: Joshua Poore >Assignee: Ryan Brill > Fix For: Tap 0.1.0 > > > Need to fix event based filters to select appropriate data streams for > sequential visualization. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SENSSOFT-233) D3 Sankey Not Redrawing Correctly
[ https://issues.apache.org/jira/browse/SENSSOFT-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135823#comment-16135823 ] Joshua Poore commented on SENSSOFT-233: --- issue is in D3 Sankey Exit Selectors > D3 Sankey Not Redrawing Correctly > - > > Key: SENSSOFT-233 > URL: https://issues.apache.org/jira/browse/SENSSOFT-233 > Project: SensSoft > Issue Type: Bug > Components: TAP >Affects Versions: Tap 0.1.0 >Reporter: Arthi Vezhavendan >Assignee: Ryan Brill > Original Estimate: 8h > Remaining Estimate: 8h > > When trying to use the update on filter functionality and transition, > artifacts persist and are not erased, even though they should be gone. > It has to do with these two functions: > * D3’s .exit() is not selecting the right things after the data is passed to > the nodes/rectangles/links > * D3’s remove() function not removing everything that is selected, even > though it should -- This message was sent by Atlassian JIRA (v6.4.14#64029)
