Closed
Bug 1005985
Opened 12 years ago
Closed 12 years ago
Include additional ontologies/categories/classification for improving research algorithms
Categories
(Content Services Graveyard :: General, defect)
Content Services Graveyard
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Mardak, Unassigned)
References
Details
1. Goal
* To better understand the pros/cons of various ways to analyze browsing history, we'll need to implement and package various different types of analysis with the study. This includes more complex ontologies that might be hierarchical or simpler by classifying to just domains or just keywords.
2. Acceptance Criteria (AC)
* Deploy study updates that include additional types of history analysis
* Ensure submitted data is usable for offline analysis
* Follow the privacy guidelines set in the study's privacy policy
3. Notes/Supporting Documentation
* Previously computed ODP: https://github.com/mozilla/prospector/blob/master/aboutProfile/data/categories.txt
* Source ODP http://www.dmoz.org/
* Blekko slashtags https://raw.githubusercontent.com/blekko/slashtag-data/master/slastag.json
* Classifying to domains or classifying to keywords (e.g., meta description or titles) might need to be differently hashed per user for submission
Flags: firefox-backlog+
| Reporter | ||
Updated•12 years ago
|
Component: Firefox Operations → Content Services
Product: Tracking → Mozilla Services
Version: --- → unspecified
Updated•12 years ago
|
Whiteboard: p=13 s=it-32c-31a-30b.1 [story] [qa-] → p=13 s=it-32c-31a-30b.1 [qa-]
Updated•12 years ago
|
Whiteboard: p=13 s=it-32c-31a-30b.1 [qa-] → p=13 s=it-32c-31a-30b.2 [qa-]
| Reporter | ||
Comment 1•12 years ago
|
||
We'll be tracking research stuff outside of the backlog.
Assignee: mzhilyaev → nobody
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Flags: firefox-backlog+ → firefox-backlog-
Resolution: --- → INVALID
Whiteboard: p=13 s=it-32c-31a-30b.2 [qa-]
| Assignee | ||
Updated•11 years ago
|
Product: Mozilla Services → Content Services
You need to log in
before you can comment on or make changes to this bug.
Description
•