Custom Elements
This page documents the custom metadata elements for the GeoBTAA Metadata Profile. These elements extend the official OpenGeoMetadata (Aardvark) schema.
Code
| Label |
Code |
| URI |
b1g_code_s |
| Profile ID |
b1g-01 |
| Obligation |
Required |
| Multiplicity |
1-1 |
| Field type |
string |
| Purpose |
To group records based upon their source |
| Entry Guidelines |
Codes are developed by the metadata coordinator and indicate the provider, the type of institution hosting the resources, and a numeric sequence number. For more details, see Code Naming Schema |
| Commentary |
This administrative field is used to group and track records based upon where they are harvested. This is frequently an identical value to "Member Of". The value will differ for records that are retired (these are removed from "Member Of") and records that are part of a subcollection. |
| Controlled Vocabulary |
yes-strict |
| Example value |
12d-01 |
| Element Set |
B1G |
Status
| Label |
Status |
| URI |
b1g_status_s |
| Profile ID |
b1g-02 |
| Obligation |
Optional |
| Multiplicity |
0-1 |
| Field type |
string |
| Purpose |
To indicate if a record is currently active, retired, or unknown. It can also be used to indicate if individual data layers from website has been indexed in the Geoportal. |
| Entry Guidelines |
Plain text string is acceptable |
| Commentary |
This is a legacy admin field that was previously used to track published vs retired items. The current needs are still TBD. |
| Controlled Vocabulary |
no |
| Example value |
Active |
| Element Set |
B1G |
Accrual Method
| Label |
Accrual Method |
| URI |
b1g_dct_accrualMethod_s |
| Profile ID |
b1g-03 |
| Obligation |
Required |
| Multiplicity |
1-1 |
| Field type |
string |
| Purpose |
To describe how the record was obtained |
| Entry Guidelines |
Some values, such as "ArcGIS Hub" should be entered consistently. Others may be more descriptive, such as "Manually entered from text file." |
| Commentary |
This allows us to find all of the ArcGIS records in one search. It also can help track records that have been harvested via different methods within the same collection. |
| Controlled Vocabulary |
no |
| Example value |
ArcGIS Hub |
| Element Set |
B1G/ Dublin Core |
Accrual Periodicity
| Label |
Accrual Periodicity |
| URI |
b1g_dct_accrualPeriodicity_s |
| Profile ID |
b1g-04 |
| Obligation |
Optional |
| Multiplicity |
0-1 |
| Field type |
string |
| Purpose |
To indicate how often a collection is reaccessioned |
| Entry Guidelines |
Enter one of the following values: Annually, Semiannually, Quarterly, Monthly, As Needed |
| Commentary |
This field is primarily for collection level records. |
| Controlled Vocabulary |
yes-not strict |
| Example value |
As Needed |
| Element Set |
B1G/ Dublin Core |
Date Accessioned
| Label |
Date Accessioned |
| URI |
b1g_dateAccessioned_s |
| Profile ID |
b1g-05 |
| Obligation |
Required |
| Multiplicity |
1-1 |
| Field type |
string |
| Purpose |
To store the date a record was harvested |
| Entry Guidelines |
Enter the date a record was harvested OR when it was added to the geoportal using the format yyyy-mm-dd |
| Commentary |
This field allows us to track how many records are ingested into the portal in a given time period and to which collections. |
| Controlled Vocabulary |
no |
| Example value |
2021-01-01 |
| Element Set |
B1G |
Date Retired
| Label |
Date Retired |
| URI |
b1g_dateRetired_s |
| Profile ID |
b1g-06 |
| Obligation |
Conditional |
| Multiplicity |
0-1 |
| Field type |
string |
| Purpose |
To store the date the record was removed from the geoportal public interface |
| Entry Guidelines |
Enter the date a record was removed from the geoportal |
| Commentary |
This field allows us to track how many records have been removed from the geoportal interface by time period and collection. |
| Controlled Vocabulary |
no |
| Example value |
2021-01-02 |
| Element Set |
B1G |
Child Record
| Label |
Child Record |
| URI |
b1g_child_record_b |
| Profile ID |
b1g-07 |
| Obligation |
Optional |
| Multiplicity |
0-1 |
| Field type |
string boolean |
| Purpose |
To apply an algorithm to the record that causes it to appear lower in search results |
| Entry Guidelines |
Only one of two values are allowed: true or false |
| Commentary |
This is used to lower a record's placement in search results. This can be useful for a large collection with many similar metadata values that might clutter a user's experience. |
| Controlled Vocabulary |
string boolean |
| Example value |
true |
| Element Set |
B1G |
| Label |
Mediator |
| URI |
b1g_dct_mediator_sm |
| Profile ID |
b1g-08 |
| Obligation |
Conditional |
| Multiplicity |
0-0 or 1-* |
| Field type |
string |
| Purpose |
To indicate the universities that have licensed access to a record |
| Entry Guidelines |
The value for this field should be one of the names for each institution that have been coded in the GeoBlacklight application. |
| Commentary |
This populates a facet on the search page so that users can filter to only databases that they are able log into based upon their institutional affiliation. |
| Controlled Vocabulary |
yes |
| Example value |
University of Wisconsin-Madison |
| Element Set |
B1G/ Dublin Core |
Access
Image
| Label |
Image |
| URI |
b1g_image_ss |
| Profile ID |
b1g-10 |
| Obligation |
Optional |
| Multiplicity |
0-0 or 0-1 |
| Field type |
stored string (URL) |
| Purpose |
To show a thumbnail on the search results page |
| Entry Guidelines |
Enter an image file using a secure link (https). Acceptable file types are JPEG or PNG |
| Commentary |
This link is used to harvest an image into the Geoportal server for storage and display. Once it has been harvested, it will remain in storage, even if the orginal link to the image stops working. |
| Controlled Vocabulary |
no |
| Example value |
https://gis.allencountyohio.com/GIS/Image/countyseal.jpg |
| Element Set |
B1G |
GeoNames
| Label |
GeoNames |
| URI |
b1g_geonames_sm |
| Profile ID |
b1g-11 |
| Obligation |
Optional |
| Multiplicity |
0-* |
| Field type |
stored string (URI) |
| Purpose |
To indicate a URI for a place name from the GeoNames database |
| Entry Guidelines |
Enter a value in the format "http://sws.geonames.org/URI" |
| Commentary |
This URI provides a linked data value for one or more place names. It is optional as there is currently no functionality tied to it in the GeoBlacklight application |
| Controlled Vocabulary |
yes |
| Example value |
https://sws.geonames.org/2988507 |
| Element Set |
B1G |
Publication State
| Label |
Publication State |
| URI |
b1g_publication_state_s |
| Profile ID |
b1g-12 |
| Obligation |
Required |
| Multiplicity |
1-1 |
| Field type |
string |
| Purpose |
To communicate to Solr if the item is public or hidden |
| Entry Guidelines |
Use the dropdown or batch editing functions to change the state |
| Commentary |
When items are first added to GBL Admin, they are set as Draft by default. When they are ready to be published, they can be manually changed to Published. If the record is retired or needs to be hidden, it can be changed to Unpublished |
| Controlled Vocabulary |
yes |
| Example value |
Draft |
| Element Set |
B1G |
Language string
| Label |
Language string |
| URI |
b1g_language_sm |
| Profile ID |
b1g-13 |
| Obligation |
Required |
| Multiplicity |
1-* |
| Field type |
string |
| Purpose |
To display the spelled out string (in English) of a language code to users |
| Entry Guidelines |
This field is automatically generated from the Language field in the main form |
| Commentary |
The OGM schema specified using a 3-digit code to indicate lanuage. In order to display this to users, it needs to be translated into a human-readable string. |
| Controlled Vocabulary |
yes |
| Example value |
French |
| Element Set |
B1G |
Creator ID
| Label |
Creator ID |
| URI |
b1g_creatorID_sm |
| Profile ID |
b1g-14 |
| Obligation |
Optional |
| Multiplicity |
0-* |
| Field type |
string |
| Purpose |
To track the URI of a creator value |
| 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 |
http://id.worldcat.org/fast/2013467 |
| Element Set |
B1G |
| 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 |
| 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 |
