Talk:Data Migration Process and Considerations
Post and Comment data
- Your post and comment data will appear in Google-markup format. This includes _italic_ and *bold* markup, as well as internal Google profile references. I don’t recall their format, but references may not be directly translatable.
Are you sure this information isn't based on the *old* Takeout data format? Unless I'm missing something in the current JSON files, formatting of posts is currently only available in HTML format.
- I'm not at all certain of this. I haven't used Google Data Takeout in some years, likely since ~2013. --Dredmorbius (talk) 17:31, 26 October 2018 (CEST)
While the old takeout json contained an 'originalContent' key/value pair, which did contain the markdown-like formatting, the current json files only contain the 'content' key/value pair which contains HTML-formatted content, which just uses b and i tags for bold and italic formatting. --FiXato (talk) 02:36, 26 October 2018 (CEST)
- Thanks. My recollection was that Google were using specific, minified CSS classes for bold and italic, rather than sane markup. If they've stopped that particular idiocy, so much the better. (I'm more familiar with Google's CSS horrors than Data Takeout, presently --Dredmorbius (talk) 17:31, 26 October 2018 (CEST)
Takeout Data Structure
I've added a section about the Takeout Data (JSON) Structure, and specifically one about Post Activity data. This likely should go on a page of its own, however I'll leave the naming and categorisation of that up to Dr. Edward Morbius. It's probably a good idea to create a single page for each resource (such as Post Activity, Photo Activity, Photo Metadata, etc), and put them all in a single Takeout Data Structure category, but we might want to wait with that till we've documented the structures of more than 1 takeout file, so we have a better idea of how to categorise/structure it. --FiXato (talk) 05:27, 26 October 2018 (CEST)
Good work, though to keep the sensory overload to a minimum that should be moved off to its own page in future. Go ahead and develop that in place for now.
(There's already far too much sensory overload here, most of it my fault.)
As I'd threatened to do ;-) above, I've abstracted the Google Takeout Data Structure content to its own page. Been planning that for a while now.