Federated General Assembly » #OWSdirectory

Here are a bunch I put together to work from for the entity / v1 directory modeling... don't know how many admin ones I got to here but there is some material to be had...

http://projects.occupy.net/projects/fga/wiki/UserStoriesBrainDump

I like the personas that Thiago & Andrew have been using in visuals as a start, though I still feel politically required to grumble about 'user' and 'persona' based human representation.

Here's where I also admit that whatever we call it we will still be using a role-centric modeling approach, so...

I think within the scope of this project, we don't need to think of people as having access levels until we determine that fits the workflow.

User stories will depend to some extent on how the site is exposed - as API, dumb listing, or actual resource directory, and what sort of linkbacks we get from downstream parties that are using the data.

I see one possible broad division of "infrastructure builder/maintainer" vs "content curator/creator." The infrastructure person cares that the site URL is right, the content person is sorta motivated by wanting to make sure that their twitterbooktube team is getting exposure.

If we get in touch with folks at occupytogether & wealloccupy (#124) , they may have an opinion on who's reaching out to them to add/correct data.

yikes - @fourth man, sorry, but the scope of the user stories this ticket is intended to refer to is only that for interacting with the directory site. those user stories you linked to are about the whole of FGA. yes, we'll eventually need to connect the dots on the two, but we're trying to keep it simple here.

what i had in mind was something more like:

Personas:

• Anonymous viewers
• Data maintainers
• Site admins

• I want to give general feedback on the appearance of the site
• I want to make a suggestion about the data we capture
• Data for my occupation was imported and I need to gain access to the account that owns it.
• I need to update my occupation's data.

some simple examples there. really, the use here is mapping out all the situations we expect people to be in, on initial launch (and later, moving forward) in terms of getting access to manage their occupation's data, the process they'd go through to get that access, then how they'd actually do those updates.

seems increasingly clear that we need a statement about the purpose of this site and the evolution we see for it over time. we've been talking about it in our little wednesday night huddles, but haven't written it up.

• Project Definition
• Project Specification

I've now expanded the spec to include a section on personas and user stories, which puts our Directory Spec more in line with the Main FGA spec format-wise.

Let's work out the Personas and Stories on the Spec: http://projects.occupy.net/projects/fga/wiki/Occupation_Directory_Specification