Docs integration into ERP

[AbdealiLoKo]

Trying to use Google drive in ERP for basic file management.

[shahidhk]

Basic integration is done.

Regarding sharing, what is best? Make doc public, and "Accessible to anyone having url" or share individually?

Both are possible in the API

[paranoidsp]

Make it accessible to everyone with the URL, and use your own methods to control URL access. That way you can have secret docs when required. On Apr 14, 2014 1:03 PM, "Shahidh K Muhammed" notifications@github.com wrote:

Basic integration is done.

Regarding sharing, what is best? Make doc public, and "Accessible to anyone having url" or share individually?

Both are possible in the API

Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339742 .

[shahidhk]

Control URL access? you mean showing URL only, right? or masking the URL with some other encoding?

On Mon, Apr 14, 2014 at 1:06 PM, Karthikeya Viswanath < notifications@github.com> wrote:

Make it accessible to everyone with the URL, and use your own methods to control URL access. That way you can have secret docs when required. On Apr 14, 2014 1:03 PM, "Shahidh K Muhammed" notifications@github.com wrote:

Basic integration is done.

Regarding sharing, what is best? Make doc public, and "Accessible to anyone having url" or share individually?

Both are possible in the API

Reply to this email directly or view it on GitHub< https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339742

.

— Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339937 .

Shahidh K Muhammed Undergraduate Student Department of Engineering Design Indian Institute of Technology Madras Chennai 600036 Mobile: (+91) 9496362472 http://shahidhkmuhammed.in

[paranoidsp]

Either works, but I'd prefer masking the URL so that only the admin of that particular doc controls the sharing. On Apr 14, 2014 1:08 PM, "Shahidh K Muhammed" notifications@github.com wrote:

Control URL access? you mean showing URL only, right? or masking the URL with some other encoding?

On Mon, Apr 14, 2014 at 1:06 PM, Karthikeya Viswanath < notifications@github.com> wrote:

Make it accessible to everyone with the URL, and use your own methods to control URL access. That way you can have secret docs when required. On Apr 14, 2014 1:03 PM, "Shahidh K Muhammed" notifications@github.com

wrote:

Basic integration is done.

Regarding sharing, what is best? Make doc public, and "Accessible to anyone having url" or share individually?

Both are possible in the API

Reply to this email directly or view it on GitHub<

https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339742

.

Reply to this email directly or view it on GitHub< https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339937>

.

Shahidh K Muhammed Undergraduate Student Department of Engineering Design Indian Institute of Technology Madras Chennai 600036 Mobile: (+91) 9496362472 http://shahidhkmuhammed.in

Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40340065 .

[AbdealiLoKo]

Two questions and an idea :

1. In your UI, does the "Share" button come from google also ? If so, people will get confused.
2. Were you able to do the api version where you can only access by oauth ?

Idea : Can you change a google doc's permissions using the API ? If so, then essentially, Doc sharing is easy and can be done via gmail emails but the sharing will be done through a good interface on ERP (like, you login via gmail to get into ERP level .. .as youre already logged in with gmail, you can continue with viewing as long as ur logged in)

On Mon, Apr 14, 2014 at 1:11 PM, Karthikeya Viswanath < notifications@github.com> wrote:

Either works, but I'd prefer masking the URL so that only the admin of that particular doc controls the sharing. On Apr 14, 2014 1:08 PM, "Shahidh K Muhammed" notifications@github.com

wrote:

Control URL access? you mean showing URL only, right? or masking the URL with some other encoding?

On Mon, Apr 14, 2014 at 1:06 PM, Karthikeya Viswanath < notifications@github.com> wrote:

Make it accessible to everyone with the URL, and use your own methods to control URL access. That way you can have secret docs when required. On Apr 14, 2014 1:03 PM, "Shahidh K Muhammed" < notifications@github.com>

wrote:

Basic integration is done.

Regarding sharing, what is best? Make doc public, and "Accessible to anyone having url" or share individually?

Both are possible in the API

Reply to this email directly or view it on GitHub<

https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339742

.

Reply to this email directly or view it on GitHub<

https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339937

.

Shahidh K Muhammed Undergraduate Student Department of Engineering Design Indian Institute of Technology Madras Chennai 600036 Mobile: (+91) 9496362472 http://shahidhkmuhammed.in

Reply to this email directly or view it on GitHub< https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40340065

.

Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40340274 .

[paranoidsp]

Something along those lines is better. On Apr 14, 2014 1:23 PM, "AbdealiJK" notifications@github.com wrote:

Two questions and an idea :

1. In your UI, does the "Share" button come from google also ? If so, people will get confused.
2. Were you able to do the api version where you can only access by oauth ?

Idea : Can you change a google doc's permissions using the API ? If so, then essentially, Doc sharing is easy and can be done via gmail emails but the sharing will be done through a good interface on ERP (like, you login via gmail to get into ERP level .. .as youre already logged in with gmail, you can continue with viewing as long as ur logged in)

On Mon, Apr 14, 2014 at 1:11 PM, Karthikeya Viswanath < notifications@github.com> wrote:

Either works, but I'd prefer masking the URL so that only the admin of that particular doc controls the sharing. On Apr 14, 2014 1:08 PM, "Shahidh K Muhammed" notifications@github.com

wrote:

Control URL access? you mean showing URL only, right? or masking the URL with some other encoding?

On Mon, Apr 14, 2014 at 1:06 PM, Karthikeya Viswanath < notifications@github.com> wrote:

Make it accessible to everyone with the URL, and use your own methods to control URL access. That way you can have secret docs when required. On Apr 14, 2014 1:03 PM, "Shahidh K Muhammed" < notifications@github.com>

wrote:

Basic integration is done.

Regarding sharing, what is best? Make doc public, and "Accessible to anyone having url" or share individually?

Both are possible in the API

Reply to this email directly or view it on GitHub<

https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339742

.

Reply to this email directly or view it on GitHub<

https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40339937

.

Shahidh K Muhammed Undergraduate Student Department of Engineering Design Indian Institute of Technology Madras Chennai 600036 Mobile: (+91) 9496362472 http://shahidhkmuhammed.in

Reply to this email directly or view it on GitHub<

https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40340065

.

Reply to this email directly or view it on GitHub< https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40340274

.

Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40341101 .

[shahidhk]

The sharing should be done individually to email.

1.Share button wont come.

2. What I am doing is that, all document will be created by the FEST-API in its own Drive. Then sharing can be done with whoever's email, programmatically, and link can be displayed. Now, when the other user, open the document, he can edit on his behalf only, not on festapi's.

In this way, ownership will be with fest api, but we can give whatever access to whoever required.

[AbdealiLoKo]

Peace and cool :)

On Mon, Apr 14, 2014 at 1:50 PM, Shahidh K Muhammed < notifications@github.com> wrote:

The sharing should be done individually to email.

1.Share button wont come.

2. What I am doing is that, all document will be created by the FEST-API in its own Drive. Then sharing can be done with whoever's email, programmatically, and link can be displayed. Now, when the other user, open the document, he can edit on his behalf only, not on festapi's.

In this way, ownership will be with fest api, but we can give whatever access to whoever required.

Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40342850 .

[shahidhk]

For browsing files, embedding the iframe is enough. But, in order to upload a file to a specific location? We need to know our current directory position, which i frame wont give. Will it? Also, it wont give a browser functionality. It will just open the files/folder in a new window

So, I found out two alternatives: A js library: http://arkadiyk.github.com/ember-google-drive-browser/

and another API called PICKER https://developers.google.com/picker/

https://docs.google.com/picker?view=(%27folders%27,+null,+%7B%27selectFolder%27:+true%7D)

Which one will be better?

I think the both will require equal amount of effort put in to make it work

[AbdealiLoKo]

Agree ... Can you start working on it ?

I'll continue as soon as I finish working on the things im doing atm

On Mon, Apr 14, 2014 at 3:30 PM, Shahidh K Muhammed < notifications@github.com> wrote:

For browsing files, embedding the iframe is enough. But, in order to upload a file to a specific location? We need to know our current directory position, which i frame wont give. Will it? Also, it wont give a browser functionality. It will just open the files/folder in a new window

So, I found out two alternatives: A js library: http://arkadiyk.github.com/ember-google-drive-browser/

and another API called PICKER https://developers.google.com/picker/

https://docs.google.com/picker?view=(%27folders%27,+null,+%7B%27selectFolder%27:+true%7D)

Which one will be better?

I think the both will require equal amount of effort put in to make it work

Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40350016 .

[paranoidsp]

Picker is the standard way of doing this. On Apr 14, 2014 3:36 PM, "AbdealiJK" notifications@github.com wrote:

Agree ... Can you start working on it ?

I'll continue as soon as I finish working on the things im doing atm

On Mon, Apr 14, 2014 at 3:30 PM, Shahidh K Muhammed < notifications@github.com> wrote:

For browsing files, embedding the iframe is enough. But, in order to upload a file to a specific location? We need to know our current directory position, which i frame wont give. Will it? Also, it wont give a browser functionality. It will just open the files/folder in a new window

So, I found out two alternatives: A js library: http://arkadiyk.github.com/ember-google-drive-browser/

and another API called PICKER https://developers.google.com/picker/

https://docs.google.com/picker?view=(%27folders%27,+null,+%7B%27selectFolder%27:+true%7D)

Which one will be better?

I think the both will require equal amount of effort put in to make it work

Reply to this email directly or view it on GitHub< https://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40350016

.

Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40350443 .

[shahidhk]

I will start working on Picker then. Anyway, both are js only

[shahidhk]

The migrations is docs have cupped, and I mistakenly pushed them. Can u reset the migration? Also, check the management command, It snot completely done.

[AbdealiLoKo]

It says there are no migrations available for docs ... Should I make them ?

On Wed, Apr 16, 2014 at 7:05 AM, Shahidh K Muhammed < notifications@github.com> wrote:

The migrations is docs have cupped, and I mistakenly pushed them. Can u reset the migration? Also, check the management command, It snot completely done.

Reply to this email directly or view it on GitHubhttps://github.com/The-WebOps-Club/fest-api/issues/28#issuecomment-40554416 .

[shahidhk]

Ya. I have a few more changes in mind.

1. Change the ForeignKey in model, its useless.
2. Instead of storing in db, save as string in settings.py. Tell me when you are working. I can complete this by 5pm only.

[shahidhk]

This is what I was trying to do

• We need the access credentials including the refresh token in hand and needs to exchange it for access token every time we call the API. So, I wrote a management command (not complete yet) which will read email, scope and other parameters from settings and get the refresh token along with other credentials. This is then displayed to be saved in settings file, as well as saved in db as backup. So, we need to read the settings variable to get the token.
• apps/docs/api.py has some of the functions that calls the API. This functions are utilized from the views to get things done.
• Google Picker has to be implemented for selecting as well as browsing files. (not yet started)

There are some redundant links and views which I wrote for testing out, not yet removed.

Will work on this today evening. @AbdealiJK Let me know if you are making any changes

[AbdealiLoKo]

• [x] - view files
• [x] - open/edit files (online google docs)
• [x] - upload files
• [x] - create files
• [x] - rename files
• [x] - download files
• [ ] - permissions

[Phoenix25]

aside from permission handling... the remaining have been implemented except for

• [x] - delete folders.
• [ ] - create blank doc.( function ready, linking leftover )

[AbdealiLoKo]

This doesn't look very nice :D

@Phoenix25 : Can we sit sometime today for about an hour so you can quickly explain the code to me ? And I'll fix the frontend tonight ? (As you said, the mixture of bs 1 and 2 is confusing, so ill do it ... itll be easier for you)

[shahidhk]

@mhtkmr54 Create a field called drive_folders in ERPProfile and save all the related folders into it as a parsable string (see json.dumps and json.loads).

Use a function to populate this field, which will be called whenever some change happens

[AbdealiLoKo]

As this idea is packed - closing it.