Go to:
Discussion
Online Doc
File
Poll
Event
Picture
David Vess's picture

Strategic Plan Project List

Project List

  • Project 5
    • LITA Events web page planning (DSV: I feel like this is really somewhat accomplished with our work in Project 3, but there's always room for improvement.)
    • WCC Volunteers:
      • Patrick and Jessica
    • Background:
    • Activities from January to June 2013
      • Jessica and Patrick shared proposal (see Oct. 2012 update link above) with Jenny Levine in ALA's ITTS in March.  No word back yet on integration ideas.

Completed Projects

  • Project 3 Web Site Migration
    • WCC  Volunteers:
      • David Vess
      • Holly Nguyen 
      • Patrick Confer

 


 

Project 1

Project 1 Strategic Plan Mapping

Goal Area:

THE ORGANIZATION

Anticipated Date of Completion: TBD

Objective:

Create a culture of communication and collaboration among all LITA entities.

Strategy:

1.1.1 Identify and support tools needed by membership, committees and interest groups e.g. ALA Connect.

 

Goal Area:

INNOVATION

Anticipated Date of Completion: TBD

Objective:

2.3.3 Embrace innovations in information, communication, learning, and scholarly technologies.

Strategy:

Establish best practices for use of ALA-wide communication tools and technologies.

 

Project 1 Plan

Implementation Steps

(What will be done?)

Roles & Responsibilities

(Who will do it?)

Resources
(What’s needed?)

A: Resources Available

B. Resources Needed

Timeline

(When will it get done?)

Communication Plan

(Who are we going to tell and how are we going tell them about it?)

Emerging Leaders Project O, LITA communications channels

  • Transfer the LITA Wiki content to ALA Connect.
  • Add a description, purpose, and intended audience of each LITA listserv to ALA connect.  This can be accomplished by asking listerv owners to add an entry.
  • Identify point person/people for Twitter and Facebook.
  • Make sure the blog is pushing to Twitter and that Twitter is pushing to Facebook.
  • Predominately feature ALA Connect on the LITA website.

 

Emerging Leaders Project O, LITA communications channels

Technology Subcommittee -- investigate automating content import

This would make an ideal project for a graduate intern or others looking to gain experience with LITA.

Communications Subcommittee - Identify a point person for social media, more regular contributions to LITA.org

 

 

Emerging Leaders Project O, LITA communications channels

No additional server or software requirements, but it requires someone to evaluate the best method for importing Wiki content, and then moving it to ALA Connect.

 

Emerging Leaders Project O, LITA communications channels

 

TBD; depends heavily on other LITA projects. Could push through some of this fairly quickly. Migrating content from the wiki to connect could take a while.

 

Emerging Leaders Project O, LITA communications channels

Communication consists of three parts:

1.      Informing LITA membership of the changes to the wiki (and perhaps blog).

2.      Reinforcing that ALA Connect is the de facto tool for interactive LITA communications.

3.      Provide regular virtual training on how to use ALA Connect (both basic and advanced)

4.      Publishing the outline of what container is for what information on all channels and maintaining it in a FAQ section of the website, listserv documentation, blog, and ALA Connect.

 

Additional Comments:

Potential Barriers and how they will be addressed: The largest barrier is ensuring that new communication technologies are evaluated for their appropriateness and sustainability before being adopted as official LITA communication channels.

It will also be a challenge to inform everyone of this more standardized approach. People are used to using different tools in different ways, and this approach will not be what everyone is used to.

Final Results: A more consistent and up to date LITA web presence, clearer channels of communication for those interested in learning more about LITA

Completed Date: TBD

 

 

 


 

 

 

Project 2

Project 2 Strategic Plan Mapping

Goal Area:

THE ORGANIZATION

Anticipated Date of Completion: March 2011

Objective:

Develop and promote the LITA brand.

Strategy:

1.2.1 Broaden and promote knowledge of LITA services and programs.

 

Goal Area:

THE ORGANIZATION

Anticipated Date of Completion: March 2011

Objective:

Develop and promote the LITA brand.

Strategy:

1.2.2 Identify and prioritize LITA's technology strengths to determine our niche within the greater community.

 

Goal Area:

INNOVATION

Anticipated Date of Completion: March 2011

Objective:

Embrace innovations in information, communication, learning, and scholarly technologies.

Strategy:

2.3.4 Apply mobile access thinking to all LITA communication, marketing, and publishing activities.

Project 2 Plan

Implementation Steps

(What will be done?)

Roles & Responsibilities

(Who will do it?)

Resources
(What’s needed?)

A: Resources Available

B. Resources Needed

Timeline

(When will it get done?)

Communication Plan

(Who are we going to tell and how are we going tell them about it?)

LITABlog Renewal

1. Move (future) posts that are primarily intra-LITA on to ALA Connect

 

2. Create an editorial team with at an editor to manage each of the categories

-- establish formal

relationship with every Interest Group, ITALICA, BIGWIG, etc.

 

3. Establish post conventions that follow specific categories highlighting LITA members'

knowledge and appeal to people with a general interest in library technologies.

 

4. Create a way of decision-making on categories or features that is inclusive but agile enough to not require waiting until next physical meeting to incorporate

 

LITABlog Renewal

Technology Subcommittee will maintain the server space, software patches, upgrades, new plugin requests, etc.

Perhaps Chair of Technology Subcommittee should sit in with BIGWIG?

 

Communications Subcommittee will recruit and manage editorial team.

 

Members of Communication Subcommittee work with IGs, reach out annually to encourage editor recruitment.

LITABlog Renewal

A. We have the blog hosting space.

B. Editorial time and talent needed

 

Regular maintenance window for blog and server

 

Commitment from WCC Chair and/or Board Liaison to mediate transition from older format to new content model

LITABlog Renewal

1. Immediately, already in progress

 

2. Recruitment has begun and will be ongoing

 

3. A team established and posting by Midwinter or soon after

 

4. Discussion at Midwinter can define initial categories, further refinement should be ongoing

LITABlog Renewal

Communicate with frequent and longstanding contributors to share the vision of the new direction of LITABlog

 

Announcements via LITA-L, LITABlog, ALA Connect, and American Libraries calling for editors of specified categories

 

Communications Subcommittee members contact IGs to invite their participation

 

Explore opportunities to announce to other relevant communities not under the ALA structure e.g. Code4Lib, LISNews, other blogs, etc.

Additional Comments:

Potential Barriers and how they will be addressed: 

Final Results: LITA Blog content will evolve to appeal to people with a general interest in library technologies

A completed event site within the LITA site that addresses work flow issues.  This would be implemented with an eye towards maintaining this information the site indefinitely and would require minimal edits and/or moving of pages/content.

Completed Date: March 2011 for LITABlog, July 2011 Conference Portal

 

 


 

 

Project 4

Project 4 Strategic Plan Mapping

Goal Area:

INNOVATION

Anticipated Date of Completion: July 2011

Objective:

Experiment—become a hive for innovation.

Strategy:

2.4.1 Provide an environment to experiment with new technologies.

Project 4 Plan

Implementation Steps

(What will be done?)

Roles & Responsibilities

(Who will do it?)

Resources
(What’s needed?)

A: Resources Available

B. Resources Needed

Timeline

(When will it get done?)

Communication Plan

(Who are we going to tell and how are we going tell them about it?)

Sandbox

1.      Explore needs of LITA members for platform

2.      Explore different platforms available

3.      Write up report making recommendation of platform

4.      Work with ITTS to determine where and how to implement

5.      Implement Platform

6.      Provide documentation on how to request access and capabilities available

7.      Assess success

 

 

 

Emerging Leaders Group?

 

ITTS

 

Matthew Hamilton and Tech Subcommittee members

 

BIGWIG?

 

A. Server space from ITTS, Technical Assistance from ITTS staff, Technical skills on WCC

 

B. Need to define what would be useful in a Sandbox server

 

1. By end of March 2011

 

2. April 2011

 

3. May 2011

 

4. May 2011

 

5. June - July 2011

 

6. July 2011

 

7. November 2011

 

1. Create a survey and send out to LITA-L list, post on LITABlog, ALAConnect, etc.

 

3. Email to board liaison, Mary Taylor, Melissa Prentice,  ITTS, and ALA's WAC

 

4.  ITTS - TBD

 

6. Make announcements on LITA-L, LITABlog, ALA Connect

Additional Comments:

Potential Barriers and how they will be addressed: 

Final Results: A Sandbox environment for use by members of LITA for innovation and learning

Completed Date: July 2011

 

 


 

 

Project 5

(DSV: I feel like this is really somewhat accomplished with our work in Project 3, but there's always room for improvement.)

Project 5 Strategic Plan Mapping

Goal Area:

COLLABORATION & OUTREACH

Anticipated Date of Completion: June 2011

Objective:

Actively engage members, both virtually and in person, throughout the year.

Strategy:

4.1.1 Implement virtual tools that will allow LITA to reach out to and engage more of its existing and potential members.

Project 5 Plan

Implementation Steps

(What will be done?)

Roles & Responsibilities

(Who will do it?)

Resources
(What’s needed?)

A: Resources Available

B. Resources Needed

Timeline

(When will it get done?)

Communication Plan

(Who are we going to tell and how are we going tell them about it?)

Emerging Leaders Portal Project P

 

1. Establish naming conventions of web page files; establish the index page contents of the “Programs and Events” directory in consultation with LITA staff needs.  (will index page always lead to the top-level event page?  If it does, it will help us keep all this material long term and reduce time moving things)           

 

2. Implement template into the existing Programs and Events node of the LITA site             

Emerging Leaders Portal Project P

 

Tara Lannen-Stanton (Emerging Leader Project Participant); ask Tara who of the Group might be good people to ask to work on this? ; member2; member3;

 

This work overlaps with the work of the Links & Structure group.  Some members of this group will assist with this endeavor.

Emerging Leaders Portal Project P

Available: Collage training for new volunteers;

 

1. Needed: volunteer training in Collage;

 

2. Needed: more volunteers; Access and training for new Drupal site.     

Emerging Leaders Portal Project P

 

 

 

Feb 21, 2011

 

May 16, 2011

Emerging Leaders Portal Project P

Email:

* Matthew Hamilton, WCC Chair;

* Louise Gruenberg lgruenberg@ala.org, ALA Usability Officer; LITA personnel; LITA-L to announce test of new approach and call for feed back after Annual?

 

Additional Comments: WCC will need to establish (perhaps) always have a small group of members volunteer to manage this website within our website?

Potential Barriers and how they will be addressed: 

    * Needs/input from LITA staff are unknown currently.  Will establish a liaison working on this project to work with LITA staff on identifying their needs and expectations.

    * Timely maintenance of such pages is idea.  Old LITA events pages are the worst at having broken links.  Will explore documenting what links can be removed from event pages after conferences/forums/meetings are over. (Create reminders in a calendaring system?)

Final Results: A completed event site within the LITA site that addresses work flow issues.  This would be implemented with an eye towards maintaining this information the site indefinitely and would require minimal edits and/or moving of pages/content.

Completed Date: June 2011

 

 


 

Completed Projects

Project 3 (Migration of LITA Website into new content management system)

Project 3 Strategic Plan Mapping

Goal Area:

THE ORGANIZATION

Completed June 2011. Site migration competed Nov 2011.

Objective:

Develop and promote the LITA brand.

Strategy:

1.2.3 Develop a strong online presence.

 

Goal Area:

COLLABORATION & OUTREACH

Completed June 2011. Site migration competed Nov 2011.

Objective:

Actively engage members, both virtually and in person, throughout the year.

Strategy:

4.2.2 Increase engagement with ALA Information Technology & Telecommunication Services (ITTS).

Project 3 Plan

Implementation Steps

(What will be done?)

Roles & Responsibilities

(Who will do it?)

Resources
(What’s needed?)

A: Resources Available

B. Resources Needed

Timeline

(When will it get done?)

Communication Plan

(Who are we going to tell and how are we going tell them about it?)

LITA.org Update

1. Evaluate all links on LITA web site.  Repair broken links and links pointing to incorrect destinations.

2. Analyze site structure.  Note the section’s structure is acceptable or offer a new structure in our model site noted above.  (Acceptable site structures and recommended structures will all be captured in mock site.)

3. Submit the mock site for approval to WCC Chair and/or LITA Board ?

4. Implement site structure per approval of WCC Chair, (Do we need LITA Board approval?)

 

 

 

 

LITA.org Update

David S. Vess

Holly Nguyen

Patrick Confer

LITA.org Update

Permissions to change the left Navigation bar for team members.  (David has permissions and over a year of experience editing the GLBTRT’s site navigation.)

LITA.org Update

1.      5 January, 2011

2.      15 February, 2011

3.      15 February, 2011

4.      20 June, 2011

LITA.org Update

Email: 
* Matthew Hamilton, WCC Chair;

* Louise Gruenberglgruenberg@ala.org, ALA Usability Officer; other ALA personnel?

Additional Comments: The LITA Website Redesign Basics June 27, 2010 document notes that the website directories and actual page names should be shortened so that urls are shorter and neater.  After the above work is done, team members will likely be able to suggest the renaming of all the structures on the site.  While the above work is proceeding, it may be practical to rename directories and pages.  It might be good to consult with ALA staff.  Louise Gruenberg lgruenberg@ala.org, ALA Usability Officer and others?  Normally creating redirects for changed pages is ideal but the scale of this work is impractical.

Another matter and future goal concerns cleaning up code.  If all the above can be accomplished, we may be able to set goals for cleaning up code so that documents are marked up with proper headings, paragraph tags, etc.

When LITA’s site has to be imported into the new Drupal site will be important.

Potential Barriers and how they will be addressed: 
* Confusion, scale, number of people involved – the group will use the mock LITA site to share with each other, LITA members and ALA staff.  The intention of the site is only to illustrate structure, not to edit text.

*  Most work will be done virtually; meet online; use email.

 

Final Results:

* repair all broken links and links that are pointing to incorrect destinations.

* recommend, seek approval for and implement a new site structure beneath all top-level navigation buttons. (crumb menus will work).

* shorten/rename verbose names of directories and files so that URLs are shorter (will improve crumb menus).

Completed June 2011. Site migration competed Nov 2011.