Skip to content

Commit 6019629

Browse files
karenmajewiczkarenmajewicz
committed
aardvark page and created more sections
1 parent 65c5ec8 commit 6019629

191 files changed

Lines changed: 40361 additions & 110289 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/about-ogm-aardvark.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -98,6 +98,10 @@ OGM Aardvark gives preference to elements found in established schemas over cust
9898

9999
The original schema features several descriptive metadata fields that only accept one value. The new schema expands many of these to multiple. This changes the URI suffix from `_s` to` _sm`. Although it will not affect the GeoBlacklight functionality, this practice may conflict with indexing, as Solr will treat `dct_publisher_s` as a different field than `dct_publisher_sm`.
100100

101+
#### More intuitive name for unique key
102+
103+
Metadata for GeoBlacklight instances is stored and indexed in Solr, which uses a "Unique Key Field" as the identifier for each document. The OGM Aardvark schema uses the straightforward `id` as the Unique Key Field (in GBL 1.0, this field was called `layer_slug_s`).
104+
101105
### Will Aardvark work with my GeoBlacklight installation?
102106

103107
You will need to upgrade to at least GeoBlacklight version 3.3 to test out Aardvark. All previously hardcoded field names were removed in GeoBlacklight version 3.3 (see [this pull request](https://github.com/geoblacklight/geoblacklight/pull/1020) for more information). This means that field names are defined in the `settings.yml` file and can be configured to use Aardvark. However, only the fields in the crosswalk will have display, facet, or other functionality enabled by default in version 3.3.

docs/configuring-external-links.md renamed to docs/configure-external-links.md

File renamed without changes.

docs/creating-metadata.md renamed to docs/create-metadata.md

File renamed without changes.

‎docs/explanation/index.md‎

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,14 @@
22
icon: octicons/comment-discussion-24
33
---
44

5-
# Explanation
5+
# Explanation
6+
7+
Our explanation guides discuss the background and context for OpenGeoMetadata including:
8+
9+
### [**Repositories:** the purpose and history of OpenGeoMetadata](../about-ogm-repositories)
10+
11+
### [**Metadata:** the development of the Aardvark schema and element categories](../about-ogm-aardvark)
12+
13+
!!! tip
14+
15+
[OpenGeoMetadata Community members have additional resources listed here that may be helpful.](../further-reading)

‎docs/further-reading.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
# Further Reading
22

3-
43
## Community Resources
54

65
* Big Ten Academic Alliance Geospatial Data Project's [Metadata Handbook](https://z.umn.edu/gbl-handbook)

‎docs/gbl-1.0.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ hide:
44

55
!!! warning
66

7-
This is a legacy format. The GeoBlacklight Community recommends using [OGM Aardvark](ogm-aardvark) for GeoBlacklight versions 4.0 and higher.
7+
This is a legacy format. The GeoBlacklight Community recommends using [OGM Aardvark](../ogm-aardvark) for GeoBlacklight versions 4.0 and higher.
88

99
---
1010

‎docs/harvest-ogm.md‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
!!! info
2+
3+
this page is a placeholder for work-in-progress
4+
5+
6+
Metadata in OpenGeoMetadata can be freely harvested and ingested into other discovery applications.
7+
8+
9+
## Suffixes
10+
11+
Altering suffixes can result in metadata schema incompatibilities across institutions. Any deviations in element names causes Solr to treat the elements as separate fields: for example `dct_subject_s` and `dct_subject_sm` would be stored separately. If GeoBlacklight is set up to display a facet for `dct_subject_s`, it will not pick up values stored in `dct_subject_sm` in the filter. Therefore, if you are gathering metadata from other institutions, make sure to inspect their metadata fields to determine if there will be inconsistencies in your Solr index.

‎docs/how-to-guides/index.md‎

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,12 @@
22
icon: octicons/tools-24
33
---
44

5-
# How-to Guides
5+
# How-to
6+
7+
Our How-to guides provide step-by-step workflows for:
8+
9+
### [**Repositories:** How to share your metadata on OpenGeoMetadata](share-metadata)
10+
11+
### [**Metadata:** Creating, transforming, and structuring metadata](create-metadata)
12+
13+
### [**GeoBlacklight:** Ingesting to Solr and viewing metadata in GeoBlacklight](index-to-solr)

docs/publishing-in-solr.md renamed to docs/index-in-solr.md

File renamed without changes.

‎docs/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ OpenGeoMetadata is a discovery metadata schema for geospatial resources and an o
2323
<div class="cell">
2424
<a href = "reference"> <img style="float: left; padding: 1em;" src="images/ogm-logo.png"> </a>
2525
<h2><a href = "reference"> Metadata Schemas</a></h2>
26-
Looking for schema reference and how to upgrade? Visit the <a href = "reference"> schema documentation pages</a> or <a href = "upgrading"> our Upgrade Guide </a>.
26+
Looking for schema reference and how to upgrade? Visit the <a href = "reference"> schema documentation pages</a> or <a href = "upgrade-metadata"> our Upgrade Guide </a>.
2727

2828
</div>
2929

0 commit comments

Comments
 (0)