Closed
Bug 1161872
Opened 11 years ago
Closed 11 years ago
Verify data mapping from e.me data to zamboni
Categories
(Marketplace Graveyard :: General, enhancement, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2015-06-02
People
(Reporter: ddurst, Assigned: mat)
References
Details
(Whiteboard: [qa-])
Before we run the import job on the majority of the e.me data, we should verify the data mapping and results using the (highly-scrutinized, approved, and small) initial data that Thomas, Adora, Lindsay, and everyone else has created prior to the temps' work.
| Reporter | ||
Comment 1•11 years ago
|
||
Putting some notes here about data mapping wrt e.me data spreadsheets. It's important to remember that they're starting from presumed "mobile URLs" (via e.me data) and focusing on reflecting the MOBILE information:
* if a 'desktop URL' is responsive and there is no mobile-specific URL, the record is noted as responsive=Y, and the 'desktop URL' is put into the mobileURL field only (desktopURL is left blank).
* if a 'desktop URL' redirects to a mobile-sprecific URL, the record is noted as responsive=R, and the 'desktop URL' is put into the mobileURL field (desktopURL is left blank).
* if a desktopURL is not blank, responsive=N, and mobileURL is blank -- we won't enter that data.
* it's presumed that we will not see a record in which desktopURL is not blank, responsive=Y, and mobileURL is not blank (and is not equal to desktopURL). If that happens, we should log it and skip it.
| Reporter | ||
Updated•11 years ago
|
Severity: normal → enhancement
Priority: -- → P1
| Assignee | ||
Comment 2•11 years ago
|
||
I've been working on the import script in bug 1161871 and logging all suspicious data, then fixing it. https://docs.google.com/spreadsheets/d/1CPrPQ4xVsbll_vp_Bca0iWkTgg2nx7WrhCprVHwS-6Y/edit#gid=304044273 should be clean and match our model perfectly now.
Assignee: nobody → mpillard
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
| Assignee | ||
Updated•11 years ago
|
Target Milestone: --- → 2015-06-02
You need to log in
before you can comment on or make changes to this bug.
Description
•