[CODE4LIB] Job Posting: infrastructure developer at Stanford University Libraries
Software Engineer/Java Developer for Digital Library Systems and Services This is a 2 year fixed term position. Full description and application process found at http://jobs.stanford.edu/find_a_job.html Search for keyword 30271 Short Description: The System Software Developer for Digital Library Systems will play an integral role in defining, developing and delivering information systems and infrastructure for the library of the future at Stanford University. As part of the Digital Library Systems and Services (DLSS) unit within Stanford University Libraries, the successful candidate will help lead development efforts to support scholarship in the digital age by delivering on the promises of the digital library. The incumbent will be a part of the Digital Library Infrastructure group, focused on realizing core components of Stanford's emerging digital library architecture. The team will deliver cross-cutting digital library services and infrastructure, such as metadata generation, transformation and management; service oriented library cyberinfrastructure; and digital asset rights management. This group works closely with peer teams focused on other aspects of digital library functionality, including Web/UI application development, and the creation of common and reusable technologies and components. The successful candidate will be responsible for the design and initial development of key technologies needed to support Stanford’s vision of the digital library of the future. Duties and Responsibilities: - Principle responsibility for implementing the Digital Object Registry, a core XML- and RDF-based metadata management component of our digital library, plus critical related services. - Lead role in defining and implementing an underlying strategy for a simple, REST-based service oriented architecture to deliver infrastructure services. - Provide analysis and software engineering support for implementing and leveraging the open source Fedora framework as part of our overall digital library access and management architecture. - Contribute analysis, expertise and development to other SULAIR cyberinfrastructure and content middleware efforts, e.g., digitization workflow tools; metadata generation, transformation, editing QA tools; personalization and collaboration. - Work collaboratively with the the DLSS web development team, Stanford Digital Repository team, metadata experts, digitization staff and information architects to help define and develop an extensible, robust and modular digital library architecture, infrastructure and application environment. Qualifications: - Proven success as a software engineer in a J2EE environment, and experience in contributing to and/or defining the technical architecture of complex systems. - Demonstrated ability to write solid, simple, elegant code both independently and in a team-programming environment and within schedule limitations. - Demonstrated success in working in an academic environment. - Demonstrated ability to work collaboratively on a project from specification to launch; and to work with multiple levels of staff, and colleagues at peer institutions and open source communities. - Knowledge of agile software development practices and test driven design principles. Demonstrated understanding of best practices for software development, and an ability to introduce and reinforce application of those practices in a team environment. - Expertise in Java, familiarity with C and C+. Working knowledge of, or ability to quickly learn, relevant scripting technologies such as Perl, Ruby on Rails, Python, AJAX, etc. - Demonstrated expertise with XML and related tools and technologies (e.g., XML schema, schema management and databases, XSLT, X-forms). Familiarity with RDF and its relationship to Library metadata standards. - Knowledge of SQL and relational database concepts. - Masters degree or equivalent professional experience in Computer Science, Information Science or related field. - Five or more years experience designing middleware, services or infrastructure for software systems. Desired: - Experience in digital library community. - Familiarity with library-related metadata and metadata standards, particularly MARC, MODS, METS, TEI, EAD. - Software Quality Assurance (functional and performance) and testing experience with various applications. -- (Mr.) Lynn McRae Infrastructure/Integration Architect Stanford University Libraries
[CODE4LIB] FW: CDL releases eXtensible Text Framework (XTF) 2.1
-- Forwarded Message From: Lisa Schiff [EMAIL PROTECTED] Date: Tue, 13 May 2008 14:53:30 -0700 To: [EMAIL PROTECTED] Subject: CDL releases eXtensible Text Framework (XTF) 2.1 **This announcement is being widely released; apologies in advance for duplication.** FOR IMMEDIATE RELEASE Contact: Lisa Schiff California Digital Library University of California, Office of the President 415 20th St., 4th Floor Oakland, CA 94612 (510) 587-6132 [EMAIL PROTECTED] http://www.cdlib.org/inside/projects/xtf/ California Digital Library Announces New Release of the eXtensible Text Framework (XTF) Oakland, CA, May 12, 2008 - The California Digital Library (CDL) is pleased to announce a new release of its search and display technology, the eXtensible Text Framework (XTF) http://www.cdlib.org/inside/projects/xtf/ version 2.1 (http://www.cdlib.org/inside/projects/xtf/ ). XTF is an open source, highly flexible software application that supports the search, browse and display of heterogeneous digital content. XTF offers efficient and practical methods for creating customized end-user interfaces for distinct digital content collections. Highlights from the 2.1 release include: * Extensive interface improvements, including new search forms, built-in faceted browsing, and a new look and feel. * Increased support for document and information exchange formats. * XHTML and OAI-PMH output * NLM article format indexing and output * Microsoft Word indexing * Streamlined XSLT stylesheets for simpler deployment and adaptation. * Updated documentation that has been moved to the XTF project wiki http://xtf.wiki.sourceforge.net/ , allowing XTF implementers to share solutions with entire user community. * Freeform Boolean query language, offered as an experimental feature. * Backward compatibility with existing XTF implementations. A complete list of changes http://xtf.wiki.sourceforge.net/changeLog_2.1 is available on the XTF Project page on SourceForge http://sourceforge.net/projects/xtf/ , where the distribution (including documentation) can also be downloaded. Since the first deployment of XTF in 2005, the development strategy has been to build and maintain an indexing and display technology that is not only customizable, but also draws upon tested components already in use by the digital library and search communities - in particular the Lucene text search engine, Java, XML, and XSLT. By coordinating these pieces in a single platform that can be used to create multiple unique applications, CDL has succeeded in dramatically reducing the investment in infrastructure, staff training and development for new digital content projects. XTF offers a suite of customizable features that support diverse intellectual access to content. Interfaces can be designed to support the distinct tools and presentations that are useful and meaningful to specific audiences. In addition, XTF offers the following core features: * Easy to deploy: Drops directly in to a Java application server such as Tomcat or Resin; has been tested on Solaris, Mac, Linux, and Windows operating systems. * Easy to configure: Can create indexes on any XML element or attribute; entire presentation layer is customizable via XSLT. * Robust: Optimized to perform well on large documents (e.g., a single text that exceeds 10MB of encoded text); scales to perform well on collections of millions of documents; provides full Unicode support. * Extensible: * Works well with a variety of authentication systems (e.g., IP address lists, LDAP, Shibboleth). * Provides an interface for external data lookups to support thesaurus-based term expansion, recommender systems, etc. * Can power other digital library services (e.g., XTF contains an OAI-PMH data provider that allows others to harvest metadata, and an SRU interface that exposes searches to federated search engines). * Can be deployed as separate, modular pieces of a third-party system (e.g., the module that displays snippets of matching text). * Powerful for the end user: * Spell checking of queries * Faceted displays for browsing * Dynamically updated browse lists * Session-based bookbags These basic features can be tuned and modified. For instance, the same bookbag feature that allows users to store links to entire books, can also store links to citable elements of an object, such as a note or other reference. A sampling of XTF-based applications both within and outside of the CDL include: * Mark Twain Project Online http://www.marktwainproject.org/ (http://www.marktwainproject.org), developed by the Mark Twain Papers Project, the CDL and the University of California Press. * Calisphere http://www.calisphere.org/ (http://www.calisphere.org/), a curated collection of primary sources keyed to the curriculum standards of California¹s K-12 community, developed by the CDL. * The Encyclopedia of Chicago
Re: [CODE4LIB] place for code examples?
Out of curiosity, as an infrequent wikier, why the strong preference for dokuwiki? On Mon, May 12, 2008 at 10:30 AM, Jonathan Rochkind [EMAIL PROTECTED] wrote: I would still personally really like a dokuwiki hosted at code4lib.org. I am not happy with the mediawiki. If anyone is interested in setting up and admining a dokuwiki, I would support that. Jonathan Ryan Eby wrote: Just catching up now on Code4Lib emails. I threw this idea around awhile back in #code4lib and it seemed like most thought people used their own blog for snippets and code hosts for real projects and it wasn't worth doing. I was thinking wiki for code snippets with maybe svn for various small libraries / hacks. At the time I was looking at just using trac so the two would be together. If there's enough movement for just the snippets parts then I agree with others that dokuwiki or drupal category would probably be useful. Eby On Fri, Mar 28, 2008 at 5:07 PM, Keith Jenkins [EMAIL PROTECTED] wrote: Does there already exist some place to put some code examples to share with the code4lib community? (I'm thinking of snippets somewhere on the order of 10-100 lines, like the definition of a php function.) Keith -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu -- Andrew Darby Web Services Librarian Ithaca College Library http://www.ithaca.edu/library/ [EMAIL PROTECTED]
Re: [CODE4LIB] place for code examples?
1. It is set up for including code samples in a way that MediaWiki is not. 2. It allows one wiki installation to include various sub-sections which are kept seperarate, in seperate namespaces. We have several different independent projects on our MediaWiki, but MediaWiki mixes them all together. 3. In general, it was written for documentation and code content, rather than for encyclopedia content. Code4Lib needs tilt more toward the former. Jonathan Andrew Darby wrote: Out of curiosity, as an infrequent wikier, why the strong preference for dokuwiki? On Mon, May 12, 2008 at 10:30 AM, Jonathan Rochkind [EMAIL PROTECTED] wrote: I would still personally really like a dokuwiki hosted at code4lib.org. I am not happy with the mediawiki. If anyone is interested in setting up and admining a dokuwiki, I would support that. Jonathan Ryan Eby wrote: Just catching up now on Code4Lib emails. I threw this idea around awhile back in #code4lib and it seemed like most thought people used their own blog for snippets and code hosts for real projects and it wasn't worth doing. I was thinking wiki for code snippets with maybe svn for various small libraries / hacks. At the time I was looking at just using trac so the two would be together. If there's enough movement for just the snippets parts then I agree with others that dokuwiki or drupal category would probably be useful. Eby On Fri, Mar 28, 2008 at 5:07 PM, Keith Jenkins [EMAIL PROTECTED] wrote: Does there already exist some place to put some code examples to share with the code4lib community? (I'm thinking of snippets somewhere on the order of 10-100 lines, like the definition of a php function.) Keith -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu -- Andrew Darby Web Services Librarian Ithaca College Library http://www.ithaca.edu/library/ [EMAIL PROTECTED] -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu
[CODE4LIB] Job Posting - DSpace developer
As you may know, Harvard's faculty in the Faculty of Arts and Sciences has recently voted to provide open access to scholarly articles created by faculty. This job posting is in support of that goal. If interested, please contact Randy Stern. Digital Library Software Engineer Harvard University Library Office for Information Systems Grade 57, One Year Term Duties Responsibilities: Reporting to the Manager of Systems Development in the Office for Information Systems, serves as the lead developer for software applications and tools for the implementation of a new institutional repository within the Harvard University Library. Responsibilities include the configuration, customization, and on-going support of a DSpace instance at Harvard, as well as the development, maintenance, and integration of institutional repository software tools to create an extremely user friendly deposit and repository management and reporting process. May also integrate authentication processes and other DSpace modules with Harvard systems. This position includes customizing the user interface of DSpace, utilizing XML, XSL, and JSP technologies. This position requires the ability to grasp a high level view of requirements from discussions with stakeholders, recommend solutions, and iteratively translate that into specifications, prototypes, and working code with accompanying documentation. Requirements: BA/BS in computer science with a minimum of 4 years development experience in java. Ability to produce results and work independently with general guidance in an environment in which requirements evolve over time. Strong interpersonal, verbal and written communication skills. Experience designing, developing, deploying, and managing both stand alone and Internet applications utilizing Unix and World Wide Web technologies. Experience with java stand alone and web applications, SQL, JDBC, XML, XSL, HTML. Desirable: Experience with IT and library systems in a higher education environment; experience with Open Source software; familiarity with library metadata standards such as Dublin Core, METS, MODS, and the OAI protocol; knowledge of associated digital storage formats and conversion principles, procedures, and operations; strong understanding of information organization and retrieval technologies used to organize, store, and access digital content; experience with programming best-practices, including test-drive development and design patterns. Hands-on experience with DSpace, Perl, CVS, Eclipse, Struts, Tomcat, Cocoon, Maven, Ant a plus. Randy Stern Manager of Systems Development Harvard University Library Office for Information Systems 90 Mount Auburn Street Cambridge, MA 02138 Tel. +1 (617) 495-3724 Email [EMAIL PROTECTED]
Re: [CODE4LIB] place for code examples?
On Fri, Mar 28, 2008 at 4:07 PM, Keith Jenkins [EMAIL PROTECTED] wrote: Does there already exist some place to put some code examples to share with the code4lib community? (I'm thinking of snippets somewhere on the order of 10-100 lines, like the definition of a php function.) At the risk of sounding really stupid amidst the discussion of wikis and repositories... why not pastie? Sure, it's not a 'forever' solution, but will your code snippet really be interesting in 5 years? Curious, -Nate
Re: [CODE4LIB] Q.: deep-linking syntax for Encore?
Is anybody using III's Encore system and happens to know if there is a deep-linking syntax, either documented or inferred, for it? I'm not actually using this, but you can reference an individual record using the syntax http://encore.scottsdaleaz.gov/iii/encore/record/C|Rb1425309 where b1425309 is the record number. This will give you a nice looking public display. If you need anything other than a formatted record display based on a simple record number or keyword search, you are much better off working in the old catalog (which all Encore libraries still have) -- it has significantly more search and display options. As far as I can tell, Encore allows keyword searching only, and there is no way to pull a record in MARC view, to search by ISBN/ISSN or do a number of other tasks. That's probably why clicking on the Advanced search button in an Encore system or on the Find out more in the individual record display takes you to the old system. kyle
Re: [CODE4LIB] Life after Expect
Is their any hope for those of us who rely on our Expect-monkeys in III? My most important Expect scripts use the create-list function, and I hope that'll stay around for a while. But I'm sure they'll eventually go away too. Has III shown any interest in building in their own macros/automation features to do the sorts of tasks for which we rely on Expect? Ken Kyle Banerjee wrote: Last week, III announced that they are removing a number of circulation functions from the telnet menus in a software update that became generally available this month. From what I've been able to surmise, functions that will be removed include placing holds and checking things in or or out. Removing these menu options will break scripts that have been in use for years at institutions in our consortium, and lots more staff time will be required to perform certain tasks after some systems are upgraded. Apparently, III recently discovered that a bug involving holds was caused by the character-based system, but it is also related to a desire to port everything to Millennium. Based on the reasoning behind the announcement, future updates are likely result in other mission critical scripts breaking as other character-based functionality is deprecated. Just a reminder of the risks of relying on automation that depend on interfaces that are losing vendor support. kyle -- Ken Irwin Reference Librarian Thomas Library, Wittenberg University
