LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  August 2013

CODE4LIB August 2013

Subject:

Re: Subject guide policies (was [CODE4LIB] LibGuides: I don't get it)

From:

Ron Gilmour <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 14 Aug 2013 12:35:45 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (217 lines)

We don't do tabs (we use SubjectsPlus, not Libguides). Our rules about side
columns read as follows:

Left Column should contain primary content.

Right column should contain supplemental content including, but not limited
to:

   - Dashboard (directly under subject specialist)
   - Other content may include Related guides, Selected journals / RSS,
   Associations, Help documents.

Not very strict, since "primary" and "supplemental" are subjective. I've
also had to remind that their right-column content will display below their
left column content on a smaller screen.




On Wed, Aug 14, 2013 at 10:50 AM, Josh Welker <[log in to unmask]> wrote:

> Thanks.Do you have any guidelines around the numbers and colors of tabs?
> That is one of the big issues. Also, do you have rules around what is
> allowed in side columns?
>
> Josh Welker
>
> On Aug 14, 2013, at 9:33 AM, Ron Gilmour <[log in to unmask]> wrote:
>
> > At Ithaca College, the web team has recently written some very loose
> > guidelines on the construction of subject guides. Generally, we stayed
> away
> > from saying much about content, so most of the rules apply to the
> presence
> > and placement of certain common structural elements. For example, there
> > should always be contact information for the librarian and this should
> > always be in the top right. There should be table of contents (unless the
> > guide is really short) and it should be located at the top of the main
> > column.
> >
> > There are also some rules that are intended to prevent responsivity
> > problems (e.g., wrap your embedded videos in a <div
> > class="fitvid<http://fitvidsjs.com/>">
> > to make sure they are usable on mobile devices).
> >
> > In order to keep a reasonable content hierarchy, we ask that librarians
> use
> > only h3 or lower for internal headers.
> >
> > We've specified what we call a "dashboard" widget that contains links to,
> > well, things that are often linked to from subject guides (e.g., ILL,
> > citation info). This element is required on all guides.
> >
> > Regarding buy-in, we stressed that these rules were based on responses
> from
> > actual users in usability tests. This is convincing to most (not all)
> > librarians. Our usability tests showed that consistency across guides is
> > important to users. We presented the rules as representing a balance
> > between pedagogical freedom for librarians and the need for consistency
> and
> > ease of navigation for users. (A paper on this is currently under
> review.)
> >
> > Enforcement has not been a major issue. Content-creators have been
> *cough* we
> > use tasers *cough* very cooperative.
> >
> > Ron Gilmour
> > Web Services Librarian
> > Ithaca College Library
> >
> >
> > On Wed, Aug 14, 2013 at 9:27 AM, Joshua Welker <[log in to unmask]> wrote:
> >
> >> One of the recurring themes in the LibGuides thread was that libraries
> >> need better policies regarding content and style management in guides. I
> >> wholeheartedly agree here, but my attempts to do so in the past were
> shot
> >> down in favor of giving all librarians maximum freedom.
> >>
> >> I have two questions:
> >>
> >> 1) What kind of policies do you all have in place for subject guide
> style
> >> and content management?
> >> 2) How do you get librarians to buy in to the policies, and how are they
> >> enforced?
> >>
> >> Josh Welker
> >> Information Technology Librarian
> >> James C. Kirkpatrick Library
> >> University of Central Missouri
> >> Warrensburg, MO 64093
> >> JCKL 2260
> >> 660.543.8022
> >>
> >>
> >> -----Original Message-----
> >> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> >> Jimmy Ghaphery
> >> Sent: Tuesday, August 13, 2013 5:49 PM
> >> To: [log in to unmask]
> >> Subject: Re: [CODE4LIB] LibGuides: I don't get it
> >>
> >> I have followed this thread with great interest. In 2011 Erin White and
> I
> >> researched many of the issues the group has been hitting on,
> demonstrating
> >> the popularity of LibGuides in ARL libraries, the locus of control
> outside
> >> of systems' departments, and the state of content policies.[1]
> >>
> >> Our most challenging statement in the article to the library tech
> >> community (which was watered down a bit in the peer review process) was
> >> "The popularity of LibGuides, at its heart a specialized content
> >> management system, also calls into question the vitality and/or
> >> adaptability of local content management system implementations in
> >> libraries."
> >>
> >> One of the biggest challenges I see toward creating a non-commercial
> >> alternative is that the library code community is so dispersed in the
> >> various institutions that it makes it difficult to get away from the
> >> download tar.gz model. Are our institutions ready to collaborate across
> >> themselves such that there could be a shared SaaS model (of anything
> >> really) that libraries could subscribe/contribute to? The barriers here
> >> certainly aren't technological, but more along the lines of policy,
> >> governance, etc.
> >>
> >> As for Research Guides in general, I see a very clear divide in the
> >> public/tech communities not only on platform but more philosophical.
> From
> >> the tech side once it is all boiled down, heck why do you even need a
> >> third party system; catalog the databases with some type of local genres
> >> and push out an api/xml feeds to various disciplines. From the public
> side
> >> there is a long lineage of individually curated guides that goes to the
> >> core of value of professionally knowing one's community and serving it.
> >>
> >> [1] https://ejournals.bc.edu/ojs/index.php/ital/article/view/1830
> >>
> >> best,
> >>
> >> Jimmy
> >>
> >>
> >>
> >> On Tue, Aug 13, 2013 at 11:13 AM, Galen Charlton <[log in to unmask]>
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> On Tue, Aug 13, 2013 at 6:53 AM, Wilhelmina Randtke <[log in to unmask]
> >>>> wrote:
> >>>
> >>>> There's not a lock-in issue with LibGuides, because it's used to
> >>>> host pathfinders. Those are supposed to be periodically revisited.
> >>>> One of
> >>> the
> >>>> big problems is that librarians will start a guide and never finish,
> >>>> or make one then never maintain it. Periodically deleting
> >>>> everything is a good thing for pathfinders and subject guides, and
> >>>> people should do it anyway. No one's talking about tools for
> >>>> digital archives, which have
> >>> lock
> >>>> in issues and are way more expensive.
> >>>>
> >>>
> >>> Lock-in doesn't have to be absolute to be effective, it just has to
> >>> has raise the bar sufficiently high to make users think twice about
> >>> migrating away.
> >>>
> >>> This applies even if the data to be moved is transitory and constantly
> >>> changing. For example, if a library has been diligently updating
> their
> >>> pathfinders, but wants to switch platforms, if there were no way to
> >>> export them to load into the successor system, the effort of redoing
> >>> them or doing a lot of copy-and-pasting could be prohibitive.
> >>>
> >>> As a general statement -- and I know that this battle has been
> >>> bitterly fought in the ILS space -- I believe that *all* library
> >>> software services, whether based on F/LOSS software or proprietary
> >>> software, should provide a way for the library to obtain a full dump
> >>> of their data, in an accessible format, at no additional charge.
> >>>
> >>> I see that LibGuides advertises the ability to make local backups of
> >>> individual pages and also provides (via a paid add-on module) an XML
> >>> export function. I don't know if SpringShare will also provide free
> >>> one-time exports on request, but I would hope they do.
> >>>
> >>> Of course, even if one has the data in hand, data migrations can still
> >>> take a lot of time, effort, and expertise.
> >>>
> >>> Regards,
> >>>
> >>> Galen
> >>> --
> >>> Galen Charlton
> >>> Manager of Implementation
> >>> Equinox Software, Inc. / The Open Source Experts
> >>> email: [log in to unmask]
> >>> direct: +1 770-709-5581
> >>> cell: +1 404-984-4366
> >>> skype: gmcharlt
> >>> web: http://www.esilibrary.com/
> >>> Supporting Koha and Evergreen: http://koha-community.org &
> >>> http://evergreen-ils.org
> >>>
> >>
> >>
> >>
> >> --
> >> Jimmy Ghaphery
> >> Head, Digital Technologies
> >> VCU Libraries
> >> 804-827-3551
> >>
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager