Last modified by Julian Hurst on 2021/04/21 10:01
Show last authors
1 {{ddtoc/}}
2
3 = Prerequisites =
4
5 * A service account to store documents and a .p12 file (see below)
6 * Follow the tutorial « google_drive_config_en.pdf » to get your configuration data (service account and .p12 file).
7
8 = Creating a new Google Drive documents server =
9
10 Digdash Enterprise allows you to get your documents on a Google Drive service account.
11
12 * Via the Digdash Studio
13
14 To create a new Google Drive document server in the Digdash Studio :
15
16 Open Digdash’s Enterprise Studio > **Tools** > **Server URL manager…** > **New...**
17
18 [[image:google_drive_en_html_716ce981812a4b9b.gif||height="169" width="422"]]
19 \\
20
21 [[image:google_drive_en_html_94926f384710c402.gif||height="131" width="508"]]
22
23
24 //__Screenshot: Creation of a new Google Drive document server__//
25
26
27 * Via the browser
28
29 [[image:google_drive_en_html_1e0029baac8fe94a.png||height="253" width="472"]]
30
31
32 [[image:google_drive_en_html_a7642093cc4034e8.png||height="291" width="486"]]
33 [[image:google_drive_en_html_a7642093cc4034e8.png||height="291" width="486"]]
34 //__Screenshot: Creation of a new Google Drive document server via the browser__//
35
36 = Server configuration =
37
38 * Via the Digdash Studio
39
40 [[image:google_drive_en_html_d71d75d85ec642f7.png||height="287" width="365"]]
41
42
43 //__Screenshot: Server configuration for Google Drive via the Studio__//
44
45
46 * Via the browser
47
48 [[image:google_drive_en_html_e02f9023858c37b2.png||height="347" width="372"]]
49
50
51 //__Screenshot: Server configuration for Google Drive via the browser__//
52
53 == Server name ==
54
55 Give a name to your new Google Drive document server.
56
57 == Google Drive configuration ==
58
59 |**Service account name** :|It’s the account name in an email address form that you got at the creation of the service account in the Google Cloud console.
60 |**P12 file **:|It’s the secret key in a .p12 file form generated and that you downloaded at the creation of the service account in the Google Cloud console.
61 |**Shared with** :|(((
62 In this non-mendatory field, you can mention one or multiple email addresses of users you want to share your Google Drive documents with. Those users will receive a notification (via email) everytime a new document is available on the server. They will also be able to see these documents in their own Google Drive account, in the « Shared with me » section.
63
64 In case of mutiple email addresses, you need to separate them with commas or semicolons.
65 )))
66 |**Convert to Google format:**|If this option is selected, documents will always be uploaded in their matching Google format when possible (Cf appendix 1). If the conversion is not possible, the documents will be uploaded in their original format.
67
68 __**Note :**__
69
70 Even if you created the service account while connected to your own Google account, this service account is not related - in any way - to your own Google Drive account.
71
72 The service account is a Google account in its own right and has its own Google Drive account, its own Google Calendar, etc.
73
74 When uploading to the service account, the document will go to the service account’s Google Drive and not to the Google Drive of the Google account that was used to create the service account.
75
76 (% class="box infomessage" %)
77 (((
78 **NB** : There is no Web interface for a service account, which means that you can’t authenticate and list which documents have been uploaded. This can only be achieved via a client able to use this service account, like Digdash.
79 )))
80
81 = Possible actions =
82
83 Via the browser version of the document manager, you can proceed many actions on your documents on your Google Drive account.
84
85 == Downloading ==
86
87 [[image:google_drive_en_html_e8be82e5671f4612.png||height="321" width="450"]]
88
89
90 //__Screenshot : Downloading a document from__ __Google Drive__//
91
92 It is a basic action. Every connected Digdash user is at least able to read any documents on the server.
93
94 This action is possible via this icon:[[image:google_drive_en_html_814415e769e4e78a.png]] .
95
96
97 == Uploading ==
98
99 [[image:google_drive_en_html_1861f8352928915a.png||height="380" width="624"]]
100
101
102 //__Screenshot: Uploading a document on Google Drive__//
103
104
105 (% class="box infomessage" %)
106 (((
107 __**Note:**__ In Digdash, it is preferable to upload documents with explicit extensions.
108 )))
109
110 Three options are possible:
111
112 * **Choose a local file**: click on **Browse...  **to select the document to add. Click **OK**.**  **The dialog **Open** shows.
113 * **Enter a URL**: Enter the URL of your document. If the checkbox **Only add the URL link to the Documents server **is deselected, the content pointed by the URL is downloaded only just once. If the checkbox **Only add the URL link to the Documents server** is selected, the content will be downloaded by the server every time it needs to (for a data source or required by the user). If required by the user, the URL must be reachable by the server. You can also insert user variables in the URL (${user.uid}, etc. Cf documentation). You can use a URL starting with « file:~/~/ » but in that case, the option **Only add the URL link to the Documents server** is selected by default. This kind of URL should refer to a file on the disk of the server. The link name must end with the extension of the file (.csv, .html, etc.).
114 * **Create a new link**: Create a new link to a document on the server. The pointed file is the last document (alphabetically) corresponding to the link. For example, a link like “document*.csv” will refer to the last CSV file starting with “document”.
115
116 == Updating ==
117
118 [[image:google_drive_en_html_e8f75050c70ebf8f.png||height="282" width="554"]]
119
120
121 //__Screenshot : Updating a document on Google Drive__//
122
123
124 This action is possible via this icon:[[image:google_drive_en_html_64558e71f36001ee.png]] .
125
126 Here are the possible actions:
127
128 === Updating a document content ===
129
130 You are able to update the content of an existing document selecting another file on their file system.
131
132 (% class="box warningmessage" %)
133 (((
134 [[image:google_drive_en_html_adf402587d43fa67.jpg]] This unique action will not alter the document name.
135 )))
136
137 === Renaming ===
138
139 You are able to rename a document. You will specify in the text field the new name without any extension (it remains the same).
140
141 == Deleting ==
142
143 You are able to delete one or several existing documents in the directory specified during the server configuration.
144
145 If the user wants to delete more than one document, they can do it thanks to the check boxes.
146
147 This action is possible via this icon: [[image:google_drive_en_html_98f66c55bdffcaac.png]] .
148
149 **APPENDIX 1 : Possible conversions**
150
151
152
153 |**Type of file**|**Google Format**
154 |doc|(% rowspan="11" %)**Google Docs**
155 |docx
156 |odt
157 |html
158 |rtf
159 |txt
160 |jpg
161 |png
162 |gif
163 |bmp
164 |pdf
165 |xls|(% rowspan="5" %)**Google Sheets**
166 |xlsx
167 |ods
168 |csv
169 |tsv
170 |ppt|(% rowspan="3" %)**Google Slides**
171 |pptx
172 |odp
173
174

Sommaire

DigDash Enterprise [2021R1] User Guides
Deployment
Customisation
Base de connaissances

Copyright ©2006-2023 DigDash SAS