Archives
-
+
- July 2016 +
- June 2016 +
- May 2016
- April 2016
- March 2016
- February 2016 diff --git a/index.html b/index.html index 2405058..e28f5d6 100644 --- a/index.html +++ b/index.html @@ -47,16 +47,16 @@
- Data
- Social Media diff --git a/posts/2014/dec18.html b/posts/2014/dec18.html index 258a490..03c2c31 100644 --- a/posts/2014/dec18.html +++ b/posts/2014/dec18.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -85,9 +85,9 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2014/nov10.html b/posts/2014/nov10.html index d0fcec7..2920a1c 100644 --- a/posts/2014/nov10.html +++ b/posts/2014/nov10.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -145,6 +145,7 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2014/oct23.html b/posts/2014/oct23.html index 1ca2a47..c904ef9 100644 --- a/posts/2014/oct23.html +++ b/posts/2014/oct23.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -79,9 +79,9 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/apr14.html b/posts/2015/apr14.html index ad0a522..8841e4d 100644 --- a/posts/2015/apr14.html +++ b/posts/2015/apr14.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -83,7 +83,7 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/aug14.html b/posts/2015/aug14.html index 9b85bc9..c60c444 100644 --- a/posts/2015/aug14.html +++ b/posts/2015/aug14.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -102,6 +102,7 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/dec16.html b/posts/2015/dec16.html index ff337c2..d8c5a5c 100644 --- a/posts/2015/dec16.html +++ b/posts/2015/dec16.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -83,9 +83,9 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/feb12.html b/posts/2015/feb12.html index a1fa715..36cbfc3 100644 --- a/posts/2015/feb12.html +++ b/posts/2015/feb12.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -79,24 +79,24 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/jan14.html b/posts/2015/jan14.html index 9cda183..3c8f1ad 100644 --- a/posts/2015/jan14.html +++ b/posts/2015/jan14.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -77,9 +77,9 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/jun2.html b/posts/2015/jun2.html index da8448c..2161665 100644 --- a/posts/2015/jun2.html +++ b/posts/2015/jun2.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -116,6 +116,7 @@ @@ -100,6 +100,7 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/may1.html b/posts/2015/may1.html index f28fe41..34436b3 100644 --- a/posts/2015/may1.html +++ b/posts/2015/may1.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -77,9 +77,9 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/nov20.html b/posts/2015/nov20.html index a957101..bc83770 100644 --- a/posts/2015/nov20.html +++ b/posts/2015/nov20.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -79,12 +79,12 @@ data librarianship.
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/oct10.html b/posts/2015/oct10.html index 4726dbc..dd36046 100644 --- a/posts/2015/oct10.html +++ b/posts/2015/oct10.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -166,6 +166,7 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2015/sep21.html b/posts/2015/sep21.html index 91351eb..dcacf33 100644 --- a/posts/2015/sep21.html +++ b/posts/2015/sep21.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -112,6 +112,7 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2016/apr20.html b/posts/2016/apr20.html index 6ff0747..dfe1846 100644 --- a/posts/2016/apr20.html +++ b/posts/2016/apr20.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -81,12 +81,12 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2016/feb16.html b/posts/2016/feb16.html index acb3437..7df7af9 100644 --- a/posts/2016/feb16.html +++ b/posts/2016/feb16.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -79,9 +79,9 @@
- Monday: Keeping Your Data Safe +
- Monday: Keeping Your Data Safe -
- Tuesday: Organizing Your Data +
- Tuesday: Organizing Your Data -
- Wednesday: Documenting Your Data +
- Wednesday: Documenting Your Data -
- Thursday: Getting Credit for Your Data +
- Thursday: Getting Credit for Your Data -
- Friday: Reusing and Reproducing Your (and others'!) Data +
- Friday: Reusing and Reproducing Your (and others'!) Data
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2016/jan15.html b/posts/2016/jan15.html index 038c9d5..c75ce3a 100644 --- a/posts/2016/jan15.html +++ b/posts/2016/jan15.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -79,7 +79,7 @@
- Research: Currently I’m involved in a few different research projects, all collaborations, across three different domains/topics. I’d really like to finalize and publish at least one of these projects this year into a peer-reviewed, academic journal.
- Reproducibility as Research: I would also like to look at reproducibility more specifically as a research target area. I am really interested in learning more about reproducibility and possible applications or crossover with library services.
- Teaching Me How to Teach: I would love to learn more about teaching and pedagogical theory, as its own entity. While I have certainly taught before, I’ve never attended classes or the like on the actual practice of instruction, evaluating instruction, active teaching, diversity in instruction, etc. I think that I would benefit from taking some workshops on teaching. I’m going to attend at least three of these sessions by the end of the academic year at a minimum. -
- Multimedia Instruction/Outreach: I’m super interested in making short, two-to-five minute videos outlining tools that could be of use in managing data, such as the Open Science Framework, Open ICPSR, converting files to archival formats, etc. I think a varied approach to disseminating RDM information would get us some more love. I would like to complete two of these "how-to" videos by the end of this academic year. +
- Multimedia Instruction/Outreach: I’m super interested in making short, two-to-five minute videos outlining tools that could be of use in managing data, such as the Open Science Framework, Open ICPSR, converting files to archival formats, etc. I think a varied approach to disseminating RDM information would get us some more love. I would like to complete two of these "how-to" videos by the end of this academic year.
- Build Up the Curriculum: I want to expand instructional offerings from three classes a semester to six classes a semester at a minimum, starting in the spring 2016 semester. Approaching the entire RDM lifecycle in one class can be overwhelming to some first-time users. By offering classes that separately address each aspect of the RDM lifecycle (i.e. data creation, data documentation, etc.) it allows for a more in-depth and digestible delivery of information.
- Targeted Outreach: I want to incorporate some more relationship building into my daily workflow. I think that by entering a 1-1 dialogue with certain users would help to disseminate information on RDM services at NYU, and hopefully start a dialogue about RDM and reproducibility leading to some action items within the target group. By the end of this academic year, I will choose one department to make direct inroads with and speak 1-1 with the faculty members of that department. -
- Improving the Libguide: I’m really interesting in building up a corpus of online knowledge base through expanding the LibGuide as much as possible. To accomplish this, every Friday I plan on setting aside an hour to update the LibGuide and add instructional and informational offerings. +
- Improving the Libguide: I’m really interesting in building up a corpus of online knowledge base through expanding the LibGuide as much as possible. To accomplish this, every Friday I plan on setting aside an hour to update the LibGuide and add instructional and informational offerings.
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2016/jul15.html b/posts/2016/jul15.html new file mode 100644 index 0000000..0572787 --- /dev/null +++ b/posts/2016/jul15.html @@ -0,0 +1,149 @@ + + + + + + + + + + + +
- Data
- Social Media @@ -104,6 +104,7 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2016/mar20.html b/posts/2016/mar20.html index a4a65ba..42302c6 100644 --- a/posts/2016/mar20.html +++ b/posts/2016/mar20.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -79,7 +79,7 @@
- July 2016
- June 2016
- May 2016
- April 2016 diff --git a/posts/2016/may15.html b/posts/2016/may15.html index fd6dd1d..29cf0e1 100644 --- a/posts/2016/may15.html +++ b/posts/2016/may15.html @@ -47,16 +47,16 @@
- Data
- Social Media @@ -82,7 +82,7 @@
- Juliana Freire, Professor of Computer Science and Engineering and Data Science; Executive Director, NYU Moore-Sloan Data Science Environment -
- Dennis Shasha, Professor of Computer Science, Courant Institute of Mathematical Sciences, NYU -
- Kyle Cranmer, Associate Professor of Physics, NYU College of Arts and Sciences -
- Fernando Chirigati, PhD Student, NYU Tandon School of Engineering -
- Remi Rampin, Research Engineer, NYU Tandon School of Engineering -
- Margaret Smith, Physical Sciences Librarian, NYU Division of Libraries +
- Juliana Freire, Professor of Computer Science and Engineering and Data Science; Executive Director, NYU Moore-Sloan Data Science Environment +
- Dennis Shasha, Professor of Computer Science, Courant Institute of Mathematical Sciences, NYU +
- Kyle Cranmer, Associate Professor of Physics, NYU College of Arts and Sciences +
- Fernando Chirigati, PhD Student, NYU Tandon School of Engineering +
- Remi Rampin, Research Engineer, NYU Tandon School of Engineering +
- Margaret Smith, Physical Sciences Librarian, NYU Division of Libraries
- "Your science doesn't belong to you" -- this one got a lot of attention from the researchers in the room... @@ -152,7 +152,7 @@
The Library kicked off the party season this year, with probably 50+ people eating and drinking in the reading room (it’s only one night of the year, librarian friends who are cringing!) as the night went on. This was a great opportunity for me to better get to know many of the scientists that I've interviewed for my NDSR project in a more informal environment.
-Friday the 12th was the day of the physical sciences party. Since it’s one of the better slots for parties, the Rose Center was absolutely packed. What usually sets the physical sciences party apart from others is the high probability of seeing some science celebrities, since it is held in the same wing as Neil deGrasse Tyson’s office.
+Friday the 12th was the day of the physical sciences party. Since it’s one of the better slots for parties, the Rose Center was absolutely packed. What usually sets the physical sciences party apart from others is the high probability of seeing some science celebrities, since it is held in the same wing as Neil deGrasse Tyson’s office.
-For me, the first celeb sighting of the night was Bill Nye the Science Guy! I walked by Neil deGrasse Tyson’s office on the way to the bar/food room, and looked in hoping for a quick look look at NDT himself, and to assess the number of people at the party. To my surprise, I saw Bill Nye in there dancing!! I promptly freaked out to my boss but kept moving as the office was way too crowded for me to get in.
+For me, the first celeb sighting of the night was Bill Nye the Science Guy! I walked by Neil deGrasse Tyson’s office on the way to the bar/food room, and looked in hoping for a quick look look at NDT himself, and to assess the number of people at the party. To my surprise, I saw Bill Nye in there dancing!! I promptly freaked out to my boss but kept moving as the office was way too crowded for me to get in.
Me & Billy Nye the Science Guy!! Childhood made.
@@ -116,6 +116,7 @@Archives
-
+
Archives
-
+
Science: The Final Frontier
-Science: the final frontier. These are the voyages of Vicky Steeves. Her nine-month mission: to explore how scientific data can be preserved more efficiently at the American Museum of Natural History, to boldly interview every member of science staff involved in data creation and management, to go into the depths of the Museum where none have gone before.
+Science: the final frontier. These are the voyages of Vicky Steeves. Her nine-month mission: to explore how scientific data can be preserved more efficiently at the American Museum of Natural History, to boldly interview every member of science staff involved in data creation and management, to go into the depths of the Museum where none have gone before.
-Hi there. Digital preservation of scientific data is criminally under-addressed nationwide. Scientific research is increasingly digital and data intensive, with repositories and aggregators built everyday to house this data. Some popular aggregators in natural history include the NIH-funded GenBank for DNA sequence data and the NSF funded MorphBank for image data of specimens. These aggregators are places where scientists submit their data for dissemination and act as phenomenal tools for data sharing, however they cannot be relied upon for preservation.
+Hi there. Digital preservation of scientific data is criminally under-addressed nationwide. Scientific research is increasingly digital and data intensive, with repositories and aggregators built everyday to house this data. Some popular aggregators in natural history include the NIH-funded GenBank for DNA sequence data and the NSF funded MorphBank for image data of specimens. These aggregators are places where scientists submit their data for dissemination and act as phenomenal tools for data sharing, however they cannot be relied upon for preservation.
Image taken from AMNH Scorpion Lab homepage.
@@ -117,6 +117,7 @@Archives
-
+
For the Residency itself, all I have left to do is my final report--this is a compilation of my previous reports and analyses with recommendations for storage, management, and preservation of the Museum’s vast scientific collections and research data. These previous reports include: a plan for the length of retention for digital assets, an environmental scan to see what other similar institutions are doing for their data, and an overview of what federal agencies fund AMNH research, and whether those agencies require data management plans or not. All these previous reports will come together to form my recommendations as well as provide the Museum with the information it needs to understand and interpret my recommendations.
- DigiMan from Team Digital Preservation, original video found here: https://www.youtube.com/user/wepreserve
DigiMan from Team Digital Preservation, original video found here: https://www.youtube.com/user/wepreserve
From there, I will take the results of my survey and translate them into functional requirements I believe should be met by the Museum. This will be the final half of the report. What I anticipate taking up the bulk of the report are my findings and analytical work. This is the evidence for my recommendations and must be given the majority of emphasis. Translating my enormous excel sheet of results into nicely graphic'd and verbal will be a task worthy of its two month timeline for sure.
@@ -111,6 +111,7 @@Archives
-
+
Archives
-
+
Last year during NDSR, it seemed like I was giving a presentation at a conference, professional organization meeting, webinar, etc. every other week. It’s been exceptionally restful (well, sort of...) to spend these past 5 months getting to know NYU, my colleagues, the scope of my work, and really just getting a feel for my day-to-day.
-One of the most exciting outputs from my first semester here at NYU has surrounded my work on the Moore-Sloan Data Science Environment (msdse.org). Back in October (link to Oct 2015 post), I wrote about the MSDSE Summit that was held at Suncadia Resort in Washington state. God it was so incredibly beautiful there and I got to do some really cool stuff, but the best thing that happened was definitely meeting Jenny Muilenburg and Erik Mitchell.
+One of the most exciting outputs from my first semester here at NYU has surrounded my work on the Moore-Sloan Data Science Environment (msdse.org). Back in October (link to Oct 2015 post), I wrote about the MSDSE Summit that was held at Suncadia Resort in Washington state. God it was so incredibly beautiful there and I got to do some really cool stuff, but the best thing that happened was definitely meeting Jenny Muilenburg and Erik Mitchell.
-As the three librarians in the MSDSE, we wanted to meet and discuss some of the potential outputs that our Libraries Working Group (which had its first in-person meeting at the Summit!) could produce. One thing that came out of it was our presentation at the Coalition of Networked Information Fall 2015 Meeting in Washington, DC.
+As the three librarians in the MSDSE, we wanted to meet and discuss some of the potential outputs that our Libraries Working Group (which had its first in-person meeting at the Summit!) could produce. One thing that came out of it was our presentation at the Coalition of Networked Information Fall 2015 Meeting in Washington, DC.
There we are! Left to right: Jenny, me, Erik.
@@ -101,7 +101,7 @@ -You can see our slides on the Open Science Framework as well as our recorded presentation, which CNI is graciously hosting on their YouTube and Vimeo channels:
+You can see our slides on the Open Science Framework as well as our recorded presentation, which CNI is graciously hosting on their YouTube and Vimeo channels:
@@ -122,6 +122,7 @@Archives
-
+
code4Lib 2015!
-Hi everyone, this is Vicky reporting from Portland, Oregon! I am here on the west coast for the first time attending code4Lib 2015, and since today is the last day of the conference, I thought I’d give everyone a bit of a report about what went on here.
+Hi everyone, this is Vicky reporting from Portland, Oregon! I am here on the west coast for the first time attending code4Lib 2015, and since today is the last day of the conference, I thought I’d give everyone a bit of a report about what went on here.
First, I want to talk about the format of presentations at code4Lib. It’s absolutely unlike any other conference I’ve ever been too. There are no multiple sessions going at once. Everything is streamlined into one room. Yes--we sat in a room from 9-5pm watching 20 minute presentations, with an hour for lunch and two to three half hour breaks. This sounds really daunting but I have to tell you--it was so refreshing! I’ll talk a little bit more about the actual presentations later on.
-code4Lib also is the first conference I’ve ever been to that takes the idea of explicit consent to heart and offers attendees and presenters ways to opt-in to potential anxiety-triggering events (like being filmed or photographed) rather than opt-out. I find this really progressive and important--other conferences, take note. All presenters had to sign a consent form, and could opt-in to being filmed and live-streamed (find the live stream and archived videos here). Attendees wore red lanyards if they didn’t. You can find a great blog post on explicit consent by code4Libber Tara Robinson here.
+code4Lib also is the first conference I’ve ever been to that takes the idea of explicit consent to heart and offers attendees and presenters ways to opt-in to potential anxiety-triggering events (like being filmed or photographed) rather than opt-out. I find this really progressive and important--other conferences, take note. All presenters had to sign a consent form, and could opt-in to being filmed and live-streamed (find the live stream and archived videos here). Attendees wore red lanyards if they didn’t. You can find a great blog post on explicit consent by code4Libber Tara Robinson here.
Picture taken from the blog mentioned above.
We had an NDSR moment too! Rebecca from the Boston cohort presented on the “horror story” of data loss in LTO tapes at WGBH. It gave everyone in the audience a chill and started some really interesting conversations at break about preservation. It’s especially important because this was the only presentation that focused on digital preservation. I was shocked a conference as techy as code4Lib didn’t include more presentations on digipres, but the presentation are chosen by votes so maybe most attendees didn’t think the other presentations on digipres were relevant. Read more about Rebecca’s presentation here.
+We had an NDSR moment too! Rebecca from the Boston cohort presented on the “horror story” of data loss in LTO tapes at WGBH. It gave everyone in the audience a chill and started some really interesting conversations at break about preservation. It’s especially important because this was the only presentation that focused on digital preservation. I was shocked a conference as techy as code4Lib didn’t include more presentations on digipres, but the presentation are chosen by votes so maybe most attendees didn’t think the other presentations on digipres were relevant. Read more about Rebecca’s presentation here.
- + -
Peggy and Rebecca also participated in the pre-conference PBCore Hackaton! Read more about that here.
+Peggy and Rebecca also participated in the pre-conference PBCore Hackaton! Read more about that here.
The content of the presentations was super diverse and interesting. The conference organizers did a really good job of grouping the presentations by topic so everything flowed really organically from one to the other. Kudos!
-I found that my favorite presentations dealt with actual technical products or services that people had been developing. This was especially interesting to me because of my background in computer science and continued work in the tech-related side of LIS. While there were great presentations on other subjects I’m interested in (management practices and libs & social justice work, to name a few), I found these “meat and potatoes” presentations to be the most eye-opening for me. I had no idea that SASS was something gaining traction in web development, but apparently it’s the next step in web aesthetics. It’s basically a cleaner version of CSS that compiles into CSS--the best part for me: you can have variables instead of duplicates in your code! No more will my web pages have CSS that reads: +
I found that my favorite presentations dealt with actual technical products or services that people had been developing. This was especially interesting to me because of my background in computer science and continued work in the tech-related side of LIS. While there were great presentations on other subjects I’m interested in (management practices and libs & social justice work, to name a few), I found these “meat and potatoes” presentations to be the most eye-opening for me. I had no idea that SASS was something gaining traction in web development, but apparently it’s the next step in web aesthetics. It’s basically a cleaner version of CSS that compiles into CSS--the best part for me: you can have variables instead of duplicates in your code! No more will my web pages have CSS that reads:
body{background-color:#222930;color:#E9E9E9;} *scroll down about 100 lines* @@ -106,12 +106,12 @@@color: #E9E9E9;that can be instantiated anywhere I want it! I can change one value instead of one thousand! Mind=blown. -Other tech touched upon library tools that make jobs as techy-librarians easier. Like the presentation on packer.io. Packer.io is a tool for creating identical machine images for multiple platforms (Docker, VMWare, VirtualBox, etc), all from a single source configuration. The presenters gave the example of an Islanadora install. There are a lot of software dependencies that comes with the install and it is a really convoluted and intense process. If you want to put this on another computer, it would require you to do that whole install all over again. With packer.io, there are no more crazy software stacks. You just “clone” the first computer and boot up the second one with the system image disk. Boom. Just one config.
+Other tech touched upon library tools that make jobs as techy-librarians easier. Like the presentation on packer.io. Packer.io is a tool for creating identical machine images for multiple platforms (Docker, VMWare, VirtualBox, etc), all from a single source configuration. The presenters gave the example of an Islanadora install. There are a lot of software dependencies that comes with the install and it is a really convoluted and intense process. If you want to put this on another computer, it would require you to do that whole install all over again. With packer.io, there are no more crazy software stacks. You just “clone” the first computer and boot up the second one with the system image disk. Boom. Just one config.
It’s scriptable so that builds can be automated and it’s API is extendable to make it work with just about anything. This is such an awesome tool and I’m so glad I got to hear someone speak on it in detail. It could definitely have some possibilities at the AMNH. You can see the full line-up of presentations here, many of which have the slides attached.
+-
A slide from a presentation on packer.io. The rest of the slides here & info on packer.io here.
A slide from a presentation on packer.io. The rest of the slides here & info on packer.io here.
Portland has also been a blast to explore. As my first introduction to the west coast, its basically everything I thought it would be: Williamsburg if Williamsburg were a huge city. It was filled with trendy thrift shops, tiny hole-in-the-wall music and tea shops, and a population dressed in the finest worn leather jackets and combat boots. Everyone is really friendly and willing to help when tourists (read: me) get hopelessly lost. The city even gave me a sign post to make getting home easier: @@ -130,7 +130,7 @@
Today I am going to continue my exploration by adding Powell’s City of Books (apparently, the Strand of Portland) and a cat cafe called Purrington’s Cat Lounge to my list of visited places in Portland. Though I’m sad the conference is over, I’m glad I had the opportunity to both explore a new city and to speak with other techy-librarians and get to see what such a diverse population of institutions are doing to contribute to the management, organization, and storage of digital assets. Needless to say, I’ll be back next year to explore a (hopefully) new city and new conference materials.
-PS. As an aside, I thought this was quite funny: after the two people live-tweeting the event, I am the person tweeting the most about the con! How weird...BUT everyone can access the #c4l15 twitter archive here if they want to see what everyone’s been tweeting about!
+PS. As an aside, I thought this was quite funny: after the two people live-tweeting the event, I am the person tweeting the most about the con! How weird...BUT everyone can access the #c4l15 twitter archive here if they want to see what everyone’s been tweeting about!
Archives
-
+
Library Advocacy
-Everyone reading my posts must be saying, “Damn, this girl is obsessed with proving the value of the library! We get it already!” Blame Jim Matarazzo, my corporate libraries professor back at Simmons. He really drilled it into my head that if a library can’t prove that it’s worth having, it will be the first thing cut from a budget. And it scared me into constantly thinking about it. Thanks, Jim!
+Everyone reading my posts must be saying, “Damn, this girl is obsessed with proving the value of the library! We get it already!” Blame Jim Matarazzo, my corporate libraries professor back at Simmons. He really drilled it into my head that if a library can’t prove that it’s worth having, it will be the first thing cut from a budget. And it scared me into constantly thinking about it. Thanks, Jim!
-In my last NDSR-NY post, I described how the needs assessment survey can be utilized to show value on an institutional level, in the setting of meetings with business operatives and institutional leaders. In my blog post for the SIGNAL, I wrote about how programs like NDSR can prove their value on an interdisciplinary level as well as to the LIS field.
+In my last NDSR-NY post, I described how the needs assessment survey can be utilized to show value on an institutional level, in the setting of meetings with business operatives and institutional leaders. In my blog post for the SIGNAL, I wrote about how programs like NDSR can prove their value on an interdisciplinary level as well as to the LIS field.
In this post, I’m going to discuss the day-to-day bias that libraries and librarians face within their user groups. It’s something I’ve dealt with as the resident at the AMNH, and as such I’ve had to do a lot of advocacy work at the “ground level.” With librarians becoming increasingly digitally proficient and offering new digital services, a common question many face is: “Why is the library doing this? Isn’t this an IT thing?”
@@ -93,7 +93,7 @@
Image from Adra
Nor should librarians work solely in analog materials anymore. With so much born-digital material being created daily, we need to be involved in its organization and management or data loss is a big concern. This interview with Sibyl Schaefer in the SIGNAL paints this idea perfectly; she says “we don’t all need to be digital archivists, but we do need to be archivists who work with digital materials.”
+Nor should librarians work solely in analog materials anymore. With so much born-digital material being created daily, we need to be involved in its organization and management or data loss is a big concern. This interview with Sibyl Schaefer in the SIGNAL paints this idea perfectly; she says “we don’t all need to be digital archivists, but we do need to be archivists who work with digital materials.”
We need to help cultivate a culture that trusts librarians with both analog and digital materials. Libraries are a service, and as such we as librarians need to make known and understood the services we offer. This is done usually through interpersonal communication, in email, phone, text, IM, or face-to-face. Each of these interactions provide the librarian a great opportunity to explain why the services they and the library offer are only available through them. A few sentences here and there spawn larger conversations where we can continue to prove our knowledge and worth as digitally proficient staff. From there, institutional culture and indeed, wider stereotypes of librarians as stodgy old women can finally, finally end.
@@ -111,6 +111,7 @@Archives
-
+
Archives
-
+
So you've decided to apply to NDSR....
-Applications to the 2015-16 National Digital Stewardship Residencies in New York are open! The deadline to apply has been extended by two weeks, to Friday, May 22! Woo! As if you needed more good news than that, METRO also recently announced the host institutions for this round of residencies, and they’re very exciting (like we’d probably compete with you for them if we could!). You can learn all about them and their projects here.
+Applications to the 2015-16 National Digital Stewardship Residencies in New York are open! The deadline to apply has been extended by two weeks, to Friday, May 22! Woo! As if you needed more good news than that, METRO also recently announced the host institutions for this round of residencies, and they’re very exciting (like we’d probably compete with you for them if we could!). You can learn all about them and their projects here.
-As the the current cohort round the corner and bring their 2014-15 residencies into the home stretch, we’re frequently asked for our advice to prospective Residents, those of you considering applying to the program (most important advice: do it!). We touched on some of these themes in our most recent interview with METRO. Here, in the meantime, are our summary responses to those questions most frequently asked of us live and online:
+As the the current cohort round the corner and bring their 2014-15 residencies into the home stretch, we’re frequently asked for our advice to prospective Residents, those of you considering applying to the program (most important advice: do it!). We touched on some of these themes in our most recent interview with METRO. Here, in the meantime, are our summary responses to those questions most frequently asked of us live and online:
How did you approach the video portion of the NDSR application?
@@ -91,7 +91,7 @@Karl: I followed Julia’s and Shira’s general approaches to creating the video, but in terms of what I wanted it to actually achieve for me, I focused on making it the best possible representation of who I am and how I like to communicate--especially when challenged to speak on such a complicated topic in a short time frame. I can’t stress heavily enough just how many directions you could take that in your own case, and therefore how beneficial it is to be yourself and make it your own.
-Vicky: To be honest, I totally winged it. My boyfriend’s twin sister has a degree in photography with a concentration in film (big thank you to Zoë Catalano!), so after a double shift at the restaurant I was working at, I went to their house to film. It was nice that she had an HD camera and editing abilities, so the actual quality of the video was very good. As for the content, I didn’t practice or write a script, I just got in front of the camera and tried to focus on the reasons why I am interested in digital preservation, and then focused it onto the project at the AMNH--because I really, really, wanted that one. That being said, tailoring it so specifically probably isn’t a good idea...but for me in this one instance, it really worked. I agree with Peggy--think of it as a video cover letter.
+Vicky: To be honest, I totally winged it. My boyfriend’s twin sister has a degree in photography with a concentration in film (big thank you to Zoë Catalano!), so after a double shift at the restaurant I was working at, I went to their house to film. It was nice that she had an HD camera and editing abilities, so the actual quality of the video was very good. As for the content, I didn’t practice or write a script, I just got in front of the camera and tried to focus on the reasons why I am interested in digital preservation, and then focused it onto the project at the AMNH--because I really, really, wanted that one. That being said, tailoring it so specifically probably isn’t a good idea...but for me in this one instance, it really worked. I agree with Peggy--think of it as a video cover letter.
What does good preparation for the residency look like? How did you do it?
@@ -99,7 +99,7 @@Vicky: Keep up with the profession--librarians and archivists of all types are super active on Twitter, listservs, LinkedIn--you name it, we’re on it. Read the blogs, read the articles, and stay up to date with the latest developments in the field. This will put you ahead.
-Shira: What Vicky said. Read widely, read closely, and in particular read the standards. During your residency it will be crucial to be able to explain the high-level digital preservation concepts within OAIS, TDR, etc., in layman’s terms, and so making sure you’re familiar with these documents is essential.
+Shira: What Vicky said. Read widely, read closely, and in particular read the standards. During your residency it will be crucial to be able to explain the high-level digital preservation concepts within OAIS, TDR, etc., in layman’s terms, and so making sure you’re familiar with these documents is essential.
Julia: While I agree with what everyone else has said, I also want to stress that it depends. Each fellowship is different. I don’t think the fellows would be interchangeable on each other’s projects. For example, my thesis work in digital forensics applications to archives and my week long “Born-Digital Forensics” course at the Maryland Institute of Technology Humanities in Learning and Teaching all helped prepare me specifically for some of the challenges at NYU and made it much easier to hit the ground running with my project to start my acquisition workflows and documentation.
@@ -117,7 +117,7 @@Julia: My relationship with my mentor. While I don’t necessarily see or work with him on a daily or even every-other-day basis, if we didn’t agree on how to prioritize and focus my energies this project might not have worked out. Luckily, he’s given me a lot of flexibility to explore the issues that I think are interesting, like emulated access to complex media, while also giving me support when I get stuck, run out of ideas, and just need some help. I’ve also been super lucky in that we’ve been able to collaborate on talks and papers together.
-Karl: I’ll agree with Julia and say that it’s all about relationships. To the success of my project, it was definitely more important that I could work and communicate effectively among geographically (and hierarchically) dispersed teammates than that I had any particular experience with software, metadata schemas, or scripting languages. Those are useful only insofar as you can gain and sustain buy-in for your work, and yes, having an engaged and engaging mentor in your corner can make all the difference there.
+Karl: I’ll agree with Julia and say that it’s all about relationships. To the success of my project, it was definitely more important that I could work and communicate effectively among geographically (and hierarchically) dispersed teammates than that I had any particular experience with software, metadata schemas, or scripting languages. Those are useful only insofar as you can gain and sustain buy-in for your work, and yes, having an engaged and engaging mentor in your corner can make all the difference there.
Peggy: I will also add that taking advantage of the cohort model of NDSR is incredibly important. By that I mean utilizing this built in support network of residents going through a very similar experience to you. I’ve found it so helpful to discuss problems and questions with the other residents, especially at the beginning of the program when you may be more hesitant to ask a lot of questions at your institution (even though, of course, you totally should! But I understand the hesitancy when you’re just starting somewhere). The other residents will probably be going through a lot of the same stuff you’re going through and be very grateful for someone to talk about it with.
@@ -136,6 +136,7 @@Archives
-
+
My First LITA
- A few weeks ago, I attend the Library Information Technology Association’s Forum. Over the 13-15th, I attended several sessions, explored Minneapolis for the first time, and met some really awesome people. I was, as always, a bit nervous attending a new conference but the organizers had some really great 101-type sessions, and even set up a Slack channel which I found to be immensely helpful throughout the day. People organized dinners, discussed sessions in real-time, posed questions, and uploaded some hysterical gifs.
+A few weeks ago, I attend the Library Information Technology Association’s Forum. Over the 13-15th, I attended several sessions, explored Minneapolis for the first time, and met some really awesome people. I was, as always, a bit nervous attending a new conference but the organizers had some really great 101-type sessions, and even set up a Slack channel which I found to be immensely helpful throughout the day. People organized dinners, discussed sessions in real-time, posed questions, and uploaded some hysterical gifs.
- Image from Metro UK.
+Image from Metro UK.
-The first session I attended cemented to me that this conference is 1000% worth attending. Jason Casden talked about the state of open source software in the LIS community and why we are falling short of creating what he called “mature” software. He began this discussion by commending libraryland for creating and publishing a lot of open source software, but there was the big essential caveat: it has to be maintained. This becomes an issue when other institutions want to use your software, but lack prerequisite knowledge--the point is, the software is ECONOMICALLY free to obtain, but requires labour and some prerequisite hardware or software configurations you may not have and may not be free.
+The first session I attended cemented to me that this conference is 1000% worth attending. Jason Casden talked about the state of open source software in the LIS community and why we are falling short of creating what he called “mature” software. He began this discussion by commending libraryland for creating and publishing a lot of open source software, but there was the big essential caveat: it has to be maintained. This becomes an issue when other institutions want to use your software, but lack prerequisite knowledge--the point is, the software is ECONOMICALLY free to obtain, but requires labour and some prerequisite hardware or software configurations you may not have and may not be free.
He went into some really cool discussion about the open source community in general, of course starting with Richard Stallman and his ideas on developing standardized methods of delivering software and on creating "ideologically free software."
@@ -98,7 +98,7 @@ data librarianship.Again, the open source movement is super important and no disrespect to the developers spending their time creating amazing community resources. But the idea is that our field should spend some time thinking, deliberating, and creating tools that are easier to install, maintain, and evaluate.
- 2011-2012 ALA Public Library Funding & Technology Access Study
+2011-2012 ALA Public Library Funding & Technology Access Study
To help, Jason discussed some reasonable task performance metrics that we can apply to our own open source projects. We ideally should meet an 80% threshold of usefulness for software based on these key characteristics, assessed together using the same user group for each one, and using the same success rate for each one:
@@ -113,25 +113,25 @@ data librarianship.-
Another amazing session I attended at LITA was all about "Collaborating to Deliver Better Data Management Services" from Brianna Marshall, the lead in Research Data Services at University of Wisconsin, Madison, and Kristin Briney, the Data Services Librarian at University of Wisconsin, Milwaukee. This session focused on some really cool actionable stuff for me to take home to New York, as Nick and I begin to think on some greater outreach campaigns for the research data management services we provide.
+Another amazing session I attended at LITA was all about "Collaborating to Deliver Better Data Management Services" from Brianna Marshall, the lead in Research Data Services at University of Wisconsin, Madison, and Kristin Briney, the Data Services Librarian at University of Wisconsin, Milwaukee. This session focused on some really cool actionable stuff for me to take home to New York, as Nick and I begin to think on some greater outreach campaigns for the research data management services we provide.
- ~Go fighting Badgers~ Image from the UW Athletics page.
+~Go fighting Badgers~ Image from the UW Athletics page.
The two started off respectively discussing the environments at their own institutions. At UW-Madison, a research institution that spends about $1.1 billion in research spending, the focus of Research Data Services is mainly education and training, consultations, and support for data management plans. UW-Milwaukee is a Carnegie high research institution ($59mil research spending) with a more demographically diverse population. Their Data Services also include DMP consultations, data management training, and data management consultations.
-Brianna went onto describe her initial framework for everything they did in the past year: increasing awareness, and creating buzz so researchers could see them as a valuable service. The first step was to improve the website for Research Data Services: by providing a useful knowledge hub that had an updated aesthetic, they wanted to convey to users that RDS is a useful, active group. The blog attached to this site has amazingly cute RDM-themed graphics, too!!
+Brianna went onto describe her initial framework for everything they did in the past year: increasing awareness, and creating buzz so researchers could see them as a valuable service. The first step was to improve the website for Research Data Services: by providing a useful knowledge hub that had an updated aesthetic, they wanted to convey to users that RDS is a useful, active group. The blog attached to this site has amazingly cute RDM-themed graphics, too!!
- Image from the RDS website.
+Image from the RDS website.
-Additionally, Brianna started a research data management-themed digest as a way for them to both generate content and push users towards the new and improved RDS website. On this shared news, content, and events. These two were bolstered up by the newly created RDS twitter.
+Additionally, Brianna started a research data management-themed digest as a way for them to both generate content and push users towards the new and improved RDS website. On this shared news, content, and events. These two were bolstered up by the newly created RDS twitter.
-Brianna also discussed two in-person meetings they began this past year: a brown bag talk series and a data information literacy reading group. The first was all about finding really awesome researchers and putting the spotlight on them, loosely surrounding their research data management practices and workflows. The idea here was to capitalize on researcher’s social capital to bring people together to talk about research workflows and management.
+Brianna also discussed two in-person meetings they began this past year: a brown bag talk series and a data information literacy reading group. The first was all about finding really awesome researchers and putting the spotlight on them, loosely surrounding their research data management practices and workflows. The idea here was to capitalize on researcher’s social capital to bring people together to talk about research workflows and management.
The data information literacy reading group had about 12 participants so far, a mix of information literacy librarians, subject librarians, graduate students, library IT, and academic IT. The goal was to essentially explore the intersection between research data management and information literacy--and, create some data management evangelists on the way! This group had monthly notes as well as a teaching and learning forum talk.
-At UW-Milwaukee, Data Services was really prompted by the 2011 NSF requirement for the inclusion of data management plans with grant applications. Again, the biggest thing at this campus was creating a marketing campaign to get the word out about this new service in the library. Data Services went to faculty meetings, created a partnership with sponsored research, etc. They've put out some sweet videos also like this one below for giving researchers and others some impetus for data managements:
+At UW-Milwaukee, Data Services was really prompted by the 2011 NSF requirement for the inclusion of data management plans with grant applications. Again, the biggest thing at this campus was creating a marketing campaign to get the word out about this new service in the library. Data Services went to faculty meetings, created a partnership with sponsored research, etc. They've put out some sweet videos also like this one below for giving researchers and others some impetus for data managements:
@@ -140,19 +140,19 @@ data librarianship.Kristen described her model for Data Services as "playing around in the data sandbox," which I absolutely adored. Their focus is on interdisciplinary programming, trying to train people on skills that cut across all disciplines, so in this spirit they’ve created things like "Data Day!" This was a part of a larger GIS series. They are trying to connect more with digital humanities also by providing support and training on TEI, OpenRefine, and RegEx.
- Find resources on their Data Management Guide
+Find resources on their Data Management Guide
What has been a great advantage for Data Services is their ability to try things, see what works, and possibly fail. Because it's a smaller department than the UW-Madison RDS, they have less people to get things done. For Data Services, this wiggle room has been awesome for them as they build new and kind of experimental services around data and data management.
Lastly, Brianna and Kristen went over the cross-campus collaboration that went on between their departments at Madison and Milwaukee. There were some existing infrastructure that helped them think more holistically about the way that they delivered their services. The UW system is completely connection: there is one system across all the UW campuses for library services. They use Primo and Alma, there is a DPLA Wisconsin hub, so why not one data services? They each had some limited local resources and didn’t want to reinvent the wheel, so the idea is that they can use what each other develops!
- Sharing is caring! Image taken from http://extraimago.com/image/qnu
+Sharing is caring! Image taken from http://extraimago.com/image/qnu
-Perhaps one of the coolest RDM-related things I had ever seen is their one of their joint projects, the Midwest Data Librarians Symposium. Milwaukee hosted and Madison kicked in some money for food and space. They asked a registration fee of $30 for this one day event that centered on all aspects of data librarianship. They had four facilitators who taught in four different sections: teaching data management (focus on lesson planning/curriculum building), curating data, building collaborations, and consulting. What was most exciting was that folks from other states saying they wanted to host it next year!! I really want to do this in New York. The closest thing is The University of Massachusetts and New England Area Librarian e-Science Symposium but I’m wondering if there is an avenue to explore for explicit RDM-type sessions.
+Perhaps one of the coolest RDM-related things I had ever seen is their one of their joint projects, the Midwest Data Librarians Symposium. Milwaukee hosted and Madison kicked in some money for food and space. They asked a registration fee of $30 for this one day event that centered on all aspects of data librarianship. They had four facilitators who taught in four different sections: teaching data management (focus on lesson planning/curriculum building), curating data, building collaborations, and consulting. What was most exciting was that folks from other states saying they wanted to host it next year!! I really want to do this in New York. The closest thing is The University of Massachusetts and New England Area Librarian e-Science Symposium but I’m wondering if there is an avenue to explore for explicit RDM-type sessions.
- Great turnout for the 2015 Symposium! See contents (and original image) here.
+Great turnout for the 2015 Symposium! See contents (and original image) here.
Some future projects for them include providing some liaison librarian training, producing teaching materials for others on RDM, and collecting some cool data that passes through their doors. This involves some more intellectual work, since they have to develop a collection development policy, come up with some metadata recommendations, licensing standards, and think of a role for repository. They also want to formalize these relationships on some state/system level.
@@ -179,6 +179,7 @@ data librarianship.Archives
-
+
Archives
-
+
Archives
-
+
W.O.W.
-So, I kind of am in love with the FORCE conference I just went to. FORCE2016 is the annual conference from an organization called FORCE11 (ha, the year they started the org.). This year, 500 people came from around the world: researchers, librarians, software developers, large scale repositories, open science advocates, and everyone in between. It was not only a very diverse conference in terms of home country and job, but also in the way the conference and program was run.
+So, I kind of am in love with the FORCE conference I just went to. FORCE2016 is the annual conference from an organization called FORCE11 (ha, the year they started the org.). This year, 500 people came from around the world: researchers, librarians, software developers, large scale repositories, open science advocates, and everyone in between. It was not only a very diverse conference in terms of home country and job, but also in the way the conference and program was run.
First, one of the coolest things I have ever seen: in addition to the MULTITUDE of tweets around the event (seriously everyone was so active, it was amazing), they hired a company to take visual notes!! While everything was going on!! Everyone, the gist of their talks, panels, lightning talks, EVERYTHING! Such a great idea and it produced a great visual overview of the con!
Taken from this tweet from Portland Center Stage
+Taken from this tweet from Portland Center Stage
There was a great program of people. I'm going to highlight my two favourites. The first was from Steven Pinker surrounding how absolutely astoundingly convoluted academic writing is, and how it contributes to a toxic publishing culture in academia. The question he examines is: why is SO MUCH communication ineffective? Is it on purpose? Or is it because of what he calls the Curse of Knowledge—the difficulty we all have in imagining what it’s like not to know something we know? Pinker approached this in (duh) a really understandable way -- he is not only articulate himself, but perfectly explains how academic writing has changed over time -- from classic style, where the reader and writer are equals, and the writer is simply trying to provide a window into the world (showing not telling), to the currently popular postmodern/self-conscious style, where the goal is to not seem ignorant about one's own enterprise.
@@ -112,7 +112,7 @@Now, onto the fun stuff: I was able to get on stage!! This session was entitled "Starting Off on the Right Foot with Data Management" and was run by Rebecca Boyles and Danny Kingsley. It was essentially data management and open X debate club!! Goodness it was so fun.
Taken from this tweet from Emily Glenn.
+Taken from this tweet from Emily Glenn.
The 8 of us on stage were split into two teams: the 'For' team and the 'Against' team. We were then given ballons to pop with statements inside, such as: 'Sharing data openly is a waste of time' and others in that vein. We then had to argue, and the audience voted on whose arguments were the strongest. I was on the 'Against' team and we won!! Mostly because we were given a bunch of double-negatives, so we argued for openness and well-managed data.
@@ -133,6 +133,7 @@Archives
-
+
#LYD16 Recap
-This past week, February 8-12th, was Love Your Data Week!! Is there a more perfect holiday for data librarians, especially right before Valentine's Day??
+This past week, February 8-12th, was Love Your Data Week!! Is there a more perfect holiday for data librarians, especially right before Valentine's Day??
-#LYD16 was a social media event coordinated officially by 27 academic and research institutions, of which both NYU Data Services and NYU Health Sciences Library were a part. The idea behind this social media blitz was to raise awareness of research data management and the support/resources for RDM at each individual institution.
+#LYD16 was a social media event coordinated officially by 27 academic and research institutions, of which both NYU Data Services and NYU Health Sciences Library were a part. The idea behind this social media blitz was to raise awareness of research data management and the support/resources for RDM at each individual institution.
Although just under 30 institutions officially were a part of the team, MANY MORE ended up joining the conversation on social media and jumping in, sharing their own thoughts and resources. We saw input from commercial organizations, researchers, faculty members, librarians, non-profits, and even academic journals! It was really great to see a conversation started around data stewardship and the importance of loving your data as much as it loves you!
@@ -96,20 +96,20 @@Each day of the week had it’s own theme where everyone shared tips and tricks, stories, examples, resources, and experts:
-
-
#LYD16 also happened to coincide with the deployment of Nick and I’s ongoing project, Data Dispatch. You’ll see that if you click on the above links, you’ll get directed to posts on this blog! This site is replacing the previous Data Services blog, and has been in the works in one form or another since Nick arrived at Data Services (two weeks after me). The old blog was another avenue for the department to advertise classes, events, or push out the cool link or two. This new platform functions more as a space to show off the cool data that comes through our doors, in addition to the features of the last blog (advertising us, our classes, and services). With this new site, we are hoping to create more of a conversation about data-driven initiatives both here and beyond NYU.
+#LYD16 also happened to coincide with the deployment of Nick and I’s ongoing project, Data Dispatch. You’ll see that if you click on the above links, you’ll get directed to posts on this blog! This site is replacing the previous Data Services blog, and has been in the works in one form or another since Nick arrived at Data Services (two weeks after me). The old blog was another avenue for the department to advertise classes, events, or push out the cool link or two. This new platform functions more as a space to show off the cool data that comes through our doors, in addition to the features of the last blog (advertising us, our classes, and services). With this new site, we are hoping to create more of a conversation about data-driven initiatives both here and beyond NYU.
-Anyway, for #LYD16 Nick and I organized ourselves using our collaborative Open Science Framework project, "Data Management Team Planning." The first thing we did was create a separate wiki page for our #LYD16 planning. On this wiki, we wrote down our social media etiquette. For instance: Vicky will tweet from @nyudataservices, then Nick and Vicky will retweet, or Vicky will instagram this photo and using IFTTT, push it out onto her tumblr. Basically, we set up some basic ground rules for posting during the week. Everything #LYD16!!
+Anyway, for #LYD16 Nick and I organized ourselves using our collaborative Open Science Framework project, "Data Management Team Planning." The first thing we did was create a separate wiki page for our #LYD16 planning. On this wiki, we wrote down our social media etiquette. For instance: Vicky will tweet from @nyudataservices, then Nick and Vicky will retweet, or Vicky will instagram this photo and using IFTTT, push it out onto her tumblr. Basically, we set up some basic ground rules for posting during the week. Everything #LYD16!!
A portion of this page was dedicated to scheduling our social media blasts. We made this editorial calendar so we could coordinate who would be responsible for what during the week. Since the OSF wiki supports the amazing feature of strikethrough, I had a blast crossing things off our list as the week progressed.
@@ -121,14 +121,14 @@
Just one page of many for our #LYD16 images.
-After the fact, we wanted to examine some of the impact that Love Your Data week had on our Data Services social media presence. We captured the tweets using the hashtag #LYD16 via NCapture, a browser extension for NVivo, a qualitative data software from QSR International. This was great because we could perform some network analysis as well as do some basic word-frequency queries, cluster analysis, and mapping if the tweets are geocoded (some but not all are for our #LYD16 dataset!).
+After the fact, we wanted to examine some of the impact that Love Your Data week had on our Data Services social media presence. We captured the tweets using the hashtag #LYD16 via NCapture, a browser extension for NVivo, a qualitative data software from QSR International. This was great because we could perform some network analysis as well as do some basic word-frequency queries, cluster analysis, and mapping if the tweets are geocoded (some but not all are for our #LYD16 dataset!).
In this little chart we made in NVivo, usernames ranked by how often they were mentioned with #LYD16--@nyudataservices and @VickySteeves are in the top 10!
- AND if you all followed our advice, you might have enough points for a nifty RDM Badge to show off to all your friends, followers, and colleagues!
+AND if you all followed our advice, you might have enough points for a nifty RDM Badge to show off to all your friends, followers, and colleagues!
I am definitely a level 4! Which are you?
@@ -146,6 +146,7 @@Archives
-
+
Goals for 2016 & How I'll Make Them Happen
-If you’ve been following this blog for a while, or even took a quick look on my resume page, you'll see I haven't been at my position at NYU for very long. January 3rd marks the fifth month (to the day!) that I've been NYU’s official "Research Data Management and Reproducibility Librarian." There was a bit of an adjustment period where I just spent the majority of my time introducing myself to my colleagues, getting to know what my daily workflow would look like, and brainstorm with Nick about what our services will look like, some good groups for targeted outreach, and what classes we are going to teach as a part of Data Services typical course offerings.
+If you’ve been following this blog for a while, or even took a quick look on my resume page, you'll see I haven't been at my position at NYU for very long. January 3rd marks the fifth month (to the day!) that I've been NYU’s official "Research Data Management and Reproducibility Librarian." There was a bit of an adjustment period where I just spent the majority of my time introducing myself to my colleagues, getting to know what my daily workflow would look like, and brainstorm with Nick about what our services will look like, some good groups for targeted outreach, and what classes we are going to teach as a part of Data Services typical course offerings.
This was all well and good, but since I started in August I missed the goal-setting timeline that is typical for my colleagues. As such, I wanted to make some, and my supervisor in the library thought it would be a good way to measure growth besides. Plus, since I’m pretty early career, setting goals for a measurable outcome was kind of new for something not project based. This was just trying to assess my own growth, not necessarily the growth of a project I’m working on.
@@ -88,39 +88,39 @@-
I have a twofold method to keeping these goals in order and make sure I "get 'er done" (ew sorry for this). The first one is more for the collaborative projects I've listed under these goals, and that's the Open Science Framework(OSF) I mentioned under goal #4.
+I have a twofold method to keeping these goals in order and make sure I "get 'er done" (ew sorry for this). The first one is more for the collaborative projects I've listed under these goals, and that's the Open Science Framework(OSF) I mentioned under goal #4.
-The OSF is a FREE tool created by the non-profit, the Center for Open Science, to integrate with resarchers' daily workflows. Besides allowing for maximum control over data access (with really robust controls for creating labs/collaborators on specific projects, and even more granularly, specific components of specific projects), the OSF helps people document and archive materials from all parts of the research data lifecycle, from study design to data to publication. What's also great is that the OSF is completely open source, which means there is an API and lots of addon features that you can use. My favourites are the Google Drive and GitHub addon (probably because I use it the most), but it also has integration with Amazon S3, Box, Dataverse, Dropbox, Figshare, OSF Storage, Mendeley, and Zotero.
+The OSF is a FREE tool created by the non-profit, the Center for Open Science, to integrate with resarchers' daily workflows. Besides allowing for maximum control over data access (with really robust controls for creating labs/collaborators on specific projects, and even more granularly, specific components of specific projects), the OSF helps people document and archive materials from all parts of the research data lifecycle, from study design to data to publication. What's also great is that the OSF is completely open source, which means there is an API and lots of addon features that you can use. My favourites are the Google Drive and GitHub addon (probably because I use it the most), but it also has integration with Amazon S3, Box, Dataverse, Dropbox, Figshare, OSF Storage, Mendeley, and Zotero.
All my projects listed on OSF, with Nick as my collaborator on almost all.
-Nick and I use the OSF for all our projects for Team RDM in Data Services. We use it to track files in each of our individual, NYU-Google Drive accounts, link in code that we write from our respective GitHubs, and keep metrics open for our public projects as a great boost to our reviews. It's been really useful, also because of the integrated Wiki feature that lets us keep robust to-do lists for each other/our team and allows gives us a space to document explicitly what we have been doing, how we've been doing it, how we are disseminating information, and how we are maintaining all the different aspects of our RDM outreach and instructional work.
+Nick and I use the OSF for all our projects for Team RDM in Data Services. We use it to track files in each of our individual, NYU-Google Drive accounts, link in code that we write from our respective GitHubs, and keep metrics open for our public projects as a great boost to our reviews. It's been really useful, also because of the integrated Wiki feature that lets us keep robust to-do lists for each other/our team and allows gives us a space to document explicitly what we have been doing, how we've been doing it, how we are disseminating information, and how we are maintaining all the different aspects of our RDM outreach and instructional work.
Plus, it's a standardized markup so we can do some cool strikethrough effects and style it like any other Wiki page. As someone who lives for striking out tasks, this was honestly one little tiny feature I just absolutely adored.
Nick and I are super productive, as you can see ;)
-The second one is strangely analog. I always make a plan in my Passion Planner to make sure I keep my behind in gear and keep a big picture focus of all the things I want to get done before August 2016. I'm a proud member of the #PashFam on Facebook and Instagram, and using my Passion Planner I’ve definitely kept up with a lot of goals that may or may not have previously fallen to the wayside. It just has a great interface to goal tracking and accountability that has helped me refine my focus professionally and personally.
+The second one is strangely analog. I always make a plan in my Passion Planner to make sure I keep my behind in gear and keep a big picture focus of all the things I want to get done before August 2016. I'm a proud member of the #PashFam on Facebook and Instagram, and using my Passion Planner I’ve definitely kept up with a lot of goals that may or may not have previously fallen to the wayside. It just has a great interface to goal tracking and accountability that has helped me refine my focus professionally and personally.
Look at all the crossed-off goals and "to-do's!"
Plus, Passion Planner has really great inspiration quotes on each page, along with a “Good Things That Happened” section each week for me to fill out. As a generally negative person, I genuinely feel like this helped to keep me positive and less bogged down in my anxiety. The paper is super thick also so I like to draw with my multi-colored pens to make everything seem just that little bit better.
-Passion Planner works for me because it’s not only a place to keep my schedule, but also a place to doodle, journal, write notes, and do some short and long-term goal setting activities complete with weekly to-do-lists and monthly check-ins. Each week and day have a "Focus" section, where you write in your focus for that week, and then each individual day. As someone who loves to multitask but also loves to plan (almost obsessively loves to plan) this has kept me super on-track for getting things done, especially since there are separate to-do lists on each week for my personal and professional life. I'm kind of obsessed with it. I have like 3 of these in the wings for when I finish this one. What's cool is you can also download it for free as a pdf!
+Passion Planner works for me because it’s not only a place to keep my schedule, but also a place to doodle, journal, write notes, and do some short and long-term goal setting activities complete with weekly to-do-lists and monthly check-ins. Each week and day have a "Focus" section, where you write in your focus for that week, and then each individual day. As someone who loves to multitask but also loves to plan (almost obsessively loves to plan) this has kept me super on-track for getting things done, especially since there are separate to-do lists on each week for my personal and professional life. I'm kind of obsessed with it. I have like 3 of these in the wings for when I finish this one. What's cool is you can also download it for free as a pdf!
- Image from Passion Planner website
+Image from Passion Planner website
Archives
-
+
Data, Science, & Librarians,
Oh My!
+ My thoughts as I navigate the world of data librarianship.
+SHARE Week
+ + +
+ + + +
Archives
-
+
Getting Use Cases is Hard
-One of my big tasks since coming into NYU last August was to work on the ReproZip project. My role is largely outreach and education: I was tasked with teaching ReproZip and general reproducibility principles, gathering use cases in a wider variety of disciplines (when I arrived, the use cases were largely in computer science), and supporting users in general.
+One of my big tasks since coming into NYU last August was to work on the ReproZip project. My role is largely outreach and education: I was tasked with teaching ReproZip and general reproducibility principles, gathering use cases in a wider variety of disciplines (when I arrived, the use cases were largely in computer science), and supporting users in general.
ReproZip kind of blew my mind when I arrived; it's an open source software tool that simplifies the process of creating reproducible experiments. Basically it tracks operating system calls and creates a package that contains all the binaries, files, and dependencies required to reproduce the experiment. A reviewer can then extract the experiment on their own machine using ANY operating system (even if it's different from the original one!!) to reproduce the results. As a librarian, I was like "OH MY GOD. THE DIGITAL PRESERVATION GAME JUST GOT UPPED." Anyway, here's basically how ReproZip works -- in 2 steps:
@@ -93,20 +93,20 @@
-
Rémi Rampin, the current developer of ReproZip, Fernando Chirigati, the former developer, and I created this great GitHub repository called ReproZip Examples, dedicated to showcasing examples and use cases from different domains using ReproZip. We have everything from digital humanities (a history paper used ReproZip!) to archived websites and client-server architecture, to machine learning. It's awesome -- check it out and try to unpack stuff if you want!
+Rémi Rampin, the current developer of ReproZip, Fernando Chirigati, the former developer, and I created this great GitHub repository called ReproZip Examples, dedicated to showcasing examples and use cases from different domains using ReproZip. We have everything from digital humanities (a history paper used ReproZip!) to archived websites and client-server architecture, to machine learning. It's awesome -- check it out and try to unpack stuff if you want!
I'm really advocating hard for libraries to start at least investigating using ReproZip for their digital collections -- there is so much unused potential for this it's actually crazy, which brings us around to the title. Getting use cases is hard.
-In May, Rémi and I will be at the Data and Software and Preservation for Open Science workshop, Container Strategies for Data Software Preservation that Promote Open Science. I'm serving as an external organizer, but the two of us will be doing some extensive work with ReproZip while there.
+In May, Rémi and I will be at the Data and Software and Preservation for Open Science workshop, Container Strategies for Data Software Preservation that Promote Open Science. I'm serving as an external organizer, but the two of us will be doing some extensive work with ReproZip while there.
- Image from the DASPOS website.
+Image from the DASPOS website.
The DASPOS project, NSF funded, "represents a collective effort to explore the realization of a viable data, software, and computation preservation architecture for High Energy Physics (HEP)." But at this point, it's grown FAR beyond HEP -- the workshop so far is slotted to have representation from a variety of fields and professions (like libraries!!).
In addition to a talk/demo during the conference proceedings, Rémi and I are leading three breakout sessions that will allow people to try out ReproZip for themselves, using their research if they brought some. I'm hoping that, with the new ReproZip-Examples, we can get some people at the DASPOS workshop to add their own .rpz packages for us to try and reproduce! This would be the best-case scenario, but it depends a lot on the research of the participants.
-Anyway. I'm really looking forward to learning more about some other containerizing tools like Umbrella and meeting some other folks (hopefully a lot of librarians!!) who are involved in the reproducibility and preservation space. The community doing active tool development in this area seems fairly small, so it'll be great for fostering interoperability having us all in a room.
+Anyway. I'm really looking forward to learning more about some other containerizing tools like Umbrella and meeting some other folks (hopefully a lot of librarians!!) who are involved in the reproducibility and preservation space. The community doing active tool development in this area seems fairly small, so it'll be great for fostering interoperability having us all in a room.
Archives
-
+
NYU Reproducibility Symposium
-My first time organizing a conference-ish thing! I helped to organize the 2016 NYU Reproducibility Symposium which took place May 3, 2016 in the Jacob's room of The Center for Urban Science + Progress. This was an initiative of the The Moore-Sloan Data Science Environment at NYU. We put a call out for lighting talks and demos, and the response we received from the NYU community and beyond was really great! We ended up putting together a fairly diverse schedule packed with folks who work in fields like computer science, psychology, libraries, physics, maths, and more.
+My first time organizing a conference-ish thing! I helped to organize the 2016 NYU Reproducibility Symposium which took place May 3, 2016 in the Jacob's room of The Center for Urban Science + Progress. This was an initiative of the The Moore-Sloan Data Science Environment at NYU. We put a call out for lighting talks and demos, and the response we received from the NYU community and beyond was really great! We ended up putting together a fairly diverse schedule packed with folks who work in fields like computer science, psychology, libraries, physics, maths, and more.
The point of the day was to showcase tools to help make the reproducibility process easy, along with case studies showing how creating reproducible experiments has helped other research groups. We had a great turn out across the MSDSE. Our partners UC Berkeley and University of Washington made up 11% of the registrations and 33% of the speakers.
@@ -101,26 +101,26 @@
A breakdown of the status of those registered for the Symposium. I generated this via Google Forms.
We ended up deviating a bit from the schedule; we had all our lightning talks (with a few coffee breaks and a brown bag lunch) and in place of the breakout sessions in the afternoon, we ended up having a rountable discussion based on the participants vote. We gathered around the table to discuss some hands-on strategies for things like the best way to change the rewards systems to encourage openness and reproducibility (promotion/tenure, publishing, etc.), teaching reproducibility concepts, and culture hacking (thanks to Philip Stark for this one). The last session was a panel, which I unfortunately had to miss to head out to another conference...
+We ended up deviating a bit from the schedule; we had all our lightning talks (with a few coffee breaks and a brown bag lunch) and in place of the breakout sessions in the afternoon, we ended up having a rountable discussion based on the participants vote. We gathered around the table to discuss some hands-on strategies for things like the best way to change the rewards systems to encourage openness and reproducibility (promotion/tenure, publishing, etc.), teaching reproducibility concepts, and culture hacking (thanks to Philip Stark for this one). The last session was a panel, which I unfortunately had to miss to head out to another conference...
A photo I took of our roundtable!
Big props also to my fellow organizers:
-
-
RDAP
-So, I actually had to leave the Reproducibility Symposium early to make my way down to Atlanta, GA for my first ever RDAP Summit! It had a great program stacked with leaders in the field of data management, repository management, and other roles related to researchers and their data. From the RDAP website: "The Summit is relevant to the interests and needs of data managers and curators, librarians who work with research data, and researchers and data scientists. A wide range of disciplines from the life sciences, physical sciences, social sciences, and humanities will be represented. The Summit will bring together practitioners and researchers from academic institutions, data centers, funding agencies, and industry." A lot was covered from a lot of different perspectives--my favourite panel for this was kind of unexpected. Panel 5: "Data Management Plans and Public Access: Agency and Data Service Experiences" had an incredible selection of panelists -- one person from the DOE, one from NSF (division of biological infrastructure), one from NIH, and one librarian at an academic university. I loved this panel because the audience got to hear the status of DMPs right from the source -- the federal agencies. There was a lot of discussion about auditing DMPs, budgeting for RDM, and repositories for data deposit. It was absolutely great.
+So, I actually had to leave the Reproducibility Symposium early to make my way down to Atlanta, GA for my first ever RDAP Summit! It had a great program stacked with leaders in the field of data management, repository management, and other roles related to researchers and their data. From the RDAP website: "The Summit is relevant to the interests and needs of data managers and curators, librarians who work with research data, and researchers and data scientists. A wide range of disciplines from the life sciences, physical sciences, social sciences, and humanities will be represented. The Summit will bring together practitioners and researchers from academic institutions, data centers, funding agencies, and industry." A lot was covered from a lot of different perspectives--my favourite panel for this was kind of unexpected. Panel 5: "Data Management Plans and Public Access: Agency and Data Service Experiences" had an incredible selection of panelists -- one person from the DOE, one from NSF (division of biological infrastructure), one from NIH, and one librarian at an academic university. I loved this panel because the audience got to hear the status of DMPs right from the source -- the federal agencies. There was a lot of discussion about auditing DMPs, budgeting for RDM, and repositories for data deposit. It was absolutely great.
A minor but very important reason for my attendance at this year's RDAP Summit was because I had a poster accepted! My co-author Kevin Read was able to go with me, but our other co-author Drew Gordon had to miss it. We got a lot of interesting questions -- our poster was essentially displaying some work we have done and continue to do to bridge the gaps across the vast NYU campuses and researchers to deliver better and more coordinated data services. Check it out:
@@ -131,16 +131,16 @@DASPOS
-My last conference of May was the Container Strategies for Data and Software Preservation Workshop, a two day workshop organized by the NSF-funded Data and Software Preservation for Open Science (DASPOS) project, hosted at the University of Notre Dame.
+My last conference of May was the Container Strategies for Data and Software Preservation Workshop, a two day workshop organized by the NSF-funded Data and Software Preservation for Open Science (DASPOS) project, hosted at the University of Notre Dame.
-I served as an external organizer, and Rémi & I (we're super cute and have a joint speaker bio) had one large demo + presentation, and then ran three separate breakout sessions, all for ReproZip. ReproZip is an open source software developed at NYU that seeks to lower the barrier of making research reproducible. ReproZip allows researchers to create a compendium of their research environment by automatically tracking programs and identifying all their required dependencies (data files, libraries, configuration files, etc.). After two commands, the researcher ends up with a neat archived package of their research that they can then share with anyone else, regardless of operating system or configuration. These community members can unzip the package using ReproUnzip, and reproduce the findings.
+I served as an external organizer, and Rémi & I (we're super cute and have a joint speaker bio) had one large demo + presentation, and then ran three separate breakout sessions, all for ReproZip. ReproZip is an open source software developed at NYU that seeks to lower the barrier of making research reproducible. ReproZip allows researchers to create a compendium of their research environment by automatically tracking programs and identifying all their required dependencies (data files, libraries, configuration files, etc.). After two commands, the researcher ends up with a neat archived package of their research that they can then share with anyone else, regardless of operating system or configuration. These community members can unzip the package using ReproUnzip, and reproduce the findings.
-@remram44 & I are presenting #ReproZip today @ #DASPOS workshop on container. sci! Lowering the barrier to #repro: https://t.co/3wDCu5XsvE
— Vicky Steeves (@VickySteeves) May 19, 2016
The DASPOS organizers used the Open Science Framework to organize all the conference materials such as notes, presentations, code, videos, whatever people wanted to contribute. For our breakouts, we had a separate ReproZip OSF component to take notes and centralize materials and accompanying GitHub repro where people could deposit any examples or use-cases. And we actually got one! Bertini is a a package for solving polynomial systems, developed at Notre Dame in the math department. The ReproZip package was deposited into our ReproZip OSF con. The depositor has made a great README with instructions and also provided a .rpz package so others can reproduce his work!
+The DASPOS organizers used the Open Science Framework to organize all the conference materials such as notes, presentations, code, videos, whatever people wanted to contribute. For our breakouts, we had a separate ReproZip OSF component to take notes and centralize materials and accompanying GitHub repro where people could deposit any examples or use-cases. And we actually got one! Bertini is a a package for solving polynomial systems, developed at Notre Dame in the math department. The ReproZip package was deposited into our ReproZip OSF con. The depositor has made a great README with instructions and also provided a .rpz package so others can reproduce his work!
-The last day of the workshop I was invited to sit on a panel--which was the last session of the whole thing! Here are some notes summarizing what was said -- ultimately, I went kinda punk rock about reproducibility, as I always do. Some key quotes of mine include:
+The last day of the workshop I was invited to sit on a panel--which was the last session of the whole thing! Here are some notes summarizing what was said -- ultimately, I went kinda punk rock about reproducibility, as I always do. Some key quotes of mine include:
-.@philipbstark 's "hacking the culture" quote has now made its way into all my convos about #reproducibility #quoteparasite
— Vicky Steeves (@VickySteeves) May 19, 2016
The organizers said they would release all the videos, transcripts, and other A/V related materials as soon as possible, which is great. What I love is that DASPOS walks the walk: all the presentations are available for people to look at, download, critique, whatever, along with the rest of the conference materials. Everything was done in the open! We just have to containerize our OSF for Meeting space ;)
+The organizers said they would release all the videos, transcripts, and other A/V related materials as soon as possible, which is great. What I love is that DASPOS walks the walk: all the presentations are available for people to look at, download, critique, whatever, along with the rest of the conference materials. Everything was done in the open! We just have to containerize our OSF for Meeting space ;)