Common PSMFC “data use agreement or policy” Overview of current data sharing in PTAGIS, RMIS, StreamNet.

Slides:



Advertisements
Similar presentations
Installation & User Guide
Advertisements

Peter Griffith and Megan McGroddy 4 th NACP All Investigators Meeting February 3, 2013 Expectations and Opportunities for NACP Investigators to Share and.
The Health Insurance Portability and Accountability Act of 1996– charged the Department of Health and Human Services (DHHS) with creating health information.
UTHSC IRB Donna Hollaway, RN, CCRC 11/30/2011 Authority to Audit 45 CFR (e) An IRB shall conduct continuing review of research covered by this.
NOAA Data Sharing Policy for Grants and Cooperative Agreements Ingrid Guch NOAA Environmental Data Management Committee.
The School of Graduate and Postdoctoral Studies Presentation Title Goes in Here Electronic Thesis and Dissertation (ETD) Topic Submitting.
How To Use NCA’s Online Grant Application System
CRC Protocol Documents Protocol Submissions Amendments Publications Study Closure.
Department of Transportation Support Services Branch ODOT Procurement Office Intergovernmental Agreements 455 Airport Rd. SE, Bldg K Salem, OR
Things To Remember About Completing I-9 Forms
Form I-9 Process An Online Training for Supervisors and Designees Presented by Human Resources Revised November 2009.
Developing a Records & Information Retention & Disposition Program:
Author’s Rights : How to Comply with the New NIH Mandates Lisa McGuire, MLIS Assistant Librarian, Bio-Medical Library February 27, 2008
Social Engineering Jero-Jewo. Case study Social engineering is the act of manipulating people into performing actions or divulging confidential information.
1 NIH PUBLIC ACCESS POLICY Overview Office of Research & Sponsored Programs Compliance Subgroup 1, 2 & 3 Meeting April 1, 2008.
Long-term Archive Service Requirements draft-ietf-ltans-reqs-00.txt.
What forms are required when entering into a Cooperative Agreement or Grant? And where can I find them? Presented by: Christina L. Williams.
How to get your free Windows Store Access
Mandatory Annual ACE Training Fiscal Year 2011 – 2012.
Cobb County School District After School Program Financial and Operational Training APS Directors Monday, July 13,2015.
WHOIS Policy Review Team Interaction with the Community 16 March 2011.
SWIS Digital Inspections Project (SWIS DIP) Chris Allen, Information Management Branch California Integrated Waste Management Board November 5, 2008 The.
EaTIS Vendor Training - FY EaTIS Training for Vendors – Process Overview EaTIS Version 3.01 Last Modified on April 5, 2007.
By: Carol Martineau, Acting Assistant Manager, Aircraft Maintenance Division, AFS-301 Date: June 7, 2015 Federal Aviation Administration ASA Conference.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Documents and Record Control Liu Xue Ning.
RESULTS FRPA s.108 Application November 2010 Presented by Mei-Ching Tsoi
Mandatory Annual ACE Training Fiscal Year 2010 – 2011.
Considerations for Regional Data Collection, Sharing and Exchange Bruce Schmidt StreamNet Program Manager Pacific States Marine Fisheries Commission Presentation.
StreamNet Project Overview for Data Management Category Review Bruce Schmidt Pacific States Marine Fisheries Commission Presented to: NPCC Independent.
Documenting the Participation of Fishing Vessel Crew Members in Alaska’s Commercial Fisheries Documenting the Participation of Fishing Vessel Crew Members.
Division of AIDS Data Interchange. Division of AIDS Data Interchange Agenda.
Event Management & ITIL V3
EPASS - Overview November 2007 eWiSACWIS Production Access Security System.
Online Editorial Management On-line Management of Scholarly Journals Mahmoud Saghaei.
Journalism & Media Studies Graduate Student Culminating Work : Steps for Submitting to the Campus Digital Archive at USFSP November 21, 2011 by Carol Hixson.
MOFEP Data Management. Data & Metadata The main MOFEP page is at To reach the metadata and data upload page from here, click.
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks David Kelsey RAL/STFC,
U.S. Department of the Interior U.S. Geological Survey CDI Webinar Series 2013 Data Management at the National Climate Change and Wildlife Science Center.
DOC Web Policies & Best Practices Jennifer Hammond NOAA Research WebShop 2002 August 7, 2002.
Entry Pathways General Administration April 2012.
How much do you really know?. 1. A student downloads 10 pictures from various Internet sites for his science presentation. On the last slide, he lists.
National Interoperability Information eXchange – – National Public Safety Telecommunications.
SWIS Digital Inspections Project Chris Allen, Information Management Branch California Integrated Waste Management Board August 22, 2008.
NASA TECHNICAL STANDARDS PROGRAM NASA TECHNICAL STANDARDS PROGRAM January 18, 2005http://standards.nasa.gov 1 STANDARDS UPDATE NOTIFICATION SYSTEM (SUNS)
Enterprise Service Desk (ESD) Enterprise Service Desk for Notification / Knowledge Article Authors.
Coordinated Assessments April 3, 2014 Workshop Data Exchange Standard: Overview, Changes, Additions, and Direction Mike Banach PSMFC
The United States Department of Transportation. The United States Department of Transportation Public Access Plan is still under development and is subject.
CTRP User Call May 7, 2014 Gene Kraus CTRP Program Director.
Responsible Data Use: Copyright and Data Matthew Mayernik National Center for Atmospheric Research Version 1.0 Review Date.
Copyright 2010, The World Bank Group. All Rights Reserved. Recommended Tabulations and Dissemination Section B.
Science & Engineering Research Support soCiety Guest Editor Guidelines for Special Issue 1. Quality  Papers must be double -blind.
Connecting for Health Common Framework: the Model Contract for Health Information Exchange Gerry Hinkley com July 18, 2006 Davis Wright.
NCIC VALIDATION PROCESS. Control, Validation, and Other Procedures  Agencies that enter records in NCIC are responsible for their accuracy, timeliness,
VETERANS HEALTH ADMINISTRATION SLIDE 0 New Requirements for VA ORD Investigators: Implementation of Data Management and Access Plans.
Collecting Copyright Transfers and Disclosures via Editorial Manager™ -- Editorial Office Guide 2015.
Copyright 2013 Exostar LLC.| All Rights Reserved.| Proprietary and Confidential1 Identity Proofing Service United Technologies Corporation September 26.
Form I-9 Process Training for Supervisors and Designees Developed by Talent Development & Human Resources Revised April 2013.
The Chest – Supplier Training Information. Website url
Considerations for Regional Data Collection, Sharing and Exchange Bruce Schmidt StreamNet Program Manager Pacific States Marine Fisheries Commission Presentation.
How To Use NCA’s Online Grant Application System.
Instructions for NFBC material request - for RESEARCHERS 1.Login at
1 Auditing Your Fusion Center Privacy Policy. 22 Recommendations to the program resulting in improvements Updates to privacy documentation Informal discussions.
Training for Supervisors and Designees
Referral to Community Support Services
Student Privacy in an Ever-Changing Digital World
REACH 2018 Find your co-registrants and prepare to register jointly.
2-1-1 Automated Verifications
Module 5 Liaison and Managing Relationships with Stakeholders
Fundamental Science Practices (FSP) of the U.S. Geological Survey
Presentation transcript:

Common PSMFC “data use agreement or policy” Overview of current data sharing in PTAGIS, RMIS, StreamNet

Current Status Each project has its own approach. StreamNet Main database and its query systems Data Store RMIS PTAGIS

Current Status StreamNet Main database and its query systems No restrictions in use mentioned. It has always been assumed that only public-domain data are provided. We have a “Citing StreamNet” page that is not integrated with the query systems. It is a best practices “how to” cite Internet resources. It is not prescriptive. Data Store Data set submitters can fill an element in the metadata for “Restrictions or legal prerequisites for accessing and using this data set.” Data set submitters can thus specify anything they like. Attempts to refine this by Bruce Schmidt and then Chris Wheaton. (More later.)

Current Status RMIS No restrictions in use mentioned. It has always been assumed that only public-domain data are provided. Data made freely available day after submittal. Data availability dictated by Pacific Salmon Treaty 1985, 1999, 2009, which states U.S. and Canada will: make “... arrangements for exchange of available data on the stocks...”. “... exchange fisheries statistics and any other relevant information on a current and regular basis...”

Current Status PTAGIS Has formal “Data Use Policy” that was prescribed by the PTAGIS Steering Committee. Link to it is on every web page.

PTAGIS – Data submitters 1.Data contributors recognize and accept that data submitted to PTAGIS are immediately available to anyone who is a registered PTAGIS user. 2.Data contributors should ensure data accuracy to the extent possible prior to submittal. Corrections, if necessary, should be made in a timely manner. 3.All tagging data submitted to PTAGIS are associated with a Tag Data Coordinator (i.e., the person responsible for the data), and all interrogation data are associated with a Site Data Steward. As the Tag Data Coordinator or Site Data Steward, your contact information will be available to data users so you can be contacted regarding your data. 4.All tagging data in the PTAGIS database are assumed to be preliminary until and unless the appropriate Tag Data Coordinator verifies the integrity and application of those data.

PTAGIS – Data users 1.The Data User is expected to contact the appropriate Tag Data Coordinator(s) prior to significant use of data from any release group in any publication or presentation for other than internal distribution. This includes both peer-reviewed and non-reviewed documents. Data users will contact the Tag Data Coordinators in order to: a)Obtain verification and context for data. b)Secure appropriate permissions prior to submission for publication. c)Arrange appropriate acknowledgements, citations and/or authorships.

Draft Data Sharing Agreement and Data Use Policy for the StreamNet Data Store Third DRAFT Background The StreamNet Data Store is a repository for various fish and related data sets collected in the Columbia Basin (and elsewhere) that are not appropriate for inclusion in existing regional or national scale data sets such as StreamNet's main database, the Fish Passage Center, PTAGIS, and EPA's Water Quality Exchange. The Data Store is a viable secure repository for projects that may not have other agency-specific alternatives, and is specifically designed to make data available for sharing. Managers who wish to use the Data Store as a repository should review this draft “Data Sharing Agreement and Data Use Policy” (Agreement) and provide comments if they wish. This Agreement is intended for use with data sets that have passed the provider’s QA and are to be made available to others through a means such as the StreamNet Data Store. Note: there is also a provision for keeping data in draft (not publicly available) form in the Data Store for a limited time. StreamNet Data Store Data Sharing Agreement for those that submit data: Providers should ensure that appropriate metadata, including protocols and citations to individual agencies or tribes, biologists, databases, and reports, are provided when they enter data into the Data Store. Appropriate metadata will help to assure that contributors are properly acknowledged and referenced by data users. Data submitted should be identified with the appropriate metric category selected from the list on monitoring methods.org; So that it can be catalogued properly in the Data Store. Data in the store will be searchable by these subcategories. 1.Data contributors recognize and accept that data submitted to the StreamNet Data Store, once published, are immediately available to anyone who acknowledges the Store’s data use policy. 2.Data contributors should ensure data accuracy to the extent possible prior to submittal. Corrections, if necessary, should be made in a timely manner. 3.All data submitted to the StreamNet Data Store should be accompanied by appropriate metadata, including contact and citation information. As the data contributor, your contact information will be available to data users so you can be contacted regarding your data. Data providers are asked to respond to data publication requests within 90 days. 4.Data in the StreamNet Data Store are assumed to be publicly available (i.e. published”) unless designated as draft on submission. Draft data will not be shared with the public immediately, but will be “published” (i.e. made public) upon notification to StreamNet by the data provider, or one calendar year from the original date of submission, whichever comes first. StreamNet Data Store Data Use Policy for those that use data: The Data User is expected to contact the listed data contributor prior to significant use of data in any publication or presentation. This includes both peer-reviewed and non-reviewed documents. Data users should contact the data contributors in order to: 1.Obtain verification and context for data. 2.Secure appropriate permissions prior to submission for publication. 3.Arrange appropriate acknowledgements, citations and/or authorships. Data Users acknowledge the following; (clicking “yes” gives access to the site) Access, sharing, and use of these data sets is provided with the following understanding. Users should; 1.Acknowledge that data in the StreamNet Data Store may be updated at any time if revised information becomes available. 2.Understand that corrections to data may at times be necessary. Data contributors will strive to make corrections in a timely manner, but are under no obligation to do so. 3.Data contributors, StreamNet, PSMFC, and BPA accept no responsibility or liability for the accuracy of data or for the uses and/or interpretations to which data may be put. 4.Data contributors may have included links to metadata and associated publications that may discuss the limitations and proper use of the data. It is your responsibility to understand and comply with these restrictions if you use data. 5.Data users should be careful to properly credit individuals and agencies when using data, and should follow reputable standards for the use and interpretation of scientific information. 6.Users assume responsibility to determine the usability of the data for their purposes. 7.Before publication; The Data User is expected to contact the appropriate Data Contributor and to maintain a record of contact via and, if necessary, phone prior to significant use of data in any publication in order to: a.Obtain verification, data use limitations and context for data through metadata records. b.Secure appropriate permissions prior to submission for publication by sending requests to data owners and cc’ing the data publishers or peer review team. c.Arrange appropriate acknowledgements, citations and/or authorships. 8.Failure to comply with these expectations may result in restrictions on data sharing in future. Please help to retain open access to data with your cooperation. Upon clicking this acknowledgement, data users will be allowed free access to the published data in the Data Store. Please note that StreamNet will try to design and maintain access to the data for only those that acknowledge, cannot accept any liability or any enforcement function. Any requirements imposed for data sharing by an agency or funding entity are not the purview of StreamNet. Draft SN Data Store User Agreement

Various points PSMFC has no enforcement authority if a data use agreement is ignored. Various projects have different authorities under which they operate. RMIS = BPA a little, international treaty mostly. PTAGIS and StreamNet = BPA SN Data Store data sets not necessarily from BPA projects. RMIS cannot legally restrict their data.

Should the status quo change? Discussion points: Why? What’s the purpose of such a proposal? Who wants it? Is there a problem big enough to bother addressing? What would be the scope of a common approach? SN Data Store; SN database; PTAGIS. RMIS not possible. Is the SN Data Store the only one of interest? If there is no enforcement ability, then what actually changes? What would a new agreement look like?