[CODE4LIB] 2015 Code4Lib Keynote Nominations closing in one week!

[Eric Phetteplace]

Hi Code4Lib,

The Keynote Speakers Committee will close the nominations process and
prepare for voting in one week. Get your nominations in now!
http://wiki.code4lib.org/2015_Invited_Speakers_Nominations

We only have 7 nominations at the moment; there were 23 (!) last year. We
can do better! Please add in your dream technology speakers.

Best,
Your Code4Lib 2015 Keynote Speakers Committee
Eric Phetteplace & Heidi Dowding

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Jonathan Rochkind]

Mouse hover is not available to anyone using a touch device rather than 
a mouse, as well as being problematic for keyboard access.


While there might be ways to make the on-hover UI style keyboard 
accessible (perhaps in some cases activating on element focus in 
addition toon hover), there aren't really any good ones I can think for 
purely touch devices (which don't really trigger focus state either).


An increasing amount of web use, of course, is mobile touch devices, and 
probably will continue to be and to increase for some time, including on 
library properties.


So I think probably on-hover UI should simply be abandoned at this 
point, even if some people love it, it will be inaccessible to an 
increasing portion of our users with no good accomodations.


Jonathan

On 9/17/14 4:25 PM, Jesse Martinez wrote:

On the same token, we're making it a policy to not use mouse hover over
effects to display database/asset descriptions in LG2 until this can become
keyboard accessible. This is a beloved feature from LG1 so I'm hoping
SpringShare read my pestering emails about this...

Jesse

On Wed, Sep 17, 2014 at 3:38 PM, Brad Coffield 
wrote:


Johnathan,

That point is well taken. Accessibility, to me, shouldn't be a tacked-on
"we'll do the best we can" sort of thing. It's an essential part of being a
library being open to all users. Unfortunately I know our site has a lot of
work to be done regarding accessibility. I'll also pay attention to that
when/if I make mods to the v2 templates.

On Wed, Sep 17, 2014 at 1:49 PM, Jonathan LeBreton 
wrote:


I might mention here that we (Temple University)  found LibGuides 2.0  to
offer some noteworthy improvements in section 508 accessibility
when compared with version 1.0.   Accessibility is a particular point of
concern for the whole institution as we look across the city, state, and
country at other institutions that have been called out and settled with
various disability advocacy groups.
So we moved to v. 2.0 during the summer in order to have those
improvements in place for the fall semester, as well as to get the value
from some other developments in v. 2.0 that benefit all customers.

When I see email on list about making  modifications to templates and
such, it gives me a bit of concern on this score that by doing so,  one
might easily begin to make the CMS framework for content less accessible.
   I thought I should voice that.This is not to say that one shouldn't
customize and explore enhancements etc.,  but one should do so with some
care if you are operating with similar mandates or concerns.Unless I

am

mistaken, several of the examples noted are now throwing 508 errors that
are not in the out-of-the box  LibGuide templates and which are not the
result of an individual content contributor/author inserting "bad stuff"
like images without alt tags.




Jonathan LeBreton
Senior Associate University Librarian
Editor:  Library & Archival Security
Temple University Libraries
Paley M138,  1210 Polett Walk, Philadelphia PA 19122
voice: 215.204.8231
fax: 215.204.5201
mobile: 215.284.5070
email:  lebre...@temple.edu
email:  jonat...@temple.edu

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Cindi Blyberg
Sent: Wednesday, September 17, 2014 12:03 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] LibGuides v2 - Templates and Nav

Hey everyone!

Not to turn C4L into Support4LibGuides, but... :)

The infrastructure for all the APIs is in place; currently, the Guides

API

and the Subjects API are functioning.  Go to Tools > API > Get Guides to
see the general structure of the URL.  Replace "guides" with "subjects"

to

retrieve your subjects.  You will need your LibGuides site ID, which you
can get from the LibApps Dashboard screen.

Word is that it will not take long to add other API calls on the back

end;

if you need these now, please do email supp...@springshare.com and
reference this conversation.

As for v1, we are planning on supporting it for 2 more years--that said,
we would never leave anyone hanging, so if it takes longer than that to

get

everyone moved over, we're ready for that.

Best,
  -Cindi

On Wed, Sep 17, 2014 at 10:46 AM, Nadaleen F Tempelman-Kluit <

n...@nyu.edu



wrote:


Hi all-
While we're on the topic of LibGuides V2, when will the "GET subjects"
API (and other API details) be in place? We're in a holding pattern
until we get those details and we've not been able to get any timeline
as to when those assets will be in place. So we're deciding between
building out LibGuides CMS "Global" landing pages using the V1
platform, or waiting until some future date which, very soon, will
mean abandoning this project till next summer. If we go the former
route, it would also be great to know how long V1 will be supported.
Thanks



On Wed, Sep 17, 2014 at 10:29 AM, Cindi Blyberg 
wrote:


On Tue, Sep 16, 2014 at 7:15 PM, Michael Schofield

wrote:



Q1. How complicated is it to 

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Jonathan Rochkind]

However I'd also point out that if that class, instead of being simply 
'hidden', had been similar to Bootstrap's "sr-only", or even a more 
fully spelled out "screen-reader-only", the later developer would have 
been more likely to wonder "Hmm, maybe that's not simply hidden but 
means something else, maybe I should try to look up or ask someone what 
it means if I'm not sure"


Attempting self-documenting code always matters for successor 
developers, not just in issues of accessibility. And labelling something 
simply 'hidden' that is not fact always hidden is misleading  your 
successors.


I mean, in your example they left a comment with their thought process 
-- the thing was labelled 'hidden' after all.


Jonathan

On 9/17/14 5:03 PM, Will Martin wrote:

To digress a bit from LibGuides ...

The biggest problem with accessibility is not technical: it's cultural.
Producing HTML that meets basic accessibility tests is not all THAT
difficult.  The harder part is setting up a culture where everyone --
everyone! -- who writes content for the web is trained on how to do it
accessibly.  A content editor who is clueless about accessibility can
very easily screw up their pages without even knowing they're doing so.

The same applies to developers.  Once while reviewing a library site's
code, I came across a chunk of HTML that looked like this (roughly):



An earlier developer had put that in to assist screen reader users in
getting back to the top of the page if they wanted.  The "hidden" class
was a correctly written class for hiding content while leaving it
available for screen reader users.  But the next person to fill that job
wasn't trained on WHY and took it out again.

If you really want to commit to accessibility, it needs to be a
criterion in the job description for your developers, and there needs to
be a training process in place for anyone who produces content for your
site.  Probably with refreshers at intervals.

Will

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Will Martin]

To digress a bit from LibGuides ...

The biggest problem with accessibility is not technical: it's cultural.  
Producing HTML that meets basic accessibility tests is not all THAT 
difficult.  The harder part is setting up a culture where everyone -- 
everyone! -- who writes content for the web is trained on how to do it 
accessibly.  A content editor who is clueless about accessibility can 
very easily screw up their pages without even knowing they're doing so.


The same applies to developers.  Once while reviewing a library site's 
code, I came across a chunk of HTML that looked like this (roughly):




An earlier developer had put that in to assist screen reader users in 
getting back to the top of the page if they wanted.  The "hidden" class 
was a correctly written class for hiding content while leaving it 
available for screen reader users.  But the next person to fill that job 
wasn't trained on WHY and took it out again.


If you really want to commit to accessibility, it needs to be a 
criterion in the job description for your developers, and there needs to 
be a training process in place for anyone who produces content for your 
site.  Probably with refreshers at intervals.


Will

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Jesse Martinez]

On the same token, we're making it a policy to not use mouse hover over
effects to display database/asset descriptions in LG2 until this can become
keyboard accessible. This is a beloved feature from LG1 so I'm hoping
SpringShare read my pestering emails about this...

Jesse

On Wed, Sep 17, 2014 at 3:38 PM, Brad Coffield 
wrote:

> Johnathan,
>
> That point is well taken. Accessibility, to me, shouldn't be a tacked-on
> "we'll do the best we can" sort of thing. It's an essential part of being a
> library being open to all users. Unfortunately I know our site has a lot of
> work to be done regarding accessibility. I'll also pay attention to that
> when/if I make mods to the v2 templates.
>
> On Wed, Sep 17, 2014 at 1:49 PM, Jonathan LeBreton 
> wrote:
>
> > I might mention here that we (Temple University)  found LibGuides 2.0  to
> > offer some noteworthy improvements in section 508 accessibility
> > when compared with version 1.0.   Accessibility is a particular point of
> > concern for the whole institution as we look across the city, state, and
> > country at other institutions that have been called out and settled with
> > various disability advocacy groups.
> > So we moved to v. 2.0 during the summer in order to have those
> > improvements in place for the fall semester, as well as to get the value
> > from some other developments in v. 2.0 that benefit all customers.
> >
> > When I see email on list about making  modifications to templates and
> > such, it gives me a bit of concern on this score that by doing so,  one
> > might easily begin to make the CMS framework for content less accessible.
> >   I thought I should voice that.This is not to say that one shouldn't
> > customize and explore enhancements etc.,  but one should do so with some
> > care if you are operating with similar mandates or concerns.Unless I
> am
> > mistaken, several of the examples noted are now throwing 508 errors that
> > are not in the out-of-the box  LibGuide templates and which are not the
> > result of an individual content contributor/author inserting "bad stuff"
> > like images without alt tags.
> >
> >
> >
> >
> > Jonathan LeBreton
> > Senior Associate University Librarian
> > Editor:  Library & Archival Security
> > Temple University Libraries
> > Paley M138,  1210 Polett Walk, Philadelphia PA 19122
> > voice: 215.204.8231
> > fax: 215.204.5201
> > mobile: 215.284.5070
> > email:  lebre...@temple.edu
> > email:  jonat...@temple.edu
> >
> > -Original Message-
> > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> > Cindi Blyberg
> > Sent: Wednesday, September 17, 2014 12:03 PM
> > To: CODE4LIB@LISTSERV.ND.EDU
> > Subject: Re: [CODE4LIB] LibGuides v2 - Templates and Nav
> >
> > Hey everyone!
> >
> > Not to turn C4L into Support4LibGuides, but... :)
> >
> > The infrastructure for all the APIs is in place; currently, the Guides
> API
> > and the Subjects API are functioning.  Go to Tools > API > Get Guides to
> > see the general structure of the URL.  Replace "guides" with "subjects"
> to
> > retrieve your subjects.  You will need your LibGuides site ID, which you
> > can get from the LibApps Dashboard screen.
> >
> > Word is that it will not take long to add other API calls on the back
> end;
> > if you need these now, please do email supp...@springshare.com and
> > reference this conversation.
> >
> > As for v1, we are planning on supporting it for 2 more years--that said,
> > we would never leave anyone hanging, so if it takes longer than that to
> get
> > everyone moved over, we're ready for that.
> >
> > Best,
> >  -Cindi
> >
> > On Wed, Sep 17, 2014 at 10:46 AM, Nadaleen F Tempelman-Kluit <
> n...@nyu.edu
> > >
> > wrote:
> >
> > > Hi all-
> > > While we're on the topic of LibGuides V2, when will the "GET subjects"
> > > API (and other API details) be in place? We're in a holding pattern
> > > until we get those details and we've not been able to get any timeline
> > > as to when those assets will be in place. So we're deciding between
> > > building out LibGuides CMS "Global" landing pages using the V1
> > > platform, or waiting until some future date which, very soon, will
> > > mean abandoning this project till next summer. If we go the former
> > > route, it would also be great to know how long V1 will be supported.
> > > Thanks
> > >
> > >
> > >
> > > On Wed, Sep 17, 2014 at 10:29 AM, Cindi Blyberg 
> > > wrote:
> > >
> > > > On Tue, Sep 16, 2014 at 7:15 PM, Michael Schofield
> > > > 
> > > > wrote:
> > > >
> > > > >
> > > > > Q1. How complicated is it to change all 3 column guides to a
> > > > single-column
> > > > > left/right-nav layout?
> > > > >
> > > > > A little. You can force the entire group [or all groups] to use a
> > > single
> > > > > template, which is a huge time saver, except your guides' middle
> > > > > and
> > > > right
> > > > > columns will be in "hidden" columns rather than forced to collapse
> > > into a
> > > > > single column. This was pretty con

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Brad Coffield]

Johnathan,

That point is well taken. Accessibility, to me, shouldn't be a tacked-on
"we'll do the best we can" sort of thing. It's an essential part of being a
library being open to all users. Unfortunately I know our site has a lot of
work to be done regarding accessibility. I'll also pay attention to that
when/if I make mods to the v2 templates.

On Wed, Sep 17, 2014 at 1:49 PM, Jonathan LeBreton 
wrote:

> I might mention here that we (Temple University)  found LibGuides 2.0  to
> offer some noteworthy improvements in section 508 accessibility
> when compared with version 1.0.   Accessibility is a particular point of
> concern for the whole institution as we look across the city, state, and
> country at other institutions that have been called out and settled with
> various disability advocacy groups.
> So we moved to v. 2.0 during the summer in order to have those
> improvements in place for the fall semester, as well as to get the value
> from some other developments in v. 2.0 that benefit all customers.
>
> When I see email on list about making  modifications to templates and
> such, it gives me a bit of concern on this score that by doing so,  one
> might easily begin to make the CMS framework for content less accessible.
>   I thought I should voice that.This is not to say that one shouldn't
> customize and explore enhancements etc.,  but one should do so with some
> care if you are operating with similar mandates or concerns.Unless I am
> mistaken, several of the examples noted are now throwing 508 errors that
> are not in the out-of-the box  LibGuide templates and which are not the
> result of an individual content contributor/author inserting "bad stuff"
> like images without alt tags.
>
>
>
>
> Jonathan LeBreton
> Senior Associate University Librarian
> Editor:  Library & Archival Security
> Temple University Libraries
> Paley M138,  1210 Polett Walk, Philadelphia PA 19122
> voice: 215.204.8231
> fax: 215.204.5201
> mobile: 215.284.5070
> email:  lebre...@temple.edu
> email:  jonat...@temple.edu
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Cindi Blyberg
> Sent: Wednesday, September 17, 2014 12:03 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] LibGuides v2 - Templates and Nav
>
> Hey everyone!
>
> Not to turn C4L into Support4LibGuides, but... :)
>
> The infrastructure for all the APIs is in place; currently, the Guides API
> and the Subjects API are functioning.  Go to Tools > API > Get Guides to
> see the general structure of the URL.  Replace "guides" with "subjects" to
> retrieve your subjects.  You will need your LibGuides site ID, which you
> can get from the LibApps Dashboard screen.
>
> Word is that it will not take long to add other API calls on the back end;
> if you need these now, please do email supp...@springshare.com and
> reference this conversation.
>
> As for v1, we are planning on supporting it for 2 more years--that said,
> we would never leave anyone hanging, so if it takes longer than that to get
> everyone moved over, we're ready for that.
>
> Best,
>  -Cindi
>
> On Wed, Sep 17, 2014 at 10:46 AM, Nadaleen F Tempelman-Kluit  >
> wrote:
>
> > Hi all-
> > While we're on the topic of LibGuides V2, when will the "GET subjects"
> > API (and other API details) be in place? We're in a holding pattern
> > until we get those details and we've not been able to get any timeline
> > as to when those assets will be in place. So we're deciding between
> > building out LibGuides CMS "Global" landing pages using the V1
> > platform, or waiting until some future date which, very soon, will
> > mean abandoning this project till next summer. If we go the former
> > route, it would also be great to know how long V1 will be supported.
> > Thanks
> >
> >
> >
> > On Wed, Sep 17, 2014 at 10:29 AM, Cindi Blyberg 
> > wrote:
> >
> > > On Tue, Sep 16, 2014 at 7:15 PM, Michael Schofield
> > > 
> > > wrote:
> > >
> > > >
> > > > Q1. How complicated is it to change all 3 column guides to a
> > > single-column
> > > > left/right-nav layout?
> > > >
> > > > A little. You can force the entire group [or all groups] to use a
> > single
> > > > template, which is a huge time saver, except your guides' middle
> > > > and
> > > right
> > > > columns will be in "hidden" columns rather than forced to collapse
> > into a
> > > > single column. This was pretty confusing at first. We were afraid
> > > > we actually lost content during the migration. You will need to
> > > > manually
> > hit
> > > > every guide and change the layout to single-column, but that's
> > > > just a
> > > click
> > > > of the button. If you have 400+ guides, though, that's 400+ clicks.
> > > >
> > >
> > > Alas, yes. Once we realized this was happening, our devs hashed it
> > > out
> > and
> > > will be rolling out a fix to the migration script so that this won't
> > happen
> > > again.
> > >
> > > Q2. Three-columns or single column?
> > > > Single column. Us

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Benjamin Florin]

It's also important to note that because the out-of-the-box LG2 uses
Bootstrap there are some of the same accessibility problems in LG 2 that
plague most out-of-the-box Bootstrap implementations, especially with
keyboard navigation. For example, the top-navigation sub-page dropdowns
can't be accessed from the keyboard nor can the database information
popovers.

You'll need to test out-of-the-box LG 2 just as thoroughly as customized LG
2 templates and use tools like Paypal's Bootstrap Accessibility Plugin (
https://github.com/paypal/bootstrap-accessibility-plugin). The
out-of-the-box will probably pass automated testing, but it might not
always pass more thorough manual testing.

Ben

On Wed, Sep 17, 2014 at 1:49 PM, Jonathan LeBreton 
wrote:

> I might mention here that we (Temple University)  found LibGuides 2.0  to
> offer some noteworthy improvements in section 508 accessibility
> when compared with version 1.0.   Accessibility is a particular point of
> concern for the whole institution as we look across the city, state, and
> country at other institutions that have been called out and settled with
> various disability advocacy groups.
> So we moved to v. 2.0 during the summer in order to have those
> improvements in place for the fall semester, as well as to get the value
> from some other developments in v. 2.0 that benefit all customers.
>
> When I see email on list about making  modifications to templates and
> such, it gives me a bit of concern on this score that by doing so,  one
> might easily begin to make the CMS framework for content less accessible.
>   I thought I should voice that.This is not to say that one shouldn't
> customize and explore enhancements etc.,  but one should do so with some
> care if you are operating with similar mandates or concerns.Unless I am
> mistaken, several of the examples noted are now throwing 508 errors that
> are not in the out-of-the box  LibGuide templates and which are not the
> result of an individual content contributor/author inserting "bad stuff"
> like images without alt tags.
>
>
>
>
> Jonathan LeBreton
> Senior Associate University Librarian
> Editor:  Library & Archival Security
> Temple University Libraries
> Paley M138,  1210 Polett Walk, Philadelphia PA 19122
> voice: 215.204.8231
> fax: 215.204.5201
> mobile: 215.284.5070
> email:  lebre...@temple.edu
> email:  jonat...@temple.edu
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Cindi Blyberg
> Sent: Wednesday, September 17, 2014 12:03 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] LibGuides v2 - Templates and Nav
>
> Hey everyone!
>
> Not to turn C4L into Support4LibGuides, but... :)
>
> The infrastructure for all the APIs is in place; currently, the Guides API
> and the Subjects API are functioning.  Go to Tools > API > Get Guides to
> see the general structure of the URL.  Replace "guides" with "subjects" to
> retrieve your subjects.  You will need your LibGuides site ID, which you
> can get from the LibApps Dashboard screen.
>
> Word is that it will not take long to add other API calls on the back end;
> if you need these now, please do email supp...@springshare.com and
> reference this conversation.
>
> As for v1, we are planning on supporting it for 2 more years--that said,
> we would never leave anyone hanging, so if it takes longer than that to get
> everyone moved over, we're ready for that.
>
> Best,
>  -Cindi
>
> On Wed, Sep 17, 2014 at 10:46 AM, Nadaleen F Tempelman-Kluit  >
> wrote:
>
> > Hi all-
> > While we're on the topic of LibGuides V2, when will the "GET subjects"
> > API (and other API details) be in place? We're in a holding pattern
> > until we get those details and we've not been able to get any timeline
> > as to when those assets will be in place. So we're deciding between
> > building out LibGuides CMS "Global" landing pages using the V1
> > platform, or waiting until some future date which, very soon, will
> > mean abandoning this project till next summer. If we go the former
> > route, it would also be great to know how long V1 will be supported.
> > Thanks
> >
> >
> >
> > On Wed, Sep 17, 2014 at 10:29 AM, Cindi Blyberg 
> > wrote:
> >
> > > On Tue, Sep 16, 2014 at 7:15 PM, Michael Schofield
> > > 
> > > wrote:
> > >
> > > >
> > > > Q1. How complicated is it to change all 3 column guides to a
> > > single-column
> > > > left/right-nav layout?
> > > >
> > > > A little. You can force the entire group [or all groups] to use a
> > single
> > > > template, which is a huge time saver, except your guides' middle
> > > > and
> > > right
> > > > columns will be in "hidden" columns rather than forced to collapse
> > into a
> > > > single column. This was pretty confusing at first. We were afraid
> > > > we actually lost content during the migration. You will need to
> > > > manually
> > hit
> > > > every guide and change the layout to single-column, but that's
> > > > just a
> > > click
> > > > of 

[CODE4LIB] REGISTER for Advanced DSpace Training

[Carol Minton Morris]

Sept. 17, 2014

Read it online: http://bit.ly/1qJsGgg
Contact: Valorie Hollister 

Register for Advanced DSpace Training

In response to overwhelming community demand, we are happy to announce the 
dates for an in-person, 3-day Advanced DSpace Course in Austin October 22-24, 
2014. The total cost of the course is being underwritten with generous support 
from the Texas Digital Library and DuraSpace. As a result, the registration fee 
for the course for DuraSpace Members is only $250 and $500 for Non-Members 
(meals and lodging not included). Seating will be limited to 20 participants.

Course Overview
The three-day Advanced DSpace course provides instruction on advanced features 
and customizations in DSpace 4.2. Topics covered will include:

Configuration
* Themes and Aspects
* Emails
* Internationalization
* Authentication
* Media Filters
* Curation Tasks
* Submission Workflows
* Controlled Vocabularies
* Discovery, Search, and Browse
* Statistics
* Server Configuration
Content Transmission
* OAI protocols and harvesting
* RESTSubmission/Dissemination Packages
* AIP backup and restore
* SWORD servers and clients
* Batch Imports
XMLUI Theming
* Creating a new theme
* Colors, Fonts, and Layouts with CSS
* Presentation and Interaction

For more information or to register visit here. If you have any questions 
please contact Valorie Hollister at vhollis...@duraspace.org.

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Jonathan LeBreton]

I might mention here that we (Temple University)  found LibGuides 2.0  to offer 
some noteworthy improvements in section 508 accessibility 
when compared with version 1.0.   Accessibility is a particular point of 
concern for the whole institution as we look across the city, state, and 
country at other institutions that have been called out and settled with 
various disability advocacy groups. 
So we moved to v. 2.0 during the summer in order to have those improvements in 
place for the fall semester, as well as to get the value from some other 
developments in v. 2.0 that benefit all customers. 

When I see email on list about making  modifications to templates and such, it 
gives me a bit of concern on this score that by doing so,  one might easily 
begin to make the CMS framework for content less accessible.I thought I 
should voice that.This is not to say that one shouldn't customize and 
explore enhancements etc.,  but one should do so with some care if you are 
operating with similar mandates or concerns.Unless I am mistaken, several 
of the examples noted are now throwing 508 errors that are not in the 
out-of-the box  LibGuide templates and which are not the result of an 
individual content contributor/author inserting "bad stuff" like images without 
alt tags.   




Jonathan LeBreton
Senior Associate University Librarian
Editor:  Library & Archival Security
Temple University Libraries
Paley M138,  1210 Polett Walk, Philadelphia PA 19122
voice: 215.204.8231
fax: 215.204.5201
mobile: 215.284.5070
email:  lebre...@temple.edu
email:  jonat...@temple.edu

-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Cindi 
Blyberg
Sent: Wednesday, September 17, 2014 12:03 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] LibGuides v2 - Templates and Nav

Hey everyone!

Not to turn C4L into Support4LibGuides, but... :)

The infrastructure for all the APIs is in place; currently, the Guides API and 
the Subjects API are functioning.  Go to Tools > API > Get Guides to see the 
general structure of the URL.  Replace "guides" with "subjects" to retrieve 
your subjects.  You will need your LibGuides site ID, which you can get from 
the LibApps Dashboard screen.

Word is that it will not take long to add other API calls on the back end; if 
you need these now, please do email supp...@springshare.com and reference this 
conversation.

As for v1, we are planning on supporting it for 2 more years--that said, we 
would never leave anyone hanging, so if it takes longer than that to get 
everyone moved over, we're ready for that.

Best,
 -Cindi

On Wed, Sep 17, 2014 at 10:46 AM, Nadaleen F Tempelman-Kluit 
wrote:

> Hi all-
> While we're on the topic of LibGuides V2, when will the "GET subjects" 
> API (and other API details) be in place? We're in a holding pattern 
> until we get those details and we've not been able to get any timeline 
> as to when those assets will be in place. So we're deciding between 
> building out LibGuides CMS "Global" landing pages using the V1 
> platform, or waiting until some future date which, very soon, will 
> mean abandoning this project till next summer. If we go the former 
> route, it would also be great to know how long V1 will be supported.
> Thanks
>
>
>
> On Wed, Sep 17, 2014 at 10:29 AM, Cindi Blyberg 
> wrote:
>
> > On Tue, Sep 16, 2014 at 7:15 PM, Michael Schofield 
> > 
> > wrote:
> >
> > >
> > > Q1. How complicated is it to change all 3 column guides to a
> > single-column
> > > left/right-nav layout?
> > >
> > > A little. You can force the entire group [or all groups] to use a
> single
> > > template, which is a huge time saver, except your guides' middle 
> > > and
> > right
> > > columns will be in "hidden" columns rather than forced to collapse
> into a
> > > single column. This was pretty confusing at first. We were afraid 
> > > we actually lost content during the migration. You will need to 
> > > manually
> hit
> > > every guide and change the layout to single-column, but that's 
> > > just a
> > click
> > > of the button. If you have 400+ guides, though, that's 400+ clicks.
> > >
> >
> > Alas, yes. Once we realized this was happening, our devs hashed it 
> > out
> and
> > will be rolling out a fix to the migration script so that this won't
> happen
> > again.
> >
> > Q2. Three-columns or single column?
> > > Single column. Users scan, and they scan the top and left-most 
> > > portions
> > of
> > > the screen. Anything in the middle and to the right is lost.  
> > > Also,
> three
> > > columns on a responsive site is a little weird, because content is
> pretty
> > > squishy; on tablets you might have pretty narrow left and right
> columns.
> > >
> >
> > Actually, when you view a 3-column layout on a smaller screen, it 
> > scales down to a single column.  If you're seeing otherwise, can you 
> > send us
> some
> > examples in case this is a bug we need to fix?  Thanks. :)  The key 
> > he

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Cindi Blyberg]

Hey everyone!

Not to turn C4L into Support4LibGuides, but... :)

The infrastructure for all the APIs is in place; currently, the Guides API
and the Subjects API are functioning.  Go to Tools > API > Get Guides to
see the general structure of the URL.  Replace "guides" with "subjects" to
retrieve your subjects.  You will need your LibGuides site ID, which you
can get from the LibApps Dashboard screen.

Word is that it will not take long to add other API calls on the back end;
if you need these now, please do email supp...@springshare.com and
reference this conversation.

As for v1, we are planning on supporting it for 2 more years--that said, we
would never leave anyone hanging, so if it takes longer than that to get
everyone moved over, we're ready for that.

Best,
 -Cindi

On Wed, Sep 17, 2014 at 10:46 AM, Nadaleen F Tempelman-Kluit 
wrote:

> Hi all-
> While we're on the topic of LibGuides V2, when will the "GET subjects" API
> (and other API details) be in place? We're in a holding pattern until we
> get those details and we've not been able to get any timeline as to when
> those assets will be in place. So we're deciding between building out
> LibGuides CMS "Global" landing pages using the V1 platform, or waiting
> until some future date which, very soon, will mean abandoning this project
> till next summer. If we go the former route, it would also be great to know
> how long V1 will be supported.
> Thanks
>
>
>
> On Wed, Sep 17, 2014 at 10:29 AM, Cindi Blyberg 
> wrote:
>
> > On Tue, Sep 16, 2014 at 7:15 PM, Michael Schofield 
> > wrote:
> >
> > >
> > > Q1. How complicated is it to change all 3 column guides to a
> > single-column
> > > left/right-nav layout?
> > >
> > > A little. You can force the entire group [or all groups] to use a
> single
> > > template, which is a huge time saver, except your guides' middle and
> > right
> > > columns will be in "hidden" columns rather than forced to collapse
> into a
> > > single column. This was pretty confusing at first. We were afraid we
> > > actually lost content during the migration. You will need to manually
> hit
> > > every guide and change the layout to single-column, but that's just a
> > click
> > > of the button. If you have 400+ guides, though, that's 400+ clicks.
> > >
> >
> > Alas, yes. Once we realized this was happening, our devs hashed it out
> and
> > will be rolling out a fix to the migration script so that this won't
> happen
> > again.
> >
> > Q2. Three-columns or single column?
> > > Single column. Users scan, and they scan the top and left-most portions
> > of
> > > the screen. Anything in the middle and to the right is lost.  Also,
> three
> > > columns on a responsive site is a little weird, because content is
> pretty
> > > squishy; on tablets you might have pretty narrow left and right
> columns.
> > >
> >
> > Actually, when you view a 3-column layout on a smaller screen, it scales
> > down to a single column.  If you're seeing otherwise, can you send us
> some
> > examples in case this is a bug we need to fix?  Thanks. :)  The key here,
> > of course, is to have the most important information in the left-hand
> > column, and not to have too many boxes on a single page.
> >
> >
> > > Q5. Has anyone split the main content column into two smaller columns?
> > > LG2 makes it crazy easy to change number and percentage-based widths of
> > > the columns. So you could still use the tabs-across-the-top template
> and
> > > create a little 33% wide left "sidebar" column and a 66% wide right
> main
> > > column.
> > >
> >
> > One slight caution here:  if you add a second content column to a
> side-nav
> > layout and the guide author wants to display nav pills for the page's
> > boxes, only the boxes from the first content column will be displayed as
> > pills. This is by design, but we've filed it as a known issue.
> >
> >
> > >
> > >
> > > -Original Message-
> > > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf
> Of
> > > Blake Galbreath
> > > Sent: Tuesday, September 16, 2014 6:37 PM
> > > To: CODE4LIB@LISTSERV.ND.EDU
> > > Subject: Re: [CODE4LIB] LibGuides v2 - Templates and Nav
> > >
> > > I have always thought that left-nav was the UX standard for
> left-to-right
> > > languages (as opposed to Arabic, eg.: http://www.france24.com/ar/).
> > >
> > > Personally, I feel that right-nav makes more sense across the board,
> due
> > > to the fact that it is less distance to travel for right-handed people.
> > But
> > > the convention seems pretty set in stone. I am also not sure how screen
> > > readers deal with right-nav - although i am guessing that there is no
> > > problem there programming wise.
> > >
> > > Blake
> > >
> > > On Tue, Sep 16, 2014 at 3:24 PM, Brad Coffield <
> > > bcoffield.libr...@gmail.com>
> > > wrote:
> > >
> > > > Benjamin: "Unfortunately we have authors who want *three* columns
> plus
> > > > left-nav..." LOL
> > > >
> > > > Margaret: Love the floating nav on that page. It's exciting that

[CODE4LIB] book scanner experiences/recommendations

[Laura Buchholz]

Hi all,

We're looking into a overhead book scanner and I'd love to hear
suggestions. I've seen a thread from March (http://ntrda.me/1o3j9uT) but
we're looking for something more for patron use than digitization of rare
books.

-If you have a Bookeye4 (or others from Image Access), do you like it and
are happy with it? Does anyone have the glass v-shaped attachment for
flattening books that don't lay open? Or it that rarely a problem?
-Does anyone have a diy bookscanner that is for patron use? Do they do fine
with it? I'm looking at the kits, and drooling a little over the new one
, but it seems
more appropriate for staff use than patron use.
-Any other options I should consider, commercial or otherwise?
-If you have a scanner that you're happy with, and are in the Portland OR
area, could we come visit?

We want something primarily for staff (ILL, e-reserves), but it would be in
a public place for patrons to use as well. We're not looking at this time
for anything for archives or long-term digital projects, so something that
is easy to use takes precedence over high dpi or super careful handling of
rare materials.

Thanks for any help!

-- 
Laura Buchholz
Digital Assets Specialist
Reed College
503-517-7629
laura.buchh...@reed.edu

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Nadaleen F Tempelman-Kluit]

Hi all-
While we're on the topic of LibGuides V2, when will the "GET subjects" API
(and other API details) be in place? We're in a holding pattern until we
get those details and we've not been able to get any timeline as to when
those assets will be in place. So we're deciding between building out
LibGuides CMS "Global" landing pages using the V1 platform, or waiting
until some future date which, very soon, will mean abandoning this project
till next summer. If we go the former route, it would also be great to know
how long V1 will be supported.
Thanks



On Wed, Sep 17, 2014 at 10:29 AM, Cindi Blyberg  wrote:

> On Tue, Sep 16, 2014 at 7:15 PM, Michael Schofield 
> wrote:
>
> >
> > Q1. How complicated is it to change all 3 column guides to a
> single-column
> > left/right-nav layout?
> >
> > A little. You can force the entire group [or all groups] to use a single
> > template, which is a huge time saver, except your guides' middle and
> right
> > columns will be in "hidden" columns rather than forced to collapse into a
> > single column. This was pretty confusing at first. We were afraid we
> > actually lost content during the migration. You will need to manually hit
> > every guide and change the layout to single-column, but that's just a
> click
> > of the button. If you have 400+ guides, though, that's 400+ clicks.
> >
>
> Alas, yes. Once we realized this was happening, our devs hashed it out and
> will be rolling out a fix to the migration script so that this won't happen
> again.
>
> Q2. Three-columns or single column?
> > Single column. Users scan, and they scan the top and left-most portions
> of
> > the screen. Anything in the middle and to the right is lost.  Also, three
> > columns on a responsive site is a little weird, because content is pretty
> > squishy; on tablets you might have pretty narrow left and right columns.
> >
>
> Actually, when you view a 3-column layout on a smaller screen, it scales
> down to a single column.  If you're seeing otherwise, can you send us some
> examples in case this is a bug we need to fix?  Thanks. :)  The key here,
> of course, is to have the most important information in the left-hand
> column, and not to have too many boxes on a single page.
>
>
> > Q5. Has anyone split the main content column into two smaller columns?
> > LG2 makes it crazy easy to change number and percentage-based widths of
> > the columns. So you could still use the tabs-across-the-top template and
> > create a little 33% wide left "sidebar" column and a 66% wide right main
> > column.
> >
>
> One slight caution here:  if you add a second content column to a side-nav
> layout and the guide author wants to display nav pills for the page's
> boxes, only the boxes from the first content column will be displayed as
> pills. This is by design, but we've filed it as a known issue.
>
>
> >
> >
> > -Original Message-
> > From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> > Blake Galbreath
> > Sent: Tuesday, September 16, 2014 6:37 PM
> > To: CODE4LIB@LISTSERV.ND.EDU
> > Subject: Re: [CODE4LIB] LibGuides v2 - Templates and Nav
> >
> > I have always thought that left-nav was the UX standard for left-to-right
> > languages (as opposed to Arabic, eg.: http://www.france24.com/ar/).
> >
> > Personally, I feel that right-nav makes more sense across the board, due
> > to the fact that it is less distance to travel for right-handed people.
> But
> > the convention seems pretty set in stone. I am also not sure how screen
> > readers deal with right-nav - although i am guessing that there is no
> > problem there programming wise.
> >
> > Blake
> >
> > On Tue, Sep 16, 2014 at 3:24 PM, Brad Coffield <
> > bcoffield.libr...@gmail.com>
> > wrote:
> >
> > > Benjamin: "Unfortunately we have authors who want *three* columns plus
> > > left-nav..." LOL
> > >
> > > Margaret: Love the floating nav on that page. It's exciting that we'll
> > > be able to leverage Bootstrap with our guides now. Moving the entire
> > > library website to libguides CMS is looking more and more promising.
> > >
> > >
> > > Some more thoughts:
> > >
> > > I'm no UX expert but is it generally agreed that left-nav is the much
> > > better choice? It seems like it to me. Given current web wide
> > > conventions etc.
> > >
> > > One big issue to switching to left-nav in v2 is the amount of work
> > > it's going to take everyone to convert all guides to the new layout.
> > > Which is one of those things that both shouldn't matter (when looking
> > > at it in a principledness way - that is, "Whatever is best for the
> > > patrons! No matter
> > > what!) but also does matter (in a practical way - that is, "OMG we are
> > > all so busy being awesome").
> > >
> > > But part of me, when looking at other people's guides and my own,
> > > wonders if three columns isn't just a little TOO much for the user.
> > > How is one supposed to scan the page? What's the prioritized
> > > information? For a couple years now I've be

[CODE4LIB] Lesbian Herstory Archives Internships - Fall 2014

[DYV]

​​
*​​Lesbian Herstory Archives Internships*

​The *Lesbian Herstory Archives *
 (located in Park Slope, Brooklyn, NYC) is looking for students who are
interested in gaining library and/or archives experience with a
demonstrated interest in Lesbian Studies, History and Activism.  We have a
number of exciting projects for the upcoming academic year​.​  Students
must be currently enrolled in an M.L.S., Archival or DAM studies program to
apply. This is an unpaid internship opportunity.

*What We're Offering*

   - Interns will have the opportunity for practical application of
   archives and library skills.
   - Course credit and letters of recommendation will be provided upon
   request.
   - Interns will also receive the opportunity
   ​ to attend
workshops and classes outside of LHA
   - Interns will be supervised by professional librarians and other
   archives
   ​ professional​
   staff
   - ​Lunch will be provided​


*Requirements*

   - Avail
   ​ability​
​
   for a
   ​t leas
   ​t
one full
   ​8/hr week day
   per week.
   - ​C
   ompletion of *core *
   ​Library Science
   ​/Archives Management​
   courses
- Familiarity with cataloging
   ​, database data entry​
   and archival processing
   - Skilled in the use of MS Office and/or Google Docs and regular office
   equipment
   ​(copier, scanner, etc)​
   - ​Accustomed to working in a Windows/PC environment



*COLLECTION AREAS*


 *​Collection Processing (​*
*Periodicals*
*​, Video, Books​, Graphics, T-Shirts, ​Special Collections​​ ) ​*
​
​
Intern will process incoming donated materials​, ​update cataloging
records, prepare collections for ​off-site storage ​and contribute to the
collection management meetings & creation of the operating procedures
manual.
​


*​Online Public Access Catalog (​*
*OPAC​)​ Project*

Interns will perform database cleanup in a variety of collections and
contribute to the design, testing and launch of the LHA’s new OPAC.


*​Audio Digitization*

Interns will assist with the cataloging, digitization, indexing and
re-housing of
​spoken word and oral history ​
audio tapes.

​
​*Web Development*

​Interns will work in a team with professional web developers to overhaul
the LHA website. Students will have the opportunity to attend coding
courses and access other web-development related instruction​
​
​. Experience with introduction level CSS/HTML coding is required.
Experience using Square Space (or a similar web development platform)
preferred.​


*APPLICATION PROCESS*


 *​*
*​Applications​ are ​accepted on a rolling basis.  Please read the
instructions below very carefully.*

Candidates must submit a *Cover Letter *(indicating skills, experience,
relevant interests
​ ​
& availability) and *Resume* to* lha_inte...@earthlink.net
*

​
Please include the
​ ​
​phrase​
 *“Internship​ - Fall 2014​”**.  * All documents must be attached as a
*PDF.*

*NOTE:* LHA cannot provide housing for interns. LHA will provide
confirmation of internship acceptance for candidates who may need this
documentation to accompany a grant or fellowship application.
​
​*NO PHONE CALLS PLEASE.*

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Cindi Blyberg]

On Tue, Sep 16, 2014 at 7:15 PM, Michael Schofield 
wrote:

>
> Q1. How complicated is it to change all 3 column guides to a single-column
> left/right-nav layout?
>
> A little. You can force the entire group [or all groups] to use a single
> template, which is a huge time saver, except your guides' middle and right
> columns will be in "hidden" columns rather than forced to collapse into a
> single column. This was pretty confusing at first. We were afraid we
> actually lost content during the migration. You will need to manually hit
> every guide and change the layout to single-column, but that's just a click
> of the button. If you have 400+ guides, though, that's 400+ clicks.
>

Alas, yes. Once we realized this was happening, our devs hashed it out and
will be rolling out a fix to the migration script so that this won't happen
again.

Q2. Three-columns or single column?
> Single column. Users scan, and they scan the top and left-most portions of
> the screen. Anything in the middle and to the right is lost.  Also, three
> columns on a responsive site is a little weird, because content is pretty
> squishy; on tablets you might have pretty narrow left and right columns.
>

Actually, when you view a 3-column layout on a smaller screen, it scales
down to a single column.  If you're seeing otherwise, can you send us some
examples in case this is a bug we need to fix?  Thanks. :)  The key here,
of course, is to have the most important information in the left-hand
column, and not to have too many boxes on a single page.


> Q5. Has anyone split the main content column into two smaller columns?
> LG2 makes it crazy easy to change number and percentage-based widths of
> the columns. So you could still use the tabs-across-the-top template and
> create a little 33% wide left "sidebar" column and a 66% wide right main
> column.
>

One slight caution here:  if you add a second content column to a side-nav
layout and the guide author wants to display nav pills for the page's
boxes, only the boxes from the first content column will be displayed as
pills. This is by design, but we've filed it as a known issue.


>
>
> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Blake Galbreath
> Sent: Tuesday, September 16, 2014 6:37 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] LibGuides v2 - Templates and Nav
>
> I have always thought that left-nav was the UX standard for left-to-right
> languages (as opposed to Arabic, eg.: http://www.france24.com/ar/).
>
> Personally, I feel that right-nav makes more sense across the board, due
> to the fact that it is less distance to travel for right-handed people. But
> the convention seems pretty set in stone. I am also not sure how screen
> readers deal with right-nav - although i am guessing that there is no
> problem there programming wise.
>
> Blake
>
> On Tue, Sep 16, 2014 at 3:24 PM, Brad Coffield <
> bcoffield.libr...@gmail.com>
> wrote:
>
> > Benjamin: "Unfortunately we have authors who want *three* columns plus
> > left-nav..." LOL
> >
> > Margaret: Love the floating nav on that page. It's exciting that we'll
> > be able to leverage Bootstrap with our guides now. Moving the entire
> > library website to libguides CMS is looking more and more promising.
> >
> >
> > Some more thoughts:
> >
> > I'm no UX expert but is it generally agreed that left-nav is the much
> > better choice? It seems like it to me. Given current web wide
> > conventions etc.
> >
> > One big issue to switching to left-nav in v2 is the amount of work
> > it's going to take everyone to convert all guides to the new layout.
> > Which is one of those things that both shouldn't matter (when looking
> > at it in a principledness way - that is, "Whatever is best for the
> > patrons! No matter
> > what!) but also does matter (in a practical way - that is, "OMG we are
> > all so busy being awesome").
> >
> > But part of me, when looking at other people's guides and my own,
> > wonders if three columns isn't just a little TOO much for the user.
> > How is one supposed to scan the page? What's the prioritized
> > information? For a couple years now I've been eschewing three columns
> > whenever possible. Do others agree that three columns can be info
> overload?
> >
> > Brad
> >
> > On Tue, Sep 16, 2014 at 4:32 PM, Benjamin Florin <
> > benjamin.flo...@gmail.com>
> > wrote:
> >
> > > We've been tinkering with our LibGuides template in preparation for
> > > an eventual redesign of our site and guides, e.g.:
> > >
> > > http://libguides.bc.edu/libraries/babst/staff
> > >
> > > Some of our guide authors weren't happy with the LibGuides
> > > side-navigation's single-column limitation, so we made our own
> > > template, moved {{guide_nav}} off to a left column, and wrote our
> > > own styles to
> > make
> > > the default top-nav display as left-nav. We've found that a 50/50 or
> > 75/25
> > > split next to the left nav looks pretty good.
> > >
> > > Unfo

[CODE4LIB] Job: Application Developer at University of Michigan

[jobs]

Application Developer
University of Michigan
Ann Arbor

  
The University of Michigan Library Systems Office is seeking a talented and
resourceful application developer to help our team develop new systems and
services while enhancing and troubleshooting our existing applications and
infrastructure.

  
Major areas of work will include some or all of the
following:

* development of a registry of metadata, including a significant suite of 
related procedures and interfaces, that will identify the complete corpus of 
U.S. federal government documents;  
* updates and/or enhancements to a HathiTrust database (and the suite of 
scripts used to manage it) that tracks the physical holdings of HathiTrust 
partner institutions;  
* enhancements to the infrastructure that underlies the University of 
Michigan's Mirlyn library catalog and the HathiTrust bibliographic catalog  
* porting of existing publicly available bibliographic databases from a 
deprecated hosting platform to a new environment  
  
This is a term-limited position, funded for two years, with the possibility of
renewal. The full posting with application information is available at
http://umjobs.org/job_detail/96990/applications_developer

The University of Michigan is a non-discriminatory, affirmative action
employer.



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

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Sean Hannan]

On 9/16/14, 7:15 PM, "Michael Schofield"  wrote:

>
>Q4. No nav?
>Okay, nobody actually brought this up, but users don¹t tend to look at
>sidebars at all. Most libraries have a top menu in the header. If this is
>the case, consider dropping sidebars entirely and positioning your single
>column of content with equal margins. Why? Well, white-space. People like
>white-space. Too much stuff on the page--stuff, by the way, people won't
>look at anyway--increases cognitive load, which might just put your
>patrons in a grumpy mood when looking for simple content. Also consider
>that libraries--like every industry--will eventually have their mobile
>moment. For some of us it might be pretty far away, but eventually mobile
>traffic will eclipse traditional desktop traffic (charts!
>http://talks.ns4lib.com/patrons-on-performance/images/mobile-web-usage.png
> and 
>http://talks.ns4lib.com/patrons-on-performance/images/mobilemoment.png ).
>
>Removing sidebar content also forces your design committee / content
>creators to think harder about the quality of their content and be a
>little bit more choosy about screen real estate.
>
>If you're interested in trying the no-sidebar thing, you may consider
>customizing the template so that the "side nav" appears as good old
>fashioned links at the top of your content, like--well--a table of
>contents. This isn't the best example, but it's an idea:
>http://public.library.nova.edu/help/#content.

On this front, our analytics repeatedly show that users do not use the nav
within libguides. They do not browse around between pages within the
guides. Most of the entries to secondary pages come from Google searches
using keywords directly related to their information. Non-search entry
points are only the ŒHome¹ (first) page of the guide and those come from
librarians showing the guide in instruction sessions or from the list of
guides displayed on our homepage[1].

Now, this could be because the nav in LG1 is terrible, tabs with
overlapping drop-downs are a horrible idea, and the design lends itself
more towards users ignoring the nav section than engaging with it. YMMV.
>From other research we¹ve done, we know that our users are quick to
google, have pointed questions that demand pointed answers. They¹re not
much into exploring the breadth of information gathering techniques for
their discipline/topic (e.g. Someone looking for the registration
information for SciFinder isn¹t going to suddenly going to see the
ŒUndergraduate Labs¹ link and feel the need to check it out.).

[1] http://www.library.jhu.edu

-Sean

Re: [CODE4LIB] LibGuides v2 - Templates and Nav

[Will Martin]

Have you tried assigning the Health Sciences guides to their own groups 
and

adding custom header HTML at the group-level (Admin > Groups >
Header/Footer/Tabs/Boxes)? You can't use the new mustache-based 
templating

inside the headers, but you can use plain-jane HTML.


An excellent suggestion!  But, alas, groups are only available in 
LibGuides CMS.  Due to budgetary constraints, we're stuck with the 
regular version.


Templates are customizable, and those customizations apply to the 
entire
page, not just to the content area, although Will's right that with 
regular
LibGuides the entire system and all the guides have a single look & 
feel.


Yes, that's a good clarification -- the template can adjust the whole 
page, not just the content area as I mistakenly wrote.  But there's no 
mechanism for applying a template to a specific page or group of pages 
unless you have LibGuides CMS, so that doesn't help in my case.


I thought about writing some JS to surgically alter the page header 
after load time, determining who was in which library based on guide 
tags.  That would have been like pulling your wallet from your left 
pocket with your right hand -- it'd work, it's just horribly awkward.  
Also I'm pretty certain given my set of librarians that the tags would 
be forgotten or mistyped fairly often, followed by complaints that it's 
broken.  But ultimately, the main reason I shelved the idea was that I'm 
the only web developer the library has -- I have to be chary of my time, 
and other projects took priority.


Will

[CODE4LIB] Job: Support Engineer (Unix-Linux) at University of Oxford

[jobs]

Support Engineer (Unix-Linux) 
University of Oxford
Oxford

Bodleian Libraries, Osney One, Oxford

Grade 7: £30,434 - £37,394 p.a.

Bodleian Digital Library Systems and Services (BDLSS) is seeking to appoint a
Support Engineer (Unix-Linux) to join their team who develop and maintain a
range of applications, supporting the libraries in their day to day
operations, and delivering services to staff, students, researchers, and the
wider public.

  
You will have experience in managing complex applications in a Linux
environment to provide support for the Integrated Library System and discovery
platform alongside other members of the team. You will manage databases which
power important library systems (principally the Bodleian Libraries Admissions
card service).

  
We are moving towards a more resilient Service Delivery structure, while
consolidating our servers and services to better meet the needs of our
customers and users at the libraries. We are looking for someone with a
proactive approach to service improvement and delivery, who will take
initiative to suggest improvements, changes or development ideas.

  
You will have experience of using the Unix/Linux command line for management
of scripts, configuration and services; scripting experience; and knowledge of
web technologies including HTML and CSS. Excellent problem-solving and
analytical skills, with experience in troubleshooting of technical issues, are
also essential.

  
Applications for this vacancy are to be made online. You will be required to
upload a supporting statement as part of your online application. Your
supporting statement should list each of the essential and desirable selection
criteria, as listed in the further particulars, and explain how you meet each
one. CVs will not form part of the selection process.

  
Only applications received online before 12.00 midday on 10 October 2014 can
be considered. It is anticipated that interviews will take place on 27 October
2014.



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