Add temp files '*~' to .gitignore
Merge pull request #1 from CDLUC3/master

Weekly Fork Update CDL-2-UCI
Merge remote-tracking branch 'upstream/master'
Add geoLocation, geoLocationPoint, and geoLocationBox models and MySQL tables

GeoLocation has a polymorphic association with geoLocationPoint and
geoLocationBox. A geoLocationBox or geoLocationPoint can have many
geoLocations, and a record can have one geoLocation. The MySQL tables
for Points and Boxes make use of the rgeo, rgeo-activerecord, and
activerecord-mysql2spatial-adapter gems. This allows the table to
store coordinates as the spatial data types 'point' and 'polygon'.
Rgeo may require the use of the GEOS library
(http://trac.osgeo.org/geos).
Add geoLocation and geoLocationPlace to the new record form

This includes properly associating GeoLocation with Record. Also,
a javascript asset was added in preparation for map display.
Add Leaflet map to Record form

Leaflet code from vendor added, as well as CSS for the map. When
the user selects the geoLocationPoint button, the map appears.
Merge pull request #2 from CDLUC3/master

Weekly Fork Update CDL-2-UCI
merge with stage
merge with stage
merge with stage
removing this since there's an MIT license.txt file that's more recent
Associate geoLocation fields directly with Record

The geoLocation table has been removed in favor of direct associations
between Record and GeoLocationPoint/GeoLocationBox. GeoLocationPlace
is now a checkbox which, if the submitter opts in, will assign
GeoLocationPlace to be "Orange County (Calif.)" and will reveal the
other geoLocation fields.
Destroy geoLocationPoints if superseded by other geospatialType

Before Record and its children are validated, geoLocationPoints are
checked against the selected geospatialType (points/box/none), and for
blank fields. Unused or superseded Points are marked for destruction.

Client-side, Point latitudes and longitudes must be within the range of
valid coordinates. These fields are also checked during db validation.
Set geographic fields' visibility for Record edits

When editing a Record, the geographic fields are automatically
expanded if the Record previously included geographic information.
Similarly, the fields belonging to the correct geospatialType
(Point/Box) are automatically visible.

Code was added to the Record model to generate Datacite's
geoLocations in XML.
Add revised schema file to changes
Merge pull request #3 from CDLUC3/master

Weekly Fork Update CDL-2-UCI
Install Leaflet.draw toolbars and drawing functions

When the user elects to provide geoLocationPoints or a geoLocationBox,
the correct Leaflet.draw tool will allow them to draw markers or
rectangles on the map. When drawing a rectangle, the coordinates of
the SW and NE corners will be automatically added to the Box form
fields.
Differentiate between Leaflet featureLayers

Leaflet now switches between editing a layer of <= 25 markers and
a layer of 0-1 rectangle. The visibility of these layers toggles
when geoLocation type is chosen.

Also, Leaflet default images have been added to the vendor assets.
Fix enforcement of map drawing limitations

The previous system of "grey-ing out" the drawing tool was buggy.
Instead, JQuery toggles the visibility of the Draw toolbar itself
when the limit of geospatial objects on the map has been reached.

Also, the geoLocationBox form fields are now updated when the
drawn rectangle is edited. Entering coordinates into the form
will trigger the creation of a new rectangle if one did not
previously exist.
Merge remote-tracking branch 'upstream/master'