This is a rough spec for the User Workflow laid out in a meeting on 5-18-09.

First, there is a way to register a new user.

1. ???
2. ???
3. There is no spec for this.
4. But presumably, it is as simple as possible, requires no email confirmation, and on the backend just requires a call to the Users REST API.
5. Fields include username, and a couple other simple text fields like Real Name and Organization. Maybe a dummy password?
6. Creating a user should probably sign you in (it's more demoable that way)

Next, there's got to be a way to sign in as a user.

1. Some kind of log in dialogue, triggered by a "Log in" button or link.
2. Input username and password
3. Get logged in. Visual display of which user is logged in.

When somebody is logged in, there should be:

1. The ability to log out.

Next, there's viewing a user profile. How can this user profile get accessed?

• When you see that you are logged in, there should probably be a "view profile" link that shows the profile. (It is kind of stupid to implement profiles if this is the only way to see them)
• When another user is listed (in association with a layer or map, for example), their name should link to a profile. (Do we have any UI elements where people's names are listed in this way? It is not clear from any spec.)

The contents of user profiles:

1. Username
2. Simple text fields like organization, real name (etc.?)
3. A list of maps the user has created (i.e., OWS content documents that the user has saved)
4. A list of layers the user has uploaded.
5. A list of styles the user has made. (This may not be needed for 1.0 since styles can only be created on upload? Or is it? See UploadWorkflow)