<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
All,
<div class=""><br class="">
</div>
<div class="">This seems a good moment to reference GO FAIR's "FAIR Funder Implementation Study" [1], which is intended to address this very idea, by offering an example of an end-to-end "virtuous cycle" of FAIR data (described by FAIR metadata) that is initiated
by the funding agencies.
<div class=""><br class="">
</div>
<div class="">Whether the chosen incentive is "the last slug" of money, or "the next round" of money, might be different for different agencies. But having a robust ecosystem in which it is easy to determine the products of previous funding cycles—and how FAIR
and open those products are—is one of those "everyone wins" exercises, if it can be funded and is executed effectively.<br class="">
<div class=""><br class="">
</div>
<div class="">(Full disclosure, CEDAR [2] is one of the founding technology contributors of this project.)</div>
<div class=""><br class="">
</div>
<div class="">John</div>
<div class=""><br class="">
</div>
<div class="">[1] <a href="https://www.go-fair.org/today/fair-funder/" class="">https://www.go-fair.org/today/fair-funder/</a></div>
<div class="">[2] <a href="https://metadatacenter.org" class="">https://metadatacenter.org</a> <br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Nov 4, 2019, at 7:25 AM, Baru, Chaitanya K. <<a href="mailto:cbaru@nsf.gov" class="">cbaru@nsf.gov</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi Mercury,<br class="">
This is an interesting idea and would, indeed, be interesting to look at what it takes to get this done. You are basically suggesting what I would call "exit criteria" for projects. Projects would not receive that last slug of funding until these criteria are
met, which means of course that there needs to be some sort of review process--which may be a combination of manual and automated, etc.
<br class="">
As you develop your proposal, you may want to keep in mind what is the "burden" on the funding agencies, in terms of reviewing the exit criteria.
<br class="">
<br class="">
Cheers,<br class="">
--chaitan<br class="">
Senior Advisor, Data Science Strategic Initiatives<br class="">
Office of the Vice President for Research<br class="">
San Diego Supercomputer Center<br class="">
Halicioglu Data Science Institute<br class="">
UC San Diego<br class="">
La Jolla, CA 921093<br class="">
<a href="mailto:cbaru@ucsd.edu" class="">Email: cbaru@ucsd.edu</a> <br class="">
<br class="">
<br class="">
On 11/4/19, 12:24 AM, "CODATA-international on behalf of Mercury Fox" <<a href="mailto:codata-international-bounces@lists.codata.org" class="">codata-international-bounces@lists.codata.org</a> on behalf of
<a href="mailto:ceds@email.arizona.edu" class="">ceds@email.arizona.edu</a>> wrote:<br class="">
<br class="">
Hi Anita and All-<br class="">
<br class="">
I am in the early stages of developing a proposal for an institutional<br class="">
review of NSF's award process. I believe that they are currently<br class="">
receptive to this type of review, and support from publishers and the<br class="">
open research community would be very helpful.<br class="">
<br class="">
The solution here is so simple and obvious--tie the money to the data<br class="">
by making it a deliverable--that there must be something seriously<br class="">
dysfunctional in the award process.<br class="">
<br class="">
Funders can just withhold the last 20% (or whatever) of the award<br class="">
until the data, which they paid for, is formatted and posted according<br class="">
to agency guidelines. Then we can forget this nonsense about how to<br class="">
shift community norms toward open research and data sharing, and focus<br class="">
on how to promote and incorporate FAIR principles in those agency<br class="">
guidelines.<br class="">
<br class="">
I think we all know why these simple solutions aren't adopted, and I<br class="">
think that an institutional review would be a good place to start<br class="">
moving past those encumbrances.<br class="">
<br class="">
<br class="">
<br class="">
On 11/3/19, Dewaard, Anita (ELS-HBE) <<a href="mailto:A.dewaard@elsevier.com" class="">A.dewaard@elsevier.com</a>> wrote:<br class="">
<blockquote type="cite" class="">It would actually be very interesting to 'get you started on the publishing<br class="">
industry', Mark!<br class="">
<br class="">
I completely agree with Mercury that 'publishers should be partners in the<br class="">
research ecosystem, not gatekeepers who determine what gets in<br class="">
and what stays out of the sphere of public knowledge': so what should we<br class="">
do, that we're not currently doing, to be the best partners that we can be?<br class="">
<br class="">
<br class="">
Thanks so much for your advice!<br class="">
<br class="">
Best,<br class="">
<br class="">
Anita<br class="">
<br class="">
<br class="">
Anita de Waard<br class="">
Vice President of Research Collaborations<br class="">
Elsevier Research Collaborations Unit<br class="">
71 Hanley Lane, Jericho, VT 05465<br class="">
@anitawaard | +1 (619) 252 8589<br class="">
<br class="">
-----Original Message-----<br class="">
From: CODATA-international <<a href="mailto:codata-international-bounces@lists.codata.org" class="">codata-international-bounces@lists.codata.org</a>><br class="">
On Behalf Of Parsons, Mark<br class="">
Sent: Friday, November 1, 2019 1:56 PM<br class="">
To: Mercury Fox <<a href="mailto:ceds@email.arizona.edu" class="">ceds@email.arizona.edu</a>><br class="">
Cc: Falk Huettmann <<a href="mailto:fhuettmann@alaska.edu" class="">fhuettmann@alaska.edu</a>>; CODATA International<br class="">
<<a href="mailto:codata-international@lists.codata.org" class="">codata-international@lists.codata.org</a>><br class="">
Subject: Re: [CODATA-international] October 2019: Publications in the Data<br class="">
Science Journal<br class="">
<br class="">
<br class="">
I totally agree, Mercury. (Don’t get me started on the publishing industry).<br class="">
I just wanted to give credit to one small program (NSF Arctic) that is doing<br class="">
the right thing, and that other agencies and programs should follow its<br class="">
lead.<br class="">
<br class="">
cheers,<br class="">
<br class="">
-m.<br class="">
<br class="">
<blockquote type="cite" class="">On 1 Nov 2019, at 11:52, Mercury Fox <<a href="mailto:ceds@email.arizona.edu" class="">ceds@email.arizona.edu</a>> wrote:<br class="">
<br class="">
Thanks, Mark--that's a great point. That program's open data policy<br class="">
is stated in the DCL<br class="">
(<a href="https://www.nsf.gov/pubs/2016/nsf16055/nsf16055.jsp" class="">https://www.nsf.gov/pubs/2016/nsf16055/nsf16055.jsp</a>), which also<br class="">
states that the policy is a requirement of international treaty, which<br class="">
probably provides some context for the political will behind the<br class="">
policy in this case. My point is that this kind of clear policy<br class="">
directive shouldn't be a one-off.<br class="">
<br class="">
And since I'm on a soap box about it, I also don't think it's<br class="">
acceptable for NSF & c. to expect the scientific community to simply<br class="">
shift norms and practices in this regard, when the federal funding<br class="">
agencies are unwilling to change the institutional conditions that<br class="">
drive those norms.<br class="">
<br class="">
And another thing... I also think it's inappropriate for them to pass<br class="">
their oversight and quality control duties to the publishing industry,<br class="">
which is basically a roadmap for corruption. I'm not pointing fingers<br class="">
at any specific publisher or agency; but publishers should be partners<br class="">
in the research ecosystem, not gatekeepers who determine what gets in<br class="">
and what stays out of the sphere of public knowledge.<br class="">
<br class="">
OK, that's all the rant I have left in me for today. Thanks everybody<br class="">
and have a great weekend!<br class="">
<br class="">
<br class="">
-Mercury<br class="">
<br class="">
On 11/1/19, Parsons, Mark <<a href="mailto:parsom3@rpi.edu" class="">parsom3@rpi.edu</a>> wrote:<br class="">
<blockquote type="cite" class=""><br class="">
<br class="">
On 1 Nov 2019, at 10:04, Mercury Fox<br class="">
<<a href="mailto:ceds@email.arizona.edu" class="">ceds@email.arizona.edu</a><<a href="mailto:ceds@email.arizona.edu" class="">mailto:ceds@email.arizona.edu</a>>> wrote:<br class="">
<br class="">
they could change the norm overnight by simply tying the policy to<br class="">
the award and requiring open data as a deliverable.<br class="">
<br class="">
For the record, the NSF Arctic Program does just that, and they<br class="">
follow up and do QC, AND they fund an archive to make it possible.<br class="">
<br class="">
cheers,<br class="">
<br class="">
-m.<br class="">
<br class="">
</blockquote>
<br class="">
<br class="">
--<br class="">
Merc Fox<br class="">
Director, CODATA-UA Center of Excellence in Data for Society<br class="">
Data7 + iSchool<br class="">
University of Arizona<br class="">
Tucson, AZ 85721<br class="">
<br class="">
<a href="https://ceds.arizona.edu" class="">https://ceds.arizona.edu</a><br class="">
<br class="">
https://orcid.org/0000-0002-0726-7301<br class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
CODATA-international mailing list<br class="">
<a href="mailto:CODATA-international@lists.codata.org" class="">CODATA-international@lists.codata.org</a><br class="">
http://lists.codata.org/mailman/listinfo/codata-international_lists.codata.org<br class="">
<br class="">
</blockquote>
<br class="">
<br class="">
-- <br class="">
Merc Fox<br class="">
Director, CODATA-UA Center of Excellence in Data for Society<br class="">
Data7 + iSchool<br class="">
University of Arizona<br class="">
Tucson, AZ 85721<br class="">
<br class="">
<a href="https://ceds.arizona.edu" class="">https://ceds.arizona.edu</a><br class="">
<br class="">
<a href="https://orcid.org/0000-0002-0726-7301" class="">https://orcid.org/0000-0002-0726-7301</a><br class="">
<br class="">
_______________________________________________<br class="">
CODATA-international mailing list<br class="">
<a href="mailto:CODATA-international@lists.codata.org" class="">CODATA-international@lists.codata.org</a><br class="">
<a href="http://lists.codata.org/mailman/listinfo/codata-international_lists.codata.org" class="">http://lists.codata.org/mailman/listinfo/codata-international_lists.codata.org</a><br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
CODATA-international mailing list<br class="">
<a href="mailto:CODATA-international@lists.codata.org" class="">CODATA-international@lists.codata.org</a><br class="">
http://lists.codata.org/mailman/listinfo/codata-international_lists.codata.org<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
========================
<div class="">John Graybeal</div>
<div class="">Technical Program Manager</div>
<div class="">Center for Expanded Data Annotation and Retrieval /+/ NCBO BioPortal</div>
<div class="">Stanford Center for Biomedical Informatics Research<br class="">
650-736-1632 | ORCID 0000-0001-6875-5360</div>
<div class=""><br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br class="Apple-interchange-newline">
</div>
<br class="">
</div>
</div>
</div>
</body>
</html>