LibraryOfCongress/viewshare — pull request #30 by wamberg (2013-09-10 21:14:18+00:00)
Title: Property editor to DraftExhibit API without augmentation

Click on the 'Edit' button from a view and you'll see the property editor. One thing to note with this pull request, the builder wasn't coming up for me. I know there was recently a flurry of activity to get the datasource upload to redirect to a status screen before redirecting to the builder screen. I'm not sure why that change wasn't working after I pulled loc/develop into this branch. Hopefully it's a small setting I missed or a caching issue. It may be worth pulling this branch and doing an upload check before merging it immediately.

The next step is to build out the augmentation back-end. This involves several additions:

1. Create a viewshare.apps.augment.models.AugmentTransaction. This will be similar to viewshare.apps.augment.models.UploadTransation except it will have a foreign key to a freemix.exhibit.models.ExhibitProperty.
2. There needs to be a view that kicks off an AugmentTransaction. [Looking through our notes](https://github.com/LibraryOfCongress/viewshare/issues/23#issuecomment-21952549) I believe the first GET request to a ...//data/ URL of a that doesn't exist is that view.
3. freemix.exhibit.views.DraftExhibitPropertyDataStatusView needs to check if an AugmentTransaction was successful and return according to the HTTP statuses we outlined [here](https://github.com/LibraryOfCongress/viewshare/issues/23#issuecomment-21969081)
4. viewshare.apps.augment.tasks will have to be finalized. It will look similar to viewshare.apps.upload.tasks but the augmentation function will have to query for a viewshare.apps.augment.models.AugmentTransaction and call .run() on it.

I'll get emails on github through Thursday, Sept. 12th. If you have any questions please feel free to ask.