atomic-data-docs icon indicating copy to clipboard operation
atomic-data-docs copied to clipboard

New Drives and Agents - registration / onboarding process

Open joepio opened this issue 4 years ago • 1 comments

Drives are top-level nodes in the Hierarchy that you can think of as a hard drive (hence the name). It's a thing that contains other things. In atomic, Drives must give some agent read an write rights.

Currently, drives are created when a server is initialized. I think, Ideally, a drive is created when a user accepts an invite. Either the front-end or the back-end could do this. If the front-end does this, it needs to know that Drives don't have parents, and the back-end should not default to some parent (currently it defaults to the default store). If the back-end does this, we could handle everything in the invite handler. The URL might be ugly, though, at least in the beginning. If we want pretty URLs, we need some sort of form in the front-end.

This new drive form should:

  • Create a link from the Agent to the Drive (in the drives list)

Invites accept usernames

If we add a username option to invites, we can:

  • Create Agents with pretty URLs
  • Create Drives with pretty URLs
  • Return an error if the username is taken

joepio avatar Nov 27 '21 10:11 joepio

Should we always create a Drive for new users? I can imagine that for some servers, this might be overkill. For example, If I'm only filling in some anonymous survey. Creating these Drives might motivate the new users to create all sorts of content, which the server may not want to deal with.

Perhaps creating Drives should be a server setting. Or maybe an invite setting. I don't know.

joepio avatar Dec 11 '21 10:12 joepio