<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Open Data Literacy - Medium]]></title>
        <description><![CDATA[An education and research project focused on improving the accessibility of open data. - Medium]]></description>
        <link>https://medium.com/open-data-literacy?source=rss----c29559733c9f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Open Data Literacy - Medium</title>
            <link>https://medium.com/open-data-literacy?source=rss----c29559733c9f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:51:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/open-data-literacy" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[COVID Data Collection: Lessons Learned and Future Approaches]]></title>
            <link>https://medium.com/open-data-literacy/covid-data-collection-lessons-learned-and-future-approaches-8bfc3420ec0d?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/8bfc3420ec0d</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[covid19]]></category>
            <dc:creator><![CDATA[Seattle Informationist]]></dc:creator>
            <pubDate>Tue, 23 Jun 2020 22:36:41 GMT</pubDate>
            <atom:updated>2020-06-23T22:36:41.451Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*liDh9c5UJmkqFyLahdDOhw.jpeg" /><figcaption>An image of a checklist that says yes and no.</figcaption></figure><p>This spring, I began an internship with the Washington State Library as part of the Open Data Literacy Project at the University of Washington. The internship had originally focused on crowdsourcing library resource data, but due to the COVID-19 pandemic, I pivoted to tackling the question of how public entities can gather data that are reliable, accurate, and comprehensive in a short period of time, especially in a time of crisis. In a <a href="https://medium.com/open-data-literacy/tracking-washington-state-public-library-responses-in-crisis-60482ea7e080">previous post</a>, I provide an in-depth look at the Washington State Library’s response, as well as an overview of the response of other states. In this article, I will discuss the lessons that were learned through this process, and provide recommendations for future approaches.</p><p>In early 2020, the novel coronavirus spread across the United States, shutting down libraries everywhere from Alaska to Puerto Rico. At least 13 state libraries opted to collect data about COVID impacts, along with several individuals and organizations that have stepped up to collect data nationally. Given the unprecedented circumstances, data collectors often had to work through trial and error. There simply was not the time for planning the perfect data model or collection method — the data were needed, and needed quickly. How quickly datasets appeared (within days) should not come as a surprise — industry research says that some organizations actually <a href="https://info.dataminr.com/hubfs/Reports/1118_Report_A_Survey_of_Real-Time_Data_Collection_in_a_Crisis_Situation.pdf">gauge their success based on the speed of their reactions</a> in crisis.</p><p>With the rise of the pandemic, there was unity in librarians’ approaches. Information was shared quickly, albeit informally, about actions their branches were taking to curb the spread of the virus and protect patrons and employees. When the time for closures began, March 12th in Washington state, information about hours, openings, and closings was distributed. Listservs in the library community got information to others not only locally, but across the country, as well.</p><p>I endeavoured to determine what people should keep in mind when collecting and publicizing data during crisis situations. I read academic literature, and industry publications about both simple data curation as well as crisis data collection. I then gathered information about the data collection approaches of each state library during the COVID-19 pandemic crisis. This included looking at surveys, data dashboards, spreadsheets, blogs, and other reporting of response. This was a total of 18 state library collection efforts, some published on websites and some shared among state data coordinators. I also looked at three independent collections by <a href="https://surveys.ithaka.org/jfe/form/SV_8qN8F2274hMBBBz">ITHAKA</a>, <a href="http://www.ala.org/pla/issues/covid-19/surveyoverview">PLA</a>, and <a href="https://docs.google.com/spreadsheets/d/1vG21vqjeWUyqQNin7QzAoxUBg2UMO8mCgGQ_rhnX2lI/edit?fbclid=IwAR0YK6q1WVoP8b_NwFym6LStGY-l6CSoZAn9ZvvRGbpXBjxpObYo_4L_QN0#gid=0">Travelin’ Librarian</a>. Using my own understanding of data curation and the information pulled from literature, I have developed a series of lessons learned that may be of use in a future crisis collection for public agencies:</p><p><strong>Choose tractability over expressiveness</strong></p><p>This is a difficult item to fulfill, particularly when conditions are changing rapidly and there is no time for a proper evaluation of needs. People tend to opt for gathering the most data possible in order to maximize the chances of catching needed information, however, this adds strain to the curators, collectors, and collection populations, all of which are likely strained by the crisis itself already. The tradeoff between the tractability (how manageable) of data and the expressiveness (how extensive) of data is well-documented in <a href="https://onlinelibrary.wiley.com/doi/abs/10.1111/j.1467-8640.1987.tb00176.x">academic literature</a>, and despite the increased need for information in crisis, this extends to those situations. Many of the crisis data collections I analyzed had between 3 and 30 variables, with the average around 9–10. While there was no link between amount of variables and recency of last update, what I found was that, unfortunately, most of these datasets were not kept up to date; as of this writing (June 1st, 2020), 11 of the 18 reviewed published datasets do not seem to have been updated in the last month, and we know library services have changed since then. While the expansivity of the data when it was timely had a benefit, that benefit has since been lost due to the intractability of it now. In order for the data maintenance to be sustainable and the data as rapidly deployed as one might desire, there need to be limitations to each given dataset.</p><p><strong>Do not expect the stability of information nor resources</strong></p><p>In a crisis, information often changes quickly. Of course most curators anticipate that circumstances will probably change faster than the data can be updated, but in my analysis I have also noticed that several of the library COVID-19 datasets have linked to resources no longer available, no longer in the same location, or with limited access to the public. When linking to or otherwise referencing items such as datasets, web-hosted spreadsheets, websites, or other content, do not expect that they will be stable. Links can break down, items can move, or hosts can delete content. Prepare appropriately by not only monitoring changes, but also consider alternative storage methods. Downloading the resource and storing it locally can allow you to keep track of the resource, but backing up resources to the <a href="https://archive.org/web/">Wayback Machine</a> can also create stability for the resource as long as the format is supported by the archive. Moreover, the Center for Open Science (COS) offers a product called <a href="https://help.osf.io/hc/en-us/articles/360019930893-Register-Your-Project">OSF </a>which allows projects to be registered by their organization with periodic snapshots. This is another option to make your work more stable.</p><p>Additionally, when making decisions about the dataset’s maintenance, decide: will there be a regularly scheduled update, will there be rolling updates immediately with changes, or something else? Moreover, how will you notify data consumers of these changes? Keep in mind, it is possible that not every variable that needs to be monitored will need an update with the same frequency. In some situations items may need to be separated out based on the regularity with which they require updating. My recommendation, for whichever method is chosen, is to at minimum, indicate the date and type of the most recent update somewhere in the dataset, either as its own variable or elsewhere. While it is possible that changes do not occur for long periods of time, giving an indication of when the last time the variable was confirmed lends trust to the data’s current validity.</p><p>Appropriately, your own data are not immune to this, either. There can be server access issues, hardware or storage loss, personnel inaccessibility, software changes, and countless other possible situations where your data could be compromised by people or technology. During a crisis when people fall back on data, particularly that from reputable public agencies, it is critical to protect it from modification or loss.</p><p>It can be difficult to anticipate what might go wrong with data in a crisis. Prepare accordingly by providing contact information of the data curator or manager clearly, on both the collection tool and the data product, whether it be a dashboard, a spreadsheet, or another data object. This opens a channel for feedback, communication of broken links or features, and clarifying questions should something be unclear.</p><p><strong>When or if time allows, consider refining the data for future use</strong></p><p>This may seem to contradict the first lesson, but it is important to consider future use cases when designing, or updating, a dataset. Using the COVID-19 crisis as an example: patrons and librarians may need to know urgently about business hours, services offered, and return deadlines — but what might a future researcher of the effects of COVID-19 need to know in addition to just identification of things that did or did not happen?</p><p>Curating for future use can mean many things, from creating documentation that clarifies the data to making sure the data can be processed by machines. While it is not possible to know every future use of a dataset, particularly one made public, there are some best practices to consider implementing for these purposes. Among them is following “<a href="https://cran.r-project.org/web/packages/tidyr/vignettes/tidy-data.html">tidy data</a>” principles: on the most basic level, this means three things: each variable has its own column, each observation has its own row, and each value has its own cell. This standard allows a tabular dataset to be most easily understood by both people and machines, and limits how much thought needs to go into how to structure a table or spreadsheet. Additionally, something that came up in my analysis is the need to track dates, not just values — this would allow changes to be tracked over the course of the crisis to see how events developed. For example, if a survey were to ask whether a library branch was closed, storing the date value for the closure rather than only a yes/no or other binary value would be more useful while still inherently determining whether or not the branch is closed.</p><p><strong>Keep surveys manageable</strong></p><p>Designing a survey for crisis data collection is a topic of its own, but there are certainly some overarching themes that can guide design in a pinch. First, limit the length of your survey to only what collection is needed, and each survey question only to what is needed for the respondent to respond appropriately. The more short-form the survey can be, the better — however, this does not suggest that a single open response question is best. Pew Research suggests focusing on short sets of closed-ended questions with prepopulated options as the best choice for maximizing response and limiting burden to participants. If you are having difficulty determining what to ask or what options to present, a deep analysis of literature and needs is the <a href="http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.466.8045&amp;rep=rep1&amp;type=pdf">standard</a>. However, with limited time and resources, an <a href="https://www.pewresearch.org/methods/u-s-survey-research/questionnaire-design/">informal discussion</a> with a few potential participants instead can help to break down common responses and further information that could be needed.</p><p>The closed-ended questions in the Texas State Library <a href="https://www.surveygizmo.com/s3/5502431/Library-Closures-Due-to-COVID-19">survey</a> excellently exhibit the practice of keeping questions short. While just a single question collects data regarding closures, hours, and programming, it is done in a rapid-fire checklist rather than asking each question individually. Even if each option in just the first closed question were to be changed to just a sentence, obtaining the information would take 7 times as long.</p><p>Something else to keep in mind while designing the questions is how to best format them to present in a table legibly and logically. For example, while “tell us about your branch closures” as an open format question can be easily read by the curator, it would be more universally understood (both by a person and a machine) if the system provided a set of drop-down menus with dates which can be uniformly parsed into the table under <a href="https://www.iso.org/iso-8601-date-and-time-format.html">ISO 8601</a> principles. This goal of designing for clear tables is also supported by the use of closed-ended questions in general.</p><p>Third, but certainly not last, a survey should be designed to be able to iterate and update if changes of circumstances occur. Accounting for the same user or organization (library) to need to make changes is necessary, and the literature on this topic would best suggest a user or library ID as the best method to track changes. However, other methods can include a question to link previously submitted responses, tracked users through emails or IP addresses, authentication requirements, and more.</p><h3>Resources for Future Crises and Collections</h3><p><strong>Research</strong></p><p>Determining scale of research: <a href="https://journals.sagepub.com/doi/abs/10.1177/014920639502100509">https://journals.sagepub.com/doi/abs/10.1177/014920639502100509</a></p><p>Best practices for longitudinal research: <a href="https://dl.acm.org/doi/pdf/10.1145/1520340.1520742">https://dl.acm.org/doi/pdf/10.1145/1520340.1520742</a></p><p>Collecting data during conflicts and crises: <a href="https://alliance-primo.hosted.exlibrisgroup.com/primo-explore/fulldisplay?vid=UW&amp;search_scope=all&amp;tab=default_tab&amp;docid=TN_sage_s10_1177_0022343314551563&amp;lang=en_US&amp;context=PC&amp;adaptor=primo_central_multiple_fe&amp;query=any,contains,Best%20practices%20in%20the%20collection%20of%20conflict%20data">https://alliance-primo.hosted.exlibrisgroup.com/primo-explore/fulldisplay?vid=UW&amp;search_scope=all&amp;tab=default_tab&amp;docid=TN_sage_s10_1177_0022343314551563&amp;lang=en_US&amp;context=PC&amp;adaptor=primo_central_multiple_fe&amp;query=any,contains,Best%20practices%20in%20the%20collection%20of%20conflict%20data</a></p><p><a href="https://ieeexplore.ieee.org/abstract/document/6570634">https://ieeexplore.ieee.org/abstract/document/6570634</a></p><p><a href="https://ieeexplore.ieee.org/abstract/document/7427199">https://ieeexplore.ieee.org/abstract/document/7427199</a></p><p><a href="http://www.inase.org/library/2015/zakynthos/bypaper/COMPUTERS/COMPUTERS-78.pdf">http://www.inase.org/library/2015/zakynthos/bypaper/COMPUTERS/COMPUTERS-78.pdf</a></p><p>Collecting education data: <a href="https://apa.sdg4education2030.org/sites/apa.sdg4education2030.org/files/2020-05/Essential%20education%20data_%20COVID19.pdf">https://apa.sdg4education2030.org/sites/apa.sdg4education2030.org/files/2020-05/Essential%20education%20data_%20COVID19.pdf</a></p><p>Social media crisis data collection: <a href="https://www.sciencedirect.com/science/article/pii/S0747563215005270">https://www.sciencedirect.com/science/article/pii/S0747563215005270</a></p><p>Formatting spreadsheet data: <a href="https://www.tandfonline.com/doi/pdf/10.1080/00031305.2017.1375989?iOS=&amp;">https://www.tandfonline.com/doi/pdf/10.1080/00031305.2017.1375989?iOS=&amp;</a></p><p>Sharing data across organizations: <a href="https://www.sciencedirect.com/science/article/abs/pii/S0920548906000250">https://www.sciencedirect.com/science/article/abs/pii/S0920548906000250</a></p><p><strong>Survey resources (all free or have free trials)</strong></p><p>Survey best practices (industry): <a href="https://www.surveymonkey.com/mp/survey-guidelines/">https://www.surveymonkey.com/mp/survey-guidelines/</a></p><p><a href="https://www.pewresearch.org/methods/u-s-survey-research/questionnaire-design/">https://www.pewresearch.org/methods/u-s-survey-research/questionnaire-design/</a></p><p><a href="https://www.qualtrics.com/blog/10-tips-for-building-effective-surveys/">https://www.qualtrics.com/blog/10-tips-for-building-effective-surveys/</a></p><p>Survey best practices (academia): <a href="https://www.surveypractice.org/api/v1/articles/3027-the-smart-phone-way-to-collect-survey-data.pdf">https://www.surveypractice.org/api/v1/articles/3027-the-smart-phone-way-to-collect-survey-data.pdf</a></p><p><a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2828303/">https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2828303/</a></p><p><a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2254236/">https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2254236/</a></p><p><a href="https://scholarworks.umass.edu/cgi/viewcontent.cgi?article=1161&amp;context=pare">https://scholarworks.umass.edu/cgi/viewcontent.cgi?article=1161&amp;context=pare</a></p><p><strong>Data and/or visualization resources (all free or have free trials)</strong></p><p>The Internet Archive: <a href="https://archive.org/web/">https://archive.org/web/</a></p><p>Tidy Data: <a href="https://cran.r-project.org/web/packages/tidyr/vignettes/tidy-data.html">https://cran.r-project.org/web/packages/tidyr/vignettes/tidy-data.html</a></p><p><a href="https://jezcope.github.io/library-spreadsheets/02-common-mistakes/">https://jezcope.github.io/library-spreadsheets/02-common-mistakes/</a></p><p><a href="https://jezcope.github.io/library-spreadsheets/01-format-data/">https://jezcope.github.io/library-spreadsheets/01-format-data/</a></p><p><strong>Data curation best practices:</strong></p><p><a href="https://www.dataone.org/all-best-practices">https://www.dataone.org/all-best-practices</a></p><p><strong>Survey services:</strong></p><p><a href="https://www.surveymonkey.com/">https://www.surveymonkey.com/</a></p><p><a href="https://www.typeform.com/">https://www.typeform.com/</a></p><p><a href="https://www.qualtrics.com/">https://www.qualtrics.com/</a></p><p><a href="https://www.google.com/forms/about/">https://www.google.com/forms/about/</a></p><p><a href="https://www.surveylegend.com/">https://www.surveylegend.com/</a></p><p>https://surveygizmo.com</p><p><strong>Visualization sites, services, and software:</strong></p><p><a href="https://infogram.com/">https://infogram.com/</a></p><p><a href="https://www.tableau.com/">https://www.tableau.com/</a></p><p><a href="https://www.chartjs.org/">https://www.chartjs.org/</a></p><p><a href="https://developers.google.com/chart">https://developers.google.com/chart</a></p><p><a href="https://jupyter.org/">https://jupyter.org/</a></p><p><a href="https://www.domo.com/solution/data-visualization">https://www.domo.com/solution/data-visualization</a></p><p><a href="https://www.visme.co/">https://www.visme.co/</a></p><p><strong>Project backup:</strong></p><p><a href="https://help.osf.io/hc/en-us/articles/360019930893-Register-Your-Project">https://help.osf.io/hc/en-us/articles/360019930893-Register-Your-Project</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bfc3420ec0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/covid-data-collection-lessons-learned-and-future-approaches-8bfc3420ec0d">COVID Data Collection: Lessons Learned and Future Approaches</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Recommendations for Creating Internships with the Public Sector]]></title>
            <link>https://medium.com/open-data-literacy/10-recommendations-for-creating-internships-with-the-public-sector-518769ba5e55?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/518769ba5e55</guid>
            <category><![CDATA[ischool]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[public-sector]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[open-data]]></category>
            <dc:creator><![CDATA[Bree Norlander]]></dc:creator>
            <pubDate>Wed, 20 May 2020 22:53:36 GMT</pubDate>
            <atom:updated>2020-05-20T23:56:42.634Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Open Data Literacy Logo" src="https://cdn-images-1.medium.com/max/600/1*ek9wMaD9O7H1Fj7KYaihxQ.png" /></figure><p>Immediately upon graduating with my Master of Library and Information Science (MLIS), I began project-managing the <a href="https://www.imls.gov/">Institute for Museum and Library Services</a> (IMLS) grant funded <a href="https://odl.ischool.uw.edu/">Open Data Literacy</a> (ODL) project headed by Carole Palmer and Nicholas Weber. Now, three years into my role, we are wrapping up the project and reflecting on our progress. We have provided placements at six governmental or public library locations for fourteen students. We have solicited and co-created internship projects from our civic partners that can be completed in a limited timeframe with specific deliverables. As is often the case, the internship projects and experiences have improved over the years and I wanted to take this opportunity to offer guidance to anyone taking on the task of partnering with external organizations to provide internships that benefit all parties involved. To that end, I have distilled my thoughts into a top ten list of recommendations for creating successful internships in partnership with public sector organizations.</p><p><strong>1.Pay interns competitive wages</strong></p><p>I have no doubt that offering our interns competitive wages during their approximately 8-week-long internships was one key to success. In our case, the stipends for internships were proposed in and paid for by the <a href="https://www.imls.gov/grants/available/laura-bush-21st-century-librarian-program">Laura Bush 21st Century Librarian Program</a> IMLS grant. The public sector partners committed their time and a physical location for the interns, but did not have to support the interns’ wages. Competitive pay meant that we could attract top-notch students to the opportunities and we could compensate them appropriately for the high-level work they performed. Moreover, unpaid internships can <a href="https://www.linkedin.com/pulse/how-unpaid-internships-undermine-diversity-inclusion-daniels-mba-jd">reinforce societal inequities</a> and we embrace the <a href="https://www.washington.edu/diversity/">University of Washington’s commitment</a> “to advance the values of diversity, equity and inclusion”.</p><p><strong>2.Scope the project</strong></p><p>This is so important and yet difficult to describe in a “how-to” format. In our experience, most projects needed to be reduced in scope from the original idea. This is what our process looked like when it was most successful:</p><ol><li>We solicited ideas for internship projects from partner organizations 7 months prior to the internship start dates.</li><li>We chose to fund internships that were best aligned with our grant goals and had the most clarity in deliverables.</li><li>We spoke with the project partners to further refine the internship plan.</li><li>In collaboration with partners, we hired interns whose interests and experiences were well aligned with the specific projects.</li><li>We asked interns to meet with the partner and fill out a Plan of Work document (including sections for Problem Statement, Goals, Deliverables, Sustainability, Milestones). Within the goals section we included a section for “Out of Scope” and “Time Allowing.” These sections provided a placeholder for the many ideas that surface but aren’t necessarily accomplish-able within the internship timeframe.</li><li>We reviewed the Plans of Work, provided feedback, and checked in throughout the internship on the progress.</li></ol><p>A successfully scoped project feels like it has well-defined “walls” (what is within scope and what is without) and deliverables. It evokes a clear sense of steps required for completion. From day one, the intern will understand where to begin and how to progress. To gauge the scope, ask the intern, “do you know what to do next and what you will be doing for the next week?” If they are hesitant, the scoping needs more work.</p><p><strong>3.Be flexible</strong></p><p>As the project gets underway, new information is likely to change the direction of the project or the specific deliverables. As an extreme example, one of our internships pivoted in its entirety when the COVID-19 pandemic hit Washington state and the sponsor organization, Washington State Library, needed help documenting public library service changes due to the pandemic. Be flexible with changes to the plan, but always make sure that the scoping is reasonable and that there are clear deliverables. Part of the learning that comes with any time-bounded project is adjusting expectations for what is possible, and what is feasible to actually complete in an 8 week internship. We have found that taking these adjustments seriously requires a project mentor and support team to be regularly available for consultation, and to be active in the revision of a project’s scope. Doing so teaches valuable project management skills to students and helps them quickly realize the realities of working in a dynamic public sector setting.</p><p><strong>4.Define roles and be available</strong></p><p>Too many cooks don’t necessarily spoil the broth as long as each has a defined role. These roles should be explained and agreed upon by all parties prior to the start of the internship. Ideally, hosting an internship onboarding event will allow you to cover this in detail. Our interns received mentoring from us (the academic institution) and our partners (public sector organizations and libraries). The academic partners can elicit feedback from interns on how the internship is going, provide literature recommendations, new ideas, administrative information or referrals, and encouragement. The partners should provide the domain knowledge, orientation to the physical space, networking and introductions to other staff, and feedback on deliverables. We often found that one or two meetings that included all mentors and the intern were valuable in making sure everyone was on the same page.</p><p><strong>5.Create community</strong></p><p>If you have multiple interns, even if they are working for different public sector partners, provide opportunities for them to work together. We created a Slack channel for each year’s cohort and hosted happy hours and lunches throughout the internship timeframe. These opportunities allowed the interns to network, ask questions of each other, share ideas, and commiserate over shared frustrations.</p><p><strong>6.Provide opportunities for dissemination</strong></p><p>Provide interns opportunities to present or publish the work they are doing. We created a <a href="https://medium.com/open-data-literacy/archive">Medium publication</a> and had interns publish two or more blogposts during their internship which we promoted via <a href="https://twitter.com/ODLiteracy">social media</a>. We also held a showcase event at the end of summer in which interns gave short presentations on their work. We shared invitations to this event with sponsors and the iSchool community at large. Events like the showcase or a poster session also provide opportunities to network, create artifacts for resumes and portfolios, and to immerse them in a community of domain enthusiasts. We’ve had interns submit journal articles and present at conferences based on their internship accomplishments. These experiences give students tangible experiences to use in job applications and interviews.</p><p><strong>7.Create an online workspace</strong></p><p>Create an online place for the intern to store all relevant artifacts from datasets to workplans to blogpost drafts. We used <a href="https://github.com/OpenDataLiteracy">Github repositories</a>, but other platforms such as Open Science Framework (OSF), Gitlab, or Bitbucket are also available. These workspaces should be made accessible to all stakeholders of the internship, if not fully open to the public.</p><p><strong>8.Encourage documentation</strong></p><p>The online workspace allows interns and stakeholders to track the progress of the internship. This is useful for following along and for retrospective review. Each internship will have different documentation requirements, but examples include methodologies (for data collection, for analysis, for tool building, etc.), code, changes to the Plan of Work, drafts of blogposts, slides for presentations. We often review our interns Github repositories when writing papers, presentations, and annual reports.</p><p><strong>9.Provide opportunities for remote work.</strong></p><p>If at all possible, offer some remote internships. The <a href="https://ischool.uw.edu/programs/mlis">University of Washington MLIS program</a> offers both residential and online degrees and we strive to make opportunities available to all students. We worked closely with a couple partners to craft remote internships that mean we could recruit and hire some outstanding students who were not local. For us, this required regular online check-ins via Zoom or other conferencing applications, but it was time well spent.</p><p><strong>10.Feed interns</strong></p><p>Seriously, food goes a long way to creating community and building relationships. Host lunches, happy hours, or coffee times.</p><p>To celebrate a successful project, we are hosting an online alumni event for interns, public sector and public library sponsors, and our team. The enthusiasm for the event suggests to me that we made a lasting impact on interns and partners alike. Not only did the interns leave the experience with resume-building deliverables and experiences, but the partners continue to build upon and utilize deliverables. We, the ODL team, were able to use feedback from the interns about their experiences to update coursework to better prepare students for this type of work, and to create resources for professionals in the field to use now. Each year we improved our internship program based on the experiences of the previous year. In the end we have a cohort of former interns that are still excited about engaging and networking with each other, partners who are eager to hear from former interns, and new graduate students who are benefiting from a data curation curriculum that is fresh and relevant.</p><p>I hope that others can benefit from what we learned as much as we did!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=518769ba5e55" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/10-recommendations-for-creating-internships-with-the-public-sector-518769ba5e55">10 Recommendations for Creating Internships with the Public Sector</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tracking Washington State Public Library Responses in Crisis]]></title>
            <link>https://medium.com/open-data-literacy/tracking-washington-state-public-library-responses-in-crisis-60482ea7e080?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/60482ea7e080</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[library-science]]></category>
            <category><![CDATA[coronavirus]]></category>
            <category><![CDATA[covid19]]></category>
            <dc:creator><![CDATA[Seattle Informationist]]></dc:creator>
            <pubDate>Thu, 30 Apr 2020 21:31:29 GMT</pubDate>
            <atom:updated>2020-04-30T21:31:29.015Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wYoQ_8RiIBCXgz35YxEQ-Q.jpeg" /><figcaption>A photo of a children’s drawing toy that says “stay home.” Photo by <a href="https://unsplash.com/@glencarrie?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Glen Carrie</a> on <a href="https://unsplash.com/s/photos/covid?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This spring, I began an internship with the Washington State Library as part of the Open Data Literacy Project at the University of Washington. The internship had originally focused on crowdsourcing library resource data, but due to the COVID-19 pandemic, I pivoted to tackling the question of how public entities can gather data that are reliable, accurate, and comprehensive in a short period of time, especially in a time of crisis. In this post, I will discuss how the Washington State Library went about gathering pandemic-response data from WA public libraries.</p><p>The novel coronavirus outbreak of 2019 indiscriminately derailed the plans of individuals and organizations across the world — and libraries were no exception. In Washington State, the public library system rushed to keep up with the changing circumstances, particularly as it was the first state in the country to be hit hard by infections. At the start of the outbreak, the first responding libraries implemented actions ranging from removal of high-touch offerings like children’s toys to cancellation of library events and meeting rooms. Approaches changed almost daily in an attempt to mitigate the spread of the virus.</p><p>With the rapid increase in cases, libraries acted similarly in adding precautions for patrons and employees. With closures of private and public institutions across the state, public libraries, mission-driven to provide equitable community support, were left scrambling for alternatives. Many began purchases of extended online access resources, while others added curbside and contactless pickup opportunities. Facilities increased sanitation and distancing measures, limited hours, and encouraged the use of online resources for patrons. By end of day March 12th, facility closure announcements had begun. Before a week had passed, 51 of the 60 public library systems in the state had closed — most of the final nine followed not long after.</p><p>Beginning in March, the Washington State Library began collecting data on library responses to COVID-19. The State Library wanted to provide a service to the libraries themselves, hoping that sharing action steps with one another could help libraries update and maintain appropriate strategies for the rapidly changing circumstances. Kathleen Sullivan, the Open Data Librarian at the Washington State Library and creator of the <a href="https://data.wa.gov/Culture-and-Community/Washington-State-Public-Library-Services-Affected-/6iab-kcxu">dataset on closures and COVID-19 responses </a>in Washington public libraries, stated that “we [the Washington State Library] also wanted a record of how key community gathering places — institutions dedicated to access and support for all — responded to a quickly developing public health emergency.” Library staff manually went through each system’s press releases, websites, and social media pages, gathering any relevant response data. While this was extremely labor-intensive on State Library staff, it helped to shift pressure from public library systems already swarmed with countless new tasks and expectations.</p><p>When documenting responses, the library began tracking any action that was taken by multiple libraries. This meant the dataset grew to include ten response variables, including increased sanitation, cancellations of programming, and expanded Public Service information — this was a manageable amount to continuously monitor by State Library staff. Long-term plans for data curation aim to refine the log to precisely identify dates of actions, both for documentation purposes and for reference during later crises.</p><p>To date, most of the libraries remain actively offering a variety of services, ranging from Census and tax filing assistance, online access books, movies, magazines, online and telephone assistance, and even simplified online card registration for those desiring to register for an account. Many have designed popular online-only book readings, socials, and other events using social media, primarily through Facebook Live and Facebook Pages functions.</p><p>To get a national perspective, I reviewed the websites of 51 state library websites (US states and territories) to determine what role other state libraries played in gathering data about the impacts of COVID-19 on public libraries. Nationally, libraries remain functional to varying degrees, and each state has taken a different approach to the documentation of how libraries are managing themselves during the crisis, although nearly all (at least 48 of 51 surveyed) state libraries have released some form of COVID guidance on their main website. Some have sent out regular surveys to each library branch and/or system to receive updates on their service offerings, and others have created portals librarians can access to provide new information. There are at least 15 states with publicly available live-updating spreadsheets breaking down available resources at each library — some clearly refreshed regularly, some with no updates for over a month as of the writing of this article, and many more sit somewhere in between. While tables are the most common display of the library crisis response data, a handful of states provide some very in-depth and unique approaches. One such state is Montana, which has used Esri, a GIS mapping software, to produce a rich, visually appealing <a href="http://montana.maps.arcgis.com/apps/opsdashboard/index.html#/d2c7245e462a49fe9a51a6c7fab69d65">dashboard</a> of closures and service offerings for 132 libraries so far.</p><p>Many other groups have stepped up for the library response data collection effort, including the Public Library Association, which surveyed over 2,500 library systems to analyze the immediate <a href="http://www.ala.org/pla/issues/covid-19/surveyoverview">impacts</a> the crisis was having on them. ITHAKA created a <a href="https://surveys.ithaka.org/jfe/form/SV_8qN8F2274hMBBBz">form</a> to collect academic library-specific closure data with thousands of <a href="https://surveys.ithaka.org/results/public/aXRoYWthLVVSX3E5c3lDWkJzM0ZEVDd4Zi01ZTY5NTFkZTUwYWU5YjAwMTAyYWI2YjQ=#/pages/Page_e741d33b-94f0-47c8-933c-64110371029e">responses</a>, as well. Even an independent blogger from Nebraska’s <a href="http://travelinlibrarian.info/2020/03/public-libraries-closed-for-covid-19/">record</a> of public libraries closed due to coronavirus has gone viral in the librarian community — to date, he and his small team have recorded information from well over 4,000 systems and branches across the country.</p><p>Moving forward, libraries and their data gatherers will face the task of keeping impact data current, and making sure this documentation can serve future public agencies looking to see not only how this crisis developed, but how to create the most efficient data management system for rapidly changing circumstances.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60482ea7e080" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/tracking-washington-state-public-library-responses-in-crisis-60482ea7e080">Tracking Washington State Public Library Responses in Crisis</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[COVID-19 Open Data Round-up]]></title>
            <link>https://medium.com/open-data-literacy/covid-19-open-data-round-up-71936b75e2bd?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/71936b75e2bd</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[open-data]]></category>
            <dc:creator><![CDATA[Kaitlin Throgmorton]]></dc:creator>
            <pubDate>Tue, 07 Apr 2020 17:00:32 GMT</pubDate>
            <atom:updated>2020-04-07T17:00:32.138Z</atom:updated>
            <content:encoded><![CDATA[<p>Even in the midst of a global pandemic, open data continues to be important, paving the way for scientific breakthroughs, as well as enabling timely information-sharing during an unprecedented time of uncertainty and stringent containment measures.</p><p>One of the most prominent examples of COVID-19 open data is the <a href="https://www.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6">Johns Hopkins global cases dashboard</a> (<a href="https://www.technologyreview.com/s/615367/coronavirus-24000-research-papers-available-open-data/?mc_cid=27ea56651d&amp;mc_eid=e343ef22bc">Dong et al., 2020</a>), for which all data collected and displayed are made freely available in a <a href="https://github.com/CSSEGISandData/COVID-19">Github</a> repository. This open data dashboard has been widely shared by major U.S. news media outlets, and its visualizations have helped the general public understand the reach and severity of the disease.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fyvPeqSx2sBkWFYd" /><figcaption><a href="https://www.arcgis.com/apps/opsdashboard/index.html#/bda7594740fd40299423467b48e9ecf6">JHU’s COVID-19 Data Dashboard</a> as of 4/6/20.</figcaption></figure><p>Smaller locales are taking the same data sources Johns Hopkins is using to create localized dashboards with additional area-specific information. For instance, the Sioux Falls, South Dakota, <a href="https://coronavirus-cityofsfgis.hub.arcgis.com/">coronavirus data hub</a> shows case information, as well as maps of food assistance locations along with restaurants open for takeout and delivery (Dataworks, 2020).</p><p>Under a directive from the White House Office of Science and Technology Policy (OSTP), in collaboration with the National Library of Medicine, National Institutes of Health, Microsoft, Chan Zuckerberg Initiative, and the Allen Institute for Artificial Intelligence, more than 44,000 research outputs related to coronavirus have been made freely available as the <a href="https://cset.georgetown.edu/covid-19-open-research-dataset-cord-19/">COVID-19 Open Research Dataset, or CORD-19</a> (Georgetown University, n.d.). Released openly and in machine-readable JSON format, the dataset will enable the global machine learning community to perform text and data mining in order to uncover insight into SARS-CoV-2 and the current COVID-19 pandemic (<a href="https://www.technologyreview.com/s/615367/coronavirus-24000-research-papers-available-open-data/">Hao, 2020</a>).</p><p>In addition to disease research, open data is helping communities understand the scope of COVID-19’s economic impact, through the release of information such as unemployment insurance claims, and organization closures. At the federal level, the U.S. Department of Labor maintains an API that can be used to access their <a href="https://developer.dol.gov/expanding-growth/oui-inital-claims/">open data on unemployment insurance claims</a> by time series, and many states release similar data. Department of Labor unemployment data has shown that for the week ending in March 21, 2020, Americans filed more than 3 million claims, nearly five times the previous record — and then again, last week (ending in March 28), unemployment claims reached 6 million, shattering the previous week’s record (Schneider, 2020). While this information is concerning, it’s important to disclose it freely and openly, so that governments and other organizations can respond with solutions.</p><p>Finally, in library open data news, Kathleen Sullivan — one of ODL’s former interns, now working as an open data consultant for the Washington State Library (WSL) — and her WSL colleagues manually compiled an open dataset about <a href="https://data.wa.gov/Culture-and-Community/Washington-State-Public-Library-Services-Affected-/6iab-kcxu">Washington state public library services affected by the COVID-19 outbreak</a> (Sullivan, 2020). The dataset tracks closures and impacts to programs, as well as relaxed fines and library PSAs to patrons about where to obtain factual information about COVID-19.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Npav8utUlVxJ_0EW" /><figcaption>A visualization of most common measures taken by Washington library systems ahead of and during COVID-19 library closures, based on data retrieved from the <a href="https://data.wa.gov/Culture-and-Community/Washington-State-Public-Library-Services-Affected-/6iab-kcxu">Washington State Public Library Services Affected by COVID-19 dataset</a> on 4/6/2020.</figcaption></figure><p>While the dataset was initially launched as a service to public libraries to compare their own system’s strategy to that of other systems, Sullivan envisions the dataset assisting future research. “Over the longer term, the dataset should ideally serve as a record of how key community gathering places — institutions dedicated to access and support for all — responded to a quickly developing public health emergency. This should be useful for libraries themselves, and anyone else assessing responses to an epidemic,” Sullivan said. Retaining a record of mitigation strategies and other steps employed by libraries could serve to inform future practice, when reviewed at a later date by researchers and other interested parties.</p><p>Open data are helping to produce innovative research to stop the COVID-19 pandemic, and to keep the public informed about its impacts — and advancing the use and understanding of open data continues to be the <a href="http://odl.ischool.uw.edu/">Open Data Literacy</a> project’s primary goal.</p><p><strong>Resources:</strong></p><ul><li><a href="https://www.academicdatascience.org/covid">Academic Data Science Alliance | COVID-19 Data Science Resources</a></li><li><a href="https://coronavirustechhandbook.com/home">COVID19 Tech Handbook</a></li><li><a href="https://catalog.data.gov/dataset?q=covid&amp;sort=score+desc%2C+name+asc&amp;as_sfid=AAAAAAXpAlgvVCyDE2dIruLjQOvqVgKQcUVGgd0wPEdHywpwKTBhF6u3AIu9We4XMV-qjdUMdOB-aY94_kYwc681aaZt9kjtQg0Tmfye3M7bLSM3-4IQfknAo9OT-is8JuR5AhE%3D&amp;as_fid=18b58215938b16fd4c41e93b1df6b7ba9dc4f646">COVID-19-related data on data.gov</a></li></ul><p><strong>References:</strong></p><p>Dataworks. (2020). City of Sioux Falls Coronavirus Resources. <a href="https://coronavirus-cityofsfgis.hub.arcgis.com/">https://coronavirus-cityofsfgis.hub.arcgis.com</a>.</p><p>Dong, E., Du, H., &amp; Gardner L. (2020). An interactive web-based dashboard to track COVID-19 in real time. <em>The Lancet: Infectious Diseases.</em> <a href="https://doi.org/10.1016/S1473-3099(20)30120-1">doi:10.1016/S1473–3099(20)30120–1</a>.</p><p>Georgetown University. (n.d.). COVID-19 Open Research Dataset (CORD-19). <a href="https://cset.georgetown.edu/covid-19-open-research-dataset-cord-19">https://cset.georgetown.edu/covid-19-open-research-dataset-cord-19</a>.</p><p>Hao, K. (2020, March 16). Over 24,000 coronavirus research papers are now available in one place. MIT Technology Review. <a href="https://www.technologyreview.com/s/615367/coronavirus-24000-research-papers-available-open-data">https://www.technologyreview.com/s/615367/coronavirus-24000-research-papers-available-open-data</a>.</p><p>Schneider, A. (2020, April 2). Staggering: Record 10 million file for unemployment in 2 weeks. NPR. <a href="https://www.npr.org/sections/coronavirus-live-updates/2020/04/02/825383525/6-6-million-file-for-unemployment-another-dismal-record">https://www.npr.org/sections/coronavirus-live-updates/2020/04/02/825383525/6-6-million-file-for-unemployment-another-dismal-record</a>.</p><p>Sullivan, K. (2020). Washington State Public Library Services Affected by COVID-19. Data.WA.gov. <a href="https://data.wa.gov/Culture-and-Community/Washington-State-Public-Library-Services-Affected-/6iab-kcxu">https://data.wa.gov/Culture-and-Community/Washington-State-Public-Library-Services-Affected-/6iab-kcxu</a>.</p><p>U.S. Department of Labor Development Portal. (n.d.). OUI Initial Claims. <a href="https://developer.dol.gov/expanding-growth/oui-inital-claims/">https://developer.dol.gov/expanding-growth/oui-inital-claims/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71936b75e2bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/covid-19-open-data-round-up-71936b75e2bd">COVID-19 Open Data Round-up</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Public Libraries & Open Data Survey: Initial Findings]]></title>
            <link>https://medium.com/open-data-literacy/public-libraries-open-data-survey-initial-findings-f5d0e666f5aa?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/f5d0e666f5aa</guid>
            <category><![CDATA[public-libraries]]></category>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[surveys]]></category>
            <dc:creator><![CDATA[Kaitlin Throgmorton]]></dc:creator>
            <pubDate>Mon, 09 Mar 2020 22:57:47 GMT</pubDate>
            <atom:updated>2020-03-09T22:57:47.828Z</atom:updated>
            <content:encoded><![CDATA[<p>During the summer of 2019, the Open Data Literacy (ODL) project, working in collaboration with the <a href="https://www.sos.wa.gov/library/">Washington State Library</a>, conducted a survey on open data and public libraries. All public library systems in the state were invited to participate in the 11-question <a href="http://odl.ischool.uw.edu/survey/">survey</a> about their open data interests and activities.</p><p>Fifty-one system and branch libraries participated — a 45% response rate. Among those respondents, 49% were from libraries with service populations over 100,000, and 51% represented service populations under 100,000. The table below shows the full breakdown of responses by legal service area (LSA) population.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y1-qWrnLDuviIwpd" /></figure><p>Results from participating libraries indicate that many Washington state public libraries are already well-positioned to work with open data. Two-thirds of respondents agree that open data aligns with their mission (67%) and their community’s interests (64%). Most are already involved in adjacent activities, such as providing access to local government information, local history, and special collections, as well as information about matters of public interest. Additionally, more than 90% of respondent libraries agreed that they offer guidance on information technologies, new information resources, and information about community activities and resources — whereas only 55% of respondents say their local government information is available in digital form.</p><p>With open data in particular, public libraries in Washington are more active than expected. Nearly 20% describe themselves as highly active in publishing their library’s data as open data, and 43% report at least some level of activity in this area. Only 8% report they are unlikely to become active in open data publishing. Even more promising, 19% are “likely” to begin publishing library data as open data, and 25% are “somewhat likely” to do so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FY-tSy9Uei-98pZ1" /></figure><p>Open data activity at the reference desk is also quite strong, with 22% of respondent libraries indicating they are highly active in providing “reference assistance for community members on finding or using open data.” Sixty-five percent report at least some level of activity in this area, and only 6% say they’re unlikely to provide reference services in this area.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SrjYp1Y4-Y8kIN2d" /></figure><p>In the open-ended survey responses, one librarian explained their support for open data reference activity as follows:</p><p><em>“It’s common to hear librarians lamenting the fact that they never get asked actual reference questions anymore. …But open data is an area where skilled guides are still needed. With the appropriate training, our librarians could be showing our community a richer way to view the world than through a simple google search. I think that given the opportunity, many librarians would jump at the chance to learn more.”</em></p><p>While activity and interest in open data among Washington public libraries is high, libraries do have some hesitations. For example, ODL was surprised that 18% of respondents indicated they are unlikely to “build collections of open data of value to [their] community,” given the responses on current involvement in providing access to local government information and other information of public interest. Respondents were also divided about who should take the lead on local open data initiatives. Forty-three percent agree that libraries should lead in this area, whereas 37% were neutral, and 8% disagreed. Views varied on which library positions would be most likely to work on open data activities, with respondents listing directors, reference librarians, adult services librarians, IT staff, and a variety of other positions.</p><p>Not surprisingly, 47% of respondents agreed that prioritizing open data initiatives would be difficult for their library, with more than two-thirds (69%) indicating a strong need for increased budgets or grant funds. However, we were encouraged to see that most libraries recognize the value of “new or improved collaboration with city, state, or other partners” (67%), as well as “professional development on access, use, and instruction” (57%), for moving forward with open data. That understanding, coupled with almost two-thirds (61%) of surveyed libraries either active or likely to become active in publishing their library data as open data, suggests a highly robust state of ambition in Washington public libraries for advancing open data.</p><p><strong>Learn more about the survey<br></strong>To learn more about the survey findings, <a href="https://drive.google.com/file/d/1x1uJMRfOQNw6VSIek8n8Pvh1SsiXAzmi/view?usp=sharing">view the slides</a> from our presentation at the Chief Officers of State Library Agencies (COSLA) 2019 Membership Meeting, “From Ambition to Action: State &amp; Public Libraries Partnering on Open Data.”</p><p><strong>Launch the survey in your area<br></strong>ODL is now working to extend the Public Libraries and Open Data survey beyond the state of Washington in collaboration with the <a href="https://tascha.uw.edu/">Technology and Social Change Group (TASCHA)</a>, at the University of Washington Information School. If your state is interested in launching the survey, please contact TASCHA’s senior research scientist, <a href="https://www.tascha.uw.edu/people/chris-jowaisas/">Chris Jowaisas</a>, at chrisjow@uw.edu.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5d0e666f5aa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/public-libraries-open-data-survey-initial-findings-f5d0e666f5aa">Public Libraries &amp; Open Data Survey: Initial Findings</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes open data good, and how can we make it better?]]></title>
            <link>https://medium.com/open-data-literacy/what-makes-open-data-good-and-how-can-we-make-it-better-c37275e71319?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/c37275e71319</guid>
            <category><![CDATA[metadata]]></category>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[open-government]]></category>
            <dc:creator><![CDATA[Kaitlin Throgmorton]]></dc:creator>
            <pubDate>Sat, 12 Oct 2019 02:26:07 GMT</pubDate>
            <atom:updated>2019-10-12T02:26:06.783Z</atom:updated>
            <content:encoded><![CDATA[<p>After a year of working for the <a href="http://odl.ischool.uw.edu/">Open Data Literacy</a> project, and a summer of working for City of Seattle’s Open Data Team, it’s safe to say that my opinion on open data is biased. I believe in it, I’m passionate about it, and I want more of it, at all levels of government and at research institutions. However, in multiple conversations about open data, I’ve noticed that while many people tend to think that more information about public services, rather than less, is a good thing — and thus, that open data is a good thing (or, <a href="https://www.pewinternet.org/2015/04/21/open-government-data/">at least promising, according to Pew Research</a>) — moving from understanding that open data is valuable, to actually producing valuable open data, can be challenging.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MEV79ONwRAyaNYG1F-9Wdw.jpeg" /></figure><h3><strong>Metadata at a minimum</strong></h3><p>So, what makes open data good? First of all, it’s important to correct the misconception that open data is inherently good. According to Taylor et al. (2015), data are often considered “a proxy for the facts.” While it’s tempting to believe that data are objective, beneficial, and valuable as is, this belief is much too simple, and often untrue. As Taylor et al. (2015) explain:</p><blockquote>“Seen as anything but raw, data is understood to be produced or enacted through on-going circulations and relations. Data, from this viewpoint, doesn’t by itself assert things in the world; rather it helps to surface, assemble, cement and (at times) unravel forms of knowing, ideas controversies, and so on.” (p. 2863).</blockquote><p>Understanding that open datasets are always situated in context, and not just neutral ‘fact proxies,’ is crucial to producing good open data.</p><p>At a minimum, I define good open data as findable and usable. One of the best and most established ways to achieve those two goals is to provide rich metadata, which was the focus of my City of Seattle internship. Metadata demystifies and contextualizes data — not only describing it, but revealing potential limitations and possibilities. The process of demystification, enacted through the creation of metadata, is especially essential for open data. By definition, open data is meant for a public audience that, without metadata, won’t have the benefit of knowing where the data came from, why and how it was created, if it was modified from its original format, if it contains any errors or missing data, etc.</p><p>Take, for instance, the <a href="https://data.seattle.gov/dataset/Checkouts-by-Title-Physical-Items-/3h5r-qv5w">Checkouts by Title</a> dataset available in the <a href="https://data.seattle.gov/">City of Seattle</a> open data portal from the Seattle Public Library. While this dataset has excellent metadata, the main description originally didn’t contain a link to its <a href="https://data.seattle.gov/Community/Integrated-Library-System-ILS-Data-Dictionary/pbt3-ytbc">data dictionary, which is actually a dataset</a>, too. While someone familiar with the data portal might know to browse by data owner to find other relevant open data, new users likely would not — and without the data dictionary, decoding the data becomes much more difficult. To see other examples of how important metadata is, see <a href="https://medium.com/open-data-literacy/the-myth-of-the-obvious-ca6afb08b02d">my other blog post</a>.</p><h3><strong>Beyond metadata</strong></h3><p>While sufficient metadata is the foundation of creating valuable open data, it’s really just the beginning. One of the most significant things I learned this summer is how much more the open data movement can grow. As an emerging area in many governments, opportunities to improve open data abound. Some other ways to make open data better, that I would have loved to tackle this summer if I’d had more time, include:</p><p><strong>Centering open data around user needs.</strong></p><p>As open government data aims to be accessible to entire geographic populations — for instance, in the case of my internship, the city of Seattle — understanding user needs and behaviors can improve the usefulness of open data, as well as improve equity. User-centered open data applies to metadata, too, as it aids in knowing how much description is necessary to make the data reusable. Various projects are currently underway to make open data more user-centered, including Sunlight Foundation’s <a href="https://communities.sunlightfoundation.com/discovery/personas-library/">Open Data Persona Library</a>.</p><p><strong>Improving open data’s compatibility with various tools.</strong></p><p>Currently, the number of ready-made open data platforms is limited, and governments must either develop their own, or use existing vendors. While these platforms have powered the open data movement so far, more robust tools are needed, particularly for metadata creation and maintenance. If metadata and usability were more emphasized in open data publishing tools, they might also be more prominent on open datasets.</p><p><strong>Promoting a culture of openness at the institutional level.</strong></p><p>Opening up data to the public isn’t always an easy process. Sometimes, large amounts of work go into extracting and transforming data before loading and preparing it for publishing. While sometimes these processes can’t be changed or sped up, it is possible to integrate the concept of openness into an organization’s overall culture and workflow. Currently, while many U.S. government institutions have committed to open data at the legislative level, prioritizing openness as a core value has less momentum. Until governments commit to being as open about their operations as is feasibly and ethically viable, open data (and all other open projects, such as contracts, budgets, meetings, etc.) initiatives will suffer from their status as a side project. To be successful, openness should be an organizational mindset, and an ingrained way of doing business.</p><p>For the open data movement to grow, we must realize that open data is much more complex than we often make it out to be. It’s not ‘just data,’ and opening it up isn’t as simple as exporting some data to a public website. Facing these complexities will not only make the open data movement stronger, but strengthen public understanding of and trust in government as a whole.</p><h3>References</h3><p>City of Seattle Open Data Portal. (2019.) Checkouts by Title (Physical Items) [dataset]. Seattle Public Library. Retrieved from <a href="https://data.seattle.gov/dataset/Checkouts-by-Title-Physical-Items-/3h5r-qv5w">https://data.seattle.gov/dataset/Checkouts-by-Title-Physical-Items-/3h5r-qv5w</a>.</p><p>City of Seattle Open Data Portal. (2017.) Integrated Library System (ILS) Data Dictionary [dataset]. Seattle Public Library. Retrieved from <a href="https://data.seattle.gov/Community/Integrated-Library-System-ILS-Data-Dictionary/pbt3-ytbc">https://data.seattle.gov/Community/Integrated-Library-System-ILS-Data-Dictionary/pbt3-ytbc</a>.</p><p>Horrigan, J.B., &amp; Rainie, L. (2015). Americans’ Views on Open Government Data. Pew Research Center. Retrieved from <a href="https://www.pewinternet.org/2015/04/21/open-government-data/">https://www.pewinternet.org/2015/04/21/open-government-data</a>.</p><p>Roadmap to Informed Communities. (n.d.) Library of user personas for open data. Sunlight Foundation. Retrieved from <a href="https://communities.sunlightfoundation.com/discovery/personas-library/">https://communities.sunlightfoundation.com/discovery/personas-library</a>.</p><p>Taylor, A., Lindley, S., Regan, T., Sweeney, D., Vlachokyriakos, V., Grainger, L., &amp; Lingel, J. (2015). Data-in-Place: Thinking through the relations between data and community. <em>Proceedings of the 33rd Annual ACM Conference on Human Factors in Computing Systems, 2015, </em>2863–2872.<em> </em>DOI: 10.1145/2702123.2702558.</p><h3>Further Reading</h3><p>For a great summary of more ways open data can improve, this article, <a href="https://sunlightfoundation.com/2019/07/02/the-future-of-open-government-reflections-from-ogp-code-for-america-2019/">“The future of open government,” from Sunlight Foundation</a> sums up the latest evolutions in open government data from the Open Government Partnership Summit and Code for America 2019.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c37275e71319" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/what-makes-open-data-good-and-how-can-we-make-it-better-c37275e71319">What makes open data good, and how can we make it better?</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Open Data to Understand Communities Around Seattle Public Libraries]]></title>
            <link>https://medium.com/open-data-literacy/using-open-data-to-understand-communities-around-seattle-public-libraries-fa3f9a96f3be?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/fa3f9a96f3be</guid>
            <category><![CDATA[r-programming-language]]></category>
            <category><![CDATA[census-data]]></category>
            <category><![CDATA[maps]]></category>
            <category><![CDATA[public-libraries]]></category>
            <dc:creator><![CDATA[Karalyn Ostler]]></dc:creator>
            <pubDate>Fri, 20 Sep 2019 20:30:27 GMT</pubDate>
            <atom:updated>2019-09-20T20:30:27.138Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Browser application with maps of Seattle" src="https://cdn-images-1.medium.com/max/949/1*WSBnuIcONY2V0BbW9sGbRQ.png" /><figcaption>Map dashboard created for this project using data from the US Census Bureau. Maps show the city of Seattle, with census tracts colored by median age. Dashboard can be found at: <a href="https://kostler.shinyapps.io/SPL-Seattle-Census-Data/">https://kostler.shinyapps.io/SPL-Seattle-Census-Data/</a></figcaption></figure><p>This summer, as a part of my <a href="https://odl.ischool.uw.edu/">Open Data Literacy</a> internship, I worked with the <a href="https://www.spl.org/">Seattle Public Library</a> (SPL) to transform external open data into actionable intelligence for frontline staff. SPL is a large public library system serving the city of Seattle. It has 27 different branch locations divided into 6 different regions and offers a variety of services and outreach programs. Though library staff already learn about their community through methods such as talking to patrons and local organizations, open data could be used to supplement these efforts and assist staff in their outreach and service planning processes. With my mentor at SPL, David Christensen, I created a plan to assess the needs of SPL staff, search for relevant open datasets, and create deliverables for use by staff.</p><p><strong>Assessing Data Needs of SPL Staff</strong></p><p>Before I could start transforming open data, I needed to find out what types of information would be most useful for SPL staff. Initially I started my project with the idea that I would try to assess the needs of all staff at SPL. However, since this project had a limited timeframe, we decided to limit the assessment to only two regions of SPL. To get a general idea of the data needs of staff at multiple locations, I interviewed Francesca Wainwright, the regional manager for the northeast region, and Wei Cai, the regional manager for the southeast region. Each interview lasted about 20 minutes and was conducted over the phone. For the interviews, I prepared a script with background information on the project, questions about the goals and needs of staff at each branch, and suggestions of possible datasets in case the regional managers did not have any ideas.</p><p>The regional managers were able to provide insight on the current programs and future projects at their region’s branch libraries. Overall, both regional managers had a really good idea about what kind of information would be useful for their staff and did not need the prepared dataset ideas. Both regions expressed the desire for demographic and socio-economic information about the communities around each branch. Specifically, they wanted to know about age, income, languages spoken, education levels, and employment rates. With this information, staff could identify areas of greater need among the community and better plan outreach services. One region was particularly interested in how many students were attending private schools versus public schools, with the thinking that an area with more public schools might need more library services because public schools tend to have less funding. One commonality among both interviews was that the managers really wanted more granular data than what they usually received. Both mentioned that they would receive information about the region or city as a whole and not about the immediate community around the branch, making it hard to pinpoint specific areas of focus.</p><p>From the interviews with the regional managers, I was able to create a large list of potential factors about the community that I could use to look for open datasets. To keep this project’s scale manageable, I decided to limit the list of factors to four main topics: age, household income, language spoken at home, and school enrollment type. These topics covered basic traits of the community and could be used by any branch in their planning.</p><p><strong>Searching for Suitable Open Data</strong></p><p>With the four key topics I had collected from the interviews, I started to look for open datasets that would best serve SPL staff needs. Since there was a lot of focus on communities around the libraries, I began with looking for local open datasets about Seattle in the <a href="https://data.seattle.gov/">City of Seattle Open Data Portal</a> and the <a href="https://data.wa.gov/">Washington State Open Data Portal</a>. Both of these portals provide many interesting open datasets published by various city departments and state departments. For this project, I found a few datasets about low-income housing and public-school locations, but not many that would provide basic information about the communities in Seattle that the regional managers were looking for.</p><p>For Seattle community demographics, I decided to look at the <a href="https://www.census.gov/">United States Census Bureau</a>. Since the Census Bureau’s <a href="https://www.census.gov/about/what.html">mission</a> is “to serve as the nation’s leading provider of quality data about its people and economy,” the Census Bureau is the perfect place to find data about age, income, and many other qualities about the American people. When people think of the “Census,” they usually think of the Decennial Census that is conducted every 10 years to record population and housing counts, but there are many other censuses and surveys that they conduct periodically. The Census Bureau is committed to open government, so they release pubic data from their censuses and surveys, and it is openly available to everyone. To start searching the large amount of datasets from the Census Bureau, I used their <a href="https://factfinder.census.gov/faces/nav/jsf/pages/index.xhtml">American FactFinder</a> tool’s advanced search feature to search for the topics I was interested in for this project. I was pleasantly surprised to find that there were datasets that aligned with all four of my topics from the American Community Survey (ACS) and that there were relatively recent estimates from 2017. The American FactFinder allows users to download each dataset as a spreadsheet or presentable document, both with associated metadata. Census data can also be downloaded via the <a href="https://www.census.gov/developers/">Census API</a>, which can be a better option if downloading the data for use in a programming language like R or Python. For this project, I chose to use the API because I wanted to use R.</p><p><strong>Creating an interactive Map Dashboard Using R</strong></p><p>Many different types of visualizations could be created from the estimates provided by the 2017 ACS. Based on what I had learned in the interviews and conversations with my mentor, I decided that maps would be the best visual representations for the census data. Maps would allow staff to pinpoint areas of interest and explore the local neighborhoods around the libraries. I chose R instead of Python to create visualizations for this project because it has well developed visualization packages and was the preferred programming language of my mentor at SPL. I used the package <a href="https://github.com/walkerke/tidycensus">tidy_cenus</a> to read in data from the Census API. This package allowed me to easily access the data I wanted and gave me the polygon coordinates needed to map the census tracts’ shapes. I used census tracts because they were the smallest geographic units I could download with the tidy_census package, which helped create a more granular look at the community like the regional managers wanted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*l8p8qJejxrcqFP2WudJs-Q.png" /><figcaption>Age map with library branch location marker popup selected. Popup shows statistics found using data from the US Census Bureau. Code create the interactive maps and statistics can be found at: <a href="https://github.com/OpenDataLiteracy/SPL-KO">https://github.com/OpenDataLiteracy/SPL-KO</a>.</figcaption></figure><p>Since there was so much information that I wanted to include in the maps, I looked for an R package that would allow me to create interactive maps that could limit the amount of information on the screen at any one given time. I found the <a href="https://rstudio.github.io/leaflet/">Leaflet</a> package, which creates colored, interactive maps with popups and layers. Leaflet was able to read the data I downloaded from the API and create maps with colors based on selected values. I was also able to add a layer with location markers for each SPL branch, add different base color layers, add zoom buttons for each region, add legends, and add popups for each census tract and branch marker. In total, I created four different maps, age, median household income, language spoken at home, and school enrollment type (private versus public school). For more information about how I created these maps, feel free to look at my documented R code that I uploaded into this project’s GitHub repository at: <a href="https://github.com/OpenDataLiteracy/SPL-KO">https://github.com/OpenDataLiteracy/SPL-KO</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*CeYP8v5rCFc7cVoscYcISg.png" /><figcaption>The map dashboard created for this project can be found at: <a href="https://kostler.shinyapps.io/SPL-Seattle-Census-Data/">https://kostler.shinyapps.io/SPL-Seattle-Census-Data/</a>. All maps are publicly accessible and interactive.</figcaption></figure><p>Though the maps looked great with in the R Markdown Notebook that I had created, their format was not very shareable. To share the maps easily with others, I used a R package called <a href="https://shiny.rstudio.com/">Shiny</a> to create a map dashboard. Shiny takes the R code I created and converts it into a browser friendly application that functions exactly as it did in my R notebook, while avoiding the clutter of code. To make the dashboard truly shareable, I uploaded my Shiny app onto <a href="https://www.shinyapps.io/">shinyapps.io</a>. Shinyapps.io is hosted by RStudio and gives your Shiny app a stable URL that can be easily shared with others. All the maps remain interactive and only require the URL for access by anybody. My map dashboard is available at: <a href="https://kostler.shinyapps.io/SPL-Seattle-Census-Data/">https://kostler.shinyapps.io/SPL-Seattle-Census-Data/</a>. With shinyapps.io, I am able to update my code on my computer and reupload the changes to the URL location.</p><p><strong>Comparison with Internal Dataset</strong></p><p>While the maps provide some insight on the communities around SPL branches, I wanted to find a way to incorporate some of the internal data that is collected by SPL. To compare the census data to the actual population that is using the libraries, I used a dataset with library account use counts divided by each patron age divided by each branch location. For the most accurate comparison, I limited the data to only the counts from 2017 and then grouped the ages into the same ranges I used in the census data analysis. Using R, it was relatively easy to group the data together by each branch and find a median age and the same percentages of population statistics I found for the census data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*8uHNpraSsSQw7scq7Ia8IQ.png" /><figcaption>Example of comparison table from reports created for regional managers. Table shows statistics found from the internal SPL dataset and the census data for age.</figcaption></figure><p>Overall, the statistics found with the internal dataset were pretty close to the census statistics for most of the branches. There were a few differences between the two datasets, like one branch location’s internal dataset showed that the population that was using their library cards was on average younger than the median general population that lived around that branch. The user base for this library could be younger because they have a lot of young adult or children’s programs or maybe they have a lot of schools around their branch, so students visit after class. I did not delve too deep into the possible reasoning between the differences between the two datasets, but I provided reports with both the census data and internal datasets for SPL staff in the Northeast and Southeast regions so that SPL staff could investigate possible factors. I also gave the R code for the internal dataset to my SPL mentor for future use and published my code for the census data in this project’s GitHub repository. Hopefully library staff will be able to look at these materials and use the differences in the data to inform them of possible factors in their planning process.</p><p><strong>Next Steps</strong></p><p>Now that this part of the project is finished, the next step for SPL will be distributing the map dashboard and reports for use by staff at each branch. Though this project focused on the needs for the northeast and southeast regions, the maps provide statistics for all the branches and can be used by anyone interested in Seattle. The map dashboard and project repository both have public URLs that can be shared with anyone and could be used in annual reports about demographics served by SPL, in policy advocacy, or even with the SPL Foundation. In addition to sharing the deliverables of this project, feedback from staff about the maps and reports should be collected to inform future improvements of the maps and other data projects.</p><p>As for next steps for ODL, I plan on continuing parts of this project as an independent study this next quarter as a part of my Master of Library and Information Science program. I would like to publish a journal article about the use of census/open data in public libraries, so that other researchers and library workers can build on the work I have done this summer. I also plan on producing a <a href="https://mybinder.org/">Binder</a> instance or something similar to create an interactive code environment that does not require downloading software to use and play around with the code. This project was a small step in using open data in public libraries and I hope that other libraries will be able to use what I have done in their own workflows. All software I used in this project was open source and anyone can download R, RStudio, and the census data I used or modify the code I created. Publishing open data is a great practice for libraries but using external open datasets can also help create the best services possible for the community.</p><p>Seattle Census Data Map Dashboard: <a href="https://kostler.shinyapps.io/SPL-Seattle-Census-Data/">https://kostler.shinyapps.io/SPL-Seattle-Census-Data/</a></p><p>Project GitHub Repository: <a href="https://github.com/OpenDataLiteracy/SPL-KO">https://github.com/OpenDataLiteracy/SPL-KO</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa3f9a96f3be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/using-open-data-to-understand-communities-around-seattle-public-libraries-fa3f9a96f3be">Using Open Data to Understand Communities Around Seattle Public Libraries</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Laying the Groundwork for Transportation Research Data Management]]></title>
            <link>https://medium.com/open-data-literacy/laying-the-groundwork-for-transportation-research-data-management-b8fd222a9d52?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/b8fd222a9d52</guid>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[transportation-research]]></category>
            <category><![CDATA[data-management-plan]]></category>
            <category><![CDATA[open-government]]></category>
            <dc:creator><![CDATA[Joan Hua]]></dc:creator>
            <pubDate>Mon, 16 Sep 2019 18:48:49 GMT</pubDate>
            <atom:updated>2019-09-16T18:48:49.107Z</atom:updated>
            <content:encoded><![CDATA[<p>The process of data curation is about providing high quality data that are reusable, accessible, and ready to be archived for long-term preservation. Active and careful human intervention is key throughout this process — from organizing, describing, cleaning, contextualizing, to preserving, weeding, and removing. For this summer’s <a href="https://odl.ischool.uw.edu/">Open Data Literacy</a> internship at the Washington State Department of Transportation (WSDOT) via the University of Washington Information School (UW iSchool), I tackled the “problem” of data management planning for research data at WSDOT Research &amp; Library Services. This experience has especially reinforced in my mind the idea that much of data management and curation is for the most part a social problem and less a technology problem. I believe this is why library and information professionals make valuable contributions in this area. We are trained to examine information needs and information seeking behaviors and solve problems with human-centered approaches.</p><p>The problem statement I received at the start of my project says that “WSDOT lacks a defined process for creating data management plans” and that while data resources have been developed and managed according to the needs of individual business units, the organization “[does] not have an accurate picture of the nature of these data and information resources (suggesting a high likelihood of duplicative or even conflicting data), nor how they are being managed.”</p><p>Research data, in particular, occupy a unique area of data resources at WSDOT. They are not captured by the WSDOT Data Catalog (Data or Term Search, DOTS), Data Warehouse, or Data Library. Currently, the tangible output of WSDOT research exists in the form of final narrative reports, and these WA-RD reports are published on the <a href="https://www.wsdot.wa.gov/Research/Reports/default.htm">agency’s website</a>. Once cataloged and published on wsdot.wa.gov, the research is considered complete. Research data, on the other hand, are not managed by WSDOT as renewable assets and are not integrated as part of the research procedures. Research data are made discoverable and accessible to neither internal WSDOT personnel, contract researchers, nor the public.</p><p>To investigate the problem statement, I can parse it into more granular problems to tackle with a socially minded approach:</p><p><strong>Problem 1</strong>: We need to improve upon the ways in which researchers independently describe and manage their datasets, and we need to fill in gaps where datasets are missing to tell the whole story of a research project. Why datasets are collected and managed the way they are now — inconsistent from one research project to another — is a social question.</p><p><strong>Problem 2</strong>: We need to further define what kinds of data we are looking to publish. What’s the general understanding among the research teams when we mention publishing complete datasets that support a discrete research project? What version(s) of datasets can best facilitate reuse? What kinds of datasets can we feasibly collect from researchers and package into sets of digital objects? In this problem, user needs, perceptions, and viability make up the core questions.</p><p><strong>Problem 3</strong>: How do we ensure that the datasets associated with research projects are suitable for open publication, and according to whom? Considerations of sensitive data, data ethics, and liability issues at a government agency like WSDOT can very much be a social problem centered around human concerns.</p><p><strong>Problem 4</strong>: Do decision makers recognize the value of research data and the work to care for them before and after publication? Individuals who have responsibilities in the various stages of research data management and open data publication need to have adequate resources and institutional support in order to succeed and sustain the work.</p><p>These are all messy inquiries that take time and larger cultural shifts to answer. For the Open Data Literacy project, I aimed to produce tangible tools, such as a data management plan (DMP) template, data inventory starter file, and a division of responsibilities worksheet, that will help guide WSDOT Research &amp; Library Services in the next steps in setting and meeting its short- and long-term goals.</p><figure><img alt="Image of trees planted in rows" src="https://cdn-images-1.medium.com/max/640/1*eTQ029alslLLT3WhGMFngw.jpeg" /><figcaption>Contractor crews working for the WSDOT SR 530 reconstruction strategically designed the layout of the 43 trees, 2014. Photo from <a href="https://flic.kr/p/psqdjB">WSDOT flickr</a> (CC BY-NC-ND 2.0).</figcaption></figure><h3>Align with national guidelines and peer organizations</h3><p>To do so, I focused on seeking alignment and avoiding reinventing the wheel. There are existing guidelines to help address some of the questions. For example, with reference to problem 2, the U.S. Department of Transportation (USDOT) <a href="https://www.transportation.gov/mission/open/official-dot-public-access-plan-v11">Public Access Plan</a> requires that final research data be made publicly accessible. With reference to problem 3, the WSDOT Open Data Committee has been carefully evaluating ethical and liability issues surrounding open data publication at the agency, and it recently completed a final draft of a detailed and comprehensive Open Data Risk Register. In addition, with regard to sensitive data, the Washington State <a href="https://ocio.wa.gov/policy/securing-information-technology-assets-standards">OCIO policy 141.10 section 4</a> has classified data into four categories based on publishing restrictions and how the data must be handled. These are existing policies and guidelines that should be consulted and followed. The purpose of a project-level DMP, then, is to have a document and an opportunity for PIs and Research Managers to determine, based on the OCIO classification, whether or not certain datasets need to be excluded from open publication and specify these decisions and sensitivity levels in the DMP.</p><p>The issue of managing research data assets is receiving increased attention at other state DOTs. And these peer organizations are confronting similar issues in parallel with WSDOT. Beyond national guidelines, it is helpful to compare practices at other state DOTs and look to them for resources.</p><p>Among state DOTs, I found that Wyoming DOT has the most comprehensive data management planning documents, accompanied by an agency metadata schema, a data dictionary, and a master contract for research projects containing language addressing research data management. These documents are included as part of WyDOT’s <a href="http://www.dot.state.wy.us/home/planning_projects/research-center/guidelines-and-evaluations.html">Research Center Guideline</a> (last revised in June 2018). Missouri is one other state whose DOT has followed WyDOT’s model and created its own research DMP template (finalized August 2018) and a suite of <a href="https://www.modot.org/information-researchers">resources for MODOT researchers</a>.</p><h3>Tailor to WSDOT-specific needs</h3><p>Creating a template for WSDOT research DMPs, I focused on ensuring standardization. The result is a template that closely resembles that of other state DOTs and even research institutions. Once I had the necessary structure, I thought about what kinds of customization this DMP template, to be used specifically for research projects, would need in order to ensure consistency across research projects. What are the decisions that can be made at the organizational level, so that it does not fall on researchers and PIs to come up with their own solutions, which would likely end up introducing redundancies or unwanted deviations?</p><p>One area to customize with more specific instructions, I believe, is the type of research datasets that should be submitted (problem 2). As mentioned above, the USDOT Public Access Plan addresses specifically final research data. “Final research data” appears to be the standard language in the DMP examples from WyDOT and MODOT, as well as the <a href="http://depts.washington.edu/pactrans/research/data-management/">Pacific Transportation Consortium</a>. WyDOT defines final research data as “recorded factual material commonly accepted in the scientific community as necessary to validate research findings.” It goes on to give examples of what to exclude, such as “preliminary analyses,” “laboratory notebooks,” “communications with colleagues,” and “partial datasets.”</p><p>Knowing the national standard, it may be beneficial for WSDOT to refine the specific meaning of final research data within the agency and decide whether or not that is the desirable scope that would best serve its audience and data users. Would final datasets, as opposed to raw, less manipulated datasets (resulting, for example, from experiments and simulations), be more reusable to the research community? To determine which version is the most reusable and useful for supporting research findings, WSDOT may need to build use cases to understand how the agency’s open research data may be used and by whom. Such an investigation would also strengthen the argument for treating research data as valuable assets and ensure long-term support (problem 4).</p><p>One way to approach this is to systematically survey researchers working on WSDOT research in the current or recent biennium and gain a better understanding of the data management practices and behaviors in accessing and depositing research data. This activity would lead us back to addressing problem 1 and back to user behaviors and management practices. This summer, I conducted a preliminary assessment of the six research projects, where I discovered a range of practices and familiarity with DMPs and open data publishing. I asked each project’s PI or PhD student researcher to fill out a preliminary assessment about their data management practices. In our one-on-one, loosely structured conversations, I asked about data characteristics (e.g., attributes, timeline for collecting, expectations for storage). When possible, they gave me feedback on a draft DMP template. Going forward, a comprehensive assessment across WSDOT research projects may help inform the implementation of DMP requirements and detect gaps.</p><h3>Laying the groundwork</h3><p>At the conclusion of this summer Open Data Literacy project, three important open data documents are being finalized concurrently in August 2019 by the WSDOT open data committee: the Risk Register IT Open Data Risks, the executive order on open data publication, and the Open Data Publication Manual. This development shows promising and emerging traction in open data publishing at the state DOT level. For future next steps, my recommendations for WSDOT Research &amp; Library Services included implementing a research DMP template, integrating data management as part of the research procedures and project management, strategically prioritizing research projects based on funding programs, and evaluating repository options for depositing data to be openly published.</p><p>WSDOT’s research data serve two important communities that benefit from open data. One comprises users of government information and civic data and another the scientific community, as WSDOT research produces engineering data, environmental and land use data, materials science data, and more. The effective management, open publication, and long-term care of these data would benefit a range of stakeholders, including the public — promoting democracy, accountability, and innovation — and other transportation and academic researchers doing similar work. Finally, implementing strategies in managing research data would not only be a proactive step to anticipate future requirements, but also an ideal way to ensure assets generated by the agency are built to be renewable and effective information resources.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8fd222a9d52" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/laying-the-groundwork-for-transportation-research-data-management-b8fd222a9d52">Laying the Groundwork for Transportation Research Data Management</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Opening Rural Library Data: Applying Coursework to the Field]]></title>
            <link>https://medium.com/open-data-literacy/opening-rural-library-data-applying-coursework-to-the-field-3137ce64c187?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/3137ce64c187</guid>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[public-libraries]]></category>
            <category><![CDATA[data-curation]]></category>
            <dc:creator><![CDATA[Lillian Curanzy]]></dc:creator>
            <pubDate>Wed, 04 Sep 2019 17:49:04 GMT</pubDate>
            <atom:updated>2019-09-04T17:49:04.835Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NTJRGwODFfXQ_y2UA2Bv2Q.png" /><figcaption>Snake River, Clarkston, WA</figcaption></figure><p>Asotin County Library (ACL) has introduced an open data initiative that will provide public access to civic data collected by local government agencies. Library staff members are well suited to provide open data support to their communities by working as <a href="https://www.urisa.org/clientuploads/directory/Documents/Journal/Vol28_final.pdf">civic infomediaries</a>. Despite the natural relationship between open data and public libraries, it remains uncommon for libraries to openly publish their own data. The scarcity of open library data can be attributed to demands on staff time, a perceived lack of data usage by external groups, or an overestimation of the skills required to process and publish data. This post discusses the methods, tools, and standards used to prepare and openly publish library data.</p><p>Libraries collect and use data for a variety of purposes. Circulation, holdings, and bibliographic data describe resources — physical and subject characteristics, location, authorship, and use history. Libraries collect data around programming and other services that track desired audience, program themes, and attendance. Operational data include financial reports, salaries, funding, and facilities information. These domains inform various internal activities like budget planning, collection development, staffing, and service offerings. However, there are definite applications for each of these domains across multiple user groups.</p><p>I was able to utilize the methods and tools covered in the data curation curriculum at the University of Washington iSchool to complete an internship with ACL and Open Data Literacy (ODL) over the summer. Two significant goals of the internship were to publish Asotin County Library data to Washington State’s open data portal, data.wa.gov, and to create documentation that will streamline the publication process of future open publishing in Asotin County — both by the library and other agency partners.</p><p>­­­­­</p><p>A terminal project in the data curation curricula at the iSchool asked students to design the curation protocol for a data repository. We practiced weighing, defining, and assigning various metadata elements from several well-used schemas. This gave us insight into how proper metadata use promotes data sharing. Furthermore, the understanding of why repositories require certain elements to be filled out by data providers guided the development of a metadata template.</p><p>In order to make the data preparation and publication process easier for future contributions, it made sense to create a template for metadata creation that is broadly designed for use with Socrata repository software. A principal objective of the metadata template is that it can be used by library staff to publish prepare and publish data from other civic agencies.</p><p>In addition to the record-level description and dataset metadata, it also captures context and preserves primary data. When filled out prior to data ingest, this template supplies the data partner with complete and accurate documentation which will facilitate discovery and reuse. It also serves as a record for the dataset owner of what data has been uploaded to the portal and what it takes to replicate the process.</p><p>While thorough metadata is essential for data sharing, financial concerns can limit how much staff time is devoted to documentation. Economic sustainability was taken into account when designing the template. A cost analysis is included in the requested information for each dataset. The value of a dataset can be appraised by considering its impact and likelihood of reuse. Administrators can leverage this value and cost estimate to inform their organization’s open data plan.</p><p>The next goal, publishing datasets to the state data portal, required some preliminary steps including the selection of datasets to publish. Data privacy and other ethical considerations — significant aspects of Fundamentals of Data Curation — were instrumental in shaping the kind of data that was ultimately published. The question of data demand and the likelihood of reuse also factored into data selection.</p><p>In order to predict potential data reuse, I drafted comprehensive use cases related to multiple stakeholders. A use case is a question answered or problem solved through access to the dataset at hand. Informed by case studies and personal experiences, these use cases were among the most advantageous steps in the data preparation process. This practice was emphasized in the cumulative final project of Advanced Data Curation. Not only do they work to justify open publishing by illustrating how the data could be used by external stakeholders, but they can also guide data collection and retrieval.</p><p>Once the data were selected, based on use cases and <a href="https://data.seattle.gov/Community/Checkouts-by-Title/tmmm-ytt6">open library data precedent</a>, they needed to be transformed from how they were exported from the library’s database to conform to tidy data expectations. Version control was a vital component at this stage of the project. The original spreadsheet as it was exported from the database is saved in the template, but also in separate files on the computer and in a dedicated web-based repository for the project. <a href="http://openrefine.org/">OpenRefine</a>, an open source tool for working with tabular data, was integral in transforming the data while simultaneously logging those changes in a manner that will aid future automation.</p><p><a href="https://vita.had.co.nz/papers/tidy-data.pdf">Tidy data</a> concepts were covered broadly in Advanced Data Curation. When data is clearly formatted, it can be shared and analyzed most effectively. Therefore, tidy data standards were applied to the public library datasets that were chosen to be published. This project allowed me to implement proper data formatting standards, but it also gave me cause to investigate the Resource Description and Access (RDA) and Library of Congress rules that govern how bibliographic data is stored.</p><p>Through this project, I learned that, other than having a knowledge of data best practices, the skills needed to prepare and publish open data are widely possessed by library staff. We work with databases and information organization daily. However, the courses I completed at the iSchool instructed me in the importance of complete documentation, tidy data standards, version control, and preservation activities.</p><p>Moving forward, a few challenges remain. Further automation in the form of adaptable Python scripts will allow datasets to be easily formatted. The API provided by the library’s catalog software can be used to routinely retrieve data. These steps toward automation will require knowledge of systems and coding but once these protocols are in place, demands on staff time will decrease. Despite increasingly effective automation, it’s clear from my experience with ODL and coursework that human intervention remains the most integral part of successful data curation and sharing.</p><p>Moving forward, a few challenges remain. Further automation in the form of adaptable Python scripts will allow datasets to be easily formatted. The API provided by the library’s catalog software can be used to routinely retrieve data. These steps toward automation will require knowledge of systems and coding but once these protocols are in place, demands on staff time will decrease. Despite increasingly effective automation, it’s clear from my experience with ODL and coursework that human intervention remains the most integral part of successful data curation and sharing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3137ce64c187" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/opening-rural-library-data-applying-coursework-to-the-field-3137ce64c187">Opening Rural Library Data: Applying Coursework to the Field</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Facing the Flood: Assessing Metadata Quality on Washington’s Open Data Portal]]></title>
            <link>https://medium.com/open-data-literacy/facing-the-flood-assessing-metadata-quality-on-washingtons-open-data-portal-d76312d767fe?source=rss----c29559733c9f---4</link>
            <guid isPermaLink="false">https://medium.com/p/d76312d767fe</guid>
            <category><![CDATA[metadata-assessment]]></category>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[metadata-quality]]></category>
            <dc:creator><![CDATA[Andrew Mckenna-Foster]]></dc:creator>
            <pubDate>Sun, 25 Aug 2019 20:32:53 GMT</pubDate>
            <atom:updated>2019-08-25T20:32:53.579Z</atom:updated>
            <content:encoded><![CDATA[<p>Washington State’s open data portal (<a href="https://data.wa.gov/">data.wa.gov</a>) was launched around 2009 and is now one of the largest and more well-established state portals in the country. It currently contains over 800 datasets covering 14 categories. Any of the state’s <a href="https://data.wa.gov/dataset/Washington-State-Agencies-Listing/hsx3-pn9g">197 agencies</a> can publish to the portal giving it a broad scope and making it a valuable resource for the state. However, there is no central quality control and while this laissez-faire system is likely a driver of the portal’s success, the consequence is a proliferation of poor-quality metadata. This has made finding the high-quality data more difficult and has reduced the reusability of datasets on the portal in general. The focus of my <a href="https://odl.ischool.uw.edu/">Open Data Literacy</a> internship this summer was understanding the extent of the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MF4S8HaUQqVa9foEHdb8Mw.jpeg" /><figcaption>This dataset has some of the available metadata filled out.</figcaption></figure><p>Consider this scenario. If you lived in Washington State and wanted to see some data on water quality tests, you might decide to bypass a Google search and head straight to data.wa.gov. However, a search for “water tests” will return <a href="https://data.wa.gov/browse?q=water+test&amp;sortBy=relevance">over 500 results</a>, many of which are pdf documents concerning lead tests in school water systems. Those documents, while very important, barely meet the first star of the <a href="http://opendatahandbook.org/glossary/en/terms/five-stars-of-open-data/">five stars of open data</a>. As savvy as you are, you filter the results to <a href="https://data.wa.gov/browse?limitTo=datasets&amp;q=water+test&amp;sortBy=relevance">just datasets</a> and get four results, one of which shows <a href="https://data.wa.gov/Health/WA-School-Water-Lead-Test-Data/i3jn-y8vx">lead test data</a> for all schools in the state. Not exactly what you started looking for but still interesting. Closer inspection shows that the metadata for that dataset is partially complete with a short description, the name of the owner, and the date updated. Those metadata are enough to convey what the data are about but there are still key pieces of information missing, such as how frequently the data are updated, what license the data are published under, and what each column in the dataset means (the data dictionary). These gaps might mean you still need to contact the dataset owner to get more information before using the data. As it turns out, despite missing those metadata elements, this dataset is one of the higher quality datasets available on data.wa.gov.</p><p>Data.wa.gov is not alone in its metadata problems; quality issues are a <a href="https://blog.okfn.org/2017/05/31/open-data-quality-the-next-shift-in-open-data/">global problem in open government data portals</a>. In 2016, the portal software company <a href="https://www.tylertech.com/products/socrata">Socrata</a><a href="https://benchmarkstudy.socrata.com/Developer-Survey/Developers-Rate-the-Current-State-of-Gov-Data-Acce/4j6z-qhyp">,</a> on which data.wa.gov is built, <a href="https://benchmarkstudy.socrata.com/Developer-Survey/Developers-Rate-the-Current-State-of-Gov-Data-Acce/4j6z-qhyp">surveyed developers</a> on their perceptions of open government data (OGD) and found that over half thought that metadata is inconsistent between datasets, data is not up to date, and data is not clean or accurate.</p><p>To address metadata quality issues on data.wa.gov, the WA Office of the Chief Information Officer (OCIO), which manages data.wa.gov, approached the <a href="https://www.sos.wa.gov/library/">Washington State Library</a> (WSL) and the Open Data Literacy program for help. My internship this summer was the first step in a potential partnership between the OCIO and the WSL to curate data.wa.gov to make it more usable.</p><p>This project consisted of two components:</p><ol><li>Interview state agencies to understand data publishing behavior</li><li>Assess the current state of metadata quality on the portal</li></ol><h3>Interviews</h3><p>I interviewed eight agencies and one organization that uses data from the portal. Most agencies held positive views of the data.wa.gov and it became clear that every agency uses the portal to meet their unique data needs. In fact, publishing behavior is only generalizable to the extent that it is unique to every agency. Publishing behavior included publishing for</p><ul><li><strong>Specific users </strong>— Example: Healthcare Provider Credential data for hospitals</li><li><strong>Transparency </strong>— Example: State Art Collection locations</li><li><strong>Internal or interagency use</strong> — Example: Salmon Recovery data</li></ul><p>Rather than individual citizens, the primary users are other agencies, local governments, federal agencies, and 3rd parties such as businesses, nonprofits, and the media. Some agencies know exactly who their main users are while other agencies can only guess. Seven out of the eight interviewed publishers expect to continue or increase their publishing on the portal.</p><blockquote><strong>Publishing behavior is only generalizable to the extent that it is unique to every agency</strong></blockquote><p>What does this mean for a potential curator? The varying needs and publishing behaviors of the agencies suggest a curator will need to work closely with publishers to encourage better metadata practices. Any sweeping attempts to increase metadata quality on the portal will affect agencies in different ways and may produce unintended consequences.</p><h3>Metadata Assessment</h3><p>There are many ways to assess metadata quality (e.g. <a href="https://www.sciencedirect.com/science/article/pii/S0740624X16301319">Kubler et al. 2018</a>). I assessed metadata quality by examining completeness and understandability using a combination of variables common in multiple other studies.</p><p>While the OCIO provides excellent guidelines on open data best practices for data publishers, agencies are only required to fill out the title of a dataset on data.wa.gov. Perhaps for that reason, over half of the published datasets are missing 50% or more of the 11 available metadata elements. About 19% of datasets only have the title. The least filled out elements include license, posting frequency (how often the dataset is updated), period of time, originator, and the metadata language (typically English).</p><figure><img alt="Four charts of summary statistics of metadata existence and understandability on data.wa.gov." src="https://cdn-images-1.medium.com/max/1024/1*8M_jrQ1WwWVponC3p9bp1g.jpeg" /><figcaption>Metadata existence and understandability on data.wa.gov for a sample of datasets from August 5, 2019. Over half of datasets fill out less than half of the available metadata elements and license and posting frequency are some of the least filled out. About 40% of dataset titles are difficult to understand.</figcaption></figure><p>It is clear that agencies only fill out a fraction of the metadata, so it would be helpful if they were filling out metadata that provided the most useful information. I selected five elements that if filled out properly would allow a dataset to pass the <a href="https://en.wikipedia.org/wiki/CRAAP_test">CRAAP test</a>. These are attribution (publishing agency), description, category, posting frequency, and license. Of these elements, the former three are filled out in some combination in about 60% of datasets, but 69% of datasets are missing posting frequency and 67% are missing license. A full 21% do not include any of these five elements.</p><p>So, while it’s impressive if an agency fills in some metadata, if the information they include is incomprehensible, that is just as bad as not filling it out in the first place. I looked at a sample of 112 datasets to assess the understandability of metadata. If information was confusing or incorrect it was scored as difficult to understand. I found that forty percent of dataset titles are enigmatic. Half of the sampled datasets had confusing temporal or spatial information, often both. Only 25% of datasets include a data dictionary (column descriptions) that helps understand the data itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ZDjfWxksmyD_CafWdxqIdw.jpeg" /><figcaption>Curation efforts should focus on areas that would most efficiently improve the overall quality of data on data.wa.gov</figcaption></figure><p>The search experience and usability of data.wa.gov would be much improved if every dataset had at the least all five core elements completed with understandable information. At the moment, only seven percent meet all these criteria and 48% are either missing information or have enigmatic information in one to two core elements. A curator could efficiently improve a significant portion of the metadata needs on the portal by focusing on this 48%.</p><p>I also noted other curation needs in addition to metadata quality. At least 13% of sampled datasets contained the same data as one or more other datasets, but from a different time period. Datasets in a time series should be combined to one dataset that is regularly updated. About eight percent of datasets are test or dummy datasets that should be unpublished or removed. Three percent of datasets do not meet the <a href="https://ocio.wa.gov/programs/open-data/guidance-open-data-definitions">OCIO’s definition of data</a> and are candidates for removal.</p><h3><strong>Recommendations</strong></h3><p>The takeaway from this work is that data.wa.gov is an important resource for state agencies but more than half the datasets need metadata improvements or other curation work. It is tempting to compare the portal to a centrally managed library catalog of books in need of development and weeding. However, this comparison is not appropriate because a curator of the portal cannot control what gets published or removed. Instead, a curator will have to work closely with state agencies to collaboratively fix and update metadata.</p><p>Here are specific recommendations to help guide a future curator:</p><p><strong>Focus work on the five core metadata elements</strong></p><ul><li>Include controlled vocabularies for Data Provided By and Posting Frequency</li><li>Provide metadata explanations to help publishers fill out metadata elements</li><li>Work with publishers to fix existing metadata</li></ul><p><strong>Remove datasets when necessary</strong></p><ul><li>Implement a policy to identify datasets for removal</li><li>Create a procedure that removes datasets in a transparent way</li></ul><p><strong>Evaluate curation efforts</strong></p><ul><li>Run the assessment script available on the ODL GitHub repository several times a year to evaluate how curation efforts are affecting metadata quality</li></ul><h3><strong>Next Steps</strong></h3><p>This project was a massive learning experience for me and an introduction to new challenges facing open data portals. There is much more behind this analysis and it is all available on the ODL GitHub repository. I hope to continue working with WSL to study dataset removal policies in OGD portals and I am looking forward to learning what WSL curation efforts teach us about improving metadata quality.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d76312d767fe" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open-data-literacy/facing-the-flood-assessing-metadata-quality-on-washingtons-open-data-portal-d76312d767fe">Facing the Flood: Assessing Metadata Quality on Washington’s Open Data Portal</a> was originally published in <a href="https://medium.com/open-data-literacy">Open Data Literacy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>