[CODE4LIB] Job: Web Services Librarian, Athens, Ohio, USA
Please excuse cross-posting. Position Announcement Web Services Librarian The Ohio University Libraries invites applications and nominations for the position of Web Services Librarian. We seek an innovative candidate who is comfortable in a changing environment; eager to engage stakeholders in a dynamic, fast-paced atmosphere; committed to working effectively with students, faculty and staff from diverse backgrounds; and energized by an exciting future. Reporting to the Head of Web Services, the Web Services Librarian performs ongoing analysis of the Libraries' web presence to support continuous improvement of the user experience; participates in the development, operation, and maintenance of Libraries web sites and services; and works with library staff to develop knowledge and capability in the use of web sites and services. *Working from a librarianship and customer service perspective, plans and conducts ongoing analysis of the Libraries' web services, including market research, user studies, web analytics and related activities toward the continuous improvement of the user experience. *In collaboration with the Web Designer, ILS Coordinator, and other staff, participates in the development, operation, and maintenance of the Libraries' web sites and services, possibly including but not limited to the Libraries' web site, integrated library system, discovery layer, link resolver, proxy server, and digital collections. *Provides library staff development, training, and support related to the Libraries' web sites and services. *Engages in continuing self-education as necessary to adapt to new technologies and continually improve the Libraries' web services. *Engages in regular professional development through research, publications, presentations and participation in regional and national associations as part of the continuing commitment to bring best practices and innovative services to Ohio University students and faculty. *In collaboration with the Libraries' IT Support Specialists, provides occasional general technical support to Libraries staff and patrons. Minimum Qualifications *Master's degree in Library/Information Science from an ALA-accredited program by the time of the appointment. *Experience using library web services (examples: integrated library systems, discovery layers, link resolvers) utilizing staff-facing services and/or assisting library patrons with the use of patron-facing services *Strong general computer literacy; ability to quickly learn and adapt to new technologies. *Familiarity with HTML and CSS and basic understanding of web site development and maintenance *Introductory-level familiarity with a computer programming or scripting language (examples: JavaScript, Python) *Demonstrated analytical and problem-solving skills Preferred Qualifications *Experience with web analytics software such as Google Analytics *Experience with web usability testing *Teaching, training, or technical support experience *Experience with the WordPress content management system, EBSCO library products, and/or Innovative Interfaces integrated library systems Ohio University Libraries takes pride in providing outstanding service to all its clientele. University Libraries is a member of the Association of Research Libraries, the Center for Research Libraries, and a founding member of OhioLINK. The Libraries' facilities include the Vernon R. Alden Library, the Music/Dance Library and the Southeast Ohio Regional Library Depository. With over 3,300,000 volumes, 2,000,000+ e-books and 55,000 e-journals, OHIO has one of the largest academic libraries in North America. During the 2012/2013 academic year, the Libraries received nearly 2,000,000 visits, 5,000,000+ database and catalog searches, and close to 12,000 virtual reference transactions. Alden Library housed the largest open-computing lab and wireless network on campus. The University Libraries are known for their leadership across campus for innovative technology services to students and researchers and a robust social media presence. Digitized collections include those of Senator George V. Voinovich; pioneer newspaper entrepreneur E.W. Scripps; King Chulalongkorn of Siam diaries; Ceremonial Artifacts Collection of the Yao culture of North Vietnam; and University Archives including yearbooks and videos. More information about the Libraries unique collections can be viewed at http://media.library.ohiou.edu/. Ohio University is a comprehensive, state-assisted institution that is classified, by the Carnegie Foundation as a Research Universities (high research activity) institution. Ohio University, located in the scenic foothills of the Appalachian Mountains, shares the City of Athens, a culturally-rich sustainable community 75 miles southea
[CODE4LIB] CFP: Second International Workshop on Linked Media (LiME 2014)
=== CFP: Second International Workshop on Linked Media (LiME 2014) http://www.linkedtv.eu/event/LiME2014/ === The workshop is co-located with the ESWC 2014 conference held in Heraklion, Greece on 25-29 May 2014. *Deadlines*: - Submission deadline: March 6, 2014, 23:59PM Hawaii Time - Notifications: April 1, 2014, 23:59PM Hawaii Time - Camera ready version: April 15, 2014, 23:59PM Hawaii Time Goals of the workshop: If the future Web will be able to fully use the scale and quality of online media, a Web scale layer of structured and semantic media annotation is needed, which we call *Linked Media*. Drawing on the success of the Linked Data movement, we believe annotation of media using Linked Data concepts can be the basis for Web-wide media interlinking based on concept matching and relationships. This 2nd international workshop on Linked Media (LiME'2014), building on last year's successful event held at WWW 2013, aims at promoting the principles of Linked Media on the Web by gathering semantic multimedia and Linked Data researchers to exchange current research and development work on creating conceptual descriptions of media items, multimedia metadata publication on the Web, and its semantic processing, particular based on Linked Data approaches to concept matching and relationships. Specifically, we aim to build a research community to promote a future Web where automated multimedia analysis results can be used as a basis to integrate Linked Data-based conceptual annotations into structured media descriptions, which can be published and shared online. When media descriptions are more easily findable and processable, new applications and services can be created in which online media is more easily shared, retrieved, re-used and re-purposed. This will offer a wide ra! nge of possibilities for various stakeholders in the creative industries. Workshop topics and themes: To push further the evolution of the Rich Media Web, and to facilitate its convergence with the Semantic Web, it is essential to establish consensus on online media annotation standards, the use of semantics in describing what media represents, and demonstrate approaches to leverage such structured and semantic media descriptions in Web applications. While non-textual content is often now the first destination of online agents rather than HTML/textual resources, and thus access to structured annotation of the online media is increasingly important for new Web applications capable of media search, retrieval, adaptation and presentation, the online media annotation space is still limited, fragmented and lacking in consensus for building Web tools and interfaces to support it. LiME'2014 focuses on identifying the key building blocks required to foster the development of new Web tools and interfaces that will support the growth and re-use of Linked Media, which is inspired by the Linked Data movement for making structured descriptions of resources more easily available online. The workshop topics include, but are not limited to: * Approaches to online media descriptions - Tools and approaches aligning the fragmented approaches to online media description, its processing and publication, e.g. based around Linked Data, W3C Media Ontology and Media Fragments URI. - Tools and approaches to search and retrieval of online media based on its structured description, scaling to the Web - Tools and approaches addressing issues of trust, quality and rights of online media * Extracting and linking - Tools and approaches to lower the cost of creating structured descriptions of online media resources - New methods of automatic, real time, metadata extraction of any online media content (including live streams) - Ideas how to incorporate Linked Data into media description (and benefit from the additional metadata of the Linked Data cloud) - New methods for automatically assessing the suitability of (non-trusted) content for interweaving (e.g. violence detection, nudity detection), and publishing such assessments * Showcases, business models and assessment - New Web applications making use of Linked Media (across different platforms) including evaluation with end-users and/or suitable business models - Approaches to tracking user interaction with media (and exploiting this knowledge to enrich annotations) The workshop is sponsored by the EU projects LinkedTV (http://www.linkedtv.eu) and MICO (http://www.mico-project.eu/) as well as the large open source community around Apache Stanbol (http://stanbol.apache.org/) & Apache Marmotta (http://marmotta.apache.org/). Submission: Submissions should not exceed 12 pages and are to be formatted according to Springer LNCS guidelines (http://www.springer.com/computer/lncs?SGWID=0-164-7-72376-0) and submitted to htt
Re: [CODE4LIB] A couple quick questions for Hydra or Islandora users
On Tue, Feb 18, 2014 at 2:43 PM, Brown, Jacob wrote: > Greetings! A couple quick questions for Hydra or Islandora > users/developers: > > 1) What made you choose your framework over others (for example, DSpace)? > What is its "killer feature"? Flexibility? More metadata options? > Availability of SPARQL endpoint? Language? The community? > > Hi! We chose Hydra at Penn State after confirming it would meet our functional (feature checklist) and architectural (multiple apps using a common, extensible platform) needs. The big reason? The community. Community is the heart of Hydra, not Fedora or Rails or any particular technology. The consistent growth, technical maturity, and vibrant collaborative climate are what convinced us that Hydra was the best community for us to be involved in. A colleague and I wrote a bit about how community is a fundamental strategy for our efforts, which touches on how/why we selected Hydra. You can read that here if you want more info: http://www.diglib.org/archives/5288/ The number of partners has doubled each of the past couple years -- we're now up to 21 partners, with more on the way. To see the list of partners, check out the footer of projecthydra.org. 2) What has your experience been like developing within that framework? If > you migrated from another digital asset management system, what are the > comparative strengths/weakness of your framework? > > Our experience has been extremely positive, and we continue to be engaged in sustaining and growing the Hydra community and its technologies. The overriding strength of Hydra, AFAIC, is the growing number of institutions that have committed not only to using it but to maintaining it and improving it; Hydra is organized in a decentralized, distributed manner, and each of the partners holds a stake in advancing it. I can't say I've witnessed more vibrant or more diverse development communities within libraryland and that was more important to us than some of the more tactical concerns like Rails v. Django, Solr v. ElasticSearch, or Fedora v. whatever. Good luck with your fact-finding mission, Jacob! -Mike
Re: [CODE4LIB] A couple quick questions for Hydra or Islandora users
Jacob, On Feb 18, 2014, at 5:43 PM, Brown, Jacob wrote: > Greetings! A couple quick questions for Hydra or Islandora users/developers: > > 1) What made you choose your framework over others (for example, DSpace)? > What is its "killer feature"? Flexibility? More metadata options? > Availability of SPARQL endpoint? Language? The community? We chose Hydra. It was the only solution that fit our metadata and storage needs. Hydra has a lot of flexibility, allowing you to model your content as you wish, and use any metadata standard you wish, while at the same time having a lot of very solid core features. Being written in Ruby, and using the Rails framework, I found this compelling because I could develop new features fairly quickly. Test-driven development practices, which are at the heart of Rails as well as Hydra, made me feel confident that introducing new features wouldn’t break existing ones. The Hydra community has also been incredibly helpful, too. I wouldn’t have been able to do what I’ve done without it. > > 2) What has your experience been like developing within that framework? If > you migrated from another digital asset management system, what are the > comparative strengths/weakness of your framework? For Ruby on Rails, I was completely new to it. I knew a lot of PHP and Perl, but very little of Java. This prevented me from digging into DSpace of Fedora’s source code for solutions. Hydra helps you interface with Fedora, but in a Rails way. I latched on to Ruby right away, and just sort of went from there. It has its strengths and weaknesses, and its idiosyncrasies, no doubt, but as a framework/interface for Fedora, it fit the bill regarding our application needs, so the weaknesses and idiosyncracies weren’t an issue. It was a steep learning curve, but that mostly had to do with my lack of experience with Rails, as well as Solr, Blacklight, and the other components of the Hydra “stack”. I wouldn’t try to push it on someone else who’s trying to make their own decisions, but only offer my experiences and resources if you’d like to investigate it further. Checkout the Dive into Hydra tutorial [1] and feel free to send questions to our mailing list: hydra-t...@googlegroups.com Best of luck, …adam __ Adam Wead Systems and Digital Collections Librarian Library + Archives Rock and Roll Hall of Fame and Museum 216.515.1960 aw...@rockhall.org [1] https://github.com/projecthydra/hydra/wiki/Dive-into-Hydra
Re: [CODE4LIB] Python CMSs
Though I haven't used it myself, there is a new open source Django CMS that is called Wagtail. It was originally built for the Royal College of Art in London. They say their focus is on flexibility and user experience and do have a demo site and docs. Here's the Github page in case it might be of interest: https://github.com/torchbox/wagtail/ HTH, Amy Shelton
