Best Practices. Geospatial Metadata Creation. MWDL Cultural Heritage Digital Repositories

Similar documents
Navigating to Success: Finding Your Way Through the Challenges of Map Digitization

Meeting Increasing Demands for Metadata

Information and documentation The Dublin Core metadata element set

Network Working Group

SEARCH ENGINE OPTIMIZATION FOR DIGITAL COLLECTIONS. Kenning Arlitsch Patrick OBrien Sandra McIntyre

Digitize All the Things

Getting Found: Search Engine Optimization for Digital Repositories

GUIDELINES FOR THE CREATION OF DIGITAL COLLECTIONS

Metadata, Geospatial data, Data management, Project management, GIS

Archive I. Metadata. 26. May 2015

Digital Public Library of America (DPLA)

Interagency Science Working Group. National Archives and Records Administration

South Dublin County Library Local Studies Collection Development Policy

European Forest Information and Communication Platform

DataShare & Data Audit. Lessons Learned. Robin Rice. Digital Curation Practice, Promise and Prospects

Report of the Ad Hoc Committee for Development of a Standardized Tool for Encoding Archival Finding Aids

Metadata Quality Control for Content Migration: The Metadata Migration Project at the University of Houston Libraries

Queensland recordkeeping metadata standard and guideline

Septennial Calendar by Accredited Institution Revised February 12, 2009

INSTITUTIONALIZE METADATA BEFORE IT INSTITUTIONALIZES YOU

Statement of Work (SOW) for Web Harvesting U.S. Government Printing Office Office of Information Dissemination

INFORMATION SYSTEMS (IS) DATA SERVICES JOB TITLES CANNOT USE FOR VACANCIES

Three use case scenarios for geospatial metadata automation. Tony Mathys and James Reid, EDINA National Data Centre, The University of Edinburgh

Response to Invitation to Tender: requirements and feasibility study on preservation of e-prints

Using Dublin Core for DISCOVER: a New Zealand visual art and music resource for schools

Archimedes Palimpsest Transcription Metadata Standard 22 October 2007 DRAFT

local content in a Europeana cloud for small & medium content providers

Metadata for Data Discovery: The NERC Data Catalogue Service. Steve Donegan

NATIONAL CLIMATE CHANGE & WILDLIFE SCIENCE CENTER & CLIMATE SCIENCE CENTERS DATA MANAGEMENT PLAN GUIDANCE

Covered California CAHPS Ratings Fall 2014 Scoring Health Plan s Historical CAHPS Results

Standards for the Preparation of Digital Geospatial Metadata

Comprehensive Exam Analysis: Student Performance

geoxwalk A Gazetteer Server and Service for UK Academia J.S.Reid

Notes about possible technical criteria for evaluating institutional repository (IR) software

CONSENT AGENDA ACTION ITEM

D EUOSME: European Open Source Metadata Editor (revised )

North Carolina Department of Cultural Resources Digital Preservation Plan. State Archives of North Carolina State Library of North Carolina

Maximise your Microsoft investment to provide Legal Matter Management

North Carolina Digital Preservation Policy. April 2014

SPC 1. Summary Report Integrated Strategic Plan Review and Revision

Melvin P. Thatcher FamilySearch Utah, USA

STATES THAT RECOGNIZE AMERICAN SIGN LANGUAGE AS A FOREIGN LANGUAGE

Geospatial Data Integration with Linked Data and Provenance Tracking

Environment Canada Data Management Program. Paul Paciorek Corporate Services Branch May 7, 2014

OCLC CONTENTdm. Geri Ingram Community Manager. Overview. Spring 2015 CONTENTdm User Conference Goucher College Baltimore MD May 27, 2015

How to Improve Your Library Collections by Increasing Visibility and reliability of Google Webmaster

AHDS Digital Preservation Glossary

Using the Getty Vocabularies as Linked Open Data in a Cataloging Tool for an Academic Teaching Collection: Case Study at the University of Denver

E-Content Service Group Virtual Meeting. Digital Preservation: How to Get Started

UK-EOF Data Solutions Workshop

Quality Assurance Source Requirements Traceability Database. Ram Murthy. Anna Naydenova

Question/Answer Transaction Protocol Overview First Committee Working Draft NISO Committee AZ: September 22, 2003

Metadata for Research Data: Current Practices and Trends

1 Building a metadata schema where to start 1

Bathymetric Attributed Grids (BAGs): Discovery of Marine Datasets and Geospatial Metadata Visualization

OCLC CONTENTdm and the WorldCat Digital Collection Gateway Overview

Sustainability of Large Marine Ecosystems: Bridging the Governance and Socio-Economic Gap

National Geospatial Data Policy Procedure for Geospatial Metadata Management

VITA Bradford R. Cole Utah State University, Merrill-Cazier Library Logan, Utah

Enterprise Vault Whitepaper

Western Association of Fish and Wildlife Agencies/US Fish and Wildlife Service Greater Sage-Grouse Inter-LCC Research Request for Proposals

VGIS HANDBOOK PART 2 - STANDARDS SECTION D METADATA STANDARD

State of Florida ELECTRONIC RECORDKEEPING STRATEGIC PLAN. January 2010 December 2012 DECEMBER 31, 2009

Future Trends in Big Data

Managing Business Records and Archives at the Getty Center

2012 Audit Plan. Finance, Audit and Facilities Committee Board of Regents. November 2011 ATTACHMENT

Data Management Resources at UNC: The Carolina Digital Repository and Dataverse Network

Australian Recordkeeping Metadata Schema. Version 1.0

Analyzing and creating GIS data using Python programming. Josh Foery, JR Franks, Connor McMillan

Chapter 10 Supplement

DIGITAL STEWARDSHIP SUPPLEMENTARY INFORMATION FORM

Monitoring and Reporting Drafting Team Monitoring Indicators Justification Document

CDI/THREDDS Interoperability: the SeaDataNet developments. P. Mazzetti 1,2, S. Nativi 1,2, 1. CNR-IMAA; 2. PIN-UNIFI

Appendix B: SWMP Contact List

Integrating FLOSS repositories on the Web

Guiding Digital Success

United States General Accounting Office February 2003 GAO

Next-Generation Technical Services (NGTS) Digital Asset Management System (DAMS) Requirements

Kristine Brancolini Loyola Marymount University 16 September 2009

Charged! By the Technology Services Council to:

Learning about GPS and GIS

CDI SSF Category 1: Management, Policy and Standards

Agreement Elements for Outsourcing Transfer of Born Digital Content

Checklist for a Data Management Plan draft

Integration of Polish National Bibliography within the repository platform for science and humanities

Indiana University s Library focusing on the Online Archive Kelsey Bawel

Databases & Data Infrastructure. Kerstin Lehnert

CAPITAL REGION GIS SPATIAL DATA DEMONSTRATION PROJECT

Substantive Change Proposal

Taking Forward The Curl Vision: The Year s Highlights

Creating Geospatial Metadata. Kim Durante Geo4Lib Camp

Database of the Mines and Prospects of Idaho

Content Standard for Digital Geospatial Metadata Workbook (For use with FGDC-STD )

Development of Enhanced Feature Recognition Software for the Extraction of Mine Features from USGS Topographic Maps

National Geothermal Data System and Global Geosciences Data Integration

Central data archive (CDA)

How To Write An Inspire Directive

Encoding Library of Congress Subject Headings in SKOS: Authority Control for the Semantic Web

Spatial Information Data Quality Guidelines

Government & Heritage Library State Library of North Carolina

Transcription:

Best Practices for Geospatial Metadata Creation for MWDL Cultural Heritage Digital Repositories Final Report of the Mountain West Geospatial Discovery Task Force July 2015 FINAL DRAFT SUBMITTED FOR APPROVAL BY THE UALC DIGITIZATION COMMITTEE July 31, 2015

MWDL Geospatial Discovery Task Force members Co-Chairs Kristen Jensen, Utah Department of Heritage and Arts Liz Woolcott, Utah State University Merrill-Cazier Library Phase One Contributors Phase Two Contributors Phase Three Contributors Anna Neatrour, Mountain West (Team Lead) Michelle Olsen, Snow College, Richfield Campus Library (Team Lead) Liz Woolcott, Utah State University Merrill-Cazier Library (Team Lead) Sowmya Athithan, Utah Valley University Greta Bahnemann, Minnesota Devin Becker, University of Idaho Library Bert Granberg, Utah Automated Geographic Reference Center Kristen Jensen, Utah Department of Heritage and Arts Robyn Keeling, Utah Geological Survey Library Ray Matthews, Utah State Library Sandra McIntyre, Mountain West Paula Mitchell, Southern Utah University Sherratt Library Jeremy Myntti, University of Utah Ken Rockwell, University of Utah Christian Sarason, OCLC Silvia Southwick, University of Nevada Las Vegas University Libraries Kristen Jensen, Utah Department of Heritage and Arts (Team Lead) Anna Neatrour, Mountain West (Team Lead) Dustin Olson, Utah State University Merrill-Cazier Library (Team Lead) Rachel Wittmann, Clemson University Library (Team Lead) Greta Bahnemann, Minnesota Devin Becker, University of Idaho Library Bert Granberg, Utah Automated Geographic Reference Center Sandra McIntyre, Mountain West Paula Mitchell, Southern Utah University Sherratt Library Jeremy Myntti, University of Utah Heidi Orchard, Utah Department of Heritage and Arts Ken Rockwell, University of Utah Christian Sarason, OCLC Silvia Southwick, University of Nevada Las Vegas University Libraries Liz Woolcott, Utah State University Merrill-Cazier Library Kristen Jensen, Utah Department of Heritage and Arts (Team Lead) Liz Woolcott, Utah State University Merrill-Cazier Library (Team Lead) Greta Bahnemann, Minnesota Scott Eldredge, Brigham Young University, Harold B. Lee Library Ray Matthews, Utah State Library Catherine McIntyre, Utah Valley University Library Sandra McIntyre, Mountain West Jeremy Myntti, University of Utah Anna Neatrour, Mountain West Ken Rockwell, University of Utah Silvia Southwick, University of Nevada Las Vegas University Libraries Rachel Wittmann, Clemson University Library Additional Members Devin Becker, University of Idaho Library Rebekah Cummings, Mountain West Nick Hayen, Mountain West Geri Ingram, OCLC Robyn Krohn, Utah State Library Kinza Masood, University of Utah Becky McKown, Brigham Young University Harold B. Lee Library David Monk, LDS Church History Library Dave Morrison, University of Utah Anne Morrow, University of Utah Elizabeth Perkes, Utah State Archives Matt Pierce, University of Utah Quinney Law Library Jason Roy, University of Minnesota Libraries Amy Rudersdorf, Digital Public Library of America Lorelei Rutledge, University of Utah Gina Strack, Utah State Archives Dorotea Szkolar, former geospatial metadata intern, MWDL Christopher Vinson, Clemson University Libraries Cheryl Walters, Utah State University Merrill-Cazier Library Andy Wesolek, Clemson University Libraries Glee Willis, University of Nevada Reno Libraries MWDL Geospatial Discovery Task Force Final Report Page 1

Table of Contents Executive Summary.. 3 Methodology. 5 Final Recommendations... 6 Recommendations for Standardizing Geospatial Metadata... 6 Future Task Force Activities..... 7 Recommendations for UALC Digitization Committee actions... 7 Appendices... 8 I - Geospatial website and documentation.... 8 II - Meeting minutes and reports.... 8 III - GeoNames Instructions.... 8 MWDL Geospatial Discovery Task Force Final Report Page 2

Best Practices for Geospatial Metadata Creation for MWDL Cultural Heritage Digital Repositories Final Report of the Mountain West Geospatial Discovery Task Force Submitted: July 31, 2015 Approved: Executive Summary In July of 2013, the Mountain West Geospatial Discovery Task Force convened with the purpose of developing a standard format for recording geospatial metadata and developed the following Task Force charge: 1. Identify existing geospatial metadata practices used by Mountain West (MWDL) partners and other digital libraries, as well as other disciplines and organizations. a. Identify areas for potential development and improvement (e.g., key issues and problems) b. Identify easily achievable practices that MWDL partners can implement in the interim before a final recommendation is made. c. Identify examples of map-based search Interfaces, successful and unsuccessful 2. Develop guidelines for MWDL partners to use in standardizing metadata practices to optimize geographically-based discovery of digital resources. a. Suggest steps for addressing key issues and problems b. Recommend revisions to the MWDL Dublin Core Application Profile to accommodate geospatial metadata 3. Develop recommendations and instructions for creating map-based search interfaces or augmenting existing interfaces with map-based search functionality. 4. Identify and share tools related to geospatial metadata and the creation of map-based search interfaces. 5. Create the following deliverables. a. An online bibliography of resources b. Guidelines for MWDL geospatial metadata practices c. Recommendations and instructions for creating map-based search interfaces or search functionality d. Final report on the task force s activities, findings, and recommendations During the course of this process, the task force identified two limitations on the initial charge: MWDL Geospatial Discovery Task Force Final Report Page 3

1. Technical requirements and recommendations for map-based interfaces were beyond the scope of the task force, since they depended too heavily on the type of digital repository used by an institution and not solely on the format of geospatial metadata recorded. 2. Geospatial metadata recommendations would need to focus primarily on place name metadata, since this was the most applicable type of metadata for cultural heritage objects. GIS and geospatial metadata represented as data sets were outside the scope of the majority of content provided by MWDL repositories. The final recommendation of the task force was two-fold: 1) that MWDL partners use the GeoNames database as the primary recommended controlled vocabulary to create a geospatial metadata entry and 2) at minimum, geospatial metadata would present in a hierarchy from smallest entity to largest, with the hierarchy split by commas. For example, Boise, Idaho would be represented as: Boise, Ada County, Idaho, United States Additionally, MWDL partners are highly encouraged to provide the URI following the name hierarchy in order to begin laying the groundwork for future involvement in linked data initiatives. All place name metadata referring to the same place should be separated by commas, only. Semi-colons should only be used to indicate separate and distinct places within the same geospatial field. An example entry for Boise, Idaho would look like this: Boise, Ada County, Idaho, United States, http://sws.geonames.org/5586437/ Additionally, if any institution would like to include latitude and longitude, these coordinates can be included after the place name hierarchy and URI. An example would include: Boise, Ada County, Idaho, United States, http://sws.geonames.org/5586437/, 43.6135, -116.20345 To aid in the creation of geospatial metadata, instructions were developed for using the GeoNames database. These included examples of the construction of geospatial metadata for a variety of place types, and included instructions on how to include multiple geospatial metadata elements, such as the URI and latitude and longitude. Please see Appendix III for a link to the GeoNames Instructions). The full list of recommendations is highlighted in Section 1 of this document. MWDL Geospatial Discovery Task Force Final Report Page 4

Methodology These recommendations were developed over the course of more than two years from the efforts of the Mountain West (MWDL) Geospatial Discovery Task Force. The task force was constituted following the research work of MWDL graduate school intern Dorotea Szkolar in the summer of 2012. Dorotea documented the widely varying practices of the MWDL collections partners in managing geospatial metadata, and described emerging international standards. The task force was formed in July 2013 and was composed of 39 members from MWDL partner repositories and non-mwdl repositories from around the country. The task force operated in three phases. During the first two phases, the task force split into three subgroups that analyzed specific research topics. The first phase was conducted from July through December 2013 and included subgroups that 1) examined Dorotea Szkolar s report on geospatial metadata, 2) developed suggestions for low-hanging fruit or recommendations that could be implemented easily before the final conclusions of the task force, and 3) looked for examples of successful map-based interfaces for digital repositories. The findings were reported to the whole task force and archived on the Mountain West Geospatial Discovery Task Force website. (See Appendix I). The second phase was conducted from January through July 2014 and also split into three subgroups that took the information from the first phase subgroups and researched recommendations further. Those subgroups looked at 1) controlled vocabulary options, 2) formats for recording coordinate information, and 3) the technical specifications for the previously identified successful map-based interfaces. The reports and meeting minutes of these subgroups were recounted to the whole task force and archived at the MWDL Geospatial Discovery Task Force website (see Appendix I). The preliminary findings of the first two phases were reported at several conferences, including the Federation Forum in October 2014. The third and final phase was conducted from January 2015 through July 2015. During this final phase, the task force acted on the recommendations of the previous phase and looked into the analysis of controlled vocabularies. Due to the straightforward nature of the work in the third and final phase, the task force did not split into subgroups. The work conducted during the third phase included selecting the GeoNames database as the recommended controlled vocabulary for MWDL partners and developing instructions on how to format the metadata entry and use the GeoNames database. During the course of this process, several recommendations were made for future task force groups to look at. Section 2 - Future Task Force Activities and Section 3 - Recommendations for UALC Digitization Committee Actions in the recommendation list below outlines possible future tasks to be done. MWDL Geospatial Discovery Task Force Final Report Page 5

Final Recommendations 1. Recommendations for Standardizing Geospatial Metadata 1.1. GeoNames is the preferred geographic database from which to derive controlled vocabulary terms, uniform resource identifiers (URI)s, and latitude and longitude information for metadata creation. 1.1.1. The preferred format for geospatial metadata will follow this pattern: place name hierarchy, URI, Latitude, Longitude, with the place name hierarchy being the minimal accepted format. Examples: Minimal accepted format: Aurora (historical), Mineral County, Nevada, United States Highly recommended format: Aurora (historical), Mineral County, Nevada, United States, http://sws.geonames.org/5499519/ Additional accepted format: Aurora (historical), Mineral County, Nevada, United States, http://sws.geonames.org/5499519/, 38.28714, -118.9007 1.1.2. Place name hierarchy should be presented from smallest to largest, with places spelled out, separated by commas. 1.1.3. Latitude-longitude coordinates should be expressed as decimal degrees, without directional letters ( N, W, etc.), and separated by commas. 1.1.4. When referring to more than one place, place semi-colons only between each unique place while retaining the commas between the elements that describe each place. Example: Aurora (historical), Mineral County, Nevada, United States, http://sws.geonames.org/5499519/; Phoenix, Maricopa County, Arizona, United States, http://sws.geonames.org/5308655/ 1.1.5. Additional geospatial information (such as street addresses) or metadata that needs to be entered in a different order than what is prescribed in 1.1.1 should be placed in unmapped metadata fields. 1.2. A metadata value in a field mapped to the spatial coverage refinement (dcterms:spatial) is recommended for all records harvested by MWDL. The mapping to dcterms:spatial can be done at the collection level. The OAI provider for the repository hosting the collection should support provision of qualified Dublin Core. MWDL Geospatial Discovery Task Force Final Report Page 6

1.3. A metadata value in a field mapped to the spatial coverage refinement (dcterms:spatial) is highly recommended for all records in new collections harvested by MWDL. 1.4. Where converting legacy data may be too difficult, partners can add an additional separate field mapped to the Dublin Core term spatial (dcterms:spatial) with basic, minimal geospatial metadata at least at county or county equivalent (e.g., parish, borough, shire) level, in accordance with GeoNames. 1.5. Since MWDL contributors may need to use varied controlled vocabularies, it is recommended that conformance to these standards be highly recommended but not enforced. Failure to adhere to these standards will not lead to collections being excluded from harvest. However, MWDL and DPLA may not be able to interpret spatial information that is expressed outside the parameters of these standards. 1.6. All standards and practices adopted by the MWDL Metadata Review Board should be compliant with applicable ISO standards for geographic metadata. 2. Future Task Force Activities 2.1. Based off the recommendations for a preferred controlled vocabulary, create actionable plans for Collections Partners and Member Repositories to deal with legacy geospatial data including: 2.1.1. Creating a list of common find-and-replace scenarios that may be useful for all who contribute their collections to MWDL. 2.1.2. Performing a global search-and-replace of simple geospatial metadata with more in-depth formatted spatial metadata when possible. 2.1.3. Having a subgroup look at the top five strategies currently in use by MWDL partners to assign geospatial metadata and estimate what would need to be done to convert legacy data. 2.2. Have a subgroup look at adopting and/or developing a gazetteer of regional place names that are missing from international controlled vocabularies. 2.3. Review the formatting and syntax of Points and Boxes, particularly in regards to the DCMI Box/Point Encoding Schemes. 2.4. Look further into GeoJSON vs. KML for presenting spatial data on map interfaces. 3. Recommendations for UALC Digitization Committee Actions 3.1. Formally revise the MWDL Dublin Core Application Profile element spatial to reflect the above recommendations. MWDL Geospatial Discovery Task Force Final Report Page 7

3.2. As part of MWDL s future work with updating the MWDL Dublin Core Application Profile and General Guidelines for Digital Collections Metadata, MWDL should foster a larger discussion on the topics of subject coverage vs. geospatial coverage, and how the two areas may relate. Appendices Appendix I - Geospatial Website https://sites.google.com/site/mwdlgeospatial/home Appendix II - Reports and Meeting Minutes of the Entire Task Force https://sites.google.com/site/mwdlgeospatial/home/meeting-minutes Appendix III - GeoNames Instructions https://docs.google.com/document/d/1vmey1vpcakfhy0faikugnvavn5s6idxberf1x7ikuoa MWDL Geospatial Discovery Task Force Final Report Page 8