Merge pull request #106 from kgjenkins/main

fix links

Author: karenmajewicz

docs/gbl-0.5.md

@@ -5,13 +5,13 @@ hide:
 
 !!! warning
 
-	This is a legacy format. The GeoBlacklight Community recommends using [OGM Aardvark](ogm-aardvark) for GeoBlacklight versions 4.0 and higher.
+	This is a legacy format. The GeoBlacklight Community recommends using [OGM Aardvark](../ogm-aardvark) for GeoBlacklight versions 4.0 and higher.
 
 ---
 
 ## Deprecated fields
 
-The earliest metadata schema for GeoBlacklight is the same as [GBL 1.0](gbl-1.0.md), except that it also included these now-deprecated fields:
+The earliest metadata schema for GeoBlacklight is the same as [GBL 1.0](../gbl-1.0), except that it also included these now-deprecated fields:
 
 * `uuid`
 * `dc_relation_sm`

docs/gbl-1.0.md

@@ -234,7 +234,7 @@ hide:
 | Controlled Vocabulary			| no|
 | Element Set					| Dublin Core Metadata Element Set|
 | Example						| "stanford-vr593vj7147"|
-| Commentary |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 Using the Data Relations Widget](https://geoblacklight.org/guides.html#using-the-data-relations-widget) for more information.|
+| Commentary |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 the GeoBlacklight [data relations widget](https://geoblacklight.org/docs/data_relations_widget/) for more information.|
 
 ## Subject
 

docs/ogm-aardvark/provider.csv

@@ -5,7 +5,7 @@ Field Type,String
 Obligation,Suggested
 Multivalued,False
 Purpose,To clarify which organization holds the resource or acts as the custodian for the metadata record and to help users understand which resources they can access.
-Entry Guidelines,"This field can be any string value. However, if the value corresponds to the name of an SVG icon in GeoBlacklight, the icon will display next to the title. See the [GeoBlacklight documentation](https://geoblacklight.org/docs/customization/adding_svg_icons/) on adding SVG icons for more details."
+Entry Guidelines,"This field can be any string value. However, if the value corresponds to the name of an SVG icon in GeoBlacklight, the icon will display next to the title. See the GeoBlacklight documentation on [adding SVG Icons](https://geoblacklight.org/docs/adding_svg_icons/) for more details."
 Commentary,This field was named **Provenance** in the GBL 1.0 metadata schema.
 Controlled Vocabulary,Yes - not strict
 Example Value,"""University of Minnesota"""

docs/ogm-aardvark/rights.csv

@@ -6,7 +6,7 @@ Obligation,Suggested
 Multivalued,True
 Purpose,"To provide a free text field for rights information, such as usage, access, or copyright."
 Entry Guidelines,"Enter free text of generic, catch-all access and usage rights."
-Commentary,"This field is intended to be flexible to accommodate different types of rights and disclaimers. Users are encouraged to adopt one of the rightsstatements.org statements. This is a plain text field by default, but it can include clickable links if the GeoBlacklight software is customized; see the [GeoBlacklight documentation](https://geoblacklight.org/docs/customization/rendering_html_from_description/) on how to render HTML from a text field."
+Commentary,"This field is intended to be flexible to accommodate different types of rights and disclaimers. Users are encouraged to adopt one of the rightsstatements.org statements. This is a plain text field by default, but it can include clickable links if the GeoBlacklight software is customized; see the GeoBlacklight documentation on [rendering HTML in metadata fields](https://geoblacklight.org/docs/rendering_html_from_description/)."
 Controlled Vocabulary,No
 Example Value,"""All data is copyrighted by China Data Center and/or its suppliers. Derived works that include the source data must be merged with other value-added data in such a way that the derived work cannot be converted back to the original source data format. This data is licensed by UC Berkeley for research, educational, and other non-commercial use by authorized users, which include persons affiliated with UC Berkeley and walk-in users who must access the data in person at the library. [https://rightsstatements.org/page/InC/1.0/?language=en](https://rightsstatements.org/page/InC/1.0/?language=en)."""
 Element Set,DCMI

docs/upgrade-metadata.md

@@ -38,7 +38,7 @@ This option involves updating your local transformation workflow that extracts v
 Programmatically convert the JSON files
 
 ![convert-jsons](images/transform-option2.png)
-Fig.2 - Programmatic transformation process using Geoblacklight 1.0 Metadata JSONs
+Fig.2 - Programmatic transformation process using GeoBlacklight 1.0 Metadata JSONs
 
 
 ### Scenarios

docs/validate-metadata.md

@@ -4,4 +4,4 @@
 Once the metadata records are in the OpenGeoMetadata format, they should be validated to make sure the fields are correctly formatted. The current version of the schema is available as a [JSON-Schema file](https://github.com/geoblacklight/geoblacklight/blob/master/schema/geoblacklight-schema.json). This file format provides support for data validation with the [JSON Schema Vocabulary](http://json-schema.org).
 
 
-Use [GeoCombine](https://github.com/OpenGeoMetadata/GeoCombine), which has a [.valid? method](http://www.rubydoc.info/gems/geo_combine/0.1.0/GeoCombine/Geoblacklight#valid%3F-instance_method) that makes using these tools simple.
+Use [GeoCombine](https://github.com/OpenGeoMetadata/GeoCombine), which has a [.valid? method](http://www.rubydoc.info/gems/geo_combine/0.1.0/GeoCombine/GeoBlacklight#valid%3F-instance_method) that makes using these tools simple.