agrc · steveoh · Aug 18, 2021 · Aug 18, 2021 · Aug 18, 2021 · Aug 18, 2021
diff --git a/_layouts/default.html b/_layouts/default.html
@@ -143,14 +143,10 @@ <h2 class="logo-text">UGRC
       {%- assign current = page.url | downcase | split: '/' -%}
       <nav class="site-nav">
         <ul id="menu-main-menu" class="menu">
-          <li class="menu-item{%- if current[1] == 'news' -%}{{ " active-1" | prepend: " " }}{%- endif -%}"><a
-              href="{% link news/index.html %}">News</a></li>
-          <li class="menu-item{%- if current[1] == 'data' -%}{{ " active-2" | prepend: " " }}{%- endif -%}"><a
-              href="{% link data/index.html %}">Data</a></li>
-          <li class="menu-item{%- if current[1] == 'developer' -%}{{ " active-3" | prepend: " " }}{%- endif -%}"><a
-              href="{% link developer/index.md %}">Developer</a></li>
-          <li class="menu-item{%- if current[1] == 'about' -%}{{ " active-4" | prepend: " " }}{%- endif -%}"><a
-              href="{% link about/index.md %}">About</a></li>
+          <li class="menu-item{%- if current[1] == 'news' -%}{{ "active-1" | prepend: " " }}{%- endif -%}"><a href="{% link news/index.html %}">News</a></li>
+          <li class="menu-item{%- if current[1] == 'data' -%}{{ "active-2" | prepend: " " }}{%- endif -%}"><a href="{% link data/index.html %}">Data</a></li>
+          <li class="menu-item{%- if current[1] == 'developer' -%}{{ "active-3" | prepend: " " }}{%- endif -%}"><a href="{% link developer/index.md %}">Developer</a></li>
+          <li class="menu-item{%- if current[1] == 'about' -%}{{ "active-4" | prepend: " " }}{%- endif -%}"><a href="{% link about/index.md %}">About</a></li>
           <li class="menu-item"><a href="https://agrc-status.netlify.app/">Status</a></li>
           <li class="menu-item"><a href="{% link search/index.html %}">{% include fa_icon.html class="svg-inline--fa
               fa-w-16" search=true %}</a></li>

diff --git a/_posts/2019-11-12-sgid-product-relaunch-update.md b/_posts/2019-11-12-sgid-product-relaunch-update.md
@@ -58,7 +58,7 @@ UGRC is currently exploring the possibility of expanding the public database to
 ## Open Data Sharing
 {: .text-left}
 
-One of our main goals for the SGID moving forward is to continue to cultivate a sense of open data sharing in the Utah GIS community. The SGID Open Data website is a great example of the success of our [data sharing workflow]({% link gis-data-sharing/open-data/index.md %}), as you can see from the [authoritative data](https://opendata.gis.utah.gov/search?source=utah%20dnr%20online%20maps%2Cutah%20division%20of%20water%20resources) being shared from our agency partners (DNR Water Resources, DNR Water Rights, and Utah Division of State History). We invite our readers to join these partners and participate in this data-sharing initiative. {% include contact.html subject=page.title text="Please get in touch with " contact=site.data.contacts.sgid %} if you have authoritative ArcGIS Online data to share to the SGID Open Data website.
+One of our main goals for the SGID moving forward is to continue to cultivate a sense of open data sharing in the Utah GIS community. The SGID Open Data website is a great example of the success of our [data sharing workflow]({% link sharing/index.md %}), as you can see from the [authoritative data](https://opendata.gis.utah.gov/search?source=utah%20dnr%20online%20maps%2Cutah%20division%20of%20water%20resources) being shared from our agency partners (DNR Water Resources, DNR Water Rights, and Utah Division of State History). We invite our readers to join these partners and participate in this data-sharing initiative. {% include contact.html subject=page.title text="Please get in touch with " contact=site.data.contacts.sgid %} if you have authoritative ArcGIS Online data to share to the SGID Open Data website.
 
 We are excited for the future of the SGID, and we hope you will get involved to help us provide the highest quality GIS data to the State of Utah.
 

diff --git a/_posts/2020-07-14-thinking-beyond-the-map.md b/_posts/2020-07-14-thinking-beyond-the-map.md
@@ -94,8 +94,8 @@ While traditionally we think of GIS as a tool for making maps and creating and m
 
 #### Links related to UGRC's efforts
 
-- [Partnerships and Sharing]({% link gis-data-sharing/index.md %})
-- [Data sharing Initiatives - Farm to AGOL project]({% link gis-data-sharing/open-data/index.md %})
+- [Partnerships and Sharing]({% link sharing/index.md %})
+- [Data sharing Initiatives - Farm to AGOL project]({% link sharing/index.md %}#open-data)
 - [State Geographic Information Database (SGID) - data index]({% link data/index.html %})
 - [Open Data - SGID ESRI Hub site](https://opendata.gis.utah.gov/)
 - [Open SGID - PostgreSQL/PostGIS cloud SGID database]({% link _posts/2020-05-04-introducing-open-sgid.md %})

diff --git a/_redirects b/_redirects
@@ -62,7 +62,7 @@
 /data/farming/grazing-improvement-area/                                                                   /data/farming/grazing-improvements/                                           301
 /data/farming/grazing-improvement-area/                                                                   /data/farming/grazing-improvements/                                           301
 /data/geoscience/aquifers-2/                                                                              /data/geoscience/aquifers/                                                    301
-/data/gis-data-sharing/                                                                                   /gis-data-sharing/                                                            301
+/data/gis-data-sharing/                                                                                   /sharing/                                                            301
 /data/google-imagery-license-signup/                                                                      /discover/license/                                                            301
 /data/google-imagery-license/                                                                             /discover/license/                                                            301
 /data/googleimagery/                                                                                      /data/discover-server-information/                                            301

diff --git a/about/policy/index.md b/about/policy/index.md
@@ -24,7 +24,7 @@ Agreement between UGRC and data stewards for data shared through the SGID.
 #### [SGID Database Policies]({% link about/policy/sgid/index.md %})
 {: .text-left}
 
-UGRC’s guidelines for creating, editing, maintaining, and removing data in the SGID database.
+UGRC’s guidelines for creating, editing, maintaining, and removing data in the SGID.
 
 #### [Open SGID Terms of Use]({% link about/policy/open-sgid/index.md %})
 {: .text-left}

diff --git a/about/policy/metadata/index.md b/about/policy/metadata/index.md
@@ -6,109 +6,57 @@ tags:
   - metadata
   - sgid
 date: 2020-07-09 09:33:34 -0600
-title: Basic Metadata Guidelines
+title: Basic Metadata Requirements
 categories: []
 ---
 
-By most accounts, creating metadata is right up there with organizing your garage. It can be a chore, but it doesn't have to be.
-
-At UGRC, we have decided to make the process more conversational. In other words, instead of looking at a long list of metadata requirements, we thought it would be easier to talk about the data. This is our solution to metadata procrastination.
-
-We have distilled the basic elements of metadata into a few approachable questions. If you can answer these simple questions about your data, then you're officially on your way to good metadata.
-
-#### Can you answer these questions about your data?
-{: .text-left}
-
-##### Summarize your Data
-{: .text-left}
-
-- What is this dataset?
-- What is the purpose of this dataset?
-
-##### Describe your Data
-{: .text-left}
-
-- What does this dataset represent?
-  - ex: road centerlines represent the centerline of a physical road
-- How was this dataset created?
-  - ex: digitized, GPS, etc.
-- How reliable and accurate is the dataset?
-  - ex: survey-grade, mapping-grade, etc.
-- What is the general update schedule for this dataset?
-  - ex: monthly, yearly, as needed, etc.
-- Are there any warnings or limitations on the data?
-  - ex: don’t use parcels as a legal boundary depiction
-  - ex: don’t use parcels as a complete dataset for geocoding
-  - ex: don’t use zip codes for demographic generalization
-- Are there any common misconceptions or assumptions about this data that should be further explained?
-  - ex: highway milepost markers are not an accurate length measurement. If a highway is lengthened or shortened, the markers are not adjusted.
-
-##### Establish Contact Info
-{: .text-left}
-
-- Who created this dataset?
-- What is the best point of contact for this dataset?
-  - if someone had further questions or would like to get involved, who should they contact?
-
-Your answers to these questions can be plugged into the basic metadata elements (discussed below). It's that simple - answer a few questions, transfer your responses, and voilà, you officially have informative, standardized metadata.
-
-_Note: If you contribute data to Utah's State Geographic Information Database (SGID), we encourage you to use our [metadata form](https://docs.google.com/forms/d/e/1FAIpQLSeJSV935GTN3djtErkBdeXkumuZvd10z2805It1-eFn0Mlo9w/viewform?usp=sf_link). It's a great way to update your metadata and make it more discoverable. The form covers all the questions above -and best of all- after you submit your responses, your portion of the process is done! UGRC, in collaboration with the DTS editor, will handle the remaining details._
-
-The above questions are designed to work with the ESRI [Item Description](https://desktop.arcgis.com/en/arcmap/latest/manage-data/metadata/metadata-standards-and-styles.htm#ESRI_SECTION1_29222DC149544E89A4147541A4ACAF86) metadata style. We have found this style to be well-balanced for creating useful, as well as achievable, metadata.
-
-Let's take a closer look at the basic elements of SGID metadata. We like to think of these as our minimum requirements.
-
-### Basic SGID Metadata
-{: .text-left}
+Effective metadata helps people understand the source of a dataset, how up-to-date it is, and any of its inherent restrictions or limitations. Listed below are the minimum metadata items that should be present in any SGID datasets. These correspond to the Esri [Item Description](https://pro.arcgis.com/en/pro-app/latest/help/metadata/view-and-edit-metadata.htm) metadata style and the metadata displayed on an item's ArcGIS Online page.
+## Basic SGID Metadata
 
 #### Title
 {: .text-left}
 
 The title should match the dataset name. If it's a statewide dataset, the title should begin with the word "Utah".
 
-`example: Utah County Boundaries`
+Example: `Utah County Boundaries`
 
 #### Tags
 {: .text-left}
 
-Tags are included in data searches, so at minimum, each SGID dataset should include the stewarding agency (ie: UGRC), SGID, and the appropriate ISO category tag. We also recommend adding any additional, relevant tags that might help with data discoverability. However, there is no need to include words that are contained in the layer's title (these will be omitted).
+Tags are used by ArcGIS Online in its search algorithms and can be used in Open Data to group data. At a minimum, each SGID dataset's tags should include the stewarding agency (ie: UGRC), "SGID", and the appropriate category name. We also recommend adding any additional, relevant tags that might help with data discoverability. However, there is no need to include words that are contained in the layer's title (these will be omitted).
 
 All words in tags should be title-cased except for articles (“of”, “the”, “and”, etc.) or abbreviations. Each tag should be separated by a comma. Please refer to [Using tags effectively](https://www.esri.com/arcgis-blog/products/arcgis-online/data-management/using-tags-effectively/) for more ideas and information.
 
-`example: UGRC, SGID, Recreation, Paths, Biking, Hiking, Horseback Riding`
+Example: `UGRC, SGID, Recreation, Paths, Biking, Hiking, Horseback Riding`
 
 #### Summary
 {: .text-left}
 
-The summary should summarize the description in approximately 2 to 3 sentences.
+The summary should _briefly_ explain the dataset in under 250 characters (an ArcGIS Online limitation). It is primarily used when reviewing ArcGIS Online search results. The summary may end up being very similar to the dataset name for some datasets.
 
-The summary should address the questions presented above in the [summarize your data](#summarize-your-data) section.
+Example: `Utah public library and bookmobile locations`
 
 #### Description
 {: .text-left}
 
-The Description is a more in-depth version of the summary and it should stand on its own. The description should expand on the summary. This is important, particularly, in the event that the summary is missing in the metadata (which is currently the case with [Open Data](https://opendata.gis.utah.gov/) datasets).
-
-The first line of the description should be a date, indicating the last update.
+The description is a more in-depth version of the summary and should stand on its own. It is a great place for details on the source of the data, how frequently it's updated, its usability at certain scales, or any common misconceptions. A good description is also important because it's the main info displayed in [Open Data](https://opendata.gis.utah.gov/) (the summary is not shown).
 
-This section should also contain a link to the corresponding [gis.utah.gov data page]({% link data/index.html %})
+The first line of the description should be the date the dataset was last updated so people have a clear and consistent place to see how fresh or stale it is.
 
-Additionally, the description should address the questions presented above in the [describe your data](#describe-your-data) section.
+For datasets hosted by UGRC, this section should also contain a link to the corresponding [gis.utah.gov data page]({% link data/index.html %}).
 
 #### Credits (as in the source of the data)
 {: .text-left}
 
-This should cover who created the dataset and how you can get in contact with them.
+The credits should clearly state who created the dataset and how you can get in contact with them.
 
-The credits should address the questions presented above in the [establish contact info](#establish-contact-info) section.
+Example: `UGRC, UDOT`
 
-#### Use Limitations
+#### Use Limitations/Terms of Use
 {: .text-left}
 
-This section covers limitation and licensing on the data.
+This section includes both usage limitations (any constraints on where or how the dataset can be used, including disclaimers and attribution rules) and the intellectual property license (if any) associated with the dataset (like Creative Commons).
 
-The language presented here is for reference only and is populated automatically via our [Sweeper](https://github.com/agrc/sweeper) project.
+We use [Sweeper](https://github.com/agrc/sweeper) to automatically populate our hosted datasets with our standard [disclaimer]({% link about/policy/license-disclaimer/index.md %}#disclaimer) and [license]({% link about/policy/license-disclaimer/index.md %}#license).
 
->The data herein, including but not limited to geographic data, tabular data, analytical data, electronic data structures or files, are provided "as is" without warranty of any kind, either expressed or implied, or statutory, including, but not limited to, the implied warranties or merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of the data is assumed by the user.
->[![Creative Commons License](https://i.creativecommons.org/l/by/4.0/88x31.png)](http://creativecommons.org/licenses/by/4.0/){: loading="lazy" }
-This work is licensed under a [Creative Commons Attribution 4.0 International License](http://creativecommons.org/licenses/by/4.0/).
+Open Data will try to find references to the common licenses and will link to the appropriate license. Otherwise, it just lists "Custom License" and displays the item's Terms of Use text.