# Google Workspace: Drive file listing

**URL:** <https://community.metaspike.com/t/google-workspace-drive-file-listing/1896>\
**Category:** eDiscovery\
**Created:** [February 26, 2024, 5:11pm UTC](https://community.metaspike.com/t/google-workspace-drive-file-listing/1896 "2024-02-26T17:11:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lars.schou](https://community-cdn.metaspike.com/user_avatar/community.metaspike.com/lars.schou/32/488_2.png) [@lars.schou](https://community.metaspike.com/u/lars.schou)\
**Post date:** [February 26, 2024, 5:11pm UTC](https://community.metaspike.com/t/google-workspace-drive-file-listing/1896/1 "2024-02-26T17:11:43Z")

</div>

We have a client with approximately 10 TB of Drive data in their corporate Google Workspace, which they would like to generate file listings of.

Importantly, they want the paths included, which would seem to rule out using Google Vault.

Any suggestions for scripts or tools?

---

<div class="post-metadata">

**Author:** ![Greg](https://community-cdn.metaspike.com/letter_avatar_proxy/v4/letter/g/71c47a/32.png) [@Greg](https://community.metaspike.com/u/Greg)\
**Post date:** [February 29, 2024, 10:09pm UTC](https://community.metaspike.com/t/google-workspace-drive-file-listing/1896/2 "2024-02-29T22:09:47Z")

</div>

One of these projects should do it.

> **[GitHub - odeke-em/drive: Google Drive client for the commandline](https://github.com/odeke-em/drive)**
>
> Google Drive client for the commandline. Contribute to odeke-em/drive development by creating an account on GitHub.

> **[Build software better, together](https://github.com/topics/google-drive-api)**
>
> GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.

My gut feeling is that @agungor has a preferred library for interfacing with Google that he likely has already used in his products. Perhaps he can point you at what library he has had the most success with. I imagine that you can solve this problem with a little custom scripting and a good library to lean on.

---

<div class="post-metadata">

**Author:** ![mgray](https://community-cdn.metaspike.com/letter_avatar_proxy/v4/letter/m/a88e4f/32.png) [@mgray](https://community.metaspike.com/u/mgray)\
**Post date:** [March 4, 2024, 3:02am UTC](https://community.metaspike.com/t/google-workspace-drive-file-listing/1896/3 "2024-03-04T03:02:34Z")

</div>

I’d generally utilise the listing commands in rClone to accomplish this in the easiest way possible. I prefer using rClone because it allows you the ability to set up the remove either including libraries shared with a user or not.

---

<div class="post-metadata">

**Author:** ![agungor](https://community-cdn.metaspike.com/user_avatar/community.metaspike.com/agungor/32/719_2.png) [@agungor](https://community.metaspike.com/u/agungor)\
**Post date:** [March 4, 2024, 6:16pm UTC](https://community.metaspike.com/t/google-workspace-drive-file-listing/1896/4 "2024-03-04T18:16:36Z")

</div>

> [@Greg](#):
>
> My gut feeling is that @agungor has a preferred library for interfacing with Google that he likely has already used in his products

The first place to look would be Google’s official API client libraries:

> **[API Client Libraries  |  Google for Developers](https://developers.google.com/api-client-library)**
>
> Access the client libraries that make coding against the APIs for Google products easier. Includes support for Java, Python, PHP, .NET, and more.

---

<div class="post-metadata">

**Author:** ![agungor](https://community-cdn.metaspike.com/user_avatar/community.metaspike.com/agungor/32/719_2.png) [@agungor](https://community.metaspike.com/u/agungor)\
**Post date:** [March 4, 2024, 6:38pm UTC](https://community.metaspike.com/t/google-workspace-drive-file-listing/1896/5 "2024-03-04T18:38:19Z")

</div>

Another similar option might be to use [Mountain Duck](https://mountainduck.io/) to mount Drive as a volume. I like that Mountain Duck is able to mount in a read-only manner.

A general warning about using a third-party tool to mount Drive as a volume: some tools do not display any files / folders (including anything within the folders) if the file or folder contains characters that would be invalid in the target file system.

For example, I have a test Drive folder with the `|` character in its name with more subfolders and files within (we use this as one of our tests in FEC’s Drive attachment workflow). When I mount Drive as a volume on Windows with Mountain Duck, that entire folder tree is absent until/unless I rename the folder and get rid of the special character. Same applies to individual files. This would be a non-issue if you interrogate Drive API directly and get a list of the items without mounting anything. Generally, the more middle-men you have, the more potential problems 😁
