<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="">
Thank you Jean-Christophe for highlighting the data “Cleaners”. As a former data cleaner, it’s nice to see proper academic recognition.
<div class=""><br class="">
</div>
<div class="">FWIW, we often called ourselves data “wranglers”. I That term has ben somewhat co-opted, but the key point is that data managers need to be embedded in the science and scientist need to be embedded in the data management.</div>
<div class=""><br class="">
</div>
<div class="">See:</div>
<div class=""><br class="">
</div>
<div class="">Parsons, M. A., M. J. Brodzik, and N. J. Rutter. 2004. “Data Management for the Cold Land Processes Experiment: Improving Hydrological Science.” Hydrological Processes 18(18) (18): 3637–53. <a href="https://dx.doi.org/10.1002/hyp.5801" class="">https://dx.doi.org/10.1002/hyp.5801</a>.<br class="">
(Also paywalled, but available on request)<br class="">
<br class="">
<br class="">
<div class="">cheers,</div>
<div class=""><br class="">
</div>
<div class="">-m. </div>
<br class="">
<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; -webkit-line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="text-align: start; text-indent: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
Mark A. Parsons</div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
0000-0002-7723-0950</div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
Senior Research Scientist</div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
Tetherless World Constellation</div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
Rensselaer Polytechnic Institute</div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
<a href="http://tw.rpi.edu" class="">http://tw.rpi.edu</a></div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
+1 303 941 9986</div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
Skype: mark.a.parsons</div>
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;" class="">
mail: 1550 Linden Ave., Boulder CO 80304, USA</div>
<div style="margin: 0px;" class=""><br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br class="Apple-interchange-newline">
<br class="Apple-interchange-newline">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 21 Jun 2018, at 05:00, <a href="mailto:themaintainers-request@lists.stevens.edu" class="">
themaintainers-request@lists.stevens.edu</a> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Send Themaintainers mailing list submissions to<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span><a href="mailto:themaintainers@lists.stevens.edu" class="">themaintainers@lists.stevens.edu</a><br class="">
<br class="">
To subscribe or unsubscribe via the World Wide Web, visit<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>https://lists.stevens.edu/mailman/listinfo/themaintainers<br class="">
or, via email, send a message with subject or body 'help' to<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>themaintainers-request@lists.stevens.edu<br class="">
<br class="">
You can reach the person managing the list at<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>themaintainers-owner@lists.stevens.edu<br class="">
<br class="">
When replying, please edit your Subject line so it is more specific<br class="">
than "Re: Contents of Themaintainers digest..."<br class="">
<br class="">
<br class="">
Today's Topics:<br class="">
<br class="">
1. Re: Recently published article on data cleaners /<span class="Apple-tab-span" style="white-space:pre">
</span>digression<br class="">
on repostiories (Ruth Kitchin Tillman)<br class="">
<br class="">
<br class="">
----------------------------------------------------------------------<br class="">
<br class="">
Message: 1<br class="">
Date: Wed, 20 Jun 2018 10:01:04 -0400<br class="">
From: Ruth Kitchin Tillman <ruthtillman@gmail.com><br class="">
To: themaintainers@lists.stevens.edu<br class="">
Subject: Re: [Themaintainers] Recently published article on data<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>cleaners /<span class="Apple-tab-span" style="white-space:pre">
</span>digression on repostiories<br class="">
Message-ID:<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span><CADLX-Af=Q9dJjvDFp_3tPnk302tw53eruFUTfuy8t8PK_y-uMg@mail.gmail.com><br class="">
Content-Type: text/plain; charset="utf-8"<br class="">
<br class="">
Thanks so much for sharing that, Jean-Christophe! I look forward to reading<br class="">
it. And to cj for the alternative (though luckily I have institutional<br class="">
access).<br class="">
<br class="">
Speaking of preprints, I wanted to note that the London School of Economics<br class="">
and Political Science has a preprint (and, depending on publisher rules,<br class="">
post-print) site where the article could be posted online:<br class="">
http://eprints.lse.ac.uk/ You may already have this in the works,<br class="">
Jean-Christophe. If not this page has the email where you can send your<br class="">
work and further details http://eprints.lse.ac.uk/faq.html<br class="">
<br class="">
I thought I'd email the whole group because I know folks aren't often aware<br class="">
that they have these opportunities available to them and because one of my<br class="">
earliest jobs was as a maintainer tasked with keeping the repository<br class="">
running and finding things to put in it. If you have such a repository, I<br class="">
encourage you to consider putting things in it when possible, as it's a<br class="">
service to those who don't feel comfortable using SciHub and who don't use<br class="">
ResearchGate, etc. Some of you have disciplinary repositories, like arXive<br class="">
and SSRN, which are great alternatives (well, ok now that SSRN is<br class="">
Elsevier-owned).<br class="">
<br class="">
A little on the history of these projects, and of their maintainers. Based<br class="">
on visions from around 2003, that it would be helpful for those in<br class="">
disciplines without the arXiv to also have places to put their publications<br class="">
online -- a number of libraries started building these institutional<br class="">
repositories. When polled, a lot of faculty agreed because... I think we<br class="">
can all agree it's helpful to have freely-available copies of things<br class="">
online, whether the author's accepted manuscript or an actual copy from the<br class="">
journal.<br class="">
<br class="">
The disconnect here was that university and library administrators and<br class="">
others who saw this expected that one could then rely on people to develop<br class="">
a habit of submitting their work to such repositories. So there was a<br class="">
flurry of building them, primarily from around 2005-2011, expecting that<br class="">
"if you build it, they will come." Certainly there was outreach, there were<br class="">
people tasked with metadata cleanup, there was a lot of work done selling<br class="">
benefits to the institution. Imagine if you could visit a single page on<br class="">
such a repository and see every publication put out by your Anthropology<br class="">
department in the last 5 years!<br class="">
<br class="">
But that didn't happen.<br class="">
<br class="">
The literature of "we're doing this!" transformed into the literature of<br class="">
"ok what's wrong?" Issues varied from poor software design and usability<br class="">
issues, administrator fears over accidentally violating copyright and thus<br class="">
complicating submission processes, researcher concerns about the quality of<br class="">
other things submitted to the repository and/or disciplinary disconnects<br class="">
with pre-print submission, and the sheer additional burden of figuring out<br class="">
what's necessary to deposit. Those with most robust pre-print cultures<br class="">
already had places like the arXiv and SSRN (now under publisher control)<br class="">
and had no need to put things in a second place.<br class="">
<br class="">
Library workers were told to find ways to make submission easier. Hence the<br class="">
LSE repository linked above has an email address where you can send the<br class="">
info and the person or people receiving it are probably versed in all the<br class="">
rules around which copy you can use depending on publisher and may fill in<br class="">
the metadata and do all the work of actually putting it online. Other<br class="">
places mostly gave up on soliciting material and just kept the<br class="">
infrastructure up-to-date to prevent hacks.<br class="">
<br class="">
Other places charged library workers with the mind-numbing task of finding<br class="">
out what people at their institution are publishing and just putting the<br class="">
work in the repository (this can generally be done without contact the<br class="">
author or with contacting them with an FYI if the policies are in place).<br class="">
These positions are often filled by librarians fresh from graduate school<br class="">
who have the job of looking for announcements of new publications,<br class="">
searching journal indexers, even looking through CVs. This was my first<br class="">
post-graduate position.<br class="">
<br class="">
Salo's "Innkeeper at the Roach Motel" is perhaps the best take on this<br class="">
whole story https://minds.wisconsin.edu/handle/1793/22088 with her far more<br class="">
biting take of shiny initiatives and mismanagement in the Journal of<br class="">
Librarianship and Scholarly Communication:<br class="">
https://jlsc-pub.org/articles/abstract/10.7710/2162-3309.1075/ If you read<br class="">
Salo's work, you can catch the undercurrent of the emotional harm done to<br class="">
these workers and how it affects them. I admire her for leaving that<br class="">
vulnerability in her writing.<br class="">
<br class="">
My own piece in the JLSC attempted to get a more quantitative look at it,<br class="">
which I wrote primarily so that the people in the situations Salo describes<br class="">
would have the data to understand that it's really not just them. When<br class="">
you're in a position like this, you really need to know that it's not just<br class="">
something wrong with you or your institution. The few places where this has<br class="">
gone "successfully," put in infrastructures which tie it to promotion and<br class="">
tenure and have some form of OA mandate, but a great deal of labor<br class="">
(generally made invisible) goes into ensuring the information submitted by<br class="">
faculty gets transformed into something which can go in repositories<br class="">
https://jlsc-pub.org/articles/abstract/10.7710/2162-3309.2203/<br class="">
<br class="">
I admit I'm sharing the story partly because I hope that making it a<br class="">
narrative vs. just encouraging deposit will mean that it stays in your<br class="">
imagination when you think about sharing your work and where you can put<br class="">
it. Not all of you will have such repositories, of course, but many people<br class="">
I talk to about them are surprised to learn they have one. And while I'm<br class="">
not in that business any more, new librarians on the job market will take<br class="">
more of these positions over the summer and find themselves in this strange<br class="">
world where they're tasked with filling in for the gap between aspiration<br class="">
and practice. I want more people to know that story.<br class="">
<br class="">
And I want you to know that if you volunteer your work to one of these,<br class="">
you'll (probably) cause some maintainer somewhere to have a really good<br class="">
day. You'll give them a day where they know their work is actually<br class="">
sometimes visible. That someone knows that they're making things available<br class="">
online.<br class="">
<br class="">
If you've made it this far, thanks for reading.<br class="">
Ruth<br class="">
-------------- next part --------------<br class="">
An HTML attachment was scrubbed...<br class="">
URL: <http://lists.stevens.edu/pipermail/themaintainers/attachments/20180620/3dc5ec0b/attachment-0001.html><br class="">
<br class="">
------------------------------<br class="">
<br class="">
_______________________________________________<br class="">
Themaintainers mailing list<br class="">
Themaintainers@lists.stevens.edu<br class="">
https://lists.stevens.edu/mailman/listinfo/themaintainers<br class="">
<br class="">
<br class="">
End of Themaintainers Digest, Vol 28, Issue 7<br class="">
*********************************************<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>