yangchongze00 / google-gdata

Automatically exported from code.google.com/p/google-gdata
0 stars 0 forks source link

Unable to differenciate the file is linked or moved into the parent folder. #390

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create a Google document for example TestDoc.txt.
2. Select "All Items" and select TestDoc.txt and link it to a folder called for 
example "TestFolder".
3. Select "My Folders" and select "TestFolder" then select the "TestDoc.txt", 
now you can see the "Move to", select a folder called for example "TestFolder2" 
to move the file.
4. Now the document is moved to "TestFolder2".

At this stage if you delete the folder the file also getting deleted, but not 
when it linked. So we need a way to find out whether the file is linked or 
moved, alternatively whether the parent folder is linked or real parent.

What is the expected output? What do you see instead?
Must be able to identify the file is linked or moved from the feed. But the 
feed entry doesn't have any information to identify this.

Please use labels and text to provide additional information.
From the feed entry, the category XML node must be tweaked with more info to 
identify the file is really moved or just linked.

The delete works differently when the file is linked or moved. So the 
information must be present in the feed.

Original issue reported on code.google.com by anbu.me...@gmail.com on 8 Jun 2010 at 4:51

GoogleCodeExporter commented 8 years ago
Just for clarification. Do you want the .NET API to expose existing data, 
because it currently does not, or do you want the service to add data to the 
feed to make this possible. If it is the later, this should be filed against 
the service itself...

Original comment by fman...@gmail.com on 10 Jun 2010 at 3:47

GoogleCodeExporter commented 8 years ago
The feed from server currently doesn't expose this information, so we cannot do 
anything with the .NET API until this get resolved by the service.

If you could guide me to the right forum, then I'll file the case against the 
service. Once it resolved then I'll come back again to request the 
implementation in .NET API.

Thanks for your clarification.

Original comment by anbu.fre...@gmail.com on 10 Jun 2010 at 4:57

GoogleCodeExporter commented 8 years ago

Original comment by ccherub...@google.com on 18 Mar 2011 at 1:37