drive2goruce creates a gource compatible log from the history of a Google Drive folder.
Google Drive's history data is complex. The code here is sufficient to handle the data we threw at it, but there are edge cases and activity types we don't handle; you may need to make some changes to get it to work on your folders. If you do, we'd appreciate if you send a pull request!
This tool currently works on histories up to around 10000 activities (about a year of moderate to heavy activity, in our experience). Anything much longer than that is likely to run out of Google Apps Script memory.
The code here is split between Google Apps Script to get the raw activity data and a local Node.js script to process it into Goruce format; this split allows access to the Google API without dealing with OAuth while also allowing fast local iteration on the tricky conversion code.
- Make sure you have Node.js and Gource installed. The latter is available as
gourcefrom Homebrew and most Linux package managers; Windows builds of Gource are also available, but this script hasn't been tested there. - Find the ID of the Google Drive folder you want to visualize. This will look something like
1RmiS97L0x0k_CQRbK8__Vuqt4X7ijWr7; it can be found by navigating to the folder in the Google Drive web UI and looking at the URL. - Create a Google Apps Script project and paste in the contents of
get-history.js, substituting in the folder ID from the previous step at the top. - In "Services" on the left, add "Drive Activity API" and "Peopleapi", keeping the default options for each.
- Click "Run" at the top.
- If this is the first time, click through the permission prompt. (The script requires permission to read from Google Drive and Google Drive activity for obvious reason; write to Google Drive so we can store the output somewhere, and "access your contacts" to get the names of other editors.)
- When it's done, it'll save a
.ndjsonfile to your My Drive folder, and print the download link; download it. - Run
node history-to-gource.mjs FolderIdFromStep2 path/to/log.ndjson "Your Name" > gource.log.- The last parameter (your name) is only required if you appear in the activity log; Google Apps Script makes it easy enough to get the names of other editors but surprisingly difficult to get your own, so we ask for it manually.
- Run
gource gource.log(plus whatever other Gource parameters you'd like).- See Gource's docs for a full list of parameters. You'll probably want to set
--seconds-per-dayto something less than the default of 10, and--max-file-lag(which limits how long, in seconds, Gource can delay showing an event to make the animation look better) to something close to your--seconds-per-dayto prevent the animation from getting too far out of sync.--high-dpi(Gource v0.53+) is well worth setting if you have a monitor that supports it. - To generate a video (as opposed to viewing the visualization directly in Gource), see Gource's docs.
- See Gource's docs for a full list of parameters. You'll probably want to set
Thank you for considering contributing to an Open Source project of the US Government! For more information about our contribution guidelines, see CONTRIBUTING.md
For more information about our Security, Vulnerability, and Responsible Disclosure Policies, see SECURITY.md.
A full list of contributors can be found on https://github.cms.gov/dsacms/drive2gource/graphs/contributors.
This project is licensed within in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.
All contributions to this project will be released under the CC0 dedication. By submitting a pull request or issue, you are agreeing to comply with this waiver of copyright interest.