[CODE4LIB] Universal Design for Libraries and Librarians - an important LITA web course

[Ken Varnum]

Consider this important new LITA web course:
Universal Design for Libraries and Librarians


Instructors: Jessica Olin, Director of the Library, Robert H. Parker
Library, Wesley College; and Holly Mabry, Digital Services Librarian,
Gardner-Webb University

Offered: April 11 – May 27, 2016
A Moodle based web course with asynchronous weekly content
lessons, tutorials, assignments, and groups discussion.

Register Online, page arranged by session date (login required)


Universal Design is the idea of designing products, places, and experiences
to make them accessible to as broad a spectrum of people as possible,
without requiring special modifications or adaptations. This course will
present an overview of universal design as a historical movement, as a
philosophy, and as an applicable set of tools. Students will learn about
the diversity of experiences and capabilities that people have, including
disabilities (e.g. physical, learning, cognitive, resulting from age and/or
accident), cultural backgrounds, and other abilities. The class will also
give students the opportunity to redesign specific products or environments
to make them more universally accessible and usable.

Takeaways

By the end of this class, students will be able to…


   - Articulate the ethical, philosophical, and practical aspects of
   Universal Design as a method and movement – both in general and as it
   relates to their specific work and life circumstances
   - Demonstrate the specific pedagogical, ethical, and customer service
   benefits of using Universal Design principles to develop and recreate
   library spaces and services in order to make them more broadly accessible
   - Integrate the ideals and practicalities of Universal Design into
   library spaces and services via a continuous critique and evaluation cycle


Here’s the Course Page

Jessica Olin is the Director of the Library, Robert H. Parker
Library, Wesley College. Ms. Olin received her MLIS from Simmons College in
2003 and an MAEd, with a concentration in Adult Education, from Touro
University International. Her first position in higher education was at
Landmark College, a college that is specifically geared to meeting the
unique needs of people with learning differences. While at Landmark, Ms.
Olin learned about the ethical, theoretical, and practical aspects of
universal design. She has since taught an undergraduate course for both the
education and the entrepreneurship departments at Hiram College on the
subject.

Holly Mabry received her MLIS from UNC-Greensboro in 2009. She is currently
the Digital Services Librarian at Gardner-Webb University where she manages
the university’s institutional repository, and teaches the
library’s for-credit online research skills course. She also works for an
international virtual reference service called Chatstaff. Since finishing
her MLIS, she has done several presentations at local and national
library conferences on implementing universal design in libraries with a
focus on accessibility for patrons with disabilities.

Dates:

February 29 – March 31, 2016

Costs:

• LITA Member: $135
• ALA Member: $195
• Non-member: $260

Technical Requirements:

Moodle login info will be sent to registrants the week prior to the start
date. The Moodle-developed course site will include weekly new content
lessons and is composed of self-paced modules with facilitated interaction
led by the instructor. Students regularly use the forum and chat room
functions to facilitate their class participation. The course web site will
be open for 1 week prior to the start date for students to have access to
Moodle instructions and set their browser correctly. The course site will
remain open for 90 days after the end date for students to refer back to
course material.

Registration Information:

Register Online, page arranged by session date (login required)

OR
Mail or fax form to ALA Registration

OR
call 1-800-545-2433 and press 5
OR
email registrat...@ala.org

Questions or Comments?

For all other questions or comments related to the course, contact
LITA at (312)
280-4268 or Mark Beatty, mbea...@ala.org


Ken Varnum for the LITA Education Committee

--
Ken Varnum
Senior Program Manager for Discovery, Delivery, and Learning Analytics
Library Information Technology | University of Michigan Library
var...@umich.edu | @varnum | 734-615-3287
http://www.lib.umich.edu/users/varnum

Re: [CODE4LIB] code4lib mailing list [domain]

[Ranti Junus]

I, too, have no preference in branding. Regarding DLF's offer to host the
list, I think that's a good idea too (thank you, Bethany!)


thanks,
ranti.

On Mon, Mar 28, 2016 at 12:02 PM, William Denton  wrote:

> On 27 March 2016, Eric Lease Morgan wrote:
>
> Everybody, please share with the rest of us your opinion about our mailing
>> list’s domain. This need to move from the University of Notre Dame is a
>> possible opportunity to have our list come from the cod4lib.org domain.
>> For example, the address of the list might become
>> code4...@lists.code4lib.org. If it moved to Google, then the address
>> might be code4...@googlegroups.com. Is the list’s address important for
>> us to brand?
>>
>
> -1 for Google as with the others, +1 for the DLF since that seems smooth
> and stable, +0 for branding.
>
> And many thanks to Eric for all his work over the years---and to the small
> group of folks who got this all started a decade or more ago.
>
> Bill
> --
> William Denton ↔  Toronto, Canada ↔  https://www.miskatonic.org/




-- 
Bulk mail.  Postage paid.

Re: [CODE4LIB] Validating MARC records

[Paul Hoffman]

On Mon, Mar 28, 2016 at 02:01:42PM +, Jiao, Dazhi wrote:
> At IU we are running our OPAC using Blacklight. From time to time 
> there are some catalog errors that would cause errors in our custom 
> code to extract fields from the MARC records. For example, sometimes a 
> subfield may unexpectedly appear in a field, or an expected subfield 
> is accidentally named to another subfield.
> 
> While we can catch these errors in our code, we’d also like to be able 
> to discover them and notify the catalogers before the records are 
> exposed in the discover layer. I wonder if anyone here has experiences 
> with some MARC validation tool for this purpose?

Are you talking about low-level structural problems, like the record 
length field (Ldr/00-05) not matching the actual record length?  Or 
high-level errors, like a 245 field without a subfield $a or an invalid 
country code?

If it's the latter, Bryan Baldus wrote a Perl module (MARC::Lint) that 
looks pretty comprehensive:

https://metacpan.org/release/MARC-Lint

It includes a script (marclint) that you can use directly from the 
command line.

If it's the former, I've attached a Perl script I wrote (marcdiag) that 
catches most low-level errors.  It only has one dependency -- 
Getopt::Long, which is pretty standard but not part of a core Perl 
installation.

Paul.

-- 
Paul Hoffman 
Systems Librarian
Fenway Libraries Online
c/o Wentworth Institute of Technology
550 Huntington Ave.
Boston, MA 02115
(617) 442-2384 (FLO main number)
#!/m1/shared/bin/perl

use strict;
use warnings;
use bytes;

use Getopt::Long
qw(:config posix_default gnu_compat require_order bundling no_ignore_case);

use constant RECORD_TERMINATOR  => "\x1d";
use constant FIELD_TERMINATOR   => "\x1e";
use constant SUBFIELD_DELIMITER => "\x1f";

sub emit;
sub summarize;
sub record;
sub fatal;
sub info;
sub error;
sub warning;
sub ok;
sub fail;

my $rx_record_terminator  = qr/\x1d/;
my $rx_field_terminator   = qr/\x1e/;
my $rx_subfield_delimiter = qr/\x1f/;
my $rx_struc_char = qr/[\x1d-\x1f]/;
my $rx_nonstruc_char = qr/[^\x1d-\x1f]/;

my %ecode2format = (
L05 => "Unrecognized record status: %s",
L06 => "Unrecognized record type: %s",
L07 => "Unrecognized bib level: %s",
L08 => "Unrecognized control type: %s",
L09 => "Unrecognized character encoding: %s",
L10 => "Invalid indicator count: %s",
L11 => "Invalid subfield code count: %s",
L17 => "Unrecognized encoding level: %s",
L18 => "Unrecognized cataloging form: %s",
M18 => "Unrecognized item info: %s",
L19 => "Unrecognized multipart resource record level: %s",
L20 => "Invalid length-of-field length: %s",
L21 => "Invalid length-of-offset length: %s",
L22 => "Invalid length-of-impldef length: %s",
L23 => "Invalid undefined value in leader: %s",
DLN => "Directory length: not a multiple of 12 bytes",
DNT => "Directory not terminated",
EFT => "Embedded field terminator in field %s",
ERT => "Embedded record terminator in field %s",
ETG => "Invalid field tag %s",
ESD => "Subfield delimiter in control field %s",
IIN => "Invalid indicator in field %s",
ISI => "Invalid subfield identifier %s in field %s",
IUT => "Invalid UTF-8 in field %s",
JAB => "Junk at beginning of field %s",
JAE => "Junk at end of field %s",
MSI => "Missing subfield identifier in field %s",
NSF => "Empty subfield %s in field %s",
NWF => "Not a USMARC record: pathological leader",
RLN => "Record length doesn't match the length encoded in the leader",
TRU => "Truncated field %s",
UFD => "Unterminated field %s",
);

my %rstat2label = (
'a' => 'increase in encoding level',
'c' => 'corrected or revised',
'd' => 'deleted',
'n' => 'new',
'p' => 'increase in encoding level from prepublication',
);

my ($show_error_details, $verbose, $parseable, $terse, $quiet, $check_utf8, 
$strict);
my $summarize = 1;
my %ignore;
my (%err, %errmsg, %enc, %bad);
my %rstat = ('c' => 0, 'd' => 0, 'n' => 0);
my $max_errs_in_record = 1;
my $max_errs_total = 1<<31;

GetOptions(
'h'   => \,
'l'   => \_codes,
'r=i' => \$max_errs_in_record,
't=i' => \$max_errs_total,
'a'   => sub { $max_errs_total = $max_errs_in_record = 1 << 31 },
'1'   => sub { $max_errs_total = $max_errs_in_record = 1 },
'u'   => \$check_utf8,
's'   => \$strict,
'e'   => \$show_error_details,
'x=s' => sub { $ignore{$_} = 1 for split /,/, $_[1] },
'v'   => \$verbose,
'E'   => \$terse,
'n'   => sub { $summarize = 0 },
'p'   => \$parseable,
'q'   => \$quiet,
) or usage();

my ($file, $fh);
if (@ARGV == 1) {
$file = shift @ARGV;
open $fh, '<', $file
or fatal "Can't open input file $file: $!";
}
elsif (@ARGV == 0) {
$file = '';
$fh = \*STDIN;
}
else {
usage();
}
binmode $fh;
binmode STDOUT;

my ($n, $rtype_bib, $rtype_mfhd, $rtype_auth, $rtype_other) = (0, 0, 0, 0, 0);
my $skipped = 0;
my 

Re: [CODE4LIB] code4lib mailing list [domain]

[William Denton]

On 27 March 2016, Eric Lease Morgan wrote:

Everybody, please share with the rest of us your opinion about our mailing 
list’s domain. This need to move from the University of Notre Dame is a 
possible opportunity to have our list come from the cod4lib.org domain. For 
example, the address of the list might become code4...@lists.code4lib.org. If 
it moved to Google, then the address might be code4...@googlegroups.com. Is 
the list’s address important for us to brand?


-1 for Google as with the others, +1 for the DLF since that seems smooth and 
stable, +0 for branding.


And many thanks to Eric for all his work over the years---and to the small group 
of folks who got this all started a decade or more ago.


Bill
--
William Denton ↔  Toronto, Canada ↔  https://www.miskatonic.org/

[CODE4LIB] ALA Annual 2016: Digital Conversion IG Call for Proposals

[Titkemeyer, Erica Lynn]

ALA Annual 2016: Digital Conversion Interest Group Seeks Presenters

The ALCTS PARS Digital Conversion Interest Group is now accepting proposals for 
speakers to present at the ALA Annual Conference (Orlando, FL) on Saturday June 
25th, 2016 from 1:00-2:30 PM.

The Digital Conversion Interest Group provides a venue to discuss the 
preservation of audio, photographic, and moving image materials in both analog 
and digital formats and the digitization or reformatting of audio, 
photographic, print, and moving image materials for preservation and access.

The interest group Co-Chairs are seeking 15-20 minute presentations surrounding 
current trends and projects as they relate to digitization or digital migration 
of library collections, with possible topics including:


· Methods for prioritizing analog materials for digitization

· Tools for digitization, metadata management, file transfers, and 
file management

· Planning for digital preservation storage

· Cross-departmental collaboration (Preservation, Conservation, IT, 
Reference & Information)

· Risk monitoring and migration of born-digital formats



Please email your proposals to the co-chairs (Erica 
Titkemeyer
 and Ivey 
Glendon)
 by Friday April 15th, 2016.

Erica Titkemeyer and Ivey Glendon, DCIG Co-Chairs

Erica Titkemeyer
AV Conservator / Project Director
Southern Folklife Collection
University of North Carolina at Chapel Hill
Chapel Hill, NC 27515-8890
(919)962-4339
etit...@email.unc.edu

[CODE4LIB] Call for Nominations: DLF Community/Capacity Award!

[Wayne Graham]

Dear Colleagues,

Nominations are now open for the first annual Digital Library Federation 
Community/Capacity Award!

https://www.diglib.org/opportunities/community-capacity-award/

The DLF Comm/Cap Award is a new expression of gratitude from the full Digital 
Library Federation membership, to be selected each year by vote.

First announced at the "Community and Capacity" panel of the 2015 DLF Forum, 
Comm/Caps are not prizes for pure innovation, individualism, or disruption. 
Instead, this award honors constructive capacity-building in digital libraries 
and allied fields: efforts that contribute to our ability to collaborate across 
institutional lines and/or work toward something larger, together. DLF 
Comm/Caps are about community spirit, generosity, openness, and care for fellow 
digital library, archives, and museum practitioners and for the various publics 
and missions we serve.

The 2016 DLF Comm/Cap Award will go to an inspiring project, team, or person 
selected by the Digital Library Federation membership at large (one org, one 
vote: DLF member institutions will decide locally how to make their pick!). 
Nominated work may be primarily technical, social, or a blend of the two, and 
there is no requirement that nominees be affiliated with a DLF member 
institution.

This year's winner (person or group) will receive a $1000 prize, one free Forum 
registration, and assistance with travel expenses to make it possible for a 
representative to accept the award in person at the 2016 DLF Forum in 
Milwaukee, WI, 7-9 November 2016: https://www.diglib.org/forums/2016forum/

Send your nominations now through May 1st: http://goo.gl/forms/SEPqkxGgl0

— and help DLF celebrate the community spirit that makes our field more than 
the sum of its parts.

—
Wayne Graham
Technical Director
Council on Library and Information Resources (CLIR)
https://github.com/waynegraham | http://twitter.com/wayne_graham

[CODE4LIB] Validating MARC records

[Jiao, Dazhi]

Hi,

At IU we are running our OPAC using Blacklight. From time to time there are 
some catalog errors that would cause errors in our custom code to extract 
fields from the MARC records. For example, sometimes a subfield may 
unexpectedly appear in a field, or an expected subfield is accidentally named 
to another subfield.

While we can catch these errors in our code, we’d also like to be able to 
discover them and notify the catalogers before the records are exposed in the 
discover layer. I wonder if anyone here has experiences with some MARC 
validation tool for this purpose?

Best,

David

--
David Jiao
Principal Software Engineer
Indiana University Enterprise Library Systems
812.855.7189; dj...@iu.edu

[CODE4LIB] Job: Head of Digital Scholarship and Technology Services at Vassar College Libraries at Vassar College

[jobs]

Head of Digital Scholarship and Technology Services at Vassar College Libraries
Vassar College
Poughkeepsie

Vassar College Libraries seeks collaborative and
entrepreneurial candidates for the position of Head of Digital Scholarship and
Technology Services. The incumbent will work closely with colleagues to
advance the Libraries' efforts to work with faculty and students pursuing
digitally-enhanced modes of learning and research. Along with partners in the
Libraries as well as Computing and Information Services, the Head of Digital
Scholarship and Technology Services will identify and develop digital
projects, technological resources, physical and virtual spaces, and training
opportunities that address emerging needs across disciplines. The successful
candidate will help to sustain and enhance the Libraries' longstanding
strengths in digital collections, metadata expertise, and long-term
stewardship, merging them with faculty work in the digital humanities and
digitally-enhanced learning, and offering services to address changing
practices in scholarly communications.

  
The Head of Digital Scholarship and Technology Services will consult with
faculty, students, and colleagues using emerging tools and methods (e.g. text
mining, data visualization, mapping), and work alongside colleagues to develop
training and programming that builds the college's capacity to support work in
these areas. The incumbent will actively maintain awareness of issues in
digital scholarship, and facilitate workshops and presentations to develop
broader awareness and to foster a community of practitioners on campus.

  
The Head of Digital Scholarship and Technology Services also oversees the
Libraries' digital technologies department, which includes three professionals
with library-wide responsibilities for digital collections, digital repository
services, and library systems. In this role, the incumbent will work with
colleagues to ensure that the libraries' uses of technologies are aligned with
and responsive to pedagogical and scholarly work at the college, and that the
libraries' technical and user services are well-supported to serve the
academic mission.

  * Advanced degree in a relevant discipline, or, MLS/MLIS
  * Significant and progressively responsible experience engaging with and 
managing digital scholarly activities at an academic institution.
  * Demonstrated proficiency with one or more methodologies common to digital 
humanities research (e.g. text mining, data visualization, mapping)
  * Demonstrated ability to manage complex projects with a diverse team of 
stakeholders.
  * Working knowledge of one or more programming or scripting languages 
commonly used in DH projects (e.g. Python, Javascript, Processing)
  * Familiarity with common digital humanities software (e.g. Omeka, Neatline, 
D3.js)
  * Familiarity with common library metadata formats
  * Commitment to collaboration and the ability to work cooperatively across 
organizational and disciplinary boundaries.
  * Competence and sensitivity in working at a college in which students are 
broadly diverse with regard to many facets of identity, including but not 
limited to gender, ethnicity, nationality, sexual orientation, and religion.



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/25166/
To post a new job please visit http://jobs.code4lib.org/

Re: [CODE4LIB] code4lib mailing list [domain]

[Childs, Riley]

+1
On Mar 27, 2016 23:51, "Stuart A. Yeates"  wrote:

> On Monday, 28 March 2016, Mark Sandford  wrote:
>
> > >
> > >
> > >
> > > Everybody, please share with the rest of us your opinion about our
> > mailing
> > > list’s domain. This need to move from the University of Notre Dame is a
> > > possible opportunity to have our list come from the cod4lib.org
> domain.
> > > For example, the address of the list might become
> > > code4...@lists.code4lib.org . If it moved to Google,
> then
> > the address
> > > might be code4...@googlegroups.com . Is the list’s
> > address important for
> > > us to brand?
> > >
> > > —
> > > ELM
> > >
> >
> > ​I've never given much thought to the domain that a list comes from,
> > personally.
> >
>
> To my mind brand is a much lower priority than reliability and things 'just
> working'.
>
> Cheers
> Stuart
>
>
>
>
> --
> --
> ...let us be heard from red core to black sky
>

[CODE4LIB] Job: Digital Library Software Developer at University of California, Los Angeles

[jobs]

Digital Library Software Developer
University of California, Los Angeles
Los Angeles

dr version at bottom.

  
Under the direction of the Digital Library Architect, the Digital Library
Software Developer (DLSD) provides systems analysis and programming to develop
custom software programs with source data from a locally-developed legacy
Digital Assets Management System (DAMS) and Fedora Commons open source DAMS.
The DLSD is responsible for web application development and back end
repository and database development.

Working hours may include emergency support on weekends, evenings and
holidays.

  
Digital Initiatives and Information Technology (DIIT) supports library staff
and users by providing access to library technologies via the campus network
infrastructure backbone. Supported technology resources include the integrated
library system and online catalog; network connectivity including servers,
storage, operating system and application server delivery; and programming and
application development in support of digital and web based initiatives.
Through collaborative efforts with all areas of UCLA's libraries, DIIT assists
in the development and delivery of technologies for all types of electronic
resources. DIIT is comprised of three teams: Operations and Services
(including Data Center and Network Team, Helpdesk Team and Learning & Research
Technology Services), Development, and Digital Library Program. DIIT's 40
staff members also work as collaborative partners with units in other areas of
the library, and provide technology support for the major business systems
used by the libraries.

  
Desired Qualifications:

  
1. Bachelor's degree in computer programming, information science and 3 years'
experience or equivalent education and experience.

Required



2. Demonstrated ability to communicate orally with users, peers and management
about project management and technology.

Required



3. Demonstrated ability to write clear technical documentation.

Required



4. Demonstrated ability to analyze, design, develop and test computer programs
and scripts in a language such as java, php, python.

Required



5. Working knowledge of XML syntax, namespaces, and schemas.

Required



6. Working knowledge or Solr, ElasticSearch or other search framework.

Required



7. Experience with Fedora, DSpace or other repository software.

Required



8. Working knowledge of SQL and relational database technology.

Required



9. Experience working independently and efficiently with minimal supervision.

Required



10. Detail oriented with strong organizational skills and ability to manage
multiple projects.

Required



11. Working knowledge of linux/unix shell command line.

Required



12. Working knowledge of distributed code repositories such as git.

Required



13. Ability to get to work reliably and on time and to be present in the
workplace during normal working hours.

Required



14. Ability to follow directions from supervisors and to provide clear
directions to staff and student employees.

Required



15. Ability to initiate and maintain cooperative working relationships with
coworkers, supervisors, and managers. Ability to work harmoniously and as a
team player, thrive in a team-based environment, and skill in fostering
teamwork among others.

Required



16. Working knowledge of Drupal content types, blocks, panels, and other
components of web site building in a Drupal environment.

Preferred



17. Demonstrated ability to design and develop RESTful web services.

Preferred

  
  
TL;DR; -

  
We're looking to shore up our data delivery services at the UCLA Digital
Library. This software developer position would be an integral part of laying
the groudwork to create a unified API from a variety of different data sources
(Solr, Fedora repository, custom DBs) to be used both internally by developers
and published externally for public use.

  
  



Brought to you by code4lib jobs: http://jobs.code4lib.org/job/25154/
To post a new job please visit http://jobs.code4lib.org/