anchor.diff:  The various objects and their properties are documented in much more detail here:
   https://github.com/commonsmachinery/catalog/blob/master/doc/datamodel/core.md
   
  -## Media [/media/{mediaID}]
  +## Media [/media/{mediaID}{?annotations}]
   A media instance, which is a read-only record of a particular media instance of a Work
   at the time it was recorded in the catalog.
   
   Media instances are intended to be the "raw material" of Works, so access to them
   may be restricted in the catalog to require a reference via a Work (see Work Media below).
  +
  +To make the annotations easier to use in web pages the parameter `annotations` can be set
  +to a list of property names, e.g. `title,locator`.  This will change the response from a plain list to a map, only
  +including the listed properties.  (`all` means that all properties are included in the map.)
  +The keys in this map are the `propertyName`, and the value a list of the Annotations for
  +that property.  This allows easy access like `annotations.title[0].property.value` to show
  +e.g. a title without having to dig through the list.
  +
  ++ Parameters
  +    + annotations (string, optional) ... Select properties to get or update in map.
   
   + Model
       + Headers
  
positive.code: ### Update a Work [PUT]
  The following parameters can be updated, any others are ignored:
  
      - alias
      - description
      - public
      - collaborators
      - annotations (see below)
      - sources (only source_work)
      - media
      
  This really behaves like `PATCH`, so that any omitted parameters are not changed.
  
  
negative.code:     [Media][]
  
  
  ## Media collection [/media{?offset,count,filter,sort,annotations}]
  Given the role of Media as mainly internal raw material means that it often makes more sense to use
  the Work Media collection instead of this one (see below).
  
  