Explanation
For my use case, both myself and my partner will be importing out google keeps to our own accounts. However the google takeout includes all notes including ones you don't own.
Right now myself and my partner would end up with duplicate notes of the ones we have shared with each other.
Proposed Solution
I think the ideal solution would be:
- Option to ignore notes that aren't owned by the current user.
- Import shared users so that if I share my note with my partner, it will try to share that note with a user in glass keep with the same name.
Data Examples
Owned
Note that I own and shared with another user. This seems to have a list of sharees where none have the isOwner:true:
This can probably ignore the GROUP type as it doesn't translate to a feature on Glass Keep. However the USER type could try to share with a user that matches. Only concern is Glass Keep has username, not email. So you'd need to set the username to the email.
Shared
Note that another user owns and shares with me. This is where a sharee has the isOwner:true.

Explanation
For my use case, both myself and my partner will be importing out google keeps to our own accounts. However the google takeout includes all notes including ones you don't own.
Right now myself and my partner would end up with duplicate notes of the ones we have shared with each other.
Proposed Solution
I think the ideal solution would be:
Data Examples
Owned
Note that I own and shared with another user. This seems to have a list of sharees where none have the
isOwner:true:This can probably ignore the
GROUPtype as it doesn't translate to a feature on Glass Keep. However the USER type could try to share with a user that matches. Only concern is Glass Keep has username, not email. So you'd need to set the username to the email.Shared
Note that another user owns and shares with me. This is where a sharee has the
isOwner:true.