This workshop is full
Speaker(s)
- {% if page.type == 'workshop' %} - {% for speakerId in page.speakers %} - {% if speaker != 0 %} - - {% assign speaker = site.data.speakers_final[speakerId] %} - {% if speaker %} - - - {% else %} - - {% assign speaker = site.data.speakers_temp[speakerId] %} - {% if speaker %} -
- {{ speaker.name }}
-
- {% if event.groupId != 'key-open' and event.groupId != 'key-close' %}
- {{ speaker.Name }}
- {% endif %}
-
+ {% if event.groupId != 'key-open' and event.groupId != 'key-close' %}
+ {{ speaker.Name }}
{% endif %}
-
- {% endif %}
+ Building off of last year’s first Code4Arc event, this pre-conference is an opportunity for the archivists and developers who work with them to talk about archives specific tools, workflows and development, with an emphasis on open-source software. We wish to create a space to talk about how coding for archives may be different than coding for libraries and interaction with cross-domain tools such as repositories, discovery and access systems. Code4Arc is a participatory event and the agenda will be made available in advance for participants to sign up for lightening talks, demonstrations or case studies. We will also have break-out sessions to discuss topics of interest to the participants, for example, workflows, tool integrations, handoffs and metadata conventions. Short community project updates will be available from BitCurator Access, Educopia, Archivematica, ArchivesSpace, AtoM and Islandora.
\ No newline at end of file diff --git a/_posts/2016-03-07-HandsOn-Fedora-4.md b/_posts/2016-03-07-HandsOn-Fedora-4.md index dcbf60b..29bd2ca 100755 --- a/_posts/2016-03-07-HandsOn-Fedora-4.md +++ b/_posts/2016-03-07-HandsOn-Fedora-4.md @@ -11,6 +11,7 @@ date: 2016-03-07 categories: workshops slugTitle: hands-on-fedora-4 title: Hands-On Fedora 4 +slides: '/slides/Workshop-Fedora4.pdf' --- This workshop is a hands-on introduction to: diff --git a/_posts/2016-03-07-Islandora-for-Developers.html b/_posts/2016-03-07-Islandora-for-Developers.html index 980904d..0c78a35 100755 --- a/_posts/2016-03-07-Islandora-for-Developers.html +++ b/_posts/2016-03-07-Islandora-for-Developers.html @@ -1,8 +1,8 @@ --- layout: presentation speakers: -- 5050096501 - 3518211291 +- 5050096501 - 0 - 0 - 0 diff --git a/_posts/2016-03-07-Islandora-for-Managers.html b/_posts/2016-03-07-Islandora-for-Managers.html index 4516a34..9d66409 100755 --- a/_posts/2016-03-07-Islandora-for-Managers.html +++ b/_posts/2016-03-07-Islandora-for-Managers.html @@ -1,9 +1,8 @@ --- layout: presentation speakers: -- 5050096501 - 3518211291 -- 0 +- 5050096501 - 0 - 0 type: workshop diff --git a/_posts/2016-03-07-Migrating-Hydrabased-repositories-from-Fedora-3-to-4.md b/_posts/2016-03-07-Migrating-Hydrabased-repositories-from-Fedora-3-to-4.md index 0535f71..c108019 100755 --- a/_posts/2016-03-07-Migrating-Hydrabased-repositories-from-Fedora-3-to-4.md +++ b/_posts/2016-03-07-Migrating-Hydrabased-repositories-from-Fedora-3-to-4.md @@ -11,6 +11,7 @@ date: 2016-03-07 categories: workshops slugTitle: migrating-hydra-based-repositories-from-fedora-3-to-4 title: Migrating Hydra-based repositories from Fedora 3 to 4 +slides: '/slides/Workshop-Fedora4-Hydra-Migration.pdf' --- Do you have a Hydra-based repository that is still on Fedora 3? diff --git a/_posts/2016-03-08-Gabriel-Weinberg.html b/_posts/2016-03-08-Gabriel-Weinberg.html index 762c55b..d9ba932 100755 --- a/_posts/2016-03-08-Gabriel-Weinberg.html +++ b/_posts/2016-03-08-Gabriel-Weinberg.html @@ -9,12 +9,13 @@ - 0 day: 3 group: key-close -spot: +spot: length: 45 type: talk startTime: 1457446500 endTime: 1457449200 milTime: 09:15-10:00 title: Gabriel Weinberg +slides: '/slides/keynote_ddg_code4lib_7.pdf' --- - \ No newline at end of file + diff --git a/_posts/2016-03-08-Architecture-is-politics-the-power-and-the-perils-of-systems-design.html b/_posts/2016-03-09-Architecture-is-politics-the-power-and-the-perils-of-systems-design.html similarity index 90% rename from _posts/2016-03-08-Architecture-is-politics-the-power-and-the-perils-of-systems-design.html rename to _posts/2016-03-09-Architecture-is-politics-the-power-and-the-perils-of-systems-design.html index 0ab4556..b3f8782 100755 --- a/_posts/2016-03-08-Architecture-is-politics-the-power-and-the-perils-of-systems-design.html +++ b/_posts/2016-03-09-Architecture-is-politics-the-power-and-the-perils-of-systems-design.html @@ -16,5 +16,6 @@ endTime: 1457549100 milTime: 13:25-13:45 title: Architecture is politics: the power and the perils of systems design +slides: '/slides/architecture_is_politics-dre-orphanides.pdf' --- -As the designers and implementers of complex systems (such as websites, discovery tools, and knowledge repositories), we have great -- if sometimes unrealized -- power. And, as Stan Lee says, with great power comes great responsibility. In this presentation we will explore three key lessons in the ethics of systems design, and examine the practical implications of these lessons in the design of your own systems. We'll investigate how design choices can (intentionally or unintentionally) influence user behavior, reveal organizational priorities, and exacerbate or ease conflicts between your interests and those of your users. And we'll discuss how to be mindful of these considerations during the design process in order to ensure that your systems more effectively reflect your values, address your users' needs, and allow both your users and your organization to find success.
\ No newline at end of file +As the designers and implementers of complex systems (such as websites, discovery tools, and knowledge repositories), we have great -- if sometimes unrealized -- power. And, as Stan Lee says, with great power comes great responsibility. In this presentation we will explore three key lessons in the ethics of systems design, and examine the practical implications of these lessons in the design of your own systems. We'll investigate how design choices can (intentionally or unintentionally) influence user behavior, reveal organizational priorities, and exacerbate or ease conflicts between your interests and those of your users. And we'll discuss how to be mindful of these considerations during the design process in order to ensure that your systems more effectively reflect your values, address your users' needs, and allow both your users and your organization to find success.
diff --git a/_posts/2016-03-08-Beyond-the-Bento-Box-Using-linked-data-and-smart-algorithms-to-integrate-repository-data-in-context.html b/_posts/2016-03-09-Beyond-the-Bento-Box-Using-linked-data-and-smart-algorithms-to-integrate-repository-data-in-context.html similarity index 96% rename from _posts/2016-03-08-Beyond-the-Bento-Box-Using-linked-data-and-smart-algorithms-to-integrate-repository-data-in-context.html rename to _posts/2016-03-09-Beyond-the-Bento-Box-Using-linked-data-and-smart-algorithms-to-integrate-repository-data-in-context.html index 69f0c36..3a74de0 100755 --- a/_posts/2016-03-08-Beyond-the-Bento-Box-Using-linked-data-and-smart-algorithms-to-integrate-repository-data-in-context.html +++ b/_posts/2016-03-09-Beyond-the-Bento-Box-Using-linked-data-and-smart-algorithms-to-integrate-repository-data-in-context.html @@ -16,8 +16,9 @@ endTime: 1457558100 milTime: 15:55-16:15 title: Beyond the Bento Box: Using linked data and smart algorithms to integrate repository data in context +slides: '/slides/Beyond_the_Bento_Box.pptx' ---With modern discovery layers, libraries are finally able to integrate all of their content into a single search experience, but fluid discovery across content sources using a single interface is still lacking. Users are typically given one of two options: 1) bento box results where once a user chooses a path they must start their search over to switch content sources 2) federated searches that mash everything together in a muddled mess, hiding the most relevant resources. Using linked data and smart algorithms, we will demonstrate how Marmot is enhancing the open-source Pika discovery layer to create an experience that combines the best of these scenarios. Users looking for books will have the opportunity to discover related digital content at every step as their search evolves. Users researching digitized historic photos will be offered books on the history of the places they’re looking at. This type of fully integrated discovery layer allows users to focus on their primary research objective while revealing previously hidden gems. -
\ No newline at end of file + diff --git a/_posts/2016-03-08-Beyond-the-Keyword-Creative-Search-and-Query-Expansions-based-on-DBpedia.html b/_posts/2016-03-09-Beyond-the-Keyword-Creative-Search-and-Query-Expansions-based-on-DBpedia.html similarity index 89% rename from _posts/2016-03-08-Beyond-the-Keyword-Creative-Search-and-Query-Expansions-based-on-DBpedia.html rename to _posts/2016-03-09-Beyond-the-Keyword-Creative-Search-and-Query-Expansions-based-on-DBpedia.html index 3df999f..7cff090 100755 --- a/_posts/2016-03-08-Beyond-the-Keyword-Creative-Search-and-Query-Expansions-based-on-DBpedia.html +++ b/_posts/2016-03-09-Beyond-the-Keyword-Creative-Search-and-Query-Expansions-based-on-DBpedia.html @@ -16,15 +16,16 @@ endTime: 1457535000 milTime: 09:35-09:50 title: Beyond the Keyword: Creative Search and Query Expansions based on DBpedia +slides: '/slides/Marya_Sawaf.pptm' --- -Does the notion of keyword search and relevance that powers search engines really meet the needs of all searchers? What alternative advanced search features can be implemented to meet fuzzier search needs? +
Does the notion of keyword search and relevance that powers search engines really meet the needs of all searchers? What alternative advanced search features can be implemented to meet fuzzier search needs? -This talk discusses these questions by demonstrating the potential of a new search tool called "Brainforks" in everyday search, scholarly search and book search. +This talk discusses these questions by demonstrating the potential of a new search tool called "Brainforks" in everyday search, scholarly search and book search. -By building an interactive graph of query expansions, the user can take part in a search that is both "exploratory" and "creative". +By building an interactive graph of query expansions, the user can take part in a search that is both "exploratory" and "creative". "Exploratory" search removes the assumption that the searcher has a clearly defined search need and recreates the library browsing experience in your browser. "Creative" or "serendipitous" search allows the searcher to find solutions from other fields that are functionally analogous, so ideas can be shared across disciplines. -Coded in Python, Brainforks makes use of many semantic tools and natural language processing libraries such as NLTK and data from Dbpedia, Wordnet, Faroo and Google Ngrams.
\ No newline at end of file +Coded in Python, Brainforks makes use of many semantic tools and natural language processing libraries such as NLTK and data from Dbpedia, Wordnet, Faroo and Google Ngrams. diff --git a/_posts/2016-03-08-Building-Desktop-Applications-using-Web-Technologies-with-Electron.html b/_posts/2016-03-09-Building-Desktop-Applications-using-Web-Technologies-with-Electron.html similarity index 95% rename from _posts/2016-03-08-Building-Desktop-Applications-using-Web-Technologies-with-Electron.html rename to _posts/2016-03-09-Building-Desktop-Applications-using-Web-Technologies-with-Electron.html index 56d56ae..46bfae2 100755 --- a/_posts/2016-03-08-Building-Desktop-Applications-using-Web-Technologies-with-Electron.html +++ b/_posts/2016-03-09-Building-Desktop-Applications-using-Web-Technologies-with-Electron.html @@ -16,5 +16,6 @@ endTime: 1457556900 milTime: 15:40-15:55 title: Building Desktop Applications using Web Technologies with Electron +slides: 'http://ronallo.com/presentations/c4l16/' --- -Everything that was once a desktop application has gone to the cloud and no one builds desktop applications anymore, right? Wrong. Companies like Github, Slack, and a number of startups are building desktop applications today. Why? I'll show you why desktop applications are still preferred sometimes, how you can use the web technologies you're already familiar with (HTML, CSS, & JavaScript) to build them, and some reasons why you will want to consider creating a desktop application even if you've always written them off in the past. We'll see how easy it is to get started and what's different about this model of programming like how processes can communicate. I'll tie this all back to examples of library and archives use cases for desktop applications.
\ No newline at end of file +Everything that was once a desktop application has gone to the cloud and no one builds desktop applications anymore, right? Wrong. Companies like Github, Slack, and a number of startups are building desktop applications today. Why? I'll show you why desktop applications are still preferred sometimes, how you can use the web technologies you're already familiar with (HTML, CSS, & JavaScript) to build them, and some reasons why you will want to consider creating a desktop application even if you've always written them off in the past. We'll see how easy it is to get started and what's different about this model of programming like how processes can communicate. I'll tie this all back to examples of library and archives use cases for desktop applications.
diff --git a/_posts/2016-03-08-Building-a-userfriendly-authorities-browse-in-Blacklight.html b/_posts/2016-03-09-Building-a-userfriendly-authorities-browse-in-Blacklight.html similarity index 100% rename from _posts/2016-03-08-Building-a-userfriendly-authorities-browse-in-Blacklight.html rename to _posts/2016-03-09-Building-a-userfriendly-authorities-browse-in-Blacklight.html diff --git a/_posts/2016-03-08-Constructive-disintegration--reimagining-the-library-platform-as-microservices.html b/_posts/2016-03-09-Constructive-disintegration--reimagining-the-library-platform-as-microservices.html similarity index 94% rename from _posts/2016-03-08-Constructive-disintegration--reimagining-the-library-platform-as-microservices.html rename to _posts/2016-03-09-Constructive-disintegration--reimagining-the-library-platform-as-microservices.html index 670bc8e..7802403 100755 --- a/_posts/2016-03-08-Constructive-disintegration--reimagining-the-library-platform-as-microservices.html +++ b/_posts/2016-03-09-Constructive-disintegration--reimagining-the-library-platform-as-microservices.html @@ -16,6 +16,7 @@ endTime: 1457550300 milTime: 13:45-14:05 title: Constructive disintegration -- re-imagining the library platform as microservices +slides: '/slides/sebastianhammer.pptx' ---Imagine a world where libraries are free to choose their own ideal combination of vendor-supplied services and open source or home-built custom code. Where traditional core functions like cataloging and circulation can be chosen independently, and can interoperate freely with learning management, scholarly communication, and all the things we haven't even thought of yet. It's a world where libraries and vendors challenge each other to innovate, to explore new opportunities for libraries to bring value, and to reduce costs. @@ -23,4 +24,4 @@ There are many challenges. We need a lean, implementation-driven approach to defining our interfaces and data models, rather than sluggish, do-it-all designed-by committee specifications that are outdated before the first draft is complete. We need to challenge vendors and libraries alike to a dialog about best practices, and we need to build toolsets and platforms to lower the bar of entry, to make it easy for everyone to benefit and contribute. -We would like to discuss these questions and our work on this framework, as well as invite ideas and collaboration.
\ No newline at end of file +We would like to discuss these questions and our work on this framework, as well as invite ideas and collaboration. diff --git a/_posts/2016-03-08-Curate-my-web-crawl-Building-a-multiprocessing-web-crawler-for-ethnographic-research.html b/_posts/2016-03-09-Curate-my-web-crawl-Building-a-multiprocessing-web-crawler-for-ethnographic-research.html similarity index 100% rename from _posts/2016-03-08-Curate-my-web-crawl-Building-a-multiprocessing-web-crawler-for-ethnographic-research.html rename to _posts/2016-03-09-Curate-my-web-crawl-Building-a-multiprocessing-web-crawler-for-ethnographic-research.html diff --git a/_posts/2016-03-08-Getty-Research-Portal-Reboot-Angular-and-Elasticsearch-for-Metadata-Search-Aggregation.html b/_posts/2016-03-09-Getty-Research-Portal-Reboot-Angular-and-Elasticsearch-for-Metadata-Search-Aggregation.html similarity index 93% rename from _posts/2016-03-08-Getty-Research-Portal-Reboot-Angular-and-Elasticsearch-for-Metadata-Search-Aggregation.html rename to _posts/2016-03-09-Getty-Research-Portal-Reboot-Angular-and-Elasticsearch-for-Metadata-Search-Aggregation.html index b6d19d6..0fa6b8e 100755 --- a/_posts/2016-03-08-Getty-Research-Portal-Reboot-Angular-and-Elasticsearch-for-Metadata-Search-Aggregation.html +++ b/_posts/2016-03-09-Getty-Research-Portal-Reboot-Angular-and-Elasticsearch-for-Metadata-Search-Aggregation.html @@ -16,7 +16,8 @@ endTime: 1457547900 milTime: 13:15-13:25 title: Getty Research Portal Reboot: Angular and Elasticsearch for Metadata Search Aggregation +slides: '/slides/getty_GRP_Reboot.pptx' --- -As part of the continuous evolution of library search tools, the time for a revamp of the Getty Research Portal, an aggregated search index of digitized art history books across major art institutions, had arrived. +
As part of the continuous evolution of library search tools, the time for a revamp of the Getty Research Portal, an aggregated search index of digitized art history books across major art institutions, had arrived. -Drawing from the original application, written primarily with Java and Solr, we have reconstructed the Getty Research Portal 2.0 as an Angular application with an Elasticsearch server. By harnessing the power of Angular for a seamlessly responsive front end and Elasticsearch to provide a schema-less search engine, we have given the Portal refined search capabilities and drastically improved maintainability. We will walk through the benefits and challenges of building an application with these technologies and give the Code4Lib community a high-level understanding of metadata aggregation for libraries the Angular and Elasticsearch way.
\ No newline at end of file +Drawing from the original application, written primarily with Java and Solr, we have reconstructed the Getty Research Portal 2.0 as an Angular application with an Elasticsearch server. By harnessing the power of Angular for a seamlessly responsive front end and Elasticsearch to provide a schema-less search engine, we have given the Portal refined search capabilities and drastically improved maintainability. We will walk through the benefits and challenges of building an application with these technologies and give the Code4Lib community a high-level understanding of metadata aggregation for libraries the Angular and Elasticsearch way. diff --git a/_posts/2016-03-08-How-not-to-waste-catalogers-time-Making-the-most-of-subject-headings.html b/_posts/2016-03-09-How-not-to-waste-catalogers-time-Making-the-most-of-subject-headings.html similarity index 91% rename from _posts/2016-03-08-How-not-to-waste-catalogers-time-Making-the-most-of-subject-headings.html rename to _posts/2016-03-09-How-not-to-waste-catalogers-time-Making-the-most-of-subject-headings.html index 64cb957..688511d 100755 --- a/_posts/2016-03-08-How-not-to-waste-catalogers-time-Making-the-most-of-subject-headings.html +++ b/_posts/2016-03-09-How-not-to-waste-catalogers-time-Making-the-most-of-subject-headings.html @@ -16,19 +16,20 @@ endTime: 1457536800 milTime: 10:05-10:20 title: How not to waste catalogers' time: Making the most of subject headings +slides: '/slides/JMO-code4lib-cataloging.pptx' ---The subject descriptions of well-cataloged library resources have rich semantics, but most online catalogs and discovery systems do not take full advantage of them, and the headings assigned by librarians do not always match the descriptions users expect. This session features ideas, demonstrations, and discussion on how we can improve the design and the data in our catalogs and discovery systems to improve discovery -of relevant materials. It will focus on how to better take advantage of the kinds of data that catalogers already create. +of relevant materials. It will focus on how to better take advantage of the kinds of data that catalogers already create. Topics to be discussed include: - -- How to take advantage of subject heading order in summaries + -- How to take advantage of subject heading order in summaries and in relevance ranking of user searches. -- How to use relationships between subject headings, both those explicitly stated in authority data, and those that can be automatically inferred from data, to improve browsing and search. -- How to exploit the respective strengths (and work around the respective - weaknesses) of LCSH, FAST, and Wikipedia in subject searches.
\ No newline at end of file + weaknesses) of LCSH, FAST, and Wikipedia in subject searches. diff --git a/_posts/2016-03-08-Janus--Nodejs-Handler-for-all-Library-Searches.html b/_posts/2016-03-09-Janus--Nodejs-Handler-for-all-Library-Searches.html similarity index 92% rename from _posts/2016-03-08-Janus--Nodejs-Handler-for-all-Library-Searches.html rename to _posts/2016-03-09-Janus--Nodejs-Handler-for-all-Library-Searches.html index 1a3f4d6..a98d86c 100755 --- a/_posts/2016-03-08-Janus--Nodejs-Handler-for-all-Library-Searches.html +++ b/_posts/2016-03-09-Janus--Nodejs-Handler-for-all-Library-Searches.html @@ -16,7 +16,8 @@ endTime: 1457547300 milTime: 13:05-13:15 title: Janus - Node.js Handler for all Library Searches +slides: 'https://umnlibraries.github.io/janus-preso-code4lib-2016/#/' ---Libraries websites often attempt to present a single interface to multiple, disparate search engines: vendor databases, institutional repositories, finding aids, discovery layers, search appliances, etc. How do we impose order on this chaos? How do we know whether our attempts to do so meet users' needs? Do we build our own bespoke portal UIs, using vendor APIs for each and every search engine, refusing to use any vendor UIs? Or do we just provide links, or maybe search forms, that redirect to the vendor UIs? -Janus presents a middle path, allowing libraries to present a single interface to multiple search engines, and to capture and analyze much of the significant use of those search engines, without completely replacing vendor UIs. Janus provides a simple URL API that encapsulates and abstracts away the complexities of vendor APIs. It supports Shibboleth and many other, more common, authentication tools, as well as common logging tools. Janus is implemented in Node.js for high performance and ease of testing of interaction with vendor web UIs, which often rely heavily on JavaScript. Janus has been in production for several months at the University of Minnesota Libraries, where we are preparing to release the code as open source before coe4lib 2016.
\ No newline at end of file +Janus presents a middle path, allowing libraries to present a single interface to multiple search engines, and to capture and analyze much of the significant use of those search engines, without completely replacing vendor UIs. Janus provides a simple URL API that encapsulates and abstracts away the complexities of vendor APIs. It supports Shibboleth and many other, more common, authentication tools, as well as common logging tools. Janus is implemented in Node.js for high performance and ease of testing of interaction with vendor web UIs, which often rely heavily on JavaScript. Janus has been in production for several months at the University of Minnesota Libraries, where we are preparing to release the code as open source before coe4lib 2016. diff --git a/_posts/2016-03-08-Linked-Open-Dime-Novels-or-19th-Century-Fiction-and-21st-Century-Data.html b/_posts/2016-03-09-Linked-Open-Dime-Novels-or-19th-Century-Fiction-and-21st-Century-Data.html similarity index 97% rename from _posts/2016-03-08-Linked-Open-Dime-Novels-or-19th-Century-Fiction-and-21st-Century-Data.html rename to _posts/2016-03-09-Linked-Open-Dime-Novels-or-19th-Century-Fiction-and-21st-Century-Data.html index bc864ae..40eb336 100755 --- a/_posts/2016-03-08-Linked-Open-Dime-Novels-or-19th-Century-Fiction-and-21st-Century-Data.html +++ b/_posts/2016-03-09-Linked-Open-Dime-Novels-or-19th-Century-Fiction-and-21st-Century-Data.html @@ -16,6 +16,7 @@ endTime: 1457534100 milTime: 09:15-09:35 title: Linked Open Dime Novels; or, 19th Century Fiction and 21st Century Data +slides: '/slides/katz_short_code4lib.pdf' ---Dime novels were the predominate form of popular fiction in the United States from 1865 to 1915, yet for many years, they have been all but forgotten. Recent digitization efforts have begun to shed new light on this treasure trove of popular culture, now entirely within the public domain. However, fully describing these works offers some unique challenges due to their complex publication histories and tangled webs of authorship. Matthew Short of Northern Illinois University and Demian Katz of Villanova University have undertaken a project to expose and share data about this fascinating literature by combining the best of library cataloging practices, data collected by domain experts, and linked data techniques. This project has demonstrated the feasibility of small-scale linked data projects within existing applications as well as the power and benefits of a productive collaboration. @@ -24,4 +25,4 @@ - A realistic assessment of linked data strengths and weaknesses - Strategies for taking advantage of linked data in legacy systems - A discussion of significant limitations in current bibliographic models (and possible solutions) -- Awesome dime novel artwork and must-read titles (because every 21st century programmer needs some 19th century entertainment)
\ No newline at end of file +- Awesome dime novel artwork and must-read titles (because every 21st century programmer needs some 19th century entertainment) diff --git a/_posts/2016-03-08-Making-new-discoveries-from-old-data-Utilizing-digital-scholarship-to-foster-new-research-in-Special-Collections.html b/_posts/2016-03-09-Making-new-discoveries-from-old-data-Utilizing-digital-scholarship-to-foster-new-research-in-Special-Collections.html similarity index 95% rename from _posts/2016-03-08-Making-new-discoveries-from-old-data-Utilizing-digital-scholarship-to-foster-new-research-in-Special-Collections.html rename to _posts/2016-03-09-Making-new-discoveries-from-old-data-Utilizing-digital-scholarship-to-foster-new-research-in-Special-Collections.html index e11c907..af48e95 100755 --- a/_posts/2016-03-08-Making-new-discoveries-from-old-data-Utilizing-digital-scholarship-to-foster-new-research-in-Special-Collections.html +++ b/_posts/2016-03-09-Making-new-discoveries-from-old-data-Utilizing-digital-scholarship-to-foster-new-research-in-Special-Collections.html @@ -16,9 +16,10 @@ endTime: 1457560200 milTime: 16:40-16:50 title: Making new discoveries from old data: Utilizing digital scholarship to foster new research in Special Collections +slides: '/slides/Matt_Carruthers_Code4Lib.pdf' ---The University of Michigan Library is exploring a framework for fostering new and original research in Special Collections which moves beyond traditional scholarship methods. We are currently utilizing existing Special Collections data from finding aids, along with openly available digital scholarship tools, to identify and visualize hidden connections and social networks among creators of our archival collections. This new information can serve as a novel and innovative resource to help guide further research with Special Collections materials. In the future, we hope to build upon this framework in an innovative "library lab" model to support digital scholarship on campus, facilitate connections between researchers, and incubate projects, positioning Special Collections as an active collaborator in research using its materials. -In this presentation, we will discuss the methodology and tools we are using to surface hidden connections and social networks among individuals represented in our archival collections, as well as our goals for using this as a basis to develop a digital scholarship service.
\ No newline at end of file +In this presentation, we will discuss the methodology and tools we are using to surface hidden connections and social networks among individuals represented in our archival collections, as well as our goals for using this as a basis to develop a digital scholarship service. diff --git a/_posts/2016-03-08-So-You-Think-You-Want-to-Migrate-to-RDF.html b/_posts/2016-03-09-So-You-Think-You-Want-to-Migrate-to-RDF.html similarity index 100% rename from _posts/2016-03-08-So-You-Think-You-Want-to-Migrate-to-RDF.html rename to _posts/2016-03-09-So-You-Think-You-Want-to-Migrate-to-RDF.html diff --git a/_posts/2016-03-08-The-Modern-Day-Sisyphus-libtech-Burnout-and-You.html b/_posts/2016-03-09-The-Modern-Day-Sisyphus-libtech-Burnout-and-You.html similarity index 100% rename from _posts/2016-03-08-The-Modern-Day-Sisyphus-libtech-Burnout-and-You.html rename to _posts/2016-03-09-The-Modern-Day-Sisyphus-libtech-Burnout-and-You.html diff --git a/_posts/2016-03-08-Transcending-Traditional-Systems-and-Labels-An-APIFirst-Archives-Approach-at-NPR.html b/_posts/2016-03-09-Transcending-Traditional-Systems-and-Labels-An-APIFirst-Archives-Approach-at-NPR.html similarity index 95% rename from _posts/2016-03-08-Transcending-Traditional-Systems-and-Labels-An-APIFirst-Archives-Approach-at-NPR.html rename to _posts/2016-03-09-Transcending-Traditional-Systems-and-Labels-An-APIFirst-Archives-Approach-at-NPR.html index b4e0fdb..2a6d332 100755 --- a/_posts/2016-03-08-Transcending-Traditional-Systems-and-Labels-An-APIFirst-Archives-Approach-at-NPR.html +++ b/_posts/2016-03-09-Transcending-Traditional-Systems-and-Labels-An-APIFirst-Archives-Approach-at-NPR.html @@ -16,5 +16,6 @@ endTime: 1457551500 milTime: 14:05-14:25 title: Transcending Traditional Systems and Labels: An API-First Archives Approach at NPR +slides: 'http://www.slideshare.net/CamilleSalas1/radc4l16-an-apifirst-archives-approach-at-npr-59698533' --- -National Public Radio’s Research, Archives, and Data Strategy (RAD) team (f/k/a the Library) has been working beyond the limits of traditional database structures -- as well as the traditional library label -- to upgrade our current archival workflow tool, reposition our department and foster new interdepartmental connections. As NPR’s structure and content production evolve, the needs of our colleagues across many departments continue to grow. RAD embarked on a collaborative effort with our Digital Media colleagues to refactor NPR’s archival database to address these changes and create a more flexible system for future requirements. The out-of-the-box database in use had been selected several years earlier as a means to archive and catalog NPR’s broadcast content to fulfill FCC and grant reporting requirements, as well as to retrieve archival content. Users requested additional database services such as metadata reporting capabilities from internal production systems, and more metadata tagging for born-digital content, such as podcasts and blogs. We needed to explore new ways to utilize and deploy the metadata describing these stories. We chose an API-First approach in order to focus first on the data, and then to create a user interface aligned with NPR’s other digital platforms. During our work on the refactor, the Library rebranded itself and became the RAD team. We hired our first dedicated developer to collaborate on our evolving archive and workflow needs, and to assist with the implementation of a new taxonomy management and tagging system. Our presentation will focus on the refactor project within the context of the rebranding and share lessons learned thus far about an API-First approach. For reference, our development stack includes: Amazon Web Services, Hypermedia API, ElasticSearch, Node.js and NoSQL.
\ No newline at end of file +National Public Radio’s Research, Archives, and Data Strategy (RAD) team (f/k/a the Library) has been working beyond the limits of traditional database structures -- as well as the traditional library label -- to upgrade our current archival workflow tool, reposition our department and foster new interdepartmental connections. As NPR’s structure and content production evolve, the needs of our colleagues across many departments continue to grow. RAD embarked on a collaborative effort with our Digital Media colleagues to refactor NPR’s archival database to address these changes and create a more flexible system for future requirements. The out-of-the-box database in use had been selected several years earlier as a means to archive and catalog NPR’s broadcast content to fulfill FCC and grant reporting requirements, as well as to retrieve archival content. Users requested additional database services such as metadata reporting capabilities from internal production systems, and more metadata tagging for born-digital content, such as podcasts and blogs. We needed to explore new ways to utilize and deploy the metadata describing these stories. We chose an API-First approach in order to focus first on the data, and then to create a user interface aligned with NPR’s other digital platforms. During our work on the refactor, the Library rebranded itself and became the RAD team. We hired our first dedicated developer to collaborate on our evolving archive and workflow needs, and to assist with the implementation of a new taxonomy management and tagging system. Our presentation will focus on the refactor project within the context of the rebranding and share lessons learned thus far about an API-First approach. For reference, our development stack includes: Amazon Web Services, Hypermedia API, ElasticSearch, Node.js and NoSQL.
diff --git a/_posts/2016-03-08-What-does-it-take-to-get-a-job-these-days-Analyzing-jobscode4liborg-data-to-understand-current-technology-skillsets.html b/_posts/2016-03-09-What-does-it-take-to-get-a-job-these-days-Analyzing-jobscode4liborg-data-to-understand-current-technology-skillsets.html similarity index 90% rename from _posts/2016-03-08-What-does-it-take-to-get-a-job-these-days-Analyzing-jobscode4liborg-data-to-understand-current-technology-skillsets.html rename to _posts/2016-03-09-What-does-it-take-to-get-a-job-these-days-Analyzing-jobscode4liborg-data-to-understand-current-technology-skillsets.html index 60ecd4c..6253e82 100755 --- a/_posts/2016-03-08-What-does-it-take-to-get-a-job-these-days-Analyzing-jobscode4liborg-data-to-understand-current-technology-skillsets.html +++ b/_posts/2016-03-09-What-does-it-take-to-get-a-job-these-days-Analyzing-jobscode4liborg-data-to-understand-current-technology-skillsets.html @@ -16,5 +16,6 @@ endTime: 1457559000 milTime: 16:15-16:30 title: What does it take to get a job these days? Analyzing jobs.code4lib.org data to understand current technology skillsets +slides: '/slides/mmaceli_code4lib_pres.pptx' --- -The jobs.code4lib.org site contains years of usefully-structured data that gives us a unique view into who we are as a community. A holistic look at this data yields numerous insights – what to teach, what to learn, where to focus our technical efforts, and the emergence (and decline) of technology trends. This talk will describe the data collected by the code4lib jobs site and the text analysis performed for research purposes, which has yielded multiple publications. The talk will conclude with an open call for possible future collaborations or applications of this data within the code4lib community.
\ No newline at end of file +The jobs.code4lib.org site contains years of usefully-structured data that gives us a unique view into who we are as a community. A holistic look at this data yields numerous insights – what to teach, what to learn, where to focus our technical efforts, and the emergence (and decline) of technology trends. This talk will describe the data collected by the code4lib jobs site and the text analysis performed for research purposes, which has yielded multiple publications. The talk will conclude with an open call for possible future collaborations or applications of this data within the code4lib community.
diff --git a/_posts/2016-03-08-ArchivesSpaceArchivematicaDSpace-Workflow-Integration.html b/_posts/2016-03-10-ArchivesSpaceArchivematicaDSpace-Workflow-Integration.html similarity index 89% rename from _posts/2016-03-08-ArchivesSpaceArchivematicaDSpace-Workflow-Integration.html rename to _posts/2016-03-10-ArchivesSpaceArchivematicaDSpace-Workflow-Integration.html index 0dc1575..a724b99 100755 --- a/_posts/2016-03-08-ArchivesSpaceArchivematicaDSpace-Workflow-Integration.html +++ b/_posts/2016-03-10-ArchivesSpaceArchivematicaDSpace-Workflow-Integration.html @@ -16,5 +16,6 @@ endTime: 1457628000 milTime: 11:30-11:40 title: ArchivesSpace-Archivematica-DSpace Workflow Integration +slides: 'https://docs.google.com/presentation/d/1yn7Wc-V0WfQ4-BeUfBw0GDY7E2S7yLyuynp4oxg6itU/edit#slide=id.p4' --- -In April 2014, the Bentley Historical Library received a $355,000 grant from the Andrew W. Mellon Foundation to partner with the University of Michigan Library and Artefactual Systems on the integration of ArchivesSpace, Archivematica, and DSpace in an end-to-end digital archives workflow. The project seeks to expedite the ingest, description, and overall curation of digital archives by facilitating (a) the review and characterization of newly acquired content, (b) the creation and reuse of descriptive and administrative metadata among emerging platforms and (c) the deposit of fully processed content into a digital preservation repository. This presentation will identify key project goals and outcomes and demonstrate features and functionality of Archivematica's new 'Appraisal and Arrangement' tab developed by Artefactual Systems.
\ No newline at end of file +In April 2014, the Bentley Historical Library received a $355,000 grant from the Andrew W. Mellon Foundation to partner with the University of Michigan Library and Artefactual Systems on the integration of ArchivesSpace, Archivematica, and DSpace in an end-to-end digital archives workflow. The project seeks to expedite the ingest, description, and overall curation of digital archives by facilitating (a) the review and characterization of newly acquired content, (b) the creation and reuse of descriptive and administrative metadata among emerging platforms and (c) the deposit of fully processed content into a digital preservation repository. This presentation will identify key project goals and outcomes and demonstrate features and functionality of Archivematica's new 'Appraisal and Arrangement' tab developed by Artefactual Systems.
diff --git a/_posts/2016-03-08-Free-your-workflows-and-the-rest-will-follow-communitydriven-AV-solutions-through-open-source-workflow-development.html b/_posts/2016-03-10-Free-your-workflows-and-the-rest-will-follow-communitydriven-AV-solutions-through-open-source-workflow-development.html similarity index 94% rename from _posts/2016-03-08-Free-your-workflows-and-the-rest-will-follow-communitydriven-AV-solutions-through-open-source-workflow-development.html rename to _posts/2016-03-10-Free-your-workflows-and-the-rest-will-follow-communitydriven-AV-solutions-through-open-source-workflow-development.html index 039caf1..99d15e6 100755 --- a/_posts/2016-03-08-Free-your-workflows-and-the-rest-will-follow-communitydriven-AV-solutions-through-open-source-workflow-development.html +++ b/_posts/2016-03-10-Free-your-workflows-and-the-rest-will-follow-communitydriven-AV-solutions-through-open-source-workflow-development.html @@ -16,7 +16,8 @@ endTime: 1457626800 milTime: 11:00-11:20 title: Free your workflows (and the rest will follow): community-driven AV solutions through open source workflow development +slides: 'http://ablwr.github.io/free_your_workflows/#/' --- -Much of our work as librarians and archivists is devoted to researching, planning, documenting, and implementing workflows based on our knowledge of best practices and locally defined needs. However, this documentation of workflows rarely leaves the institution it is created for. Instead, we share our processes at THATCamps, unconferences, and local and regional association conferences, and occasionally post them on personal or institutional websites. These exchanges are integral to the development of our field, and anecdotally, we hear from our colleagues that these encounters are some of the most useful and rewarding events to attend professionally. +
Much of our work as librarians and archivists is devoted to researching, planning, documenting, and implementing workflows based on our knowledge of best practices and locally defined needs. However, this documentation of workflows rarely leaves the institution it is created for. Instead, we share our processes at THATCamps, unconferences, and local and regional association conferences, and occasionally post them on personal or institutional websites. These exchanges are integral to the development of our field, and anecdotally, we hear from our colleagues that these encounters are some of the most useful and rewarding events to attend professionally. -Our presentation will consider how this sharing of workflows could be supported on a regular basis through the open-sourcing of documented workflows, software, and hardware. We will explore how “open-sourcing” AV digitization and digital preservation workflows, software, and advocating for open file formats and standards for audio visual archives has the potential to empower and build community among AV archivists. Further, we will look at how this might provide greater transparency and insight into how exactly materials are processed, and encourage collaboration among institutions, organizations, and archivists. We intend to ground our presentation in concrete examples from the field, such as the implementation of open source micro-service scripts for archival processing at a broadcasting station and work on the open source digital video file conformance checker software, MediaConch (a PREFORMA project).
\ No newline at end of file +Our presentation will consider how this sharing of workflows could be supported on a regular basis through the open-sourcing of documented workflows, software, and hardware. We will explore how “open-sourcing” AV digitization and digital preservation workflows, software, and advocating for open file formats and standards for audio visual archives has the potential to empower and build community among AV archivists. Further, we will look at how this might provide greater transparency and insight into how exactly materials are processed, and encourage collaboration among institutions, organizations, and archivists. We intend to ground our presentation in concrete examples from the field, such as the implementation of open source micro-service scripts for archival processing at a broadcasting station and work on the open source digital video file conformance checker software, MediaConch (a PREFORMA project). diff --git a/_posts/2016-03-08-Indoor-Positioning-Services---Location-Based-Recommendations.html b/_posts/2016-03-10-Indoor-Positioning-Services---Location-Based-Recommendations.html similarity index 90% rename from _posts/2016-03-08-Indoor-Positioning-Services---Location-Based-Recommendations.html rename to _posts/2016-03-10-Indoor-Positioning-Services---Location-Based-Recommendations.html index 682c8d5..dc1f465 100755 --- a/_posts/2016-03-08-Indoor-Positioning-Services---Location-Based-Recommendations.html +++ b/_posts/2016-03-10-Indoor-Positioning-Services---Location-Based-Recommendations.html @@ -16,12 +16,13 @@ endTime: 1457627400 milTime: 11:20-11:30 title: Indoor Positioning Services & Location Based Recommendations +slides: 'https://www.ideals.illinois.edu/bitstream/handle/2142/89471/code4lib2016_jimhahn.pdf?sequence=3' --- -With beacon technology, real-time turn-by-turn directions and real-time recommendations in the print collection can be provided to a user’s mobile device. With the infrastructure and research trajectory developed for an augmented reality experiment ( http://journal.code4lib.org/articles/10881 ), researchers undertook an experimental project to incorporate Estimote beacons ( http://estimote.com/ ) into an Undergraduate Library collection so that students new to the environment can see the location of their mobile device within the library building, supporting wayfinding to items, and discovery of like items with location-based recommendations. +
With beacon technology, real-time turn-by-turn directions and real-time recommendations in the print collection can be provided to a user’s mobile device. With the infrastructure and research trajectory developed for an augmented reality experiment ( http://journal.code4lib.org/articles/10881 ), researchers undertook an experimental project to incorporate Estimote beacons ( http://estimote.com/ ) into an Undergraduate Library collection so that students new to the environment can see the location of their mobile device within the library building, supporting wayfinding to items, and discovery of like items with location-based recommendations. Presenters will demonstrate the distributed computing processes and workflows necessary to integrate beacons into collections-based wayfinding and walk through key components for the recommendation algorithm used for “topic spaces” in collections. -The experimental location‐based recommendation service is grounded in the advantages of collocation that support information discovery and are supplemented with existing ILS data -- e.g. sum total circulation of a particular item. +The experimental location‐based recommendation service is grounded in the advantages of collocation that support information discovery and are supplemented with existing ILS data -- e.g. sum total circulation of a particular item. Presenters will demonstrate techniques and approaches utilized in developing improvements for beacon precision, enabling increased location granularity in library environments, along with security considerations for location based services. -
\ No newline at end of file + diff --git a/_posts/2016-03-08-Issues-to-consider-before-pushing-out-an-Open-Source-Project.html b/_posts/2016-03-10-Issues-to-consider-before-pushing-out-an-Open-Source-Project.html similarity index 100% rename from _posts/2016-03-08-Issues-to-consider-before-pushing-out-an-Open-Source-Project.html rename to _posts/2016-03-10-Issues-to-consider-before-pushing-out-an-Open-Source-Project.html diff --git a/_posts/2016-03-08-Scribe-Toward-a-general-framework-for-community-transcription.html b/_posts/2016-03-10-Scribe-Toward-a-general-framework-for-community-transcription.html similarity index 93% rename from _posts/2016-03-08-Scribe-Toward-a-general-framework-for-community-transcription.html rename to _posts/2016-03-10-Scribe-Toward-a-general-framework-for-community-transcription.html index d0779c9..8c7dfe0 100755 --- a/_posts/2016-03-08-Scribe-Toward-a-general-framework-for-community-transcription.html +++ b/_posts/2016-03-10-Scribe-Toward-a-general-framework-for-community-transcription.html @@ -16,6 +16,7 @@ endTime: 1457628600 milTime: 11:40-11:50 title: Scribe: Toward a general framework for community transcription +slides: '/slides/Beaudoin_Paul-Scribe_Community_Transcription.pdf' ---NYPL Labs and Zooniverse built Scribe, a highly configurable, open source framework for setting up community transcription projects around handwritten or OCR-resistant texts. Scribe suits digital humanities, library, and citizen science projects seeking to extract highly structured, normalizable data from a set of digitized materials (e.g. historical manuscripts, account ledgers, catalog cards, or maritime logbooks). @@ -24,4 +25,4 @@ The talk will identify the community transcription design patterns that informed the unique architecture of Scribe. March will be a great time to also discuss the successes and challenges of Emigrant City ( http://emigrantcity.nypl.org ), a project built with Scribe that launched in Nov 2015. http://scribeproject.github.io -http://emigrantcity.nypl.org
\ No newline at end of file +http://emigrantcity.nypl.org diff --git a/css/main.css b/css/main.css index cef8a15..95b967d 100755 --- a/css/main.css +++ b/css/main.css @@ -862,3 +862,36 @@ p.speaker-inst{ margin-bottom: 0.5em; margin-left: 0.5em; } + +.search_results { + position: relative; + display:none; + background-color: #fff; +} + +.search_results i { + position: absolute; + top: 0.5em; + right: 0.5em; + font-size: 2em; +} + +.search_results h2 { + display: block; + margin-left: auto; + margin-right: auto; + max-width: 25em; +} + +#search_results { + margin-left: auto; + margin-right: auto; + max-width: 59em; + margin-top: 2em; + margin-bottom: 2em; + list-style-type: none; +} + +#search_results li { + padding: 1em; +} diff --git a/js/lunr.min.js b/js/lunr.min.js new file mode 100644 index 0000000..b0198df --- /dev/null +++ b/js/lunr.min.js @@ -0,0 +1,7 @@ +/** + * lunr - http://lunrjs.com - A bit like Solr, but much smaller and not as bright - 0.7.0 + * Copyright (C) 2016 Oliver Nightingale + * MIT Licensed + * @license + */ +!function(){var t=function(e){var n=new t.Index;return n.pipeline.add(t.trimmer,t.stopWordFilter,t.stemmer),e&&e.call(n,n),n};t.version="0.7.0",t.utils={},t.utils.warn=function(t){return function(e){t.console&&console.warn&&console.warn(e)}}(this),t.utils.asString=function(t){return void 0===t||null===t?"":t.toString()},t.EventEmitter=function(){this.events={}},t.EventEmitter.prototype.addListener=function(){var t=Array.prototype.slice.call(arguments),e=t.pop(),n=t;if("function"!=typeof e)throw new TypeError("last argument must be a function");n.forEach(function(t){this.hasHandler(t)||(this.events[t]=[]),this.events[t].push(e)},this)},t.EventEmitter.prototype.removeListener=function(t,e){if(this.hasHandler(t)){var n=this.events[t].indexOf(e);this.events[t].splice(n,1),this.events[t].length||delete this.events[t]}},t.EventEmitter.prototype.emit=function(t){if(this.hasHandler(t)){var e=Array.prototype.slice.call(arguments,1);this.events[t].forEach(function(t){t.apply(void 0,e)})}},t.EventEmitter.prototype.hasHandler=function(t){return t in this.events},t.tokenizer=function(e){return arguments.length&&null!=e&&void 0!=e?Array.isArray(e)?e.map(function(e){return t.utils.asString(e).toLowerCase()}):e.toString().trim().toLowerCase().split(t.tokenizer.seperator):[]},t.tokenizer.seperator=/[\s\-]+/,t.tokenizer.load=function(t){var e=this.registeredFunctions[t];if(!e)throw new Error("Cannot load un-registered function: "+t);return e},t.tokenizer.label="default",t.tokenizer.registeredFunctions={"default":t.tokenizer},t.tokenizer.registerFunction=function(e,n){n in this.registeredFunctions&&t.utils.warn("Overwriting existing tokenizer: "+n),e.label=n,this.registeredFunctions[n]=e},t.Pipeline=function(){this._stack=[]},t.Pipeline.registeredFunctions={},t.Pipeline.registerFunction=function(e,n){n in this.registeredFunctions&&t.utils.warn("Overwriting existing registered function: "+n),e.label=n,t.Pipeline.registeredFunctions[e.label]=e},t.Pipeline.warnIfFunctionNotRegistered=function(e){var n=e.label&&e.label in this.registeredFunctions;n||t.utils.warn("Function is not registered with pipeline. This may cause problems when serialising the index.\n",e)},t.Pipeline.load=function(e){var n=new t.Pipeline;return e.forEach(function(e){var i=t.Pipeline.registeredFunctions[e];if(!i)throw new Error("Cannot load un-registered function: "+e);n.add(i)}),n},t.Pipeline.prototype.add=function(){var e=Array.prototype.slice.call(arguments);e.forEach(function(e){t.Pipeline.warnIfFunctionNotRegistered(e),this._stack.push(e)},this)},t.Pipeline.prototype.after=function(e,n){t.Pipeline.warnIfFunctionNotRegistered(n);var i=this._stack.indexOf(e);if(-1==i)throw new Error("Cannot find existingFn");i+=1,this._stack.splice(i,0,n)},t.Pipeline.prototype.before=function(e,n){t.Pipeline.warnIfFunctionNotRegistered(n);var i=this._stack.indexOf(e);if(-1==i)throw new Error("Cannot find existingFn");this._stack.splice(i,0,n)},t.Pipeline.prototype.remove=function(t){var e=this._stack.indexOf(t);-1!=e&&this._stack.splice(e,1)},t.Pipeline.prototype.run=function(t){for(var e=[],n=t.length,i=this._stack.length,r=0;n>r;r++){for(var o=t[r],s=0;i>s&&(o=this._stack[s](o,r,t),void 0!==o&&""!==o);s++);void 0!==o&&""!==o&&e.push(o)}return e},t.Pipeline.prototype.reset=function(){this._stack=[]},t.Pipeline.prototype.toJSON=function(){return this._stack.map(function(e){return t.Pipeline.warnIfFunctionNotRegistered(e),e.label})},t.Vector=function(){this._magnitude=null,this.list=void 0,this.length=0},t.Vector.Node=function(t,e,n){this.idx=t,this.val=e,this.next=n},t.Vector.prototype.insert=function(e,n){this._magnitude=void 0;var i=this.list;if(!i)return this.list=new t.Vector.Node(e,n,i),this.length++;if(eYuuss! You got ' + results.length + ' search result' + s + '!
'; + $search_results_container.prepend(prependString); + + // Iterate over the results + results.forEach(function(result) { + var item = loaded_data[result.ref]; + + // Build a snippet of HTML for this result + var appendString = 'Speakers: ' + item.speakers + '
' + item.type + '