Darren Hardy

see https://github.com/sul-dlss/gis-robot-suite/pull/74

That field uses a `tint` (`solr.TrieIntField`) like so: ``` ``` we'd need to add that to our `schema.xml` for an `_im`(?) suffix. We're already using a `solr.TrieIntField` field for our...

Another data point here... When you're faceted on Level, for example, the suggestion is not context-sensitive, so when you select a suggestion that's from a component: ![screen shot 2017-05-17 at...

see https://jirasul.stanford.edu/jira/browse/SAR-2636

yes, i think so. it would go into both geoblacklight and geoblacklight-schema

we have Purdue in the provenance -- perhaps we need a generic warning message? ``` "layer_slug_s": "1d8b2277-f32e-491b-9ccd-93aa247a3336", "dct_provenance_s": "Purdue", ```

related to https://github.com/sul-dlss/earthworks/issues/403

We're not using iso2geoBL.xsl in our production environment (we go from ISO to MODS to GeoBlacklight) so our instance uses `dc_publisher_s`. I don't see a reason, however, that you couldn't...

@jvine do we have a list of relator terms that we can strip out programatically? We're not getting structured data for those authors ``` AUTHORS: ["Sovacool, Benjamin K., Author", "Linnér,...

See https://github.com/ebsco/edsapi-ruby/issues/51 for the question of how to identify the relator terms