You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/aardvark-gbl-1-crosswalk.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ The following chart shows the full Aardvark schema and which GBL 1.0 fields can
7
7
8
8
## Elements without a crosswalk
9
9
10
-
Most of the elements from GBL 1.0 can be crosswalked directly into OGM Aardvark. The values for these elements are the same - only the URI name has changed or the field has been converted to an array.
10
+
Most of the elements from GBL 1.0 can be crosswalked directly into OGM Aardvark. The values for these elements are the same - only the field name has changed or the field has been converted to an array.
11
11
12
12
However, there are three elements in GBL 1.0 that do not directly translate into OGM Aardvark. While they have been replaced with similar fields in OGM Aardvark, the **values themselves** would need to be altered during crosswalking.
13
13
@@ -24,4 +24,4 @@ However, there are three elements in GBL 1.0 that do not directly translate into
24
24
**Is Part Of (`dct_isPartOf_sm`)**
25
25
26
26
* GBL 1.0 Description: This multi-valued GBL 1.0 plain text field is for writing out the name of a collection. Example: `dct_isPartOf_sm:"Village Maps of India"`
27
-
* Similar Aardvark element: The URI is the same in Aardvark, but it is now a non-literal field. The value must be one or more IDs that reference another record within the system. Example: `dct_isPartOf_sm:"princeton-z603r079s"`
27
+
* Similar Aardvark element: The field name is the same in Aardvark, but it is now a non-literal field. The value must be one or more IDs that reference another record within the system. Example: `dct_isPartOf_sm:"princeton-z603r079s"`
Copy file name to clipboardExpand all lines: docs/about-ogm-aardvark.md
+7-10Lines changed: 7 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,9 @@ Details about the OpenGeoMetadata metadata schema, OGM Aardvark
15
15
***GBL 1.0**: The legacy metadata schema designed for GeoBlacklight versions 2.0-3.7. [The schema is documented on this Legacy page.](gbl-1.0.md)
16
16
***OGM Aardvark**: The new metadata schema that is compatible with GeoBlacklight version 4.0.
17
17
***GeoBlacklight**: When spelled out, GeoBlacklight refers to [the application itself](https://geoblacklight.org), not its namesake legacy metadata schema, GBL 1.0.
18
-
***URI**: This is the name we give to the metadata element itself. For example, the URI for the Subject field is `dct_subject_sm`.
19
-
***Namespace**: This is how we signify which family of standards or schemas an element belongs to. For the GeoBlacklight schema, this takes the form of the URI’s prefix. For the URI`dct_subject_sm`, `dct_` is the prefix and signifies that this element is from Dublin Core.
20
-
***Solr field type**: This is the suffix appended to the URI and indicates what kind of Solr field should be indexed. For `dct_subject_sm`, the `_sm` stands for String Multiple. It indicates that the field type is a string and that it can have multiple values.
18
+
***Field name**: This is the name we give to the metadata element itself. For example, the field name for the Subject field is `dct_subject_sm`.
19
+
***Namespace**: This is how we signify which family of standards or schemas an element belongs to. For the GeoBlacklight schema, this takes the form of the field name's prefix. For `dct_subject_sm`, `dct_` is the prefix and signifies that this element is from Dublin Core.
20
+
***Solr field type**: This is the suffix appended to the field name and indicates what kind of Solr field should be indexed. For `dct_subject_sm`, the `_sm` stands for String Multiple. It indicates that the field type is a string and that it can have multiple values.
21
21
***Value**: This is the information that is entered in a field. It may be free text (literal value) or a URI/code (nonliteral value).
22
22
23
23
OGM Aardvark is a discovery metadata schema for geospatial resources. It was intentionally developed with cross-application in mind and can be used to describe geospatial assets of all kinds.
@@ -56,7 +56,7 @@ The minimal nature of the original GeoBlacklight schema combined with the growin
56
56
57
57
The new set of rights elements are:
58
58
59
-
| Label |URI| Description and Entry Guidelines |
59
+
| Label |Field Name| Description and Entry Guidelines |
| Access Rights |`dct_accessRights_s`| One of two possible values, "Public" or "Restricted"; controls whether a user can preview or download an item. This element replaces `dc_rights_s`. |
62
62
| Rights |`dct_rights_sm`| Free-text field for generic, catch-all access and usage rights. Can include clickable links. |
@@ -73,7 +73,7 @@ GeoBlacklight version 3.4 and earlier has an Item Relations widget that displays
73
73
74
74
The new set of relationship elements are:
75
75
76
-
| Label |URI| Description and Entry Guidelines |
76
+
| Label |Field Name| Description and Entry Guidelines |
| Source |`dct_source_sm`| For items that have been derived from another item (e.g. a digitized shapefile from a historical map). |
79
79
| Is Part Of |`dct_isPartOf_sm`| For items that are a subset of another item (e.g. a page in a book). This value type is changing from free-text in Version 1.0 to an ID (slug) in the new schema. |
@@ -84,7 +84,7 @@ The new set of relationship elements are:
84
84
| Relation |`dct_relation_sm`| For a general purpose relation. |
85
85
86
86
87
-
#### Consistent namespaces for all metadata element URIs
87
+
#### Consistent namespaces for all metadata element field names
88
88
89
89
OGM Aardvark gives preference to elements found in established schemas over custom fields.
90
90
@@ -96,7 +96,7 @@ OGM Aardvark gives preference to elements found in established schemas over cust
96
96
97
97
#### Multivalued elements whenever possible
98
98
99
-
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`.
99
+
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 field name 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`.
100
100
101
101
#### More intuitive name for unique key
102
102
@@ -158,6 +158,3 @@ Refinements to OpenGeoMetadata have continued through the work of the ongoing Me
|[Identifier](#identifier)|`dc_identifier_s`| X ||
15
15
|[Rights](#rights)|`dc_rights_s`| X ||
@@ -43,7 +43,7 @@ hide:
43
43
44
44
| Label | Identifier|
45
45
|:----------------------|:-----------|
46
-
|uri|`dc_identifier_s`|
46
+
|Field Name|`dc_identifier_s`|
47
47
| Required | yes|
48
48
| Type | string|
49
49
| Description | Unique identifier for layer as a URI. It should be globally unique across all institutions, assumed not to be end-user visible|
@@ -58,7 +58,7 @@ hide:
58
58
59
59
| Label | Rights|
60
60
|:----------------------|:-----------|
61
-
|uri|`dc_rights_s`|
61
+
|Field Name|`dc_rights_s`|
62
62
| Required | yes|
63
63
| Type | string|
64
64
| Description | Signals access in the geoportal and is indicated by a padlock icon. Users need to sign in to download restricted items|
@@ -72,7 +72,7 @@ hide:
72
72
73
73
| Label | Title|
74
74
|:----------------------|:-----------|
75
-
|uri|`dc_title_s`|
75
+
|Field Name|`dc_title_s`|
76
76
| Required | yes|
77
77
| Type | string|
78
78
| Description | The name of the resource|
@@ -86,7 +86,7 @@ hide:
86
86
87
87
| Label | Provenance|
88
88
|:----------------------|:-----------|
89
-
|uri|`dct_provenance_s`|
89
+
|Field Name|`dct_provenance_s`|
90
90
| Required | yes|
91
91
| Type | string|
92
92
| Description | The name of the institution that holds the resource or acts as the custodian for the metadata record|
@@ -100,7 +100,7 @@ hide:
100
100
101
101
| Label | Schema Version|
102
102
|:----------------------|:-----------|
103
-
|uri|`geoblacklight_version`|
103
+
|Field Name|`geoblacklight_version`|
104
104
| Required | yes|
105
105
| Type | string|
106
106
| Description | Indicates which version of the GeoBlacklight schema is in use|
@@ -114,7 +114,7 @@ hide:
114
114
115
115
| Label | Slug|
116
116
|:----------------------|:-----------|
117
-
|uri|`layer_slug_s`|
117
+
|Field Name|`layer_slug_s`|
118
118
| Required | yes|
119
119
| Type | string|
120
120
| 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.|
@@ -128,7 +128,7 @@ hide:
128
128
129
129
| Label | Bounding Box|
130
130
|:----------------------|:-----------|
131
-
|uri|`solr_geom`|
131
+
|Field Name|`solr_geom`|
132
132
| Required | yes|
133
133
| Type | string|
134
134
| Description | The rectangular extents of the resource. Note that this field is indexed as a Solr spatial (RPT) field|
@@ -142,7 +142,7 @@ hide:
142
142
143
143
| Label | Solr Year|
144
144
|:----------------------|:-----------|
145
-
|uri|`solr_year_i`|
145
+
|Field Name|`solr_year_i`|
146
146
| Required | no|
147
147
| Type | integer|
148
148
| 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)|
@@ -156,7 +156,7 @@ hide:
156
156
157
157
| Label | Creator|
158
158
|:----------------------|:-----------|
159
-
|uri|`dc_creator_sm`|
159
+
|Field Name|`dc_creator_sm`|
160
160
| Required | no|
161
161
| Type | array|
162
162
| Description | The person(s) or organization that created the resource|
@@ -170,7 +170,7 @@ hide:
170
170
171
171
| Label| Description|
172
172
|:----------------------|:-----------|
173
-
|uri|`dc_description_s`|
173
+
|Field Name|`dc_description_s`|
174
174
| Required | no|
175
175
| Type | string|
176
176
| 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.|
@@ -184,7 +184,7 @@ hide:
184
184
185
185
| Label | Format|
186
186
|:----------------------|:-----------|
187
-
|uri|`dc_format_s`|
187
+
|Field Name|`dc_format_s`|
188
188
| Required | yes, if download link is included AND if download URL is configured as a single key:value pair|
189
189
| Type | string|
190
190
| Description | This indicates the file format of the data. If a download link is included, this value displays on the item page in the button under the download widget|
@@ -198,7 +198,7 @@ hide:
198
198
199
199
| Label | Language|
200
200
|:----------------------|:-----------|
201
-
|uri|`dc_language_sm`|
201
+
|Field Name|`dc_language_sm`|
202
202
| Required | no|
203
203
| Type | array|
204
204
| Description | Indicates the language of the data or map|
@@ -212,7 +212,7 @@ hide:
212
212
213
213
| Label | Publisher|
214
214
|:----------------------|:-----------|
215
-
|uri|`dc_publisher_s`|
215
+
|Field Name|`dc_publisher_s`|
216
216
| Required | no|
217
217
| Type | array|
218
218
| Description | The organization that made the original resource available|
@@ -226,7 +226,7 @@ hide:
226
226
227
227
| Label | Source|
228
228
|:----------------------|:-----------|
229
-
|uri|`dc_source_sm`|
229
+
|Field Name|`dc_source_sm`|
230
230
| Required | no|
231
231
| Type | array|
232
232
| Description | This is used to indicate parent/child relationships between data layers and activates the Data Relations widget in GeoBlacklight|
@@ -240,7 +240,7 @@ hide:
240
240
241
241
| Label | Subject|
242
242
|:----------------------|:-----------|
243
-
|uri|`dc_subject_sm`|
243
+
|Field Name|`dc_subject_sm`|
244
244
| Required | no|
245
245
| Type | array|
246
246
| Description | These are theme or topic keywords|
@@ -254,7 +254,7 @@ hide:
254
254
255
255
| Label | Type|
256
256
|:----------------------|:-----------|
257
-
|uri|`dc_type_s`|
257
+
|Field Name|`dc_type_s`|
258
258
| Required | no|
259
259
| Type | string|
260
260
| Description | This is a general element to indicate the larger genre of the resource|
@@ -268,7 +268,7 @@ hide:
268
268
269
269
| Label | Is Part Of|
270
270
|:----------------------|:-----------|
271
-
|uri|`dct_isPartOf_sm`|
271
+
|Field Name|`dct_isPartOf_sm`|
272
272
| Required | no|
273
273
| Type | array|
274
274
| Description | Holding entity for the layer, such as the title of a collection|
@@ -282,7 +282,7 @@ hide:
282
282
283
283
| Label | Date Issued|
284
284
|:----------------------|:-----------|
285
-
|uri|`dct_issued_s`|
285
+
|Field Name|`dct_issued_s`|
286
286
| Required | no|
287
287
| Type | string|
288
288
| Description | This is the publication date for the resource|
@@ -296,7 +296,7 @@ hide:
296
296
297
297
| Label | References|
298
298
|:----------------------|:-----------|
299
-
|uri|`dct_references_s`|
299
+
|Field Name|`dct_references_s`|
300
300
| Required | no|
301
301
| Type | string|
302
302
| 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|
@@ -310,7 +310,7 @@ hide:
310
310
311
311
| Label | Spatial Coverage|
312
312
|:----------------------|:-----------|
313
-
|uri|`dct_spatial_sm`|
313
+
|Field Name|`dct_spatial_sm`|
314
314
| Required | no|
315
315
| Type | array|
316
316
| Description | This field is for place name keywords|
@@ -324,7 +324,7 @@ hide:
324
324
325
325
| Label | Temporal Coverage|
326
326
|:----------------------|:-----------|
327
-
|uri|`dct_temporal_sm`|
327
+
|Field Name|`dct_temporal_sm`|
328
328
| Required | no|
329
329
| Type | array|
330
330
| 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|
@@ -338,7 +338,7 @@ hide:
338
338
339
339
| Label | Geometry Type|
340
340
|:----------------------|:-----------|
341
-
|uri|`layer_geom_type_s`|
341
+
|Field Name|`layer_geom_type_s`|
342
342
| Required | no|
343
343
| Type | string|
344
344
| Description | This element shows up as Data type in GeoBlacklight, and each value has an associated icon|
@@ -352,7 +352,7 @@ hide:
352
352
353
353
| Label | Layer ID|
354
354
|:----------------------|:-----------|
355
-
|uri|`layer_id_s`|
355
+
|Field Name|`layer_id_s`|
356
356
| Required | no|
357
357
| Type | string|
358
358
| Description | Indicates the layer id for any WMS or WFS web services listed in the `dct_references_s` field|
@@ -366,7 +366,7 @@ hide:
366
366
367
367
| Label | Modified Date|
368
368
|:----------------------|:-----------|
369
-
|uri|`layer_modified_dt`|
369
+
|Field Name|`layer_modified_dt`|
370
370
| Required | no|
371
371
| Type | date-time|
372
372
| Description | Last modification date for the metadata record|
@@ -380,7 +380,7 @@ hide:
380
380
381
381
| Label | Suppressed|
382
382
|:----------------------|:-----------|
383
-
|uri|`suppressed_b`|
383
+
|Field Name|`suppressed_b`|
384
384
| Required | no|
385
385
| Type | boolean|
386
386
| Description | If set to True, the record will not appear in search results. If is still accessible from the Data Relations widget and via direct URL.|
0 commit comments