Version 4.5

Update input guidelines for Creator, Creator ID
Remove Harvesting Guide info (migrating to separate site)
Edit Submitting Metadata page
Minor copy editing

docs/GEOMG.md

@@ -1,5 +1,3 @@
-!!! Warning "This guide is a work in progress (August 2022)"
-
 ## About
 
 **What is it?**
@@ -16,7 +14,9 @@
 
 **Can other GeoBlacklight projects adopt it?**
 
-Not yet. We are currently working on offering this tool as a plugin for GeoBlacklight. Our tentative plan for release is early 2023.  In the meantime, this presentation describes the motivation for building the tool and a few screencasts showing how it works:
+We are currently working on offering this tool as a plugin for GeoBlacklight.
+
+In the meantime, this presentation describes the motivation for building the tool and a few screencasts showing how it works:
 
 <iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQAlzzbZxoS__W9ZoLQ1A3GbiwEE9lkvPzTw_VLrlY_7dkPrc8k5ApappPv35-1IjyIM1--Rh0UO28j/embed?start=false&loop=false&delayms=3000" frameborder="0" width="400" height="400" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
 
@@ -25,32 +25,40 @@ Not yet. We are currently working on offering this tool as a plugin for GeoBlack
 ## Layout
 
 
-**Dashboard (Home page)**
+### Dashboard (Home page)
 
 The Dashboard shows a list of all records in the index. These can be selected or filtered. The search functionality mimics the GeoBlacklight interface:
 
-* a search bar at the top: lets a user enter text searches
-* a list of facets on the left: lets a user filter records
-* a Date Range filter above the facets: lets a user select items by Date Created (when they were first added to GEOMG).
+* a search bar at the top for text searches
+* a list of facets on the left to filter records
+* a Date Range filter above the facets to select items by Date Created (when they were first added to GEOMG).
 
 ![](images/geomg-dashboard.png)
 
 
 ----------
-**Form view**
+### Form view
 
-This page is where new records can be manually created and existing records can be edited. Click on the button "View in Geoportal" to open a new tab with the record in the Geoportal. Note: the record is still viewable in the Geoportal via this button, even if it is a Draft or Unpublished.
+This page is where new records can be manually created and existing records can be edited.
 
 ![](images/formView.png)
 
+!!! tip
+	Click on the button "View in Geoportal" to open a new tab with the record in the Geoportal. Note: the record is still viewable in the Geoportal via this button, even if it is a Draft or Unpublished.
 
 ------------
-**Notifications**
+### Notifications
 
 Notifications is where the exported files can be found.
 
 ![](images/notifications.png)
 
+------------
+### Admin Tools
+
+The Admin Tools is a dropdown menu item that contains links to the various actions.
+
+![](images/adminTools.png)
 
 
 ## Selecting records
@@ -97,15 +105,14 @@ A user can create records one by one using the form view.
 	- 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.
+	- When complete, review and troubleshoot any items that did not import in the Failed tab.
 
 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
+	- 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.
+	- Inspect the record and test the links.	- Repeat this process for about 3 records.
 
 
 4. Convert records from 'Draft' to 'Published'

docs/harvest.md

@@ -0,0 +1,32 @@
+The BTAA Geoportal holds metadata records that point to geospatial data, maps, aerial imagery, web services, and websites hosted online by external organizations. These records can be submitted directly using the [GeoBTAA Metadata Template](https://z.umn.edu/b1g-template) or the metadata can be harvested via parsing scripts.
+
+### Spreadsheets (direct submission)
+
+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 [GeoBTAA Metadata Template](https://z.umn.edu/b1g-template) shows all of the fields needed for GeoBlacklight.
+
+
+### API Harvesting or HTML Parsing
+
+Most data portals have APIs or HTML structures 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](https://www.w3.org/TR/vocab-dcat/).
+
+* **CKAN / DKAN** portals: This application uses a custom metadata schema for their API.
+
+* **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.](https://github.com/geobtaa/workflows/tree/main/harvesting/parse-html)
+
+* **OAI-PMH**: The [Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH)](https://www.openarchives.org/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. 
+
+
+### Individual Metadata 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](https://github.com/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.\
+
+* **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.
+

docs/inputGuidelines.md

@@ -10,7 +10,10 @@ For the following elements, the GeoBTAA Metadata Profile has input guidelines be
 : Although [Language is optional in the OGM schema](https://opengeometadata.org/docs/ogm-aardvark/language), a three-digit code is required for the BTAA Geoportal.
 
 ### Creator
-: Spell all Acronyms out.
+: When possible, Creators should be drawn from a value in the [Faceted Application of Subject Terminology (FAST)](https://www.oclc.org/research/areas/data-science/fast.html).
+
+### Creator ID
+: If the Creator value is from a name authority, insert the ID in this field.
 
 ### Publisher
 : **Maps**: Publisher values for maps are pulled from the original catalog record. Remove subfields for place names and dates.
@@ -20,7 +23,6 @@ For the following elements, the GeoBTAA Metadata Profile has input guidelines be
 ### 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.
 
-
 ### Bounding Box
 :  On the Metadata Editing Template, provide Bounding Boxes in this format: **W,S,E,N**
 

docs/lifecycle.md

@@ -3,8 +3,6 @@ toc:
   baselevel:2
 ---
 
-!!! Warning "This guide is a work in progress (August 2022)"
-
 
 ![Metadata Workflow](./images/btaa-metadata-workflow.png)
 
@@ -26,28 +24,26 @@ Things to include:
 
 **3. The submission will be added to our collections processing queue**
 
-Metadata processing tasks are tracked on our public [GitHub project dashboard](https://github.com/orgs/geobtaa/projects/4).
+!!! info
+
+	Metadata processing tasks are tracked on our public [GitHub project dashboard](https://github.com/orgs/geobtaa/projects/4).
 
 
 ## 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.
 
-!!! info "See our [Harvest Guide](harvestGuide.md) for more information on formats and techniques for harvesting metadata"
-
 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. 
 
 
-
-
 ## 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](http://z.umn.edu/b1g-template) is for creating GeoBlacklight metadata.
-- Refer to the documentation for the [Aardvark fields](https://opengeometadata.github.io/aardvark/aardvarkMetadata.html) and the [B1G profile fields](b1g-custom-elements.md) for guidance on values and formats.
+- [The GeoBTAA Metadata Template](http://z.umn.edu/b1g-template) is for creating GeoBlacklight metadata.
+- Refer to the documentation for the [OpenGeoMetadata, version Aardvark fields](https://opengeometadata.org/docs/ogm-aardvark) and the [GeoBTAA Custom Elements](b1g-custom-elements.md) for guidance on values and formats.
 
 
 ## 4. Publish Records

mkdocs.yml

@@ -66,7 +66,7 @@ nav:
      - 'Resource Classes' : 'resourceClasses.md'
 
 - Curation Workflows:
-      - 'Identifying Resources' : 'identify.md'
       - 'Resource Lifecycle' : 'lifecycle.md'
-      - 'Harvest Guide' :  'harvestGuide.md'
+      - 'Identifying Resources' : 'identify.md'
+      - 'Submitting Metadata' :  'harvest.md'
       - 'GEOMG Metadata Toolkit' : 'geomg.md'