Overview. Overview. Broadsheet for PNAMP Metadata Builder. Metadata Entity Set Information. Taurus Monitoring

Transcription

1 Overview Overview The Metadata Builder Tool aims to facilitate and encourage the development of metadata for aquatic monitoring data collected by government agencies and partners in the Pacific Northwest. To support this goal, the builder tool would collect project level metadata elements from various project tracking systems in the region, as well as other web resources such as MonitoringMethods.org, and integrate these currently disparate elements of a metadata record into one metadata record. While not all elements of a standard metadata record are contained within online systems, the builder would look to maximize efficiencies where the elements do exist. The deliverables from this work include a prototype Metadata Builder Tool and a document describing recommendations for regional application of the Metadata Builder Tool. Customers Natural Resources Management Agencies Bonneville Power Administration Data Consumers (NOAA) Factors for Success Advisory Group PNAMP Metadata Workgroup A successful metadata builder relies on successful web development and programming, metadata content standardization, ease of user interface, utility to the user, and integration with other proposed tools. A scoping exercise for a regional metadata builder tool should focus on all of these perspectives. Once the pilot metadata builder development is complete or near completion, the PNAMP Metadata Working Group and others will discuss these topics and provide recommendations to PNAMP for a more robust regional tool. Scope This task is to conduct a pilot effort that will specifically focus on project tracking systems currently used by BPA (Pisces, Taurus) and PNAMP sponsored systems (MonitoringResources.org). We plan to do a short scoping exercise to review ISO requirements, discuss which are important to BPA, and spend some time reviewing similar existing tools, such as InPort from NMFS. Conduct short scoping exercise specific to BPA to identify metadata ISO requirements; systems that can deliver the information; plan for development Work with a contractor to develop pilot metadata builder application based on existing web services with BPA and PNAMP systems Conduct more expansive scoping exercise to discuss what was learned from pilot effort, value of a more robust regional tool, effort needed to support multiple entities in using a regional tool, additional metadata ISO requirements. A Proof-of-Concept The Metadata Builder will be a prototype aimed at demonstrating a proof-of-concept. The goal is to pull together and re-use information that was entered into various information systems and generated a metadata record that describes a particular dataset. In concept, the creation of a dataset is funded by an organization to meet a defined objective. The objective, rationale, and other descriptive information about the resulting dataset were likely already documented during the proposal and contracting phase. It stands to reason that if, this information were recorded in structured information systems and those systems were accessible, then a tool could be built to accumulate that information into a formal metadata document complainant with national or international standards. Or at minimum, generate a document that includes a significant portion of a complainant metadata document. Bonneville Power Administration (BPA) now requires all contractors to submit proposals through Taurus, to manage and report on contracts in Pisces, and to document methodology in Monitoring Methods. As such, BPA contracts provide an opportunity to test this concept. The challenge will be to align the granularity of the information on contracts and methodology with the scope or extent of monitoring datasets. If the Metadata Builder proves to be an effective and efficient approach to jump starting the creation of metadata, then the tool could be scaled up to incorporate information systems maintained by other regional funding entities. Taurus Monitoring Resources Mapping to The North American Profile of ISO 19115:2003 Metadata Entity Set Information Idenfitication Information (6.2.14) Metadata Constraints (6.2.15) Data Quality Information (6.2.16) Metadata Maintenance (6.2.17) Spatial Representation (6.2.18) Reference System Information (6.2.19) Content Information (6.2.20) Portrayal Catalogue Information (6.2.21) Distribution Information (6.2.22) Application Schema Information (6.2.23) CHaMP Monitoring Pisces Full Document - Page: 1 of 9

2 UI - My Metadata The Metadata Builder will be built as a stand-alone application that consumes web services from other independent information systems. Users will be able to access the tool via a link within Monitoring Resources website or potential through links in other systems. A side bar in Monitoring Resources website will provide a description of the tool and an opportunity to promote the tool within the monitoring community. An initial splash screen will describe the context, scope and future plans for the tool. Search My Metadata Files Searching metadata files will be limited to those files created by the logged in user. The purpose of the Metadata Builder is to create metadata files for submission to regional or national metadata repositories. Therefore the goal of the search functionality is simply to assist the user locate the metadata file they need to edit or submit. Searching will be accomplished using simple text-based grid filters. Viewing options will include both a form-view and XML view. The form-view will be a read-only version of the forms on the following 7 pages. The XML version will be the ISO compliant version of the data. Editing of the metadata file will be performed using a wizard with forms to support seven steps. The following pages each of these steps. When creating a new metadata file, the user will be asked to identify the funding source (for this initial prototype, BPA will be the only option), project number, and protocol. These input parameters will be used to locate the correct information from external sources and prepopulate many of the required fields. Page: 2 of 9

3 UI - Select Project InPort - Title ISO (C) ISO (O) InPort - Maintenance Frequency ISO (O) ISO (M, ) ISO (M) The red astrik at the right edge of data fields indicates a required field. Required fields were determine based on input from the PNAMP DMLT and Russ Scraton at BPA. ISO (M) ISO (M) ISO (M) Page: 3 of 9

4 UI - Contact Info ISO (M) InPort - Support Role ISO (O) ISO (O) ISO (O) ISO (M) ISO (M) ISO (O) ISO (O) ISO (O) ISO (O) ISO (O) ISO (O) ISO (O) ISO (O) Page: 4 of 9

5 UI - Identification Info ISO (M, ) ISO (M) From MM.org protocol Citation InPort - Abstract ISO (M) ISO (O) From MM.org protocol Purpose and Objectives From MM.org protocol Metric Subcategory ISO (M, ) InPort - Keywords ISO (M, ) ISO (M, ) Page: 5 of 9

6 UI - Access Contraints ISO (O, ) From MM.org protocol Key Assumptions ISO (O, ) ISO (O, ) Page: 6 of 9

7 UI - Extent Info From cbfish.org - Work Site InPort - Geographic Area Geographic Area Geographic Area Geographic Area ISO (M) ISO (M) ISO (M) ISO (M) ISO (O) InPort - Geographic Area From cbfish.org - Project Duration InPort - Time Frame ISO (M) ISO (M) Page: 7 of 9

8 UI - Distribution Info InPort - URL ISO (O) ISO (O) ISO (M) ISO (M) ISO (O) Use units attribute to convert Transfer Size value into megabytes From Taurus ISO (O) ISO (O) ISO (O) ISO (O) Page: 8 of 9

9 UI - Share/Export Page: 9 of 9