It looks like the datamodel allows multiple locations per item, but the user interface does not. With exposure of the API, a client could post new locations in a way that the current admin UI doesn't allow.
Maybe the Omeka 2.1-compatible plugin changes UI to allow multiple locations, and maybe even eats its own dogfood?
Playing with this on branch multiple_locations
It looks like the datamodel allows multiple locations per item, but the user interface does not. With exposure of the API, a client could post new locations in a way that the current admin UI doesn't allow.
Maybe the Omeka 2.1-compatible plugin changes UI to allow multiple locations, and maybe even eats its own dogfood?
Playing with this on branch
multiple_locations