[CODE4LIB] Software developer position open @ Penn State Digital Library Technologies

[Michael J. Giarlo]

Working at the University Park campus of Penn State has its perks:
generous benefits, great schools, affordable real estate, proximity to
many trails and rivers, and safe neighborhoods lined with trees and
views of the Alleghenies.

The Libraries and central IT organization are hard at work on building
an institutional digital stewardship program and this is an
opportunity to join a talented team of technologists, librarians, and
curators, writing code to help provide access and discovery services
and keep data around for the long haul.

But really, the primary perk is getting to work with me because, let's
face it, I'm a pretty OK guy.  Apply early, apply often*!

-Mike

* Just once will do.



Software Developer (Programmer/Analyst)
Job number: 33102
Date Announced: 10/01/2010

Digital Library Technologies, a unit of Information Technology
Services at The Pennsylvania State University, has a vacancy for a
Software Developer. The Software Developer will develop and integrate
software and web applications for an institutional content stewardship
program. This requires the ability to work collaboratively with
content curators as well as fellow technologists. The Software
Developer will be expected to: share advancements in standards,
software development practices, and IT trends; constantly refine his
or her skill set; and apply new knowledge and techniques. This is an
opportunity to work with an innovative unit on building a sustainable,
enterprise-level content stewardship program at a large, multi-campus
institution recognized for its commitment to excellence. This job will
be filled as a level 3 or level 4, depending upon the successful
candidate’s education and experience. Typically requires a Bachelor’s
degree in computer science, information science, or related field plus
four years of experience developing and deploying software in a team
environment or an equivalent combination of education and experience
for a level 3. Additional experience and/or education and competencies
are required for higher level jobs.

The successful candidate will demonstrate: proficiency with multiple
programming languages and more than one programming language paradigm;
enthusiasm for staying informed about cutting-edge technologies for
use with software development initiatives, and for engaging the
broader digital library software development community; ability to
work independently and as a member of a team with diverse
constituencies; commitment to providing outstanding customer service;
excellent interpersonal, oral, and written communication skills.
Desired: working knowledge of command-line environments and Web
architecture, Web services based on the REST architectural style, and
the Linked Data pattern; experience with Web-based client- and
server-side programming; knowledge of digital repository and content
management services and toolkits; familiarity with digital library
standards such as OAI-ORE and SWORD; understanding of semantic
technologies such as descriptive metadata and RDF ontologies;
experience with shared or distributed version control systems and
practices; experience solving deployment issues regarding scale,
stability, and performance; experience releasing open source software.

Apply online at http://psu.jobs/ (job # 33102)

Re: [CODE4LIB] Systems Tracker

[marijane white]

I believe Marshall Breeding's Library Technology Guide covers some of what
you're looking for.
http://www.librarytechnology.org/



-marijane

On Fri, Oct 1, 2010 at 1:43 PM, Dave Bretthauer
wrote:

> Hello LITA and Code4Lib colleagues,
>
>
>
> We at UConn Libraries find ourselves looking to other institutions
> frequently when seeking solutions.
>
>
>
> As a result, we've been discussing how we might begin an effort to track
> enterprise software used by our colleagues at other institutions, rather
> than seek this information on an ad-hoc basis every time we need
> it-software such as:
>
> *   Integrated Library System (e.g. Koha, Unicorn, etc.)
> *   Web Content Management System (e.g. Drupal, Vignette)
> *   Learning Management System (e.g. Sakai, Blackboard)
> *   OpenURL Link Resolver (e.g. SFX, 360LINK)
> *   Metasearch (e.g. MetaLib)
> *   Discovery (e.g. Ebsco Discovery Service, Primo Central)
> *   Electronic Resources Management (e.g. CORAL, III's ERM)
> *   Reserves Management (e.g. Reserves Direct, Aries)
> *   Document Delivery/Interlibrary Loan (e.g. ILLiad)
> *   Digital Asset Management (e.g. Rezuna, Artesia)
> *   Local Digital Collection Management (e.g. Fedora, CONTENTdm)
> *   Institutional Repository (e.g. DSpace, DigitalCommons)
> *   Find Aids Search Tool (e.g. XTF)
> *   Authentication/Authorization methods used (e.g. LDAP, CAS,
> Shibboleth)
> *   Institutional ERP (e.g. Kuali, Peoplesoft)
>
>
>
> This is a partial, brainstormed list which obviously will change. We're
> looking for a balance of useful & manageable without becoming
> overwhelming. Also, the examples above are not intended as endorsements,
> just examples to help clarify since lines of distinction between
> categories are not always clear.
>
>
>
> We are not thinking of this as a rating or evaluation tool, rather
> simply a tool to keep track of this information to help us see who's
> using which software tools to accomplish a set of tasks or services.
>
>
>
> Our questions for the LITA and Code4Lib communities at the moment:
>
> 1.  Does anyone know of such a resource already available? Assuming
> the answer is no...
> 2.  Would such a database be of interest to you or others at your
> institution (i.e., would you find  such a database useful in your
> organization if we made it available publicly)?
> 3.  If we created such a resource and made it available, would you
> be willing to contribute information to it about your home institution
> and keep it up to date?
> 4.  What other systems or organizational eccentricities would you
> find useful to include in such tracking?
> 5.  Would you be interested in having this data tracked over time,
> or only the current state?
> 6.  What data points should be gathered? We have thus far can
> thought of software, version, locally hosted or remotely hosted (e.g.
> cloud)? Also, institutional entity granularity will need to be
> subdivided for some of these, we know.
>
>
>
> What do you think?
>
>
>
> Thanks for sharing any thoughts you have.
>
>
>
> Dave
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Dave Bretthauer
>
> Library Webmaster
>
> Digital Programs Team
>
> University of Connecticut Libraries
>
> 369 Fairfield Way U-2005P
>
> Storrs, CT 06269-2005
>
> Voice: (860) 486-6494
>
> Fax: (860) 486-6017
>
> http://www.lib.uconn.edu/~dbretthauer
> 
> >
>
>
>
>
>

[CODE4LIB] Systems Tracker

[Dave Bretthauer]

Hello LITA and Code4Lib colleagues,

 

We at UConn Libraries find ourselves looking to other institutions
frequently when seeking solutions.

 

As a result, we've been discussing how we might begin an effort to track
enterprise software used by our colleagues at other institutions, rather
than seek this information on an ad-hoc basis every time we need
it-software such as:

*   Integrated Library System (e.g. Koha, Unicorn, etc.)
*   Web Content Management System (e.g. Drupal, Vignette)
*   Learning Management System (e.g. Sakai, Blackboard)
*   OpenURL Link Resolver (e.g. SFX, 360LINK)
*   Metasearch (e.g. MetaLib)
*   Discovery (e.g. Ebsco Discovery Service, Primo Central)
*   Electronic Resources Management (e.g. CORAL, III's ERM)
*   Reserves Management (e.g. Reserves Direct, Aries)
*   Document Delivery/Interlibrary Loan (e.g. ILLiad) 
*   Digital Asset Management (e.g. Rezuna, Artesia)
*   Local Digital Collection Management (e.g. Fedora, CONTENTdm)
*   Institutional Repository (e.g. DSpace, DigitalCommons)
*   Find Aids Search Tool (e.g. XTF)
*   Authentication/Authorization methods used (e.g. LDAP, CAS,
Shibboleth)
*   Institutional ERP (e.g. Kuali, Peoplesoft)

 

This is a partial, brainstormed list which obviously will change. We're
looking for a balance of useful & manageable without becoming
overwhelming. Also, the examples above are not intended as endorsements,
just examples to help clarify since lines of distinction between
categories are not always clear.

 

We are not thinking of this as a rating or evaluation tool, rather
simply a tool to keep track of this information to help us see who's
using which software tools to accomplish a set of tasks or services.

 

Our questions for the LITA and Code4Lib communities at the moment:

1.  Does anyone know of such a resource already available? Assuming
the answer is no...
2.  Would such a database be of interest to you or others at your
institution (i.e., would you find  such a database useful in your
organization if we made it available publicly)?
3.  If we created such a resource and made it available, would you
be willing to contribute information to it about your home institution
and keep it up to date?
4.  What other systems or organizational eccentricities would you
find useful to include in such tracking?
5.  Would you be interested in having this data tracked over time,
or only the current state?
6.  What data points should be gathered? We have thus far can
thought of software, version, locally hosted or remotely hosted (e.g.
cloud)? Also, institutional entity granularity will need to be
subdivided for some of these, we know.

 

What do you think?

 

Thanks for sharing any thoughts you have.

 

Dave

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Dave Bretthauer

Library Webmaster

Digital Programs Team

University of Connecticut Libraries

369 Fairfield Way U-2005P

Storrs, CT 06269-2005

Voice: (860) 486-6494

Fax: (860) 486-6017

http://www.lib.uconn.edu/~dbretthauer
 

 

 

[CODE4LIB] Position announcement: Metadata Librarians, Cornell University Library, Ithaca, NY

[Dianne Dietrich]

Cornell University Library seeks two creative, productive librarians who will 
explore, lead, and collaborate on diverse projects. The successful candidates 
will work at the intersection of many user-focused services and projects, which 
may include technical services, archives, data curation, and digital libraries. 
One librarian will primarily work on projects related to the humanities and 
special collections, and the other position will include responsibilities 
related to e-science and research data. The successful candidates will be 
comfortable in exploring emerging technologies and standards for description 
and access, and they will welcome working in a collegial and collaborative 
environment. The positions will be an integral part of the newly merged 
Cataloging and Metadata Services division, a team evolving and expanding to 
meet users' needs for the discovery and delivery of resources.

Position Description:

Under the general direction of the Assistant Director, Cataloging and Metadata 
Services, the Metadata Librarians provide metadata consultation, design, and 
development services to facilitate the use of digital and analog information 
for research and education. These
librarians work simultaneously on various metadata projects, collaborating 
closely with staff throughout Central Library Operations, Digital Scholarship 
Services, Information Technology, and various special collections units to 
enhance access to the library's collections. The Metadata Librarians 
participate in the library's research and development efforts and in local and 
national discussions relating to the access, retrieval, description, 
preservation, and management of objects in digital collection systems. The 
librarians play an active role in professional organizations inside and outside 
of the Cornell University Library community.

Duties and responsibilities may include:

* Participate in Cornell University Library initiatives related to the 
discovery of digital resources.
* Consult with Cornell's faculty, staff, and community partners on a variety of 
metadata and information organization and access needs.
* Recommend, design, and implement appropriate metadata schemes for digital 
library projects.
* Draft metadata components of grant proposals.
* Assist Cornell researchers in the preparation of data management plans.
* Establish workflows for metadata creation or capture.
* Suggest methods for streamlining or automating metadata creation and 
management, using various tools for metadata manipulation and scripting.
* Collaborate with database management staff on batch processing projects.
* Assess and work to improve access to resources such as e-books, CUL web 
sites, and locally-created digital collections.
* Advise on digital preservation strategies, including metadata used for CUL 
digital repositories.
* Serve as a resource to departments and staff on issues related to metadata 
and digital initiatives.
* Create and maintain local documentation on metadata standards and metadata 
application guidelines.
* Train cataloging and metadata staff to use tools and standards required for 
projects.
* Actively participate in Central Library Operations, library-wide, 2CUL 
(partnership with Columbia University), and national working groups, task 
forces, and committees.
* Monitor and contribute to the development of local, national, and 
international metadata standards and trends.
* Actively seek to participate in library's role in digital humanities and/or 
research data projects when possible.

Knowledge/Experience Requirements:

Required:
* ALA-accredited MLS or equivalent or advanced degree.
* Subject expertise in a humanities or science field.
* Working knowledge of a variety of metadata standards (e.g. Dublin Core, VRA 
Core, EAD, METS, EML, DDI, FGDC Biological Data Profile) and best practices for 
managing digital collections.
* Interest in metadata issues and emerging technologies.
* Aptitude for learning digital collection management, electronic resource 
management, and metadata standards and formats.
* Demonstrated experience with a range of software applications, including 
those supporting the development of digital libraries.
* Excellent collegial, communication, and analytic skills, including the 
ability to work well within a team environment with diverse groups of library 
staff.
* Evidence of an ability to plan, analyze, and solve problems creatively, 
flexibly, and resourcefully.
* Interest in professional development activities, including research and 
participation in professional organizations.
* Strong service orientation and interest in library users' values and needs.

Preferred:
* Working knowledge of the use of cataloging principles, standards, and tools, 
as well as understanding of controlled vocabularies, thesauri, taxonomies, and 
ontologies.
* Understanding of archival description and/or experience using EAD.
* Knowledge of data sets in all formats.
* Experience with XML edit

Re: [CODE4LIB] simple,flexible ILS for a small library.

[Jon Gorman]

> Perhaps from a usual library perspective, ILL is fancy, but programatically,
> it isn't any more complicated than a borrower.  Except a lender checks a
> book in first and simultaneously creates a record for it.

Most ILL software also offer different options for delivery, automates
much of the communications for requests and the like between
institutions, using systems similar for p2p for electronic document
delivery, ways to set up different shipping and payment methods, allow
individuals to track shipping, copyright control and licensing (does
institution x in Mexico have the right to loan us x), etc.  Most ILL
systems are geared towards sharing with non-partner institutions.
Usually true partner institutions share the same ILS or use some sort
of similar universal borrowing setup.

I'd imagine that's what most people started thinking when you said ILL
was a requirement but it sounds like you might also just be asking
more about universal borrowing configuration.  Typical lingo for what
it sounds like you want is good support for "on the fly" records for
patron and books.  In other words, it's really quick and easy to
create records, even at the point where you're about to circulate.
Universal borrowing setups tend to do this by either grabbing patron
info or having dummy patrons that correspond to the institution.

Illiad is probably our most heavily used ILL system, but we run more
than one for the electronic sharing aspects.

Most ILS systems don't have the ILL integrated with them, mostly due
to historical reasons.   In fact, ILS are increasingly moving away
from monolithic models into more modular ones.  (After all, typically
the catalog interface is a huge part of the ILS, but it sounds like
you want to use VuFind).


If you know all this I apologize, but I think there's some confusion
with how you're using the terms.  Or how I'm understanding your use.

Jon Gorman

Re: [CODE4LIB] simple,flexible ILS for a small library.

[McDonald, Stephen]

> I was only thinking that if any ILS had the ability to handle book
> lending,
> it would be through creative use of ILL, as no other common function
> has
> anything to do with a library borrowing a book.  So, while looking
> through
> available ILSs, ILL was the functionality I was most curious about.
> And I
> agree that even creative use of ILL is probably not good enough.

ILL is a _lot_ more complicated than simple borrowing.  Almost all ILS systems 
have a mechanism to handle simple borrowing.  Only a few are designed to handle 
ILL.

> Out of curiosity, where does the difficulty of implementing borrowing
> come
> in?

It _isn't_ that difficult.  As I said above, it is ILL that is difficult.  If 
what you really want is support for borrowing, then you don't need to require 
ILL support.  Say what you _really_ want, not what you assume you need in order 
to get that.

Steve McDonald
steve.mcdon...@tufts.edu

Re: [CODE4LIB] simple,flexible ILS for a small library.

[...]

> I keep going back to this point. What type of "partner libraries" are
> these? Are they part of a given institution, or consortium? Honestly,
> I don't think ILL is the right solution, and as others have said on
> this thread, implementing ILL (or even borrowing) is certainly
> non-trivial.
>
>
The "partner libraries" are patrons on the same level as borrowers (probably
often the same people).

I was only thinking that if any ILS had the ability to handle book lending,
it would be through creative use of ILL, as no other common function has
anything to do with a library borrowing a book.  So, while looking through
available ILSs, ILL was the functionality I was most curious about.  And I
agree that even creative use of ILL is probably not good enough.

Out of curiosity, where does the difficulty of implementing borrowing come
in?  Creating databases of books linked to MARC records and borrowers with
contact info is not difficult.  using a script to mark books as checked out
by a borrower in that database is not difficult.  End of Day processing and
sending emails requires some thought.  A user interface could be difficult,
but once all the scripts are done, if I eventually need a UI it could be
done.  I never considered the task trivial, and there will certainly be
dozens of scripts over multiple files, but it seems to me just a matter of
time and not brain crushing data processing.

I do think that learning the code behind evergreen or another ILS and trying
to tweak it to do something it was not intended to do would be more
difficult and time consuming.

Re: [CODE4LIB] simple,flexible ILS for a small library.

[Mark A. Matienzo]

On Mon, Sep 27, 2010 at 6:15 PM, ...  wrote:

> book sharing will probably happen through creative use of inter-library loan
> functionality, and so an ILS that has a solid and flexible ILL is necessary.
>
> We will probably have less than 1,000 books (perhaps a couple thousand if
> things really take off) and less than 100 borrowers.  Probably about as many
> book sharers (ie, partner libraries) as borrowers.

I keep going back to this point. What type of "partner libraries" are
these? Are they part of a given institution, or consortium? Honestly,
I don't think ILL is the right solution, and as others have said on
this thread, implementing ILL (or even borrowing) is certainly
non-trivial.

One possibility would be to have a centralized ILS for all the partner
libraries, and to manage each as a location within the ILS. This is
the model that many public library networks use, for what it's worth.

Mark A. Matienzo
Digital Archivist, Manuscripts and Archives
Yale University Library

[CODE4LIB] bibliographic datasets: title, authors, venue, year

[Jodi Schneider]

If you're looking for some bulk title/author/venue/year data, there are a 
couple of datasets gathered from DBLP, ACM, and Google Scholar that might be of 
interest:
http://dbs.uni-leipzig.de/en/research/projects/object_matching/fever/benchmark_datasets_for_entity_resolution

For more details, see the papers also linked from that site, which include work 
on data cleaning (i.e. are two objects the same).

-Jodi

[CODE4LIB] Developer position at the Library Innovation Lab at Harvard Law Library

[Kim Dulin]

We're writing from the Library Innovation Laboratory at Harvard Law
School.  We're new.  We have an available job, and we're all about
innovating for libraries.  We've got a great team that works really well
together and we're looking to bring somebody else on.  To see some of
what we're working on, check out the website: librarylab.law.harvard.edu

 

Here is a link to our job description:
https://jobs.brassring.com/1033/asp/tg/cim_jobdetail.asp?partnerID=25240
&siteID=5341&AReq=22156BR

 

Feel free to pass along and thanks, 

 

The team at the Harvard Library Innovation Lab  

&

Kim Dulin

 

 

Kim Dulin

Associate Director for Collection Development and Digital Initiatives

Harvard Law Library

526 Areeda Hall

1545 Massachusetts Ave.

Cambridge, MA 02138

(617) 496-3292

fax (617) 495-4449

 

[CODE4LIB] CORRECTION: Room Rate ENDS TODAY! - Ex Libris Northeast User Group (formerly EMA) Meeting

[Schwartz, Raymond]

Room Rate ENDS TODAY!

 

Ex Libris Northeast User Group (ENUG, formerly EMA) Meeting

October 21 & 22, 2010  


 

The Ex Libris Northeast User Group (ENUG, formerly EMA) promotes the
exchange of ideas and innovation between users of all Ex Libris products
(Aleph, Voyager, SFX, MetaLib, DigiTool, Verde, and Primo) in
Connecticut, Delaware, Maine, Massachusetts, New Hampshire, New Jersey,
New York, Pennsylvania, Rhode Island, and Vermont.  In addition, we
invite users from any other state or country.


The annual Ex Libris Northeast Users Group (ENUG) Meeting will be held
at William Paterson University's Cheng Library in Wayne, New Jersey on
October 21st from 8am to 22nd till 2pm, 2010. 

 

Information is available on the official conference website at:
http://www.emausers.org  

The conference registration fee is $50.00 and covers continental
breakfasts on Thursday and Friday, and lunch on Thursday, along with
snacks during meeting breaks. 

Presenters are exempt from this fee. 

After October 15th the registration fee is $55.00. 

Online registration is open until 12:00 midnight Tuesday, October 19th,
after which NO on-site registrations will be accepted.  Please send a
payment in as early as you can or plan to pay at the conference.

 

Make your hotel reservation by 10/1/2010 to make sure you get a room.
After that date the room block will be released and your reservation is
subject to rate and availability.

We have arranged for a block of rooms at a conference rate of
$65.00/night. Please ask for LA QUINTA INN & SUITES WAYNE (1850 State
Rt. 23 North, Wayne NJ 07470
Phone: (973) 696-8050) and GROUP #566. Please also state the room type
(2 full-size beds or 1 king), arrival and departure dates as well as
smoking preference. For further information click here
http://www.emausers.org/information.html

 

Directions for Driving are available at
http://www.wpunj.edu/directories/directions-and-map.dot

 

Public Transportation is available via NJ Transit - www.njtransit.com.
There is a NJ Transit bus from Manhattan's Port Authority Bus Terminal
direct to the Campus (1 hour trip).  Its schedule is available at
http://www.njtransit.com/pdf/bus/T1196.pdf

 

If you are driving to Wayne, NJ and are willing to take passengers,
please provide some details for carpooling on the registration form.

   
The program includes:

 

Ex Libris & ELUNA Presentations

* ELUNA/IGeLU Updates

* Ex Libris Update and Overview of product plans

Roundtable Discussions

* Best practices with EDI (Aleph) - KJ Collins, Stony Brook
University 

* Customization of Tomcat WebVoyage (Voyager)- Yongming Wang,
The College of New Jersey 

* Authority control (General)- Jennifer Palmisano, Center for
Jewish History 

* Cataloging (General)- Deb Pluss, William Paterson University 

Keynote

* URM and Princeton: A Partner's Perspective - Trevor Dawes,
Janet Lute, Princeton University

Breakout Sessions 1

* Acquisitions Automation: import without data going bump in the
night(Aleph) - Kevin J Collins, Stony Brook University 

* Voyager Extracts and Batch Editing for Catalogers (Voyager)-
Mark Sandford, William Paterson University

* Data Warehousing and Mining Data from Library and University
Systems for Assessment of Library Operations (General) - Ray Schwartz,
William Paterson University 

Breakout Sessions 2

* E-Books Management: Focus Group Update and Discussion
(General)- Karin Wikoff, Ithaca College 

* Techniques for Voyager Disaster Recovery and Business
Continuity (Voyager)- Christopher Manly, Cornell University 

* Aleph Product Working Group Update (Aleph) - Christine Moulen,
MIT 

* Integrating Umlaut and Xerxes with Primo via PDS (Primo)- Scot
Dalton, NYU 

Breakout Sessions 3

* Managing a Bibliographic Reconciliation between our Voyager
ILS and OCLC's Worldcat (Voyager)- Melissa A. Wisner, Yale University 

* Mobile Library Websites (General)- Yongming Wang, The College
of New Jersey 

*Aleph data back and forth with other campus systems (Aleph) -
Christine Moulen, MIT 

Breakout Sessions 4

* Web OPAC 2.0: Discovering a Better Search Tool (General)-
Kevin J Collins, Darren Chase, Stony Brook University 

* Voyager Server Security and Monitoring (Voyager)- James
DeRose, William Paterson University 

* Metadata Cross-walking/Transforming and Federated Searching in
Ex Libris Products (General) - Anthony Dellureficio, New School
University 

Lightning Talks

Your attendance and participation is very much appreciated!

 

ENUG Planning Committee

 

[CODE4LIB] Conference and Room Rate ENDS TODAY! - Ex Libris Northeast User Group (formerly EMA) Meeting

[Schwartz, Raymond]

Conference and Room Rate ENDS TODAY!

 

Ex Libris Northeast User Group (ENUG, formerly EMA) Meeting

October 21 & 22, 2010  


 

The Ex Libris Northeast User Group (ENUG, formerly EMA) promotes the
exchange of ideas and innovation between users of all Ex Libris products
(Aleph, Voyager, SFX, MetaLib, DigiTool, Verde, and Primo) in
Connecticut, Delaware, Maine, Massachusetts, New Hampshire, New Jersey,
New York, Pennsylvania, Rhode Island, and Vermont.  In addition, we
invite users from any other state or country.


The annual Ex Libris Northeast Users Group (ENUG) Meeting will be held
at William Paterson University's Cheng Library in Wayne, New Jersey on
October 21st from 8am to 22nd till 2pm, 2010. 

 

Information is available on the official conference website at:
http://www.emausers.org  

The conference registration fee is $50.00 and covers continental
breakfasts on Thursday and Friday, and lunch on Thursday, along with
snacks during meeting breaks. 

Presenters are exempt from this fee. 

After October 15th the registration fee is $55.00. 

Online registration is open until 12:00 midnight Tuesday, October 19th,
after which only on-site registrations will be accepted.  Please send a
payment in as early as you can or plan to pay at the conference.

 

Make your hotel reservation by 10/1/2010 to make sure you get a room.
After that date the room block will be released and your reservation is
subject to rate and availability.

We have arranged for a block of rooms at a conference rate of
$65.00/night. Please ask for LA QUINTA INN & SUITES WAYNE (1850 State
Rt. 23 North, Wayne NJ 07470
Phone: (973) 696-8050) and GROUP #566. Please also state the room type
(2 full-size beds or 1 king), arrival and departure dates as well as
smoking preference. For further information click here
http://www.emausers.org/information.html

 

Directions for Driving are available at
http://www.wpunj.edu/directories/directions-and-map.dot

 

Public Transportation is available via NJ Transit - www.njtransit.com.
There is a NJ Transit bus from Manhattan's Port Authority Bus Terminal
direct to the Campus (1 hour trip).  Its schedule is available at
http://www.njtransit.com/pdf/bus/T1196.pdf

 

If you are driving to Wayne, NJ and are willing to take passengers,
please provide some details for carpooling on the registration form.

   
The program includes:

 

Ex Libris & ELUNA Presentations

* ELUNA/IGeLU Updates

* Ex Libris Update and Overview of product plans

Roundtable Discussions

* Best practices with EDI (Aleph) - KJ Collins, Stony Brook
University 

* Customization of Tomcat WebVoyage (Voyager)- Yongming Wang,
The College of New Jersey 

* Authority control (General)- Jennifer Palmisano, Center for
Jewish History 

* Cataloging (General)- Deb Pluss, William Paterson University 

Keynote

* URM and Princeton: A Partner's Perspective - Trevor Dawes,
Janet Lute, Princeton University

Breakout Sessions 1

* Acquisitions Automation: import without data going bump in the
night(Aleph) - Kevin J Collins, Stony Brook University 

* Voyager Extracts and Batch Editing for Catalogers (Voyager)-
Mark Sandford, William Paterson University

* Data Warehousing and Mining Data from Library and University
Systems for Assessment of Library Operations (General) - Ray Schwartz,
William Paterson University 

Breakout Sessions 2

* E-Books Management: Focus Group Update and Discussion
(General)- Karin Wikoff, Ithaca College 

* Techniques for Voyager Disaster Recovery and Business
Continuity (Voyager)- Christopher Manly, Cornell University 

* Aleph Product Working Group Update (Aleph) - Christine Moulen,
MIT 

* Integrating Umlaut and Xerxes with Primo via PDS (Primo)- Scot
Dalton, NYU 

Breakout Sessions 3

* Managing a Bibliographic Reconciliation between our Voyager
ILS and OCLC's Worldcat (Voyager)- Melissa A. Wisner, Yale University 

* Mobile Library Websites (General)- Yongming Wang, The College
of New Jersey 

*Aleph data back and forth with other campus systems (Aleph) -
Christine Moulen, MIT 

Breakout Sessions 4

* Web OPAC 2.0: Discovering a Better Search Tool (General)-
Kevin J Collins, Darren Chase, Stony Brook University 

* Voyager Server Security and Monitoring (Voyager)- James
DeRose, William Paterson University 

* Metadata Cross-walking/Transforming and Federated Searching in
Ex Libris Products (General) - Anthony Dellureficio, New School
University 

Lightning Talks

Your attendance and participation is very much appreciated!

 

ENUG Planning Committee