document data model changes required in readme
Adds new editor and associate editor roles to the auth system

* define and create the configuration for mapping top level roles to low level roles
* update the Authorise object to check role based on that config where necessary
Add template for editor area

* navigation element on man nav which goes to /editor
* a blueprint for the editor area which currently serves the index page
* a template directory and base/nav templates and the index page
Add the admin area features to manage editor groups

* a search page using facetview to browse/search editor groups
* a web form to create and edit editor groups
* back-end implementation which validates the form and applies role changes to editors/associate editors as needed
Add the first pass at assigning an editor group to a journal.

We still need to apply this to new applications, and we still need to resolve the behaviour of the Editor field
Add Editor Group as a facet in the admin search for journals, and add it as a field in the result set also
Add Group Info and Group Journal page for Editor's Area

* Group Info (default editors area page) presents the user's group memberships
* Two new tabs: Your Group's Journals and Your Group's Applications (only the former currently works)
* Facetview mirroring admin page journal searches on Your Group's Journals
* Back-end changes to filter editor view of journals to only those journals for groups they are in
Create logical separation between the admin area's journal edit link and the actual handling of journal edits

The purpose of this is so that we can then re-purpose journal editing within the editor's area, and maintain separate role-based authorisations on the two routes to the edit form
Initial customisations to allow Editors to access the journal form

* Security framework for editors when accessing journal form
* Ability to route Editors to journal edit handler
Allow Journal edit form to be accessed via the editor area and support the assigment of associate editors to tasks

* Continues the logical separation of journal handling code from web ui routes /editor and /admin
* customised permissions for different access routes
* changes to form template for editor route, to only give editors features they are allowed to hvae
* resolve the slightly fiddly workflow between admin assigning editor groups and editors assiging associates through the same form fields
add Editor facet to journals search in editor area
Add journal list view and edit view for associate editors, plus associated fixes

* add 2 new tabs to editor area: your journals and your suggestions (only the first one works atm)
* add facetview to your suggestions, and back-end filtering to only show those which are assigned to that associate editor
* remove "editorial" section from journal edit page when editing as associate
* prevent editorial being updated at all when editing as associate (i.e. back-end security)
* add "editor" facet to editor's group's journals facetview

This has all be manually tested, but it's challenging to do, so some user testing will be required
add facility to send email to associate editor when a journal is assigned to them
Enable Managing Editor access to Editorial options on Applications

* Added Editor and Editor Group facets to "Applications" section of admin area
* Created logical separation between admin vew on suggestions and the code which handles suggestions/suggestion form (which will allow us to then have other routes into that code from the editor area
* Added "Editorial" section to suggestion form template
* Ported similar functionality for handling editorial details from the journal handler
* normalised the usage of the suggestion form with editorial features with the public-facing Apply form, and fixed a bunch of minor issues in doing that
Activate Editor's "Your Group's Suggestions" page.

* added and customised a facetview for that page
* tested assignment of suggestions to editor groups and confirmed the suggestions appear on this page
Enable Edit Suggestion for Editor (not yet Associate Editor)

* Add implementation for edit suggestion for editor
* add "Editor" field to search results on group's journals/suggestions pages
Add view of "your suggestions" to editor area

* add implementation of your suggesions page with facetview
* testing of transition to editing a suggestion and confirm that suggestion editing works correctly
merge master down to editor
Prevent Editors/Associate editors from accepting applications into the DOAJ

* makes the population of the available statuses dynamic, depending on user role
* adds a new status "ready" which is available to editors
* only makes "accepted" available to managing editors
Large commit which adds edit lock support to journals and suggestions in both admin and editor areas

* provides data model to support edit locking and back-end storage of locks
* interface for adding and removing locks with appropriate authorisation checks
* notification on top right of journal and suggestion pages as to the lock expiry time
* ability to close a page and remove the lock instantaneously
* error page which is displayed to users if they can't get an edit lock on a journal or an application, with information about when they will be able to