Google Drive is a way to store your files on Google's servers, or in the Cloud. If you run the free Google Drive application, then you get a folder on your computer (Windows or Mac OS X) that looks just like a directory on your hard disk that you can drag your files in to. Anything stored in that folder is kept on your hard disk and is also copied to your account in the cloud. You can access those files through drive.google.com or from other computers, including mobile devices.
Google Drive file storage offers users a number of features:
- flexibility: the synchronization can be performed from different devices or using the web version.
- free 5 MB storage by default: can be extended with pay option
- usable as backup service
- your resources are encrypted
ODS Briefcase offers a new "GDrive" folder type which provides several additional features, once the ODS system is configured with a registered Google API key and secret pair:
- Specify credentials for authentication against Google Drive, enabling retrieval of any or all of your folders and files, including any associated metadata
- Specify which Sponger Extractor Cartridges and Sponger Meta Cartridges should be run against your GDrive data
- Save fetched data, metadata, and Sponger output, into a newly created GDrive-specific RDF Graph in the Virtuoso RDF Quad Store
- Specify other ODS Users or
WebID-based ACLs which should be granted access to your GDrive data through ODS Briefcase
Here is a sample scenario showing the whole process, from setting the Google Drive API key and secret pair in ODS, to retrieving all Google Drive content to ODS Briefcase.
- A Google user account, configured with Google Drive access
- Files and folders (data) stored in your Google Drive Space
- Administrative (DBA) access to a Virtuoso Server instance, on which the following have been installed --
- Browse to Google Developer Console, and log in with your existing Google user credentials
- If this is your first Google API Project, click the Create Project button:
- If you already have some Google API Projects, select Create Project from the Project menu.
- Make sure you have your project picked, then click Create Credentials and choose OAuth client ID:
- A form will appear on the next page.
For the Application Type, choose Web application.
Edit the Authorized Redirect URI to contain ODS Callback URL: https://[Host][Port]/val/api/thirdparty_callback
- Click Create and you?ll receive a Client ID and Client Secret.
Save these values to use later.
You?ll need them for all of your application?s interactions with Google.
- Select Library to choose the needed APIs
- Select and enable Google Drive API
- Browse to your Virtuoso + ODS instance,
http://<cname>[:<port>]/ods, e.g., <http://example.com/ods/>, and click Sign In.
- Log in as a Virtuoso+ODS user with Administrator privileges, e.g.,
- Click on Site Settings:
- Click on Login Authentication Keys:
- Select Google API in the API Name menu, provide the Email address and Client secret from the new Client ID for web applications you created above, and click Add.
- ODS-Briefcase is now configured to use the Google API.
- Browse to your Virtuoso + ODS instance,
http://<cname>[:<port>]/ods, e.g., <http://example.com/ods/>.
- Log in as a Virtuoso+ODS user with normal privileges, e.g.,
- Click to the ODS-Briefcase application:
- Click New Folder from the main Briefcase control strip:
- In the New Folder form, specify a Folder Name, e.g.,
MyGoogleDriveFolder, and set the Folder type to Google Drive:
- Click to the newly visible Google Drive tab:
- All RDF data extracted from and otherwise collected about your Google Drive files will be saved to a named graph, where the default name is constructed from the host ODS instance, the ODS username, and the Briefcase folder name --
http://<host>[:<port>]/DAV/home/<user-name>/<folder-name>#this-- so, in this example, the default graph would be named <http://example.com/ods/demo/MyGoogleDriveFolder#this>. Expert users may wish to change this graph name, but the default is suitable for most users.
- You can also turn on the Virtuoso Sponger, to process your Google Drive files more comprehensively.
When the Sponger is enabled for your folder, you can specify which "Sponger Extractor Cartridges" and "Sponger Meta Cartridges" will be run over the files in your Google Drive.
You can enable all cartridges, but this will introduce some processing overhead.
It's generally best to enable only those cartridges which will be applicable to your files and their content.
For instance, you may know that you'll only be storing Microsoft and Open Office documents here.
Then, click "Authenticate", to connect your new folder to your Google Drive:
- You'll be prompted to enter your Google Drive user's credentials.
Note that this Google Drive user need not be the application owner/"developer" who got the API key earlier.
- Google will prompt for confirmation that you intend to let your application ("MyODSGoogleDrive?") have access to your Google Drive content.
Click Allow access.
- Your Google user name and associated email address will now be displayed.
Click Create to finish the folder creation process.
- Your new Google Drive-linked folder should now be displayed in your Briefcase resources list:
- Click the folder name to see the resources ODS-Briefcase has found in your Google Drive Dataspace:
- How Linked Data & WebID Deliver Controlled Access to Resources in Google Drive, Microsoft OneDrive (formerly SkyDrive), DropBox, Box.Net, and Amazon S3
- Guide how to register Google Application
- Using ODS-Briefcase to mediate access to data stored on Amazon S3
- Using ODS-Briefcase to mediate access to data stored on Box (a/k/a box.com or box.net)
- Using ODS-Briefcase to mediate access to data stored on DropBox
- Using ODS-Briefcase to mediate access to data stored on Microsoft OneDrive (formerly SkyDrive)
- Manage different Briefcase type folders in Briefcase
- Virtuoso Sponger
- OpenLink-supplied Virtuoso Sponger Cartridges
- Supported Meta Cartridges in Virtuoso
- Meta Cartridges Usage via REST Request
- Parameterized Examples of Meta Cartridge Usage via REST Request