Skip to content

Commit

Permalink
Merge pull request #787 from geobtaa/783_newFields
Browse files Browse the repository at this point in the history 
783 new fields
  • Loading branch information
@karenmajewicz
karenmajewicz authored Feb 5, 2025
2 parents 19fca5e + c2b0284 commit 45704f4
Show file tree
Hide file tree
Showing 8 changed files with 171 additions and 79 deletions.
8 changes: 4 additions & 4 deletions docs/arcgis-hub-guidelines.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,10 @@

`Version 2.0 - April 24, 2023`

!!! info

This document replaces the [BTAA GDP Accession Guidelines for ArcGIS Open Data Portals, version 1.0](arcgis-harvest-policy-2018.md).

## Overview

This document describes the BTAA-GIN Scanning Guidelines for ArcGIS Hubs, including eligible sites and records, harvest schedules, and remediation work. This policy may change at any time in response to updates to the ArcGIS Hub architecturs platform and/or the BTAA-GIN harvesting and remediation processes.
This document describes the BTAA-GIN Scanning Guidelines for ArcGIS Hubs, including eligible sites and records, harvest schedules, and remediation work. This policy may change at any time in response to updates to the ArcGIS Hub architecture platform and/or the BTAA-GIN harvesting and remediation processes.

## Eligible sites

Expand Down Expand Up @@ -39,4 +36,7 @@ This document describes the BTAA-GIN Scanning Guidelines for ArcGIS Hubs, includ
**Explanation**: We now scan a large number of ArcGIS Hubs, which makes manual remediation unrealistic. This is in contrast to the previous policy established in 2018, when our collection was smaller.


!!! info

This document replaces the [BTAA GDP Accession Guidelines for ArcGIS Open Data Portals, version 1.0](arcgis-harvest-policy-2018.md).

102 changes: 84 additions & 18 deletions docs/b1g-custom-elements.md
View file
Original file line number Diff line number Diff line change
@@ -1,24 +1,9 @@
# Custom Elements


This page documents the custom metadata elements for the GeoBTAA Metadata Profile. These elements extend the [official OpenGeoMetadata (Aardvark) schema](https://opengeometadata.org).

| b1g-id | Label | URI | Obligation |
| ------ | --------------------------------------------- | ------------------------------- | ----------- |
| b1g-01 | [Code](#code) | `b1g_code_s` | Required |
| b1g-02 | [Status](#status) | `b1g_status_s` | Optional |
| b1g-03 | [Accrual Method](#accrual-method) | `b1g_dct_accrualMethod_s` | Required |
| b1g-04 | [Accrual Periodicity](#accrual-periodicity) | `b1g_dct_accrualPeriodicity_s`| Optional |
| b1g-05 | [Date Accessioned](#date-accessioned) | `b1g_dateAccessioned_s` | Required |
| b1g-06 | [Date Retired](#date-retired) | `b1g_dateRetired_s` | Conditional |
| b1g-07 | [Child Record](#child-record) | `b1g_child_record_b` | Conditional |
| b1g-08 | [Mediator](#mediator) | `b1g_dct_mediator_sm` | Conditional |
| b1g-09 | [Access](#access) | `b1g_access_s` | Conditional |
| b1g-10 | [Image](#image) | `b1g_image_ss` | Optional |
| b1g-11 | [GeoNames](#geonames) | `b1g_geonames_sm` | Optional |
| b1g-12 | [Publication State](#publication-state) |`b1g_publication_state_s` | Required |
| b1g-13 | [Language String](#language-string) |`b1g_language_sm` | Required |
| b1g-14 | [Creator ID](#creator-id) |`b1g_creatorID_sm` |Optional|
{{ read_csv('tables/b1g-elements.csv') }}


## Code

Expand Down Expand Up @@ -243,5 +228,86 @@ This page documents the custom metadata elements for the GeoBTAA Metadata Profil
| Entry Guidelines | This field is entered as a URI representing an authority record |
| Commentary | These best practices recommend consulting one or two name registries when deciding how to standardize names of creators: the Faceted Application of Subject Terminology (FAST) or the Library of Congress Name Authority File (LCNAF). FAST is a controlled vocabulary based on the Library of Congress Subject Headings (LCSH) that is well-suited to the faceted navigation of the Geoportal. The LCNAF is an authoritative list of names, events, geographic locations and organizations used by libraries and other organizations to collocate authorized creator names to make searching and browsing easier.
| Controlled Vocabulary | yes |
| Example value | fst02013467 |
| Example value | http://id.worldcat.org/fast/2013467 |
| Element Set | B1G |


## Conforms To

| Label | Conforms To |
|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
| URI | `b1g_dct_conformsTo_sm` |
| Profile ID | b1g-15 |
| Obligation | Optional |
| Multiplicity | 0-* |
| Field type | string |
| Purpose | To display the coordinate reference system |
| Entry Guidelines | This field is entered as a URI from a known online reference, such as epsg.io |
| Commentary | This field is from Dublin Core. Our usage aligns with the DCAT-3 profile
| Controlled Vocabulary | no |
| Example value | https://epsg.io/26915 |
| Element Set | B1G/DCAT |

## Spatial Resolution in Meters

| Label | Spatial Resolution in Meters |
|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
| URI | `b1g_dcat_spatialResolutionInMeters_sm` |
| Profile ID | b1g-16 |
| Obligation | Optional |
| Multiplicity | 0-* |
| Field type | string |
| Purpose | To indicate the resolution of a raster dataset |
| Entry Guidelines | Enter a number representing the resolution in meters |
| Commentary | This is a DCAT-3 field |
| Controlled Vocabulary | no |
| Example value | 100 |
| Element Set | B1G/DCAT |

## Spatial Resolution as Text

| Label | Spatial Resolution as Text |
|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
| URI | `b1g_geodcat_spatialResolutionAsText_sm` |
| Profile ID | b1g-17 |
| Obligation | Optional |
| Multiplicity | 0-* |
| Field type | string |
| Purpose | To descriptively indicate the spatial resolution of an item |
| Entry Guidelines | Can be a scale, distance measure, or other free text. |
| Commentary | This can be used for any resource, but may be most applicable to scanned map records that have a Scale value in the original MARC metadata.
| Controlled Vocabulary | no |
| Example value | Scale: 1:24,000 |
| Element Set | B1G/GeoDCAT |

## Provenance Statement

| Label | Provenance Statement |
|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
| URI | `b1g_dct_provenanceStatement_sm` |
| Profile ID | b1g-18 |
| Obligation | Optional |
| Multiplicity | 0-* |
| Field type | string |
| Purpose | To indicate where a dataset came from |
| Entry Guidelines | Enter plain text. It may include URLs. |
| Commentary | This is primarily used for logging accessions, processing activities, and data sources. We are not currently using it to track where *metadata* was sourced- only where the *dataset* itself was sourced. This is a Dublin Core field that has been adopted by DCAT-3. It is a crosswalk from the lineage element in ISO 19139.
| Controlled Vocabulary | yes |
| Example value | Downloaded from https://www.nj.gov/transportation/refdata/gis/data.shtm August 19, 2024 |
| Element Set | B1G / DCAT |

## Admin Tags

| Label | Admin Tags |
|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
| URI | `b1g_adminTags_sm` |
| Profile ID | b1g-19 |
| Obligation | Optional |
| Multiplicity | 0-* |
| Field type | string |
| Purpose | To store local tags to aid in finding and filtering items. |
| Entry Guidelines | Enter tags and codes as strings. Examples are for records cleaned during sprints and metadata updates. |
| Commentary | This is a custom field that is only useful locally and not intended to be interoperable.
| Controlled Vocabulary | no |
| Example value | bbox_cleanupSprint_2024 |
| Element Set | B1G |
24 changes: 17 additions & 7 deletions docs/editingTemplate.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,23 @@ Users will need to make a copy of the spreadsheet to use for editing. In some c

The Template contains the following tabs:

- Map Template
- Dataset Template
- Website Record Template
- Values: All of the controlled vocabulary values for the associated fields.
- Access Links and Multiple Downloads: Fields for adding secondary tables.
- `Primary Template minimal`
: This tab provides the essential fields for most collections.

- `Primary Template full`
: This tab contains all of fields in our profile and is useful for records with more extensive metadata.

- `Distributions Template`
: This tab is for each resource's links, including landing pages, downloads, web services, and supplemental documentation.

- `Field Definitions`
: This lists all of the fields, their definitions, and key attributes.

- `Licensed Access Links`
: A special template for uploading access links for licensed databases

- `Controlled Vocabulary`
: A list of the acceptable values for certain fields. This tab powers the dropdown fields in the templates.

!!! Warning "Note"

Expand All @@ -17,5 +29,3 @@ The Template contains the following tabs:
- **Bounding Box** coordinates should be entered as `W,S,E,N`. The coordinates are automatically transformed to a different order `ENVELOPE(W,E,N,S)`. Read more under the [Local Input Guidelines](input-guidelines.md).

- **Date Range **should be entered as `yyyy-yyyy`. This is automatically transformed to [yyyy TO yyyy].

- External links are added separately under column headers for the type of link. These are combined into the `dct_references_s` field as a string of key:value pairs.
2 changes: 1 addition & 1 deletion docs/glossary.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ CKAN is a tool for making open data websites, it helps you manage and publish co

This chart provides links to documentation about the common metadata standards and schemas we encounter when harvesting.

{{ read_csv('../tables/metadataStandards.csv') }}
{{ read_csv('tables/metadataStandards.csv') }}

* Dublin Core: A set of metadata elements that are used to describe resources in a simple and standardized way. Dublin Core is widely used in library systems, archives, and other digital repositories.
* MODS (Metadata Object Description Schema): A flexible and extensible XML schema for describing a wide range of resources, including books, articles, and other types of digital content.
Expand Down
Loading

0 comments on commit 45704f4

Please sign in to comment.