47 lines
4.9 KiB
HTML
47 lines
4.9 KiB
HTML
<!--
|
||
.. title: 5 Things I learned at IASSIST
|
||
.. slug: iassist-report
|
||
.. date: 2017-05-26 14:08:25 UTC-04:00
|
||
.. tags: conference report
|
||
.. category: Professional Life
|
||
.. link: https://gitlab.com/VickySteeves/personal-website/blob/master/posts/2017-05-26.html
|
||
.. description:
|
||
.. type: text
|
||
-->
|
||
|
||
<!DOCTYPE html>
|
||
<html>
|
||
<body>
|
||
|
||
|
||
|
||
<p><a href="https://data-services.hosting.nyu.edu/five-things-we-learned-at-iassist-2017/">See original posting here.</a></p>
|
||
<p>I just got back from <a href="http://www.iassist2017.org/">IASSIST 2017</a> and I have to say...I was very impressed! This year, IASSIST (The International Association for Social Science Information Services & Technology) 2017 was in Lawrence, Kansas from May 23-26, 2017. True to it's name, this conference brought people from all around the world:</p>
|
||
|
||
<blockquote class="twitter-tweet" data-lang="en">
|
||
<p dir="ltr" lang="en">A map of <a href="https://twitter.com/hashtag/iassist17?src=hash">#iassist17</a> attendees! <a href="https://t.co/V6fV5Ey5iv">pic.twitter.com/V6fV5Ey5iv</a></p>
|
||
— Vicky Steeves (@VickySteeves) <a href="https://twitter.com/VickySteeves/status/867383320371441665">May 24, 2017</a></blockquote>
|
||
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
|
||
|
||
<p>These are my top 5 favourite takeaways from IASSIST 2017:</p>
|
||
<!-- TEASER_END -->
|
||
<ol>
|
||
<li>An interesting project that was recently published in PLoS One, <em><a href="http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0178261">Research data management in academic institutions: A scoping review</a></em>, which was presented as a poster during the conference. This was essentially a systematic review that was designed to describe the volume, topics, and methodologies of existing scholarly work on research data management in academia. They looked at 301 articles out of the original 13,002 titles. They made the data (the text, methods, etc.) available on Zenodo: <a href="https://zenodo.org/record/557043">Dataset for: Research data management in academic institutions: a scoping review</a>!</li>
|
||
<li><a href="https://rstudio.github.io/packrat/">Packrat</a>: a dependency manager in R that looks to solve the problem of "dependency hell" -- that software depends on other packages to run, and these change all the time with no warning, and these changes can break existing code. Packrat works by making a project specific package library, rather than using R's native package manager (which updates libraries as they are released). This means the R code can be packaged up with its dependencies. However, it doesn't pack the version of R, which can pose problems.</li>
|
||
<li>Sam Spencer of the <a href="http://aristotlemetadata.com/">Aristotle metadata registry</a> gave a great talk about work done in the open metadata space, giving a strong usecase: government data hosted on <a href="https://data.gov.au/">data.gov.au</a>. He shocked the crowd by keeping metadata in CSV format. He asks for 10 basic fields of metadata from users in CSV form -- and there it stays! He mentioned he was scared to admit this to this crowd, but it's yielded good things for him, including data linkages without explicitly doing linked data. He spoke specifically about using this for geo-metadata; you can check out how it's worked out on this <a href="http://nationalmap.gov.au/">map</a>.</li>
|
||
<li>One of the more interesting talks I went to was about digital preservation of 3D data! The speaker laid out 5 methods of creation: freeform (like CAD), measurement, observation, "mix," and algorithm/scanning or photogrammetry. 3D data is difficult to preserve mainly because of a lack of standards, particularly metadata standards. The speaker presented a case study that used Dublin Core as a basis for metadata for the Awash National Park Baboon Research Project's 3D data.</li>
|
||
<li>The Digital Curation Network gave an update on their initial planning grant. The DCN allows universities to staff share on data curation, which often is too much for one data curator. The first grant allowed six universities to test how local curation practices translates into a network practice. The next phase includes implementation of the network, during which time other institutions can join. The network also came out with centralized steps for curation:
|
||
<ol>
|
||
<li><span style="font-weight: 400;">Check data files and read documentation</span></li>
|
||
<li><span style="font-weight: 400;">Understand/try to understand the data</span></li>
|
||
<li><span style="font-weight: 400;">Request missing information or changes</span></li>
|
||
<li>A<span style="font-weight: 400;">ugment the submission with metadata</span></li>
|
||
<li><span style="font-weight: 400;">Transform file format for reuse and long-term preservation</span></li>
|
||
<li><span style="font-weight: 400;">Evaluate and rate the overall submission using FAIR </span></li>
|
||
</ol>
|
||
</li>
|
||
</ol>
|
||
|
||
</body>
|
||
</html>
|