Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

4660 custom analytics config #5416

Merged
merged 14 commits into from
Jan 11, 2019
Merged

4660 custom analytics config #5416

merged 14 commits into from
Jan 11, 2019

Conversation

mheppler
Copy link
Contributor

Related Issues

Pull Request Checklist

@coveralls
Copy link

coveralls commented Dec 20, 2018

Coverage Status

Coverage decreased (-0.06%) to 17.58% when pulling 8c88ed4 on 4660-custom-analytics-config into 9b4a874 on develop.

Copy link
Member

@pdurbin pdurbin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There seems to be a little unrelated cleanup about compute buttons and such but the core of changes make sense. Approved.

@@ -63,7 +63,7 @@
and !DatasetPage.dataset.deaccessioned
and DatasetPage.showComputeButton()}">
<!-- Compute Button Group -->
<button type="button" id="computeBatch" class="btn btn-default dropdown-toggle" data-toggle="dropdown">
<button type="button" id="computeBatch" class="btn btn-default btn-compute dropdown-toggle" data-toggle="dropdown">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This "compute" change feels a bit unrelated but whatever. Cleanup, maybe?

@@ -598,7 +598,7 @@
<span class="glyphicon glyphicon-pencil"/> #{bundle['file.dataFilesTab.metadata.addBtn']}
</p:commandLink>
<div class="btn-group" jsf:rendered="#{DatasetPage.dataset.released and !DatasetPage.dataset.deaccessioned}" >
<button class="btn btn-default dropdown-toggle" type="button" styleClass="btn btn-default" data-toggle="dropdown">
<button class="btn btn-default btn-export dropdown-toggle" type="button" styleClass="btn btn-default" data-toggle="dropdown">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I guess all of these are cleanup?

@@ -473,7 +473,7 @@
<f:setPropertyActionListener target="#{sendFeedbackDialog.recipient}" value="#{DataversePage.dataverse}"/>
<span class="glyphicon glyphicon-envelope"/> #{bundle['contact.contact']}
</p:commandLink>
<p:commandLink type="button" styleClass="text-button bootstrap-button-tooltip"
<p:commandLink type="button" styleClass="text-button btn-share bootstrap-button-tooltip"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More cleanup?

@mheppler
Copy link
Contributor Author

In reply to code review comments from @pdurbin, those are not "clean up" changes to the buttons, but the addition of new style classes to end user event buttons (e.g. Contact, Share, Compute, Download...) to aid in the tracking of those events with analytics. I had added a comment to the issue regarding the inclusion of them in order to deliver on a user request which was the origin of this custom analytics issue. They were first discussed with @kcondon, who suggested I review it with @djbrooke, who then approved including it in this issue to deliver more value to our sysadmins.

@pdurbin
Copy link
Member

pdurbin commented Dec 20, 2018

@mheppler my mistake. Thanks for the clarification! I see (now) the comment you're talking about: #4660 (comment)

@kcondon kcondon merged commit 36dea68 into develop Jan 11, 2019
@kcondon kcondon deleted the 4660-custom-analytics-config branch January 11, 2019 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants