geoblacklight 3.8.0 → 4.0.0.pre.alpha

data/schema/geoblacklight-schema.md

@@ -1,323 +0,0 @@
-## GeoBlacklight 1.0 Metadata Schema
-This is an overview of the GeoBlacklight Metadata Schema, Version 1.0. For more information on applications of these elements, visit the [Schema Commentary document](/schema/schema-commentary.md).
-## Brief
-
-| Label 						| uri| Required?|
-|-------------------						|-----------------------|:----------:|
-| [Identifier](#identifier)					| `dc_identifier_s`| X|
-| [Rights](#rights)							| `dc_rights_s`| X|
-| [Title](#title)							| `dc_title_s`| X|
-| [Provenance](#provenance)					| `dct_provenance_s`| X|
-| [Schema Version](#schema-version)			| `geoblacklight_version`| X|
-| [Slug](#slug)								| `layer_slug_s`| X|
-| [Bounding Box](#bounding-box)				| `solr_geom`| X|
-| [Solr Year](#solr-year)					| `solr_year_i`||
-| [Creator](#creator)						| `dc_creator_sm`||
-| [Description](#description)				| `dc_description_s`||
-| [Format](#format)							| `dc_format_s`||
-| [Language](#language)						| `dc_language_sm`||
-| [Publisher](#publisher)					| `dc_publisher_sm`||
-| [Source](#source)							| `dc_source_sm`||
-| [Subject](#subject)						| `dc_subject_sm`||
-| [Type](#type)								| `dc_type_s`||
-| [Is Part Of](#is-part-of)					| `dct_isPartOf_sm`||
-| [Date Issued](#date-issued)				| `dct_issued_s`||
-| [References](#references)					| `dct_references_s`||
-| [Spatial Coverage](#spatial-coverage)		| `dct_spatial_sm`||
-| [Temporal Coverage](#temporal-coverage)	| `dct_temporal_sm`||
-| [Geometry Type](#geometry-type)			| `layer_geom_type_s`||
-| [Layer ID](#layer-id)						| `layer_id_s`||
-| [Modified Date](#modified-date)			| `layer_modified_dt`|||
-
-
-## Details
-
-### Identifier
-| Label							| Identifier|
-|:------------------------------|:-----------|
-| uri							| `dc_identifier_s`|
-| Required						| yes|
-| Type							| string|
-| Description					| Unique identifier for layer as a URI. It should be globally unique across all institutions, assumed not to be end-user visible|
-| Entry Guidelines				| This is usually in the form of http://institution/id.|
-| Controlled Vocabulary			| no|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "http://purl.stanford.edu/vr593vj7147"|
-
-
-### Rights
-| Label							| Rights|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dc_rights_s`|
-| Required						| yes|
-| Type							| string|
-| Description					| Signals access in the geoportal and is indicated by a padlock icon. Users need to sign in to download restricted items|
-| Entry Guidelines				| Choose either Public or Restricted|
-| Controlled Vocabulary			| "Public" or "Restricted"|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "Public"|
-
-### Title
-| Label							| Title|
-|:------------------------------|:-----------|
-| uri							| `dc_title_s`|
-| Required						| yes|
-| Type							| string|
-| Description					| The name of the resource|
-| Entry Guidelines				| Titles should include place names and dates when available.|
-| Controlled Vocabulary			| no|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "Roads: Minneapolis, Minnesota, 2010"|
-
-### Provenance
-| Label							| Provenance|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dct_provenance_s`|
-| Required						| yes|
-| Type							| string|
-| Description					| The name of the institution that holds the resource or acts as the custodian for the metadata record|
-| Entry Guidelines				| The value for this field should be one of the agreed upon shortened names for each institution. This will embed the correct icon into the search results and item pages.|
-| Controlled Vocabulary			| This repository contains the insitutions that have shared icons: https://github.com/geoblacklight/geoblacklight-icons|
-| Element Set					| DCMI Metadata Terms|
-| Example						| "Stanford"|
-
-### Schema Version
-| Label							| Schema Version|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `geoblacklight_version`	|
-| Required						| yes|
-| Type							| string|
-| Description					| Indicates which version of the GeoBlacklight schema is in use|
-| Entry Guidelines				| Only current value is "1.0"|
-| Controlled Vocabulary			| no|
-| Element Set					| GeoBlacklight|
-| Example						| "1.0"|
-
-### Slug
-| Label							| Slug|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `layer_slug_s`|
-| Required						| yes|
-| Type							| string|
-| Description					| This is a string appended to the base URL of a GeoBlacklight installation to create a unique landing page for each resource. It is visible to the user and serves the purpose of forming a persistent URL for each catalog item.|
-| Entry Guidelines				| This string must be a globally unique value. The value should be alpha-numeric characters separated by dashes.|
-| Controlled Vocabulary			| no|
-| Element Set					| GeoBlacklight|
-| Example						| "stanford-andhra-pradesh-village-boundaries"|
-
-### Bounding Box
-| Label 						| Bounding Box|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `solr_geom`|
-| Required						| yes|
-| Type							| string|
-| Description					| The rectangular extents of the resource. Note that this field is indexed as a Solr spatial (RPT) field|
-| Entry Guidelines				| Bounding box of the layer as a ENVELOPE WKT (from the CQL standard) using coordinates in (West, East, North, South) order. The pattern is: ENVELOPE(.*,.*,.*,.*)|
-| Controlled Vocabulary			| no|
-| Element Set					| GeoBlacklight|
-| Example						| "ENVELOPE(76.76, 84.76, 19.91, 12.62)"|
-
-### Solr Year
-| Label 						| Solr Year|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `solr_year_i`|
-| Required						| no|
-| Type							| integer|
-| Description					| A four digit integer representing a year of temporal coverage or date issued for the resource. This field is used to populate the Year facet and the optional [Blacklight Range Limit gem](https://github.com/projectblacklight/blacklight_range_limit)|
-| Entry Guidelines				| This field must be an integer.|
-| Controlled Vocabulary			| no|
-| Element Set					| GeoBlacklight|
-| Example						| "1982"|
-
-### Creator
-| Label							| Creator|
-|:------------------------------|:---------------------------------------------------------|
-| uri 							| `dc_creator_sm`|
-| Required						| no|
-| Type							| array|
-| Description					| The person(s) or organization that created the resource|
-| Entry Guidelines				| This may be an individual or an organization. If available, it should match with the Library of Congress Name Authority File.|
-| Controlled Vocabulary			| The suggested controlled vocabulary is the [Library of Congress Name Authority File](http://id.loc.gov/authorities/names.html).|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "George Washington", "Thomas Jefferson"|
-
-### Description
-| Label| Description|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dc_description_s`|
-| Required						| no|
-| Type							| string|
-| Description					| At minimum, this is a reiteration of the title in sentence format. Other relevant information, such as data creation methods, data sources, and special licenses, may also be included.|
-| Entry Guidelines				| This is a plain text field.|
-| Controlled Vocabulary			| no|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "This polygon shapefile represents boundaries of election districts in New York City. It was harvested from the NYC Open Data Portal."|
-
-### Format
-| Label							| Format|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dc_format_s`|
-| Required						| no|
-| Type							| string|
-| Description					| This indicates the file format of the data. If a download link is included, this value shows up on the item page display in the download widget|
-| Entry Guidelines				| Choose from set values (see Format list)|
-| Controlled Vocabulary			| [Format Controlled Vocabulary](/schema/format-values.md)|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "Shapefile"|
-
-### Language
-| Label							| Language|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dc_language_sm`|
-| Required						| no|
-| Type							| array|
-| Description					| Indicates the language of the data or map|
-| Entry Guidelines				| Spell out language (in English) instead of using the ISO 639-1 code (e.g.,“French” instead of “fra”).|
-| Controlled Vocabulary			| no|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "English"|
-
-### Publisher
-| Label							| Publisher|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dc_publisher_s`|
-| Required						| no|
-| Type							| array|
-| Description					| The organization that made the original resource available|
-| Entry Guidelines				| This should always be an organization.|
-| Controlled Vocabulary			| The suggested controlled vocabulary is the [Library of Congress Name Authority File](http://id.loc.gov/authorities/names.html).|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "ML InfoMap (Firm)"|
-
-### Source
-| Label							| Source|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dc_source_sm`|
-| Required						| no|
-| Type							| array|
-| Description					| This is used to indicate parent/child relationships between data layers and activates the Data Relations widget in GeoBlacklight|
-| Entry Guidelines				| This is only added to the child records. Enter the layer_slug_s of the parent record(s) into this field.|
-| Controlled Vocabulary			| no|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "stanford-vr593vj7147"|
-
-### Subject
-| Label							| Subject|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dc_subject_sm`|
-| Required						| no|
-| Type							| array|
-| Description					| These are theme or topic keywords|
-| Entry Guidelines				| These should be consistent and chosen from a controlled vocabulary. Use sentence style capitalization, where only the first word of a phrase is capitalized.|
-| Controlled Vocabulary			| Recommended thesauri are [ISO Topic Categories](https://www2.usgs.gov/science/about/thesaurus-full.php?thcode=15) and Library of Congress Subject Headings.|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "Census", "Human settlements"|
-
-
-### Type
-| Label							| Type|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dc_type_s`|
-| Required						| no|
-| Type							| string|
-| Description					| This is a general element to indicate the larger genre of the resource|
-| Entry Guidelines				| Choose from Dublin Core Type values|
-| Controlled Vocabulary			| [Type Controlled Vocabulary](/schema/type-values.md)|
-| Element Set					| Dublin Core Metadata Element Set|
-| Example						| "Dataset"|
-
-### Is Part Of
-| Label							| Is Part Of|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dct_isPartOf_sm`|
-| Required						| no|
-| Type							| array|
-| Description					| Holding entity for the layer, such as the title of a collection|
-| Entry Guidelines				| Plain text that is indexed in the Collections facet|
-| Controlled Vocabulary			| no|
-| Element Set					| [DCMI Metadata Terms](http://dublincore.org/documents/dcmi-terms/)|
-| Example						| "Village Maps of India"|
-
-### Date Issued
-| Label							| Date Issued|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dct_issued_s`|
-| Required						| no|
-| Type							| string|
-| Description					| This is the publication date for the resource|
-| Entry Guidelines				| Use any date format, such as the XML Schema dateTime format (YYYY-MM-DDThh:mm:ssZ)|
-| Controlled Vocabulary			| no|
-| Element Set					| [DCMI Metadata Terms](http://dublincore.org/documents/dcmi-terms/)|
-| Example						| "2015-01-01"|
-
-### References
-| Label							| References|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dct_references_s`|
-| Required						| no|
-| Type							| string|
-| Description					| This element is a hash of key/value pairs for different types of external links. It integrates external services and references using the CatInterOp approach|
-| Entry Guidelines				| See [External Services](https://github.com/geoblacklight/geoblacklight/wiki/Schema#external-services)|
-| Controlled Vocabulary			| [References URIs](/schema/references.md)|
-| Element Set					| DCMI Metadata Terms|
-| Example						| "dct_references_s": "{\"http://schema.org/url\":\"http://purl.stanford.edu/bm662dm5913\",\"http://schema.org/downloadUrl\":\"http://stacks.stanford.edu/file/druid:bm662dm5913/data.zip\"}"|
-
-### Spatial Coverage
-| Label							| Spatial Coverage|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dct_spatial_sm`|
-| Required						| no|
-| Type							| array|
-| Description					| This field is for place name keywords|
-| Entry Guidelines				| Place name text strings should be specified out to the nation level. It is typical for the place name to represent the largest extent the data layer represents.|
-| Controlled Vocabulary			| Recommended thesaurus is [GeoNames](https://www.geonames.org/)|
-| Element Set					| DCMI Metadata Terms|
-| Example						| "Philadelphia, Pennsylvania, United States"|
-
-### Temporal Coverage
-| Label							| Temporal Coverage|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `dct_temporal_sm`|
-| Required						| no|
-| Type							| array|
-| Description					| This represents the "Ground Condition" of the resource, meaning the time period data was collected or is intended to represent. Displays on the item page in the Year value|
-| Entry Guidelines				| This is a text string and can indicate uncertainty|
-| Controlled Vocabulary			| no|
-| Element Set					| DCMI Metadata Terms|
-| Example						| "2007-2009"|
-
-### Geometry Type
-| Label							| Geometry Type|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `layer_geom_type_s`|
-| Required						| no|
-| Type							| string|
-| Description					| This element shows up as Data type in GeoBlacklight, and each value has an associated icon|
-| Entry Guidelines				| Choose from set values (see Controlled Vocabulary Lists)|
-| Controlled Vocabulary			| [Geometry Type Controlled Vocabulary](/schema/geometry-type-values.md)|
-| Element Set					| GeoBlacklight|
-| Example						| "Polygon"|
-
-### Layer ID
-| Label							| Layer ID|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `layer_id_s`|
-| Required						| no|
-| Type							| string|
-| Description					| Indicates the layer id for any WMS or WFS web services listed in the dct_references_s field|
-| Entry Guidelines				| Only the layer name is added here. The base service endpoint URLs (e.g. "https://maps-public.geo.nyu.edu/geoserver/sdr/wms") are added to the `dct_references_s` field.|
-| Controlled Vocabulary			| no|
-| Element Set					| GeoBlacklight|
-| Example						| "druid:vr593vj7147"|
-
-### Modified Date
-| Label							| Modified Date|
-|:------------------------------|:---------------------------------------------------------|
-| uri							| `layer_modified_dt`|
-| Required						| no|
-| Type							| date-time|
-| Description					| Last modification date for the metadata record|
-| Entry Guidelines				| Use the XML Schema dateTime format (YYYY-MM-DDThh:mm:ssZ)|
-| Controlled Vocabulary			| no|
-| Element Set					| GeoBlacklight|
-| Example						| "2015-01-01T12:00:00Z"|

data/schema/geometry-type-values.md

@@ -1,11 +0,0 @@
-## Geometry Type Vocabulary
-
-| Label | Icon Link | Definition|
-|:----------------------------|:-------------|:---------------------------------------------------------|
-|Point|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/point.svg)|Geospatial dataset made up of pairs of x,y coordinates|
-|Line|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/line.svg)|Geospatial dataset made up of straight or curved connected x,y coordinates|
-|Polygon|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/polygon.svg)|Geospatial dataset made up of closed connections of x,y coordinates|
-|Image|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/image.svg)|Static born-digital maps and scanned map images|
-|Raster|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/raster.svg)|Geospatial dataset that is presented as an array of cells comprised of single or multiple bands|
-|Mixed|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/mixed.svg)|Geospatial dataset with multiple geometry types|
-|Table|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/table.svg)|Nonspatial dataset as a text file with delimiter separated values|

data/schema/references.md

@@ -1,23 +0,0 @@
-# External References
-
-The field `dct_references_s` defines external services and references using the [CatInterOp](https://github.com/OSGeo/Cat-Interop) approach. The field value is a serialized JSON array of key/value pairs, with keys representing XML namespace URI's and values the URL.
-
-Type | Reference URI | Enables in GeoBlacklight
-|:---- |:------------- |:------------------------|
-Web Mapping Service (WMS) | `http://www.opengis.net/def/serviceType/ogc/wms` | Layer preview, layer preview feature inspection, downloads (vector: KMZ, raster: GeoTIFF)|
-Web Feature Service (WFS) | `http://www.opengis.net/def/serviceType/ogc/wfs` | Vector downloads in GeoJSON and Shapefile|
-International Image Interoperability Framework (IIIF) Image API | `http://iiif.io/api/image` | Image viewer using [Leaflet-IIIF](https://github.com/mejackreed/Leaflet-IIIF)|
-Direct download file | `http://schema.org/downloadUrl` | Direct file download feature|
-Data dictionary / documentation download | `http://lccn.loc.gov/sh85035852` | Direct documentation download link|
-Full layer description | `http://schema.org/url` | Further descriptive information about layer|
-Metadata in ISO 19139 | `http://www.isotc211.org/schemas/2005/gmd/` | Structured metadata in ISO standard expressed as XML|
-Metadata in FGDC | `http://www.opengis.net/cat/csw/csdgm` | Structured metadata in FGDC standard expressed as XML|
-Metadata in MODS | `http://www.loc.gov/mods/v3` | Structured metadata in MODS format|
-Metadata in HTML | `http://www.w3.org/1999/xhtml` | Structured metadata in any standard expressed as HTML|
-ArcGIS FeatureLayer | `urn:x-esri:serviceType:ArcGIS#FeatureLayer` | Previewing of ArcGIS FeatureLayer Service|
-ArcGIS TiledMapLayer | `urn:x-esri:serviceType:ArcGIS#TiledMapLayer` | Previewing of ArcGIS TiledMapLayer Service|
-ArcGIS DynamicMapLayer | `urn:x-esri:serviceType:ArcGIS#DynamicMapLayer` | Previewing of ArcGIS DynamicMapLayer Service|
-ArcGIS ImageMapLayer | `urn:x-esri:serviceType:ArcGIS#ImageMapLayer` | Previewing of ArcGIS ImageMapLayer Service|
-Harvard Geospatial Library Email Download | `http://schema.org/DownloadAction` | Retrieve a file via email from the Harvard Geospatial Library|
-OpenIndexMap | `https://openindexmaps.org` | Provide an index map preview|
-oEmbed | `https://oembed.com` | Provide an object that is embeddable through an oEmbed service

data/schema/schema-commentary.md

@@ -1,198 +0,0 @@
-## Commentary and Suggestions for the GeoBlacklight 1.0 Metadata Schema
-
-This document elaborates on the application of fields in the
-GeoBlacklight 1.0 Metadata Schema with recommendations from the
-GeoBlacklight community of practice.
-
-For a profile of the schema, visit
-[here](/schema/geoblacklight-schema.md).
-
-### Identifier
-
-This field is required, but it is not displayed in the interface. It may
-be identical to the `layer_slug_s` field, or it may be related to or derived from the `layer_id_s`. This value is
-ideally a persistent identifier or permalink (such as a [PURL](https://en.wikipedia.org/wiki/Persistent_uniform_resource_locator) or [Handle](https://en.wikipedia.org/wiki/Handle_System).
-
-### Rights
-
-This field can be set to "Public", which allows users to view and
-download an item, or "Restricted", which requires a user to log in to an
-authentication service. If there are additional licenses or rights
-associated with a resource, administrators will have to create a custom field in the local Solr schema.
-
-### Title
-
-The title is the most prominent metadata field that users see when
-browsing or scanning search results. Since many datasets are created
-with ambiguous or non-unique titles, it may be worth the effort to
-improve or enhance them. The ideal sequence of a title is something akin
-to Topic of Layer: Place, Year. Putting the year at the end of a title
-produces better search results, since titles are left-anchored.
-
-### Provenance
-
-This field indicates the institution that contributed the resource. The
-current community of practice is for this field to hold the name of the
-university or institution that has created the GeoBlacklight metadata
-record and/or hosts the dataset. Projects are encouraged to submit their
-institutional icon to the GeoBlacklight Icons repository to display with the resource.
-
-### Schema Version
-
-"1.0" is the current version of the GeoBlacklight schema.
-
-### Slug
-
-The slug makes up the URL for the resource in GeoBlacklight. If having a
-readable slug is desired, it is common to use the form,
-institution-keyword1-keyword2 (words or characters are separated by hyphens).
-
-### Bounding Box
-
-The rectangular bounding box is to aid searching with the map interface.
-Although accuracy is encouraged, it may not always be necessary to to
-have precise bounding coordinates. The field functions to facilitate discovery more than to indicate exact extents.
-
-### Solr Year
-
-This field is a four digit integer that must be inferred by the temporal
-coverage or date issued of the resource. If a single record spans multiple years, choose the earliest year for the `solr_year_i` field.
-
-### Creator
-
-The `dc_creator_sm` field is best reserved for instances in which an
-individual person has collected, produced, or generated analyses of
-data (as opposed to an agency releasing a data product or resource). See also the comments on `dc_publisher_sm`.
-
-### Description
-
-The `dc_description_s` field is the second most prominent value that users see
-when search or browsing for items. Although not required, it is strongly
-recommended. If the description is minimal or lacking, it can be
-improved by concatenating available metadata fields, such as title,
-date, format, and place. This is a plain text field, so html code is not
-supported here unless the application is customized. It is recommended to assume that discovery happens in multiple contexts (i.e., GeoBlacklight metadata may be integrated into other discovery environments), so descriptions should use complete sentences that signpost what the data object is, even though that is evident within GeoBlacklight itself.
-
-### Format
-
-A long list of formats is available [here.](/schema/format-values.md)
-The most important thing to remember about the `dc_format_s` field is that it is
-required for Download functionality. Whatever value is in the `dc_format_s`
-field will show up as text in the Download widget, unless the application has local customizations.
-
-### Language
-
-This field is intended to indicate the language of the dataset, map,
-and/or supporting documentation. The most common practice in this community
-is to spell the name language out in English (e.g., "French").
-
-### Publisher
-
-The distinction between `dc_publisher_sm` and `dc_creator_sm` for data
-is often vague. Publishers should be the administrative body or
-organization that made the original resource available, regardless of
-who compiled or produced the data.
-
-### Source
-
-The `dc_source_sm` field exists to indicate parent-child relationships between
-records. Common uses include: individual sheets within a map series that
-can point to a Shapefile that serves as an index map, individual
-Shapefile layers that have been derived from a Geodatabase that can
-point to the record for the GeoDatabase, or collection-level and related
-individual layer records. See
-https://github.com/geoblacklight/geoblacklight/wiki/Using-data-relations-widget for more information.
-
-### Subject
-
-This field is indexed as a facet by default for GeoBlacklight
-applications, and it can become unwieldy when aggregating metadata
-records from multiple sources. Controlled vocabularies for GIS data have
-typically been expressed as ISO Topic Categories and localized thesauri,
-while scanned maps are typically described with Library of Congress
-Subject Headings. Even within these vocabularies, localized spellings
-and abbreviations will result in considerable variations between
-institutions. Institutions are encouraged to observe what terms are
-commonly in use and, at the very least, strive for internal consistency
-with controlled vocabularies and spellings. This facilitates easier
-metadata sharing across projects, such as the repositories in
-[OpenGeoMetadata](https://github.com/OpenGeoMetadata). Some institutions
-choose to create custom keyword fields to hold local, unnormalized
-values. It is recommended not to use Library of Congress Subject Headings to indicate the geography or spatial coverage of a dataset; instead, use the `dct_spatial_sm` field for this.
-
-### Type
-
-The `dc_type_s` field is optional, but it can be useful for categorizing
-between datasets, scanned maps, and collections. The GeoBlacklight schema
-observes the Dublin Core controlled vocabulary for [Type](/schema/type-values.md).
-
-### Is Part Of
-
-The `dct_isPartOf_sm` field is most often used as a way to group
-collections arbitrarily. Such groupings often have meaning within local
-institutions and can be shorthand for keeping like items
-together. For example, the value could mark all of the items in a single
-data submission, all of the items that pertain to a class that is
-working with GIS data, or all of the items harvested from a specific
-Open Data portal.
-
-### Date Issued
-
-Although the `dct_issued_s` field is optional, it is often useful when
-a clear Temporal Coverage value is not present. For example, one may
-want to preserve a dataset with an uncertain lineage, but there is an
-indicator on a data portal on the date of last update.
-
-### References
-
-All of the external links for the resource are added to the `dct_references_s`
-field as a serialized JSON array of key/value pairs. For example:
-
-```
-<field name="dct_references_s">
-  {
-    "http://schema.org/url":"http://purl.stanford.edu/bb509gh7292",
-    "http://schema.org/downloadUrl":"http://stacks.stanford.edu/file/druid:bb509gh7292/data.zip",
-    "http://www.loc.gov/mods/v3":"http://purl.stanford.edu/bb509gh7292.mods",
-    "http://www.isotc211.org/schemas/2005/gmd/":"http://opengeometadata.stanford.edu/metadata/edu.stanford.purl/druid:bb509gh7292/iso19139.xml",
-    "http://www.w3.org/1999/xhtml":"http://opengeometadata.stanford.edu/metadata/edu.stanford.purl/druid:bb509gh7292/default.html",
-    "http://www.opengis.net/def/serviceType/ogc/wfs":"https://geowebservices-restricted.stanford.edu/geoserver/wfs",
-    "http://www.opengis.net/def/serviceType/ogc/wms":"https://geowebservices-restricted.stanford.edu/geoserver/wms"
-  }
-</field>
-```
-See the [References controlled vocabulary](/schema/references.md) for the URIs of the keys and their recommended uses.
-
-### Spatial Coverage
-
-It is recommended to have at least one place name for each layer that
-corresponds to the logical extent of the area of that layer. Adding
-additional place names that fall within the layer should be done only if
-they are topically relevant to the content of the data. If a long list of
-place names is desired in the metadata for search purposes, a customized
-hidden field is recommended.
-
-### Temporal Coverage
-
-The `dct_temporal_sm` field is multi-valued, so multiple strings can be used to indicate the time period the resource depicts, when the
-data was collected, and/or when the resources was created. Examples include: “1910?”, “1800-1805”, “before 2000”. If a single dataset spans multiple years, one can add each intervening year as a discrete value (e.g., 2007,2008,2009,2010). However, a common convention is to include only the first and last year (e.g., 2007,2010 for a dataset encompassing the span of time between 2007 and 2010).
-
-###  Geometry Type
-
-This field helps to differentiate between vector (Point, Line, Polygon),
-raster (Raster, Image), nonspatial formats (table), or a combination
-(Mixed). If processing metadata from a geospatial web server, this value
-may be programmatically determined. However, in many cases, it must be manually
-determined. The field is tied to icons for the resource, and provides
-the user with visual clues to the item. However, if the element is
-troublesome or unnecessary for a particular institution, it can be
-omitted. [See the controlled vocabulary.](/schema/geometry-type-values.md)
-
-### Layer ID
-
-The Layer ID is used to point to specific layers within a geospatial web
-service. This field is not used for ArcGIS Rest Services.
-
-### Modified Date
-
-This value should indicate when the metadata (not the resource itself) was last modified.

data/schema/subjects.md

@@ -1,41 +0,0 @@
-These charts lists the most common terms and spellings for Subjects
-in the GeoBlacklight community.
-
-## Geospatial Data
-
-Common spelling | Related terms
-|----|-------------
-Farming | Agriculture
-Biota | Biology |ISO Topic Category
-Boundaries | Administrative and political boundaries; Cities and towns
-Climatology, Meteorology, and Atmosphere | Climate
-Economy
-Elevation
-Environment |
-Geoscientific Information | Geology
-Health ||
-Imagery and Base Maps | Imagery; Basemaps; Landcover
-Intelligence and Military |
-Inland Waters |
-Location |
-Oceans |
-Planning and Cadastral | Property
-Society |
-Structure | Facilities and Structures
-Transportation |
-Utilities and Communications | Utilities
-
-## Maps
-
-Common spelling | Related terms
-|:---- |:------------- |
-Aeronautical charts
-Atlases
-Bathymetric maps
-Cadastral maps
-Fire insurance maps
-Geological maps
-Road maps
-Thematic maps
-Topographic maps
-Tourist maps

data/schema/type-values.md

@@ -1,10 +0,0 @@
-## GeoBlacklight Type Values
-
-| Label | Dublin Core Link | Definition|
-|:----------------------------|:-------------|:---------------------------------------------------------|
-|Dataset|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-Dataset)|Data encoded in a defined structure. Includes geospatial formats as vector, raster, and tabular data.|
-|Image|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-Image)|A visual representation other than text. Includes static born-digital maps, scanned map images, and aerial photography.|
-|Collection|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-Collection)|An aggregation of resources. Describes a group of resources that may or may not be separately described.|
-|Interactive Resource|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-InteractiveResource)|External web applications that require the user to input information to generate a filtered dataset|
-|Collection|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-Collection)|An aggregation of resources. Describes a group of resources that may or may not be separately described.|
-|Physical Object|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-PhysicalObject)|Non-digital resource, such as a paper map or a globe|

data/spec/features/tilejson_spec.rb

@@ -1,22 +0,0 @@
-# frozen_string_literal: true
-require 'spec_helper'
-
-feature 'tilejson layer' do
-  before do
-    WebMock.disable_net_connect!(allow_localhost: true, allow: 'chromedriver.storage.googleapis.com')
-  end
-
-  after do
-    WebMock.allow_net_connect!
-  end
-
-  scenario 'displays tilejson layer', js: true do
-    # Mock tilejson manifest url
-    stub_request(:get, 'https://map-tiles-staging.princeton.edu/mosaicjson/tilejson.json?id=2a91d82c541c426cb787cc62afe8f248')
-      .to_return(status: 200, body: read_fixture('manifests/tilejson.json'))
-
-    visit solr_document_path('princeton-fk4544658v-tilejson')
-    expect(page).to have_css '.leaflet-control-zoom', visible: :visible
-    expect(page).to have_css "img[src*='https://map-tiles-staging.princeton.edu/mosaicjson/tiles/WebMercatorQuad']"
-  end
-end