We had the first meeting today of what we’re calling our Linked Open Data Working Group. In addition to myself, group members are Mackenzie Brooks (Digital Humanities Librarian), Jeff Knudson (Senior Technology Architect\/ITS), and Brandon Walsh (Mellon Digital Humanities Fellow).<\/p>\n
What is it we want to accomplish through this group?<\/p>\n
We want to think about LOD in the context of our specific DH projects in order to avoid talking about it in the abstract. But we also want to make sure that we clearly identify what we want to accomplish with those projects instead of having a solution (e.g., LOD) that is looking for a problem to solve. In other words, we’re going to develop the vision for the project and then work backwards.<\/p>\n
We have several potential projects but the easiest to get started on is\u00a0literary networks<\/a>. This project evolved out of archival research relating to the Shenandoah literary magazine<\/a> published by W&L. While Shenandoah is partially indexed in MLA, a full index of Shenandoah has never been produced. (Also, the contents are not in JSTOR.) \u00a0A student worker in the library has compiled an index as part of her job in Special Collections and Archives. Our DH Librarian (previously our Metadata Librarian) identified the necessary fields and created\u00a0the spreadsheet for the data entry. The Shenandoah index has over 6,400 entries.<\/p>\n Our first task in this project doesn’t actually involve LOD: creating a web-based index to Shenandoah. But we want to keep LOD principles in mind as we develop the index. The Shenandoah data set provides research material that goes far beyond merely an index to a journal.<\/p>\n While the research agenda of the literary networks project is the topic of a future post, the essence is that I want to examine the relationships and connections among authors and editors.<\/p>\n <\/p>\n Top-level functionality<\/strong><\/p>\n Here are primary features involved in a LOD approach to this data set. Each feature is a different stage, or layer, of the project. A use case scenario describes functionality enabled by each stage.<\/p>\n Use case<\/em>: Queries based on editor. From these queries we can form network graphs based on relationships among authors and editors and issues.<\/p>\n Use case<\/em>: Exposing this data set as a LOD triple store (with possibilities of generating query results in json & csv) allows for the data to be analyzed in a variety of tools such as Palladio, R, Gephi. Plus, it provides the ability for other projects to integrate this data.<\/p>\n Use case<\/em>: the web interface shows brief biographical information and publishing history about each author. Instead of gathering this data manually and entering it directly into the data set, we want to explore creating a process that connects external information about these authors with\u00a0this data by consuming LOD.<\/p>\n Use case<\/em>: literary networks are influenced by friendships and social contacts. Publishing decisions are often made by brokers (e.g., Ezra Pound), whose influence is not formally represented in the index data. There’s a complex challenge in figuring out how to represent this information.<\/p>\n Use case<\/em>:\u00a0While the data set starts with one specific literary journal (Shenandoah), it’s the connections among authors and editors publishing in a larger set of journals during the same time period that is more interesting. Authors do not simply write for one publication.\u00a0Ultimately, the literary networks project will create a data set of authors (and editors) who published in mid-century literary journals.<\/p>\n From originating with the Shenandoah data set we gain experience with the process of utilizing LOD. What we learn through this initiative\u00a0can be applied to other projects, particularly those with biographical data.<\/p>\n Process of the LOD working group<\/strong><\/p>\n As a group we will meet once a month. We will use a Slack channel in the W&L\u00a0DHAT team for communication.<\/p>\n","protected":false},"excerpt":{"rendered":" We had the first meeting today of what we’re calling our Linked Open Data Working Group. In addition to myself, group members are Mackenzie Brooks (Digital Humanities Librarian), Jeff Knudson (Senior Technology Architect\/ITS), and Brandon Walsh (Mellon Digital Humanities Fellow). What is it we want to accomplish through this group? Develop a better understanding of […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5,34],"tags":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/posts\/962"}],"collection":[{"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/comments?post=962"}],"version-history":[{"count":27,"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/posts\/962\/revisions"}],"predecessor-version":[{"id":991,"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/posts\/962\/revisions\/991"}],"wp:attachment":[{"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/media?parent=962"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/categories?post=962"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/endlesshybrids.com\/wp-json\/wp\/v2\/tags?post=962"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
\n
\n