Interface to create and edit a Person

See 'Similarity to suspicious messages' at http://support.google.com/mail/bin/answer.py?hl=en&answer=1366858&rd=1

This is higher priority than preventing duplicates organisations, people or positions

"Make your own PopIt politician monitoring website"

Replace instance with "PopIt website"

Change instance slug to "pick a website name"

Only show 4-20 char & alphanumeric on error.

Change "Create site" to "Go"

Offer permissions control via this interface

The Position resource does not currently expand lookups to Person or Organisation - because if you go to the URL for a Person resource, which displays all Positions for that Person, and then have full=True, it will try to display the Person resource nested, continuing down for ever). However, it would be nice to have Organisation full=True when looking up a person, and vice-versa. Some manual method that sets full=True depending upon the request needs to be worked out and written.

I was in a popit presentation with Tom Steinberg and tried to create my own site at the same time as he was creating his on the projector.

Might be because we were sharing the same ip? But at the end I didn't got the confirmation email and Tom ended up owning and entering information in the instance that I was creating.

(confusing?)

I tried creating:
http://thacker.popit.mysociety.org/
and Tom:
http://pmopeople.popit.mysociety.org/

But his entry got loaded in my (thacker) instance and I never got my password. (Hope it's more easy to understand, now?)

Headers and footers that have the basic styling, and accompanying CSS and assets.

Create an app that is able to select the database it should connect to from the domain name used to connect to it, or that is specified in a another way (config file? env variable?)

Should just return a simple diagnostic page saying which db connected, or a 404 page if db could not be found.

Should 404 instead

Currently there is an admin interface and a REST API using tastypie. HTML representation for tastypie should be investigated (the github project has many many forks and issues), or at least some method of documenting the thing, like what mapit currently has for example.

URLs in the API (and IDs output by it) should be in base32.

create a login page that asks for email address and password. If correct creates a session and sets a cookie. If wrong errors. Uses the instance db for the storage

Change wording to copy wording from WriteToThem

Make sure 'check your mail' wording is visually dominant - more so than footer

Make sure wording is clear about instance homepage vs project homepage

Could use http://popit.mysociety.org - but then http://instance.popit.mysociety.org becomes clunky.

Also need to account for mispelling of 'popit' as 'poppet'

Let users change their password and other details on the site.

Currently you can make a query for organisations with a particular data key/value by doing something like /organisation/?data__key__name=KEYNAME&data__value=VALUE - should we try and improve that to something like data__KEYNAME=VALUE? And other similar query parameter lookups like this.

Will need to document what these are and that we may use them to look into any instance for admin purposes, and more?

Do we want to use an ORM to enforce a partial schema? If so which one should we use.

Depends on #23

It would be good if the bits that are output like {"key": {"name": "foo" }, "value": "bar"} could potentially be output simply as {"foo": "bar"}. I think this would be okay in all circumstances, though needs a think. Similarly for person/organisation codes, perhaps.

The drop downs on e.g. an organisation's admin page that lists all members need to be changed to use auto-complete. And probably many other enhancements.

What is the basic structure that we should be storing in the database?

Which requires being logged in, obviously

this lets us serve a single url in the API and then the user can request the image in the format they want. Use Chetan's connect-image-proxy.

Allow users who have forgotten their password to get a reset link emailed to them.

"Fantastic, thanks for confirming your email - now choose the type of first politicians"

Add various different kinds of politician options to this page - president, MP, unelected etc, but grey out all but elected assembly member.

Access the person over the API

For the hosted service what uses will we permit and what caps will be enforce. What do we do if these are exceeded.

possible things to consider:

• maximum size of database (in MB, or number of entries)
• API/web usage - number of hits, data transferred.
• data stored - just democracy related or will we host celebrities too? What won't we host?

Page that asks the user for their preferred instance name, email and password. Check that the instance name is valid and available. If so creates the instance for them and then redirects them to the login page.

In the background will have created the instance database and saved their credentials to it.

MongoDB?

We might want to stop hosting some sites because they are not used or not suitable. What are our criteria for doing this?

• Site access/month falls below certain number?
• data stored of no value and not being maintained?
• site not being maintained so serving stale or wrong data?

Temporarily, but makes doing the demos easier.

We need o framework for both the hosting site (that spawns new instances) and the instances themselves. Would seem sane to make it the same for both.

Deciding on an ORM in #24 will have a bearing as it will set the programming language used.

Ensure that this suggestion is implemented:

Make sure you include sources i.e. make it fundamental in the user interface that people put the URL and/or a text description of where they got data from.

This is vital for provenance and for later data updating. And most importantly, for the user interface to add credibility to sites made using the data.