404
+ +Page not found
+ + +'+ escapeHtml(title) + '
' + escapeHtml(summary) +'
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ BTAA Specific Entry Guidelines
+The BTAA Geoportal has more specific guidelines for some fields from OpenGeoMetadata (OGM).
+Title
+Maps: The title for scanned maps is generally left as it was originally cataloged by a participating library. MARC subfields are omitted and can be inserted in the Description field.
+Datasets: Harvested datasets often are lacking descriptive titles and may need to be augmented with place names. Dates may also be added to the end, but if the dataset is subject to updates, the data should be left off. Acronyms should be spelled out. The preferred format for dataset titles is:
+Theme [place] {date}. This punctuation allows for batch processing and splitting title elements.
Language
+Although Language is optional in the OGM schema, a three-digit code is required for the BTAA Geoportal.
+Creator
+Spell all Acronyms out.
+Publisher
+Maps: Publisher values for maps are pulled from the original catalog record. Remove subfields for place names and dates.
+Datasets: The BTAA Geoportal does not use the Publisher field for Datasets.
+Provider
+This is the name of the organization hosting the resources. If the organization is part of the BTAA library network, a university icon will display next to the resource's title. However, most Providers will not have an icon.
+The BTAA Geoportal has a much longer list of Providers than other GeoBlacklight instances. This is because we are harvesting metadata from external sources, rather than just participating library institutions.
+Bounding Box
+Provide Bounding Boxes in this format: W,S,E,N
+When the record is published to the Geoportal, these coordinates will be programmatically converted to other formats. The Bounding Box field (dcat_bbox_s) uses this order: ENVELOPE(W,E,N,S)
The Geometry field (locn_geometry) uses a WKT format and the coordinate order will be converted to this layout: POLYGON((W N, E N, E S, W S, W N))
Example: +Metadata CSV: -120,10,-80,35
+converts to
+dcat_bbox_s: ENVELOPE(-120,-80,35,10)
locn_geometry: POLYGON((-120 35, -80 35, -80 10, -120 10, -120 35))
+
+
+
+ « Previous
+
+
+ Next »
+
+
+
+
+
+
+
+
+
+
+
diff --git a/docs/images/btaa-metadata-workflow.png b/images/btaa-metadata-workflow.png
similarity index 100%
rename from docs/images/btaa-metadata-workflow.png
rename to images/btaa-metadata-workflow.png
diff --git a/docs/images/contentOrganization.png b/images/contentOrganization.png
similarity index 100%
rename from docs/images/contentOrganization.png
rename to images/contentOrganization.png
diff --git a/img/favicon.ico b/img/favicon.ico
new file mode 100644
index 00000000..e85006a3
Binary files /dev/null and b/img/favicon.ico differ
diff --git a/index.html b/index.html
new file mode 100644
index 00000000..c4254183
--- /dev/null
+++ b/index.html
@@ -0,0 +1,178 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Metadata Handbook
+Big Ten Academic Alliance Geoportal
+
This guide was prepared with the objective of assisting Team Members in the Big Ten Academic Alliance Geospatial Information Network on the BTAA Geoportal's metadata schema, content organization model, and workflows.
+Quicklinks
+All OpenGeoMetadata schema elements
+ + +Version History
+Changes for Version 4.2 (March 24, 2022) +- New Entry and Usage Guidelines page +- Expands content organization model documentation +- Changes the name of the schema from 'Aardvark' to 'OpenGeoMetadata (version Aardvark)' +- Cleans up outdated links
+Changes for Version 4.1 (Jan 2022) +- updates Status as optional; removes controlled vocabulary +- Clarifies relationship model
+Changes for Version 4.0 (July 2021) +- Incorporation of GEOMG Metadata Editor +- Upgrade to Aardvark Metadata Schema for GeoBlacklight
+Changes for version 3.3 (May 13, 2020) +- Added University of Nebraska +- Reorganized Metadata Elements to match editing template +- Updated the “Update the Collections” section to match new administrative process for tracking records
+Changes for version 3.2 (Jan 8, 2020) +- Added Date Range element
+Changes for version 3.1 (Dec 19, 2019) +- Added collection level records metadata schema
+Changes for version 3 (Oct, 2019) +- GeoNetwork and Omeka deprecated +- all GeoBlacklight records are stored in a master spreadsheet in Google - Sheets +- records are transformed from CSV to GeoBlacklight JSON with a Python script +- additional metadata fields were added for administrative purposes +- IsPartOf field now holds a code pointing to the collection record +- Administrative groupings such as “State agencies geospatial data” are now subjects, not a Collection +- updated editing templates available +- all supplemental metadata can be stored as XML or HTML in project hosted folder +- updated links to collections database
+Credits +Handbook prepared by: +- Karen Majewicz, Project Metadata Coordinator +- Ziying (Gene) Cheng - Graduate Research Assistant
+ +
+
+
+
+
+ Next »
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/js/html5shiv.min.js b/js/html5shiv.min.js
new file mode 100644
index 00000000..1a01c94b
--- /dev/null
+++ b/js/html5shiv.min.js
@@ -0,0 +1,4 @@
+/**
+* @preserve HTML5 Shiv 3.7.3 | @afarkas @jdalton @jon_neal @rem | MIT/GPL2 Licensed
+*/
+!function(a,b){function c(a,b){var c=a.createElement("p"),d=a.getElementsByTagName("head")[0]||a.documentElement;return c.innerHTML="x",d.insertBefore(c.lastChild,d.firstChild)}function d(){var a=t.elements;return"string"==typeof a?a.split(" "):a}function e(a,b){var c=t.elements;"string"!=typeof c&&(c=c.join(" ")),"string"!=typeof a&&(a=a.join(" ")),t.elements=c+" "+a,j(b)}function f(a){var b=s[a[q]];return b||(b={},r++,a[q]=r,s[r]=b),b}function g(a,c,d){if(c||(c=b),l)return c.createElement(a);d||(d=f(c));var e;return e=d.cache[a]?d.cache[a].cloneNode():p.test(a)?(d.cache[a]=d.createElem(a)).cloneNode():d.createElem(a),!e.canHaveChildren||o.test(a)||e.tagUrn?e:d.frag.appendChild(e)}function h(a,c){if(a||(a=b),l)return a.createDocumentFragment();c=c||f(a);for(var e=c.frag.cloneNode(),g=0,h=d(),i=h.length;i>g;g++)e.createElement(h[g]);return e}function i(a,b){b.cache||(b.cache={},b.createElem=a.createElement,b.createFrag=a.createDocumentFragment,b.frag=b.createFrag()),a.createElement=function(c){return t.shivMethods?g(c,a,b):b.createElem(c)},a.createDocumentFragment=Function("h,f","return function(){var n=f.cloneNode(),c=n.createElement;h.shivMethods&&("+d().join().replace(/[\w\-:]+/g,function(a){return b.createElem(a),b.frag.createElement(a),'c("'+a+'")'})+");return n}")(t,b.frag)}function j(a){a||(a=b);var d=f(a);return!t.shivCSS||k||d.hasCSS||(d.hasCSS=!!c(a,"article,aside,dialog,figcaption,figure,footer,header,hgroup,main,nav,section{display:block}mark{background:#FF0;color:#000}template{display:none}")),l||i(a,d),a}var k,l,m="3.7.3",n=a.html5||{},o=/^<|^(?:button|map|select|textarea|object|iframe|option|optgroup)$/i,p=/^(?:a|b|code|div|fieldset|h1|h2|h3|h4|h5|h6|i|label|li|ol|p|q|span|strong|style|table|tbody|td|th|tr|ul)$/i,q="_html5shiv",r=0,s={};!function(){try{var a=b.createElement("a");a.innerHTML="
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Relations and the Collection Model
+This document describes the content organization model for the GeoBlacklight application and how to relate records in the BTAA Geoportal.
+Content Organization Model
+GeoBlacklight organizes records with a network model rather than with a hierarchical model. It is a flat system whereby every database entry is a "Layer" and uses the same metadata fields. Unlike many digital library applications, it does not have different types of records for entities such as "communities," "collections," or "groups." As a result, it does not present a breadcrumb navigation structure, and all records appear in the same catalog directory with the URL of https:geo.btaa.org/catalog/ID.
Instead of a hierarchy, GeoBlacklight relates records via metadata fields. These fields include Member Of, Is Part Of, Is Version Of, Source, and a general Relation. This flexibility allows records to be presented in several different ways. For example, records can have multiple parent/child/grandchild/sibling relationships. In addition, they can be nested (i.e., a collection can belong to another collection). They can also connect data layers about similar topics or represent different years in a series.
The following diagram illustrates how the BTAA Geoportal organizes records. The connecting arrow lines indicate the name of the relationship. The labels reflect each record's Resource Class (Collections, Websites, Datasets, Maps, Web services).
+
Collections
+The BTAA Geoportal interprets the Resource Class, Collections, as top-level, custom groupings. These reflect our curation activities and priorities.
+Other records are linked to Collections using the Member Of field. The ID of the parent record is added to the child record only. View all of the current Collections in the geoportal at this link:
+https://geo.btaa.org/?f%5Bgbl_resourceClass_sm%5D%5B%5D=Collections
+
Websites
+The BTAA Geoportal uses the Resource Class, Websites, to create parent records for data portals, digital libraries, dashboards, and interactive maps. These often start off as standalone records. +Once the items in a website have been indexed, they will have child records.
+Individual Datasets, Maps, or Web services are linked to the Website they came from using the Is Part Of field. The ID of the parent record is added to the child record only.
View all of the current Websites in the geoportal at this link: https://geo.btaa.org/?f%5Bgbl_resourceClass_sm%5D%5B%5D=Websites
++
Datasets, Maps, and Web services
+The items in this Resource Class represent individual data layers, scanned map files, and/or geospatial web services. (Some items may have multiple Resource Classes attached to the same record.)
+This item class is likely to have the most relationships specified in the metadata. A typical Datasets record might have the following:
+-
+
Member Ofa Collections record
+Is Part Ofa Websites record
+- If the data was digitized from a paper map in the geoportal, it can be linked to the Maps record via the
Sourcerelation
+ - a general
Relationto a research guide or similar dataset
+
+
Multipart Items
+Many items in the geoportal are multipart. There may be individual pages from an atlas, sublayers from a larger project, or datasets broken up into more than one download. In these cases, the Is Part Of field is used.
As a result, these items may have multiple Is Part Of relationships- (1) the parent for the multipart items and (2) the original website.
+
+
+
+ « Previous
+
+
+ Next »
+
+
+
+
+
+
+
+
+
+
+
diff --git a/search.html b/search.html
new file mode 100644
index 00000000..ced9ac5c
--- /dev/null
+++ b/search.html
@@ -0,0 +1,130 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Search Results
+ + + +
+ Searching...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/search/lunr.js b/search/lunr.js
new file mode 100644
index 00000000..6aa370fb
--- /dev/null
+++ b/search/lunr.js
@@ -0,0 +1,3475 @@
+/**
+ * lunr - http://lunrjs.com - A bit like Solr, but much smaller and not as bright - 2.3.9
+ * Copyright (C) 2020 Oliver Nightingale
+ * @license MIT
+ */
+
+;(function(){
+
+/**
+ * A convenience function for configuring and constructing
+ * a new lunr Index.
+ *
+ * A lunr.Builder instance is created and the pipeline setup
+ * with a trimmer, stop word filter and stemmer.
+ *
+ * This builder object is yielded to the configuration function
+ * that is passed as a parameter, allowing the list of fields
+ * and other builder parameters to be customised.
+ *
+ * All documents _must_ be added within the passed config function.
+ *
+ * @example
+ * var idx = lunr(function () {
+ * this.field('title')
+ * this.field('body')
+ * this.ref('id')
+ *
+ * documents.forEach(function (doc) {
+ * this.add(doc)
+ * }, this)
+ * })
+ *
+ * @see {@link lunr.Builder}
+ * @see {@link lunr.Pipeline}
+ * @see {@link lunr.trimmer}
+ * @see {@link lunr.stopWordFilter}
+ * @see {@link lunr.stemmer}
+ * @namespace {function} lunr
+ */
+var lunr = function (config) {
+ var builder = new lunr.Builder
+
+ builder.pipeline.add(
+ lunr.trimmer,
+ lunr.stopWordFilter,
+ lunr.stemmer
+ )
+
+ builder.searchPipeline.add(
+ lunr.stemmer
+ )
+
+ config.call(builder, builder)
+ return builder.build()
+}
+
+lunr.version = "2.3.9"
+/*!
+ * lunr.utils
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A namespace containing utils for the rest of the lunr library
+ * @namespace lunr.utils
+ */
+lunr.utils = {}
+
+/**
+ * Print a warning message to the console.
+ *
+ * @param {String} message The message to be printed.
+ * @memberOf lunr.utils
+ * @function
+ */
+lunr.utils.warn = (function (global) {
+ /* eslint-disable no-console */
+ return function (message) {
+ if (global.console && console.warn) {
+ console.warn(message)
+ }
+ }
+ /* eslint-enable no-console */
+})(this)
+
+/**
+ * Convert an object to a string.
+ *
+ * In the case of `null` and `undefined` the function returns
+ * the empty string, in all other cases the result of calling
+ * `toString` on the passed object is returned.
+ *
+ * @param {Any} obj The object to convert to a string.
+ * @return {String} string representation of the passed object.
+ * @memberOf lunr.utils
+ */
+lunr.utils.asString = function (obj) {
+ if (obj === void 0 || obj === null) {
+ return ""
+ } else {
+ return obj.toString()
+ }
+}
+
+/**
+ * Clones an object.
+ *
+ * Will create a copy of an existing object such that any mutations
+ * on the copy cannot affect the original.
+ *
+ * Only shallow objects are supported, passing a nested object to this
+ * function will cause a TypeError.
+ *
+ * Objects with primitives, and arrays of primitives are supported.
+ *
+ * @param {Object} obj The object to clone.
+ * @return {Object} a clone of the passed object.
+ * @throws {TypeError} when a nested object is passed.
+ * @memberOf Utils
+ */
+lunr.utils.clone = function (obj) {
+ if (obj === null || obj === undefined) {
+ return obj
+ }
+
+ var clone = Object.create(null),
+ keys = Object.keys(obj)
+
+ for (var i = 0; i < keys.length; i++) {
+ var key = keys[i],
+ val = obj[key]
+
+ if (Array.isArray(val)) {
+ clone[key] = val.slice()
+ continue
+ }
+
+ if (typeof val === 'string' ||
+ typeof val === 'number' ||
+ typeof val === 'boolean') {
+ clone[key] = val
+ continue
+ }
+
+ throw new TypeError("clone is not deep and does not support nested objects")
+ }
+
+ return clone
+}
+lunr.FieldRef = function (docRef, fieldName, stringValue) {
+ this.docRef = docRef
+ this.fieldName = fieldName
+ this._stringValue = stringValue
+}
+
+lunr.FieldRef.joiner = "/"
+
+lunr.FieldRef.fromString = function (s) {
+ var n = s.indexOf(lunr.FieldRef.joiner)
+
+ if (n === -1) {
+ throw "malformed field ref string"
+ }
+
+ var fieldRef = s.slice(0, n),
+ docRef = s.slice(n + 1)
+
+ return new lunr.FieldRef (docRef, fieldRef, s)
+}
+
+lunr.FieldRef.prototype.toString = function () {
+ if (this._stringValue == undefined) {
+ this._stringValue = this.fieldName + lunr.FieldRef.joiner + this.docRef
+ }
+
+ return this._stringValue
+}
+/*!
+ * lunr.Set
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A lunr set.
+ *
+ * @constructor
+ */
+lunr.Set = function (elements) {
+ this.elements = Object.create(null)
+
+ if (elements) {
+ this.length = elements.length
+
+ for (var i = 0; i < this.length; i++) {
+ this.elements[elements[i]] = true
+ }
+ } else {
+ this.length = 0
+ }
+}
+
+/**
+ * A complete set that contains all elements.
+ *
+ * @static
+ * @readonly
+ * @type {lunr.Set}
+ */
+lunr.Set.complete = {
+ intersect: function (other) {
+ return other
+ },
+
+ union: function () {
+ return this
+ },
+
+ contains: function () {
+ return true
+ }
+}
+
+/**
+ * An empty set that contains no elements.
+ *
+ * @static
+ * @readonly
+ * @type {lunr.Set}
+ */
+lunr.Set.empty = {
+ intersect: function () {
+ return this
+ },
+
+ union: function (other) {
+ return other
+ },
+
+ contains: function () {
+ return false
+ }
+}
+
+/**
+ * Returns true if this set contains the specified object.
+ *
+ * @param {object} object - Object whose presence in this set is to be tested.
+ * @returns {boolean} - True if this set contains the specified object.
+ */
+lunr.Set.prototype.contains = function (object) {
+ return !!this.elements[object]
+}
+
+/**
+ * Returns a new set containing only the elements that are present in both
+ * this set and the specified set.
+ *
+ * @param {lunr.Set} other - set to intersect with this set.
+ * @returns {lunr.Set} a new set that is the intersection of this and the specified set.
+ */
+
+lunr.Set.prototype.intersect = function (other) {
+ var a, b, elements, intersection = []
+
+ if (other === lunr.Set.complete) {
+ return this
+ }
+
+ if (other === lunr.Set.empty) {
+ return other
+ }
+
+ if (this.length < other.length) {
+ a = this
+ b = other
+ } else {
+ a = other
+ b = this
+ }
+
+ elements = Object.keys(a.elements)
+
+ for (var i = 0; i < elements.length; i++) {
+ var element = elements[i]
+ if (element in b.elements) {
+ intersection.push(element)
+ }
+ }
+
+ return new lunr.Set (intersection)
+}
+
+/**
+ * Returns a new set combining the elements of this and the specified set.
+ *
+ * @param {lunr.Set} other - set to union with this set.
+ * @return {lunr.Set} a new set that is the union of this and the specified set.
+ */
+
+lunr.Set.prototype.union = function (other) {
+ if (other === lunr.Set.complete) {
+ return lunr.Set.complete
+ }
+
+ if (other === lunr.Set.empty) {
+ return this
+ }
+
+ return new lunr.Set(Object.keys(this.elements).concat(Object.keys(other.elements)))
+}
+/**
+ * A function to calculate the inverse document frequency for
+ * a posting. This is shared between the builder and the index
+ *
+ * @private
+ * @param {object} posting - The posting for a given term
+ * @param {number} documentCount - The total number of documents.
+ */
+lunr.idf = function (posting, documentCount) {
+ var documentsWithTerm = 0
+
+ for (var fieldName in posting) {
+ if (fieldName == '_index') continue // Ignore the term index, its not a field
+ documentsWithTerm += Object.keys(posting[fieldName]).length
+ }
+
+ var x = (documentCount - documentsWithTerm + 0.5) / (documentsWithTerm + 0.5)
+
+ return Math.log(1 + Math.abs(x))
+}
+
+/**
+ * A token wraps a string representation of a token
+ * as it is passed through the text processing pipeline.
+ *
+ * @constructor
+ * @param {string} [str=''] - The string token being wrapped.
+ * @param {object} [metadata={}] - Metadata associated with this token.
+ */
+lunr.Token = function (str, metadata) {
+ this.str = str || ""
+ this.metadata = metadata || {}
+}
+
+/**
+ * Returns the token string that is being wrapped by this object.
+ *
+ * @returns {string}
+ */
+lunr.Token.prototype.toString = function () {
+ return this.str
+}
+
+/**
+ * A token update function is used when updating or optionally
+ * when cloning a token.
+ *
+ * @callback lunr.Token~updateFunction
+ * @param {string} str - The string representation of the token.
+ * @param {Object} metadata - All metadata associated with this token.
+ */
+
+/**
+ * Applies the given function to the wrapped string token.
+ *
+ * @example
+ * token.update(function (str, metadata) {
+ * return str.toUpperCase()
+ * })
+ *
+ * @param {lunr.Token~updateFunction} fn - A function to apply to the token string.
+ * @returns {lunr.Token}
+ */
+lunr.Token.prototype.update = function (fn) {
+ this.str = fn(this.str, this.metadata)
+ return this
+}
+
+/**
+ * Creates a clone of this token. Optionally a function can be
+ * applied to the cloned token.
+ *
+ * @param {lunr.Token~updateFunction} [fn] - An optional function to apply to the cloned token.
+ * @returns {lunr.Token}
+ */
+lunr.Token.prototype.clone = function (fn) {
+ fn = fn || function (s) { return s }
+ return new lunr.Token (fn(this.str, this.metadata), this.metadata)
+}
+/*!
+ * lunr.tokenizer
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A function for splitting a string into tokens ready to be inserted into
+ * the search index. Uses `lunr.tokenizer.separator` to split strings, change
+ * the value of this property to change how strings are split into tokens.
+ *
+ * This tokenizer will convert its parameter to a string by calling `toString` and
+ * then will split this string on the character in `lunr.tokenizer.separator`.
+ * Arrays will have their elements converted to strings and wrapped in a lunr.Token.
+ *
+ * Optional metadata can be passed to the tokenizer, this metadata will be cloned and
+ * added as metadata to every token that is created from the object to be tokenized.
+ *
+ * @static
+ * @param {?(string|object|object[])} obj - The object to convert into tokens
+ * @param {?object} metadata - Optional metadata to associate with every token
+ * @returns {lunr.Token[]}
+ * @see {@link lunr.Pipeline}
+ */
+lunr.tokenizer = function (obj, metadata) {
+ if (obj == null || obj == undefined) {
+ return []
+ }
+
+ if (Array.isArray(obj)) {
+ return obj.map(function (t) {
+ return new lunr.Token(
+ lunr.utils.asString(t).toLowerCase(),
+ lunr.utils.clone(metadata)
+ )
+ })
+ }
+
+ var str = obj.toString().toLowerCase(),
+ len = str.length,
+ tokens = []
+
+ for (var sliceEnd = 0, sliceStart = 0; sliceEnd <= len; sliceEnd++) {
+ var char = str.charAt(sliceEnd),
+ sliceLength = sliceEnd - sliceStart
+
+ if ((char.match(lunr.tokenizer.separator) || sliceEnd == len)) {
+
+ if (sliceLength > 0) {
+ var tokenMetadata = lunr.utils.clone(metadata) || {}
+ tokenMetadata["position"] = [sliceStart, sliceLength]
+ tokenMetadata["index"] = tokens.length
+
+ tokens.push(
+ new lunr.Token (
+ str.slice(sliceStart, sliceEnd),
+ tokenMetadata
+ )
+ )
+ }
+
+ sliceStart = sliceEnd + 1
+ }
+
+ }
+
+ return tokens
+}
+
+/**
+ * The separator used to split a string into tokens. Override this property to change the behaviour of
+ * `lunr.tokenizer` behaviour when tokenizing strings. By default this splits on whitespace and hyphens.
+ *
+ * @static
+ * @see lunr.tokenizer
+ */
+lunr.tokenizer.separator = /[\s\-]+/
+/*!
+ * lunr.Pipeline
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * lunr.Pipelines maintain an ordered list of functions to be applied to all
+ * tokens in documents entering the search index and queries being ran against
+ * the index.
+ *
+ * An instance of lunr.Index created with the lunr shortcut will contain a
+ * pipeline with a stop word filter and an English language stemmer. Extra
+ * functions can be added before or after either of these functions or these
+ * default functions can be removed.
+ *
+ * When run the pipeline will call each function in turn, passing a token, the
+ * index of that token in the original list of all tokens and finally a list of
+ * all the original tokens.
+ *
+ * The output of functions in the pipeline will be passed to the next function
+ * in the pipeline. To exclude a token from entering the index the function
+ * should return undefined, the rest of the pipeline will not be called with
+ * this token.
+ *
+ * For serialisation of pipelines to work, all functions used in an instance of
+ * a pipeline should be registered with lunr.Pipeline. Registered functions can
+ * then be loaded. If trying to load a serialised pipeline that uses functions
+ * that are not registered an error will be thrown.
+ *
+ * If not planning on serialising the pipeline then registering pipeline functions
+ * is not necessary.
+ *
+ * @constructor
+ */
+lunr.Pipeline = function () {
+ this._stack = []
+}
+
+lunr.Pipeline.registeredFunctions = Object.create(null)
+
+/**
+ * A pipeline function maps lunr.Token to lunr.Token. A lunr.Token contains the token
+ * string as well as all known metadata. A pipeline function can mutate the token string
+ * or mutate (or add) metadata for a given token.
+ *
+ * A pipeline function can indicate that the passed token should be discarded by returning
+ * null, undefined or an empty string. This token will not be passed to any downstream pipeline
+ * functions and will not be added to the index.
+ *
+ * Multiple tokens can be returned by returning an array of tokens. Each token will be passed
+ * to any downstream pipeline functions and all will returned tokens will be added to the index.
+ *
+ * Any number of pipeline functions may be chained together using a lunr.Pipeline.
+ *
+ * @interface lunr.PipelineFunction
+ * @param {lunr.Token} token - A token from the document being processed.
+ * @param {number} i - The index of this token in the complete list of tokens for this document/field.
+ * @param {lunr.Token[]} tokens - All tokens for this document/field.
+ * @returns {(?lunr.Token|lunr.Token[])}
+ */
+
+/**
+ * Register a function with the pipeline.
+ *
+ * Functions that are used in the pipeline should be registered if the pipeline
+ * needs to be serialised, or a serialised pipeline needs to be loaded.
+ *
+ * Registering a function does not add it to a pipeline, functions must still be
+ * added to instances of the pipeline for them to be used when running a pipeline.
+ *
+ * @param {lunr.PipelineFunction} fn - The function to check for.
+ * @param {String} label - The label to register this function with
+ */
+lunr.Pipeline.registerFunction = function (fn, label) {
+ if (label in this.registeredFunctions) {
+ lunr.utils.warn('Overwriting existing registered function: ' + label)
+ }
+
+ fn.label = label
+ lunr.Pipeline.registeredFunctions[fn.label] = fn
+}
+
+/**
+ * Warns if the function is not registered as a Pipeline function.
+ *
+ * @param {lunr.PipelineFunction} fn - The function to check for.
+ * @private
+ */
+lunr.Pipeline.warnIfFunctionNotRegistered = function (fn) {
+ var isRegistered = fn.label && (fn.label in this.registeredFunctions)
+
+ if (!isRegistered) {
+ lunr.utils.warn('Function is not registered with pipeline. This may cause problems when serialising the index.\n', fn)
+ }
+}
+
+/**
+ * Loads a previously serialised pipeline.
+ *
+ * All functions to be loaded must already be registered with lunr.Pipeline.
+ * If any function from the serialised data has not been registered then an
+ * error will be thrown.
+ *
+ * @param {Object} serialised - The serialised pipeline to load.
+ * @returns {lunr.Pipeline}
+ */
+lunr.Pipeline.load = function (serialised) {
+ var pipeline = new lunr.Pipeline
+
+ serialised.forEach(function (fnName) {
+ var fn = lunr.Pipeline.registeredFunctions[fnName]
+
+ if (fn) {
+ pipeline.add(fn)
+ } else {
+ throw new Error('Cannot load unregistered function: ' + fnName)
+ }
+ })
+
+ return pipeline
+}
+
+/**
+ * Adds new functions to the end of the pipeline.
+ *
+ * Logs a warning if the function has not been registered.
+ *
+ * @param {lunr.PipelineFunction[]} functions - Any number of functions to add to the pipeline.
+ */
+lunr.Pipeline.prototype.add = function () {
+ var fns = Array.prototype.slice.call(arguments)
+
+ fns.forEach(function (fn) {
+ lunr.Pipeline.warnIfFunctionNotRegistered(fn)
+ this._stack.push(fn)
+ }, this)
+}
+
+/**
+ * Adds a single function after a function that already exists in the
+ * pipeline.
+ *
+ * Logs a warning if the function has not been registered.
+ *
+ * @param {lunr.PipelineFunction} existingFn - A function that already exists in the pipeline.
+ * @param {lunr.PipelineFunction} newFn - The new function to add to the pipeline.
+ */
+lunr.Pipeline.prototype.after = function (existingFn, newFn) {
+ lunr.Pipeline.warnIfFunctionNotRegistered(newFn)
+
+ var pos = this._stack.indexOf(existingFn)
+ if (pos == -1) {
+ throw new Error('Cannot find existingFn')
+ }
+
+ pos = pos + 1
+ this._stack.splice(pos, 0, newFn)
+}
+
+/**
+ * Adds a single function before a function that already exists in the
+ * pipeline.
+ *
+ * Logs a warning if the function has not been registered.
+ *
+ * @param {lunr.PipelineFunction} existingFn - A function that already exists in the pipeline.
+ * @param {lunr.PipelineFunction} newFn - The new function to add to the pipeline.
+ */
+lunr.Pipeline.prototype.before = function (existingFn, newFn) {
+ lunr.Pipeline.warnIfFunctionNotRegistered(newFn)
+
+ var pos = this._stack.indexOf(existingFn)
+ if (pos == -1) {
+ throw new Error('Cannot find existingFn')
+ }
+
+ this._stack.splice(pos, 0, newFn)
+}
+
+/**
+ * Removes a function from the pipeline.
+ *
+ * @param {lunr.PipelineFunction} fn The function to remove from the pipeline.
+ */
+lunr.Pipeline.prototype.remove = function (fn) {
+ var pos = this._stack.indexOf(fn)
+ if (pos == -1) {
+ return
+ }
+
+ this._stack.splice(pos, 1)
+}
+
+/**
+ * Runs the current list of functions that make up the pipeline against the
+ * passed tokens.
+ *
+ * @param {Array} tokens The tokens to run through the pipeline.
+ * @returns {Array}
+ */
+lunr.Pipeline.prototype.run = function (tokens) {
+ var stackLength = this._stack.length
+
+ for (var i = 0; i < stackLength; i++) {
+ var fn = this._stack[i]
+ var memo = []
+
+ for (var j = 0; j < tokens.length; j++) {
+ var result = fn(tokens[j], j, tokens)
+
+ if (result === null || result === void 0 || result === '') continue
+
+ if (Array.isArray(result)) {
+ for (var k = 0; k < result.length; k++) {
+ memo.push(result[k])
+ }
+ } else {
+ memo.push(result)
+ }
+ }
+
+ tokens = memo
+ }
+
+ return tokens
+}
+
+/**
+ * Convenience method for passing a string through a pipeline and getting
+ * strings out. This method takes care of wrapping the passed string in a
+ * token and mapping the resulting tokens back to strings.
+ *
+ * @param {string} str - The string to pass through the pipeline.
+ * @param {?object} metadata - Optional metadata to associate with the token
+ * passed to the pipeline.
+ * @returns {string[]}
+ */
+lunr.Pipeline.prototype.runString = function (str, metadata) {
+ var token = new lunr.Token (str, metadata)
+
+ return this.run([token]).map(function (t) {
+ return t.toString()
+ })
+}
+
+/**
+ * Resets the pipeline by removing any existing processors.
+ *
+ */
+lunr.Pipeline.prototype.reset = function () {
+ this._stack = []
+}
+
+/**
+ * Returns a representation of the pipeline ready for serialisation.
+ *
+ * Logs a warning if the function has not been registered.
+ *
+ * @returns {Array}
+ */
+lunr.Pipeline.prototype.toJSON = function () {
+ return this._stack.map(function (fn) {
+ lunr.Pipeline.warnIfFunctionNotRegistered(fn)
+
+ return fn.label
+ })
+}
+/*!
+ * lunr.Vector
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A vector is used to construct the vector space of documents and queries. These
+ * vectors support operations to determine the similarity between two documents or
+ * a document and a query.
+ *
+ * Normally no parameters are required for initializing a vector, but in the case of
+ * loading a previously dumped vector the raw elements can be provided to the constructor.
+ *
+ * For performance reasons vectors are implemented with a flat array, where an elements
+ * index is immediately followed by its value. E.g. [index, value, index, value]. This
+ * allows the underlying array to be as sparse as possible and still offer decent
+ * performance when being used for vector calculations.
+ *
+ * @constructor
+ * @param {Number[]} [elements] - The flat list of element index and element value pairs.
+ */
+lunr.Vector = function (elements) {
+ this._magnitude = 0
+ this.elements = elements || []
+}
+
+
+/**
+ * Calculates the position within the vector to insert a given index.
+ *
+ * This is used internally by insert and upsert. If there are duplicate indexes then
+ * the position is returned as if the value for that index were to be updated, but it
+ * is the callers responsibility to check whether there is a duplicate at that index
+ *
+ * @param {Number} insertIdx - The index at which the element should be inserted.
+ * @returns {Number}
+ */
+lunr.Vector.prototype.positionForIndex = function (index) {
+ // For an empty vector the tuple can be inserted at the beginning
+ if (this.elements.length == 0) {
+ return 0
+ }
+
+ var start = 0,
+ end = this.elements.length / 2,
+ sliceLength = end - start,
+ pivotPoint = Math.floor(sliceLength / 2),
+ pivotIndex = this.elements[pivotPoint * 2]
+
+ while (sliceLength > 1) {
+ if (pivotIndex < index) {
+ start = pivotPoint
+ }
+
+ if (pivotIndex > index) {
+ end = pivotPoint
+ }
+
+ if (pivotIndex == index) {
+ break
+ }
+
+ sliceLength = end - start
+ pivotPoint = start + Math.floor(sliceLength / 2)
+ pivotIndex = this.elements[pivotPoint * 2]
+ }
+
+ if (pivotIndex == index) {
+ return pivotPoint * 2
+ }
+
+ if (pivotIndex > index) {
+ return pivotPoint * 2
+ }
+
+ if (pivotIndex < index) {
+ return (pivotPoint + 1) * 2
+ }
+}
+
+/**
+ * Inserts an element at an index within the vector.
+ *
+ * Does not allow duplicates, will throw an error if there is already an entry
+ * for this index.
+ *
+ * @param {Number} insertIdx - The index at which the element should be inserted.
+ * @param {Number} val - The value to be inserted into the vector.
+ */
+lunr.Vector.prototype.insert = function (insertIdx, val) {
+ this.upsert(insertIdx, val, function () {
+ throw "duplicate index"
+ })
+}
+
+/**
+ * Inserts or updates an existing index within the vector.
+ *
+ * @param {Number} insertIdx - The index at which the element should be inserted.
+ * @param {Number} val - The value to be inserted into the vector.
+ * @param {function} fn - A function that is called for updates, the existing value and the
+ * requested value are passed as arguments
+ */
+lunr.Vector.prototype.upsert = function (insertIdx, val, fn) {
+ this._magnitude = 0
+ var position = this.positionForIndex(insertIdx)
+
+ if (this.elements[position] == insertIdx) {
+ this.elements[position + 1] = fn(this.elements[position + 1], val)
+ } else {
+ this.elements.splice(position, 0, insertIdx, val)
+ }
+}
+
+/**
+ * Calculates the magnitude of this vector.
+ *
+ * @returns {Number}
+ */
+lunr.Vector.prototype.magnitude = function () {
+ if (this._magnitude) return this._magnitude
+
+ var sumOfSquares = 0,
+ elementsLength = this.elements.length
+
+ for (var i = 1; i < elementsLength; i += 2) {
+ var val = this.elements[i]
+ sumOfSquares += val * val
+ }
+
+ return this._magnitude = Math.sqrt(sumOfSquares)
+}
+
+/**
+ * Calculates the dot product of this vector and another vector.
+ *
+ * @param {lunr.Vector} otherVector - The vector to compute the dot product with.
+ * @returns {Number}
+ */
+lunr.Vector.prototype.dot = function (otherVector) {
+ var dotProduct = 0,
+ a = this.elements, b = otherVector.elements,
+ aLen = a.length, bLen = b.length,
+ aVal = 0, bVal = 0,
+ i = 0, j = 0
+
+ while (i < aLen && j < bLen) {
+ aVal = a[i], bVal = b[j]
+ if (aVal < bVal) {
+ i += 2
+ } else if (aVal > bVal) {
+ j += 2
+ } else if (aVal == bVal) {
+ dotProduct += a[i + 1] * b[j + 1]
+ i += 2
+ j += 2
+ }
+ }
+
+ return dotProduct
+}
+
+/**
+ * Calculates the similarity between this vector and another vector.
+ *
+ * @param {lunr.Vector} otherVector - The other vector to calculate the
+ * similarity with.
+ * @returns {Number}
+ */
+lunr.Vector.prototype.similarity = function (otherVector) {
+ return this.dot(otherVector) / this.magnitude() || 0
+}
+
+/**
+ * Converts the vector to an array of the elements within the vector.
+ *
+ * @returns {Number[]}
+ */
+lunr.Vector.prototype.toArray = function () {
+ var output = new Array (this.elements.length / 2)
+
+ for (var i = 1, j = 0; i < this.elements.length; i += 2, j++) {
+ output[j] = this.elements[i]
+ }
+
+ return output
+}
+
+/**
+ * A JSON serializable representation of the vector.
+ *
+ * @returns {Number[]}
+ */
+lunr.Vector.prototype.toJSON = function () {
+ return this.elements
+}
+/* eslint-disable */
+/*!
+ * lunr.stemmer
+ * Copyright (C) 2020 Oliver Nightingale
+ * Includes code from - http://tartarus.org/~martin/PorterStemmer/js.txt
+ */
+
+/**
+ * lunr.stemmer is an english language stemmer, this is a JavaScript
+ * implementation of the PorterStemmer taken from http://tartarus.org/~martin
+ *
+ * @static
+ * @implements {lunr.PipelineFunction}
+ * @param {lunr.Token} token - The string to stem
+ * @returns {lunr.Token}
+ * @see {@link lunr.Pipeline}
+ * @function
+ */
+lunr.stemmer = (function(){
+ var step2list = {
+ "ational" : "ate",
+ "tional" : "tion",
+ "enci" : "ence",
+ "anci" : "ance",
+ "izer" : "ize",
+ "bli" : "ble",
+ "alli" : "al",
+ "entli" : "ent",
+ "eli" : "e",
+ "ousli" : "ous",
+ "ization" : "ize",
+ "ation" : "ate",
+ "ator" : "ate",
+ "alism" : "al",
+ "iveness" : "ive",
+ "fulness" : "ful",
+ "ousness" : "ous",
+ "aliti" : "al",
+ "iviti" : "ive",
+ "biliti" : "ble",
+ "logi" : "log"
+ },
+
+ step3list = {
+ "icate" : "ic",
+ "ative" : "",
+ "alize" : "al",
+ "iciti" : "ic",
+ "ical" : "ic",
+ "ful" : "",
+ "ness" : ""
+ },
+
+ c = "[^aeiou]", // consonant
+ v = "[aeiouy]", // vowel
+ C = c + "[^aeiouy]*", // consonant sequence
+ V = v + "[aeiou]*", // vowel sequence
+
+ mgr0 = "^(" + C + ")?" + V + C, // [C]VC... is m>0
+ meq1 = "^(" + C + ")?" + V + C + "(" + V + ")?$", // [C]VC[V] is m=1
+ mgr1 = "^(" + C + ")?" + V + C + V + C, // [C]VCVC... is m>1
+ s_v = "^(" + C + ")?" + v; // vowel in stem
+
+ var re_mgr0 = new RegExp(mgr0);
+ var re_mgr1 = new RegExp(mgr1);
+ var re_meq1 = new RegExp(meq1);
+ var re_s_v = new RegExp(s_v);
+
+ var re_1a = /^(.+?)(ss|i)es$/;
+ var re2_1a = /^(.+?)([^s])s$/;
+ var re_1b = /^(.+?)eed$/;
+ var re2_1b = /^(.+?)(ed|ing)$/;
+ var re_1b_2 = /.$/;
+ var re2_1b_2 = /(at|bl|iz)$/;
+ var re3_1b_2 = new RegExp("([^aeiouylsz])\\1$");
+ var re4_1b_2 = new RegExp("^" + C + v + "[^aeiouwxy]$");
+
+ var re_1c = /^(.+?[^aeiou])y$/;
+ var re_2 = /^(.+?)(ational|tional|enci|anci|izer|bli|alli|entli|eli|ousli|ization|ation|ator|alism|iveness|fulness|ousness|aliti|iviti|biliti|logi)$/;
+
+ var re_3 = /^(.+?)(icate|ative|alize|iciti|ical|ful|ness)$/;
+
+ var re_4 = /^(.+?)(al|ance|ence|er|ic|able|ible|ant|ement|ment|ent|ou|ism|ate|iti|ous|ive|ize)$/;
+ var re2_4 = /^(.+?)(s|t)(ion)$/;
+
+ var re_5 = /^(.+?)e$/;
+ var re_5_1 = /ll$/;
+ var re3_5 = new RegExp("^" + C + v + "[^aeiouwxy]$");
+
+ var porterStemmer = function porterStemmer(w) {
+ var stem,
+ suffix,
+ firstch,
+ re,
+ re2,
+ re3,
+ re4;
+
+ if (w.length < 3) { return w; }
+
+ firstch = w.substr(0,1);
+ if (firstch == "y") {
+ w = firstch.toUpperCase() + w.substr(1);
+ }
+
+ // Step 1a
+ re = re_1a
+ re2 = re2_1a;
+
+ if (re.test(w)) { w = w.replace(re,"$1$2"); }
+ else if (re2.test(w)) { w = w.replace(re2,"$1$2"); }
+
+ // Step 1b
+ re = re_1b;
+ re2 = re2_1b;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ re = re_mgr0;
+ if (re.test(fp[1])) {
+ re = re_1b_2;
+ w = w.replace(re,"");
+ }
+ } else if (re2.test(w)) {
+ var fp = re2.exec(w);
+ stem = fp[1];
+ re2 = re_s_v;
+ if (re2.test(stem)) {
+ w = stem;
+ re2 = re2_1b_2;
+ re3 = re3_1b_2;
+ re4 = re4_1b_2;
+ if (re2.test(w)) { w = w + "e"; }
+ else if (re3.test(w)) { re = re_1b_2; w = w.replace(re,""); }
+ else if (re4.test(w)) { w = w + "e"; }
+ }
+ }
+
+ // Step 1c - replace suffix y or Y by i if preceded by a non-vowel which is not the first letter of the word (so cry -> cri, by -> by, say -> say)
+ re = re_1c;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ w = stem + "i";
+ }
+
+ // Step 2
+ re = re_2;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ suffix = fp[2];
+ re = re_mgr0;
+ if (re.test(stem)) {
+ w = stem + step2list[suffix];
+ }
+ }
+
+ // Step 3
+ re = re_3;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ suffix = fp[2];
+ re = re_mgr0;
+ if (re.test(stem)) {
+ w = stem + step3list[suffix];
+ }
+ }
+
+ // Step 4
+ re = re_4;
+ re2 = re2_4;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ re = re_mgr1;
+ if (re.test(stem)) {
+ w = stem;
+ }
+ } else if (re2.test(w)) {
+ var fp = re2.exec(w);
+ stem = fp[1] + fp[2];
+ re2 = re_mgr1;
+ if (re2.test(stem)) {
+ w = stem;
+ }
+ }
+
+ // Step 5
+ re = re_5;
+ if (re.test(w)) {
+ var fp = re.exec(w);
+ stem = fp[1];
+ re = re_mgr1;
+ re2 = re_meq1;
+ re3 = re3_5;
+ if (re.test(stem) || (re2.test(stem) && !(re3.test(stem)))) {
+ w = stem;
+ }
+ }
+
+ re = re_5_1;
+ re2 = re_mgr1;
+ if (re.test(w) && re2.test(w)) {
+ re = re_1b_2;
+ w = w.replace(re,"");
+ }
+
+ // and turn initial Y back to y
+
+ if (firstch == "y") {
+ w = firstch.toLowerCase() + w.substr(1);
+ }
+
+ return w;
+ };
+
+ return function (token) {
+ return token.update(porterStemmer);
+ }
+})();
+
+lunr.Pipeline.registerFunction(lunr.stemmer, 'stemmer')
+/*!
+ * lunr.stopWordFilter
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * lunr.generateStopWordFilter builds a stopWordFilter function from the provided
+ * list of stop words.
+ *
+ * The built in lunr.stopWordFilter is built using this generator and can be used
+ * to generate custom stopWordFilters for applications or non English languages.
+ *
+ * @function
+ * @param {Array} token The token to pass through the filter
+ * @returns {lunr.PipelineFunction}
+ * @see lunr.Pipeline
+ * @see lunr.stopWordFilter
+ */
+lunr.generateStopWordFilter = function (stopWords) {
+ var words = stopWords.reduce(function (memo, stopWord) {
+ memo[stopWord] = stopWord
+ return memo
+ }, {})
+
+ return function (token) {
+ if (token && words[token.toString()] !== token.toString()) return token
+ }
+}
+
+/**
+ * lunr.stopWordFilter is an English language stop word list filter, any words
+ * contained in the list will not be passed through the filter.
+ *
+ * This is intended to be used in the Pipeline. If the token does not pass the
+ * filter then undefined will be returned.
+ *
+ * @function
+ * @implements {lunr.PipelineFunction}
+ * @params {lunr.Token} token - A token to check for being a stop word.
+ * @returns {lunr.Token}
+ * @see {@link lunr.Pipeline}
+ */
+lunr.stopWordFilter = lunr.generateStopWordFilter([
+ 'a',
+ 'able',
+ 'about',
+ 'across',
+ 'after',
+ 'all',
+ 'almost',
+ 'also',
+ 'am',
+ 'among',
+ 'an',
+ 'and',
+ 'any',
+ 'are',
+ 'as',
+ 'at',
+ 'be',
+ 'because',
+ 'been',
+ 'but',
+ 'by',
+ 'can',
+ 'cannot',
+ 'could',
+ 'dear',
+ 'did',
+ 'do',
+ 'does',
+ 'either',
+ 'else',
+ 'ever',
+ 'every',
+ 'for',
+ 'from',
+ 'get',
+ 'got',
+ 'had',
+ 'has',
+ 'have',
+ 'he',
+ 'her',
+ 'hers',
+ 'him',
+ 'his',
+ 'how',
+ 'however',
+ 'i',
+ 'if',
+ 'in',
+ 'into',
+ 'is',
+ 'it',
+ 'its',
+ 'just',
+ 'least',
+ 'let',
+ 'like',
+ 'likely',
+ 'may',
+ 'me',
+ 'might',
+ 'most',
+ 'must',
+ 'my',
+ 'neither',
+ 'no',
+ 'nor',
+ 'not',
+ 'of',
+ 'off',
+ 'often',
+ 'on',
+ 'only',
+ 'or',
+ 'other',
+ 'our',
+ 'own',
+ 'rather',
+ 'said',
+ 'say',
+ 'says',
+ 'she',
+ 'should',
+ 'since',
+ 'so',
+ 'some',
+ 'than',
+ 'that',
+ 'the',
+ 'their',
+ 'them',
+ 'then',
+ 'there',
+ 'these',
+ 'they',
+ 'this',
+ 'tis',
+ 'to',
+ 'too',
+ 'twas',
+ 'us',
+ 'wants',
+ 'was',
+ 'we',
+ 'were',
+ 'what',
+ 'when',
+ 'where',
+ 'which',
+ 'while',
+ 'who',
+ 'whom',
+ 'why',
+ 'will',
+ 'with',
+ 'would',
+ 'yet',
+ 'you',
+ 'your'
+])
+
+lunr.Pipeline.registerFunction(lunr.stopWordFilter, 'stopWordFilter')
+/*!
+ * lunr.trimmer
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * lunr.trimmer is a pipeline function for trimming non word
+ * characters from the beginning and end of tokens before they
+ * enter the index.
+ *
+ * This implementation may not work correctly for non latin
+ * characters and should either be removed or adapted for use
+ * with languages with non-latin characters.
+ *
+ * @static
+ * @implements {lunr.PipelineFunction}
+ * @param {lunr.Token} token The token to pass through the filter
+ * @returns {lunr.Token}
+ * @see lunr.Pipeline
+ */
+lunr.trimmer = function (token) {
+ return token.update(function (s) {
+ return s.replace(/^\W+/, '').replace(/\W+$/, '')
+ })
+}
+
+lunr.Pipeline.registerFunction(lunr.trimmer, 'trimmer')
+/*!
+ * lunr.TokenSet
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * A token set is used to store the unique list of all tokens
+ * within an index. Token sets are also used to represent an
+ * incoming query to the index, this query token set and index
+ * token set are then intersected to find which tokens to look
+ * up in the inverted index.
+ *
+ * A token set can hold multiple tokens, as in the case of the
+ * index token set, or it can hold a single token as in the
+ * case of a simple query token set.
+ *
+ * Additionally token sets are used to perform wildcard matching.
+ * Leading, contained and trailing wildcards are supported, and
+ * from this edit distance matching can also be provided.
+ *
+ * Token sets are implemented as a minimal finite state automata,
+ * where both common prefixes and suffixes are shared between tokens.
+ * This helps to reduce the space used for storing the token set.
+ *
+ * @constructor
+ */
+lunr.TokenSet = function () {
+ this.final = false
+ this.edges = {}
+ this.id = lunr.TokenSet._nextId
+ lunr.TokenSet._nextId += 1
+}
+
+/**
+ * Keeps track of the next, auto increment, identifier to assign
+ * to a new tokenSet.
+ *
+ * TokenSets require a unique identifier to be correctly minimised.
+ *
+ * @private
+ */
+lunr.TokenSet._nextId = 1
+
+/**
+ * Creates a TokenSet instance from the given sorted array of words.
+ *
+ * @param {String[]} arr - A sorted array of strings to create the set from.
+ * @returns {lunr.TokenSet}
+ * @throws Will throw an error if the input array is not sorted.
+ */
+lunr.TokenSet.fromArray = function (arr) {
+ var builder = new lunr.TokenSet.Builder
+
+ for (var i = 0, len = arr.length; i < len; i++) {
+ builder.insert(arr[i])
+ }
+
+ builder.finish()
+ return builder.root
+}
+
+/**
+ * Creates a token set from a query clause.
+ *
+ * @private
+ * @param {Object} clause - A single clause from lunr.Query.
+ * @param {string} clause.term - The query clause term.
+ * @param {number} [clause.editDistance] - The optional edit distance for the term.
+ * @returns {lunr.TokenSet}
+ */
+lunr.TokenSet.fromClause = function (clause) {
+ if ('editDistance' in clause) {
+ return lunr.TokenSet.fromFuzzyString(clause.term, clause.editDistance)
+ } else {
+ return lunr.TokenSet.fromString(clause.term)
+ }
+}
+
+/**
+ * Creates a token set representing a single string with a specified
+ * edit distance.
+ *
+ * Insertions, deletions, substitutions and transpositions are each
+ * treated as an edit distance of 1.
+ *
+ * Increasing the allowed edit distance will have a dramatic impact
+ * on the performance of both creating and intersecting these TokenSets.
+ * It is advised to keep the edit distance less than 3.
+ *
+ * @param {string} str - The string to create the token set from.
+ * @param {number} editDistance - The allowed edit distance to match.
+ * @returns {lunr.Vector}
+ */
+lunr.TokenSet.fromFuzzyString = function (str, editDistance) {
+ var root = new lunr.TokenSet
+
+ var stack = [{
+ node: root,
+ editsRemaining: editDistance,
+ str: str
+ }]
+
+ while (stack.length) {
+ var frame = stack.pop()
+
+ // no edit
+ if (frame.str.length > 0) {
+ var char = frame.str.charAt(0),
+ noEditNode
+
+ if (char in frame.node.edges) {
+ noEditNode = frame.node.edges[char]
+ } else {
+ noEditNode = new lunr.TokenSet
+ frame.node.edges[char] = noEditNode
+ }
+
+ if (frame.str.length == 1) {
+ noEditNode.final = true
+ }
+
+ stack.push({
+ node: noEditNode,
+ editsRemaining: frame.editsRemaining,
+ str: frame.str.slice(1)
+ })
+ }
+
+ if (frame.editsRemaining == 0) {
+ continue
+ }
+
+ // insertion
+ if ("*" in frame.node.edges) {
+ var insertionNode = frame.node.edges["*"]
+ } else {
+ var insertionNode = new lunr.TokenSet
+ frame.node.edges["*"] = insertionNode
+ }
+
+ if (frame.str.length == 0) {
+ insertionNode.final = true
+ }
+
+ stack.push({
+ node: insertionNode,
+ editsRemaining: frame.editsRemaining - 1,
+ str: frame.str
+ })
+
+ // deletion
+ // can only do a deletion if we have enough edits remaining
+ // and if there are characters left to delete in the string
+ if (frame.str.length > 1) {
+ stack.push({
+ node: frame.node,
+ editsRemaining: frame.editsRemaining - 1,
+ str: frame.str.slice(1)
+ })
+ }
+
+ // deletion
+ // just removing the last character from the str
+ if (frame.str.length == 1) {
+ frame.node.final = true
+ }
+
+ // substitution
+ // can only do a substitution if we have enough edits remaining
+ // and if there are characters left to substitute
+ if (frame.str.length >= 1) {
+ if ("*" in frame.node.edges) {
+ var substitutionNode = frame.node.edges["*"]
+ } else {
+ var substitutionNode = new lunr.TokenSet
+ frame.node.edges["*"] = substitutionNode
+ }
+
+ if (frame.str.length == 1) {
+ substitutionNode.final = true
+ }
+
+ stack.push({
+ node: substitutionNode,
+ editsRemaining: frame.editsRemaining - 1,
+ str: frame.str.slice(1)
+ })
+ }
+
+ // transposition
+ // can only do a transposition if there are edits remaining
+ // and there are enough characters to transpose
+ if (frame.str.length > 1) {
+ var charA = frame.str.charAt(0),
+ charB = frame.str.charAt(1),
+ transposeNode
+
+ if (charB in frame.node.edges) {
+ transposeNode = frame.node.edges[charB]
+ } else {
+ transposeNode = new lunr.TokenSet
+ frame.node.edges[charB] = transposeNode
+ }
+
+ if (frame.str.length == 1) {
+ transposeNode.final = true
+ }
+
+ stack.push({
+ node: transposeNode,
+ editsRemaining: frame.editsRemaining - 1,
+ str: charA + frame.str.slice(2)
+ })
+ }
+ }
+
+ return root
+}
+
+/**
+ * Creates a TokenSet from a string.
+ *
+ * The string may contain one or more wildcard characters (*)
+ * that will allow wildcard matching when intersecting with
+ * another TokenSet.
+ *
+ * @param {string} str - The string to create a TokenSet from.
+ * @returns {lunr.TokenSet}
+ */
+lunr.TokenSet.fromString = function (str) {
+ var node = new lunr.TokenSet,
+ root = node
+
+ /*
+ * Iterates through all characters within the passed string
+ * appending a node for each character.
+ *
+ * When a wildcard character is found then a self
+ * referencing edge is introduced to continually match
+ * any number of any characters.
+ */
+ for (var i = 0, len = str.length; i < len; i++) {
+ var char = str[i],
+ final = (i == len - 1)
+
+ if (char == "*") {
+ node.edges[char] = node
+ node.final = final
+
+ } else {
+ var next = new lunr.TokenSet
+ next.final = final
+
+ node.edges[char] = next
+ node = next
+ }
+ }
+
+ return root
+}
+
+/**
+ * Converts this TokenSet into an array of strings
+ * contained within the TokenSet.
+ *
+ * This is not intended to be used on a TokenSet that
+ * contains wildcards, in these cases the results are
+ * undefined and are likely to cause an infinite loop.
+ *
+ * @returns {string[]}
+ */
+lunr.TokenSet.prototype.toArray = function () {
+ var words = []
+
+ var stack = [{
+ prefix: "",
+ node: this
+ }]
+
+ while (stack.length) {
+ var frame = stack.pop(),
+ edges = Object.keys(frame.node.edges),
+ len = edges.length
+
+ if (frame.node.final) {
+ /* In Safari, at this point the prefix is sometimes corrupted, see:
+ * https://github.com/olivernn/lunr.js/issues/279 Calling any
+ * String.prototype method forces Safari to "cast" this string to what
+ * it's supposed to be, fixing the bug. */
+ frame.prefix.charAt(0)
+ words.push(frame.prefix)
+ }
+
+ for (var i = 0; i < len; i++) {
+ var edge = edges[i]
+
+ stack.push({
+ prefix: frame.prefix.concat(edge),
+ node: frame.node.edges[edge]
+ })
+ }
+ }
+
+ return words
+}
+
+/**
+ * Generates a string representation of a TokenSet.
+ *
+ * This is intended to allow TokenSets to be used as keys
+ * in objects, largely to aid the construction and minimisation
+ * of a TokenSet. As such it is not designed to be a human
+ * friendly representation of the TokenSet.
+ *
+ * @returns {string}
+ */
+lunr.TokenSet.prototype.toString = function () {
+ // NOTE: Using Object.keys here as this.edges is very likely
+ // to enter 'hash-mode' with many keys being added
+ //
+ // avoiding a for-in loop here as it leads to the function
+ // being de-optimised (at least in V8). From some simple
+ // benchmarks the performance is comparable, but allowing
+ // V8 to optimize may mean easy performance wins in the future.
+
+ if (this._str) {
+ return this._str
+ }
+
+ var str = this.final ? '1' : '0',
+ labels = Object.keys(this.edges).sort(),
+ len = labels.length
+
+ for (var i = 0; i < len; i++) {
+ var label = labels[i],
+ node = this.edges[label]
+
+ str = str + label + node.id
+ }
+
+ return str
+}
+
+/**
+ * Returns a new TokenSet that is the intersection of
+ * this TokenSet and the passed TokenSet.
+ *
+ * This intersection will take into account any wildcards
+ * contained within the TokenSet.
+ *
+ * @param {lunr.TokenSet} b - An other TokenSet to intersect with.
+ * @returns {lunr.TokenSet}
+ */
+lunr.TokenSet.prototype.intersect = function (b) {
+ var output = new lunr.TokenSet,
+ frame = undefined
+
+ var stack = [{
+ qNode: b,
+ output: output,
+ node: this
+ }]
+
+ while (stack.length) {
+ frame = stack.pop()
+
+ // NOTE: As with the #toString method, we are using
+ // Object.keys and a for loop instead of a for-in loop
+ // as both of these objects enter 'hash' mode, causing
+ // the function to be de-optimised in V8
+ var qEdges = Object.keys(frame.qNode.edges),
+ qLen = qEdges.length,
+ nEdges = Object.keys(frame.node.edges),
+ nLen = nEdges.length
+
+ for (var q = 0; q < qLen; q++) {
+ var qEdge = qEdges[q]
+
+ for (var n = 0; n < nLen; n++) {
+ var nEdge = nEdges[n]
+
+ if (nEdge == qEdge || qEdge == '*') {
+ var node = frame.node.edges[nEdge],
+ qNode = frame.qNode.edges[qEdge],
+ final = node.final && qNode.final,
+ next = undefined
+
+ if (nEdge in frame.output.edges) {
+ // an edge already exists for this character
+ // no need to create a new node, just set the finality
+ // bit unless this node is already final
+ next = frame.output.edges[nEdge]
+ next.final = next.final || final
+
+ } else {
+ // no edge exists yet, must create one
+ // set the finality bit and insert it
+ // into the output
+ next = new lunr.TokenSet
+ next.final = final
+ frame.output.edges[nEdge] = next
+ }
+
+ stack.push({
+ qNode: qNode,
+ output: next,
+ node: node
+ })
+ }
+ }
+ }
+ }
+
+ return output
+}
+lunr.TokenSet.Builder = function () {
+ this.previousWord = ""
+ this.root = new lunr.TokenSet
+ this.uncheckedNodes = []
+ this.minimizedNodes = {}
+}
+
+lunr.TokenSet.Builder.prototype.insert = function (word) {
+ var node,
+ commonPrefix = 0
+
+ if (word < this.previousWord) {
+ throw new Error ("Out of order word insertion")
+ }
+
+ for (var i = 0; i < word.length && i < this.previousWord.length; i++) {
+ if (word[i] != this.previousWord[i]) break
+ commonPrefix++
+ }
+
+ this.minimize(commonPrefix)
+
+ if (this.uncheckedNodes.length == 0) {
+ node = this.root
+ } else {
+ node = this.uncheckedNodes[this.uncheckedNodes.length - 1].child
+ }
+
+ for (var i = commonPrefix; i < word.length; i++) {
+ var nextNode = new lunr.TokenSet,
+ char = word[i]
+
+ node.edges[char] = nextNode
+
+ this.uncheckedNodes.push({
+ parent: node,
+ char: char,
+ child: nextNode
+ })
+
+ node = nextNode
+ }
+
+ node.final = true
+ this.previousWord = word
+}
+
+lunr.TokenSet.Builder.prototype.finish = function () {
+ this.minimize(0)
+}
+
+lunr.TokenSet.Builder.prototype.minimize = function (downTo) {
+ for (var i = this.uncheckedNodes.length - 1; i >= downTo; i--) {
+ var node = this.uncheckedNodes[i],
+ childKey = node.child.toString()
+
+ if (childKey in this.minimizedNodes) {
+ node.parent.edges[node.char] = this.minimizedNodes[childKey]
+ } else {
+ // Cache the key for this node since
+ // we know it can't change anymore
+ node.child._str = childKey
+
+ this.minimizedNodes[childKey] = node.child
+ }
+
+ this.uncheckedNodes.pop()
+ }
+}
+/*!
+ * lunr.Index
+ * Copyright (C) 2020 Oliver Nightingale
+ */
+
+/**
+ * An index contains the built index of all documents and provides a query interface
+ * to the index.
+ *
+ * Usually instances of lunr.Index will not be created using this constructor, instead
+ * lunr.Builder should be used to construct new indexes, or lunr.Index.load should be
+ * used to load previously built and serialized indexes.
+ *
+ * @constructor
+ * @param {Object} attrs - The attributes of the built search index.
+ * @param {Object} attrs.invertedIndex - An index of term/field to document reference.
+ * @param {Object' + noResultsText + '
'); + } +} + +function doSearch () { + var query = document.getElementById('mkdocs-search-query').value; + if (query.length > min_search_length) { + if (!window.Worker) { + displayResults(search(query)); + } else { + searchWorker.postMessage({query: query}); + } + } else { + // Clear results for short queries + displayResults([]); + } +} + +function initSearch () { + var search_input = document.getElementById('mkdocs-search-query'); + if (search_input) { + search_input.addEventListener("keyup", doSearch); + } + var term = getSearchTermFromLocation(); + if (term) { + search_input.value = term; + doSearch(); + } +} + +function onWorkerMessage (e) { + if (e.data.allowSearch) { + initSearch(); + } else if (e.data.results) { + var results = e.data.results; + displayResults(results); + } else if (e.data.config) { + min_search_length = e.data.config.min_search_length-1; + } +} + +if (!window.Worker) { + console.log('Web Worker API not supported'); + // load index in main thread + $.getScript(joinUrl(base_url, "search/worker.js")).done(function () { + console.log('Loaded worker'); + init(); + window.postMessage = function (msg) { + onWorkerMessage({data: msg}); + }; + }).fail(function (jqxhr, settings, exception) { + console.error('Could not load worker.js'); + }); +} else { + // Wrap search in a web worker + var searchWorker = new Worker(joinUrl(base_url, "search/worker.js")); + searchWorker.postMessage({init: true}); + searchWorker.onmessage = onWorkerMessage; +} diff --git a/search/search_index.json b/search/search_index.json new file mode 100644 index 00000000..329c0c7a --- /dev/null +++ b/search/search_index.json @@ -0,0 +1 @@ +{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Metadata Handbook Big Ten Academic Alliance Geoportal This guide was prepared with the objective of assisting Team Members in the Big Ten Academic Alliance Geospatial Information Network on the BTAA Geoportal's metadata schema, content organization model, and workflows. Quicklinks All OpenGeoMetadata schema elements BTAA custom elements B1G metadata templates Version History Changes for Version 4.2 (March 24, 2022) - New Entry and Usage Guidelines page - Expands content organization model documentation - Changes the name of the schema from 'Aardvark' to 'OpenGeoMetadata (version Aardvark)' - Cleans up outdated links Changes for Version 4.1 (Jan 2022) - updates Status as optional; removes controlled vocabulary - Clarifies relationship model Changes for Version 4.0 (July 2021) - Incorporation of GEOMG Metadata Editor - Upgrade to Aardvark Metadata Schema for GeoBlacklight Changes for version 3.3 (May 13, 2020) - Added University of Nebraska - Reorganized Metadata Elements to match editing template - Updated the \u201cUpdate the Collections\u201d section to match new administrative process for tracking records Changes for version 3.2 (Jan 8, 2020) - Added Date Range element Changes for version 3.1 (Dec 19, 2019) - Added collection level records metadata schema Changes for version 3 (Oct, 2019) - GeoNetwork and Omeka deprecated - all GeoBlacklight records are stored in a master spreadsheet in Google - Sheets - records are transformed from CSV to GeoBlacklight JSON with a Python script - additional metadata fields were added for administrative purposes - IsPartOf field now holds a code pointing to the collection record - Administrative groupings such as \u201cState agencies geospatial data\u201d are now subjects, not a Collection - updated editing templates available - all supplemental metadata can be stored as XML or HTML in project hosted folder - updated links to collections database Credits Handbook prepared by: - Karen Majewicz, Project Metadata Coordinator - Ziying (Gene) Cheng - Graduate Research Assistant","title":"Home"},{"location":"#metadata-handbook","text":"Big Ten Academic Alliance Geoportal This guide was prepared with the objective of assisting Team Members in the Big Ten Academic Alliance Geospatial Information Network on the BTAA Geoportal's metadata schema, content organization model, and workflows.","title":"Metadata Handbook"},{"location":"#quicklinks","text":"All OpenGeoMetadata schema elements BTAA custom elements B1G metadata templates","title":"Quicklinks"},{"location":"#version-history","text":"Changes for Version 4.2 (March 24, 2022) - New Entry and Usage Guidelines page - Expands content organization model documentation - Changes the name of the schema from 'Aardvark' to 'OpenGeoMetadata (version Aardvark)' - Cleans up outdated links Changes for Version 4.1 (Jan 2022) - updates Status as optional; removes controlled vocabulary - Clarifies relationship model Changes for Version 4.0 (July 2021) - Incorporation of GEOMG Metadata Editor - Upgrade to Aardvark Metadata Schema for GeoBlacklight Changes for version 3.3 (May 13, 2020) - Added University of Nebraska - Reorganized Metadata Elements to match editing template - Updated the \u201cUpdate the Collections\u201d section to match new administrative process for tracking records Changes for version 3.2 (Jan 8, 2020) - Added Date Range element Changes for version 3.1 (Dec 19, 2019) - Added collection level records metadata schema Changes for version 3 (Oct, 2019) - GeoNetwork and Omeka deprecated - all GeoBlacklight records are stored in a master spreadsheet in Google - Sheets - records are transformed from CSV to GeoBlacklight JSON with a Python script - additional metadata fields were added for administrative purposes - IsPartOf field now holds a code pointing to the collection record - Administrative groupings such as \u201cState agencies geospatial data\u201d are now subjects, not a Collection - updated editing templates available - all supplemental metadata can be stored as XML or HTML in project hosted folder - updated links to collections database Credits Handbook prepared by: - Karen Majewicz, Project Metadata Coordinator - Ziying (Gene) Cheng - Graduate Research Assistant","title":"Version History"},{"location":"GEOMG/","text":"1. Save edited template as a CSV file Use the B1G Template 2. Upload the spreadsheet to GEOMG This is done via the batch imports function. When logged into GEOMG, go to Admin Tools and select Imports. Click \"New Import\". Give a name to the upload and enter details about the source and description. These details are helpful later in tracking imports. Select the CSV file for upload For Type, choose the BTAA CSV. Click the Create Import button Review the Field Mappings page. If the CSV was formatted with column headers spelled the same way as the template, the fields should automatically map to the correct elements. Otherwise, manually choose the crosswalk mapping. Scroll to the bottom and click the button Create Mapping On the Import page, check that the number in the CSV Row Count matches your CSV. Click the button Run Import The import may take a few minutes. During the process, you can view the Import Results tab. Items in the queue will show up in the first sub-tab (\"Failed\"), but will transfer to the second tab upon import (\"Success\"). When complete, review any items that did not import in the Failed tab. See Troubleshooting ( coming soon ) for help. 3. Spot check records for errors and consistency The newly uploaded records will be listed as Draft under the Publication State on the main dashboard Select 'Draft' under Publication State and select an item. This will open it in editing view. Click the button View in Geoportal Inspect the record and test the links. (note: Metadata and Web Service links will not open while the item is still in Draft) Repeat this process for about 3 records. 4. Convert records from 'Draft' to 'Published' If the records are satisfactory, return to the Dashboard view and select all Draft items in the upload. Select All and then select the text \"Select all results that match this search\" Click the State button. From the dropdown, select Published. On the Bulk Action page, click the button Run Bulk Action Review 3-5 of the published records and test all the links. 5. Publish to OpenGeoMetadata Completed records are synced to the workflow GitHub online repository as needed. Records that are deemed stable and complete can be shared with the OpenGeoMetadata community .","title":"GEOMG"},{"location":"GEOMG/#1-save-edited-template-as-a-csv-file","text":"Use the B1G Template","title":"1. Save edited template as a CSV file"},{"location":"GEOMG/#2-upload-the-spreadsheet-to-geomg","text":"This is done via the batch imports function. When logged into GEOMG, go to Admin Tools and select Imports. Click \"New Import\". Give a name to the upload and enter details about the source and description. These details are helpful later in tracking imports. Select the CSV file for upload For Type, choose the BTAA CSV. Click the Create Import button Review the Field Mappings page. If the CSV was formatted with column headers spelled the same way as the template, the fields should automatically map to the correct elements. Otherwise, manually choose the crosswalk mapping. Scroll to the bottom and click the button Create Mapping On the Import page, check that the number in the CSV Row Count matches your CSV. Click the button Run Import The import may take a few minutes. During the process, you can view the Import Results tab. Items in the queue will show up in the first sub-tab (\"Failed\"), but will transfer to the second tab upon import (\"Success\"). When complete, review any items that did not import in the Failed tab. See Troubleshooting ( coming soon ) for help.","title":"2. Upload the spreadsheet to GEOMG"},{"location":"GEOMG/#3-spot-check-records-for-errors-and-consistency","text":"The newly uploaded records will be listed as Draft under the Publication State on the main dashboard Select 'Draft' under Publication State and select an item. This will open it in editing view. Click the button View in Geoportal Inspect the record and test the links. (note: Metadata and Web Service links will not open while the item is still in Draft) Repeat this process for about 3 records.","title":"3. Spot check records for errors and consistency"},{"location":"GEOMG/#4-convert-records-from-draft-to-published","text":"If the records are satisfactory, return to the Dashboard view and select all Draft items in the upload. Select All and then select the text \"Select all results that match this search\" Click the State button. From the dropdown, select Published. On the Bulk Action page, click the button Run Bulk Action Review 3-5 of the published records and test all the links.","title":"4. Convert records from 'Draft' to 'Published'"},{"location":"GEOMG/#5-publish-to-opengeometadata","text":"Completed records are synced to the workflow GitHub online repository as needed. Records that are deemed stable and complete can be shared with the OpenGeoMetadata community .","title":"5. Publish to OpenGeoMetadata"},{"location":"about/","text":"Overview The OpenGeoMetadata Schema The primary metadata record for each resource uses the official GeoBlacklight schema, known as OpenGeoMetadata. The current version of OpenGeoMetadata is called 'Aardvark'. This lightweight schema was designed specifically for the GeoBlacklight application and is geared towards discoverability. The schema is documented on the OpenGeoMetadata website . B1G Project Specific Features The B1G profile of the GeoBlacklight Schema adds ten custom elements to OpenGeoMetadata The B1G custom elements are documented here Editing Template The B1G Metadata Template contains the following tabs: - Map Template - Dataset Template - Website Record Template - Values: All of the controlled vocabulary values for the various fields. Supplemental Metadata All other forms of metadata, such as ISO 19139, FGDC Content Standard for Digital Geospatial Metadata, attribute table definitions, or custom schemas are treated as Supplemental Metadata . - Supplemental Metadata is not usually edited directly for inclusion in the project. - If this metadata is available as XML or HTML, it can be added as a hosted link for the Metadata preview tool in GeoBlacklight. - XML or HTML files can be parsed to extract metadata that forms the basis for the item\u2019s GeoBlacklight schema record. - The file formats that can be viewed within the geoportal application include: - ISO 19139 XML - FGDC XML - MODS XML - HTML (any standard)","title":"Metadata for the BTAA Geoportal"},{"location":"about/#overview","text":"","title":"Overview"},{"location":"about/#the-opengeometadata-schema","text":"The primary metadata record for each resource uses the official GeoBlacklight schema, known as OpenGeoMetadata. The current version of OpenGeoMetadata is called 'Aardvark'. This lightweight schema was designed specifically for the GeoBlacklight application and is geared towards discoverability. The schema is documented on the OpenGeoMetadata website .","title":"The OpenGeoMetadata Schema"},{"location":"about/#b1g-project-specific-features","text":"The B1G profile of the GeoBlacklight Schema adds ten custom elements to OpenGeoMetadata The B1G custom elements are documented here","title":"B1G Project Specific Features"},{"location":"about/#editing-template","text":"The B1G Metadata Template contains the following tabs: - Map Template - Dataset Template - Website Record Template - Values: All of the controlled vocabulary values for the various fields.","title":"Editing Template"},{"location":"about/#supplemental-metadata","text":"All other forms of metadata, such as ISO 19139, FGDC Content Standard for Digital Geospatial Metadata, attribute table definitions, or custom schemas are treated as Supplemental Metadata . - Supplemental Metadata is not usually edited directly for inclusion in the project. - If this metadata is available as XML or HTML, it can be added as a hosted link for the Metadata preview tool in GeoBlacklight. - XML or HTML files can be parsed to extract metadata that forms the basis for the item\u2019s GeoBlacklight schema record. - The file formats that can be viewed within the geoportal application include: - ISO 19139 XML - FGDC XML - MODS XML - HTML (any standard)","title":"Supplemental Metadata"},{"location":"b1g-custom-elements/","text":"Custom Elements This is an overview of the custom metadata elements for the B1G Profile. These elements extend the official OpenGeoMetadata (Aardvark) schema b1g-id Label URI Obligation b1g-01 Code b1g_code_s Required b1g-02 Status b1g_status_s Optional b1g-03 Accrual Method b1g_dct_accrualMethod_s Required b1g-04 Accrual Periodicity b1g_dct_accrualPeriodicity_s Optional b1g-05 Date Accessioned b1g_dateAccessioned_s Required b1g-06 Date Retired b1g_dateRetired_s Conditional b1g-07 Child Record b1g_child_record_b Conditional b1g-08 Mediator b1g_dct_mediator_sm Conditional b1g-09 Access b1g_access_s Conditional b1g-10 Image b1g_image_ss Optional 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. 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 Mediator 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 Label Access URI b1g_access_s Profile ID b1g-09 Obligation Conditional Multiplicity 0-0 or 1-1 Field type string JSON Purpose To supply the links for restricted records Entry Guidelines The field value is an array of key/value pairs, with keys representing an insitution code and values the URL for the library catalog record. See the Access Template for entry. Commentary This field is challenging to construct manually, is it is a JSON string of institutional codes and URLs. The codes are used instead of the actual names in order to make the length of the field more manageable and to avoid spaces. Controlled Vocabulary no Example value {\\\"03\\\":\\\"https://purl.lib.uiowa.edu/PolicyMap\\\",\\\"04\\\":\\\"https://www.lib.umd.edu/dbfinder/id/UMD09180\\\",\\\"05\\\":\\\"https://primo.lib.umn.edu/permalink/f/1q7ssba/UMN_ALMA51581932400001701\\\",\\\"06\\\":\\\"http://catalog.lib.msu.edu/record=b10238077~S39a\\\",\\\"07\\\":\\\"https://search.lib.umich.edu/databases/record/39117\\\",\\\"09\\\":\\\"https://libraries.psu.edu/databases/psu01762\\\",\\\"10\\\":\\\"https://digital.library.wisc.edu/1711.web/policymap\\\",\\\"11\\\":\\\"https://library.ohio-state.edu/record=b7869979~S7\\\"} Element Set B1G 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","title":"Custom Elements"},{"location":"b1g-custom-elements/#custom-elements","text":"This is an overview of the custom metadata elements for the B1G Profile. These elements extend the official OpenGeoMetadata (Aardvark) schema b1g-id Label URI Obligation b1g-01 Code b1g_code_s Required b1g-02 Status b1g_status_s Optional b1g-03 Accrual Method b1g_dct_accrualMethod_s Required b1g-04 Accrual Periodicity b1g_dct_accrualPeriodicity_s Optional b1g-05 Date Accessioned b1g_dateAccessioned_s Required b1g-06 Date Retired b1g_dateRetired_s Conditional b1g-07 Child Record b1g_child_record_b Conditional b1g-08 Mediator b1g_dct_mediator_sm Conditional b1g-09 Access b1g_access_s Conditional b1g-10 Image b1g_image_ss Optional","title":"Custom Elements"},{"location":"b1g-custom-elements/#code","text":"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. 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","title":"Code"},{"location":"b1g-custom-elements/#status","text":"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","title":"Status"},{"location":"b1g-custom-elements/#accrual-method","text":"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","title":"Accrual Method"},{"location":"b1g-custom-elements/#accrual-periodicity","text":"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","title":"Accrual Periodicity"},{"location":"b1g-custom-elements/#date-accessioned","text":"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","title":"Date Accessioned"},{"location":"b1g-custom-elements/#date-retired","text":"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","title":"Date Retired"},{"location":"b1g-custom-elements/#child-record","text":"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","title":"Child Record"},{"location":"b1g-custom-elements/#mediator","text":"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","title":"Mediator"},{"location":"b1g-custom-elements/#access","text":"Label Access URI b1g_access_s Profile ID b1g-09 Obligation Conditional Multiplicity 0-0 or 1-1 Field type string JSON Purpose To supply the links for restricted records Entry Guidelines The field value is an array of key/value pairs, with keys representing an insitution code and values the URL for the library catalog record. See the Access Template for entry. Commentary This field is challenging to construct manually, is it is a JSON string of institutional codes and URLs. The codes are used instead of the actual names in order to make the length of the field more manageable and to avoid spaces. Controlled Vocabulary no Example value {\\\"03\\\":\\\"https://purl.lib.uiowa.edu/PolicyMap\\\",\\\"04\\\":\\\"https://www.lib.umd.edu/dbfinder/id/UMD09180\\\",\\\"05\\\":\\\"https://primo.lib.umn.edu/permalink/f/1q7ssba/UMN_ALMA51581932400001701\\\",\\\"06\\\":\\\"http://catalog.lib.msu.edu/record=b10238077~S39a\\\",\\\"07\\\":\\\"https://search.lib.umich.edu/databases/record/39117\\\",\\\"09\\\":\\\"https://libraries.psu.edu/databases/psu01762\\\",\\\"10\\\":\\\"https://digital.library.wisc.edu/1711.web/policymap\\\",\\\"11\\\":\\\"https://library.ohio-state.edu/record=b7869979~S7\\\"} Element Set B1G","title":"Access"},{"location":"b1g-custom-elements/#image","text":"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","title":"Image"},{"location":"entry-usage-guidelines/","text":"BTAA Specific Entry Guidelines The BTAA Geoportal has more specific guidelines for some fields from OpenGeoMetadata (OGM). Title Maps : The title for scanned maps is generally left as it was originally cataloged by a participating library. MARC subfields are omitted and can be inserted in the Description field. Datasets : Harvested datasets often are lacking descriptive titles and may need to be augmented with place names. Dates may also be added to the end, but if the dataset is subject to updates, the data should be left off. Acronyms should be spelled out. The preferred format for dataset titles is: Theme [place] {date} . This punctuation allows for batch processing and splitting title elements. Language Although Language is optional in the OGM schema , a three-digit code is required for the BTAA Geoportal. Creator Spell all Acronyms out. Publisher Maps : Publisher values for maps are pulled from the original catalog record. Remove subfields for place names and dates. Datasets : The BTAA Geoportal does not use the Publisher field for Datasets. Provider This is the name of the organization hosting the resources. If the organization is part of the BTAA library network, a university icon will display next to the resource's title. However, most Providers will not have an icon. The BTAA Geoportal has a much longer list of Providers than other GeoBlacklight instances. This is because we are harvesting metadata from external sources, rather than just participating library institutions. Bounding Box Provide Bounding Boxes in this format: W,S,E,N When the record is published to the Geoportal, these coordinates will be programmatically converted to other formats. The Bounding Box field ( dcat_bbox_s ) uses this order: ENVELOPE(W,E,N,S) The Geometry field ( locn_geometry ) uses a WKT format and the coordinate order will be converted to this layout: POLYGON((W N, E N, E S, W S, W N)) Example: Metadata CSV: -120,10,-80,35 converts to dcat_bbox_s: ENVELOPE(-120,-80,35,10) locn_geometry: POLYGON((-120 35, -80 35, -80 10, -120 10, -120 35))","title":"Entry Guidelines"},{"location":"entry-usage-guidelines/#btaa-specific-entry-guidelines","text":"The BTAA Geoportal has more specific guidelines for some fields from OpenGeoMetadata (OGM).","title":"BTAA Specific Entry Guidelines"},{"location":"entry-usage-guidelines/#title","text":"Maps : The title for scanned maps is generally left as it was originally cataloged by a participating library. MARC subfields are omitted and can be inserted in the Description field. Datasets : Harvested datasets often are lacking descriptive titles and may need to be augmented with place names. Dates may also be added to the end, but if the dataset is subject to updates, the data should be left off. Acronyms should be spelled out. The preferred format for dataset titles is: Theme [place] {date} . This punctuation allows for batch processing and splitting title elements.","title":"Title"},{"location":"entry-usage-guidelines/#language","text":"Although Language is optional in the OGM schema , a three-digit code is required for the BTAA Geoportal.","title":"Language"},{"location":"entry-usage-guidelines/#creator","text":"Spell all Acronyms out.","title":"Creator"},{"location":"entry-usage-guidelines/#publisher","text":"Maps : Publisher values for maps are pulled from the original catalog record. Remove subfields for place names and dates. Datasets : The BTAA Geoportal does not use the Publisher field for Datasets.","title":"Publisher"},{"location":"entry-usage-guidelines/#provider","text":"This is the name of the organization hosting the resources. If the organization is part of the BTAA library network, a university icon will display next to the resource's title. However, most Providers will not have an icon. The BTAA Geoportal has a much longer list of Providers than other GeoBlacklight instances. This is because we are harvesting metadata from external sources, rather than just participating library institutions.","title":"Provider"},{"location":"entry-usage-guidelines/#bounding-box","text":"Provide Bounding Boxes in this format: W,S,E,N When the record is published to the Geoportal, these coordinates will be programmatically converted to other formats. The Bounding Box field ( dcat_bbox_s ) uses this order: ENVELOPE(W,E,N,S) The Geometry field ( locn_geometry ) uses a WKT format and the coordinate order will be converted to this layout: POLYGON((W N, E N, E S, W S, W N)) Example: Metadata CSV: -120,10,-80,35 converts to dcat_bbox_s: ENVELOPE(-120,-80,35,10) locn_geometry: POLYGON((-120 35, -80 35, -80 10, -120 10, -120 35))","title":"Bounding Box"},{"location":"relations/","text":"Relations and the Collection Model This document describes the content organization model for the GeoBlacklight application and how to relate records in the BTAA Geoportal. Content Organization Model GeoBlacklight organizes records with a network model rather than with a hierarchical model. It is a flat system whereby every database entry is a \"Layer\" and uses the same metadata fields. Unlike many digital library applications, it does not have different types of records for entities such as \"communities,\" \"collections,\" or \"groups.\" As a result, it does not present a breadcrumb navigation structure, and all records appear in the same catalog directory with the URL of https:geo.btaa.org/catalog/ ID . Instead of a hierarchy, GeoBlacklight relates records via metadata fields. These fields include Member Of , Is Part Of , Is Version Of , Source , and a general Relation . This flexibility allows records to be presented in several different ways. For example, records can have multiple parent/child/grandchild/sibling relationships. In addition, they can be nested (i.e., a collection can belong to another collection). They can also connect data layers about similar topics or represent different years in a series. The following diagram illustrates how the BTAA Geoportal organizes records. The connecting arrow lines indicate the name of the relationship. The labels reflect each record's Resource Class ( Collections , Websites , Datasets , Maps , Web services ). Collections The BTAA Geoportal interprets the Resource Class, Collections , as top-level, custom groupings. These reflect our curation activities and priorities. Other records are linked to Collections using the Member Of field. The ID of the parent record is added to the child record only. View all of the current Collections in the geoportal at this link: https://geo.btaa.org/?f%5Bgbl_resourceClass_sm%5D%5B%5D=Collections Websites The BTAA Geoportal uses the Resource Class, Websites , to create parent records for data portals, digital libraries, dashboards, and interactive maps. These often start off as standalone records. Once the items in a website have been indexed, they will have child records. Individual Datasets , Maps , or Web service s are linked to the Website they came from using the Is Part Of field. The ID of the parent record is added to the child record only. View all of the current Websites in the geoportal at this link: https://geo.btaa.org/?f%5Bgbl_resourceClass_sm%5D%5B%5D=Websites Datasets, Maps, and Web services The items in this Resource Class represent individual data layers, scanned map files, and/or geospatial web services. (Some items may have multiple Resource Classes attached to the same record.) This item class is likely to have the most relationships specified in the metadata. A typical Datasets record might have the following: Member Of a Collections record Is Part Of a Websites record If the data was digitized from a paper map in the geoportal, it can be linked to the Maps record via the Source relation a general Relation to a research guide or similar dataset Multipart Items Many items in the geoportal are multipart. There may be individual pages from an atlas, sublayers from a larger project, or datasets broken up into more than one download. In these cases, the Is Part Of field is used. As a result, these items may have multiple Is Part Of relationships- (1) the parent for the multipart items and (2) the original website.","title":"Collection Model"},{"location":"relations/#relations-and-the-collection-model","text":"This document describes the content organization model for the GeoBlacklight application and how to relate records in the BTAA Geoportal.","title":"Relations and the Collection Model"},{"location":"relations/#content-organization-model","text":"GeoBlacklight organizes records with a network model rather than with a hierarchical model. It is a flat system whereby every database entry is a \"Layer\" and uses the same metadata fields. Unlike many digital library applications, it does not have different types of records for entities such as \"communities,\" \"collections,\" or \"groups.\" As a result, it does not present a breadcrumb navigation structure, and all records appear in the same catalog directory with the URL of https:geo.btaa.org/catalog/ ID . Instead of a hierarchy, GeoBlacklight relates records via metadata fields. These fields include Member Of , Is Part Of , Is Version Of , Source , and a general Relation . This flexibility allows records to be presented in several different ways. For example, records can have multiple parent/child/grandchild/sibling relationships. In addition, they can be nested (i.e., a collection can belong to another collection). They can also connect data layers about similar topics or represent different years in a series. The following diagram illustrates how the BTAA Geoportal organizes records. The connecting arrow lines indicate the name of the relationship. The labels reflect each record's Resource Class ( Collections , Websites , Datasets , Maps , Web services ).","title":"Content Organization Model"},{"location":"relations/#collections","text":"The BTAA Geoportal interprets the Resource Class, Collections , as top-level, custom groupings. These reflect our curation activities and priorities. Other records are linked to Collections using the Member Of field. The ID of the parent record is added to the child record only. View all of the current Collections in the geoportal at this link: https://geo.btaa.org/?f%5Bgbl_resourceClass_sm%5D%5B%5D=Collections","title":"Collections"},{"location":"relations/#websites","text":"The BTAA Geoportal uses the Resource Class, Websites , to create parent records for data portals, digital libraries, dashboards, and interactive maps. These often start off as standalone records. Once the items in a website have been indexed, they will have child records. Individual Datasets , Maps , or Web service s are linked to the Website they came from using the Is Part Of field. The ID of the parent record is added to the child record only. View all of the current Websites in the geoportal at this link: https://geo.btaa.org/?f%5Bgbl_resourceClass_sm%5D%5B%5D=Websites","title":"Websites"},{"location":"relations/#datasets-maps-and-web-services","text":"The items in this Resource Class represent individual data layers, scanned map files, and/or geospatial web services. (Some items may have multiple Resource Classes attached to the same record.) This item class is likely to have the most relationships specified in the metadata. A typical Datasets record might have the following: Member Of a Collections record Is Part Of a Websites record If the data was digitized from a paper map in the geoportal, it can be linked to the Maps record via the Source relation a general Relation to a research guide or similar dataset","title":"Datasets, Maps, and Web services"},{"location":"relations/#multipart-items","text":"Many items in the geoportal are multipart. There may be individual pages from an atlas, sublayers from a larger project, or datasets broken up into more than one download. In these cases, the Is Part Of field is used. As a result, these items may have multiple Is Part Of relationships- (1) the parent for the multipart items and (2) the original website.","title":"Multipart Items"},{"location":"workflow/","text":"Workflow 1. Submit Records The B1G Geoportal holds metadata records that point to geospatial data, maps, aerial imagery, and websites hosted online by external organizations. It is the role of the Team members to seek out new content for the geoportal. Team members are responsible for finding records in their own or adjacent states. Regional or national collections will be selected by the Collections Steering Group. Criteria for submission - Review the Collections Strategy from the Collections Development Committee. - Resources need to be accessible over the web. Datasets should have a download or web services link. Maps should have a scanned image with a thumbnail and download link. - Websites and Interactive Applications will be evaluated for accession on a case by case basis. - The resources should be out of copyright and publicly available. - Places to find public domain collections: - State GIS clearinghouses - State agencies - County or City GIS departments - University libraries or research repositories - Nonprofit organizations, especially those with an environmental focus. - The resources should have a spatial component. Nonspatial data tables are out of scope. - If you are unsure if the collection meets these criteria, go ahead and submit it as \"prospective\". The Metadata Coordinator will review it in consultation with you. How to submit new records 1. Optional: Contact the organization - Use this template to inform the organization that we plan to include their resources in our geoportal. - If metadata for the resources are not readily available, the organization may be able to send them to you. 2. Send an email to the Metadata Coordinator - Include a link to the collection - Provide a Title and Description for the collection record 3. The submission will be added to our collections processing queue The Metadata Coordinator will assign an alphanumeric code for the collection. This code will also be added to each metadata record to facilitate administrative tasks and for grouping items by their source. Code Naming Schema First part of string Contributing institution 01 Indiana University 02 University of Illinois Urbana-Campaign 03 University of Iowa 04 University of Maryland 05 University of Minnesota 06 Michigan State University 07 University of Michigan 08 Pennsylvania State University 09 Purdue University 10 University of Wisconsin-Madison 11 The Ohio State University 12 University of Chicago 13 University of Nebraska-Lincoln 14 Rutgers University Second part of string Type of organization hosting the datasests a State b County c Municipality d University f Other (ex. NGOs, Regional Groups, Collaborations) g Federal Third part of string The sequence number added in order of accession or a county FIPs code -01 First collection added from same institution and type of organization -02 Second collection added from same institution and type of organization -55079 County FIPS code for Milwaukee County, Wisconsin Example code for a collection sourced from Milwaukee County: '10b-55079' 2. Metadata Transition This stage involves batch processing of the records, including harvesting, transformations, crosswalking information. This stage is carried out by the Metadata Coordinator, who may contact Team members for assistance. Regardless of the method used for acquiring the metadata, it is always transformed into a spreadsheet for editing. These spreadsheets are uploaded to GEOMG Metadata Editor. Because of the variety of platforms and standards, this process can take many forms. The Metadata Coordinator will contact Team members if they need to supply metadata directly. Here are the most common methods per resource type: Geospatial data API Harvesting Most data portals have APIs that can be programmatically parsed to obtain metadata for each record. DCAT enabled portals: ArcGIS Open Data Portals (HUB), Socrata portals, and some others share metadata in the DCAT standard . This is typically accessed by appending \u201c/data.json\u201d to the end of the portal\u2019s base URL. View our harvesting scripts for DCAT enabled portals here. CKAN / DKAN portals: This application uses a custom metadata schema for their API. View our harvesting scripts for CKAN portals here. HTML Parsing If a data portal or website does not have an API, we may be able to parse the HTML pages to obtain the metadata needed to create GeoBlacklight schema records. This is done using custom View our harvesting scripts for HTML parsing here. Individual Geospatial Metadata Standard files Geospatial metadata standards are expressed in the XML format, which can be parsed to extract metadata needed to create GeoBlacklight schema records. The following file types are accepted for metadata extraction and can serve as Supplemental Metadata: ISO 19139 XML and FGDC XML files : They are parsed to extract metadata values for GeoBlacklight metadata using the project created Python scripts found in BTAA-Geospatial-Data-Project/parse-xml ArcGIS 1.0 Metadata XML files : These records are transformed to ISO 19139 using XSLT. They are then treated the same as the ISO as described above. Downloading Data Some metadata is only available as part of a zipped download of the datasets. In this case, UMN staff will use scripts to batch download the records, unzip them, and process their metadata locally. Maps OAI-PMH The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a framework that can be used to harvest metadata records from enabled repositories. The records are usually available as a simple Dublin Core XML format. If the protocol is not set up to include extra fields, such as the map image's download link or bounding box, this method may not be sufficient on its own. Spreadsheets Administrators for university repositories for scanned maps or data can often export metadata into a spreadsheet, especially for Dublin Core. This method is preferred, because the University IT professionals and librarians can control which fields to export, and because transformations by the Metadata Coordinator are not necessary. The B1G Map Template shows all of the fields needed for GeoBlacklight. MARC files The best way to transfer this type of metadata is to send a single file containing multiple records in the .MRC or MARC XML format. The Metadata Coordinator will use MarcEdit or XML parsing to transform the records to GeoBlacklight using the project-designated MARC to GBL crosswalk, but Team Members can specify preferences. 3. Edit Records Once the metadata is in spreadsheet form, it is ready to be normalized and augmented. UMN Staff will add template information and use spreadsheet functions or scripts to programmatically complete the metadata records. The GBL Metadata Template is for creating GeoBlacklight metadata. Refer to the documentation for the Aardvark fields and the B1G profile fields for guidance on values and formats. 4. Publish Records Once the editing spreadsheets are completed, UMN Staff uploads the records to GEOMG , a metadata management tool. GEOMG validates records and performs any needed field transformations. Once the records are satisfactory, they are published and available in the BTAA Geoportal. Maintenance General Maintenance All project team members are encouraged to review the geoportal records assigned to their institutions periodically to check for issues. Use the feedback form at the top of each page in the geoportal to report errors or suggestions. This submission will include the URL of the last page you were on, and it will be sent to the Metadata Coordinator. Broken Links The geoportal will be programmatically checked for broken links on a monthly basis. Systematic errors will be fixed by UMN Staff. Some records from this report may be referred back to Team Members for investigating broken links. Subsequent Accessions Portals that utilize the DCAT metadata standard will be re-accessioned monthly. Other GIS data portals will be periodically re-accessioned by the Metadata Coordinator at least once per year. Team members may be asked to review this work and provide input on decisions for problematic records. Retired Records When an external resource has been moved, deleted, or versioned to a new access link, the original record is retired from the BTAA Geoportal. This is done by converting the Publication State of the record from 'Published' to 'Unpublished'. The record is not deleted from the database and can still be accessed via a direct link. However, it will not show up in any search queries.","title":"Lifecycle"},{"location":"workflow/#workflow","text":"","title":"Workflow"},{"location":"workflow/#1-submit-records","text":"The B1G Geoportal holds metadata records that point to geospatial data, maps, aerial imagery, and websites hosted online by external organizations. It is the role of the Team members to seek out new content for the geoportal. Team members are responsible for finding records in their own or adjacent states. Regional or national collections will be selected by the Collections Steering Group. Criteria for submission - Review the Collections Strategy from the Collections Development Committee. - Resources need to be accessible over the web. Datasets should have a download or web services link. Maps should have a scanned image with a thumbnail and download link. - Websites and Interactive Applications will be evaluated for accession on a case by case basis. - The resources should be out of copyright and publicly available. - Places to find public domain collections: - State GIS clearinghouses - State agencies - County or City GIS departments - University libraries or research repositories - Nonprofit organizations, especially those with an environmental focus. - The resources should have a spatial component. Nonspatial data tables are out of scope. - If you are unsure if the collection meets these criteria, go ahead and submit it as \"prospective\". The Metadata Coordinator will review it in consultation with you.","title":"1. Submit Records"},{"location":"workflow/#how-to-submit-new-records","text":"1. Optional: Contact the organization - Use this template to inform the organization that we plan to include their resources in our geoportal. - If metadata for the resources are not readily available, the organization may be able to send them to you. 2. Send an email to the Metadata Coordinator - Include a link to the collection - Provide a Title and Description for the collection record 3. The submission will be added to our collections processing queue The Metadata Coordinator will assign an alphanumeric code for the collection. This code will also be added to each metadata record to facilitate administrative tasks and for grouping items by their source.","title":"How to submit new records"},{"location":"workflow/#code-naming-schema","text":"First part of string Contributing institution 01 Indiana University 02 University of Illinois Urbana-Campaign 03 University of Iowa 04 University of Maryland 05 University of Minnesota 06 Michigan State University 07 University of Michigan 08 Pennsylvania State University 09 Purdue University 10 University of Wisconsin-Madison 11 The Ohio State University 12 University of Chicago 13 University of Nebraska-Lincoln 14 Rutgers University Second part of string Type of organization hosting the datasests a State b County c Municipality d University f Other (ex. NGOs, Regional Groups, Collaborations) g Federal Third part of string The sequence number added in order of accession or a county FIPs code -01 First collection added from same institution and type of organization -02 Second collection added from same institution and type of organization -55079 County FIPS code for Milwaukee County, Wisconsin Example code for a collection sourced from Milwaukee County: '10b-55079'","title":"Code Naming Schema"},{"location":"workflow/#2-metadata-transition","text":"This stage involves batch processing of the records, including harvesting, transformations, crosswalking information. This stage is carried out by the Metadata Coordinator, who may contact Team members for assistance. Regardless of the method used for acquiring the metadata, it is always transformed into a spreadsheet for editing. These spreadsheets are uploaded to GEOMG Metadata Editor. Because of the variety of platforms and standards, this process can take many forms. The Metadata Coordinator will contact Team members if they need to supply metadata directly. Here are the most common methods per resource type:","title":"2. Metadata Transition"},{"location":"workflow/#geospatial-data","text":"API Harvesting Most data portals have APIs that can be programmatically parsed to obtain metadata for each record. DCAT enabled portals: ArcGIS Open Data Portals (HUB), Socrata portals, and some others share metadata in the DCAT standard . This is typically accessed by appending \u201c/data.json\u201d to the end of the portal\u2019s base URL. View our harvesting scripts for DCAT enabled portals here. CKAN / DKAN portals: This application uses a custom metadata schema for their API. View our harvesting scripts for CKAN portals here. HTML Parsing If a data portal or website does not have an API, we may be able to parse the HTML pages to obtain the metadata needed to create GeoBlacklight schema records. This is done using custom View our harvesting scripts for HTML parsing here. Individual Geospatial Metadata Standard files Geospatial metadata standards are expressed in the XML format, which can be parsed to extract metadata needed to create GeoBlacklight schema records. The following file types are accepted for metadata extraction and can serve as Supplemental Metadata: ISO 19139 XML and FGDC XML files : They are parsed to extract metadata values for GeoBlacklight metadata using the project created Python scripts found in BTAA-Geospatial-Data-Project/parse-xml ArcGIS 1.0 Metadata XML files : These records are transformed to ISO 19139 using XSLT. They are then treated the same as the ISO as described above. Downloading Data Some metadata is only available as part of a zipped download of the datasets. In this case, UMN staff will use scripts to batch download the records, unzip them, and process their metadata locally.","title":"Geospatial data"},{"location":"workflow/#maps","text":"OAI-PMH The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a framework that can be used to harvest metadata records from enabled repositories. The records are usually available as a simple Dublin Core XML format. If the protocol is not set up to include extra fields, such as the map image's download link or bounding box, this method may not be sufficient on its own. Spreadsheets Administrators for university repositories for scanned maps or data can often export metadata into a spreadsheet, especially for Dublin Core. This method is preferred, because the University IT professionals and librarians can control which fields to export, and because transformations by the Metadata Coordinator are not necessary. The B1G Map Template shows all of the fields needed for GeoBlacklight. MARC files The best way to transfer this type of metadata is to send a single file containing multiple records in the .MRC or MARC XML format. The Metadata Coordinator will use MarcEdit or XML parsing to transform the records to GeoBlacklight using the project-designated MARC to GBL crosswalk, but Team Members can specify preferences.","title":"Maps"},{"location":"workflow/#3-edit-records","text":"Once the metadata is in spreadsheet form, it is ready to be normalized and augmented. UMN Staff will add template information and use spreadsheet functions or scripts to programmatically complete the metadata records. The GBL Metadata Template is for creating GeoBlacklight metadata. Refer to the documentation for the Aardvark fields and the B1G profile fields for guidance on values and formats.","title":"3. Edit Records"},{"location":"workflow/#4-publish-records","text":"Once the editing spreadsheets are completed, UMN Staff uploads the records to GEOMG , a metadata management tool. GEOMG validates records and performs any needed field transformations. Once the records are satisfactory, they are published and available in the BTAA Geoportal.","title":"4. Publish Records"},{"location":"workflow/#maintenance","text":"","title":"Maintenance"},{"location":"workflow/#general-maintenance","text":"All project team members are encouraged to review the geoportal records assigned to their institutions periodically to check for issues. Use the feedback form at the top of each page in the geoportal to report errors or suggestions. This submission will include the URL of the last page you were on, and it will be sent to the Metadata Coordinator.","title":"General Maintenance"},{"location":"workflow/#broken-links","text":"The geoportal will be programmatically checked for broken links on a monthly basis. Systematic errors will be fixed by UMN Staff. Some records from this report may be referred back to Team Members for investigating broken links.","title":"Broken Links"},{"location":"workflow/#subsequent-accessions","text":"Portals that utilize the DCAT metadata standard will be re-accessioned monthly. Other GIS data portals will be periodically re-accessioned by the Metadata Coordinator at least once per year. Team members may be asked to review this work and provide input on decisions for problematic records.","title":"Subsequent Accessions"},{"location":"workflow/#retired-records","text":"When an external resource has been moved, deleted, or versioned to a new access link, the original record is retired from the BTAA Geoportal. This is done by converting the Publication State of the record from 'Published' to 'Unpublished'. The record is not deleted from the database and can still be accessed via a direct link. However, it will not show up in any search queries.","title":"Retired Records"}]} \ No newline at end of file diff --git a/search/worker.js b/search/worker.js new file mode 100644 index 00000000..8628dbce --- /dev/null +++ b/search/worker.js @@ -0,0 +1,133 @@ +var base_path = 'function' === typeof importScripts ? '.' : '/search/'; +var allowSearch = false; +var index; +var documents = {}; +var lang = ['en']; +var data; + +function getScript(script, callback) { + console.log('Loading script: ' + script); + $.getScript(base_path + script).done(function () { + callback(); + }).fail(function (jqxhr, settings, exception) { + console.log('Error: ' + exception); + }); +} + +function getScriptsInOrder(scripts, callback) { + if (scripts.length === 0) { + callback(); + return; + } + getScript(scripts[0], function() { + getScriptsInOrder(scripts.slice(1), callback); + }); +} + +function loadScripts(urls, callback) { + if( 'function' === typeof importScripts ) { + importScripts.apply(null, urls); + callback(); + } else { + getScriptsInOrder(urls, callback); + } +} + +function onJSONLoaded () { + data = JSON.parse(this.responseText); + var scriptsToLoad = ['lunr.js']; + if (data.config && data.config.lang && data.config.lang.length) { + lang = data.config.lang; + } + if (lang.length > 1 || lang[0] !== "en") { + scriptsToLoad.push('lunr.stemmer.support.js'); + if (lang.length > 1) { + scriptsToLoad.push('lunr.multi.js'); + } + if (lang.includes("ja") || lang.includes("jp")) { + scriptsToLoad.push('tinyseg.js'); + } + for (var i=0; i < lang.length; i++) { + if (lang[i] != 'en') { + scriptsToLoad.push(['lunr', lang[i], 'js'].join('.')); + } + } + } + loadScripts(scriptsToLoad, onScriptsLoaded); +} + +function onScriptsLoaded () { + console.log('All search scripts loaded, building Lunr index...'); + if (data.config && data.config.separator && data.config.separator.length) { + lunr.tokenizer.separator = new RegExp(data.config.separator); + } + + if (data.index) { + index = lunr.Index.load(data.index); + data.docs.forEach(function (doc) { + documents[doc.location] = doc; + }); + console.log('Lunr pre-built index loaded, search ready'); + } else { + index = lunr(function () { + if (lang.length === 1 && lang[0] !== "en" && lunr[lang[0]]) { + this.use(lunr[lang[0]]); + } else if (lang.length > 1) { + this.use(lunr.multiLanguage.apply(null, lang)); // spread operator not supported in all browsers: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_operator#Browser_compatibility + } + this.field('title'); + this.field('text'); + this.ref('location'); + + for (var i=0; i < data.docs.length; i++) { + var doc = data.docs[i]; + this.add(doc); + documents[doc.location] = doc; + } + }); + console.log('Lunr index built, search ready'); + } + allowSearch = true; + postMessage({config: data.config}); + postMessage({allowSearch: allowSearch}); +} + +function init () { + var oReq = new XMLHttpRequest(); + oReq.addEventListener("load", onJSONLoaded); + var index_path = base_path + '/search_index.json'; + if( 'function' === typeof importScripts ){ + index_path = 'search_index.json'; + } + oReq.open("GET", index_path); + oReq.send(); +} + +function search (query) { + if (!allowSearch) { + console.error('Assets for search still loading'); + return; + } + + var resultDocuments = []; + var results = index.search(query); + for (var i=0; i < results.length; i++){ + var result = results[i]; + doc = documents[result.ref]; + doc.summary = doc.text.substring(0, 200); + resultDocuments.push(doc); + } + return resultDocuments; +} + +if( 'function' === typeof importScripts ) { + onmessage = function (e) { + if (e.data.init) { + init(); + } else if (e.data.query) { + postMessage({ results: search(e.data.query) }); + } else { + console.error("Worker - Unrecognized message: " + e); + } + }; +} diff --git a/sitemap.xml b/sitemap.xml new file mode 100644 index 00000000..f2132f64 --- /dev/null +++ b/sitemap.xml @@ -0,0 +1,38 @@ + +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Workflow
+
1. Submit Records
+The B1G Geoportal holds metadata records that point to geospatial data, maps, aerial imagery, and websites hosted online by external organizations. It is the role of the Team members to seek out new content for the geoportal. Team members are responsible for finding records in their own or adjacent states. Regional or national collections will be selected by the Collections Steering Group.
+Criteria for submission +- Review the Collections Strategy from the Collections Development Committee. +- Resources need to be accessible over the web. Datasets should have a download or web services link. Maps should have a scanned image with a thumbnail and download link. +- Websites and Interactive Applications will be evaluated for accession on a case by case basis. +- The resources should be out of copyright and publicly available. +- Places to find public domain collections: + - State GIS clearinghouses + - State agencies + - County or City GIS departments + - University libraries or research repositories + - Nonprofit organizations, especially those with an environmental focus. +- The resources should have a spatial component. Nonspatial data tables are out of scope. +- If you are unsure if the collection meets these criteria, go ahead and submit it as "prospective". The Metadata Coordinator will review it in consultation with you.
+How to submit new records
+1. Optional: Contact the organization +- Use this template to inform the organization that we plan to include their resources in our geoportal. +- If metadata for the resources are not readily available, the organization may be able to send them to you.
+2. Send an email to the Metadata Coordinator +- Include a link to the collection +- Provide a Title and Description for the collection record
+3. The submission will be added to our collections processing queue +The Metadata Coordinator will assign an alphanumeric code for the collection. This code will also be added to each metadata record to facilitate administrative tasks and for grouping items by their source.
+Code Naming Schema
+| First part of string | +Contributing institution | +
|---|---|
| 01 | +Indiana University | +
| 02 | +University of Illinois Urbana-Campaign | +
| 03 | +University of Iowa | +
| 04 | +University of Maryland | +
| 05 | +University of Minnesota | +
| 06 | +Michigan State University | +
| 07 | +University of Michigan | +
| 08 | +Pennsylvania State University | +
| 09 | +Purdue University | +
| 10 | +University of Wisconsin-Madison | +
| 11 | +The Ohio State University | +
| 12 | +University of Chicago | +
| 13 | +University of Nebraska-Lincoln | +
| 14 | +Rutgers University | +
| Second part of string | +Type of organization hosting the datasests | +
|---|---|
| a | +State | +
| b | +County | +
| c | +Municipality | +
| d | +University | +
| f | +Other (ex. NGOs, Regional Groups, Collaborations) | +
| g | +Federal | +
| Third part of string | +The sequence number added in order of accession or a county FIPs code | +
|---|---|
| -01 | +First collection added from same institution and type of organization | +
| -02 | +Second collection added from same institution and type of organization | +
| -55079 | +County FIPS code for Milwaukee County, Wisconsin | +
Example code for a collection sourced from Milwaukee County: '10b-55079'
+2. Metadata Transition
+This stage involves batch processing of the records, including harvesting, transformations, crosswalking information. This stage is carried out by the Metadata Coordinator, who may contact Team members for assistance.
+Regardless of the method used for acquiring the metadata, it is always transformed into a spreadsheet for editing. These spreadsheets are uploaded to GEOMG Metadata Editor.
+Because of the variety of platforms and standards, this process can take many forms. The Metadata Coordinator will contact Team members if they need to supply metadata directly. Here are the most common methods per resource type:
+Geospatial data
+API Harvesting
+Most data portals have APIs that can be programmatically parsed to obtain metadata for each record.
+-
+
- DCAT enabled portals: ArcGIS Open Data Portals (HUB), Socrata portals, and some others share metadata in the DCAT standard. This is typically accessed by appending “/data.json” to the end of the portal’s base URL. View our harvesting scripts for DCAT enabled portals here. + +
- CKAN / DKAN portals: This application uses a custom metadata schema for their API. View our harvesting scripts for CKAN portals here. +
HTML Parsing
+If a data portal or website does not have an API, we may be able to parse the HTML pages to obtain the metadata needed to create GeoBlacklight schema records. This is done using custom View our harvesting scripts for HTML parsing here.
+Individual Geospatial Metadata Standard files
+Geospatial metadata standards are expressed in the XML format, which can be parsed to extract metadata needed to create GeoBlacklight schema records. +The following file types are accepted for metadata extraction and can serve as Supplemental Metadata:
+-
+
- ISO 19139 XML and FGDC XML files: They are parsed to extract metadata values for GeoBlacklight metadata using the project created Python scripts found in BTAA-Geospatial-Data-Project/parse-xml +
- ArcGIS 1.0 Metadata XML files: These records are transformed to ISO 19139 using XSLT. They are then treated the same as the ISO as described above. +
Downloading Data
+Some metadata is only available as part of a zipped download of the datasets. In this case, UMN staff will use scripts to batch download the records, unzip them, and process their metadata locally.
+Maps
+OAI-PMH
+The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a framework that can be used to harvest metadata records from enabled repositories. The records are usually available as a simple Dublin Core XML format. If the protocol is not set up to include extra fields, such as the map image's download link or bounding box, this method may not be sufficient on its own.
+Spreadsheets
+Administrators for university repositories for scanned maps or data can often export metadata into a spreadsheet, especially for Dublin Core. This method is preferred, because the University IT professionals and librarians can control which fields to export, and because transformations by the Metadata Coordinator are not necessary. The B1G Map Template shows all of the fields needed for GeoBlacklight.
+MARC files +The best way to transfer this type of metadata is to send a single file containing multiple records in the .MRC or MARC XML format. The Metadata Coordinator will use MarcEdit or XML parsing to transform the records to GeoBlacklight using the project-designated MARC to GBL crosswalk, but Team Members can specify preferences.
+3. Edit Records
+Once the metadata is in spreadsheet form, it is ready to be normalized and augmented. UMN Staff will add template information and use spreadsheet functions or scripts to programmatically complete the metadata records.
+-
+
- The GBL Metadata Template is for creating GeoBlacklight metadata. +
- Refer to the documentation for the Aardvark fields and the B1G profile fields for guidance on values and formats. +
4. Publish Records
+Once the editing spreadsheets are completed, UMN Staff uploads the records to GEOMG, a metadata management tool. GEOMG validates records and performs any needed field transformations. Once the records are satisfactory, they are published and available in the BTAA Geoportal.
Maintenance
+General Maintenance
+All project team members are encouraged to review the geoportal records assigned to their institutions periodically to check for issues. Use the feedback form at the top of each page in the geoportal to report errors or suggestions. This submission will include the URL of the last page you were on, and it will be sent to the Metadata Coordinator.
+Broken Links
+The geoportal will be programmatically checked for broken links on a monthly basis. Systematic errors will be fixed by UMN Staff. Some records from this report may be referred back to Team Members for investigating broken links.
+Subsequent Accessions
+-
+
- Portals that utilize the DCAT metadata standard will be re-accessioned monthly. +
- Other GIS data portals will be periodically re-accessioned by the Metadata Coordinator at least once per year. +
- Team members may be asked to review this work and provide input on decisions for problematic records. +
Retired Records
+When an external resource has been moved, deleted, or versioned to a new access link, the original record is retired from the BTAA Geoportal. This is done by converting the Publication State of the record from 'Published' to 'Unpublished'. The record is not deleted from the database and can still be accessed via a direct link. However, it will not show up in any search queries.
+ +
+
+
+
+ « Previous
+
+
+ Next »
+
+
+
+
+
+
+
+
+
+
+