anchor.diff:  
   === Create a data record
   
  -Click the *New* button at the foot of any record list page.  A new form, is displayed for entering details of some new entity.  The initial type of new entity, and the data entry form displayed, are determined based on the list view used, but these can be overridden using thew `Type` and `Choose view` dropdowns.
  +Click the *New* button at the foot of any record list page.  A new form, is displayed for entering details of some new entity.  The initial type of new entity, and the data entry form displayed, are determined based on the list view used, but these can be overridden using thew *Type* and *Choose view* dropdowns.
   
   Example list display:
   
   image::screenshots/List-musical-instruments.png[alt="List of musical instruments"]
   
  -Based on the definition of this list, clicking on `New` briungs up a new form for entering details of a new instrument:
  +Based on the definition of this list, clicking on *New* briungs up a new form for entering details of a new instrument:
   
   image::screenshots/Edit-musical-instrument.png[alt="Edit musical instrument details"]
   
  -Enter details into the presented form, and click `Save` to create a new record with the details entered:
  +Enter details into the presented form, and click *Save* to create a new record with the details entered:
   
   image::screenshots/List-musical-instruments-2.png[alt="Updated list of musical instruments"]
   
  
positive.code: 
  === Access control and user permissions
  
  Being logged in to Annalist does not, of itself, grant permission to access or modify any Annalist data - except in a very broad sense covered by `\_default_user_perms` (see below).  That is controlled separately by _user permission_ records, which may be created for any collection ovcerv which the user is granted access permissions.
  
  When a user is logged in to Annalist (using OpenID or local credentials), their session is associated with a user identifier (user_id) and an email address, as well as some descriptive information.  The user_id alone is not a secure basis for access control, as Annalist allows anyone to create a new user_id through the OpenID based login process.  Rather, it is assumed that the associated email address has been properly checked as associated with the logged-in user:  this verification is something that should be handled by any OpenID identity provider (such as Google) worthy of being used as such.  Annalist uses the combination of user_id and email address as a reliable authenticated identifier, with which access permissions are associated.  Different user_ids may bve associated with the same email address, possibly corresponding to different roles of the authenticated user;  each such combination is associated with its own set of permissions. (Technically, Annalist internally uses a mailto: URI as an authenticated user identifier, and uses different forms of URI for some special cases.)
  
  Permissions granted to a user consist of a list of tokens denoting different access rights; e.g. VIEW, CREATE, UPDATE, DELETE, etc.  Permissions are applied at the level of a collection;  a user may have different permissions in different collections.  The permisisons granted form part of the collection metadata, and as such are replicated if an entire collection is copied or moved to a different service.  It is also possible to associate permissions with an entire Annalist site, which means they are applied in any collection for which more specific permissions are not granted;  the user interface for creating site-wide permissions currently takes the form of a limited set of `annalist_manager` commands, and is intended to be used for setting up site-wide defaults and administrative access.
  
  
negative.code: 
  === Customize collection page
  
  The default display for a collection, and all the other list views, include a *Customize* button that provides access to a "Customize collection" page, which summarizes the record types, list views and record views defined for a collection, and provides affordances to create, edit or delete them:
  
  image::screenshots/Customize-collection.png[alt="Customize collection view"]
  
  