Changes

How can we take semi-structured but messy metadata from a repository like CONTENTdm and transform it into rich linked data? Working with metadata from Tulane’s Hogan Jazz Archive Photography Collection, the Linked Jazz Project used Open Refine and Python scripts to tease out proper names, match them with name authority URIs, and specify FOAF relationships between musicians who appear together in photographs. Additional RDF triples were created for any dates associated with the photos, and for those images with place information we employed GeoNames URIs. Historical images and data that were siloed can now interact with other datasets, like Linked Jazz’s rich set of names and personal relationships, and can be visualized [link to come[http://linkedjazz.org/tulane/ see prototype visualization]] or otherwise presented on the web in any number of ways. I have not previously presented at a Code4Lib conference.

For those who are able to take an extended parental leave, we will present strategies for minimizing the impact to your career and your employer. For those (particularly in the United States) who are only able to take a short leave will require different strategies. Despite different levels of preparation, all are useful exercises in succession planning and making a stronger workplace and future ability to work a flexible schedule through reviewing workloads, cross-training personnel, hiring contract replacements, and creative divisions of labor. Such preparation makes work better for everyone, kids or no kidsor caretakers of any kind.

Times have changed. You may have heard the news that PBCore is back in action as part of the American Archive of Public Broadcasting initiative and via the Association of Moving Image Archivists (AMIA) PBCore Advisory Subcommittee. A group of archivists, public media stakeholders, and engaged users have come together to provide necessary , sustaining support for the standard and to see to its further development.

* [[User:sanderson|Steven Carl Anderson]], sanderson@bpl.org, [http://www.bpl.org Boston Public Library ] (no previously accepted prepared talks but have done lightning talks in the past)

Annotations on content resources allow users to contribute knowledge within the digital repository space. W3C Open Annotation provides a comprehensive model for web annotation on all types of content, using Linked Data as a fundamental framework. Annotation clients generate instances of this model, typically using a JSON serialization, but need to store that data somewhere using a standard interaction pattern so that best of breed clients and , servers , and data can be mixed and matched. Stanford is using Fedora4 for managing Open Annotations, via a middleware component called Triannon. Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources. Triannon could be easily modified to use other LDP implementations, or could be modified to work with linked data other than annotations. == Hydras in the Wild: A survey of current projects == * Mark Bussey, mark@curationexperts.com, Data Curation Experts You've seen the tutorials, but [https://github.com/projecthydra/hydra/wiki/Dive-into-Hydra Dive Into Hydra] seems to leave something wanting. What can you really do using the Hydra Framework? This talks looks at a number of current Hydra projects and highlights the design and functional features unique to each. Compare and contrast UX, design and functional capabilites from a range of hydra-based repositories including:* Avalon for media discovery and distribution (Indiana and Northwestern Univiersities) * HydraDam for media archive management(WGBH)* HyHull for general Institutional Repository needs (University of Hull)* T-DIL for slide library functions (Tufts University)* Sufia & Scholarsphere as a bundled self-deposit IR solution (Pennsylvania State University)* Curate & Worthwhile as general purpose repository platforms (Multiple Insititutions)This will be a whirlwind tour aimed at providing ideas and inspiration for your own repository development project. == Hydra Makeovers! == * Alicia Cozine, alicia@curationexperts.com, Data Curation Experts* Patrick Feeley, pgf8@case.edu, Case Western Reserve University Compare two Hydra-based applications with the systems they replaced. Marvel at the Before and After snapshots of functionality, speed, and look & feel. * '''Digital Case 2.0''' is an institutional repository, complete with administrative tools, derivatives transcoding, flexible XML metadata storage, embargo and lease capability, faceted searching, and content viewers for texts/TEI, images, audio recordings, and videos. Digital Case 2.0 is based on worthwhile, an open-source IR starter gem. * '''The Tufts Digital Image Library''' is a specialized tool for art and art history resources, offering image collections with user access controls, image ordering, collection nesting, drag-and-drop organization, slideshows, and export capability. Both new systems are built on hydra, the open-source Ruby-on-Rails repository solution that incorporates Fedora for storage, Solr for indexing, and Blacklight for search optimization. Their beauty is not just skin-deep!   == Helping Google (and scholars, researchers, educators, & the public) find archival audio == * Anne Wootton, anne@popuparchive.org, Pop Up Archive (www.popuparchive.org) Culturally significant digital audio collections are hard to discover on the web. There are major barriers keeping this valuable media from scholars, researchers, and the general public: Audio is opaque: you can’t picture sound, or skim the words in a recording. Audio is hard to share: there’s no text to interact with. Audio is not text: but since text is the medium of the web, there’s no path for audiences to find content-rich audio.Audio metadata is inconsistent and incomplete. At Pop Up Archive, we're helping solve this problem making the spoken word searchable. We began as a UC-Berkeley School of Information Master's thesis to provide better access to recorded sound for audio producers, journalists, and historians. Today, Pop Up Archive processes thousands of hours of sound from all over the web to create automatic, timestamped transcripts and keywords, working with media companies and institutions like NPR, KQED, HuffPost Live, Princeton, and Stanford. We're building collections of sound from journalists, media organizations, and oral history archives from around the world. Pop Up Archive is supported by the John S. and James L. Knight Foundation, the National Endowment for the Humanities, and 500 Startups. == Digital Content Integrated with ILS Data for User Discovery: Lessons Learned == * Naomi Dushay, ndushay@stanford.edu, Stanford University Libraries* Laney McGlohon, laneymcg@stanford.edu, Stanford University Libraries (first-time presenter) So you want to expose your digital content in your discovery interface, integrated with the data from your ILS? How do you make the best information user searchable? How do you present complete, up to date search results with a minimum of duplicate entries? At Stanford, we have these cases and more:* digital content with no metadata in ILS* digital content for metadata in ILS* digital content with its own metadata derived from ILS metadata. We will describe our efforts to accommodate multiple updatable metadata sources for materials in the ILS and our Digital Object Repository while presenting users with reduced duplication in SearchWorks. Included will be some failures, some successes, and an honest assessment of where we are now. == Show All the Things: Kanban for Libraries ==  * Mike Hagedon, mhagedon@email.arizona.edu, University of Arizona Libraries (first-time presenter) The web developers at the University of Arizona Libraries had a problem: we were working on a major website rebuild project with no clear way to prioritize it against our other work. We knew we wanted to follow Agile principles and initially chose Scrum to organize and communicate about our work. But we found that certain core pieces of Scrum did not work for our team. Then we discovered Kanban, an Agile meta-process for organizing work (team or individual) that treats the work more as a flow than as a series of fixed time boxes. I’ll be talking about our journey toward finding a process that works for our team and how we’ve applied the principles of Kanban to better get our work done. Specifically, I'll discuss principles like how to visualize all your work, how to limit how much you’re doing (to get more done!), and how to optimize the flow of your work. == DIY Catalog == * Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]* Amy Drayer, adrayer at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library] With so many discovery layers being made available that didn’t quite fit user needs but still came with substantial costs, Hennepin County Library determined it would develop one that could handle its customizations. So they built their own ILS API, Web services, and an interface that provides all the features (and existing custom features) of the old catalog, with new features planned, all within a responsive layout. Get a look at the system architecture, how the front end communicates through the layers back to the databases, and how to manage the infrastructure. == OverDrive: Full Integration == * Amy Drayer, adrayer at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library]* Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library] How do you increase usage of your ebooks? Seamless integration in the catalog certainly helps. Users can search for digital titles, limit to just those that are available, place a request, borrow, and manage all their digital titles from the library website alongside all the other physical titles the library has. Get a quick demo and learn how this was all made possible. The [//www.hclib.org Hennepin County Library] is ranked one of [//www.thedigitalshift.com/2014/10/ebooks/overdrive-api-usage-indicates-growth-ebook-checkouts-via-opac/ the top users of OverDrive and OverDrive’s API] and is looking to more fully integrate 3M Cloud, OneClickDigital, and other digital resources. == Dynamic Indexing: a Tragic Solr Story == * Wayne Schneider, wschneider at [//www.hclib.org hclib.org], [//www.hclib.org Hennepin County Library] Loading data from an ILS into Solr isn’t so hard, unless it needs to be dynamic, fast, and hold more data than what can be found in 1.5 million MARC records. Some additional information we’ve incorporated are from Syndetics, ILS circulation, and OverDrive. We’ll share the nitty gritty details and what we learned about dynamic Solr indexing, including how to get good performance, how to deal with indexing failures, how to schedule it all to keep the data up-to-date, and some things you can do with that data such as popularity ratings. == Fedora 4, Survey of Core Capabilities and External Modules: == * Andrew Woods, awoods@duraspace.org, DuraSpace Now that the production release of Fedora 4.0 is out, the time is right to take a step back and review the core capabilities offered by Fedora:* Basic CRUD* Versioning*- Transactions* etc ...and take a closer look at the supported external modules:* Authorization* Solr integration* Triplestore integration* Camel integration* etc In addition to clarifying specific implementation details, this is an opportunity to surface community requirements which may have not been addressed in the initial release. == Bleeding edge beacons: redesign of a library tour with new technology == * Neal Henshaw, Virginia Tech * Somiah Lattimore, Straight Up Creative* Keith Gilbertson, keith.gilbertson@vt.edu, Virginia Tech This group has not yet presented at Code4Lib A technology liaison, a designer, and a developer are working together to update a mobile audio tour of an academic library. The walking tour was originally conceived of and created by the technology liaison to provide an orientation experience for incoming students. In its current version, patrons visit several stations in the library and activate an audio description of each station by scanning a QR barcode with a mobile device. We are building a prototype to test with focus groups so that we can launch a new version of the tour in early 2015. The tour has been reimagined with a professional and communicative user interface that presents students with learning goals for each location in the library. The new version of the tour is a mobile application with integrated support for micro-location technology provided through Bluetooth low energy beacon devices, known informally as iBeacons, installed throughout the building. As a touring student walks through the library, her location is noted by the app so that an appropriate video segment is automatically played according to the current location. We will discuss perspectives on the design of the project, including * Designing with technology to achieve learning goals* Designing graphical elements, interaction, and user experience* Designing to maintain compatibility with older technologies We’ll explain our efforts to make the application usable by those with hearing impairments and mobility impairments, reactions from our first users, and challenges in working with the relatively new beacon technology. == Distributed Remediation: Small tools for big problems: == * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs Remediation of legacy data can be automated only so much. Certain essential cleanup tasks, such as aligning a name with the correct authorized version, is very difficult for a computer yet trivial for a person. While it is these types remediations that will allow an institution to take advantage and participate in the web of Linked Open Data, a wholly manual approach is unrealistic. However, by augmenting automated remediation with a light human touch we can quickly and efficiently reach our goals. This talk will look at tools and methods being developed at NYPL Labs to empower library staff and the public to help clean up our legacy metadata through collaborative remediation. ==VuFind + WorldCat: Open Source Discovery Meets Big Library Data== * Karen A. Coombs, coombsk@oclc.org, OCLC* Demian Katz, demian.katz@villanova.edu, Villanova University Good collaboration is crucial to any integration. Our project, to integrate the open source discovery tool, VuFind, with results from the new WorldCat Discovery API, is no different. We want to exploit the flexibility of VuFind and add the depth and breadth of WorldCat and central index content. Plus, the project has the potential to eliminate the hurdle of exporting and indexing MARC records for 32 VuFind libraries. While we are really excited about the UI enhancements, we are also curious to see how we can share our domain expertise between our two organizations to get the project done quickly. How will different perspectives shape our existing code bases? How will we adjust to working on the same code base simultaneously? And how can we best incorporate what we learn along the way? There is also new territory to explore using the API: integrating bibliographic and article data into a single results set. And the overarching question: will we be able to take advantage of Linked Data in the WorldCat Discovery API to create some “glue” between records in existing VuFind indexes and third-party data providers? This presentation will discuss our adventures in the OCLC WorldShare Platform/VuFind collaboration: the opportunities, challenges and results. You’ll learn what worked, what didn’t and how you can improve your own discovery interface integration project—no matter what provider or APIs you use. == Book Reader Bingo: Which Page-Turner Should I Use? == * Eben English, eenglish [at] bpl.org, Boston Public Library Another day, another library reinventing the book-viewer wheel. When will the madness end? This talk will explore the current landscape of book-viewer/page-turner applications for digital library systems with an eye towards helping you make the right decision for your project. We'll look at some the major players on the market (such as Internet Archive BookReader, Wellcome Player, Mirador, and WDL-Viewer to name a few) and compare them based on a number of criteria: feature sets, mobile/tablet friendliness, ease of integration, code health, test coverage, "market share" (number of implementers), and other important factors. We'll look at the results of ACTUAL USABILITY TESTS to see what features users REALLY want in a book-viewer, and how each app measures up.  We'll also discuss important recent trends (such as the IIIF Presentation API, ReadersFirst, and NYPL's Library Simplified initiative) that have the potential to shape the book-viewer development landscape in the immediate future. Which page-turner applications are best poised to adopt/integrate/leverage these emerging standards? Which will become obsolete? This talk has the answers you need. == Rich Citations == * Adam Becker, abecker@plos.org, Public Library of Science* Erik Hetzner, ehetzner@plos.org, Public Library of Science Citations should connect you to the research you need. They shouldlink directly to the relevant papers and data. They should tell youeverything you need to know about how and where two pieces of researchare connected. They should be easy to use and they should never get inthe way of the reading experience. In short, citations should notclumsily point to a mere chunk of plain undifferentiated text sittingin a static list at the end of the paper. But with almost noexceptions, citations in scientific papers do just that. PLOS Labs has been working on a project to capture extra informationabout citations. To this end, we have designed a metadata structuredescribing the context of a paper's citations, called rich citations.This structured information includes complete bibliographicinformation for the cited items, location and context of the in-textcitation, co-citations, reference license and status (updated,retracted, etc.), and more. We have processed the complete PLOS corpus to extract this richcitation metadata, and made this data available in an API located athttp://api.richcitations.org/. We have also developed a JavaScript overlay to enhance a paper's viewusing rich citations (http://alpha.richcitations.org). This overlayuses the underlying rich citation metadata to allow the user to viewinformation about an in-text citation, quickly navigate betweencitations, and sort and filter the paper's reference list. In this talk, we will describe the rich citation metadata that we arecapturing. We will demonstrate how this metadata can enhance areader's experience of an article and how it can be used byresearchers to better understand how citations are used in thescientific community. We will also discuss our ongoing plans to extendthis project to the wider literature beyond PLOS, and how interestedmembers of the community can help. == Scriptaloging with ArchivesSpace and NodeJS == * Brian Hoffman, brianjhoffman@gmail.com ArchivesSpace is a new web application for managing archival collections. It has a browser-based interface for entering and editing metadata, and can import data serialized as EAD, MARC, and several other formats. But there may be situations where neither of these are quite what you want. For instance, you may have a large folder of images that each need a digital object record; or you may want to export an EAD for every collection in your repository; or calculate the total extent of your collection; or execute a global search and replace; or batch-update barcodes, etc. You could write a plugin using ArchivesSpace’s plugin API, but that requires facility with Ruby as well as access to the environment where the application is running. A more lightweight approach is to access your data through ArchivesSpace’s powerful REST API, and process it using whatever scripting language you prefer. This talk will present some simple “scriptaloging” solutions that a moderately skilled programmer can use to automate data entry or import tasks using an extendable command line tool written in NodeJS (https://www.npmjs.org/package/as-cli) and loosely inspired by Drupal’s drush utilitly. == Consuming Big Linked Open Data in Practice: Authority Shifts and Identifier Drift == * Kathryn Stine, katstine@berkeley.edu, UC Berkeley (first-time presenter)* Stephanie Collett, stephanie.collett@ucop.edu, California Digital Library, UC (c4l 2012 presenter) Increasingly, authoritative datasets of interest to libraries (subjects, names, classifications, etc.) are are available in bulk, exposed as linked open data. Unfettered access can allow libraries to aggregate, connect, and augment data in new ways that will benefit users. This talk will describe our exploratory experience integrating bulk data from the Virtual International Authority File (VIAF) into HathiTrust metadata to improve discovery and collection management. Authoritative data is not static - datasets change with new contributions and re-clustering, resulting in new identifier relationships. We will describe the challenges this presents with accessing, processing, and syncing our metadata with a massive, complex linked dataset. We will talk about our technical approach to navigating an ecosystem of identifiers and mitigating cached identifier drift between systems as authority data shifts. We aim to spark conversation about data accessibility and the relationships between local, consortial, and authoritative metadata as the library community moves beyond “Hello, world” linked data examples to integrating this data at scale into existing systems. == Your Chocolate is in My Peanut Butter! Mixing up Content and Presentation Layers to Build Smarter Books in Browsers with RDFa, Schema.org, and Linked Data Topics == * Jason A. Clark [@jaclark], Head, Library Informatics & Computing, Montana State University, jaclark@montana.edu* Scott W. H. Young [@hei_scott], Digital Initiatives Librarian, Montana State University, swyoung@montana.edu Common methods of publishing book content have focused on various implementations of existing technologies such as LaTeX, Markdown, and .epub. A common theme within this development has been the separation of presentation layers and content layers. What if there was another way? In responding to that question, we’ll look at our local @msulibrary prototype software funded by an IMLS Sparks! Innovation grant for presenting books inside of web browsers (https://github.com/jasonclark/bib-template). Our talk will focus on the tools and technologies of open web publishing. We’ll consider the strange and wonderful benefits of integrating the presentation layer and content layer using semantic RDFa HTML5 markup, and we’ll demonstrate how describing and displaying books within an open web model impacts discovery, eBook production, and machine-readability. Our session will include:* The benefits of using RDFa, Schema.org, and linked data models for book production* How structured data models for book content can turn your webpage into your API* Analyze the effects of this practice for machine-understanding, SEO, and UX* Discuss the advantages and disadvantages of this model as it applies to a range of book genres, including web book prototypes for fiction and poetry. Chocolate/Peanut Butter... RDFa/HTML5... Linked Data/Dbpedia Topics... "Great tastes that go great together." == Integration/Collaboration: Playing Well With Others == * Sarah Romkey, sromkey@artefactual.com, Artefactual Systems* Justin Simpson, jsimpson@artefactual.com, Artefactual Systems There are many different software applications and systems being used in collecting institutions to handle all aspects of managing their digital collections. Within a single institution, it is possible to have several tools with overlapping functionality. Sometimes the biggest gains in functionality and productivity come from a focus on connecting these systems together.  In this talk we will present several examples of integration and collaboration that we have been involved in while working on the Archivematica project. Examples of integrations with both open source and proprietary systems, as well as examples of collaborative development processes. == BYOB: Build Your Own Bootstrap == * Axa Mei Liauw, aliauw@princeton.edu, Princeton University Library* Kevin Reiss, kr2@princeton.edu, Princeton University Library Bootstrap is awesome! It allows for quick and easy front-end development without demanding too much time with the design of the user interface. A framework like Bootstrap can also help libraries address one of our top usability problems: wild inconsistency of styles and layouts across our own in-house applications and websites. However, what if you do not want to compromise your creativity and make your project visually stand out? With enough Sass or Less knowledge it is possible to highly customize Bootstrap to fit your needs, but in the end you still end up with your design and code buying into Bootstrap's markup and design conventions, which are not always what you want. Sometimes you simply want to start with a clean slate and not fight the framework and use only the components and features you need. In that case, build your own Bootstrap! In this talk we will discuss techniques for using some of the emerging tools from the front-end development and design communities to create a maintainable, modular in-house Sass toolkit that we are implementing within a variety of tools including Drupal, Rails applications, in house PHP applications, as well as within vendor solutions like Libguides and ILLiad. Some specific tools we will discuss are Grunt, Bower, and Sass tools like Singularity, Breakpoint, and Bourbon. == Plz to let me download this ebook: an idea for better leisure reading access == * Lauren Ajamie, lajamie@nd.edu, University of Notre Dame (I haven't presented at Code4Lib before) The landscape of finding and getting fiction (and non-fiction for leisure reading) has changed dramatically in the past few years, and one of the most disruptive new developments could turn out to be Oyster, a "Netflix for books" ebook subscription. While somewhat expensive and with a developing selection of materials, the platform is amazingly easy to use, and makes finding and reading ebooks a two step process: find a book, start reading. Compare this to getting ebooks (or even print books) from your library, a process which could take multiple user names and up to a dozen steps. For both the future of libraries, and my own selfish desires, I want to make this better! This speculative talk will discuss an idea I have (that I will need help with) to make finding and borrowing leisure reading materials less frustrating, and will hopefully result in a library-wide conversation about the discovery of, and access to, leisure reading materials. == Formats For All! The Future of the Archivematica Format Policy Registry == * Misty De Meo, mdemeo@artefactual.com, Artefactual Systems (first-time talk submitter) Archivematica's Format Policy Registry (FPR) is an open-source preservation planning tool. The FPR is designed to abstract away many of the challenges involved in identifying file formats, as well as picking the right tools to use to perform tasks like metadata extraction, format transformation and normalization. The first part of this talk will focus on the FPR's structure and its capabilities, but this isn't just a vendor pitch. The current version of the registry is only designed around Archivematica's usecases, but we want to bring the FPR to the world and make it work great for other software too. Share your format policies between Archivematica, Islandora, and Hydra! Share your file IDs between applications so you never misidentify a file again! Build new software without having to worry about the details of how to run external tools on files! The second part of the talk will focus on possible future developments, how the FPR might change, and what a community effort to bring the FPR forward might look like. == PeerLibrary – Facilitating the global conversation on academic literature == * Timothy Quach, UC Berkeley* Rachel Wolfsohn, UC Berkeley, rachel at peerlibrary.org* Mitar Milutinovic, UC Berkeley, mitar.code4lib at peerlibrary.org* Not presented or attended code4lib before We present [https://peerlibrary.org/ PeerLibrary] as an example of how to intertwine various tools and methods to spread the conversation about academic publications. PeerLibrary is unique because of our collaborative annotation and discussions layer integrated with the in-browser PDF viewer. PeerLibrary provides tools to annotate and comment directly on the works. Users can highlight important information and take notes in the margins online, just as how one would mark up a physical research paper. Our vision is a virtual space spans the horizontal of all academic knowledge, where individuals across the globe can connect and learn things only another human can help teach. PeerLibrary can be used as a system for depositing original work, archive navigation, to help organize conferences and journals, as a reference manager, a social network to follow what others are doing, for proposing/recommending connections, collaboration, reading, commenting, organizing or sharing papers. PeerLibrary is a platform that synthesizes an online repository and those who utilize it. Our longer-term goal is for PeerLibrary to become a web-first standards-based publication platform. We believe that all stages of research should be collaborative, from the idea, to experiments, conclusions and publication (constant feedback). To achieve this vision we are working with partners. Such as [http://www.contentmine.org/ ContentMine], to push facts they mine in academic publications into commons available through PeerLibrary. We use Internet Archive to permanently store open access publications and public annotations for future generations. We are using code developed at projects [http://hypothes.is/ Hypothes.is] and [http://annotateit.org/ Annotator] to ensure compatibility with other annotation projects and platforms. We are also using the [http://meteor.com/ Meteor framework], [http://lens.elifesciences.org/ eLife Lens], [https://github.com/guardian/scribe The Guardian Scribe] and [https://github.com/mozilla/pdf.js Mozilla PDF.js]. Our presentation will be an exploration of how these organizations are contributing to the Open Scholarship initiative.  With no subscription or registration needed, anybody can easily access the annotations in PeerLibrary. By eliminating the need to print files, the research process is contained in one online medium, creating a greater sense of organization. Furthermore, note-taking tools encourage active analysis, a recording of insights and questions while reading. Users can choose to keep their highlights and annotations private, or they can make them public to engage in an open online discussion. We believe that the collection of tools provided in PeerLibrary will make education more inclusive. See it live here: https://peerlibrary.org/

Stanford is using Fedora4 for managing Open Annotations, via a middleware component called TriannonProject presentation: https://vimeo. Triannon receives the JSON data from the annotation client, and uses the Linked Data Platform API implementation in Fedora4 to create, retrieve, update and delete the constituent resources. This component could be used with other LDP implementations, or with some additional development to ease the migration from other linked data sources into Fedora4. com/93085636

The presentation will focus on the benefits of the approach with respect to following international standards to ease system integration, and lessons learnt regarding the development processScreencast: https://vimeo.com/109787685