Closed Bug 1173006 Opened 9 years ago Closed 7 years ago

Need public view available for SeaMonkey statistics

Categories

(Data & BI Services Team :: Other, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: iannbugzilla, Assigned: Shraddha)

References

()

Details

There used to be a public view available for the SeaMonkey ADI (see URL) but it now prompts for a SSO login. How do we get the public view back?
Hi Ian, 

Tableau is now setup with SSO. So if you have any volunteers accessing Tableau, they have to be setup an SSO and there is no difference in terms of user setup.

Before SSO was implemented in Tableau, we (in data team) would need to create the user in Tableau. 
After SSO, we (in data team) need to create the user in Tableau and add them to SSO. 

I guess I don't understand what public means to you. Do you mean you can just share the link to anybody without them being setup in Tableau? Are we allowed to make public our data outside of the organization? 

Cc-ing Callek on this bug as well.
We (SeaMonkey Team) would like to make available one or more sanitized views that could be viewed by the public without having to sign-up/login/ or anything. This used to be possible several iterations ago (arranged by Callek). However currently we are unable to discern the way to produce and display such public views.
Flags: needinfo?(jtanumijaya)
Callek, I'd like to get your views on this:

1. What does it mean by "more sanitized" views?
2. I will need somebody from the team who can sign off and authorize the access to public.

Thanks,
Josephine
Flags: needinfo?(jtanumijaya) → needinfo?(bugspam.Callek)
1:
I can let Ratty dictate what this means (he is authorized to help dictate this data being accessible), but for my own mind an ideal would be:
  * An textfile database, e.g. json, csv, or xml 
  * With a seperate file for:
       * ADI, by date (24-hour specific) [Active Daily Installations as tracked by add-on blocklist update requests] with fields for "Total" and each version associated with it (no "other" just full count, e.g. if we have 20 users on a version, I want that version specified)
       * (Tracked) manual downloads (no updates) as measured via download.m.o ("bouncer") HTTP logs (all SeaMonkey versions) -- with the same fields
   * Chunking of the data is ok (by month, year, etc.) as long as the filename is programmatically discoverable [e.g. 2015-04-adi.csv]
Again this data should be accessible outside of any login, and Ratty can extend the scope of my answer if he feels a need.

2: I can officially signoff on the data being public in a raw form like that. I can also officially signoff on Ratty [or IanN from c#0] asking for more data than that to be public.
Flags: needinfo?(bugspam.Callek)
Assignee: nobody → jtanumijaya
Assignee: jtanumijaya → spatil
Hello Ian,

We are revisiting old Tableau bugs and stumbled upon this. A quick question is this still needed or resolved?
Flags: needinfo?(iann_bugzilla)
Yes, we would still like the information as specified in comment 4 made available publicly. Thanks.
Flags: needinfo?(iann_bugzilla)
(In reply to Ian Neal from comment #6)
> Yes, we would still like the information as specified in comment 4 made
> available publicly. Thanks.

HI Justin/Ian,

Thank you for the response. Can i suggest to meet and get this closed out?
Flags: needinfo?(iann_bugzilla)
Flags: needinfo?(bugspam.Callek)
Awaiting response.
Passing the n-i to me over to :ewong, I'm not involved in SeaMonkey enough these days to own any sense of a story here.
Flags: needinfo?(bugspam.Callek) → needinfo?(ewong)
(In reply to Justin Wood (:Callek) from comment #9)
> Passing the n-i to me over to :ewong, I'm not involved in SeaMonkey enough
> these days to own any sense of a story here.

Just getting my bearings here; but, a long time ago (>5 years), the ADI page was available
for all to see without the need to log in(IIRC). 

The 'public' scope as mentioned by Ratty, would probably refer to the ability to look up
that SeaMonkey ADI page without needing to log in.  what I'm curious to know is prior to
SSO-izing the ADI information, weren't they accessible by anyone?

Comment #4 seems to point out what is needed.
Flags: needinfo?(ewong)
I've updated the URL, but it is basically what :ewong just said
It would also be useful to allow :ewong access on his credentials too.
Got it. Thanks for the clarification. I have added Edmund Wong to Seamonkey Group to be able to access the views under it. Thsi should be working, if not let me know.

Please close the bug in case it works as expected. Thank you.
(In reply to Shraddha Patil [:Shraddha Patil] from comment #12)
> Got it. Thanks for the clarification. I have added Edmund Wong to Seamonkey
> Group to be able to access the views under it. Thsi should be working, if
> not let me know.
> 
> Please close the bug in case it works as expected. Thank you.

Ok, looks like I've got access now.  Thanks Shraddha!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.