Middlebury

Difference between revisions of "LIS Website"

m
Line 427: Line 427:
 
=== 2009:  June 24  ===
 
=== 2009:  June 24  ===
  
Present:  Elin Waagen, Jess Isler, Ian McBride (time-keeper), Carrie Macfarlane (note-taker), Liz Whitaker-Freitas, Jim Beauchemin, Barbara Merz.
+
Present:  Elin Waagen, Jess Isler, Ian McBride (time-keeper), Carrie Macfarlane (note-taker), Liz Whitaker-Freitas, Jim Beauchemin, Barbara Merz.  
  
<br>
+
<br>  
  
1.&nbsp; Questions for the team - Jim and Carrie
+
1.&nbsp; Questions for the team - Jim and Carrie  
  
<br>
+
<br>  
  
 
*Jim had some questions about roles and communication methods.&nbsp; He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
 
*Jim had some questions about roles and communication methods.&nbsp; He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
Line 439: Line 439:
 
*Carrie shared what she'd done to get caught up on team training.&nbsp; She asks that team members tell her when she does something contrary to what the team learned/agreed to during training.
 
*Carrie shared what she'd done to get caught up on team training.&nbsp; She asks that team members tell her when she does something contrary to what the team learned/agreed to during training.
  
<br>
+
<br>  
  
2.&nbsp; Decide on a platform to facilitate documentation and communication&nbsp;
+
2.&nbsp; Decide on a platform to facilitate documentation and communication&nbsp;  
  
<br>
+
<br>  
  
 
*What will we use this platform for?&nbsp; Communication within the team and with our users/constituents.
 
*What will we use this platform for?&nbsp; Communication within the team and with our users/constituents.
Line 455: Line 455:
 
*Ian created this Wiki category and our blog (&lt;a href="http://blogs.middlebury.edu/liswebsite/"&gt;LIS&nbsp;Website Project&lt;/a&gt;).
 
*Ian created this Wiki category and our blog (&lt;a href="http://blogs.middlebury.edu/liswebsite/"&gt;LIS&nbsp;Website Project&lt;/a&gt;).
  
<br>
+
<br>  
  
3.&nbsp; Team Protocols
+
3.&nbsp; Team Protocols  
  
<br>
+
<br>  
  
 
*Team protocols that were agreed upon during team training were listed:
 
*Team protocols that were agreed upon during team training were listed:
  
a. Meet weekly - adjust frequency as needed if there are no/more agenda items.
+
a. Meet weekly - adjust frequency as needed if there are no/more agenda items.  
  
b. Set agenda ahead of time
+
b. Set agenda ahead of time  
  
c. Shared responsibility to generate agenda items, agenda facilitated by team leader
+
c. Shared responsibility to generate agenda items, agenda facilitated by team leader  
  
d. Agenda items will have specific time and sponsor
+
d. Agenda items will have specific time and sponsor  
  
e. Time keeper
+
e. Time keeper  
  
f. Note taker-- I think this responsibility should rotate alphabetically.&nbsp; If someone can't take notes when it's his/her turn then that person can ask for a substitute.&nbsp; &lt;a href="User:Carrie Macfarlane"&gt;Macfarlane, Carrie Miyoshi&lt;/a&gt; 13:13, 30 June 2009 (UTC)
+
f. Note taker-- I think this responsibility should rotate alphabetically.&nbsp; If someone can't take notes when it's his/her turn then that person can ask for a substitute.&nbsp; &lt;a href="User:Carrie Macfarlane"&gt;Macfarlane, Carrie Miyoshi&lt;/a&gt; 13:13, 30 June 2009 (UTC)  
  
<br>
+
<br>  
  
f1. Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting. [Barbara 6/26]
+
f1. Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting. [Barbara 6/26]  
  
g. Use shared platform for communication and development of documentation
+
g. Use shared platform for communication and development of documentation  
  
h. Timely (define?) posting of meeting notes
+
h. Timely (define?) posting of meeting notes  
  
i. Time at end (5-10 min) for discussion or overflow or to set next meeting agenda
+
i. Time at end (5-10 min) for discussion or overflow or to set next meeting agenda  
  
j. If unable to attend, responsible for getting caught up
+
j. If unable to attend, responsible for getting caught up  
  
k. Open honest dialogue (with tact)
+
k. Open honest dialogue (with tact)  
  
l. Simple majority rules
+
l. Simple majority rules  
  
m. Agreement - to ensure success (from training)
+
m. Agreement - to ensure success (from training)  
  
n. Authentic and candid dialogue
+
n. Authentic and candid dialogue  
  
o. Honest - with tact
+
o. Honest - with tact  
  
p. Open to others - come to agreement
+
p. Open to others - come to agreement  
  
q. Make the decision and move on - or fix it and move on
+
q. Make the decision and move on - or fix it and move on  
  
r. Depersonalize and on board
+
r. Depersonalize and on board  
  
s. Participate, engage, share point of view 1X
+
s. Participate, engage, share point of view 1X  
  
t. Focus on and value time over story
+
t. Focus on and value time over story  
  
u. Informed, fast decisions
+
u. Informed, fast decisions  
  
v. Confidential
+
v. Confidential  
  
w. Take notes
+
w. Take notes  
  
x. Take responsibility
+
x. Take responsibility  
  
y. Volunteer, be willing
+
y. Volunteer, be willing  
  
z. Right to expect candor and openness
+
z. Right to expect candor and openness  
  
aa. Own it
+
aa. Own it  
  
bb. Be present
+
bb. Be present  
  
cc. Be on time (late + good story = on time)
+
cc. Be on time (late + good story = on time)  
  
dd. Outlook calendars up to date (for scheduling purposes)
+
dd. Outlook calendars up to date (for scheduling purposes)  
  
ee.&nbsp; Meetings will start on time.&nbsp; Team will wait no longer than 5 minutes for late arrivals. &lt;a href="User:Carrie Macfarlane"&gt;Macfarlane, Carrie Miyoshi&lt;/a&gt; 13:14, 30 June 2009 (UTC)
+
ee.&nbsp; Meetings will start on time.&nbsp; Team will wait no longer than 5 minutes for late arrivals. &lt;a href="User:Carrie Macfarlane"&gt;Macfarlane, Carrie Miyoshi&lt;/a&gt; 13:14, 30 June 2009 (UTC)  
  
<br>
+
<br>  
  
3.&nbsp; Vision Statements
+
3.&nbsp; Vision Statements  
  
<br>
+
<br>  
  
 
*Team will meet on Th Aug 25 to develop vision statement
 
*Team will meet on Th Aug 25 to develop vision statement
Line 539: Line 539:
 
*Team members will submit draft vision statements to blog (&lt;a href="http://blogs.middlebury.edu/liswebsite/"&gt;LIS Website Project&lt;/a&gt;)
 
*Team members will submit draft vision statements to blog (&lt;a href="http://blogs.middlebury.edu/liswebsite/"&gt;LIS Website Project&lt;/a&gt;)
  
<br>
+
<br>  
  
4.&nbsp; Future agenda items
+
4.&nbsp; Future agenda items  
  
<br>
+
<br>  
  
 
*Other potential team protocols were mentioned in conversation as team members arrived at the meeting.&nbsp; It was suggested that these potential protocols be brought up during the time allotted for discussion of team protocols.&nbsp; Because we needed to plan for drafting a vision statement, we didn't have time to discuss protocols.&nbsp; Therefore, perhaps we should plan to discuss team protocols in a future meeting.
 
*Other potential team protocols were mentioned in conversation as team members arrived at the meeting.&nbsp; It was suggested that these potential protocols be brought up during the time allotted for discussion of team protocols.&nbsp; Because we needed to plan for drafting a vision statement, we didn't have time to discuss protocols.&nbsp; Therefore, perhaps we should plan to discuss team protocols in a future meeting.
  
Other items on today's agenda for which we didn't have time (we had too many other important issues to resolve!):
+
Other items on today's agenda for which we didn't have time (we had too many other important issues to resolve!):  
  
<br>
+
<br>  
  
 
*Define measurements/metrics (10 min)What does success look like?What metric will define our success?
 
*Define measurements/metrics (10 min)What does success look like?What metric will define our success?
Line 557: Line 557:
 
*Action Plan to Achieve Key Deliverables (10 min)Tasks to be accomplished?Who is accountable?Delivery Time?
 
*Action Plan to Achieve Key Deliverables (10 min)Tasks to be accomplished?Who is accountable?Delivery Time?
  
<br>
+
<br>  
  
5.&nbsp; Action items
+
5.&nbsp; Action items  
  
<br>
+
<br>  
  
 
*Jim had some questions about roles and communication methods. He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
 
*Jim had some questions about roles and communication methods. He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
Line 575: Line 575:
 
*We will meet elsewhere from time-to-time (Voter East, Music Library, Armstrong Library)
 
*We will meet elsewhere from time-to-time (Voter East, Music Library, Armstrong Library)
  
&lt;a href="User:Carrie Macfarlane"&gt;Macfarlane, Carrie Miyoshi&lt;/a&gt; 19:48, 25 June 2009 (UTC)
+
&lt;a href="User:Carrie Macfarlane"&gt;Macfarlane, Carrie Miyoshi&lt;/a&gt; 19:48, 25 June 2009 (UTC)  
  
 
=== 2009:&nbsp; June 25  ===
 
=== 2009:&nbsp; June 25  ===
  
Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz
+
Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz  
  
1. Updates
+
1. Updates  
  
*Elin is updating Jeff R./Mary B. on team meeting highlights
+
*Elin is updating Jeff R./Mary B. on team meeting highlights  
 
*Elin will create a post for LISt blog about existence of the LIS Website Project Blog.
 
*Elin will create a post for LISt blog about existence of the LIS Website Project Blog.
  
2. Vision Statement Work
+
2. Vision Statement Work  
  
 
*Discussion of bringing out common themes or words, creating a tagline (subtitle) for the blog, tags/keywords, discussion of what the statement really should be
 
*Discussion of bringing out common themes or words, creating a tagline (subtitle) for the blog, tags/keywords, discussion of what the statement really should be
  
[asides]
+
[asides]  
  
*There’s a Wordle &lt;a href="http://www.wordle.net/gallery/wrdl/967852/web_team"&gt;diagram&lt;/a&gt; of our team vision statements on the blog; discussed what WORDLE is—what it represents and where it comes from: &lt;a href="http://www.wordle.net/"&gt;Wordle&lt;/a&gt; "Wordle is a toy for generating “word clouds” from text that you provide. The clouds give greater prominence to words that appear more frequently in the source text."
+
*There’s a Wordle &lt;a href="http://www.wordle.net/gallery/wrdl/967852/web_team"&gt;diagram&lt;/a&gt; of our team vision statements on the blog; discussed what WORDLE is—what it represents and where it comes from: &lt;a href="http://www.wordle.net/"&gt;Wordle&lt;/a&gt; "Wordle is a toy for generating “word clouds” from text that you provide. The clouds give greater prominence to words that appear more frequently in the source text."  
 
*Discussed scheduling a projector room for future meetings
 
*Discussed scheduling a projector room for future meetings
  
[back to vision statement discussion]
+
[back to vision statement discussion]  
  
*Discussed important components from each team members’ individual vision statements
+
*Discussed important components from each team members’ individual vision statements  
*Decided we’d wordsmith as a team, using 1 of the statements as a building block
+
*Decided we’d wordsmith as a team, using 1 of the statements as a building block  
*Made a list of key terms/strong elements
+
*Made a list of key terms/strong elements  
*Created a 3 sentence team vision (&lt;a href="https://mediawiki.middlebury.edu/wiki/LIS/LIS_Website#Team_Vision"&gt;above&lt;/a&gt; and on &lt;a href="http://blogs.middlebury.edu/liswebsite/2009/06/25/team-vision/"&gt;blog&lt;/a&gt;)
+
*Created a 3 sentence team vision (&lt;a href="https://mediawiki.middlebury.edu/wiki/LIS/LIS_Website#Team_Vision"&gt;above&lt;/a&gt; and on &lt;a href="http://blogs.middlebury.edu/liswebsite/2009/06/25/team-vision/"&gt;blog&lt;/a&gt;)  
*Liz suggests getting Robert Keren's feedback on this (and Jeff R.'s as well)
+
*Liz suggests getting Robert Keren's feedback on this (and Jeff R.'s as well)  
 
*Sense of accomplishment around the table!
 
*Sense of accomplishment around the table!
  
3. End of meeting discussion
+
3. End of meeting discussion  
  
*Jess will post &lt;a href="http://blogs.middlebury.edu/liswebsite/2009/06/25/team-vision/"&gt;vision&lt;/a&gt; to blog
+
*Jess will post &lt;a href="http://blogs.middlebury.edu/liswebsite/2009/06/25/team-vision/"&gt;vision&lt;/a&gt; to blog  
*Elin will create agenda for next meeting and distribute
+
*Elin will create agenda for next meeting and distribute  
*Team decides it is wise to meet twice a week for the forseeable future
+
*Team decides it is wise to meet twice a week for the forseeable future  
 
*Reminders to keep following/checking the blog and wiki! Experiment and explore. Check out the wiki &lt;a href="http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet"&gt;cheat sheet&lt;/a&gt; for help with editing!
 
*Reminders to keep following/checking the blog and wiki! Experiment and explore. Check out the wiki &lt;a href="http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet"&gt;cheat sheet&lt;/a&gt; for help with editing!
  
&lt;a href="User:Jessica Isler"&gt;Jess Isler&lt;/a&gt; 17:13, 25 June 2009 (UTC)
+
&lt;a href="User:Jessica Isler"&gt;Jess Isler&lt;/a&gt; 17:13, 25 June 2009 (UTC)  
  
 
=== 2009: July 1 <br>  ===
 
=== 2009: July 1 <br>  ===
  
Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz <br>
+
Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz <br>  
  
1) Updates
+
1) Updates  
  
*keep Elin &amp; team posted about absences via Outlook calendar, meeting schedule
+
*keep Elin &amp; team posted about absences via Outlook calendar, meeting schedule  
*there was a managers meeting on 6/26 at which the manager expectations as produced at the team training were discussed (vigorously). There was pretty good buy-in, with the understanding that things will evolve.
+
*there was a managers meeting on 6/26 at which the manager expectations as produced at the team training were discussed (vigorously). There was pretty good buy-in, with the understanding that things will evolve.  
*Elin met with Jeff &amp; showed him the blog &amp; wiki. Jeff clarified what is our charge &amp; what our deliverables. Suggested we make our vision shorter. Shorter form of vision as above unanimously approved.
+
*Elin met with Jeff &amp; showed him the blog &amp; wiki. Jeff clarified what is our charge &amp; what our deliverables. Suggested we make our vision shorter. Shorter form of vision as above unanimously approved.  
 
*Ian suggested adding a resources page to this wiki - done, see above.
 
*Ian suggested adding a resources page to this wiki - done, see above.
  
2) Protocols
+
2) Protocols  
  
After short discussion, updated protocols, as below in wiki were approved.
+
After short discussion, updated protocols, as below in wiki were approved.  
  
3) Define measurements/metrics. What does success look like? What metric will define our success?
+
3) Define measurements/metrics. What does success look like? What metric will define our success?  
  
Started discussion of this topic. Need for definitions of following:
+
Started discussion of this topic. Need for definitions of following:  
  
*scope of project
+
*scope of project  
*core requirements
+
*core requirements  
 
*metrics
 
*metrics
  
Ian listed metrics currently defined by the larger web makeover project.
+
Ian listed metrics currently defined by the larger web makeover project.  
  
4) Scope
+
4) Scope  
  
Started discussion of project scope. See details in this blog above.
+
Started discussion of project scope. See details in this blog above.  
  
5) For next meeting
+
5) For next meeting  
  
Note taking duties will rotate alphabetically. Jim's up next!
+
Note taking duties will rotate alphabetically. Jim's up next!  
  
Barbara learned a valuable lesson in entering these notes - there is a SAVE button at the bottom of the wiki edit screen if only one uses the correct (outer) scroll bar.
+
Barbara learned a valuable lesson in entering these notes - there is a SAVE button at the bottom of the wiki edit screen if only one uses the correct (outer) scroll bar.  
  
 
=== 2009: July 2  ===
 
=== 2009: July 2  ===
  
Present:&nbsp; Liz, Ian, Jim, Barbara, Jess, Elin, Carrie
+
Present:&nbsp; Liz, Ian, Jim, Barbara, Jess, Elin, Carrie  
  
<br>Scope discussion:
+
<br>Scope discussion:  
  
*&nbsp;&nbsp;&nbsp;&nbsp; Ian posted a very good list of items on our page the clearly itemizes our areas of focus when it comes to our project scope (see Scope section).&nbsp;
+
*&nbsp;&nbsp;&nbsp;&nbsp; Ian posted a very good list of items on our page the clearly itemizes our areas of focus when it comes to our project scope (see Scope section).&nbsp;  
 
*&nbsp;&nbsp;&nbsp;&nbsp; We discussed the proposed Scope list and we feel at this time that the proper items are listed.
 
*&nbsp;&nbsp;&nbsp;&nbsp; We discussed the proposed Scope list and we feel at this time that the proper items are listed.
  
Criteria discussion:
+
Criteria discussion:  
  
 
*&nbsp;&nbsp;&nbsp;&nbsp; We immediately started to discuss the criteria that will be used:
 
*&nbsp;&nbsp;&nbsp;&nbsp; We immediately started to discuss the criteria that will be used:
  
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; We will document everything which is internal to our effort&nbsp;on the Wiki; a clear and concise communication plan is&nbsp;needed;&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; We agreed to strive for a reduction in PDF and Doc objects which are currently embedded in many areas of the web site.&nbsp;&nbsp;An exclusion to&nbsp;the reduction&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of PDF&nbsp;objects would be in the preservation area only.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Reduce or eliminate external links -- Could you explain a little more here?&nbsp; I don't remember this point, sorry! [[User:Carrie Macfarlane|Macfarlane, Carrie Miyoshi]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; We must improve the Search engine<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;Promotion of the 'Blog' for the purpose of discussion and communication; internal as well as external communication.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Propose 1 blog opposed to 20+ blogs - consolidation; need better catogorization of content!&nbsp; One subscription to 'the' blog and then the user can navigate to desired area(s)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Make the tools and services easy to find and access!!<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Promote other tools and utilities - let user choose (appropriate tools only)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Simple, Intuitive, 3 click away interface<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Self-Service
+
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; We will document everything which is internal to our effort&nbsp;on the Wiki; a clear and concise communication plan is&nbsp;needed;&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; We agreed to strive for a reduction in PDF and Doc objects which are currently embedded in many areas of the web site.&nbsp;&nbsp;An exclusion to&nbsp;the reduction&nbsp;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of PDF&nbsp;objects would be in the preservation area only.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Reduce or eliminate external links -- Could you explain a little more here?&nbsp; I don't remember this point, sorry! [[User:Carrie Macfarlane|Macfarlane, Carrie Miyoshi]]<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; We must improve the Search engine<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;Promotion of the 'Blog' for the purpose of discussion and communication; internal as well as external communication.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Propose 1 blog opposed to 20+ blogs - consolidation; need better catogorization of content!&nbsp; One subscription to 'the' blog and then the user can navigate to desired area(s)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Make the tools and services easy to find and access!!<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Promote other tools and utilities - let user choose (appropriate tools only)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Simple, Intuitive, 3 click away interface<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; Self-Service  
  
Additional notes:
+
Additional notes:  
  
The team expressed questions and concerns regarding the Wiki and its ease of use.&nbsp; The team agreed that we are now emersing ourselves into the very areas we are charged to<br>clean-up or re-structure.&nbsp; We also came to the conclusion that whatever we put forward for a web site that it will be a bahavior change required for all user.&nbsp; Training and general <br>prepareness will be very important and that we will need to integrate these things along the way through this restructuring process.&nbsp; We also spoke about the importance of partnering <br>with other teams so that we can truly understand the requirements of the new LIS web site.
+
The team expressed questions and concerns regarding the Wiki and its ease of use.&nbsp; The team agreed that we are now emersing ourselves into the very areas we are charged to<br>clean-up or re-structure.&nbsp; We also came to the conclusion that whatever we put forward for a web site that it will be a bahavior change required for all user.&nbsp; Training and general <br>prepareness will be very important and that we will need to integrate these things along the way through this restructuring process.&nbsp; We also spoke about the importance of partnering <br>with other teams so that we can truly understand the requirements of the new LIS web site.  
  
<br>
+
<br>  
  
Next meeting:
+
Next meeting:  
  
*&nbsp;&nbsp; Ian will present the results of the Focus Group and survey results in our next meeting
+
*&nbsp;&nbsp; Ian will present the results of the Focus Group and survey results in our next meeting  
 
*&nbsp;&nbsp; Jim and Barbara will be on vacation for our next meeting
 
*&nbsp;&nbsp; Jim and Barbara will be on vacation for our next meeting
  
<br>
+
<br>  
  
 
=== 2009: July 8  ===
 
=== 2009: July 8  ===
  
Present: Elin, Jess, Ian, Carrie, Liz and Doreen
+
Present: Elin, Jess, Ian, Carrie, Liz and Doreen  
  
Announcements and Updates:
+
Announcements and Updates:  
  
*Joe Antonioli will meet tomorrow with the Web Makeover Design/IA group and will pass our progress along. We need to invite Joe to a meeting to find out where the LIS Webpage project fits into the larger Web Makeover project. Robert Keren, Communications and Bryan Carson should also be invited.
+
*Joe Antonioli will meet tomorrow with the Web Makeover Design/IA group and will pass our progress along. We need to invite Joe to a meeting to find out where the LIS Webpage project fits into the larger Web Makeover project. Robert Keren, Communications and Bryan Carson should also be invited.  
*Elin tweaked the wiki – planning stages are now included
+
*Elin tweaked the wiki – planning stages are now included  
*Best practices – when to use the wiki and blog. Wiki will be the resting place for documents and the blog will be used for discussion purposes.
+
*Best practices – when to use the wiki and blog. Wiki will be the resting place for documents and the blog will be used for discussion purposes.  
*There is a page limitation for the main wiki page. We should consider removing the minutes from the main page and create additional pages with links to the main page.
+
*There is a page limitation for the main wiki page. We should consider removing the minutes from the main page and create additional pages with links to the main page.  
*Including names on the wiki when commenting is useful.
+
*Including names on the wiki when commenting is useful.  
*Discussion tab- use for discussion
+
*Discussion tab- use for discussion  
 
*Midd-Google login issues – send Ian your Gmail address and Ian will forward over the “DIY Guide to Reviewing and Revising Web Site Navigation and Content” document to review
 
*Midd-Google login issues – send Ian your Gmail address and Ian will forward over the “DIY Guide to Reviewing and Revising Web Site Navigation and Content” document to review
  
Focus Group Analysis
+
Focus Group Analysis  
  
*Who was being surveyed? Mostly combined groups of staff and students and communications. There were not results from actual LIS focus groups. Jeff will send some documentation to the committee from the LIS focus groups.
+
*Who was being surveyed? Mostly combined groups of staff and students and communications. There were not results from actual LIS focus groups. Jeff will send some documentation to the committee from the LIS focus groups.  
*List on wiki things to have on the webpage. Are there any gaps? What do we do about adding tagging as a bullet point? Do we want to come up with our own vocabulary?
+
*List on wiki things to have on the webpage. Are there any gaps? What do we do about adding tagging as a bullet point? Do we want to come up with our own vocabulary?  
 
*The focus group survey identified the need for tagging, RSS feed….(Ian, please fill in others)
 
*The focus group survey identified the need for tagging, RSS feed….(Ian, please fill in others)
  
What do we need on the LIS webpage?
+
What do we need on the LIS webpage?  
  
*Consider: keeping pages up-to-date – figure out how to keep updated, author and date stamp markers. Include “How-to” features and reduce clicks
+
*Consider: keeping pages up-to-date – figure out how to keep updated, author and date stamp markers. Include “How-to” features and reduce clicks  
*Combine metrics with features on each page? Some can be combined, others need discussion
+
*Combine metrics with features on each page? Some can be combined, others need discussion  
*Add service status for service and system outages
+
*Add service status for service and system outages  
 
*Add Space, Computing and Conference link
 
*Add Space, Computing and Conference link
  
- Update of R25 will give us an opportunity to show a more comprehensive list on our page. Discuss with Bryan about showing room availability.
+
- Update of R25 will give us an opportunity to show a more comprehensive list on our page. Discuss with Bryan about showing room availability.  
  
 
*Formalize the rest of the list at next week’s meeting
 
*Formalize the rest of the list at next week’s meeting
  
Develop survey questions – add to tomorrow’s meeting
+
Develop survey questions – add to tomorrow’s meeting  
  
DIY workbook
+
DIY workbook  
  
 
*Feedback and answers
 
*Feedback and answers
  
(If you could only reach one particular audience with your website, who would it be?) LIS staff/faculty and students - staff – organizational communications and services - students – 8000 pages connected to the LIS website, mostly related to resource guides, subject guides and journals - students are primary, staff/faculty secondary - Alter the question to read: who are your primary users, not just one.
+
(If you could only reach one particular audience with your website, who would it be?) LIS staff/faculty and students - staff – organizational communications and services - students – 8000 pages connected to the LIS website, mostly related to resource guides, subject guides and journals - students are primary, staff/faculty secondary - Alter the question to read: who are your primary users, not just one.  
  
*Questions are designed to address much smaller areas than LIS. We can reformat these questions in the survey and re-segment by LIS department
+
*Questions are designed to address much smaller areas than LIS. We can reformat these questions in the survey and re-segment by LIS department  
 
*Advice on Mary’s questions? Add process for updating their content. How do you know when it needs to be changed? How important will these be 2 months from now? How to track questions they get on content? Is there a way to date stamp info? Does this info reside in additional documents or in other systems?
 
*Advice on Mary’s questions? Add process for updating their content. How do you know when it needs to be changed? How important will these be 2 months from now? How to track questions they get on content? Is there a way to date stamp info? Does this info reside in additional documents or in other systems?
  
We need to closely integrate our work with training and help facilitate better and more efficient workflow.
+
We need to closely integrate our work with training and help facilitate better and more efficient workflow.  
  
All CMS pages need to be re-written and are not transportable to Drupal.
+
All CMS pages need to be re-written and are not transportable to Drupal.  
  
We need to help people write content for web – writing style training. Writing style should be conversational.
+
We need to help people write content for web – writing style training. Writing style should be conversational.  
  
Action Items:
+
Action Items:  
  
*Cancel Joe A. for tomorrow’s meeting
+
*Cancel Joe A. for tomorrow’s meeting  
*Jim and Barbara will still be out tomorrow – go ahead with the survey questions
+
*Jim and Barbara will still be out tomorrow – go ahead with the survey questions  
*Add discussion of timeline and marketing plan to agenda
+
*Add discussion of timeline and marketing plan to agenda  
*Bring 5 survey questions to the meeting
+
*Bring 5 survey questions to the meeting  
 
*Jess will post assessment summary on blog.<br>
 
*Jess will post assessment summary on blog.<br>
  
 
=== 2009: July 9<br>  ===
 
=== 2009: July 9<br>  ===
  
Present: Carrie, Doreen, Elin, Ian, Jess (notes), Liz
+
Present: Carrie, Doreen, Elin, Ian, Jess (notes), Liz  
  
 
*Survey for LIS staff<br>
 
*Survey for LIS staff<br>
  
Ian created a key survey prior to meeting with members’ input to date<br>Link and login for survey is posted privately to blog<br>Discussion of what we want to get from the survey responses/hashing it all out<br>We cut it down to 11 questions from 18 or so! <br>Please look it over, make suggestions for edits, '''take the survey'''. Time yourself. Please inform the group of your timing. <br>
+
Ian created a key survey prior to meeting with members’ input to date<br>Link and login for survey is posted privately to blog<br>Discussion of what we want to get from the survey responses/hashing it all out<br>We cut it down to 11 questions from 18 or so! <br>Please look it over, make suggestions for edits, '''take the survey'''. Time yourself. Please inform the group of your timing. <br>  
  
 
*Target
 
*Target
  
Send out the survey on Monday 7/13
+
Send out the survey on Monday 7/13  
  
 
*Announcements/updates
 
*Announcements/updates
  
Email Elin if you have agenda items for next weeks' meeting, Wednesday, 7/ 15, and Thursday, 7/14
+
Email Elin if you have agenda items for next weeks' meeting, Wednesday, 7/ 15, and Thursday, 7/14  
  
Ian and Jess are out next week<br>
+
Ian and Jess are out next week<br>  
  
 
=== 2009: July 15  ===
 
=== 2009: July 15  ===
  
Present: Liz, Barbara, Jim, Carrie, Doreen (time-keeper), Elin (notes) The Donut Angel visited our meeting today (thanks, Liz!)
+
Present: Liz, Barbara, Jim, Carrie, Doreen (time-keeper), Elin (notes) The Donut Angel visited our meeting today (thanks, Liz!)  
  
Announcements etc. Wiki Edit Summary Notes - Elin requested that as a courtesy to each other we use the summary field when editing wiki pages - if edits can easily be summarized. It helps to know at a quick glance what has been edited when alerted to changes Meeting Notes - clarified alpha order of taking meeting notes - Elin took notes today - Liz is next - our first alpha cycle is nearly complete, thanks to Jess - who has done double duty.
+
Announcements etc. Wiki Edit Summary Notes - Elin requested that as a courtesy to each other we use the summary field when editing wiki pages - if edits can easily be summarized. It helps to know at a quick glance what has been edited when alerted to changes Meeting Notes - clarified alpha order of taking meeting notes - Elin took notes today - Liz is next - our first alpha cycle is nearly complete, thanks to Jess - who has done double duty.  
  
Rotate meeting moderation? Liz asked the group if we could share responsibility for meeting moderation. We decided that team members would moderate specific agenda items.
+
Rotate meeting moderation? Liz asked the group if we could share responsibility for meeting moderation. We decided that team members would moderate specific agenda items.  
  
Finalize survey - reviewed all Q’s and our experiences taking the survey. Time to take survey varied from 5 min to 15 min - depending on familiarity with survey Q’s Barbara will tweak a few settings, and adjust a few formats Then Liz will test the survey with a few Voter colleagues Barbara - can you let us know when the edits are complete - maybe the team could take the survey again? Lots of discussion about Q 6; did not want to edit this Q without feedback from Ian and the results of the Voter test We will finalize the survey and re-evaluate Q6 tomorrow with the goal of sending the survey out on Monday 7/20 We will send the survey out using the master url option and add ability to provide name to survey, giving LIS staff the option to be anon Do we want to send out to LIS student summer employees?
+
Finalize survey - reviewed all Q’s and our experiences taking the survey. Time to take survey varied from 5 min to 15 min - depending on familiarity with survey Q’s Barbara will tweak a few settings, and adjust a few formats Then Liz will test the survey with a few Voter colleagues Barbara - can you let us know when the edits are complete - maybe the team could take the survey again? Lots of discussion about Q 6; did not want to edit this Q without feedback from Ian and the results of the Voter test We will finalize the survey and re-evaluate Q6 tomorrow with the goal of sending the survey out on Monday 7/20 We will send the survey out using the master url option and add ability to provide name to survey, giving LIS staff the option to be anon Do we want to send out to LIS student summer employees?  
  
Tomorrow’s Agenda: Finalize survey (15 min - Barbara and Liz) Timeline (30 min - Carrie) (if possible - please review timeline section and timeline discussion on wiki prior to the meeting) Notes: Liz
+
Tomorrow’s Agenda: Finalize survey (15 min - Barbara and Liz) Timeline (30 min - Carrie) (if possible - please review timeline section and timeline discussion on wiki prior to the meeting) Notes: Liz  
  
 
=== 2009: July 16<br>  ===
 
=== 2009: July 16<br>  ===
  
Present: Carrie, Doreen, Elin, Jim, Barbara, Liz(notes)
+
Present: Carrie, Doreen, Elin, Jim, Barbara, Liz(notes)  
  
Survey for LIS staff(Moderator: Barbara)<br>
+
Survey for LIS staff(Moderator: Barbara)<br>  
  
*Reviewed results from survey prototype test and updated content and questions accordingly.
+
*Reviewed results from survey prototype test and updated content and questions accordingly.  
*Barbara to make updates to actual survey
+
*Barbara to make updates to actual survey  
*Liz to request password for LIS Web Team account.
+
*Liz to request password for LIS Web Team account.  
*Liz to send out survey to LIS Staff on Monday 7/20 from LIS Web Team account. Intro text to be used as email text.
+
*Liz to send out survey to LIS Staff on Monday 7/20 from LIS Web Team account. Intro text to be used as email text.  
 
*Completed surveys due by end of day Wednesday July 22nd
 
*Completed surveys due by end of day Wednesday July 22nd
  
<br>Project Timeline (Moderator: Carrie)
+
<br>Project Timeline (Moderator: Carrie)  
  
*Initial discussion of formalizing Project Timeline
+
*Initial discussion of formalizing Project Timeline  
*Questions about how workbook being developed will be used by Web Team
+
*Questions about how workbook being developed will be used by Web Team  
*Project Timeline discussion to be continued at next meeting
+
*Project Timeline discussion to be continued at next meeting  
 
*[[Talk:LIS Website#Project_Timeline|Project Timeline Discussion on Wiki]]
 
*[[Talk:LIS Website#Project_Timeline|Project Timeline Discussion on Wiki]]
  
<br>Tasks(before next meeting on 7/22):
+
<br>Tasks(before next meeting on 7/22):  
  
*Review [http://docs.google.com/View?id=dc5256j3_3mshzw5f2 Workbook]
+
*Review [http://docs.google.com/View?id=dc5256j3_3mshzw5f2 Workbook]  
 
*Review [https://mediawiki.middlebury.edu/wikis/LIS/images/5/53/Lis.txt|Current Sitemap]
 
*Review [https://mediawiki.middlebury.edu/wikis/LIS/images/5/53/Lis.txt|Current Sitemap]
  
<br>
+
<br>  
  
 
=== 2009: July 22  ===
 
=== 2009: July 22  ===
  
Location: LIB105; next weeks meetings will be in LIB221 Present: Jim, Elin, Liz, Barbara, Ian, Jessica, Carrie
+
Location: LIB105; next weeks meetings will be in LIB221 Present: Jim, Elin, Liz, Barbara, Ian, Jessica, Carrie  
  
- Discussion to meet with Jeff R. (Sponsor) &gt; Review what we have done so far &gt; Discuss issues people on team are having with time (availability of time) to participate in this effort
+
- Discussion to meet with Jeff R. (Sponsor) &gt; Review what we have done so far &gt; Discuss issues people on team are having with time (availability of time) to participate in this effort  
  
- Geneeral discussions: &gt; Barbara - are we producing? Are we moving forward on our mission? &gt; Liz - Are we following guidelines? How can we best stay on track? &gt; Team - should we have longer meetings? More meetings? We voted 'YES' on extending the meeting by creating more time at end of agenda to better wrap-up meeting, discuss new agenda topics, prep. for next meeting.
+
- Geneeral discussions: &gt; Barbara - are we producing? Are we moving forward on our mission? &gt; Liz - Are we following guidelines? How can we best stay on track? &gt; Team - should we have longer meetings? More meetings? We voted 'YES' on extending the meeting by creating more time at end of agenda to better wrap-up meeting, discuss new agenda topics, prep. for next meeting.  
  
- Survey update (Barbara/Liz) &gt; Approximately 50 people responded (today being last day people can contribute to the survey) &gt; Managers should send-out a reminder to complete the survey - that it is important to LIS and User Services! &gt; The actual results of this survey will be reviewed at next weeks meeting.
+
- Survey update (Barbara/Liz) &gt; Approximately 50 people responded (today being last day people can contribute to the survey) &gt; Managers should send-out a reminder to complete the survey - that it is important to LIS and User Services! &gt; The actual results of this survey will be reviewed at next weeks meeting.  
  
- Make-Over DIY Workbook discussion &gt; Team decided it was best to use this guide as a general guidance document. &gt; Barbara - "We are in a role of being a Project Manager - finding Project Managers - finding primary contacts." "We need representatives that can properly represnt our interests" "We need to start identifying people who will be able to help us." Ian - "We may want to delay [contacting people] our search until we better understand the overall situation."
+
- Make-Over DIY Workbook discussion &gt; Team decided it was best to use this guide as a general guidance document. &gt; Barbara - "We are in a role of being a Project Manager - finding Project Managers - finding primary contacts." "We need representatives that can properly represnt our interests" "We need to start identifying people who will be able to help us." Ian - "We may want to delay [contacting people] our search until we better understand the overall situation."  
  
- Statistics discussion &gt; What data sources can we use to derive useful information for our effort? &gt; Jim - HEAT - Although the incidents coming into the Help Desk are classified in many different ways it may be possible to query the HEAT database to find useful information. Jim will attempt to do this for next weeks meeting. &gt; Team - Information Desk - 3 different sources of information (could Nate Burt help us with this?) &gt; Ian - We have 2 years of Google analytics &gt; Elin - We have 5-6 months of blog information we might be able to sift through somehow... &gt; Ian - Information that could be derived from some of these sources are: 1. What are the top three pages used 2. What are the most common search terms 3. What is the click path to the resources &gt; Carrie - Can we ask Joe Antoneli if he can get us stats? &gt; Elin - The Reference Librarians have (in the past) gathered information through posing questions to customers and recording the answers.
+
- Statistics discussion &gt; What data sources can we use to derive useful information for our effort? &gt; Jim - HEAT - Although the incidents coming into the Help Desk are classified in many different ways it may be possible to query the HEAT database to find useful information. Jim will attempt to do this for next weeks meeting. &gt; Team - Information Desk - 3 different sources of information (could Nate Burt help us with this?) &gt; Ian - We have 2 years of Google analytics &gt; Elin - We have 5-6 months of blog information we might be able to sift through somehow... &gt; Ian - Information that could be derived from some of these sources are: 1. What are the top three pages used 2. What are the most common search terms 3. What is the click path to the resources &gt; Carrie - Can we ask Joe Antoneli if he can get us stats? &gt; Elin - The Reference Librarians have (in the past) gathered information through posing questions to customers and recording the answers.  
  
- Site Map &gt; How do we break it down? &gt; Liz - Should we break it down into a test file? Query the text file? &gt; Barbara - Big picture is needed to see what we need to do next... &gt; Carrie - We will need to divide-up the responsibilities for this breakdown &gt; ACTION ITEM: Ian will get Liz a list of everyone who has permissions in current CMS system.
+
- Site Map &gt; How do we break it down? &gt; Liz - Should we break it down into a test file? Query the text file? &gt; Barbara - Big picture is needed to see what we need to do next... &gt; Carrie - We will need to divide-up the responsibilities for this breakdown &gt; ACTION ITEM: Ian will get Liz a list of everyone who has permissions in current CMS system.  
  
- Timeline discussion: &gt; We continued to review our timeline; adjusting dates and milestones &gt; Finalize design criteria (post survey results) on Aug 5. &gt; Ian - we could breakout content to folder structure which mimics structure today. We can then transfer what makes sense to new templates. &gt; See Timeline for details.
+
- Timeline discussion: &gt; We continued to review our timeline; adjusting dates and milestones &gt; Finalize design criteria (post survey results) on Aug 5. &gt; Ian - we could breakout content to folder structure which mimics structure today. We can then transfer what makes sense to new templates. &gt; See Timeline for details.  
  
 
=== 2009: July 23  ===
 
=== 2009: July 23  ===
  
July 23
+
July 23  
  
Announcements - Elin invited Jeff Rehbach to view the LIS Web Team blog and wiki - Elin will be on vacation beginning Aug 5th (10-14 days)
+
Announcements - Elin invited Jeff Rehbach to view the LIS Web Team blog and wiki - Elin will be on vacation beginning Aug 5th (10-14 days)  
  
This meeting was dedicated to discussing and revising the team timeline.
+
This meeting was dedicated to discussing and revising the team timeline.  
  
It was noted that as new training dates are announced (contact manager), this dates need to be included in our timeline.
+
It was noted that as new training dates are announced (contact manager), this dates need to be included in our timeline.  
  
Agenda items for July 29th meeting
+
Agenda items for July 29th meeting  
  
- Survey results and other metric analysis (helpdesk stats, media, etc.) - Building coalition (who do we want to connect with) discussion
+
- Survey results and other metric analysis (helpdesk stats, media, etc.) - Building coalition (who do we want to connect with) discussion  
  
 
=== 2009: July 29  ===
 
=== 2009: July 29  ===
  
Present: Barbara (time), Carrie, Doreen, Elin, Ian, Jess (notes), Jim
+
Present: Barbara (time), Carrie, Doreen, Elin, Ian, Jess (notes), Jim  
  
Updates
+
Updates  
  
*Liz out; Elin &amp; Carrie out 8/5-8/18 will need to adjust timeline to account for absences
+
*Liz out; Elin &amp; Carrie out 8/5-8/18 will need to adjust timeline to account for absences  
*Moderators during Elin’s absence: Barbara, Ian and Liz (2) (let us know if you’d rather not, Liz!)
+
*Moderators during Elin’s absence: Barbara, Ian and Liz (2) (let us know if you’d rather not, Liz!)  
*We’re now posting agenda items on the Blog instead of via Outlook calendar appointment updates
+
*We’re now posting agenda items on the Blog instead of via Outlook calendar appointment updates  
 
*News from web makeover managers’ meeting: Barbara says they’re not being trained yet, but developing a test for the training. The timeline is fluid, the meetings next week will hopefully be focus groups for Drupal platform familiarization and basic content editing how-tos
 
*News from web makeover managers’ meeting: Barbara says they’re not being trained yet, but developing a test for the training. The timeline is fluid, the meetings next week will hopefully be focus groups for Drupal platform familiarization and basic content editing how-tos
  
Building coalition
+
Building coalition  
  
*A sense that we are not ready to bring in others until we have buy-in from Sponsor and ADs on our documents
+
*A sense that we are not ready to bring in others until we have buy-in from Sponsor and ADs on our documents  
 
*Once we have buy-in we’ll need to involve Bryan C., Mike L., Joe A., and Petar for internal LIS action items, and Robert Keren for all staff items, as well as Curricular Tech. group for the training/support of blogging
 
*Once we have buy-in we’ll need to involve Bryan C., Mike L., Joe A., and Petar for internal LIS action items, and Robert Keren for all staff items, as well as Curricular Tech. group for the training/support of blogging
  
Survey &amp; Metric analysis
+
Survey &amp; Metric analysis  
  
*General discussion of results
+
*General discussion of results  
*Jim will get stats from Nate
+
*Jim will get stats from Nate  
*Carrie has found not much of use from library stats (for our purposes at this point; may prove useful for future tasks), except EZproxy stats = 1/4 users off campus 3/4 on campus for subscription journal use
+
*Carrie has found not much of use from library stats (for our purposes at this point; may prove useful for future tasks), except EZproxy stats = 1/4 users off campus 3/4 on campus for subscription journal use  
*How will we gauge success using surveys &amp; metrics? Possibly send out our LIS staff survey again after new website launched
+
*How will we gauge success using surveys &amp; metrics? Possibly send out our LIS staff survey again after new website launched  
*Jess &amp; Barbara will work on a short student employee survey to gather some small bit of data from the student perspective (5 question goal!)
+
*Jess &amp; Barbara will work on a short student employee survey to gather some small bit of data from the student perspective (5 question goal!)  
*FYI: In current IA from White Whale, there is no LIS link from the College homepage, and no LIS link under Academics or Quick Links. Rather, a link to the Library from Academics and a link to the Helpdesk under Quick Links.
+
*FYI: In current IA from White Whale, there is no LIS link from the College homepage, and no LIS link under Academics or Quick Links. Rather, a link to the Library from Academics and a link to the Helpdesk under Quick Links.  
*Ian sent us the White Whale IA proposal (not final; open to revision)
+
*Ian sent us the White Whale IA proposal (not final; open to revision)  
 
*Wordpress upgrade likely before start of fall semester: new admin. interface, implications for training, etc.
 
*Wordpress upgrade likely before start of fall semester: new admin. interface, implications for training, etc.
  
To Do
+
To Do  
  
*By meeting tomorrow: Thoroughly read the Recommendations document in preparation; contribute content as needed, especially library section! (Ian will edit document tone for consistency.)
+
*By meeting tomorrow: Thoroughly read the Recommendations document in preparation; contribute content as needed, especially library section! (Ian will edit document tone for consistency.)  
*Please comment on the new College website design on the web redo [http://blogs.middlebury.edu/webredo/ blog]!
+
*Please comment on the new College website design on the web redo [http://blogs.middlebury.edu/webredo/ blog]!  
*Meeting ended 5 minutes early
+
*Meeting ended 5 minutes early  
 
*Future agenda item: contacting people who requested contact on survey<br>
 
*Future agenda item: contacting people who requested contact on survey<br>
  
 
=== 2009:&nbsp; July 30  ===
 
=== 2009:&nbsp; July 30  ===
  
Present: Jim, Ian, Elin, Barbara, Jess, Carrie (notes). Liz and Doreen are out.
+
Present: Jim, Ian, Elin, Barbara, Jess, Carrie (notes). Liz and Doreen are out.  
  
Announcements
+
Announcements  
  
 
*The wiki isn't good at handling simultaneous edits. If you edit a page at the same time as someone else, you may lose your edits when you hit 'save.' To avoid this, you may wish to copy your text to Notepad before you hit 'save.'
 
*The wiki isn't good at handling simultaneous edits. If you edit a page at the same time as someone else, you may lose your edits when you hit 'save.' To avoid this, you may wish to copy your text to Notepad before you hit 'save.'
  
Timeline
+
Timeline  
  
*Prior to today's meeting, a few of us made some minor edits to the timeline based on vacation dates and the new student survey.
+
*Prior to today's meeting, a few of us made some minor edits to the timeline based on vacation dates and the new student survey.  
 
*The group looked at the timeline during the meeting and decided the following: a) we're on target for "7/30 - Evaluate information architecture and corresponding list of LIS website contacts for current LIS site" because by "information architecture" we mean top-level IA, and that's what we started to discuss this week (the "recommendations" document). b) We will delete "8/5 - Finalize design criteria" because for our purposes, "design" is synonymous with "information architecture" -- and we're already evaluating the information architecture.
 
*The group looked at the timeline during the meeting and decided the following: a) we're on target for "7/30 - Evaluate information architecture and corresponding list of LIS website contacts for current LIS site" because by "information architecture" we mean top-level IA, and that's what we started to discuss this week (the "recommendations" document). b) We will delete "8/5 - Finalize design criteria" because for our purposes, "design" is synonymous with "information architecture" -- and we're already evaluating the information architecture.
  
Recommendations
+
Recommendations  
  
*Ian mapped out his recommendations on the white board. Jess will transcribe his drawing...somehow!
+
*Ian mapped out his recommendations on the white board. Jess will transcribe his drawing...somehow!  
*We started to discuss where hard-to-pin-down sections of the current LIS site would reside in this new configuration. Media services would go to the wiki, Segue would be on the LIS landing page and in other places too.
+
*We started to discuss where hard-to-pin-down sections of the current LIS site would reside in this new configuration. Media services would go to the wiki, Segue would be on the LIS landing page and in other places too.  
*We need an LIS website contact for media services. Since Adam Dobucki is leaving, Ethan Murphy might be a good candidate.
+
*We need an LIS website contact for media services. Since Adam Dobucki is leaving, Ethan Murphy might be a good candidate.  
*Mediawiki is not suitable for private internal documentation (eg, passwords). Departments might wish to use middfiles for this type of info.
+
*Mediawiki is not suitable for private internal documentation (eg, passwords). Departments might wish to use middfiles for this type of info.  
*We need an LIS website contact for blogs. Joe A would be a good candidate.
+
*We need an LIS website contact for blogs. Joe A would be a good candidate.  
*Some blog content perhaps wouldn't be interesting to the general public. There are various ways in which we might control which postings are shared on the main LIS blog.
+
*Some blog content perhaps wouldn't be interesting to the general public. There are various ways in which we might control which postings are shared on the main LIS blog.  
 
*Generally, it seems that there are tools to accommodate most if not all concerns that have been raised about the blog.
 
*Generally, it seems that there are tools to accommodate most if not all concerns that have been raised about the blog.
  
<br>Next week, the team will discuss LIS website contacts.<br>
+
<br>Next week, the team will discuss LIS website contacts.<br>  
  
 
=== 2009:&nbsp;August 05  ===
 
=== 2009:&nbsp;August 05  ===
  
Present: Jim, Ian (notes), Barbara, Jess, Doreen, Liz (moderator).
+
Present: Jim, Ian (notes), Barbara, Jess, Doreen, Liz (moderator).  
  
Announcements
+
Announcements  
  
*Ian will attend AD meeting tomorrow in place of Elin who is on vacation.
+
*Ian will attend AD meeting tomorrow in place of Elin who is on vacation.  
**One team member would like to let ADs know that some people on the team are having trouble devoting the time they'd like to the team because of other work responsibilities
+
**One team member would like to let ADs know that some people on the team are having trouble devoting the time they'd like to the team because of other work responsibilities  
**Pointed out that people will contribute to the team in different ways as project progresses
+
**Pointed out that people will contribute to the team in different ways as project progresses  
**Our timeline is very aggressive, but is required to be due to the nature of the project
+
**Our timeline is very aggressive, but is required to be due to the nature of the project  
*We will devote 10-15 minutes at tomorrow's meeting to go over topics to be discussed in AD meeting
+
*We will devote 10-15 minutes at tomorrow's meeting to go over topics to be discussed in AD meeting  
**Vision
+
**Vision  
**Creation of team blog &amp; wiki
+
**Creation of team blog &amp; wiki  
**Scope
+
**Scope  
**Timeline
+
**Timeline  
 
**Recommendations preview / meeting with Jeff on Aug. 20
 
**Recommendations preview / meeting with Jeff on Aug. 20
  
Contacts for Site Content Management
+
Contacts for Site Content Management  
  
*Start with top-level sites and work down
+
*Start with top-level sites and work down  
 
*Include everyone who expressed interest in the survey in being contacted
 
*Include everyone who expressed interest in the survey in being contacted
  
 
{| width="100%" border="1"
 
{| width="100%" border="1"
 
|-
 
|-
! Part of Site
+
! Part of Site  
! Team Contact
+
! Team Contact  
 
! External Contact
 
! External Contact
 
|-
 
|-
| Library
+
| Library  
| Carrie Macfarlane
+
| Carrie Macfarlane  
 
| Bryan Carson
 
| Bryan Carson
 
|-
 
|-
| Library Portal
+
| Library Portal  
| Barbara Merz
+
| Barbara Merz  
 
| Mike Lynch
 
| Mike Lynch
 
|-
 
|-
| MediaWiki/Helpdesk
+
| MediaWiki/Helpdesk  
| Jim Beauchemin
+
| Jim Beauchemin  
 
| Petar Mitrevski
 
| Petar Mitrevski
 
|-
 
|-
| About LIS/Landing Page
+
| About LIS/Landing Page  
| Doreen Bernier
+
| Doreen Bernier  
 
| Doreen Bernier*
 
| Doreen Bernier*
 
|-
 
|-
| Blogs
+
| Blogs  
| Ian McBride
+
| Ian McBride  
 
| Joe Antonioli
 
| Joe Antonioli
 
|-
 
|-
| Telephone Services
+
| Telephone Services  
| Liz Whitaker-Freitas
+
| Liz Whitaker-Freitas  
 
| Peggy Fischel
 
| Peggy Fischel
 
|-
 
|-
| Banner, etc. Documentation
+
| Banner, etc. Documentation  
| Liz Whitaker-Freitas
+
| Liz Whitaker-Freitas  
 
| Marcy Smith
 
| Marcy Smith
 
|-
 
|-
| Circulation Documentation
+
| Circulation Documentation  
| Elin Waagen
+
| Elin Waagen  
 
| Elin Waagen*
 
| Elin Waagen*
 
|-
 
|-
| Special Collections
+
| Special Collections  
| Jess Isler
+
| Jess Isler  
 
| Andy Wentink
 
| Andy Wentink
 
|-
 
|-
| Music Library
+
| Music Library  
| Jess Isler
+
| Jess Isler  
 
| Dan Frostman
 
| Dan Frostman
 
|-
 
|-
| Media Services
+
| Media Services  
| Jim Beauchemin
+
| Jim Beauchemin  
 
| Adam Dobucki
 
| Adam Dobucki
 
|-
 
|-
| Help(desk)
+
| Help(desk)  
| Jim Beauchemin
+
| Jim Beauchemin  
 
| Jim Beauchemin*
 
| Jim Beauchemin*
 
|-
 
|-
| Emergency
+
| Emergency  
| Doreen Bernier
+
| Doreen Bernier  
 
| Joseph Watson
 
| Joseph Watson
 
|-
 
|-
| Collection Management
+
| Collection Management  
| Barbara Merz
+
| Barbara Merz  
 
| Terry Simpkins
 
| Terry Simpkins
 
|-
 
|-
| Teaching/Learning
+
| Teaching/Learning  
| Ian McBride
+
| Ian McBride  
 
| Curricular Technology Team (Adam Franco)
 
| Curricular Technology Team (Adam Franco)
 
|}
 
|}
Line 972: Line 972:
 
=== 2009:&nbsp;August 06  ===
 
=== 2009:&nbsp;August 06  ===
  
Present: Ian, Barbara (moderator), Jess (notes), Doreen (time), Liz
+
Present: Ian, Barbara (moderator), Jess (notes), Doreen (time), Liz  
  
Announcements
+
Announcements  
  
 
*PM meetings: are all the same, only go to 1 of the 3
 
*PM meetings: are all the same, only go to 1 of the 3
  
Ian's run-through of topics for AD meeting this afternoon:
+
Ian's run-through of topics for AD meeting this afternoon:  
  
*Not discussing vision, since it was already announced
+
*Not discussing vision, since it was already announced  
*Showing Blog &amp; Wiki, encouraging ADs to follow and participate
+
*Showing Blog &amp; Wiki, encouraging ADs to follow and participate  
*Scope of project overview
+
*Scope of project overview  
*Timeline overview: sense that we're making good progress; some individual team members feel time-strapped and some difficulty balancing increased responsibilities
+
*Timeline overview: sense that we're making good progress; some individual team members feel time-strapped and some difficulty balancing increased responsibilities  
*Mentioning 8/20 meeting with Jeff to formally review and approve recommendations, but also giving a high-level overview of our recommendations as they currently exist
+
*Mentioning 8/20 meeting with Jeff to formally review and approve recommendations, but also giving a high-level overview of our recommendations as they currently exist  
 
*Ian will post brief overview following the meeting; will go over more thoroughly in our team meeting next week
 
*Ian will post brief overview following the meeting; will go over more thoroughly in our team meeting next week
  
Contacts -- how to proceed?
+
Contacts -- how to proceed?  
  
*We'll want to talk about different systems we'll be using and how best to use them, appropriate content, etc.
+
*We'll want to talk about different systems we'll be using and how best to use them, appropriate content, etc.  
*Dispelling concerns about extra work--much of what needs to happen is what you're already in charge of anyway
+
*Dispelling concerns about extra work--much of what needs to happen is what you're already in charge of anyway  
*Instilling the idea that we cannot do the work for you; we'll be moderating, guiding, and recommending, and we will also be supportive--if you need help doing the work we will help you get additional resources/people, but the work ultimately resides with you! And FYI, the MCMS will not be operational after January 4th.
+
*Instilling the idea that we cannot do the work for you; we'll be moderating, guiding, and recommending, and we will also be supportive--if you need help doing the work we will help you get additional resources/people, but the work ultimately resides with you! And FYI, the MCMS will not be operational after January 4th.  
 
*May use web redo PM workbooks if desired
 
*May use web redo PM workbooks if desired
  
Looking ahead:
+
Looking ahead:  
  
*Goal: meet with primary contacts by the end of August (will add to timeline)
+
*Goal: meet with primary contacts by the end of August (will add to timeline)  
 
*Send out reminder to student employees to fill out the survey (Friday morning?)
 
*Send out reminder to student employees to fill out the survey (Friday morning?)
  
Agenda for Wed 8/12:
+
Agenda for Wed 8/12:  
  
*Liz will moderate meeting
+
*Liz will moderate meeting  
*Ian will give an overview of the AD meeting and reactions
+
*Ian will give an overview of the AD meeting and reactions  
*More discussion of meetings with primary contacts/working with them if needed
+
*More discussion of meetings with primary contacts/working with them if needed  
*Finalizing recommendations on the wiki; we want buy-in by the meeting!
+
*Finalizing recommendations on the wiki; we want buy-in by the meeting!  
 
*Going over student employee survey feedback
 
*Going over student employee survey feedback
  
 
=== 2009:&nbsp;August 12  ===
 
=== 2009:&nbsp;August 12  ===
  
Present: Ian, Barbara, Jess (notes), Liz (moderator/time), Jim
+
Present: Ian, Barbara, Jess (notes), Liz (moderator/time), Jim  
  
Curricular Technology Team meeting recap-Ian
+
Curricular Technology Team meeting recap-Ian  
  
*Went to CT team meeting yesterday and explained 1 link on the LIS landing page for CT, and that CT team decides what happens when people click that link--what it leads to, etc. It can be a work in progress, since the final solution will not be decided by our launch date!
+
*Went to CT team meeting yesterday and explained 1 link on the LIS landing page for CT, and that CT team decides what happens when people click that link--what it leads to, etc. It can be a work in progress, since the final solution will not be decided by our launch date!  
*Discussed Google Analytics, various options with them, etc.
+
*Discussed Google Analytics, various options with them, etc.  
*A sense that the process with CT team does not need to be overly formal, but that if they need additional resources, we can help them get some
+
*A sense that the process with CT team does not need to be overly formal, but that if they need additional resources, we can help them get some  
 
*The team has been referred to our wiki and blog to see our docs about our overall approach/what we envision
 
*The team has been referred to our wiki and blog to see our docs about our overall approach/what we envision
  
AD meeting recap-Ian
+
AD meeting recap-Ian  
  
*Recap is on blog
+
*Recap is on blog  
*Further discussion of personnel challenges/need to build in some redundancy in work roles
+
*Further discussion of personnel challenges/need to build in some redundancy in work roles  
 
*Re: question about tracking system not being in line with our scope: Since it is not yet solved, we will keep it in mind but may fall within scope when it's decided
 
*Re: question about tracking system not being in line with our scope: Since it is not yet solved, we will keep it in mind but may fall within scope when it's decided
  
...This lead to a discussion of forms and a replacement for HEAT system
+
...This lead to a discussion of forms and a replacement for HEAT system  
  
*Discussion of disparate forms and tools for forms
+
*Discussion of disparate forms and tools for forms  
*Limitations of open source forms, Cforms preventing the Wordpress upgrade, some here want to custom build a self service forms creation tool, etc.
+
*Limitations of open source forms, Cforms preventing the Wordpress upgrade, some here want to custom build a self service forms creation tool, etc.  
*Helpdesk cares a lot about efficiencies and consistency across their forms
+
*Helpdesk cares a lot about efficiencies and consistency across their forms  
*Helpdesk is replacing HEAT this year
+
*Helpdesk is replacing HEAT this year  
*At this point, Jim strongly recommends Helpdesk moving to Parature, which has its own forms tool (Jim will send us all info. on this)
+
*At this point, Jim strongly recommends Helpdesk moving to Parature, which has its own forms tool (Jim will send us all info. on this)  
*Sense that we should bring up this issue in our meeting with Jeff on 8/20
+
*Sense that we should bring up this issue in our meeting with Jeff on 8/20  
*Decided that we will add a section in our Recommendations doc discussing the need to solve the problems relating to forms
+
*Decided that we will add a section in our Recommendations doc discussing the need to solve the problems relating to forms  
*Can we find a tool that encompasses all forms across campus (not just LIS)--public safety, facilities, library, helpdesk, etc.?
+
*Can we find a tool that encompasses all forms across campus (not just LIS)--public safety, facilities, library, helpdesk, etc.?  
*We will inventory current web forms, solicit feedback on what paper forms could be switched to web forms, and make recommendations for a central place(s) on the web for forms to be organized and accessed
+
*We will inventory current web forms, solicit feedback on what paper forms could be switched to web forms, and make recommendations for a central place(s) on the web for forms to be organized and accessed  
*Try out the Drupal add-on forms tool (Amherst has been running all their web forms on this for 3 years)
+
*Try out the Drupal add-on forms tool (Amherst has been running all their web forms on this for 3 years)  
*We will add a section on soliciting feedback on forms from our primary contacts in our version of the web redo workbooks
+
*We will add a section on soliciting feedback on forms from our primary contacts in our version of the web redo workbooks  
 
*General discussion of costs and benefits of open source options, in light of budget cuts and staff reductions
 
*General discussion of costs and benefits of open source options, in light of budget cuts and staff reductions
  
LIS student employee survey results
+
LIS student employee survey results  
  
*Brief overview of results
+
*Brief overview of results  
*Pretty much concurs with our results from the LIS staff survey
+
*Pretty much concurs with our results from the LIS staff survey  
 
*See more on the Blog
 
*See more on the Blog
  
Tomorrow: Finalizing our Recommendations document in preparation for our meeting with Jeff.
+
Tomorrow: Finalizing our Recommendations document in preparation for our meeting with Jeff.  
  
 
=== 2009:&nbsp;August 13  ===
 
=== 2009:&nbsp;August 13  ===
  
Present: Liz, Barbara, Ian, Doreen, Jess
+
Present: Liz, Barbara, Ian, Doreen, Jess  
  
Recs Doc editing
+
Recs Doc editing  
  
*Going over suggested changes
+
*Going over suggested changes  
*Barbara will add in paragraph on changing the LIS Wiki Main page sections to include gateways for different users
+
*Barbara will add in paragraph on changing the LIS Wiki Main page sections to include gateways for different users  
 
*Doreen emailing Elin for clarification about her question on workflows, for other input
 
*Doreen emailing Elin for clarification about her question on workflows, for other input
  
Other
+
Other  
  
 
*Discussion of whether having PCs internal and external as same person make sense or not; a sense that perhaps these should be different people
 
*Discussion of whether having PCs internal and external as same person make sense or not; a sense that perhaps these should be different people
  
August 19 agenda:
+
August 19 agenda:  
  
*Team approves Recs doc, prepares for meeting with Jeff R.
+
*Team approves Recs doc, prepares for meeting with Jeff R.  
 
*Possible further discussion of meetings with PCs<br>
 
*Possible further discussion of meetings with PCs<br>
  
 
=== 2009: August 19<br>  ===
 
=== 2009: August 19<br>  ===
  
Present: Elin, Carrie, Liz, Barbara, Ian, Jess <br>
+
Present: Elin, Carrie, Liz, Barbara, Ian, Jess <br>  
  
Plan for meeting tomorrow with Jeff re: Recommendations.
+
Plan for meeting tomorrow with Jeff re: Recommendations.  
  
*(See aganda on blog)
+
*(See aganda on blog)  
*To start with emphasizing certain points: Parature; overall design with wiki, blog, library page etc.; one blog concept
+
*To start with emphasizing certain points: Parature; overall design with wiki, blog, library page etc.; one blog concept  
*Ask Jeff about impact of changes at media services.
+
*Ask Jeff about impact of changes at media services.  
*In considering our design, issue of how LIS will be accessed from the larger college web is important. Carrie to add issue to recs. document.
+
*In considering our design, issue of how LIS will be accessed from the larger college web is important. Carrie to add issue to recs. document.  
*Make sure there's time for Jeff to be clear on what he's taking on to the ADs.
+
*Make sure there's time for Jeff to be clear on what he's taking on to the ADs.  
 
*Elin to send link to recs to Jeff again in preparation for meeting.
 
*Elin to send link to recs to Jeff again in preparation for meeting.
  
Other - future meeting needs to revisit Team contact / External contact assignments. E.g. AD team could be responsible for "About LIS" content.
+
Other - future meeting needs to revisit Team contact / External contact assignments. E.g. AD team could be responsible for "About LIS" content.  
  
 
=== 2009: August 26<br>  ===
 
=== 2009: August 26<br>  ===
  
Present: Elin, Carrie, Liz, Barbara, Ian, Jess, Doreen, Jim
+
Present: Elin, Carrie, Liz, Barbara, Ian, Jess, Doreen, Jim  
  
Announcements - Discussion
+
Announcements - Discussion  
  
Doreen reported a wish from Mike Roy for the LIS "one blog" concept to be implemented right away and used as the platform for LISt. Some proceedural &amp; technical issues make this timing difficult. Technical: development of blog template functionality; ability to import current blog content. Re:LISt other issues include interest &amp; work flow.
+
Doreen reported a wish from Mike Roy for the LIS "one blog" concept to be implemented right away and used as the platform for LISt. Some proceedural &amp; technical issues make this timing difficult. Technical: development of blog template functionality; ability to import current blog content. Re:LISt other issues include interest &amp; work flow.  
  
Q. Are we to meet with ADs tomorrow? A. Yes - likely at 2:30pm.<br>Tomorrow's 11:15am meeting canceled.
+
Q. Are we to meet with ADs tomorrow? A. Yes - likely at 2:30pm.<br>Tomorrow's 11:15am meeting canceled.  
  
Agenda item - "map out new IA" - agreed that the next step in this process is the IA meeting to approve (or not) the high level IA we propose.
+
Agenda item - "map out new IA" - agreed that the next step in this process is the IA meeting to approve (or not) the high level IA we propose.  
  
Contacts for site make over.<br>Changes:<br>Circ, external contact Kellam Ayres.<br>LIS landing page, external contact Jeff R.<br>Media, add Mary Backus as second ext. contact<br>Helpdesk wiki, Topher ext. contact in practice.
+
Contacts for site make over.<br>Changes:<br>Circ, external contact Kellam Ayres.<br>LIS landing page, external contact Jeff R.<br>Media, add Mary Backus as second ext. contact<br>Helpdesk wiki, Topher ext. contact in practice.  
  
Additions:<br>Digital Collections, int. Barbara, ext. Mike Lynch<br>Armstrong Library, int. Carrie, ext. Todd/Nancy
+
Additions:<br>Digital Collections, int. Barbara, ext. Mike Lynch<br>Armstrong Library, int. Carrie, ext. Todd/Nancy  
  
Note: ask Mike L. as part of above how slide library should be accessed from LIS.
+
Note: ask Mike L. as part of above how slide library should be accessed from LIS.  
  
Ian reported that WW thought linking to Subj Guides from academic pages was a good idea &amp; would add such to the suggested IA.
+
Ian reported that WW thought linking to Subj Guides from academic pages was a good idea &amp; would add such to the suggested IA.  
  
Forms.<br>Ian reported that cForms is officially going away. Replacement is the Wordform module in Drupal ([[Drupal.org/project/webform|drupal.org/project/webform]]). Form users will need to migrate their own forms - preferably by January but leeway given. In addition, Parature will be used if &amp; when available &amp; custom forms will be programmed on a project basis.<br>We all need to get lists of forms in current use on the LIS site from our external contacts to combine into a master list.
+
Forms.<br>Ian reported that cForms is officially going away. Replacement is the Wordform module in Drupal ([[Drupal.org/project/webform|drupal.org/project/webform]]). Form users will need to migrate their own forms - preferably by January but leeway given. In addition, Parature will be used if &amp; when available &amp; custom forms will be programmed on a project basis.<br>We all need to get lists of forms in current use on the LIS site from our external contacts to combine into a master list.  
  
Training.<br>Drupal training for us likely late September after a suitable template is constructed. Followed by training for external contacts in early October.
+
Training.<br>Drupal training for us likely late September after a suitable template is constructed. Followed by training for external contacts in early October.  
  
<br>
+
<br>  
  
 
=== 2009: September 2<br>  ===
 
=== 2009: September 2<br>  ===
  
Meeting notes 9/2/09
+
Meeting notes 9/2/09  
  
Present: Liz, Jim, Jess (moderator), Doreen, Carrie, Ian, Elin (notes)
+
Present: Liz, Jim, Jess (moderator), Doreen, Carrie, Ian, Elin (notes)  
  
Announcements etc.<br>Jess and Ian are following up with Joe A to adjust permissions for LIS to access the web makeover folder in middfiles<br>Elin - will be meeting with Fred and other team leaders on Wed afternoon. Anything to bring to the table? No major concerns noted; small change to protocols (shared team responsibility to moderate meetings), that things are going well, some concerns regarding scope creep/changes to scope <br>Liz – created a spreadsheet in middfiles that lists the entire LIS website URL’s; the team will review to ensure we identify all pages, and eliminate overlap<br>Carrie – question about WW/web makeover meeting invites; they are optional; open process to increase involvement and invite comments; round 3 of section landing pages meeting and Amherst profile demo scheduled for today<br>Carrie – advisory groups? Will add to recommendations doc
+
Announcements etc.<br>Jess and Ian are following up with Joe A to adjust permissions for LIS to access the web makeover folder in middfiles<br>Elin - will be meeting with Fred and other team leaders on Wed afternoon. Anything to bring to the table? No major concerns noted; small change to protocols (shared team responsibility to moderate meetings), that things are going well, some concerns regarding scope creep/changes to scope <br>Liz – created a spreadsheet in middfiles that lists the entire LIS website URL’s; the team will review to ensure we identify all pages, and eliminate overlap<br>Carrie – question about WW/web makeover meeting invites; they are optional; open process to increase involvement and invite comments; round 3 of section landing pages meeting and Amherst profile demo scheduled for today<br>Carrie – advisory groups? Will add to recommendations doc  
  
Meeting with AD’s<br>Summary and discussion<br>We have the green light on our recommendations - great work by the team!<br>No follow-up required for AD’s not present<br>Discussed pix issue – all LIS staff pix in directory not part of initial scope; top down instead of team driven; or a reflection of empowering team; hr/legal issues – cannot require; maybe phase 2; wait -impact of org/staffing changes; promote who we are; visual big bang; helpful to users; not included in initial survey; will ask MR to initiate this discussion and post on webteam blog (or LISt?); ask for comments and feedback; make arrangements if resources are needed to implement, one work area already did this easily and quickly on their own; will include or not based on feedback<br>One blog – some tech/design issues to be worked out but may be able to implement prior to go-live dates; maybe an interim solution/rolling schedule – open permissions, change address of LISt blog, change template (Nov.), tag for internal or external, set up categories<br>Support for landing page idea and concept that user does not need to know we are merged – sign of a mature merged org<br>Real-time status of everything - check out laundry.mit.edu for real-time status update model<br>General support for need for new ticketing platform capable of web forms, tracking, and self-service; Jim will edit Parature section of recommendations to be more generic since no decision has been made regarding platform recommendation<br>Questions about public v. private blogs, documentation etc. – we recommend encourage but not require<br>Question about user v. staff documentation<br>Hope for improved search functionality on LIS pages and catalog<br>Quick links from college page? Library – info products; collections and resources. Technology – user centric support<br>Next phase? Promote self-services<br>Blog post on LISt regarding recommendations – Elin will post by next deadline 9/11; invite LIS comments
+
Meeting with AD’s<br>Summary and discussion<br>We have the green light on our recommendations - great work by the team!<br>No follow-up required for AD’s not present<br>Discussed pix issue – all LIS staff pix in directory not part of initial scope; top down instead of team driven; or a reflection of empowering team; hr/legal issues – cannot require; maybe phase 2; wait -impact of org/staffing changes; promote who we are; visual big bang; helpful to users; not included in initial survey; will ask MR to initiate this discussion and post on webteam blog (or LISt?); ask for comments and feedback; make arrangements if resources are needed to implement, one work area already did this easily and quickly on their own; will include or not based on feedback<br>One blog – some tech/design issues to be worked out but may be able to implement prior to go-live dates; maybe an interim solution/rolling schedule – open permissions, change address of LISt blog, change template (Nov.), tag for internal or external, set up categories<br>Support for landing page idea and concept that user does not need to know we are merged – sign of a mature merged org<br>Real-time status of everything - check out laundry.mit.edu for real-time status update model<br>General support for need for new ticketing platform capable of web forms, tracking, and self-service; Jim will edit Parature section of recommendations to be more generic since no decision has been made regarding platform recommendation<br>Questions about public v. private blogs, documentation etc. – we recommend encourage but not require<br>Question about user v. staff documentation<br>Hope for improved search functionality on LIS pages and catalog<br>Quick links from college page? Library – info products; collections and resources. Technology – user centric support<br>Next phase? Promote self-services<br>Blog post on LISt regarding recommendations – Elin will post by next deadline 9/11; invite LIS comments  
  
Primary contacts stuff<br>Post questions that come up when meeting with LIS contacts on the wiki contacts page<br>May need to adjust CMS permissions to allow full access to contacts<br>OK to start building documentation on the LIS wiki – it will work better with more users <br>Need tips and tools to help new users; training?<br>Circ will add borrower documentation to the LIS wiki – not the separate Circ wiki<br>Dokutek? Link to external platform (Amherst created own eres system in Drupal – evaluate Midd eres in phase 200?)<br>Wiki Q’s:<br>Include screenshots? Yes<br>Photographs etc. from proprietary systems? No<br>Link to pdf’s instead<br>Recommend store vendor manuals in middfiles<br>Use discretion<br>Goal to decrease use of embedded objects on web and increase direct linkage<br>May be other solutions in the future for shared docs etc.
+
Primary contacts stuff<br>Post questions that come up when meeting with LIS contacts on the wiki contacts page<br>May need to adjust CMS permissions to allow full access to contacts<br>OK to start building documentation on the LIS wiki – it will work better with more users <br>Need tips and tools to help new users; training?<br>Circ will add borrower documentation to the LIS wiki – not the separate Circ wiki<br>Dokutek? Link to external platform (Amherst created own eres system in Drupal – evaluate Midd eres in phase 200?)<br>Wiki Q’s:<br>Include screenshots? Yes<br>Photographs etc. from proprietary systems? No<br>Link to pdf’s instead<br>Recommend store vendor manuals in middfiles<br>Use discretion<br>Goal to decrease use of embedded objects on web and increase direct linkage<br>May be other solutions in the future for shared docs etc.  
  
Timeline<br>Added Drupal training schedule – last week of Sept for PM’s; mid-Oct for all<br>When could we realistically expect to implement the one blog?<br>When will we meet with WW – Ian will follow up<br>Freeze dates for CMS
+
Timeline<br>Added Drupal training schedule – last week of Sept for PM’s; mid-Oct for all<br>When could we realistically expect to implement the one blog?<br>When will we meet with WW – Ian will follow up<br>Freeze dates for CMS  
  
Thursday agenda proposals<br>Spreadsheet of over 6,000 URL’s – how to manage existing url content<br>One LIS blog
+
Thursday agenda proposals<br>Spreadsheet of over 6,000 URL’s – how to manage existing url content<br>One LIS blog  
  
<br>
+
<br>  
  
 
=== 2009: September 3<br>  ===
 
=== 2009: September 3<br>  ===
  
Meeting notes 9/3/09
+
Meeting notes 9/3/09  
  
Present: Liz(notes, Jim, Barbara, Carrie, Ian, Elin (moderator), Jess
+
Present: Liz(notes, Jim, Barbara, Carrie, Ian, Elin (moderator), Jess  
  
<br>'''Announcements'''
+
<br>'''Announcements'''  
  
*Ian will inquire with Joe A re: Wiki Training
+
*Ian will inquire with Joe A re: Wiki Training  
*Elin provided summary of meeting with Fred
+
*Elin provided summary of meeting with Fred  
*Mike Roy would like to visit with the team. Date and time to be set after his blog posting re: photos
+
*Mike Roy would like to visit with the team. Date and time to be set after his blog posting re: photos  
 
*Carrie mentioned attending Amherst Profiles presentation. Team members to read Ian's post regarding this at [http://go/ian go/ian]. Ian indicated that it is not likely that we would implement this.
 
*Carrie mentioned attending Amherst Profiles presentation. Team members to read Ian's post regarding this at [http://go/ian go/ian]. Ian indicated that it is not likely that we would implement this.
  
<br>
+
<br>  
  
 
=== 2009: September 9<br>  ===
 
=== 2009: September 9<br>  ===
  
<br>'''LIS Website URLs'''
+
<br>'''LIS Website URLs'''  
  
 
*Went through URLs Inventory Spreadsheet and assigned URLs to Project Managers
 
*Went through URLs Inventory Spreadsheet and assigned URLs to Project Managers
  
Participants: Liz, Jim, Elin, Carrie, Jess, Barbara, Ian
+
Participants: Liz, Jim, Elin, Carrie, Jess, Barbara, Ian  
  
<br>
+
<br>  
  
Discussed One Blog
+
Discussed One Blog  
  
&gt; Discussion of categories was discussed (see Ian's blog)<br>&gt; Categories/break-outs discussed for Breadloaf<br>&gt; Carrie - should we have an all LIS category?<br>&gt; Internal versus external classification (where will things be displayed?)<br>&gt; example of internal = gate count in Main Library; external example = "suscribe to feeds"<br>&gt; Important distinction<br>&gt; Barbara - Discussion insued regarding internal LIS content - who should be reading it?<br>&gt; Internal may translate to private - is this what we want to send for a message?<br>&gt; External - "Did you know" category?<br>&gt; Ian - suggests removing "Internal" completely<br>&gt; Private blogs should not be in One Blog<br>&gt; Sensitive information must be protected<br>&gt; "One Blog" = public information<br>&gt; Document should be created to talk about use of blog and discuss private issues<br>&gt; We should create a new section on our Contacts Page for above document - Barbara will create section<br>&gt; Discussed Home pages - determined by category? Categoroes --&gt; Tagging (Should tag everything)<br>&gt; Ian - use conversion script to standardize tags<br>&gt; Carrie - Areas to be categorized? By function?<br>&gt; Rules for blogging discussed briefly<br>&gt; Should we have author-based feeds?
+
&gt; Discussion of categories was discussed (see Ian's blog)<br>&gt; Categories/break-outs discussed for Breadloaf<br>&gt; Carrie - should we have an all LIS category?<br>&gt; Internal versus external classification (where will things be displayed?)<br>&gt; example of internal = gate count in Main Library; external example = "suscribe to feeds"<br>&gt; Important distinction<br>&gt; Barbara - Discussion insued regarding internal LIS content - who should be reading it?<br>&gt; Internal may translate to private - is this what we want to send for a message?<br>&gt; External - "Did you know" category?<br>&gt; Ian - suggests removing "Internal" completely<br>&gt; Private blogs should not be in One Blog<br>&gt; Sensitive information must be protected<br>&gt; "One Blog" = public information<br>&gt; Document should be created to talk about use of blog and discuss private issues<br>&gt; We should create a new section on our Contacts Page for above document - Barbara will create section<br>&gt; Discussed Home pages - determined by category? Categoroes --&gt; Tagging (Should tag everything)<br>&gt; Ian - use conversion script to standardize tags<br>&gt; Carrie - Areas to be categorized? By function?<br>&gt; Rules for blogging discussed briefly<br>&gt; Should we have author-based feeds?  
  
NEXT STEPS:
+
NEXT STEPS:  
  
- Need function names (categories)<br>- Breadloaf: School of English and Writers Conference (use sub-categories?) Are there more?<br>- Eliminate Internal classification<br>- Use "Did you know" for all public postings (default)<br>
+
- Need function names (categories)<br>- Breadloaf: School of English and Writers Conference (use sub-categories?) Are there more?<br>- Eliminate Internal classification<br>- Use "Did you know" for all public postings (default)<br>  
  
<br>
+
<br>  
  
<br>
+
<br>  
  
 
=== 2009: September 16<br>  ===
 
=== 2009: September 16<br>  ===
  
Present: Liz, Jim, Jess, Carrie, Ian, Elin, Barbara<br>
+
Present: Liz, Jim, Jess, Carrie, Ian, Elin, Barbara<br>  
  
Met with Tonya Langford from White Whale. Issues discussed:<br>
+
Met with Tonya Langford from White Whale. Issues discussed:<br>  
  
 
*Quick links to LIS content from college homepage and elsewhere - how many? wording?<br>
 
*Quick links to LIS content from college homepage and elsewhere - how many? wording?<br>
  
T. thought several quick links would be appropriate. We should consider immediate needs of constituencies and their knowledge of LIS. Consider also how they'll get to what they need by searching - it won't always be possible to provide links. Searching could be "tuned" to give good answers to oddball searches.** We should come up with a list of recommended quick links **<br>
+
T. thought several quick links would be appropriate. We should consider immediate needs of constituencies and their knowledge of LIS. Consider also how they'll get to what they need by searching - it won't always be possible to provide links. Searching could be "tuned" to give good answers to oddball searches.** We should come up with a list of recommended quick links **<br>  
  
 
*Where other than homepage does LIS appear?<br>
 
*Where other than homepage does LIS appear?<br>
  
Academics page.<br>
+
Academics page.<br>  
  
Offices &amp; Services <br>
+
Offices &amp; Services <br>  
  
Constituency based areas for faculty / staff / students.<br>
+
Constituency based areas for faculty / staff / students.<br>  
  
we should look again to see how we're refered to in these areas. OK?<br>
+
we should look again to see how we're refered to in these areas. OK?<br>  
  
 
*Advice on wiki for documentation, answers to questions. <br>
 
*Advice on wiki for documentation, answers to questions. <br>
  
We discussed the implications of FAQs - would need data collection, entry, search mechanism etc. College wide FAQ database? Wiki and/or FAQs need energy to make work. Conclusion - wherever the answers are, the search mechanism should be on the main site with direct access to the answers. We already have "answers" but access to them is the problem - good tagging necessary. <br>
+
We discussed the implications of FAQs - would need data collection, entry, search mechanism etc. College wide FAQ database? Wiki and/or FAQs need energy to make work. Conclusion - wherever the answers are, the search mechanism should be on the main site with direct access to the answers. We already have "answers" but access to them is the problem - good tagging necessary. <br>  
  
 
*Where to put Music &amp; Armstrong library pages?
 
*Where to put Music &amp; Armstrong library pages?
  
They should live "under the library page". Side discussion - library or libraries page? What needs to be on their individual pages - hours, locations, explanation of what they provide. Possibly library page needs short text for external audience - including existance of branches!
+
They should live "under the library page". Side discussion - library or libraries page? What needs to be on their individual pages - hours, locations, explanation of what they provide. Possibly library page needs short text for external audience - including existance of branches!  
  
 
*How to include info on liaisons, advisory groups etc.?
 
*How to include info on liaisons, advisory groups etc.?
  
To be included in academic depts' resource pages - subject guides already proposed for inclusion there. Who should maintain info? - liaisons. Carrie to make up sample section(s).
+
To be included in academic depts' resource pages - subject guides already proposed for inclusion there. Who should maintain info? - liaisons. Carrie to make up sample section(s).  
  
<br>
+
<br>  
  
<br>
+
<br>  
  
 
=== 2009: September 17<br>  ===
 
=== 2009: September 17<br>  ===
  
Present: Barbara, Liz, Jim, Jess, Elin Carrie and Doreen
+
Present: Barbara, Liz, Jim, Jess, Elin Carrie and Doreen  
  
We held a lengthy discussion on College homepage Quick Links. 2 landing pages named Library and Technology. Should technology be included on a universal “support” page for the college site.
+
We held a lengthy discussion on College homepage Quick Links. 2 landing pages named Library and Technology. Should technology be included on a universal “support” page for the college site.  
  
Should telephone services be listed under telephone and offices. We need to review the analytics and discuss further.
+
Should telephone services be listed under telephone and offices. We need to review the analytics and discuss further.  
  
Blog vote – Elin has crafted text in the wiki for voting purposes. Terminology choices to make: • Use “function” names instead of area names for categories (ex, Circulation instead of User Serv.) Lower level functions can be listed as tags to assist in searchability
+
Blog vote – Elin has crafted text in the wiki for voting purposes. Terminology choices to make: • Use “function” names instead of area names for categories (ex, Circulation instead of User Serv.) Lower level functions can be listed as tags to assist in searchability  
  
Should we change the name? Should we make it public? Before we vote, we need to be sure of what the catagories are, before going forward.
+
Should we change the name? Should we make it public? Before we vote, we need to be sure of what the catagories are, before going forward.  
  
It was agreed that we move to the blog for continued discussion of terminology.
+
It was agreed that we move to the blog for continued discussion of terminology.  
  
Possible external names: • Bringing the Knowledge to You • Runed In • Good to Know • Need to Know • Essentials
+
Possible external names: • Bringing the Knowledge to You • Runed In • Good to Know • Need to Know • Essentials  
  
Jess will create post for voting
+
Jess will create post for voting  
  
Vote: we agreed to proceed with one blog after a new name has been decided.
+
Vote: we agreed to proceed with one blog after a new name has been decided.  
  
Next agenda – How to launch the blog.
+
Next agenda – How to launch the blog.  
  
<br> <br>
+
<br> <br>  
  
 
=== 2009: September 23<br>  ===
 
=== 2009: September 23<br>  ===
  
Present: Barbara, Carrie, Doreen, Elin, Ian, Jess, Jim
+
Present: Barbara, Carrie, Doreen, Elin, Ian, Jess, Jim  
  
One blog stuff confirmed:
+
One blog stuff confirmed:  
  
*The Blog name is Library and Information Services (the link is changed to .../LIS)
+
*The Blog name is Library and Information Services (the link is changed to .../LIS)  
*Blog tagline is Bringing knowledge to you
+
*Blog tagline is Bringing knowledge to you  
*Category default is (star) The Essentials
+
*Category default is (star) The Essentials  
*Categories will have parent/child hierarchy
+
*Categories will have parent/child hierarchy  
*Adding a tab in the one blog for How-To do things like subscribe, comment, post, etc.
+
*Adding a tab in the one blog for How-To do things like subscribe, comment, post, etc.  
*Ian made a list of things he'll do to change LISt blog and will move our blog over
+
*Ian made a list of things he'll do to change LISt blog and will move our blog over  
*Ian is making how-to for others to move their own blogs
+
*Ian is making how-to for others to move their own blogs  
*Should we have formal training right now for people who don't already use blogs for how to post, subscribe &amp; comment?
+
*Should we have formal training right now for people who don't already use blogs for how to post, subscribe &amp; comment?  
*We'll have a formal announcement: saying contact us if you want to learn the above, how to meet with or drop in with a media tutor or have a rep from the team/LIS meet with a workgroup, or pointing to the How-To section of the blog
+
*We'll have a formal announcement: saying contact us if you want to learn the above, how to meet with or drop in with a media tutor or have a rep from the team/LIS meet with a workgroup, or pointing to the How-To section of the blog  
 
*The announcement is going to be a draft blog post, so add and edit it as you see fit (Click save when you edit, NOT publish!)
 
*The announcement is going to be a draft blog post, so add and edit it as you see fit (Click save when you edit, NOT publish!)
  
Quick links:
+
Quick links:  
  
*Discussion of 2 vs. 3
+
*Discussion of 2 vs. 3  
 
*We voted and decided to have 2 links: Library and Technology support
 
*We voted and decided to have 2 links: Library and Technology support
  
LIS landing page:
+
LIS landing page:  
  
*Remember, it is one page (i.e. no subpages)
+
*Remember, it is one page (i.e. no subpages)  
*Doreen thinks we as a team have a stake in deciding how this page should look/be organized
+
*Doreen thinks we as a team have a stake in deciding how this page should look/be organized  
*Do we want the blog link or feed on this page to be external? Probably, but we'll decide later
+
*Do we want the blog link or feed on this page to be external? Probably, but we'll decide later  
 
*Doreen will share progress for LIS landing page thus far
 
*Doreen will share progress for LIS landing page thus far
  
Discussion of work with Primary Contacts:
+
Discussion of work with Primary Contacts:  
  
*A sense that we should meet to see where there are overlaps
+
*A sense that we should meet to see where there are overlaps  
*A sense that we should have a show and tell of what our PCs have been doing, that they're not "free agents" and we should make sure they're doing what they're supposed to be doing, even though the workbook is optional... (I didn't really understand this part of the discussion so feel free to edit if this isn't correct)
+
*A sense that we should have a show and tell of what our PCs have been doing, that they're not "free agents" and we should make sure they're doing what they're supposed to be doing, even though the workbook is optional... (I didn't really understand this part of the discussion so feel free to edit if this isn't correct)  
 
*More discussion on this tomorrow
 
*More discussion on this tomorrow
  
 
=== 2009:&nbsp; September 24<br>  ===
 
=== 2009:&nbsp; September 24<br>  ===
  
Present: Barbara, Carrie (notes), Elin, Ian, Jess, Liz
+
Present: Barbara, Carrie (notes), Elin, Ian, Jess, Liz  
  
New LIS one-blog has been launched!
+
New LIS one-blog has been launched!  
  
*Thanks to Ian.
+
*Thanks to Ian.  
*A few tweaks needed, a few training points noted. Bugs will be reported at chisel.middlebury.edu/pool. As yet, it's not possible to subscribe to a category.&nbsp; Barbara will add content from FAQS to "How do I..." section.&nbsp; Ian has asked Alex for links to screencasts and tutorials.&nbsp; "The Essentials" is the default category but a check-mark doesn't appear beside this category in a new post until the new post has been published.&nbsp; "Areas and Workgroups" category doesn't automatically assign a post to the categories below it in the hierarchy.&nbsp; "Feed" links provide URL for feed for just "The Essentials."&nbsp; Blog authors who wish have their content moved to the new one-blog should be alerted that content like "resources"&nbsp;and calendars will need a new home (won't be migrated).
+
*A few tweaks needed, a few training points noted. Bugs will be reported at chisel.middlebury.edu/pool. As yet, it's not possible to subscribe to a category.&nbsp; Barbara will add content from FAQS to "How do I..." section.&nbsp; Ian has asked Alex for links to screencasts and tutorials.&nbsp; "The Essentials" is the default category but a check-mark doesn't appear beside this category in a new post until the new post has been published.&nbsp; "Areas and Workgroups" category doesn't automatically assign a post to the categories below it in the hierarchy.&nbsp; "Feed" links provide URL for feed for just "The Essentials."&nbsp; Blog authors who wish have their content moved to the new one-blog should be alerted that content like "resources"&nbsp;and calendars will need a new home (won't be migrated).  
*To do:&nbsp; a) Elin started an announcement in the new blog. Others should contribute. Deadline is end of Friday 9/25. b) Announcement will be posted to blog. Elin will send it out via email too. c) Add content to "How do I..." and "Subscribe" pages.&nbsp; d) Publicity: Suggest to your workgroups that the topic be discussed. For example, it will be introduced in an all-ETI meeting next Tuesday.
+
*To do:&nbsp; a) Elin started an announcement in the new blog. Others should contribute. Deadline is end of Friday 9/25. b) Announcement will be posted to blog. Elin will send it out via email too. c) Add content to "How do I..." and "Subscribe" pages.&nbsp; d) Publicity: Suggest to your workgroups that the topic be discussed. For example, it will be introduced in an all-ETI meeting next Tuesday.  
 
*If other blog authors want to move their blogs, they can send us a request and Ian will migrate the content. (It's a complicated process.)
 
*If other blog authors want to move their blogs, they can send us a request and Ian will migrate the content. (It's a complicated process.)
  
Checking in with team about work with primary contacts
+
Checking in with team about work with primary contacts  
  
 
*After Oct 6 (workbook deadline), team members will bring to a team meeting: a) list of content considered "essential" by their primary contact/s, and b) ideas for where else on the LIS site links to their content should appear. Based on this info, the team will create an IA modeled after what White Whale has created for other sections of the College site.
 
*After Oct 6 (workbook deadline), team members will bring to a team meeting: a) list of content considered "essential" by their primary contact/s, and b) ideas for where else on the LIS site links to their content should appear. Based on this info, the team will create an IA modeled after what White Whale has created for other sections of the College site.
  
Wiki and blog training for primary contacts
+
Wiki and blog training for primary contacts  
  
 
*info forthcoming. (Ian's meeting with Joe was canceled.)
 
*info forthcoming. (Ian's meeting with Joe was canceled.)
  
Freeze date for changing the CMS:
+
Freeze date for changing the CMS:  
  
 
*December 1, 2009.
 
*December 1, 2009.
  
Elin will be out next week. Doreen won't be able to attend on Wednesday. Wednesday meeting canceled
+
Elin will be out next week. Doreen won't be able to attend on Wednesday. Wednesday meeting canceled  
  
 
*get out and show someone else how to blog!<br>
 
*get out and show someone else how to blog!<br>
Line 1,286: Line 1,286:
 
=== 2009:&nbsp; October 1<br>  ===
 
=== 2009:&nbsp; October 1<br>  ===
  
Present: Barbara, Carrie, Ian (notes), Jess, Doreen
+
Present: Barbara, Carrie, Ian (notes), Jess, Doreen  
  
 
*NERCOMP conference for Library websites at Amherst
 
*NERCOMP conference for Library websites at Amherst
  
Because of cost, it is probably not efficient to attend as a team.
+
Because of cost, it is probably not efficient to attend as a team.  
  
Who would like to go? Barbara (yes), Jess (perhaps), people outside of the team (perhaps). We should compile a list of people who would like to attend and then find out what budget is available for this event. Doreen will check interest based on people who fill out the travel request form.
+
Who would like to go? Barbara (yes), Jess (perhaps), people outside of the team (perhaps). We should compile a list of people who would like to attend and then find out what budget is available for this event. Doreen will check interest based on people who fill out the travel request form.  
  
 
*Drupal Training Sessions
 
*Drupal Training Sessions
  
Carrie, Jess, Liz, Elin and Ian attended various sessions.
+
Carrie, Jess, Liz, Elin and Ian attended various sessions.  
  
When will additional training be offered? There will be workshops/worksessions offered each day of the week beginning later in October. The schedule will be sent to the project managers list, which can then be forwarded to people in each area who are interested in attending by the project manager.
+
When will additional training be offered? There will be workshops/worksessions offered each day of the week beginning later in October. The schedule will be sent to the project managers list, which can then be forwarded to people in each area who are interested in attending by the project manager.  
  
 
*LIS Landing Page
 
*LIS Landing Page
  
Hours: these should be entered into Resource25 so that we can build dynamic feeds and calendars to show up on the LIS landing page. Each of the branches could be listed as a location with their hours of availability scheduled through that central calendaring application. Events and room schedules should also be part of this plan.
+
Hours: these should be entered into Resource25 so that we can build dynamic feeds and calendars to show up on the LIS landing page. Each of the branches could be listed as a location with their hours of availability scheduled through that central calendaring application. Events and room schedules should also be part of this plan.  
  
The landing page shouldn't just be a list of links. There should be headers for each of these sections and then text with links in it. It could end up looking and working something like this: http://www.mahalo.com/vermont
+
The landing page shouldn't just be a list of links. There should be headers for each of these sections and then text with links in it. It could end up looking and working something like this: http://www.mahalo.com/vermont  
  
Where should emergency information end up? There should be a link off of the LIS landing page for this information which will be hosted on a remote server to ensure that it can stay up during an emergency. We'll work with Public Safety to get this information updated.
+
Where should emergency information end up? There should be a link off of the LIS landing page for this information which will be hosted on a remote server to ensure that it can stay up during an emergency. We'll work with Public Safety to get this information updated.  
  
Where should Telephone Services be listed? There will be a link on the Offices &amp; Services page to the telecom site and there should also be a link on the LIS landing page right after the Helpdesk.
+
Where should Telephone Services be listed? There will be a link on the Offices &amp; Services page to the telecom site and there should also be a link on the LIS landing page right after the Helpdesk.  
  
Where should Curricular Technology be on the Staff Directory? Rather than listing out workgroups, we'll link directly to the LIS listings in the staff directory. There will be a link to the content generated by the Curricular Technology team on the LIS landing page.
+
Where should Curricular Technology be on the Staff Directory? Rather than listing out workgroups, we'll link directly to the LIS listings in the staff directory. There will be a link to the content generated by the Curricular Technology team on the LIS landing page.  
  
Should also list out the LIS liaisons and advisory groups on the landing page in the contact section along with Helpdesk, Circulation Desk, etc.
+
Should also list out the LIS liaisons and advisory groups on the landing page in the contact section along with Helpdesk, Circulation Desk, etc.  
  
Library Disambiguation page: this will only show up if you searched for "Library". All other paths to the library take you directly to the library page on the website. Links to Special Collections, Armstrong and the Music library will be shown on the Library page of the website.
+
Library Disambiguation page: this will only show up if you searched for "Library". All other paths to the library take you directly to the library page on the website. Links to Special Collections, Armstrong and the Music library will be shown on the Library page of the website.  
  
Newsletters and alert postings on the website: these should just be posts on the new LIS blog now, rather than produce these as separate areas.
+
Newsletters and alert postings on the website: these should just be posts on the new LIS blog now, rather than produce these as separate areas.  
  
System status: widget on the LIS landing page, but not something that takes up a lot of space.
+
System status: widget on the LIS landing page, but not something that takes up a lot of space.  
  
Ticket tracking: new version of HEAT up by end of year. Self-service and forms modules to be implemented ongoing into the new year.
+
Ticket tracking: new version of HEAT up by end of year. Self-service and forms modules to be implemented ongoing into the new year.  
  
We'll need to see what shows up in the dynamic search once the site goes live and then adjust our landing page.
+
We'll need to see what shows up in the dynamic search once the site goes live and then adjust our landing page.  
  
Will there be a specific template for the library? No, it will use the same once we're using for Offices.
+
Will there be a specific template for the library? No, it will use the same once we're using for Offices.  
  
 
*Permissions on LIS blog
 
*Permissions on LIS blog
  
Currently all people are administrators. We looked at roles and privileges. Admins can change themes, install plugins and import content. We voted on whether to leave these permissions in place or change all users to Editors. Voting record:
+
Currently all people are administrators. We looked at roles and privileges. Admins can change themes, install plugins and import content. We voted on whether to leave these permissions in place or change all users to Editors. Voting record:  
  
Doreen: change to Editors Barbara: change to Editors Jess: leave as Admins Jim: change to Editors Ian: leave as Admins Carrie: change to Editors
+
Doreen: change to Editors Barbara: change to Editors Jess: leave as Admins Jim: change to Editors Ian: leave as Admins Carrie: change to Editors  
  
 
*Link checker
 
*Link checker
  
This will be submitted to the web programming request field.
+
This will be submitted to the web programming request field.  
  
 
*Analytics
 
*Analytics
  
We'll be using Google Analytics to track site usage. Chris Norris will be offering training at a later date.
+
We'll be using Google Analytics to track site usage. Chris Norris will be offering training at a later date.  
  
 
*Wiki Workflow
 
*Wiki Workflow
  
Currently this is being managed by Jim. What does "manage workflow" mean in the context of this project? Is this going to be a document delivered to our site users? Is this in reference to a publishing workflow? This will likely be different for the library, since some of the information will be in subsplus or other systems. We'll discuss content workflow at a future meeting.
+
Currently this is being managed by Jim. What does "manage workflow" mean in the context of this project? Is this going to be a document delivered to our site users? Is this in reference to a publishing workflow? This will likely be different for the library, since some of the information will be in subsplus or other systems. We'll discuss content workflow at a future meeting.  
  
 
=== 2009:&nbsp; October 7<br>  ===
 
=== 2009:&nbsp; October 7<br>  ===
  
Present: Barbara, Carrie, Ian, Jess, Doreen, Elin, Jim, Liz
+
Present: Barbara, Carrie, Ian, Jess, Doreen, Elin, Jim, Liz  
  
General:<br>Discussed how to proceed about collection descriptions. Carrie will consult with potential authors of descritions. A collections page is possible.The team is responsible for big picture overview but not details of descriptions.
+
General:<br>Discussed how to proceed about collection descriptions. Carrie will consult with potential authors of descritions. A collections page is possible.The team is responsible for big picture overview but not details of descriptions.  
  
Carrie reminded us to look over the text she wrote for resource links from Academic Depts. and comment on the blog.
+
Carrie reminded us to look over the text she wrote for resource links from Academic Depts. and comment on the blog.  
  
NERCOMP meeting Nov 9th: "Usability in Libraries and Beyond". Funding is available for team members to attend. Barbara, Elin &amp; Jess are possible attendees.
+
NERCOMP meeting Nov 9th: "Usability in Libraries and Beyond". Funding is available for team members to attend. Barbara, Elin &amp; Jess are possible attendees.  
  
Mike Roy proposes adding review of LIS internal communications to our team charge. We will think about &amp; blog about this before responding to him.
+
Mike Roy proposes adding review of LIS internal communications to our team charge. We will think about &amp; blog about this before responding to him.  
  
Agenda: workflow<br>What does it mean in our timeline that we should "Design staff workflow for moving content." Conclusion - we should pull together best practices for dealing with various types of content on the web. E.g. pdf, Word docs, video, audio. Problems in some cases of large numbers of documents. Should they all be part of web or could they be archived some other way?<br>Some sources for best practices: go/webhelp, Communications office style guide, materials on Segue, Use of PDF in accessible documents in our resources section. Team members to add appropriate links to resources section of wiki.
+
Agenda: workflow<br>What does it mean in our timeline that we should "Design staff workflow for moving content." Conclusion - we should pull together best practices for dealing with various types of content on the web. E.g. pdf, Word docs, video, audio. Problems in some cases of large numbers of documents. Should they all be part of web or could they be archived some other way?<br>Some sources for best practices: go/webhelp, Communications office style guide, materials on Segue, Use of PDF in accessible documents in our resources section. Team members to add appropriate links to resources section of wiki.  
  
Actions - team members to pass info about Drupal workshops along to their primary contacts &amp; content editors.
+
Actions - team members to pass info about Drupal workshops along to their primary contacts &amp; content editors.  
  
Agenda for Oct 14th. Review progress of LIS in web analysis/design - considering essaential site features &amp; IA.<br><br>
+
Agenda for Oct 14th. Review progress of LIS in web analysis/design - considering essaential site features &amp; IA.<br><br>  
  
<br>
+
<br>  
  
 
=== 2009:&nbsp; October 14<br>  ===
 
=== 2009:&nbsp; October 14<br>  ===
  
Present; Doreen, Jim, Ian, Barbara (moderating), Liz, Jess, Carrie, Elin (notes)<br>
+
Present; Doreen, Jim, Ian, Barbara (moderating), Liz, Jess, Carrie, Elin (notes)<br>  
  
Feel free to edit/elaborate/clarify!
+
Feel free to edit/elaborate/clarify!  
  
Announcements: Barbara, Jess and Elin attending NERCOMP Nov 9th: "Usability in Libraries and Beyond"<br>
+
Announcements: Barbara, Jess and Elin attending NERCOMP Nov 9th: "Usability in Libraries and Beyond"<br>  
  
Remember to use shared folder in middfiles for easy access/sharing with team members and contacts (we merged 2 folders)<br>
+
Remember to use shared folder in middfiles for easy access/sharing with team members and contacts (we merged 2 folders)<br>  
  
Reviewed IA word doc - basically OK - need to make a few edits/tweaks<br>
+
Reviewed IA word doc - basically OK - need to make a few edits/tweaks<br>  
  
Landing page - Drupal see previous discussion/meeting notes above<br>
+
Landing page - Drupal see previous discussion/meeting notes above<br>  
  
LIS wiki - move documentation from CMS<br>
+
LIS wiki - move documentation from CMS<br>  
  
LIS blog - done! (in beta)
+
LIS blog - done! (in beta)  
  
Library site - lots of questions - what to do about collections; overlap issues; how do we proceed? Do we need sub meetings? How-to guides? <br>
+
Library site - lots of questions - what to do about collections; overlap issues; how do we proceed? Do we need sub meetings? How-to guides? <br>  
  
Need to review IA to identify overlap and gaps; avoid duplication and maintaining content in more than one place<br>
+
Need to review IA to identify overlap and gaps; avoid duplication and maintaining content in more than one place<br>  
  
Build a beautiful skeleton, with some flesh - that we can build on after the go live dates
+
Build a beautiful skeleton, with some flesh - that we can build on after the go live dates  
  
Keep user at forefront
+
Keep user at forefront  
  
Web team can determine IA as it pertains to the LIS website
+
Web team can determine IA as it pertains to the LIS website  
  
Jim reviewed buckets organized around concept of How do I; I&nbsp;have a problem; I&nbsp;have a request
+
Jim reviewed buckets organized around concept of How do I; I&nbsp;have a problem; I&nbsp;have a request  
  
Limit to 8 sub pages (8 links on left hand navigation)
+
Limit to 8 sub pages (8 links on left hand navigation)  
  
Offices and Servcies template will be similar to academic, but with distinctive features
+
Offices and Servcies template will be similar to academic, but with distinctive features  
  
We should recommend features - what we do/do not want - to Joe A
+
We should recommend features - what we do/do not want - to Joe A  
  
Sub level sites will have their own navigation
+
Sub level sites will have their own navigation  
  
Hours will be dynamically generated to our landing page
+
Hours will be dynamically generated to our landing page  
  
Look at: midd2.middlebury.edu/offices/technology
+
Look at: midd2.middlebury.edu/offices/technology  
  
Ian has set up permissions for the team
+
Ian has set up permissions for the team  
  
Create a FAQ data base? Aggregate content across site?
+
Create a FAQ data base? Aggregate content across site?  
  
Questions about duplication of effort and content
+
Questions about duplication of effort and content  
  
Workflow for content; identify existing content to avoid duplication (search; contact primary content provider)
+
Workflow for content; identify existing content to avoid duplication (search; contact primary content provider)  
  
Preference is to NOT&nbsp;upload exisiting PDF's into wiki, but could be workable temporary solution to time/skill contraint
+
Preference is to NOT&nbsp;upload exisiting PDF's into wiki, but could be workable temporary solution to time/skill contraint  
  
Agenda 10/15 - more IA
+
Agenda 10/15 - more IA  
  
<br>
+
<br>  
  
 
=== 2009:&nbsp; October 15<br>  ===
 
=== 2009:&nbsp; October 15<br>  ===
  
Present: Doreen, Jim, Barbara, Jess (moderating), Carrie, Elin, Liz(notes)<br>
+
Present: Doreen, Jim, Barbara, Jess (moderating), Carrie, Elin, Liz(notes)<br>  
  
Feel free to edit/elaborate/clarify!
+
Feel free to edit/elaborate/clarify!  
  
Announcements
+
Announcements  
  
 
*Jim: Linda K. developed a project plan for migrating all helpdesk documentation to wiki
 
*Jim: Linda K. developed a project plan for migrating all helpdesk documentation to wiki
Line 1,434: Line 1,434:
 
*Jess: Published How do I on LIS blog. To update it to include information on posting guidelines (privacy)
 
*Jess: Published How do I on LIS blog. To update it to include information on posting guidelines (privacy)
  
<br> Library IA Outline (Carrie)
+
<br> Library IA Outline (Carrie)  
  
*Review of 1st level IA for Library site
+
*Review of 1st level IA for Library site  
*Carrie will publish IA on blog for discussion
+
*Carrie will publish IA on blog for discussion  
 
*Usability testing will happen and IA may be revised as necessary
 
*Usability testing will happen and IA may be revised as necessary
  
<br> Curricular Technology
+
<br> Curricular Technology  
  
 
*IA document can be found here: \\middlebury.edu\middfiles\orgs\WebMakeover\LIS\Curricular%20%Technology
 
*IA document can be found here: \\middlebury.edu\middfiles\orgs\WebMakeover\LIS\Curricular%20%Technology
  
<br> Library Portal (Barbara)
+
<br> Library Portal (Barbara)  
  
 
*Review of 1st level IA
 
*Review of 1st level IA
  
<br> Digital Resources (Barbara)
+
<br> Digital Resources (Barbara)  
  
 
*Review of 1st level IA
 
*Review of 1st level IA
  
<br> Collection Management (Barbara)
+
<br> Collection Management (Barbara)  
  
 
*Where will they live? About?
 
*Where will they live? About?
  
<br> IA discussion to be continued…
+
<br> IA discussion to be continued…  
  
 
=== 2009: October 21  ===
 
=== 2009: October 21  ===
  
Present: Jim, Barbara, Jess, Carrie (notes), Elin, Liz, Ian<br>
+
Present: Jim, Barbara, Jess, Carrie (notes), Elin, Liz, Ian<br>  
  
<br>
+
<br>  
  
IA for library page <br>
+
IA for library page <br>  
  
*due next week. Include names and associated privileges.
+
*due next week. Include names and associated privileges.  
*IA for subpages of library page tbd but content creators
+
*IA for subpages of library page tbd but content creators  
*Is college directory enough? Do we need to create departmental directories too?
+
*Is college directory enough? Do we need to create departmental directories too?  
 
*Feedback: Put Hours in sidebar, not subpage.
 
*Feedback: Put Hours in sidebar, not subpage.
  
<br>
+
<br>  
  
Photos in new web site
+
Photos in new web site  
  
*Where will they be stored? Drupal has a resource manager
+
*Where will they be stored? Drupal has a resource manager  
 
*Ian sent message to project managers with middfiles location of images in current CMS resource manager
 
*Ian sent message to project managers with middfiles location of images in current CMS resource manager
  
*Staff can take own photos.&nbsp; Must be less than 10 mb. Drupal will resize automatically and provide choices for display.
+
*Staff can take own photos.&nbsp; Must be less than 10 mb. Drupal will resize automatically and provide choices for display.  
 
*Pam in Communications is sorting through College photos. We might be able to use some of those, too.
 
*Pam in Communications is sorting through College photos. We might be able to use some of those, too.
  
<br>
+
<br>  
  
Tech Support page<br>
+
Tech Support page<br>  
  
*Will be in Drupal, with links to tech support content in wiki etc.
+
*Will be in Drupal, with links to tech support content in wiki etc.  
*LIS landing page will link to the Drupal page
+
*LIS landing page will link to the Drupal page  
 
*Will probably have a smaller "footprint" because of "Search"
 
*Will probably have a smaller "footprint" because of "Search"
  
<br>
+
<br>  
  
Chart on Recommendations page should be revised to show that some sections will have transitional page (eg, Tech Support link won't go straight to wiki; it'll first go to a Drupal page)
+
Chart on Recommendations page should be revised to show that some sections will have transitional page (eg, Tech Support link won't go straight to wiki; it'll first go to a Drupal page)  
  
<br>
+
<br>  
  
Wiki will eventually get a "skin" or "template" so that it matches the rest of the Midd site
+
Wiki will eventually get a "skin" or "template" so that it matches the rest of the Midd site  
  
<br>
+
<br>  
  
Collection Management page
+
Collection Management page  
  
 
*Barbara will talk with CM about internal vs external content
 
*Barbara will talk with CM about internal vs external content
  
<br>
+
<br>  
  
Blog<br>
+
Blog<br>  
  
*Alex is making changes to the template
+
*Alex is making changes to the template  
*White Whale will give us a template
+
*White Whale will give us a template  
 
*LIS landing page will link to it and contain a feed too
 
*LIS landing page will link to it and contain a feed too
  
<br>
+
<br>  
  
Telephone Services
+
Telephone Services  
  
 
*Will have Drupal landing page with links to content that lives elsewhere including wiki
 
*Will have Drupal landing page with links to content that lives elsewhere including wiki
Line 1,519: Line 1,519:
 
*LIS landing page will link to Drupal landing page
 
*LIS landing page will link to Drupal landing page
  
<br>
+
<br>  
  
Circulation Services<br>
+
Circulation Services<br>  
  
*LIS wiki now has borrowing info
+
*LIS wiki now has borrowing info  
*LIS landing page and library page both will link to a Drupal landing page
+
*LIS landing page and library page both will link to a Drupal landing page  
*The current Circ wiki is primarily for internal use. It will remain separate from the LIS wiki for now, but might be merged eventually.
+
*The current Circ wiki is primarily for internal use. It will remain separate from the LIS wiki for now, but might be merged eventually.  
 
*Ian suggested a Circ landing page that directs people to the wikis and other circ pages. Alternatively, search queries could be set to go to circ's Drupal landing page.
 
*Ian suggested a Circ landing page that directs people to the wikis and other circ pages. Alternatively, search queries could be set to go to circ's Drupal landing page.
  
<br>
+
<br>  
  
Special Collections<br>
+
Special Collections<br>  
  
*Drupal page with content and links. Some content will feed to Collections page.
+
*Drupal page with content and links. Some content will feed to Collections page.  
*Library Collections should link to the SC page
+
*Library Collections should link to the SC page  
 
*Resources sections of relevant Academic Depts should link to the SC page.
 
*Resources sections of relevant Academic Depts should link to the SC page.
  
<br>
+
<br>  
  
College Archives<br>
+
College Archives<br>  
  
*Drupal page with content and links. Some content will feed to Collections page.
+
*Drupal page with content and links. Some content will feed to Collections page.  
*Offices &amp; Services—Alumni page should link to the CA page
+
*Offices &amp; Services—Alumni page should link to the CA page  
*Administration page should link to the CA page
+
*Administration page should link to the CA page  
*Advancement page should link to the CA page
+
*Advancement page should link to the CA page  
*Resources sections of relevant Academic Depts should link to the CA page
+
*Resources sections of relevant Academic Depts should link to the CA page  
 
*“Made by Midd” and “Library Collections” pages should link to the CA page<br>
 
*“Made by Midd” and “Library Collections” pages should link to the CA page<br>
  
 
=== 2009: October 22  ===
 
=== 2009: October 22  ===
  
Present: Jim, Barbara, Jess, Carrie, Elin, Liz, Ian
+
Present: Jim, Barbara, Jess, Carrie, Elin, Liz, Ian  
  
AI Discussion continued
+
AI Discussion continued  
  
Jess/Carrie/Barbara - Meet with Collection Management for further discussions
+
Jess/Carrie/Barbara - Meet with Collection Management for further discussions  
  
&gt; Workbook and Pages will need to sync-up &gt; Further structure discussions needed
+
&gt; Workbook and Pages will need to sync-up &gt; Further structure discussions needed  
  
Elin - Digital feed on recently acquired aquisitions to the Library should be on the Library Page.
+
Elin - Digital feed on recently acquired aquisitions to the Library should be on the Library Page.  
  
&gt; Carrie - should news item from the News Area be present in feed form on Lib Page as well? &gt; Ian - Might be problematic to pull News feed into Lib Page from Middcat (should go on wish list)
+
&gt; Carrie - should news item from the News Area be present in feed form on Lib Page as well? &gt; Ian - Might be problematic to pull News feed into Lib Page from Middcat (should go on wish list)  
  
Team - There will be Wiki training workshops for staff in November - Carrie made mention that there were a few edits by Topher on the Music Library site. Jim to update Topher on the big picture. - Digital Media Tutors will make house calls to assist with Wiki and other related media technologies - Two work sessions which are on-going for Drupal training (Joe A.). These training sessions will continue through November and December. - Review AI content posted in site folders on MIDDFILES
+
Team - There will be Wiki training workshops for staff in November - Carrie made mention that there were a few edits by Topher on the Music Library site. Jim to update Topher on the big picture. - Digital Media Tutors will make house calls to assist with Wiki and other related media technologies - Two work sessions which are on-going for Drupal training (Joe A.). These training sessions will continue through November and December. - Review AI content posted in site folders on MIDDFILES  
  
Carrie - Suggested merging News Letter into LIS Blog; also merge "Did you know" content - discussion insued; tabled for now.
+
Carrie - Suggested merging News Letter into LIS Blog; also merge "Did you know" content - discussion insued; tabled for now.  
  
Elin/Team - Brief discussion on "driving directions" - where to post thaat content? About section? Central Map section? - Printing support - there is overlap - where to post support content - how to consolidate? - Visiting people to the Library - should we have a seperate place on web for these folks? Jess mentioned an Intro Page of sorts for this purpose.
+
Elin/Team - Brief discussion on "driving directions" - where to post thaat content? About section? Central Map section? - Printing support - there is overlap - where to post support content - how to consolidate? - Visiting people to the Library - should we have a seperate place on web for these folks? Jess mentioned an Intro Page of sorts for this purpose.  
  
Next Week's Agenda:
+
Next Week's Agenda:  
  
- Contrinue Workflow discussions - Discuss protocols - Discuss when a good time to connect with AD's and Sponsor for updates.
+
- Contrinue Workflow discussions - Discuss protocols - Discuss when a good time to connect with AD's and Sponsor for updates.  
  
 
=== 2009: October 28  ===
 
=== 2009: October 28  ===
  
Present: Jim, Barbara, Jess, Carrie, Doreen, Liz, Ian
+
Present: Jim, Barbara, Jess, Carrie, Doreen, Liz, Ian  
  
Announcement - we will meet with Jeff R. next Wednesday, Nov 4th.<br>
+
Announcement - we will meet with Jeff R. next Wednesday, Nov 4th.<br>  
  
1) IA continued<br>
+
1) IA continued<br>  
  
In preparation for meeting next week, we looked over the AI materials we have on the wiki and identified items that should be added:<br>
+
In preparation for meeting next week, we looked over the AI materials we have on the wiki and identified items that should be added:<br>  
  
*Help desk IA - Jim<br>
+
*Help desk IA - Jim<br>  
*LIS landing page - Doreen<br>
+
*LIS landing page - Doreen<br>  
*List of identified cross-LIS content – e.g. LIS Links for Faculty, loaner equipment, request for film screening. Plus rules for ownership of same. - Barbara<br>
+
*List of identified cross-LIS content – e.g. LIS Links for Faculty, loaner equipment, request for film screening. Plus rules for ownership of same. - Barbara<br>  
 
*LIS WIKI section - Jess<br>
 
*LIS WIKI section - Jess<br>
  
2) LIS WIKI some details<br>
+
2) LIS WIKI some details<br>  
  
WIKI&nbsp;landing page to have links to audience specific subpages: faculty, staff, students, LIS staff, visitors. Ian has already put together an example of the Staff audience wiki page which gives us a good template to work with for the other pages: [https://mediawiki.middlebury.edu/wiki/LIS/Main_Page_Staff https://mediawiki.middlebury.edu/wiki/LIS/Main_Page_Staff]<br>
+
WIKI&nbsp;landing page to have links to audience specific subpages: faculty, staff, students, LIS staff, visitors. Ian has already put together an example of the Staff audience wiki page which gives us a good template to work with for the other pages: [https://mediawiki.middlebury.edu/wiki/LIS/Main_Page_Staff https://mediawiki.middlebury.edu/wiki/LIS/Main_Page_Staff]<br>  
  
Category pages will be created:<br>
+
Category pages will be created:<br>  
  
*General staff - Ian<br>
+
*General staff - Ian<br>  
*Faculty - Carrie<br>
+
*Faculty - Carrie<br>  
*LIS staff - Jess<br>
+
*LIS staff - Jess<br>  
 
*Students, visitors - Elin<br>
 
*Students, visitors - Elin<br>
  
3) Blog discussion.<br>
+
3) Blog discussion.<br>  
  
Blog features have already been added; e-mail plug-in, improved style. Decision has been made not to advertise or encourage private posts.<br>
+
Blog features have already been added; e-mail plug-in, improved style. Decision has been made not to advertise or encourage private posts.<br>  
  
Should "*The Essentials" remain the defauly category? Should it exist at all or be renamed? Discussion to continue on LIS blog itself: [http://blogs.middlebury.edu/lis/2009/10/28/blog-categories/ http://blogs.middlebury.edu/lis/2009/10/28/blog-categories/]<br>
+
Should "*The Essentials" remain the defauly category? Should it exist at all or be renamed? Discussion to continue on LIS blog itself: [http://blogs.middlebury.edu/lis/2009/10/28/blog-categories/ http://blogs.middlebury.edu/lis/2009/10/28/blog-categories/]<br>  
  
<br>
+
<br>  
  
 
=== 2009: October 29  ===
 
=== 2009: October 29  ===
  
Present: Barbara, Jess, Carrie, Doreen, Liz, Ian, Elin
+
Present: Barbara, Jess, Carrie, Doreen, Liz, Ian, Elin  
  
Announcements: Jeff Rehbach will come to next week’s meeting to discuss IA
+
Announcements: Jeff Rehbach will come to next week’s meeting to discuss IA  
  
Computer/printer alerts: We have no solution for adding computer availability and printer status as an alert at the present time. We will investigate and perhaps include this feature in a future phase of the webpage development. Currently tech alerts are setup for only web-based products. Elin will discuss with Jim and Brian
+
Computer/printer alerts: We have no solution for adding computer availability and printer status as an alert at the present time. We will investigate and perhaps include this feature in a future phase of the webpage development. Currently tech alerts are setup for only web-based products. Elin will discuss with Jim and Brian  
  
Permissions and workflow for LIS content:
+
Permissions and workflow for LIS content:  
  
Cross departmental on IA document. Review IA document, discuss and make a recommendation for what platform to choose.
+
Cross departmental on IA document. Review IA document, discuss and make a recommendation for what platform to choose.  
  
Add permission to pages and let people know
+
Add permission to pages and let people know  
  
Where should the recommendations be placed? Add recommendations to the guideline page for type of content (video, Word doc., audio, PDF, etc.) Create a page of guidelines for each. Jess will create pages and add content types. Everyone should contribute whey they know to this document.
+
Where should the recommendations be placed? Add recommendations to the guideline page for type of content (video, Word doc., audio, PDF, etc.) Create a page of guidelines for each. Jess will create pages and add content types. Everyone should contribute whey they know to this document.  
  
Develop technology uses and fill in our recommendations with links to content
+
Develop technology uses and fill in our recommendations with links to content  
  
Pull content from the Curricular Technology IA document
+
Pull content from the Curricular Technology IA document  
  
What is needed by 11/9? Is this being addressed by training? Clarify with Jeff We need to consolidate in one place, everything from our wiki page that is related to this deliverable. Elin will create preliminary response document on the wiki (i.e., style guides, blog permissions, best practices for video, audio, etc.) Whoever manages content in Subject Plus will need to access this document. Next week’s meeting with Jeff: Elin to remind Jeff of the link to the IA on the wiki. Carrie to update library IA.
+
What is needed by 11/9? Is this being addressed by training? Clarify with Jeff We need to consolidate in one place, everything from our wiki page that is related to this deliverable. Elin will create preliminary response document on the wiki (i.e., style guides, blog permissions, best practices for video, audio, etc.) Whoever manages content in Subject Plus will need to access this document. Next week’s meeting with Jeff: Elin to remind Jeff of the link to the IA on the wiki. Carrie to update library IA.  
  
Agenda items for the next meeting:
+
Agenda items for the next meeting:  
  
Essentials status – vote Lab/printer status (ask Jeff if we need to meet with ADs soon)
+
Essentials status – vote Lab/printer status (ask Jeff if we need to meet with ADs soon)  
  
 
=== 2009: November 4  ===
 
=== 2009: November 4  ===
  
Present: Doreen, Barbara, Carrie, Liz, Jess, Elin, Ian
+
Present: Doreen, Barbara, Carrie, Liz, Jess, Elin, Ian  
  
*Cancel Wed. before Thanskgiving meeting due to absences
+
*Cancel Wed. before Thanskgiving meeting due to absences  
*Jeff will probably come to our meeting tomorrow
+
*Jeff will probably come to our meeting tomorrow  
*Checkin--are there any concerns about team cohesion? No
+
*Checkin--are there any concerns about team cohesion? No  
*We need clarification on the workflow charge from Jeff
+
*We need clarification on the workflow charge from Jeff  
*Doreen's LIS SEARCH landing page image on the IA Doc (see prior meeting [https://mediawiki.middlebury.edu/wiki/LIS/LIS_Website#2009:.C2.A0_October_1 minutes] for more on this, including an example of how a search landing page can look)
+
*Doreen's LIS SEARCH landing page image on the IA Doc (see prior meeting [https://mediawiki.middlebury.edu/wiki/LIS/LIS_Website#2009:.C2.A0_October_1 minutes] for more on this, including an example of how a search landing page can look)  
**Doreen can be a primary contact for updating hours in R25 (with others as needed)
+
**Doreen can be a primary contact for updating hours in R25 (with others as needed)  
**Elin had questions about duplicating content re: spaces
+
**Elin had questions about duplicating content re: spaces  
**Discussion about tech gadgets: where should it be, what it actually means and encompasses, tabled for future discussion
+
**Discussion about tech gadgets: where should it be, what it actually means and encompasses, tabled for future discussion  
**About on Blog page will become not "About the blog" but rather "About LIS" and including org chart stuff, mission statement, et al... (this is because there are no subpages from the LIS Search Landing Page on which to put this content)
+
**About on Blog page will become not "About the blog" but rather "About LIS" and including org chart stuff, mission statement, et al... (this is because there are no subpages from the LIS Search Landing Page on which to put this content)  
 
**Change the News/Events Feed and Blog feeds to be 3 sections: Blog feed | Events/R25 | Search results
 
**Change the News/Events Feed and Blog feeds to be 3 sections: Blog feed | Events/R25 | Search results
  
*What are we asking Jeff tomorrow?
+
*What are we asking Jeff tomorrow?  
**Does he have questions about the IA Doc?
+
**Does he have questions about the IA Doc?  
**Clarification on the workflow charge
+
**Clarification on the workflow charge  
 
**Do we need to check in with the ADs?
 
**Do we need to check in with the ADs?
  
*Blog questions:
+
*Blog questions:  
**Ian's meeting with WW on Friday and will make sure their design can support Alex's Shadowbox theme and the widgets we currently use
+
**Ian's meeting with WW on Friday and will make sure their design can support Alex's Shadowbox theme and the widgets we currently use  
**Categories can have tags listed underneath (requested addition of this functionality)
+
**Categories can have tags listed underneath (requested addition of this functionality)  
**Clarification that yes, you can subscribe to tags. Go to the tag page and append "/feed"
+
**Clarification that yes, you can subscribe to tags. Go to the tag page and append "/feed"  
 
**More discussion about the blog on the blog... <br>
 
**More discussion about the blog on the blog... <br>
  
 
=== 2009: November 5  ===
 
=== 2009: November 5  ===
  
Present: Jim, Barbara, Carrie, Liz, Jess, Elin, Ian, Jeff
+
Present: Jim, Barbara, Carrie, Liz, Jess, Elin, Ian, Jeff  
  
Q. From team: What does the "workflow" task in our charge mean? A. Jeff - Defining who is authorized to manage/edit the parts of the LIS site. How is content to be reviewed and changed &amp; regular update encouraged?
+
Q. From team: What does the "workflow" task in our charge mean? A. Jeff - Defining who is authorized to manage/edit the parts of the LIS site. How is content to be reviewed and changed &amp; regular update encouraged?  
  
Points of discussion:
+
Points of discussion:  
  
List of tools (CT list) - this is more generally useful than just for faculty. Where could it be accessed? - Add to wiki.
+
List of tools (CT list) - this is more generally useful than just for faculty. Where could it be accessed? - Add to wiki.  
  
IA - redundancy of content? No - access to shared content from multiple locations.
+
IA - redundancy of content? No - access to shared content from multiple locations.  
  
LIS page - adjustments - add search results, have fewer separate feeds areas.
+
LIS page - adjustments - add search results, have fewer separate feeds areas.  
  
Do we need library disambiguation page? Or - do we send that search to the LIS page? Or add links on the library page to CTLR? Or leave until testing is possible (phase 2)?
+
Do we need library disambiguation page? Or - do we send that search to the LIS page? Or add links on the library page to CTLR? Or leave until testing is possible (phase 2)?  
  
Provision of a branding object for LIS?
+
Provision of a branding object for LIS?  
  
All pages + blog + Wiki need to link back to LIS&nbsp;page. Will this be in the left navigation panel?
+
All pages + blog + Wiki need to link back to LIS&nbsp;page. Will this be in the left navigation panel?  
  
Where should policies go? Wiki - with links from the faculty wiki start page.
+
Where should policies go? Wiki - with links from the faculty wiki start page.  
  
Where should "About LIS" go? Blog - inculding vision, org chart etc.
+
Where should "About LIS" go? Blog - inculding vision, org chart etc.  
  
To do:
+
To do:  
  
Blog entry pointing to IA on wiki (done)
+
Blog entry pointing to IA on wiki (done)  
  
Add emphasis that LIS&nbsp;landing page is a single page. (done)
+
Add emphasis that LIS&nbsp;landing page is a single page. (done)  
  
Jeff - encourage ADs to examine IA and respond quickly with any concerns. Team can make presentation to ADs as requested. No feedback = mandate to press ahead with build out.
+
Jeff - encourage ADs to examine IA and respond quickly with any concerns. Team can make presentation to ADs as requested. No feedback = mandate to press ahead with build out.  
  
 
=== 2009: November 11  ===
 
=== 2009: November 11  ===
  
Wed 11/11 Meeting Notes Present: Carrie, Jess, Ian, Jim, Barbara (moderating), Doreen, Elin (notes)
+
Wed 11/11 Meeting Notes Present: Carrie, Jess, Ian, Jim, Barbara (moderating), Doreen, Elin (notes)  
  
 
*Announcements:
 
*Announcements:
  
Congratulations to Liz and family on the birth of Mariana Luz&nbsp;:-)
+
Congratulations to Liz and family on the birth of Mariana Luz&nbsp;:-)  
  
Summary of NERCOMP Usability conference - see LIS blog for Jess' fabulous and articulate write-up; with links to presentations
+
Summary of NERCOMP Usability conference - see LIS blog for Jess' fabulous and articulate write-up; with links to presentations  
  
Brief report from Ian on WW meetings. Blogs - in addition to themes there may be sets of genres with 2-3 themes to simplify design interface; default colors/text interface. Search - going forward with w/current strategy. Recent presentation by WW available on Makeover blog
+
Brief report from Ian on WW meetings. Blogs - in addition to themes there may be sets of genres with 2-3 themes to simplify design interface; default colors/text interface. Search - going forward with w/current strategy. Recent presentation by WW available on Makeover blog  
  
Alex -will join us at next Wed meeting
+
Alex -will join us at next Wed meeting  
  
Jim will be out all next week
+
Jim will be out all next week  
  
Ian will be out next Thurs
+
Ian will be out next Thurs  
  
<br>
+
<br>  
  
*Demo of Office Theme by Ian - links to new design now avaialble on Midd2; OK&nbsp;to use carousel and juicebar
+
*Demo of Office Theme by Ian - links to new design now avaialble on Midd2; OK&nbsp;to use carousel and juicebar  
 
*Staff and dept profiles -include dept contact info at top to encourage customer contacting dept/workgroup for help, not individuals (who may be out that day) for better customer service/response to user needs and tracking of requests; team oversight?; some standardization across LIS?; let's not turn the new system into the old; indiv dept choice?; who maintains?; what about cross-dept stuff; what is best for the user point of view?; guidance for user to know who to contact for what
 
*Staff and dept profiles -include dept contact info at top to encourage customer contacting dept/workgroup for help, not individuals (who may be out that day) for better customer service/response to user needs and tracking of requests; team oversight?; some standardization across LIS?; let's not turn the new system into the old; indiv dept choice?; who maintains?; what about cross-dept stuff; what is best for the user point of view?; guidance for user to know who to contact for what
  
*About LIS - on blog
+
*About LIS - on blog  
*System alerts - identify list of systems to monitor&nbsp; - underway with Systems, Lynch, Norris etc.
+
*System alerts - identify list of systems to monitor&nbsp; - underway with Systems, Lynch, Norris etc.  
*Planned downtimes - post on blog? Ian will talk with Jeff
+
*Planned downtimes - post on blog? Ian will talk with Jeff  
*Find a PC - underway (update post-meeting - there may be some privacy issues with this functionality)
+
*Find a PC - underway (update post-meeting - there may be some privacy issues with this functionality)  
*Rooms, Carrels, lockers, labs... - work in progress with sub-groups
+
*Rooms, Carrels, lockers, labs... - work in progress with sub-groups  
*Usability - next phase...(NYPL using interesting on-going web-based usability system - Infomaki - open-source (in very early development)
+
*Usability - next phase...(NYPL using interesting on-going web-based usability system - Infomaki - open-source (in very early development)  
*Color - no interest in being the color police; College pages - will not dictate color despite WW recommendations; WW color schemes all have high standard of usability; same color scheme can help guide user through our pages
+
*Color - no interest in being the color police; College pages - will not dictate color despite WW recommendations; WW color schemes all have high standard of usability; same color scheme can help guide user through our pages  
*LIS Suggestions - what/where?
+
*LIS Suggestions - what/where?  
 
*Landing page and Library page intersects - Doreen and Carrie will connect
 
*Landing page and Library page intersects - Doreen and Carrie will connect
  
<br>
+
<br>  
  
Thursday meeting canceled
+
Thursday meeting canceled  
  
Next week - Alex, Mike/AD's; banner - unifying element; LIS suggestions; system downtime widgets
+
Next week - Alex, Mike/AD's; banner - unifying element; LIS suggestions; system downtime widgets  
  
 
=== 2009: November 18  ===
 
=== 2009: November 18  ===
  
In attendance: Elin, Barbara, Doreen, Jess, Carrie, Ian Notes: Ian Timekeeper: Barbara
+
In attendance: Elin, Barbara, Doreen, Jess, Carrie, Ian Notes: Ian Timekeeper: Barbara  
  
December 3 meeting to be from 10-11:30 AM with Sheila and Fred to review team progress. We will try to schedule LIB 145 for this, but the location is TBD at this time. LIB 221 likely won't fit all attendees.
+
December 3 meeting to be from 10-11:30 AM with Sheila and Fred to review team progress. We will try to schedule LIB 145 for this, but the location is TBD at this time. LIB 221 likely won't fit all attendees.  
  
Presentation this afternoon: pass out card and ask these questions
+
Presentation this afternoon: pass out card and ask these questions  
  
#Who is your user?
+
#Who is your user?  
 
#What have we missed?
 
#What have we missed?
  
While people fill out the cards we will give a quick presentation on
+
While people fill out the cards we will give a quick presentation on  
  
*Landing page
+
*Landing page  
*Library page
+
*Library page  
 
*Tech pages
 
*Tech pages
  
with questions after, time permitting
+
with questions after, time permitting  
  
Future agenda item: the LIS banner image for sites. What is possible? What should this be?
+
Future agenda item: the LIS banner image for sites. What is possible? What should this be?  
  
 
==== Meeting with Mike Roy and Jeff Rehbach  ====
 
==== Meeting with Mike Roy and Jeff Rehbach  ====
  
*We should get all the AD feeback and AD questions resolved now so that work on the site can be completed without interruption
+
*We should get all the AD feeback and AD questions resolved now so that work on the site can be completed without interruption  
*Do we have the resources we need for this?
+
*Do we have the resources we need for this?  
*LIS website 'sets the stage' for future web work and communications
+
*LIS website 'sets the stage' for future web work and communications  
 
*Do people understand the top level information architecture / separate Library and Tech sites.
 
*Do people understand the top level information architecture / separate Library and Tech sites.
  
Feedback from librarians: people want to know where particular items are in the new site, but are not questioning the overall LIS site IA
+
Feedback from librarians: people want to know where particular items are in the new site, but are not questioning the overall LIS site IA  
  
Useability
+
Useability  
  
*We want to collect feedback on item names, detailed item placement, etc. in IA
+
*We want to collect feedback on item names, detailed item placement, etc. in IA  
*We will conduct usability tests based on 'how would you find this particular resource'
+
*We will conduct usability tests based on 'how would you find this particular resource'  
*We might use the usability testing software shown at the usability conference attended by team members
+
*We might use the usability testing software shown at the usability conference attended by team members  
*We might set up a form to collect task suggestions from our community
+
*We might set up a form to collect task suggestions from our community  
*When would this testing occur? There are no students here in December, we want to have a well-formed site on which to conduct tests, and we want to collect information from an outside perspective.
+
*When would this testing occur? There are no students here in December, we want to have a well-formed site on which to conduct tests, and we want to collect information from an outside perspective.  
*We will likely want to do useability testing after the hard launch of the site.
+
*We will likely want to do useability testing after the hard launch of the site.  
 
*We will collect direct feedback from LIS staff at the presentation this afternoon.
 
*We will collect direct feedback from LIS staff at the presentation this afternoon.
  
What help do you need?
+
What help do you need?  
  
*Tech site
+
*Tech site  
**Difficult to allocate staff time for this section
+
**Difficult to allocate staff time for this section  
**Platforms for information have been defined by Jim and Mary
+
**Platforms for information have been defined by Jim and Mary  
**Site information architecture has been defined by Jim and Mary
+
**Site information architecture has been defined by Jim and Mary  
**Need to port content from current site
+
**Need to port content from current site  
 
**Recommending that we discontinue use of PDFs in the future, but acknowledging that using existing content is realistic for site launch
 
**Recommending that we discontinue use of PDFs in the future, but acknowledging that using existing content is realistic for site launch
  
Information Architecture suggestions
+
Information Architecture suggestions  
  
*LIS home page: should we change Library Help to Library Resources?
+
*LIS home page: should we change Library Help to Library Resources?  
*Dynamic search results: these will display popular pages from a search engine
+
*Dynamic search results: these will display popular pages from a search engine  
*LIS blog feed to LIS home page: should we filter what is displayed here? How?
+
*LIS blog feed to LIS home page: should we filter what is displayed here? How?  
*Should we move Reporting the the Tech Help section?
+
*Should we move Reporting the the Tech Help section?  
*About LIS: is the blog too informal for this content? How do we best represent this content?
+
*About LIS: is the blog too informal for this content? How do we best represent this content?  
*LIS home page: do we need subpages? What content would go on these pages?
+
*LIS home page: do we need subpages? What content would go on these pages?  
*Staff and department profiles
+
*Staff and department profiles  
**Do we need a set for LIS Administration? Where should these go?
+
**Do we need a set for LIS Administration? Where should these go?  
**Are we handling other profiles correctly?
+
**Are we handling other profiles correctly?  
 
*Should we link to 'About LIS' directly from the LIS home page
 
*Should we link to 'About LIS' directly from the LIS home page
  
 
==== Meeting with Alex about ShadowBox theme  ====
 
==== Meeting with Alex about ShadowBox theme  ====
  
LIS blog is the biggest blog using this theme
+
LIS blog is the biggest blog using this theme  
  
Alex likes the use of the seal in the O+S design, so it is used as the background. Also borrowed MiddTag styles and used for both tags and categories. Dotted underlines and highlights used for link styles.
+
Alex likes the use of the seal in the O+S design, so it is used as the background. Also borrowed MiddTag styles and used for both tags and categories. Dotted underlines and highlights used for link styles.  
  
Links to related sites in the top bar
+
Links to related sites in the top bar  
  
Added RSS feeds to the bottom bar with hover previews of the RSS item
+
Added RSS feeds to the bottom bar with hover previews of the RSS item  
  
Custom author pages for blog authors
+
Custom author pages for blog authors  
  
Related tags and categories on those pages. We want to emulate how delicious manages tagging. Ian will forward Alex some code for tags within categories.
+
Related tags and categories on those pages. We want to emulate how delicious manages tagging. Ian will forward Alex some code for tags within categories.  
  
Meta links: related services to be displayed at top and bottom.
+
Meta links: related services to be displayed at top and bottom.  
  
Gray text on sidebar header and comments to automatically adjust to contrasting colors
+
Gray text on sidebar header and comments to automatically adjust to contrasting colors  
  
Should we use ShadowBox for theme designs from White Whale? These can be applied across multiple systems. We probably need to remove the branding elements at the direction of College Communications.
+
Should we use ShadowBox for theme designs from White Whale? These can be applied across multiple systems. We probably need to remove the branding elements at the direction of College Communications.  
  
 
=== 2009: November 19  ===
 
=== 2009: November 19  ===
  
In attendance: Elin, Barbara, Doreen, Jess, Carrie Notes: Jess
+
In attendance: Elin, Barbara, Doreen, Jess, Carrie Notes: Jess  
  
*Review and discussion of feedback from staff meeting
+
*Review and discussion of feedback from staff meeting  
 
*Major points and responses, if we had them (NOT an exhaustive list):<br>
 
*Major points and responses, if we had them (NOT an exhaustive list):<br>
 
<pre>Policies (link to College handbook; departmental policies live on dept. pages)
 
<pre>Policies (link to College handbook; departmental policies live on dept. pages)
Line 1,833: Line 1,833:
 
LIS for Faculty add Digital Media Tutors (Will do)
 
LIS for Faculty add Digital Media Tutors (Will do)
 
Reserve links from Faculty pages
 
Reserve links from Faculty pages
</pre>
+
</pre>  
*We will clarify in the IA Doc that the Directory link from the LIS search landing page is to the LIS directory listing not the whole directory (apparently this wasn't clear)
+
*We will clarify in the IA Doc that the Directory link from the LIS search landing page is to the LIS directory listing not the whole directory (apparently this wasn't clear)  
*Make sure profiles are shared cross-departmentally
+
*Make sure profiles are shared cross-departmentally  
*We voted to create 1 subpage off of the LIS search landing page: About LIS (We'll add this to the IA doc).
+
*We voted to create 1 subpage off of the LIS search landing page: About LIS (We'll add this to the IA doc).  
*About LIS page contains:
+
*About LIS page contains:  
 
**
 
**
***slightly more fleshed-out description of LIS, probably including mission and values statements
+
***slightly more fleshed-out description of LIS, probably including mission and values statements  
***Administrative profiles (ONLY profiles for truly cross-LIS Administrative staff will go here, other profiles for staff go on departmental profile pages <u>if they so desire!</u>)
+
***Administrative profiles (ONLY profiles for truly cross-LIS Administrative staff will go here, other profiles for staff go on departmental profile pages <u>if they so desire!</u>)  
***Another link to the LIS-focused directory listing
+
***Another link to the LIS-focused directory listing  
 
***Annual reports
 
***Annual reports
  
Item for next meeting:
+
Item for next meeting:  
  
 
*Vote on whether or not to add 1 more subpage from the LIS Search landing page: LIS liaison profiles<br>
 
*Vote on whether or not to add 1 more subpage from the LIS Search landing page: LIS liaison profiles<br>
Line 1,850: Line 1,850:
 
=== 2009: December 3<br>  ===
 
=== 2009: December 3<br>  ===
  
Present:&nbsp; Ian, Jess, Jim, Barbara, Liz, Elin, Carrie (notes)<br>
+
Present:&nbsp; Ian, Jess, Jim, Barbara, Liz, Elin, Carrie (notes)<br>  
  
*How to monitor comments on all-LIS blog: For now, the committee will review comments waiting for approval informally. If that doesn’t work then we’ll consider appointing one or two people. Team:&nbsp; If you log in and see comments waiting, please approve.
+
*How to monitor comments on all-LIS blog: For now, the committee will review comments waiting for approval informally. If that doesn’t work then we’ll consider appointing one or two people. Team:&nbsp; If you log in and see comments waiting, please approve.  
*LIS landing page subpage for liaisons: We vote yes on including a liaison subpage. <br>
+
*LIS landing page subpage for liaisons: We vote yes on including a liaison subpage. <br>  
*LIS landing page: Change name of "Teaching and Learning" tab to “Curricular Technology”
+
*LIS landing page: Change name of "Teaching and Learning" tab to “Curricular Technology”  
*Add links to LIS blogs to all-LIS blog: We decided to add links to active blogs, eg, Circ blog. Could also include instructions on how to find other LIS blogs.
+
*Add links to LIS blogs to all-LIS blog: We decided to add links to active blogs, eg, Circ blog. Could also include instructions on how to find other LIS blogs.  
*Merge "Faculty Main Page" with "Staff Main Page" on wiki: Yes, go for it.
+
*Merge "Faculty Main Page" with "Staff Main Page" on wiki: Yes, go for it.  
*Middlebury College Libraries vs Middlebury Libraries: Table this decision for now.
+
*Middlebury College Libraries vs Middlebury Libraries: Table this decision for now.  
*Can individual posts in all-LIS&nbsp;blog display a search box? Elin will ask Alex.
+
*Can individual posts in all-LIS&nbsp;blog display a search box? Elin will ask Alex.  
*Will links we enter in Drupal break when we go live? We should enter the links as relative links, eg,&nbsp; /academics/lib/whatever. Web services will try to do search and replace for midd2 URLs but some links might be missed. "Go" links will be updated and should be fine.
+
*Will links we enter in Drupal break when we go live? We should enter the links as relative links, eg,&nbsp; /academics/lib/whatever. Web services will try to do search and replace for midd2 URLs but some links might be missed. "Go" links will be updated and should be fine.  
*Feedback from all-LIS meeting: Everyone should review the feedback on the wiki in the meeting notes from Nov 19. If there are topics to discuss, propose them as agenda items.&nbsp; Regarding the suggestion that we include a button/link called "Ask a Tech/Techie"&nbsp; – Jim will consider this. Concern that inconsistent terminology will cause confusion.
+
*Feedback from all-LIS meeting: Everyone should review the feedback on the wiki in the meeting notes from Nov 19. If there are topics to discuss, propose them as agenda items.&nbsp; Regarding the suggestion that we include a button/link called "Ask a Tech/Techie"&nbsp; – Jim will consider this. Concern that inconsistent terminology will cause confusion.  
*Banner for LIS pages: It will have text over an image. Communications will decide on the image; we can give input. It will say “Library and Information Services.” Ian will ask Pam and Tim for this.
+
*Banner for LIS pages: It will have text over an image. Communications will decide on the image; we can give input. It will say “Library and Information Services.” Ian will ask Pam and Tim for this.  
*Web team assessment: Date and time change is okay. 12/17, 9:30-12.<br>
+
*Web team assessment: Date and time change is okay. 12/17, 9:30-12.<br>  
*New timeline: Do we need to adjust our timeline? Deadline is extended but no other dates are influenced.<br>
+
*New timeline: Do we need to adjust our timeline? Deadline is extended but no other dates are influenced.<br>  
 
*<br>
 
*<br>
  
Usability testing: Ian will be working with Mary, Mike and Ben to create a usability framework. We should submit tasks for the testing. Copied from web redo blog:
+
Usability testing: Ian will be working with Mary, Mike and Ben to create a usability framework. We should submit tasks for the testing. Copied from web redo blog:  
<blockquote>We have created another simple form, where you would chose the constituent (or add one) and write a task that a visitor would need to complete. We’ll gather these and incorporate them into the user testing.&nbsp; <br>[http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA http://spreadsheets.google.com/viewform?hl=en&amp;formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA] </blockquote>
+
<blockquote>We have created another simple form, where you would chose the constituent (or add one) and write a task that a visitor would need to complete. We’ll gather these and incorporate them into the user testing.&nbsp; <br>[http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA http://spreadsheets.google.com/viewform?hl=en&amp;formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA] </blockquote>  
*Goals: We will work toward the 3 items from our charge.
+
*Goals: We will work toward the 3 items from our charge.  
 
*Cancel 12/23 meeting
 
*Cancel 12/23 meeting
  
 
=== 2009: December 10<br>  ===
 
=== 2009: December 10<br>  ===
  
Present:&nbsp; Ian, Jess, Jim, Barbara, Liz, Elin, Carrie, Doreen <br>
+
Present:&nbsp; Ian, Jess, Jim, Barbara, Liz, Elin, Carrie, Doreen <br>  
  
Announcements
+
Announcements  
  
Ian: take a look at go/draftblog (can subsitute 02 - 06 for the default 01 in the URL) to see progress by Alex on the blog features.
+
Ian: take a look at go/draftblog (can subsitute 02 - 06 for the default 01 in the URL) to see progress by Alex on the blog features.  
  
Jess: should new categories being added to LIS blog be converted by us to tags? Decision - yes. Advice to that effect to be added to instructions on the blog.
+
Jess: should new categories being added to LIS blog be converted by us to tags? Decision - yes. Advice to that effect to be added to instructions on the blog.  
  
Elin: handed out draft of the "Goal Setting Process - Web Tea" document. Team members to comment by 5pm Friday 11th.
+
Elin: handed out draft of the "Goal Setting Process - Web Tea" document. Team members to comment by 5pm Friday 11th.  
  
Items
+
Items  
  
<br>
+
<br>  
  
1. Banner images for LIS&nbsp;site.&nbsp;After some discussion, we decided that we wanted to use different images for each of the major areas of the LIS site and assigned the banner images to the sites as follows:
+
1. Banner images for LIS&nbsp;site.&nbsp;After some discussion, we decided that we wanted to use different images for each of the major areas of the LIS site and assigned the banner images to the sites as follows:  
  
 
##1: Helpdesk, Administrative Systems (i.e. Banner, Hyperion) documentation, and Telephone Services (reflection of Old Chapel) <br>#2: Library (looking in - reading room)<br>#3: LIS Home Page (wall, sky, window)<br>#4: Curricular Technology (birds-eye view - main library atrium)<br>
 
##1: Helpdesk, Administrative Systems (i.e. Banner, Hyperion) documentation, and Telephone Services (reflection of Old Chapel) <br>#2: Library (looking in - reading room)<br>#3: LIS Home Page (wall, sky, window)<br>#4: Curricular Technology (birds-eye view - main library atrium)<br>
  
Images can be changed later - different images created etc.
+
Images can be changed later - different images created etc.  
  
<br>
+
<br>  
  
2. Content build. There needs to be a static library &amp; helpdesk hours page. Elin will ask Dan for help in creation of a page for this, with links from several places.
+
2. Content build. There needs to be a static library &amp; helpdesk hours page. Elin will ask Dan for help in creation of a page for this, with links from several places.  
  
3. Forms. Currently on a hidden page for ease of displaying all forms together. Alternative - each could have own page and be shared.
+
3. Forms. Currently on a hidden page for ease of displaying all forms together. Alternative - each could have own page and be shared.  
  
4. Need for WIKI&nbsp;workshop. Currently only Joe could provide this on short notice. Ian will follow up on some way to get a workshop at least for LIS&nbsp;staff who need it.
+
4. Need for WIKI&nbsp;workshop. Currently only Joe could provide this on short notice. Ian will follow up on some way to get a workshop at least for LIS&nbsp;staff who need it.  
  
5. List of systems being monitored. Liz is expecting this info from Chris. Also, how to communicate planned down times to the community? Blog? Ian will enquire of Jeff, Rick.
+
5. List of systems being monitored. Liz is expecting this info from Chris. Also, how to communicate planned down times to the community? Blog? Ian will enquire of Jeff, Rick.  
  
 
=== 2010: January 6th<br>  ===
 
=== 2010: January 6th<br>  ===
  
Present:&nbsp; Ian, Jess, Jim, Barbara, Liz, Elin, Carrie, Doreen <br>
+
Present:&nbsp; Ian, Jess, Jim, Barbara, Liz, Elin, Carrie, Doreen <br>  
  
Announcements
+
Announcements  
  
Ian: IE6 &amp; IE7 stylesheets are up for the website.<br>
+
Ian: IE6 &amp; IE7 stylesheets are up for the website.<br>  
  
Elin: met with managers - LIS communication under discussion. Blog generally approved of for internal communication but still issues of buy-in. Team members - e-mail Elin with comments to share with managers re: communication.
+
Elin: met with managers - LIS communication under discussion. Blog generally approved of for internal communication but still issues of buy-in. Team members - e-mail Elin with comments to share with managers re: communication.  
  
Agenda
+
Agenda  
  
1. Progress on web build. Generally good progress with much effort ongoing.
+
1. Progress on web build. Generally good progress with much effort ongoing.  
  
Actions for group - push web editors to reduce long text secions &amp; follow guidelines. Submit questions for useability testing at [http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA http://spreadsheets.google.com/viewform?hl=en&amp;formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA]
+
Actions for group - push web editors to reduce long text secions &amp; follow guidelines. Submit questions for useability testing at [http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA http://spreadsheets.google.com/viewform?hl=en&amp;formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA]  
  
Usability study to be scheduled.
+
Usability study to be scheduled.  
  
2. WIKI training - send names to Ian by 1/8. Joe will arrange training session if sufficient interest.
+
2. WIKI training - send names to Ian by 1/8. Joe will arrange training session if sufficient interest.  
  
3. Basecamp. Decided to test use of this tool. Not retrospective but for end of phase I and continuing into phase II of this team. Use for to-do, agenda items, agenda planning. Look at writeboard as equivalent to Google docs. Note from Ian - if used for sending a message, need to check off subscribers for the message at the bottom - or no-one gets the message!
+
3. Basecamp. Decided to test use of this tool. Not retrospective but for end of phase I and continuing into phase II of this team. Use for to-do, agenda items, agenda planning. Look at writeboard as equivalent to Google docs. Note from Ian - if used for sending a message, need to check off subscribers for the message at the bottom - or no-one gets the message!  
  
Elin will use Basecamp to share materials related to our recent assessment.
+
Elin will use Basecamp to share materials related to our recent assessment.  
  
Barbara will start on task list - all should add to it.
+
Barbara will start on task list - all should add to it.  
  
4. As we go forward - team members to scan site (web, wiki) each week for progress, issues. Report tech issues to go/webtasks
+
4. As we go forward - team members to scan site (web, wiki) each week for progress, issues. Report tech issues to go/webtasks  
  
Decide on wiki next steps - when to replace front page, set up links for user categories.
+
Decide on wiki next steps - when to replace front page, set up links for user categories.  
  
Jess will add search function to single blog postings.
+
Jess will add search function to single blog postings.  
  
 
=== 2010: January 13<br>  ===
 
=== 2010: January 13<br>  ===
  
Present: Barbara, Carrie, Doreen, Elin (moderator, time), Ian, Jess (notes)
+
Present: Barbara, Carrie, Doreen, Elin (moderator, time), Ian, Jess (notes)  
  
News/Updates/Miscellaneous:
+
News/Updates/Miscellaneous:  
  
*Discussed email options for Basecamp—digest only sends summary of newly added to-dos, completed to-dos, newly added milestones, and completed milestones (doesn’t stop you from getting an email every time someone posts a comment, but you can unsubscribe yourself manually from receiving messages)
+
*Discussed email options for Basecamp—digest only sends summary of newly added to-dos, completed to-dos, newly added milestones, and completed milestones (doesn’t stop you from getting an email every time someone posts a comment, but you can unsubscribe yourself manually from receiving messages)  
*Elin will be away next Wednesday
+
*Elin will be away next Wednesday  
 
*Doreen will run the meeting and post the agenda on the Agenda Items Writeboard in Basecamp
 
*Doreen will run the meeting and post the agenda on the Agenda Items Writeboard in Basecamp
  
Discussions:
+
Discussions:  
  
*How can we make our profiles look like business cards?
+
*How can we make our profiles look like business cards?  
**After creating subpages for all profiles and adding profiles to the subpages, navigate to the page where the profiles will appear. Create a basic content node. In the body, enter “[view:Profiles==MMID]” where MMID is the Monster Menus ID aka, the number in parentheses at the top left of the edit console. Save. Business cards appear. Yippee (Thanks, Ian!)
+
**After creating subpages for all profiles and adding profiles to the subpages, navigate to the page where the profiles will appear. Create a basic content node. In the body, enter “[view:Profiles==MMID]” where MMID is the Monster Menus ID aka, the number in parentheses at the top left of the edit console. Save. Business cards appear. Yippee (Thanks, Ian!)  
*Carrie will add a redirect on the Offices &amp; Services Academics LIS page to the LIS landing page (http://midd2.middlebury.edu/offices/academic/lis)
+
*Carrie will add a redirect on the Offices &amp; Services Academics LIS page to the LIS landing page (http://midd2.middlebury.edu/offices/academic/lis)  
*Doreen asked about having the 3 quick link tabs at the top right of the banner appear on the 3 major subsections of the LIS sites: Library, Technology &amp; Curricular Tech. As of this writing, it had been implemented for the Library site and Ian will touch base with CT to ask if they want the option added to their site.
+
*Doreen asked about having the 3 quick link tabs at the top right of the banner appear on the 3 major subsections of the LIS sites: Library, Technology &amp; Curricular Tech. As of this writing, it had been implemented for the Library site and Ian will touch base with CT to ask if they want the option added to their site.  
*A general middlebury.edu web makeover status meeting happens this afternoon. Ian will share with us any relevant feedback. Mary started outlining a plan for usability testing but is out of the office.
+
*A general middlebury.edu web makeover status meeting happens this afternoon. Ian will share with us any relevant feedback. Mary started outlining a plan for usability testing but is out of the office.  
*Where are the major gaps? Around the table: search portal, database list from subsplus, hours/calendar, r25, room reservations (scheduled for 2/1), media services (Barbara and Jess will contact Jim to see if we can assist with this part of the site)
+
*Where are the major gaps? Around the table: search portal, database list from subsplus, hours/calendar, r25, room reservations (scheduled for 2/1), media services (Barbara and Jess will contact Jim to see if we can assist with this part of the site)  
*Wiki training: Ian forwarded Joe A. the list of interested parties
+
*Wiki training: Ian forwarded Joe A. the list of interested parties  
*Wiki main page transformation: Via an LIS Blog posting Carrie will solicit additional content recommendations for the main audience-specific wiki pages, to be submitted by next Wednesday 1/20. We’ll review and assess Wiki main page readiness at our 1/20 meeting.
+
*Wiki main page transformation: Via an LIS Blog posting Carrie will solicit additional content recommendations for the main audience-specific wiki pages, to be submitted by next Wednesday 1/20. We’ll review and assess Wiki main page readiness at our 1/20 meeting.  
*Deleting a wiki page: delete all content on the page, and add “blanked for deletion” [IN THE SUMMARY FIELD] and a Wiki administrator will delete it
+
*Deleting a wiki page: delete all content on the page, and add “blanked for deletion” [IN THE SUMMARY FIELD] and a Wiki administrator will delete it  
*Scheduled system downtimes: Mary and Jeff signed off on sharing these via the Blog. Of course, these will not include explanation of WHY a system is down, just WHICH systems will be down. This is an accompaniment to email notifications, not a substitute.
+
*Scheduled system downtimes: Mary and Jeff signed off on sharing these via the Blog. Of course, these will not include explanation of WHY a system is down, just WHICH systems will be down. This is an accompaniment to email notifications, not a substitute.  
*Team agreed to Ian creating a new main category for Scheduled downtimes, with several subcategories for specific system names (i.e. Banner, Library databases, et al.) Ian mentioned the need to discuss Banner downtimes again with Marcy
+
*Team agreed to Ian creating a new main category for Scheduled downtimes, with several subcategories for specific system names (i.e. Banner, Library databases, et al.) Ian mentioned the need to discuss Banner downtimes again with Marcy  
*Carrie and Bryan will follow-up with Chris N. on getting the library database outages posted somewhere
+
*Carrie and Bryan will follow-up with Chris N. on getting the library database outages posted somewhere  
*Team will use the Agenda Items Writeboard to post specific agendas (future agenda items will be at the bottom of the board).
+
*Team will use the Agenda Items Writeboard to post specific agendas (future agenda items will be at the bottom of the board).  
 
*Creating a Writeboard to record likes and dislikes about Basecamp as a project management tool so please weigh in with your comments there.
 
*Creating a Writeboard to record likes and dislikes about Basecamp as a project management tool so please weigh in with your comments there.
  
Agenda for next week:
+
Agenda for next week:  
  
 
*Status of usability testing, Assess readiness of wiki main pages for changeover to main page by audience, Check-in for launch readiness and any updates from Ian (check Basecamp Agenda writeboard for most current version!)
 
*Status of usability testing, Assess readiness of wiki main pages for changeover to main page by audience, Check-in for launch readiness and any updates from Ian (check Basecamp Agenda writeboard for most current version!)
Line 1,968: Line 1,968:
 
=== 2010:&nbsp;January 20<br>  ===
 
=== 2010:&nbsp;January 20<br>  ===
  
Present:&nbsp; Jim, Barbara, Jess, Liz, Doreen, Carrie (notes), Ian
+
Present:&nbsp; Jim, Barbara, Jess, Liz, Doreen, Carrie (notes), Ian  
  
*Usability testing – waiting for word from Mary
+
*Usability testing – waiting for word from Mary  
*Wiki main pages – <br>o Jim will change “LIS public documentation” to “Tech Helpdesk public documentation”<br>o Wiki main page will include links to a few wiki pages (no more than 7) that are common among all audiences AND links to audience-specific pages.&nbsp; Barbara will start a writeboard with proposed links.<br>o Create “go” link for each audience-specific page and share the go link on each audience-specific page.<br>o After we decide on content of new main page, we’re ready to go, except:&nbsp; before making changes, comb thru existing page and confirm that all links have been accounted for.
+
*Wiki main pages – <br>o Jim will change “LIS public documentation” to “Tech Helpdesk public documentation”<br>o Wiki main page will include links to a few wiki pages (no more than 7) that are common among all audiences AND links to audience-specific pages.&nbsp; Barbara will start a writeboard with proposed links.<br>o Create “go” link for each audience-specific page and share the go link on each audience-specific page.<br>o After we decide on content of new main page, we’re ready to go, except:&nbsp; before making changes, comb thru existing page and confirm that all links have been accounted for.  
*Check-in on readiness for launch<br>o Last Wednesday, priorities for college site were determined. Tasks were finished sooner than expected. Will get to at least some of the post-launch priorities.<br>o Library search widget (aka library portal) is 13th on the list of post-launch priorities. Adam is assigned to it.&nbsp; AT the very least, the library will have the MIDCAT search window that's on the current library site.<br>o Hours from R25 is 16th on before-launch list (?I'm not confident about this).<br>o Subsplus integration is 30th on after-launch launch
+
*Check-in on readiness for launch<br>o Last Wednesday, priorities for college site were determined. Tasks were finished sooner than expected. Will get to at least some of the post-launch priorities.<br>o Library search widget (aka library portal) is 13th on the list of post-launch priorities. Adam is assigned to it.&nbsp; AT the very least, the library will have the MIDCAT search window that's on the current library site.<br>o Hours from R25 is 16th on before-launch list (?I'm not confident about this).<br>o Subsplus integration is 30th on after-launch launch  
*Status updates<br>o Updated progress on some sections in writeboard<br>o Helpdesk goal is to have something presentable for launch, get it proofread, then add to it over time<br>o Keep overall estimate at 90% on college spreadsheet.
+
*Status updates<br>o Updated progress on some sections in writeboard<br>o Helpdesk goal is to have something presentable for launch, get it proofread, then add to it over time<br>o Keep overall estimate at 90% on college spreadsheet.  
*Should we send our sites to Communications for review? Yes, send LIS search landing page Feb 1. Doreen will do this.
+
*Should we send our sites to Communications for review? Yes, send LIS search landing page Feb 1. Doreen will do this.  
*Carrie will tell Alex he can make the changes he suggested to the LIS&nbsp;blog.&nbsp; Ian says Alex already has editing privileges at a higher admin level, so we don't have to give him additional privileges. Carrie also will ask Alex if he still wants to meet with us, and tell him that the LIS&nbsp;web team has chosen to stay out of the discussion of a logo since it is our understanding that departments are prohibited from having their own logos.
+
*Carrie will tell Alex he can make the changes he suggested to the LIS&nbsp;blog.&nbsp; Ian says Alex already has editing privileges at a higher admin level, so we don't have to give him additional privileges. Carrie also will ask Alex if he still wants to meet with us, and tell him that the LIS&nbsp;web team has chosen to stay out of the discussion of a logo since it is our understanding that departments are prohibited from having their own logos.  
*Doreen can access Communications and Public Affairs photos. She can help us go in and get photos for web site.
+
*Doreen can access Communications and Public Affairs photos. She can help us go in and get photos for web site.  
*http://midd2.middlebury.edu/offices/technology - This will have content, perhaps a subpage list.&nbsp; It's Ian's responsibility.<br>
+
*http://midd2.middlebury.edu/offices/technology - This will have content, perhaps a subpage list.&nbsp; It's Ian's responsibility.<br>  
*Home pages for public computers: Should our team recommend which homepage should display on public computers in libaries and labs?&nbsp; Nah--HelpDesk can determine this on their own.
+
*Home pages for public computers: Should our team recommend which homepage should display on public computers in libaries and labs?&nbsp; Nah--HelpDesk can determine this on their own.  
 
*Agenda for next week: Team members should add suggestions to agenda item list<br><br>
 
*Agenda for next week: Team members should add suggestions to agenda item list<br><br>
  
 
=== 2010: January 27<br>  ===
 
=== 2010: January 27<br>  ===
  
Present: Liz, Barbara, Carrie, Elin, Ian, Jess
+
Present: Liz, Barbara, Carrie, Elin, Ian, Jess  
  
News/Updates/Miscellaneous:
+
News/Updates/Miscellaneous:  
  
Launch is officially Feb 4th. Editing can continue through Feb 3rd. We'll make sure this goes on LIS blog after it's on the Webmakeover blog.
+
Launch is officially Feb 4th. Editing can continue through Feb 3rd. We'll make sure this goes on LIS blog after it's on the Webmakeover blog.  
  
Wiki process - to remove pages, tag as "blank for deletion" in summary field. Ian will follow up on who will actually delete the pages.
+
Wiki process - to remove pages, tag as "blank for deletion" in summary field. Ian will follow up on who will actually delete the pages.  
  
Building &amp; service point hours - wiki page will provide access to various hours wherever they reside, until 25Live system gets going.
+
Building &amp; service point hours - wiki page will provide access to various hours wherever they reside, until 25Live system gets going.  
  
Tech page - page at level above Helpdesk, Banner etc. pages - currently empty. Suggestion - it redirects to LIS homepage. Ian to do.
+
Tech page - page at level above Helpdesk, Banner etc. pages - currently empty. Suggestion - it redirects to LIS homepage. Ian to do.  
  
Agenda:
+
Agenda:  
  
*Help &amp; Support Drupal pages. Not ready for prime time. How can we help get this done? Ian has asked Joe A. - Joe will have Ben provide assistance. Vaious meetings are coming up where this issue can be addressed. Team remains ready and willing to assist. Concludes that efforts now need to focus on web presence rather than wiki docs.
+
*Help &amp; Support Drupal pages. Not ready for prime time. How can we help get this done? Ian has asked Joe A. - Joe will have Ben provide assistance. Vaious meetings are coming up where this issue can be addressed. Team remains ready and willing to assist. Concludes that efforts now need to focus on web presence rather than wiki docs.  
*Quick links. We had a suggestion that all 4 Quick Links tabs should remain throughout the LIS site. After discussion, vote was tied so current structure - 3 tabs without the one refering to the page you're at - remains for launch.
+
*Quick links. We had a suggestion that all 4 Quick Links tabs should remain throughout the LIS site. After discussion, vote was tied so current structure - 3 tabs without the one refering to the page you're at - remains for launch.  
*Summary of web process to launch: Ian reports - this week functionality is still being added. Next week cross browser checking, formatting issues etc. will be happening. All team members should continue to browse the whole LIS site to spot &amp; report glitches etc.
+
*Summary of web process to launch: Ian reports - this week functionality is still being added. Next week cross browser checking, formatting issues etc. will be happening. All team members should continue to browse the whole LIS site to spot &amp; report glitches etc.  
 
*Usability testing. Conclusion - it's a priority for after launch. Continue to add suggestions for usability testing at [http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA http://spreadsheets.google.com/viewform?hl=en&amp;formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA] Plan - LIS will conduct testing in addition to college-wide. Will ask for access to suggestions from above spreadsheet.<br>
 
*Usability testing. Conclusion - it's a priority for after launch. Continue to add suggestions for usability testing at [http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA http://spreadsheets.google.com/viewform?hl=en&amp;formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA] Plan - LIS will conduct testing in addition to college-wide. Will ask for access to suggestions from above spreadsheet.<br>
  
To do:
+
To do:  
  
Add to agenda items - identification of material that will become dated. Larger issue - maintenance plan.
+
Add to agenda items - identification of material that will become dated. Larger issue - maintenance plan.  
  
Check wiki start page design writeboard. Get new wiki start page in place (who?)
+
Check wiki start page design writeboard. Get new wiki start page in place (who?)  
  
Team to check&nbsp;% complete figures writeboard &amp; update
+
Team to check&nbsp;% complete figures writeboard &amp; update  
  
 
=== 2010: February 3<br>  ===
 
=== 2010: February 3<br>  ===
  
Present: Elin, Ian, Carrie, Jess (notes), Barbara, Liz, Jim<br>
+
Present: Elin, Ian, Carrie, Jess (notes), Barbara, Liz, Jim<br>  
  
News/Updates/Miscellaneous: <br>
+
News/Updates/Miscellaneous: <br>  
  
*Sparkling apple juice, ginger cookies, and apples were enjoyed by all.
+
*Sparkling apple juice, ginger cookies, and apples were enjoyed by all.  
*Elin's last work date will be June 30th.
+
*Elin's last work date will be June 30th.  
*Discussed lib. page node for feedback--is it necessary? may be removed
+
*Discussed lib. page node for feedback--is it necessary? may be removed  
*Library spotlight section of library page-fed with tag feed from blog "library spotlight" (name to be finalized)
+
*Library spotlight section of library page-fed with tag feed from blog "library spotlight" (name to be finalized)  
*Help &amp; support pages much improved and ready for launch
+
*Help &amp; support pages much improved and ready for launch  
*Wiki workshop was well-received. Next time have the workshop focused to skill levels.
+
*Wiki workshop was well-received. Next time have the workshop focused to skill levels.  
*LIS page CAN be sent to Communications after removing the events feed (will not be ready by launch) (Doreen)
+
*LIS page CAN be sent to Communications after removing the events feed (will not be ready by launch) (Doreen)  
*Tech banner doesn't click-will be resolved (Ian)
+
*Tech banner doesn't click-will be resolved (Ian)  
*Carrie will tweak Helpdesk quicklinks drop down
+
*Carrie will tweak Helpdesk quicklinks drop down  
*Filling out the PFDP team 360 reviews: Sponsor will not see; just individuals and managers
+
*Filling out the PFDP team 360 reviews: Sponsor will not see; just individuals and managers  
*Tags on the Drupal site: Unfinished business. This will be discussed in the coming months. Sense that at the moment it's more helpful for news and events, and not so much for basic content, but the functionality with regard to search will be changing.
+
*Tags on the Drupal site: Unfinished business. This will be discussed in the coming months. Sense that at the moment it's more helpful for news and events, and not so much for basic content, but the functionality with regard to search will be changing.  
 
*Should we have table-tent or computer monitor signs encouraging people to give feedback on the site?
 
*Should we have table-tent or computer monitor signs encouraging people to give feedback on the site?
  
Launch business: <br>
+
Launch business: <br>  
  
*The site will be uneditable 2/4 starting at 9 a.m. until the College community receives an email from Ron Liebowitz stating that it is live.
+
*The site will be uneditable 2/4 starting at 9 a.m. until the College community receives an email from Ron Liebowitz stating that it is live.  
*MCMS will transition tomorrow to cms.middlebury.edu. Most of it will not be publicly available. You will be prompted to log in to view your pages. If there is something on the old site that needs to be accessible, inform Ian.
+
*MCMS will transition tomorrow to cms.middlebury.edu. Most of it will not be publicly available. You will be prompted to log in to view your pages. If there is something on the old site that needs to be accessible, inform Ian.  
 
*Elin will create a blog post about the launch of the new Midd Drupal site thanking all LIS staff members for their contributions, will also include thank-yous to wiki editors.
 
*Elin will create a blog post about the launch of the new Midd Drupal site thanking all LIS staff members for their contributions, will also include thank-yous to wiki editors.
  
Wiki homepage: <br>
+
Wiki homepage: <br>  
  
*Barbara will implement the main page switch [done]
+
*Barbara will implement the main page switch [done]  
 
*Carrie will make a blog post about the switch [done]
 
*Carrie will make a blog post about the switch [done]
  
Future agendas: <br>
+
Future agendas: <br>  
  
*Discussion and formal recommendation for implementing the White Whale blog themes for both the LIS and other Middlebury blogs
+
*Discussion and formal recommendation for implementing the White Whale blog themes for both the LIS and other Middlebury blogs  
*Suggestions blog and Circ blog--discuss if they should merge or not
+
*Suggestions blog and Circ blog--discuss if they should merge or not  
*Revisit the tabled item of meeting with Alex to discuss recent Blog changes
+
*Revisit the tabled item of meeting with Alex to discuss recent Blog changes  
 
*Discuss the need to end the business of the team as it currently exists by 6/30 since we will be losing both our team leader and out team sponsor.
 
*Discuss the need to end the business of the team as it currently exists by 6/30 since we will be losing both our team leader and out team sponsor.
  
 
=== 2010: February 10<br>  ===
 
=== 2010: February 10<br>  ===
  
Present: Elin, Ian, Carrie, Jess, Barbara, Jim<br>
+
Present: Elin, Ian, Carrie, Jess, Barbara, Jim<br>  
  
News/Updates/Miscellaneous: <br>
+
News/Updates/Miscellaneous: <br>  
  
Elin announced that Mike R. wants to have lunch with us. Cynicism ensued. Noonies was suggested as location.<br>
+
Elin announced that Mike R. wants to have lunch with us. Cynicism ensued. Noonies was suggested as location.<br>  
  
Ian will give Jim a list of "go" links pointing to the Tech Help page - some of these should point elsewhere!
+
Ian will give Jim a list of "go" links pointing to the Tech Help page - some of these should point elsewhere!  
  
Agenda items:
+
Agenda items:  
  
*Feedback on website - how to handle? Ian sees the form feedback and passes it on to appropriate primary contacts. Items relevant to the library pages go to Carrie. Decision was made to post these on the Basecamp "to-do" list, with responsibility assigned. Meeting time need not be given to discussion of these individual feedback items unless requested by a team member.<br>
+
*Feedback on website - how to handle? Ian sees the form feedback and passes it on to appropriate primary contacts. Items relevant to the library pages go to Carrie. Decision was made to post these on the Basecamp "to-do" list, with responsibility assigned. Meeting time need not be given to discussion of these individual feedback items unless requested by a team member.<br>  
*There are issues with browser IE6 - Ian will post to LIS blog about browsers supported/recommended.
+
*There are issues with browser IE6 - Ian will post to LIS blog about browsers supported/recommended.  
*End of the team. Elin will talk to Jeff about rearranging the team goals so that our work can be completed by June 30th. Our charge includes "develop site refresh strategies". We believe we can tackle that as well by June 30th as by the original date in August.
+
*End of the team. Elin will talk to Jeff about rearranging the team goals so that our work can be completed by June 30th. Our charge includes "develop site refresh strategies". We believe we can tackle that as well by June 30th as by the original date in August.  
*Search issues - Ian was to post next week about Google search updating, but he has already found a possible solution to the "Google providing links to the old site" problem &amp; is trying it out as I write.
+
*Search issues - Ian was to post next week about Google search updating, but he has already found a possible solution to the "Google providing links to the old site" problem &amp; is trying it out as I write.  
*Blog themes. Does the team wish to recommend a White Whale theme to be used by the LIS blog? Or are we OK with the locally developed theme currently in use? Team vote next week - Jess will post links to WW theme examples in the agenda.
+
*Blog themes. Does the team wish to recommend a White Whale theme to be used by the LIS blog? Or are we OK with the locally developed theme currently in use? Team vote next week - Jess will post links to WW theme examples in the agenda.  
*Blog merging. Should Circ blog merge into LIS blog? In principle yes, in practice it is very active and specific to circ and could deluge the public interest content of the LIS blog. Elin can make the decision. Similarly, the suggestions blog. Carrie will think about workflow, &amp; consider any suggestions the team wants to make. Q. Where is the suggestions form? Should there be a separate suggestion page in the LIS blog? How can spam comments be prevented? - try "enable comment spam blocking".
+
*Blog merging. Should Circ blog merge into LIS blog? In principle yes, in practice it is very active and specific to circ and could deluge the public interest content of the LIS blog. Elin can make the decision. Similarly, the suggestions blog. Carrie will think about workflow, &amp; consider any suggestions the team wants to make. Q. Where is the suggestions form? Should there be a separate suggestion page in the LIS blog? How can spam comments be prevented? - try "enable comment spam blocking".  
 
*Blogs review -&nbsp; many inactive LIS related blogs still exist. All team members should examine the blog roll (sorry but the Brit in me can't help but think "bog roll") and contact the owners in their areas to see if these can be merged or just deleted.
 
*Blogs review -&nbsp; many inactive LIS related blogs still exist. All team members should examine the blog roll (sorry but the Brit in me can't help but think "bog roll") and contact the owners in their areas to see if these can be merged or just deleted.
  
<br>
+
<br>  
  
 
=== 2010: February 17  ===
 
=== 2010: February 17  ===
  
Present: Ian, Carrie, Barbara, Doreen, Liz. Elin (notes); Jess and Jim absent<br>
+
Present: Ian, Carrie, Barbara, Doreen, Liz. Elin (notes); Jess and Jim absent<br>  
  
*Announcements/updates - Elin meeting with Jeff re: goals (re-scheduled to Mon 2/22); there will be a party to celebrate the web makeover on 3/12 in Atwater - stay tuned for details; Carrie will give a grand "tour" of the new LIS website to MBH faculty; Doreen will schedule the lunch (done!) <br>
+
*Announcements/updates - Elin meeting with Jeff re: goals (re-scheduled to Mon 2/22); there will be a party to celebrate the web makeover on 3/12 in Atwater - stay tuned for details; Carrie will give a grand "tour" of the new LIS website to MBH faculty; Doreen will schedule the lunch (done!) <br>  
*Absences - team will meet as long as there is an agenda and a majority; upcoming absences - Elin out 3/1-8 and 4/12 - 25; Liz out 3/22-26; Carrie out 3/3; Ian out 3/15-4/3 and last week in April
+
*Absences - team will meet as long as there is an agenda and a majority; upcoming absences - Elin out 3/1-8 and 4/12 - 25; Liz out 3/22-26; Carrie out 3/3; Ian out 3/15-4/3 and last week in April  
*Forms - Ian did inventory - very few forms left on old web - he will follow up; Carrie will follow up on the Library forms question/feedback
+
*Forms - Ian did inventory - very few forms left on old web - he will follow up; Carrie will follow up on the Library forms question/feedback  
 
*Basecamp to-do items as a way to record feedback issues? May not work as hoped by Carrie - she will revisit how she plans to track feedback for Lib pages
 
*Basecamp to-do items as a way to record feedback issues? May not work as hoped by Carrie - she will revisit how she plans to track feedback for Lib pages
  
*Blog theme - general discussion; features, columns, headers, images, visuals, aesthetics, custom options and pros/cons of each theme. Width and number of columns are fixed on each theme, but each theme has customizable features. Rather than vote on 1 theme, and change the current theme at this moment, we would like to recommend that all WW themes be made available as an option - in addition to the themes developed by Alex. The team acknowledged Alex's good work in customizing our current theme; the team can offer valuable feedback in the development of custom themes. Ian will follow up with Alex and others and create a blog refinements/questions/suggestions Writeboard page on Basecamp. Ian will also follow up with Alex about the Media wiki template (http://chisel.middlebury.edu/~achapin/mediawiki/); changes need to be made to wiki template - header/footer, search box placement, meta links and style guide<br>
+
*Blog theme - general discussion; features, columns, headers, images, visuals, aesthetics, custom options and pros/cons of each theme. Width and number of columns are fixed on each theme, but each theme has customizable features. Rather than vote on 1 theme, and change the current theme at this moment, we would like to recommend that all WW themes be made available as an option - in addition to the themes developed by Alex. The team acknowledged Alex's good work in customizing our current theme; the team can offer valuable feedback in the development of custom themes. Ian will follow up with Alex and others and create a blog refinements/questions/suggestions Writeboard page on Basecamp. Ian will also follow up with Alex about the Media wiki template (http://chisel.middlebury.edu/~achapin/mediawiki/); changes need to be made to wiki template - header/footer, search box placement, meta links and style guide<br>  
 
*Question about current placement of the Pages on the LIS blog. Ian will move the Pages section up.<br>
 
*Question about current placement of the Pages on the LIS blog. Ian will move the Pages section up.<br>
  
Line 2,085: Line 2,085:
 
*Trackback/pingback settings? Ian will make sure it's enabled.<br>
 
*Trackback/pingback settings? Ian will make sure it's enabled.<br>
  
*Next steps for makeover PM’s? Now that the website is launched, a fellow project manager was wondering if it would be possible to be removed from the project managers email list, and also, if the questions and answers could be made available on the form questions and answers page - Ian will follow up <br>
+
*Next steps for makeover PM’s? Now that the website is launched, a fellow project manager was wondering if it would be possible to be removed from the project managers email list, and also, if the questions and answers could be made available on the form questions and answers page - Ian will follow up <br>  
*Lib page node for feedback – still there and links to college form. Ian will forward relevant feedback to team member primarily responsible; team member will evaluate and incorporate as appropriate; will bring to team any items that need broader input<br>
+
*Lib page node for feedback – still there and links to college form. Ian will forward relevant feedback to team member primarily responsible; team member will evaluate and incorporate as appropriate; will bring to team any items that need broader input<br>  
*Any feedback from Communications? Not yet.<br>
+
*Any feedback from Communications? Not yet.<br>  
*Wiki&nbsp; and blog training – next steps? Ian will check with Joe; there may be others - Alex, Ben - who may be able to provide workshops
+
*Wiki&nbsp; and blog training – next steps? Ian will check with Joe; there may be others - Alex, Ben - who may be able to provide workshops  
*Library hours on 25Live - Ian has a meeting scheduled
+
*Library hours on 25Live - Ian has a meeting scheduled  
 
*Thanks to Ian for taking on many follow-up items from this meeting<br><br>
 
*Thanks to Ian for taking on many follow-up items from this meeting<br><br>
  
Future agenda items - add/edit items on Writeboard <br>
+
Future agenda items - add/edit items on Writeboard <br>  
  
*Refresh strategies
+
*Refresh strategies  
*Usability
+
*Usability  
 
*Usability testing – add content to the Writeboard that Jess started
 
*Usability testing – add content to the Writeboard that Jess started
  
<br>
+
<br>  
  
 
=== 2010: March 3  ===
 
=== 2010: March 3  ===
  
(Meeting canceled due to &lt;5 team members present)
+
(Meeting canceled due to &lt;5 team members present)  
  
 
*Informally discussed need to focus on Usability testing and Refresh strategies-Check Basecamp!
 
*Informally discussed need to focus on Usability testing and Refresh strategies-Check Basecamp!
Line 2,108: Line 2,108:
 
=== 2010: March 10  ===
 
=== 2010: March 10  ===
  
Present: Ian, Jess, Jim, Barbara, Doreen, Carrie, Elin (notes, sort-of...), Liz out
+
Present: Ian, Jess, Jim, Barbara, Doreen, Carrie, Elin (notes, sort-of...), Liz out  
  
Ian or others, please flesh out these meeting notes when/if you get a chance&nbsp;:-)
+
Ian or others, please flesh out these meeting notes when/if you get a chance&nbsp;:-)  
  
Announcements:
+
Announcements:  
  
*Web party - there will be awards!
+
*Web party - there will be awards!  
*Ian out 3/15 - 4/3 (gone next 3 meetings)
+
*Ian out 3/15 - 4/3 (gone next 3 meetings)  
*Lunch - maybe re-schedule for April?
+
*Lunch - maybe re-schedule for April?  
*Elin met with Jeff briefly to ask about next steps for Web Team; stay tuned
+
*Elin met with Jeff briefly to ask about next steps for Web Team; stay tuned  
*Barbara and Ian working on custom search results pages (see Ian's blog post)
+
*Barbara and Ian working on custom search results pages (see Ian's blog post)  
 
*Jim - will not be able to dedicate much time to usability until mid-April
 
*Jim - will not be able to dedicate much time to usability until mid-April
  
Usability
+
Usability  
  
*Many thanks to Jess and Ian for organizing our usability timeline, recommending ideas/software and testing possible software etc.
+
*Many thanks to Jess and Ian for organizing our usability timeline, recommending ideas/software and testing possible software etc.  
*Ian set up instance of Infomaki for testing; will take resources to set up, let's make sure we really want to use this before we ask Ian to develop; are other tools that can do the Infomaki thing just as well? Infomaki does random questions very well
+
*Ian set up instance of Infomaki for testing; will take resources to set up, let's make sure we really want to use this before we ask Ian to develop; are other tools that can do the Infomaki thing just as well? Infomaki does random questions very well  
*Ian described Silverback, Mac app uses iSight and audio, records interaction, Elin will request $50 to cover cost (check out the short video on the Silverback site)
+
*Ian described Silverback, Mac app uses iSight and audio, records interaction, Elin will request $50 to cover cost (check out the short video on the Silverback site)  
*Jess described Five-second test, 2 types - memory and clicking, Elin will request $50 to cover cost
+
*Jess described Five-second test, 2 types - memory and clicking, Elin will request $50 to cover cost  
*Google Analytics - team will need to develop targeted questions for Chris, Ian will talk to Chris about GA
+
*Google Analytics - team will need to develop targeted questions for Chris, Ian will talk to Chris about GA  
*Key Survey
+
*Key Survey  
*Survey Monkey
+
*Survey Monkey  
*Heat Maps
+
*Heat Maps  
*Jing or other screencasting tools? Screenr? Community Clips?
+
*Jing or other screencasting tools? Screenr? Community Clips?  
*Usability testing will include all LIS platforms
+
*Usability testing will include all LIS platforms  
*Does it matter if we test only on Macs?
+
*Does it matter if we test only on Macs?  
*Involve primary contacts in Usability?
+
*Involve primary contacts in Usability?  
*Pull in other staff resources? Helpdesk/LIS student employees?
+
*Pull in other staff resources? Helpdesk/LIS student employees?  
*What about user agreements for testing?
+
*What about user agreements for testing?  
 
*Other budget requests? Incentive prizes and awards?
 
*Other budget requests? Incentive prizes and awards?
  
<br>
+
<br>  
  
Mini-teams will come up with questions for each site: Technology Help: Barbara, Jim, Liz, Ian LIS pages: Elin and Doreen Library pages: Elin, Carrie, Jess
+
Mini-teams will come up with questions for each site: Technology Help: Barbara, Jim, Liz, Ian LIS pages: Elin and Doreen Library pages: Elin, Carrie, Jess  
  
'''Remember to check Basecamp regularly for updates!'''
+
'''Remember to check Basecamp regularly for updates!'''  
  
 
=== 2010: March 17  ===
 
=== 2010: March 17  ===
  
Present: Liz, Jess (notes), Barbara, Doreen, Carrie, Elin<br>
+
Present: Liz, Jess (notes), Barbara, Doreen, Carrie, Elin<br>  
  
Announcements:<br>
+
Announcements:<br>  
  
*Website launch party was tasty. Blue cake was consumed (and worn, apparently) by many. Ian won the MVP award for the College Web makeover. Congrats, Ian!!
+
*Website launch party was tasty. Blue cake was consumed (and worn, apparently) by many. Ian won the MVP award for the College Web makeover. Congrats, Ian!!  
*Elin postponed our team lunch at Noonie's until April since she'll be out
+
*Elin postponed our team lunch at Noonie's until April since she'll be out  
*Confirmed that we have AD support for usability testing
+
*Confirmed that we have AD support for usability testing  
*ADs approved budget for Silverback and enhanced 5-sec. testing purchases
+
*ADs approved budget for Silverback and enhanced 5-sec. testing purchases  
*No budget for student incentives<br>
+
*No budget for student incentives<br>  
*We may be able to have student employees (either at the Helpdesk or at Circ.) test during their regular shifts. If needed, we may also revisit an idea to use some of the extra student employee budget to pay students to test
+
*We may be able to have student employees (either at the Helpdesk or at Circ.) test during their regular shifts. If needed, we may also revisit an idea to use some of the extra student employee budget to pay students to test  
*We may also consider enlisting the help of the Digital Media Tutors in the actual testing environment
+
*We may also consider enlisting the help of the Digital Media Tutors in the actual testing environment  
*Barbara will make survey for LIS staff on website (based on our previous key survey)
+
*Barbara will make survey for LIS staff on website (based on our previous key survey)  
**Team agrees that since LIS Staff were involved with building the site and have already voiced lots of feedback about it, and given our time constraints, this will suffice for the usability testing as far as LIS Staff is concerned. As a whole, the primary audience for LIS pages is students, (with faculty and staff being second)
+
**Team agrees that since LIS Staff were involved with building the site and have already voiced lots of feedback about it, and given our time constraints, this will suffice for the usability testing as far as LIS Staff is concerned. As a whole, the primary audience for LIS pages is students, (with faculty and staff being second)  
*Clarification that click heat testing is for data gathering but not for our observational usability testing phase
+
*Clarification that click heat testing is for data gathering but not for our observational usability testing phase  
*Clarification that Web feedback about LIS pages sent to Ian is passed along to the primary contacts
+
*Clarification that Web feedback about LIS pages sent to Ian is passed along to the primary contacts  
 
*Bryan expressed interest in being involved with usability testing of library pages. Jess will put out a call to all LIS staff via the blog to see if anyone else wants to help or has additional questions or concerns they want to include for the testing<br>
 
*Bryan expressed interest in being involved with usability testing of library pages. Jess will put out a call to all LIS staff via the blog to see if anyone else wants to help or has additional questions or concerns they want to include for the testing<br>
  
Goals &amp; Next steps?:
+
Goals &amp; Next steps?:  
  
 
*Move ahead with small group work
 
*Move ahead with small group work
Line 2,172: Line 2,172:
 
*Keep in mind we'll be coming back together as a group to combine questions from each of the 3 subgroups and our testing sessions as a whole should be no longer than 30 minutes (ballpark at this point)
 
*Keep in mind we'll be coming back together as a group to combine questions from each of the 3 subgroups and our testing sessions as a whole should be no longer than 30 minutes (ballpark at this point)
  
#Aim for 5 (ballpark) questions for the Silverback portion of the testing
+
#Aim for 5 (ballpark) questions for the Silverback portion of the testing  
 
#5 second tests can be essentially unlimited
 
#5 second tests can be essentially unlimited
  
*Each small group should download one 30 day trial version of Silverback and test out their 5 questions and see how long it takes to complete them (need a Mac with a webcam to do this)
+
*Each small group should download one 30 day trial version of Silverback and test out their 5 questions and see how long it takes to complete them (need a Mac with a webcam to do this)  
*Questions about how to proceed with the Helpdesk questions. Liz and Barbara will muddle through as best they can
+
*Questions about how to proceed with the Helpdesk questions. Liz and Barbara will muddle through as best they can  
*Start thinking about when and how we will advertise the call for student testers (see new writeboard in Basecamp)
+
*Start thinking about when and how we will advertise the call for student testers (see new writeboard in Basecamp)  
 
*Jess will clean up some writeboards (delete them) and put them in the Files section for archival purposes<br>
 
*Jess will clean up some writeboards (delete them) and put them in the Files section for archival purposes<br>
  
Team direction:
+
Team direction:  
  
 
*Elin will formally ask ADs to tell us their plan for the LIS Website team. It doesn't make sense for us to propose changes until we know what they're planning. We'll review their response and if necessary form a counter-proposal.
 
*Elin will formally ask ADs to tell us their plan for the LIS Website team. It doesn't make sense for us to propose changes until we know what they're planning. We'll review their response and if necessary form a counter-proposal.
Line 2,186: Line 2,186:
 
=== 2010:&nbsp; March 24<br>  ===
 
=== 2010:&nbsp; March 24<br>  ===
  
Present: Liz, Bryan, Jess, Doreen, Elin, Barbara, Carrie (notes)
+
Present: Liz, Bryan, Jess, Doreen, Elin, Barbara, Carrie (notes)  
  
Announcements:
+
Announcements:  
  
*Elin has asked Jeff for AD input on fate of web team. Jeff will ask ADs via email.
+
*Elin has asked Jeff for AD input on fate of web team. Jeff will ask ADs via email.  
 
*Carrie has observed that people who are used to the old website have a harder time with the new site. We should consider supplementing this semester's testing with testing done in the future. We'll get some baseline measurements now, at least.
 
*Carrie has observed that people who are used to the old website have a harder time with the new site. We should consider supplementing this semester's testing with testing done in the future. We'll get some baseline measurements now, at least.
  
Line 2,199: Line 2,199:
 
*5-second test is different. You purchase tokens as you go. Doreen might be able to purchase with her p-card.
 
*5-second test is different. You purchase tokens as you go. Doreen might be able to purchase with her p-card.
  
Review Silverback Questions:
+
Review Silverback Questions:  
  
*HelpDesk has 5-6 questions. Will split into students and faculty/staff.
+
*HelpDesk has 5-6 questions. Will split into students and faculty/staff.  
 
*Library has 5 questions for students, 5 for faculty (with some overlap). Some questions are duplicated for the LIS landing page. We can remove these.
 
*Library has 5 questions for students, 5 for faculty (with some overlap). Some questions are duplicated for the LIS landing page. We can remove these.
  
 
*LIS has 5-6 questions. Will remove questions from external audience. Will split into students and faculty/staff.
 
*LIS has 5-6 questions. Will remove questions from external audience. Will split into students and faculty/staff.
  
Next steps for testing:
+
Next steps for testing:  
  
 
*Jess will put all questions in 1 writeboard. Sort Silverback by destination (eg, LIS landing page, Library page, HelpDesk page) and audience. Might not need to sort 5-second tests; will investigate.
 
*Jess will put all questions in 1 writeboard. Sort Silverback by destination (eg, LIS landing page, Library page, HelpDesk page) and audience. Might not need to sort 5-second tests; will investigate.
  
*Goal for Silverback is 12 questions for students, 12 for faculty/staff.
+
*Goal for Silverback is 12 questions for students, 12 for faculty/staff.  
*Questions will be grouped by destination, but not labeled as such.
+
*Questions will be grouped by destination, but not labeled as such.  
*Carrie and Elin will add HelpDesk questions.
+
*Carrie and Elin will add HelpDesk questions.  
*Add a question: How to get to course website/Segue
+
*Add a question: How to get to course website/Segue  
 
*Bryan will ask Joe for permissions for the LIS website section of basecamp so that he can work on the usability questions there
 
*Bryan will ask Joe for permissions for the LIS website section of basecamp so that he can work on the usability questions there
  
LIS Survey:
+
LIS Survey:  
  
 
*Carrie and Barbara added 3 questions about LIS communications due to Mike Roy's interest in creating an internal LIS blog. Barbara will remove these, and Carrie and Barbara and Doreen will work on the issue through other venues.
 
*Carrie and Barbara added 3 questions about LIS communications due to Mike Roy's interest in creating an internal LIS blog. Barbara will remove these, and Carrie and Barbara and Doreen will work on the issue through other venues.
Line 2,222: Line 2,222:
 
*Barbara will fix typos as reported by team
 
*Barbara will fix typos as reported by team
  
Marketing:
+
Marketing:  
  
 
*We will use Dean of LIS email account to invite all students and all faculty/staff to participate in observational testing.
 
*We will use Dean of LIS email account to invite all students and all faculty/staff to participate in observational testing.
Line 2,230: Line 2,230:
 
*Need to list next steps (eg, who will do the scheduling, where will the testing be done?). Add to writeboard?
 
*Need to list next steps (eg, who will do the scheduling, where will the testing be done?). Add to writeboard?
  
<br>
+
<br>  
 +
 
 
=== 2010: March 31  ===
 
=== 2010: March 31  ===
  
Present: Liz, Jess, Barbara, Jim, Carrie, Elin<br>
+
Present: Liz, Jess, Barbara, Jim, Carrie, Elin<br>  
  
Announcements:<br>
+
Announcements:<br>  
  
*Circ has arranged an RSS workshop - watch the blog for details
+
*Circ has arranged an RSS workshop - watch the blog for details  
*Office 2007 is now recommended for use at Midd. &amp;&nbsp;is available for download. Jim will post details to the blog.
+
*Office 2007 is now recommended for use at Midd. &amp;&nbsp;is available for download. Jim will post details to the blog.  
*Elin has updated the team goals document &amp; will move this document to Basecamp.
+
*Elin has updated the team goals document &amp; will move this document to Basecamp.  
*Jess is going to moonlight at the Digital Archives team!!
+
*Jess is going to moonlight at the Digital Archives team!!  
*Elin is asking all members to consider if they'd want to stay on any on-going version of this team.
+
*Elin is asking all members to consider if they'd want to stay on any on-going version of this team.  
 
*We have 6 staff &amp; 9 student responses to our web survey so far. Elin we e-mail LIS staff &amp; student workers with a reminder.
 
*We have 6 staff &amp; 9 student responses to our web survey so far. Elin we e-mail LIS staff &amp; student workers with a reminder.
  
Agenda items:
+
Agenda items:  
  
*Silverback usability testing questions. Liz edited the questions during the discussion. See [https://123.writeboard.com/3bf758a9f4a0ad005 Basecamp writeboard] for latest versions.
+
*Silverback usability testing questions. Liz edited the questions during the discussion. See [https://123.writeboard.com/3bf758a9f4a0ad005 Basecamp writeboard] for latest versions.  
*5 second testing has been determined to be unsuitable for our needs. Carrie will conduct further testing of Usabilla instead. (note if we'd used Survey Monkey, we could have had an all ape software suite)
+
*5 second testing has been determined to be unsuitable for our needs. Carrie will conduct further testing of Usabilla instead. (note if we'd used Survey Monkey, we could have had an all ape software suite)  
*All team members are asked to check the e-mail format for soliciting usability test subjects. [https://123.writeboard.com/eda76fe450bc37fa7 Writeboard here.]
+
*All team members are asked to check the e-mail format for soliciting usability test subjects. [https://123.writeboard.com/eda76fe450bc37fa7 Writeboard here.]  
 
*Elin will check out a faculty Mac laptop and get Silverback installed. Current plan for testing - Carrie, Jess, Barbara (anyone else?) will conduct 20 - 30 individual tests during the period April 12th - 23rd. Elin will look into using an empty ref office to conduct the testing.
 
*Elin will check out a faculty Mac laptop and get Silverback installed. Current plan for testing - Carrie, Jess, Barbara (anyone else?) will conduct 20 - 30 individual tests during the period April 12th - 23rd. Elin will look into using an empty ref office to conduct the testing.
  
=== 2010: April 7 ===
+
=== 2010: April 7 ===
  
Present: Liz, Barbara, Elin, Ian, Doreen, Jess, Jim, Carrie<br>
+
Present: Liz, Barbara, Elin, Ian, Doreen, Jess, Jim, Carrie<br>  
  
Announcements:<br>
+
Announcements:<br>  
  
*All campus email about usability testing was sent out. Barbara has already received several replies, including one from Faculty.
+
*All campus email about usability testing was sent out. Barbara has already received several replies, including one from Faculty.  
*Jim will soon be making a post about Office 2007 support on the blog.
+
*Jim will soon be making a post about Office 2007 support on the blog.  
*April 28th 3:00-4 PM will be an RSS workshop hosted by the Circulation Services team in LIB 105 with Alex Chapin.
+
*April 28th 3:00-4 PM will be an RSS workshop hosted by the Circulation Services team in LIB 105 with Alex Chapin.  
*Goals are up on basecamp and will be posted to the Project Directory.
+
*Goals are up on basecamp and will be posted to the Project Directory.  
 
*Liz, Jess and Elin will be out next week. Ian will be out the following week. There will be no all team meeting next week, but the people working on Usability Testing may meet.
 
*Liz, Jess and Elin will be out next week. Ian will be out the following week. There will be no all team meeting next week, but the people working on Usability Testing may meet.
  
Agenda items:<br>
+
Agenda items:<br>  
  
*LIS blog. Barbara advocates allowing LIS to set up a "private blog" as she suspects that there will be very little posted there and we can use this to prove our point about the utility of a private blog for LIS.
+
*LIS blog. Barbara advocates allowing LIS to set up a "private blog" as she suspects that there will be very little posted there and we can use this to prove our point about the utility of a private blog for LIS.  
**Do we have any stats comparing the current LIS blog with the old LISt blog? Ian will follow up and check on this.
+
**Do we have any stats comparing the current LIS blog with the old LISt blog? Ian will follow up and check on this.  
**Comment from Managers meeting: "Blog is not very interactive".
+
**Comment from Managers meeting: "Blog is not very interactive".  
**Jess: we should not assume that this is the end-all-be-all of communications and we should try other methods.
+
**Jess: we should not assume that this is the end-all-be-all of communications and we should try other methods.  
***From the survey: people don't understand the benefit of the information coming from the blog.
+
***From the survey: people don't understand the benefit of the information coming from the blog.  
**If LIS is going to set up a private blog, this team does not need to be a part of setting that up.
+
**If LIS is going to set up a private blog, this team does not need to be a part of setting that up.  
**Liz: we need to make sure that people having the training and tools to use the blog before moving on to other schemes.
+
**Liz: we need to make sure that people having the training and tools to use the blog before moving on to other schemes.  
**Doreen: people were spoiled by email because there were summaries and links to articles for more information.
+
**Doreen: people were spoiled by email because there were summaries and links to articles for more information.  
**Barbara: we should have a time at an all LIS meeting where we discuss communication within LIS. The requirement to stay informed of the work within LIS should be stated to employees.
+
**Barbara: we should have a time at an all LIS meeting where we discuss communication within LIS. The requirement to stay informed of the work within LIS should be stated to employees.  
**Ian: make recommendations to the area directors that we (1) have a discussion at an all LIS meeting to discuss LIS communications, and (2) if you want to set up a private blog, go for it. Our team will continue to offer support and training for using these tools
+
**Ian: make recommendations to the area directors that we (1) have a discussion at an all LIS meeting to discuss LIS communications, and (2) if you want to set up a private blog, go for it. Our team will continue to offer support and training for using these tools  
**Team decision: we will post these recommendations to the blog and solicit feedback. This item is off the agenda for a month.
+
**Team decision: we will post these recommendations to the blog and solicit feedback. This item is off the agenda for a month.  
*Usability testing
+
*Usability testing  
**Jim will talk to Joe about having Ben help out with Usability Testing.
+
**Jim will talk to Joe about having Ben help out with Usability Testing.  
**Testing timeline: we are on target
+
**Testing timeline: we are on target  
**Ian and Barbara will look at the Usabilla questions and come up with screenshots with 5 questions for each area
+
**Ian and Barbara will look at the Usabilla questions and come up with screenshots with 5 questions for each area  
**Jim will look at that section as well and add questions for his area
+
**Jim will look at that section as well and add questions for his area  
*Survey Report
+
*Survey Report  
**Barbara has created another Writeboard with links to summaries of both surveys. Barbara will make spreadsheets available.
+
**Barbara has created another Writeboard with links to summaries of both surveys. Barbara will make spreadsheets available.  
**The majority of responses said that the site has improved over its past version.
+
**The majority of responses said that the site has improved over its past version.  
**Team members should comment on the results or add other observations on the Writeboard that Barbara has started.
+
**Team members should comment on the results or add other observations on the Writeboard that Barbara has started.  
**Ian will compare results from current and past survey and share results with the group.
+
**Ian will compare results from current and past survey and share results with the group.  
 
**Noted: 0 survey responses from LIS Administration (well, 1 who marked themselves as 'AD' in the workgroup section
 
**Noted: 0 survey responses from LIS Administration (well, 1 who marked themselves as 'AD' in the workgroup section
  
=== 2010: April 21 ===
+
=== 2010: April 21 ===
  
Present: Jim Barbara Carrie Doreen Jess Liz<br>
+
Present: Jim Barbara Carrie Doreen Jess Liz<br>  
  
*Thanks to Jim for posting on the Blog about MS Office 2007
+
*Thanks to Jim for posting on the Blog about MS Office 2007  
*Silverback testing discussion
+
*Silverback testing discussion  
**Getting more students from LIS Student employees
+
**Getting more students from LIS Student employees  
**How are we going to use the results? Combine individual findings and create general guidelines for persons responsible for content
+
**How are we going to use the results? Combine individual findings and create general guidelines for persons responsible for content  
**Technical issues with Silverback and storing the video files mostly resolved
+
**Technical issues with Silverback and storing the video files mostly resolved  
**Is debriefing okay for our testers? i.e. helping them understand the things they find confusing-yes, it's okay
+
**Is debriefing okay for our testers? i.e. helping them understand the things they find confusing-yes, it's okay  
**Searching is still an issue for many users contacting the Helpdesk, but we've seen an improvement when it switched to the Google search (away from local)
+
**Searching is still an issue for many users contacting the Helpdesk, but we've seen an improvement when it switched to the Google search (away from local)  
**We're relatively on-track
+
**We're relatively on-track  
*Future of the team: Elin will post the AD email response to Basecamp
+
*Future of the team: Elin will post the AD email response to Basecamp  
*Usabilla finalizing questions and inputting the screenshots (Ian was tasked with starting this) Barbara will take a look and will see what Ian has done so far
+
*Usabilla finalizing questions and inputting the screenshots (Ian was tasked with starting this) Barbara will take a look and will see what Ian has done so far  
*LIS Staff survey comments: Barbara will extract and put in a spreadsheet stored in middfiles and will put the pathway to this in Basecamp
+
*LIS Staff survey comments: Barbara will extract and put in a spreadsheet stored in middfiles and will put the pathway to this in Basecamp  
 
*LIS Blog (mini-note!) seems like there's a sense that it'll stay in one blog form for the time being
 
*LIS Blog (mini-note!) seems like there's a sense that it'll stay in one blog form for the time being
  
=== 2010: April 28 ===
+
=== 2010: April 28 ===
 +
 
 +
Present: Barbara, Elin, Carrie, Ian, Jess, Liz<br> Notes: Ian
 +
 
 +
*Announcements
 +
**Jess is done with her internship and is in the last week of classes for her MLS
 +
*Revised LIS Website Team to be formed this summer
 +
**Recommendation (from Elin): four people is probably enough for this team
 +
**Recommendation (from Barbara): continuing members from the current team is preferable
 +
**Recommendation (from Ian): if the new team will be focused on refresh workflow, our team will spend the remainder of our time working on the usability review
 +
**Recommendation (from Carrie): membership of the new team should be based on sections of the website, not LIS areas
 +
*Usability Testing
 +
**Jess has three more students to work with
 +
**We will have about 20 usability reviews completed through Silverback
 +
**Jess will transfer the spreadsheet to Google Docs
 +
**Silverback testing to be completed by next week
 +
*Usabilla
 +
**Team will review the questions on the Usabilla Writeboard
 +
**Ian will create the tests in Usabilla tomorrow morning after the team's review
 +
**Ian will add widgets from Usabilla to each of the sites under review
 +
*Usability Analysis
 +
**We should create a heading for each area of the site, plus the blog, plus the wiki with recommendations under each
 +
**We'll create this in Google Docs
 +
**Some discussion of what platforms we're using to do this
  
Present: Barbara, Elin, Carrie, Ian, Jess, Liz<br>
+
=== 2010: May 5  ===
Notes: Ian
 
  
* Announcements
+
Present: Barbara, Elin, Carrie, Ian, Jess, Liz, Ian, Jim
** Jess is done with her internship and is in the last week of classes for her MLS
 
* Revised LIS Website Team to be formed this summer
 
** Recommendation (from Elin): four people is probably enough for this team
 
** Recommendation (from Barbara): continuing members from the current team is preferable
 
** Recommendation (from Ian): if the new team will be focused on refresh workflow, our team will spend the remainder of our time working on the usability review
 
** Recommendation (from Carrie): membership of the new team should be based on sections of the website, not LIS areas
 
* Usability Testing
 
** Jess has three more students to work with
 
** We will have about 20 usability reviews completed through Silverback
 
** Jess will transfer the spreadsheet to Google Docs
 
** Silverback testing to be completed by next week
 
* Usabilla
 
** Team will review the questions on the Usabilla Writeboard
 
** Ian will create the tests in Usabilla tomorrow morning after the team's review
 
** Ian will add widgets from Usabilla to each of the sites under review
 
* Usability Analysis
 
** We should create a heading for each area of the site, plus the blog, plus the wiki with recommendations under each
 
** We'll create this in Google Docs
 
** Some discussion of what platforms we're using to do this
 
  
[[Category:LIS Website]]
+
[[Category:LIS_Website]]

Revision as of 10:34, 5 May 2010

This is the space that the LIS Website Team will use for documentation and note taking.


Team Charge

  • To create a brand new LIS web presence that has the following characteristics: is easy to find (things,) is easy to use, is easy to maintain, is user centric, has more self-service functionality.

Team Priorities

  • Involve end users: develop & test [Beta test 11/09, Public beta test 12/09, Public launch 1/04/10]
  • Develop LIS staff workflow, content management, protocol procedures & apply to new web presence [Test 11/09, In place 12/09](staff workflow charge clarified Nov 09 - Defining who is authorized to manage/edit the parts of the LIS site. How is content to be reviewed and changed & regular update encouraged?)
  • Assess/evaluate new LIS web presence ( involve end users) [April 2010 & ongoing]
  • Develop “site-refresh” strategies [Aug 2010]

Team Vision

We are creating a web site with intuitive navigation, easy access to services and resources, inviting interfaces, and a workflow that allows simple maintenance.

Planning Stages

  • Define a Compelling Vision What do we want to accomplish? Why? WIIFM (what's in it for...)
  • Define measurements/metrics What does success look like? What metric will define our success?
  • Building Coalition - Creating a Marketing Plan Who do we need to engage early on? We need to engage early for: information and understanding, input, resources (actual and potential)
  • Action Plan to Achieve Key Deliverables Tasks to be accomplished? Who is accountable? Delivery Time?


LIS Website Metrics

Define measurements/metrics

  • What does success look like?
  • What metric will define our success?


Quantitative

  • Reduced support requests
  • Fewer clicks to find information
  • It is clear what is clickable
  • Reduced reliance on other communication systems
    • Fewer group emails
    • Fewer PDF newsletters and print materials
    • Unified documentation
  • More frequent updates of news content
  • Fewer dead links, reduced need to check for dead links
  • Usage analytics analysis
  • Subscription rate for syndicated content (feeds)
  • Do we want to measure how we respond to feedback, for example do we want to set a goal for ourselves that all suggestions will receive responses (even generic) within a certain amount of time? Macfarlane, Carrie Miyoshi
  • Consistent page elements, naming schemes, navigation and directional, elements, paths

Qualitative

  • User satisfaction survey (on-going, periodical) - is just doing a survey enough for us, or are we looking for a certain level of satisfaction in the result? Of course we probably will never achieve 100% satisfaction. Do we want to set a target somehow, one that is linked to the ratings on the survey (eg, at least 50% of users are at least "somewhat satisfied")? Macfarlane, Carrie Miyoshi
  • "Was this page helpful?" "Rate this page" at the bottom of content


Building Coalition - Creating a Marketing Plan

  • Who do we need to engage early on?
  • We need to engage early for: information and understanding, input, resources (actual and potential)


Action Plan to Achieve Key Deliverables

  • Tasks to be accomplished?
  • Who is accountable?
  • Delivery Time?


Project Timeline

2009

June 2009

  • Team Training

July 2009

  • All of July: Team Planning - develop vision, define measurements and metrics, build coalition and create a marketing plan, develop the action plan to achieve key deliverables
  • 7/17 - Web Makeover Kickoff with Department Contact (another session will be scheduled for those unable to attend)
  • 7/20 - Send out LIS staff survey
  • 7/22 - Deadline for LIS staff survey
  • 7/22 - Discuss what stats we want to get (Info Desk, Help Desk, Metrics, etc.). Start getting stats from old site in order to make comparison to new.
  • 7/23 - Design Unveiling White Whale will share their designs for the new site at McCullough Hall, 1pm. 
  • Week of 7/27 - Web Makeover - Project Manager meetings/training
  • 7/30 - Evaluate information architecture and corresponding list of LIS website contacts for current LIS site

August 2009

  • 8/3 - Web Makeover Meetings with Primary Contact and Project Manager
  • 8/5 - Complete gathering MOST input (more will trickle in throughout process)
  • 8/10 - Web Makeover Follow-up meetings with Primary Contact and Project Manager - discuss and respond to WW recommendations for IA/Content
  • Week of 8/17 - Web Makeover - check in - roles and timelines are due
  • 8/17 - Present roles and timelines for LIS at web project managers meeting
  • 8/20 – Proposed recommendations presented to sponsor
  • 8/26- Map out new information architecture
  • 8/27ish - Share new (proposed) IA with sponsor
  • 8/27 - Assign project managers for LIS content, create folder structure for content in middfiles
  • 8/31 - Initial discussion with primary contacts should happen by this date

Sept 2009

  • 9/1 (continuing) - Build non-drupal content as time allows
  • 9/1 - Middlebury finalizes homepage (+ top-tier) designs
  • 9/2 - Work with LIS website contacts to complete Web Makeover Workbooks (and incorporate supplemental sources of input) for LIS website. Set freeze date/s for changes/additions to current LIS site.
  • Week of 9/7 - Web Makeover Start Building Site (Content Build Out)
  • Week of 9/14 - Web Makeover Follow-up meetings with Primary Contact and Project Manager
  • 9/15 - Finalize platform improvement recommendations
  • 9/28 - Web Makeover Check-in with Project Manager
  • 9/28 - Drupal Training for Project Managers

October 2009

  • 10/1 - Design staff workflow for moving content. Get feedback.
  • Week of 10/6 - Web Makeover - completed workbook due
  • 10/6 - Complete LIS web redo workbooks
  • 10/6 - Start LIS content build out
  • 10/11 Deliverable: Test LIS staff work flow and content management, protocol procedures
  • 10/11 - Drupal Training for all CMS users
  • Wiki and blog training for LIS primary content?

November 2009

  • 11/09 - Web Makeover Check-in with Project Manager
  • 11/09 Deliverable: Test in place for LIS staff workflow, content management, protocol procedures & apply to new web presence

December 2009

  • 12/09 Deliverable - Develop LIS staff workflow, content management, protocol procedures & apply to new web presence
  • 12/15 Public beta test - beta launch
  • 12/15 Deadline for adding content to new LIS website


2010

January 2010

  • 1/04 Web Makeover - Middlebury Site Launches
  • 1/8 - Web Makeover Celebration

April 2010

  • 4/10 & ongoing Assess/evaluate new LIS web presence ( involve end users)

August 2010

  • 8/10 Develop “site-refresh” strategies


Scope

Resources


  • Workflow/Guidelines for use of social media
  1. http://socialmediagovernance.com/policies.php
  • Style Guide from College Communications
  1. Style Guide info
  • Blogs
  1. Docs on posting, an intro, etc., from the Wordpress site
  2. Tutorials and readings on blog use: Anatomy of a blog, some blog history, etc.
  3. Tons of video tutorials!
  4. Subscribing to Wordpress Categories and Feeds via Google Reader: Add /feed to the end of the URL
  • Wikis
  1. Docs on editing and a useful cheat sheet. Tutorial from Wikipedia
  2. Tutorials and readings on wiki use: wiki world (has podcasts), an article from Educause, etc.
  • Readings
  1. How Do You Measure Web Site Success? - If you can ignore the ads, I think you'll find a few good ideas for us to consider Macfarlane, Carrie Miyoshi
  2. http://www.libsuccess.org/index.php?title=Website_Design - geared to library web sites, includes examples & useability tips (it's a wiki just like ours!)
  3. Use of PDF in accessible documents - The rest of the WCAG+Samurai site is a good read too.
  4. Library terms evaluated in usability tests and other studies (Thanks, Mike L.!)
  5. Organizing Your Campus IT Security Website
  6. Usability testing of an academic library Web site: a case study - Brenda Battleson, Austin Booth and Jane Weintrop, The Journal of Academic Librarianship, Volume 27, Issue 3, May 2001, Pages 188-198
  7. Discovering how students search a library Web site: A usability case study - S Augustine, C Greene, College and Research Libraries, 2002.  Main points:  Students don't understand library jargon.  They are more likely to use 'search' than menus.  If they don't find what they want right away, they want to ask someone where it is.
  8. Usability of the academic library Web site: Implications for design - L McGillis, EG Toms,College and Research Libraries, 2001.  Main points: Students don't know where to begin when presented with a series of menus and content categories.  Library jargon is meaningless. Students performed best when faced with menu structures that had sixteen items on the first level and thirty-two items on the second level (as opposed to a menu structure with the majority of items on the first of two levels, or a menu structure with items equally distributed throughout three levels).


  • User needs analysis and assessment tools (pdfs... I know, I know...)
  1. Gathering evidence
  2. Setting up the UNA
  3. UNA methods


  • Books
  1. Don't Make Me Think: A Common Sense Approach to Web Usability - Steve Krug
  2. Designing the Digital Experience - David Lee King
  3. Library 2.0: A Guide to Participatory Library Service - M Casey/L Savastinuk
  4. The Academic Library and the Net Gen Student - S Gibbons
  5. Making library Web sites usable: a LITA guide - Lehman, Tom, and Terry Nikkel. 2008.
  6. Web site design with the patron in mind: a step-by-step guide for libraries - Davidsen, Susanna, and Everyl Yankee. 2004.


  • Sites to check out
  1. Colby Library (Colby has set up its Library page using Libguides)
  2. Williams portal
  3. Bowdoin portal
  4. ASU "Most-used resources" example
  5. BYU front page search
  6. Cornell front page search
  7. University of Washington Libraries
  8. Cal State San Marcos Drupal example
  9. U North Carolina
  10. Temple Libraries (old version)
  11. North Carolina State University Libraries
  12. [1] - optimized for mobile
  13. Syracuse University Library (old version)


What do we need on a LIS home page?

  • Systems, Services Availability/Outages
  • Google search of website - all Midd, just LIS
  • Hours for today
  • News / Featured resource or service / New acquisitions
  • Multiple OPTIONS for user to communicate with LIS
  • Exhibits and events in the Libraries
  • Easy access to user documentation for self-service; service during closed periods
  • Space - study rooms, room reservations, classrooms, labs, computing info
  • Calendar of training events, workshops, learning opportunities
  • catalog, reserves, journals, media searches (portal like http://library.williams.edu/ or http://library.bowdoin.edu/ )
  • contact live help
  • search documentation - researching, citing etc.
  • Questions for team to decide:
    • How to get ideas, needs, input from interested LIS staff?
    • Where to get good ideas from other organizations?
      • What do we need on a LIS home page? OR do we want library & tech home pages (with big link to “about LIS” on both)?
    • Overall “look and feel” constraints? - maximum freedom for all contributers.
  • A CMS-based site for the Library, which will contain links to subject guides, reference resources, journals, and digital collections. The Library site will be built as a stand-alone site in Drupal with a new set of design templates that adequately allow for free presentation of this information.
  • An expansion of the current LIS Wiki to include all Help related content. We will migrate the remaining content out of the current CMS, PDF documents, and knowledge base. We will work to integrate links to this information into our help systems. Additionally, we will make authorship of this information available throughout the organization and offer training and support for LIS staff to update the content relevant to their work.
  • Focus intensely on SEARCH: A portal to search all of the collections and databases within LIS. A long-term goal in this area will be federated search, but to begin we will create a unified area where users can view all of the collection offerings and perform basic and advanced searches of them.
  • A place to interact with LIS. This will be achieved through consolidation of the various LIS blogs, feedback forms, request forms, comment submissions and staff directories. The goal is to have a *single* blog for LIS with all staff as authors. This area of our site will also provide an appropriate place to present material on the organization, direction, and policies of LIS.
  • Interactive - LIS presence on social media sites? Monitor LIS in social media spaces?
  • Easy front end acces to communication options - email, phone, in person, blog, microblog, wiki, texting, tagging, commenting, posting etc.
  • Marketing videos of services, resources etc.
  • Mobile display - readable by mobile devices
  • Are there ADA issues we need to consider?
  • LIS - who are we? LIS mission statement - We bring knowledge to you. We help you explore, use and contrubute to it as you engage the world.
  • Easy, quick feedback options to answer "how are we doing?".  Include our responses too.
  • Keep it simple; eliminate clutter
  • No lis lingo, acronyms, etc.
  • Action words -
  • Keep the user at the center of the design and architecture
  • Hyperlinks - underlined; different color and style; changes after clicking
  • Reduce number of clicks needed to get to content - Create pages that you can DO stuff on. Eliminate pages full of long lists.
  • Ensure that pages are kept up-to-date. Include authorship/contact info and date of last revision on each page so that if someone finds info that’s no longer true they can either: 1) try to identify the author and tell them directly, or 2) tell the web team, who will figure out who the author is.
  • Project directory - What are we working on and what have we accomplished to date.
  • "How to" list.  For example, how to reserve a group study, how to find articles, how to create a blog.
  • Shortcuts to most-used library resources (see http://lib.asu.edu/)
  • Search various collections of databases from front page (see http://www.lib.byu.edu/ and http://www.library.cornell.edu/)
  • I'm not sure how this will go over with everyone -- but I'd love to have a logo to "brand" all Midd Library pages and links.  It would make it so much easier to provide continuity from one section to the next.  Logos can say a lot in a small space.  Many other libraries have a logo...


Workflow and Protocol Procedures

  • Develop LIS staff workflow, content management, protocol procedures & apply to new web presence


Training, Workshop and Learning Ideas

  • Multiple options for learning about navigating the site to access LIS resources and services
  • Quick tips with the bare minimum of text - details and long documentation a step away


Primary Contacts Information

See the LIS Primary Contacts Information article.

Recommendations

See the LIS Website Recommendations article.


LIS Website Information Architecture

See the LIS Website Information Architecture article.


All Things LIS One-Blog

CATEGORIES - will start with this set of categories - broad themes to organize posts and give user subscription choices

External Audience

  • Term TBD


Areas and Workgroups - use name of area as the category and use functions of the work area as tags (audience is mostly internal)

  • Academic Consulting Services - research support, instruction, liaison
  • Collection Management - aquire, catalog, preserve, maintain resources
  • Enterprise Technology & Infrastructure - programming, systems, reporting, network
  • LIS Administration - budget, planing, policy, assessment, strategy
  • User Services - technology help and support, borrowing and lending, computing support, computing labs, media and event support


Institutions

  • Middlebury
  • MIIS
  • Language Schools
  • Schools Abroad
  • Bread Loaf School of English
  • Bread Loaf Writers' Conference
  • MMLA

Teams

  • Area Directors
  • Curricular Technology
  • Digitization
  • LIS Website



TAGS - user generated; change frequently; narrows the 

  • Seeded by team Existing LIS dept blog categories - changed to tags
  • Benefits of tags


TIPS AND TOOLS - and guidelines for writers; staff workflows; training

  • Public blog - seen by all; all LIS staff have editor access; all LIS staff contribute regularly
  • Users (external or internal) can choose to follow all or selected categories
  • Existing (or future) group/depts may choose to have private blogs - but the One-Blog will be THE place for easy dissemination of work activity, news and events - to facilitate timeliness, relvancy and transparency of our work and communication within LIS and with our external community; THE place for LIS staff to stay up to date and engaged; THE place for LIS Admin to keep LIS staff informed. THE place for our users to stay up to date with changes to policy and services etc., updates, news, events - whatever they opt to follow. Write regularly
  • Benefits of public blog
  • Who sees my blog
  • When would you want to choose a private blog
  • How to reach the right audience
  • Who is your audience
  • Multiple authors and voices = relevant and regularly followed blog
  • Tag posts with relevant search terms
  • Select at least one category - benefit of selecting a category
  • Blogetiquette
  • Media - images and clips- how to


Wiki Main Pages

New main pages for this wiki (under construction)

Main Page Faculty/Staff

Main Page LIS Staff

Main Page Students

Main Page Visitors/Guests


Meeting Notes

2009:  June 24

Present:  Elin Waagen, Jess Isler, Ian McBride (time-keeper), Carrie Macfarlane (note-taker), Liz Whitaker-Freitas, Jim Beauchemin, Barbara Merz.


1.  Questions for the team - Jim and Carrie


  • Jim had some questions about roles and communication methods.  He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
  • Carrie shared what she'd done to get caught up on team training.  She asks that team members tell her when she does something contrary to what the team learned/agreed to during training.


2.  Decide on a platform to facilitate documentation and communication 


  • What will we use this platform for?  Communication within the team and with our users/constituents.
  • What are our options?  Basecamp, Microsoft Project, Groove, MediaWiki, Wordpress, Drupal (not yet)
  • We discussed the merits and drawbacks of the options.
  • We decided by majority:  At least in the beginning, we will use MediaWiki for meeting notes and documentation, and Wordpress for communication among ourselves and with our users/constituents.  We may use email to direct users/constituents (and team members) to Wordpress.  We may use email to communicate within the team about mundane or ephemeral matters like absences at meetings.  We can revisit this decision in the future by adding it to a meeting agenda.


3.  Team Protocols


  • Team protocols that were agreed upon during team training were listed:

a. Meet weekly - adjust frequency as needed if there are no/more agenda items.

b. Set agenda ahead of time

c. Shared responsibility to generate agenda items, agenda facilitated by team leader

d. Agenda items will have specific time and sponsor

e. Time keeper

f. Note taker-- I think this responsibility should rotate alphabetically.  If someone can't take notes when it's his/her turn then that person can ask for a substitute.  <a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 13:13, 30 June 2009 (UTC)


f1. Meeting time is a valuable resource. Team members will learn to use it wisely. Team members commit to being up to date on blog and wiki postings before each meeting. [Barbara 6/26]

g. Use shared platform for communication and development of documentation

h. Timely (define?) posting of meeting notes

i. Time at end (5-10 min) for discussion or overflow or to set next meeting agenda

j. If unable to attend, responsible for getting caught up

k. Open honest dialogue (with tact)

l. Simple majority rules

m. Agreement - to ensure success (from training)

n. Authentic and candid dialogue

o. Honest - with tact

p. Open to others - come to agreement

q. Make the decision and move on - or fix it and move on

r. Depersonalize and on board

s. Participate, engage, share point of view 1X

t. Focus on and value time over story

u. Informed, fast decisions

v. Confidential

w. Take notes

x. Take responsibility

y. Volunteer, be willing

z. Right to expect candor and openness

aa. Own it

bb. Be present

cc. Be on time (late + good story = on time)

dd. Outlook calendars up to date (for scheduling purposes)

ee.  Meetings will start on time.  Team will wait no longer than 5 minutes for late arrivals. <a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 13:14, 30 June 2009 (UTC)


3.  Vision Statements


  • Team will meet on Th Aug 25 to develop vision statement


4.  Future agenda items


  • Other potential team protocols were mentioned in conversation as team members arrived at the meeting.  It was suggested that these potential protocols be brought up during the time allotted for discussion of team protocols.  Because we needed to plan for drafting a vision statement, we didn't have time to discuss protocols.  Therefore, perhaps we should plan to discuss team protocols in a future meeting.

Other items on today's agenda for which we didn't have time (we had too many other important issues to resolve!):


  • Define measurements/metrics (10 min)What does success look like?What metric will define our success?
  • Building Coalition - Creating a Marketing Plan (10 min)Who do we need to engage early on?We need to engage early for: information and understanding, input, resources (actual and potential)
  • Action Plan to Achieve Key Deliverables (10 min)Tasks to be accomplished?Who is accountable?Delivery Time?


5.  Action items


  • Jim had some questions about roles and communication methods. He will meet with Doreen to review what he missed on Thurs afternoon and Fri morning
  • Ian will create a blog and a mediawiki page -- done!
  • Liz will create Outlook group for LIS web team
  • We will meet with our sponsor (Jeff) or sponsor-backup (Mary)
  • We will meet elsewhere from time-to-time (Voter East, Music Library, Armstrong Library)

<a href="User:Carrie Macfarlane">Macfarlane, Carrie Miyoshi</a> 19:48, 25 June 2009 (UTC)

2009:  June 25

Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz

1. Updates

  • Elin is updating Jeff R./Mary B. on team meeting highlights
  • Elin will create a post for LISt blog about existence of the LIS Website Project Blog.

2. Vision Statement Work

  • Discussion of bringing out common themes or words, creating a tagline (subtitle) for the blog, tags/keywords, discussion of what the statement really should be

[asides]

  • There’s a Wordle <a href="http://www.wordle.net/gallery/wrdl/967852/web_team">diagram</a> of our team vision statements on the blog; discussed what WORDLE is—what it represents and where it comes from: <a href="http://www.wordle.net/">Wordle</a> "Wordle is a toy for generating “word clouds” from text that you provide. The clouds give greater prominence to words that appear more frequently in the source text."
  • Discussed scheduling a projector room for future meetings

[back to vision statement discussion]

3. End of meeting discussion

<a href="User:Jessica Isler">Jess Isler</a> 17:13, 25 June 2009 (UTC)

2009: July 1

Present: Barbara, Carrie, Elin, Ian, Jess, Jim, Liz

1) Updates

  • keep Elin & team posted about absences via Outlook calendar, meeting schedule
  • there was a managers meeting on 6/26 at which the manager expectations as produced at the team training were discussed (vigorously). There was pretty good buy-in, with the understanding that things will evolve.
  • Elin met with Jeff & showed him the blog & wiki. Jeff clarified what is our charge & what our deliverables. Suggested we make our vision shorter. Shorter form of vision as above unanimously approved.
  • Ian suggested adding a resources page to this wiki - done, see above.

2) Protocols

After short discussion, updated protocols, as below in wiki were approved.

3) Define measurements/metrics. What does success look like? What metric will define our success?

Started discussion of this topic. Need for definitions of following:

  • scope of project
  • core requirements
  • metrics

Ian listed metrics currently defined by the larger web makeover project.

4) Scope

Started discussion of project scope. See details in this blog above.

5) For next meeting

Note taking duties will rotate alphabetically. Jim's up next!

Barbara learned a valuable lesson in entering these notes - there is a SAVE button at the bottom of the wiki edit screen if only one uses the correct (outer) scroll bar.

2009: July 2

Present:  Liz, Ian, Jim, Barbara, Jess, Elin, Carrie


Scope discussion:

  •      Ian posted a very good list of items on our page the clearly itemizes our areas of focus when it comes to our project scope (see Scope section). 
  •      We discussed the proposed Scope list and we feel at this time that the proper items are listed.

Criteria discussion:

  •      We immediately started to discuss the criteria that will be used:

         -  We will document everything which is internal to our effort on the Wiki; a clear and concise communication plan is needed; 
         -  We agreed to strive for a reduction in PDF and Doc objects which are currently embedded in many areas of the web site.  An exclusion to the reduction 
            of PDF objects would be in the preservation area only.
         -  Reduce or eliminate external links -- Could you explain a little more here?  I don't remember this point, sorry! Macfarlane, Carrie Miyoshi
         -  We must improve the Search engine
         -  Promotion of the 'Blog' for the purpose of discussion and communication; internal as well as external communication.
         -  Propose 1 blog opposed to 20+ blogs - consolidation; need better catogorization of content!  One subscription to 'the' blog and then the user can navigate to desired area(s)
         -  Make the tools and services easy to find and access!!
         -  Promote other tools and utilities - let user choose (appropriate tools only)
         -  Simple, Intuitive, 3 click away interface
         -  Self-Service

Additional notes:

The team expressed questions and concerns regarding the Wiki and its ease of use.  The team agreed that we are now emersing ourselves into the very areas we are charged to
clean-up or re-structure.  We also came to the conclusion that whatever we put forward for a web site that it will be a bahavior change required for all user.  Training and general
prepareness will be very important and that we will need to integrate these things along the way through this restructuring process.  We also spoke about the importance of partnering
with other teams so that we can truly understand the requirements of the new LIS web site.


Next meeting:

  •    Ian will present the results of the Focus Group and survey results in our next meeting
  •    Jim and Barbara will be on vacation for our next meeting


2009: July 8

Present: Elin, Jess, Ian, Carrie, Liz and Doreen

Announcements and Updates:

  • Joe Antonioli will meet tomorrow with the Web Makeover Design/IA group and will pass our progress along. We need to invite Joe to a meeting to find out where the LIS Webpage project fits into the larger Web Makeover project. Robert Keren, Communications and Bryan Carson should also be invited.
  • Elin tweaked the wiki – planning stages are now included
  • Best practices – when to use the wiki and blog. Wiki will be the resting place for documents and the blog will be used for discussion purposes.
  • There is a page limitation for the main wiki page. We should consider removing the minutes from the main page and create additional pages with links to the main page.
  • Including names on the wiki when commenting is useful.
  • Discussion tab- use for discussion
  • Midd-Google login issues – send Ian your Gmail address and Ian will forward over the “DIY Guide to Reviewing and Revising Web Site Navigation and Content” document to review

Focus Group Analysis

  • Who was being surveyed? Mostly combined groups of staff and students and communications. There were not results from actual LIS focus groups. Jeff will send some documentation to the committee from the LIS focus groups.
  • List on wiki things to have on the webpage. Are there any gaps? What do we do about adding tagging as a bullet point? Do we want to come up with our own vocabulary?
  • The focus group survey identified the need for tagging, RSS feed….(Ian, please fill in others)

What do we need on the LIS webpage?

  • Consider: keeping pages up-to-date – figure out how to keep updated, author and date stamp markers. Include “How-to” features and reduce clicks
  • Combine metrics with features on each page? Some can be combined, others need discussion
  • Add service status for service and system outages
  • Add Space, Computing and Conference link

- Update of R25 will give us an opportunity to show a more comprehensive list on our page. Discuss with Bryan about showing room availability.

  • Formalize the rest of the list at next week’s meeting

Develop survey questions – add to tomorrow’s meeting

DIY workbook

  • Feedback and answers

(If you could only reach one particular audience with your website, who would it be?) LIS staff/faculty and students - staff – organizational communications and services - students – 8000 pages connected to the LIS website, mostly related to resource guides, subject guides and journals - students are primary, staff/faculty secondary - Alter the question to read: who are your primary users, not just one.

  • Questions are designed to address much smaller areas than LIS. We can reformat these questions in the survey and re-segment by LIS department
  • Advice on Mary’s questions? Add process for updating their content. How do you know when it needs to be changed? How important will these be 2 months from now? How to track questions they get on content? Is there a way to date stamp info? Does this info reside in additional documents or in other systems?

We need to closely integrate our work with training and help facilitate better and more efficient workflow.

All CMS pages need to be re-written and are not transportable to Drupal.

We need to help people write content for web – writing style training. Writing style should be conversational.

Action Items:

  • Cancel Joe A. for tomorrow’s meeting
  • Jim and Barbara will still be out tomorrow – go ahead with the survey questions
  • Add discussion of timeline and marketing plan to agenda
  • Bring 5 survey questions to the meeting
  • Jess will post assessment summary on blog.

2009: July 9

Present: Carrie, Doreen, Elin, Ian, Jess (notes), Liz

  • Survey for LIS staff

Ian created a key survey prior to meeting with members’ input to date
Link and login for survey is posted privately to blog
Discussion of what we want to get from the survey responses/hashing it all out
We cut it down to 11 questions from 18 or so!
Please look it over, make suggestions for edits, take the survey. Time yourself. Please inform the group of your timing.

  • Target

Send out the survey on Monday 7/13

  • Announcements/updates

Email Elin if you have agenda items for next weeks' meeting, Wednesday, 7/ 15, and Thursday, 7/14

Ian and Jess are out next week

2009: July 15

Present: Liz, Barbara, Jim, Carrie, Doreen (time-keeper), Elin (notes) The Donut Angel visited our meeting today (thanks, Liz!)

Announcements etc. Wiki Edit Summary Notes - Elin requested that as a courtesy to each other we use the summary field when editing wiki pages - if edits can easily be summarized. It helps to know at a quick glance what has been edited when alerted to changes Meeting Notes - clarified alpha order of taking meeting notes - Elin took notes today - Liz is next - our first alpha cycle is nearly complete, thanks to Jess - who has done double duty.

Rotate meeting moderation? Liz asked the group if we could share responsibility for meeting moderation. We decided that team members would moderate specific agenda items.

Finalize survey - reviewed all Q’s and our experiences taking the survey. Time to take survey varied from 5 min to 15 min - depending on familiarity with survey Q’s Barbara will tweak a few settings, and adjust a few formats Then Liz will test the survey with a few Voter colleagues Barbara - can you let us know when the edits are complete - maybe the team could take the survey again? Lots of discussion about Q 6; did not want to edit this Q without feedback from Ian and the results of the Voter test We will finalize the survey and re-evaluate Q6 tomorrow with the goal of sending the survey out on Monday 7/20 We will send the survey out using the master url option and add ability to provide name to survey, giving LIS staff the option to be anon Do we want to send out to LIS student summer employees?

Tomorrow’s Agenda: Finalize survey (15 min - Barbara and Liz) Timeline (30 min - Carrie) (if possible - please review timeline section and timeline discussion on wiki prior to the meeting) Notes: Liz

2009: July 16

Present: Carrie, Doreen, Elin, Jim, Barbara, Liz(notes)

Survey for LIS staff(Moderator: Barbara)

  • Reviewed results from survey prototype test and updated content and questions accordingly.
  • Barbara to make updates to actual survey
  • Liz to request password for LIS Web Team account.
  • Liz to send out survey to LIS Staff on Monday 7/20 from LIS Web Team account. Intro text to be used as email text.
  • Completed surveys due by end of day Wednesday July 22nd


Project Timeline (Moderator: Carrie)

  • Initial discussion of formalizing Project Timeline
  • Questions about how workbook being developed will be used by Web Team
  • Project Timeline discussion to be continued at next meeting
  • Project Timeline Discussion on Wiki


Tasks(before next meeting on 7/22):


2009: July 22

Location: LIB105; next weeks meetings will be in LIB221 Present: Jim, Elin, Liz, Barbara, Ian, Jessica, Carrie

- Discussion to meet with Jeff R. (Sponsor) > Review what we have done so far > Discuss issues people on team are having with time (availability of time) to participate in this effort

- Geneeral discussions: > Barbara - are we producing? Are we moving forward on our mission? > Liz - Are we following guidelines? How can we best stay on track? > Team - should we have longer meetings? More meetings? We voted 'YES' on extending the meeting by creating more time at end of agenda to better wrap-up meeting, discuss new agenda topics, prep. for next meeting.

- Survey update (Barbara/Liz) > Approximately 50 people responded (today being last day people can contribute to the survey) > Managers should send-out a reminder to complete the survey - that it is important to LIS and User Services! > The actual results of this survey will be reviewed at next weeks meeting.

- Make-Over DIY Workbook discussion > Team decided it was best to use this guide as a general guidance document. > Barbara - "We are in a role of being a Project Manager - finding Project Managers - finding primary contacts." "We need representatives that can properly represnt our interests" "We need to start identifying people who will be able to help us." Ian - "We may want to delay [contacting people] our search until we better understand the overall situation."

- Statistics discussion > What data sources can we use to derive useful information for our effort? > Jim - HEAT - Although the incidents coming into the Help Desk are classified in many different ways it may be possible to query the HEAT database to find useful information. Jim will attempt to do this for next weeks meeting. > Team - Information Desk - 3 different sources of information (could Nate Burt help us with this?) > Ian - We have 2 years of Google analytics > Elin - We have 5-6 months of blog information we might be able to sift through somehow... > Ian - Information that could be derived from some of these sources are: 1. What are the top three pages used 2. What are the most common search terms 3. What is the click path to the resources > Carrie - Can we ask Joe Antoneli if he can get us stats? > Elin - The Reference Librarians have (in the past) gathered information through posing questions to customers and recording the answers.

- Site Map > How do we break it down? > Liz - Should we break it down into a test file? Query the text file? > Barbara - Big picture is needed to see what we need to do next... > Carrie - We will need to divide-up the responsibilities for this breakdown > ACTION ITEM: Ian will get Liz a list of everyone who has permissions in current CMS system.

- Timeline discussion: > We continued to review our timeline; adjusting dates and milestones > Finalize design criteria (post survey results) on Aug 5. > Ian - we could breakout content to folder structure which mimics structure today. We can then transfer what makes sense to new templates. > See Timeline for details.

2009: July 23

July 23

Announcements - Elin invited Jeff Rehbach to view the LIS Web Team blog and wiki - Elin will be on vacation beginning Aug 5th (10-14 days)

This meeting was dedicated to discussing and revising the team timeline.

It was noted that as new training dates are announced (contact manager), this dates need to be included in our timeline.

Agenda items for July 29th meeting

- Survey results and other metric analysis (helpdesk stats, media, etc.) - Building coalition (who do we want to connect with) discussion

2009: July 29

Present: Barbara (time), Carrie, Doreen, Elin, Ian, Jess (notes), Jim

Updates

  • Liz out; Elin & Carrie out 8/5-8/18 will need to adjust timeline to account for absences
  • Moderators during Elin’s absence: Barbara, Ian and Liz (2) (let us know if you’d rather not, Liz!)
  • We’re now posting agenda items on the Blog instead of via Outlook calendar appointment updates
  • News from web makeover managers’ meeting: Barbara says they’re not being trained yet, but developing a test for the training. The timeline is fluid, the meetings next week will hopefully be focus groups for Drupal platform familiarization and basic content editing how-tos

Building coalition

  • A sense that we are not ready to bring in others until we have buy-in from Sponsor and ADs on our documents
  • Once we have buy-in we’ll need to involve Bryan C., Mike L., Joe A., and Petar for internal LIS action items, and Robert Keren for all staff items, as well as Curricular Tech. group for the training/support of blogging

Survey & Metric analysis

  • General discussion of results
  • Jim will get stats from Nate
  • Carrie has found not much of use from library stats (for our purposes at this point; may prove useful for future tasks), except EZproxy stats = 1/4 users off campus 3/4 on campus for subscription journal use
  • How will we gauge success using surveys & metrics? Possibly send out our LIS staff survey again after new website launched
  • Jess & Barbara will work on a short student employee survey to gather some small bit of data from the student perspective (5 question goal!)
  • FYI: In current IA from White Whale, there is no LIS link from the College homepage, and no LIS link under Academics or Quick Links. Rather, a link to the Library from Academics and a link to the Helpdesk under Quick Links.
  • Ian sent us the White Whale IA proposal (not final; open to revision)
  • Wordpress upgrade likely before start of fall semester: new admin. interface, implications for training, etc.

To Do

  • By meeting tomorrow: Thoroughly read the Recommendations document in preparation; contribute content as needed, especially library section! (Ian will edit document tone for consistency.)
  • Please comment on the new College website design on the web redo blog!
  • Meeting ended 5 minutes early
  • Future agenda item: contacting people who requested contact on survey

2009:  July 30

Present: Jim, Ian, Elin, Barbara, Jess, Carrie (notes). Liz and Doreen are out.

Announcements

  • The wiki isn't good at handling simultaneous edits. If you edit a page at the same time as someone else, you may lose your edits when you hit 'save.' To avoid this, you may wish to copy your text to Notepad before you hit 'save.'

Timeline

  • Prior to today's meeting, a few of us made some minor edits to the timeline based on vacation dates and the new student survey.
  • The group looked at the timeline during the meeting and decided the following: a) we're on target for "7/30 - Evaluate information architecture and corresponding list of LIS website contacts for current LIS site" because by "information architecture" we mean top-level IA, and that's what we started to discuss this week (the "recommendations" document). b) We will delete "8/5 - Finalize design criteria" because for our purposes, "design" is synonymous with "information architecture" -- and we're already evaluating the information architecture.

Recommendations

  • Ian mapped out his recommendations on the white board. Jess will transcribe his drawing...somehow!
  • We started to discuss where hard-to-pin-down sections of the current LIS site would reside in this new configuration. Media services would go to the wiki, Segue would be on the LIS landing page and in other places too.
  • We need an LIS website contact for media services. Since Adam Dobucki is leaving, Ethan Murphy might be a good candidate.
  • Mediawiki is not suitable for private internal documentation (eg, passwords). Departments might wish to use middfiles for this type of info.
  • We need an LIS website contact for blogs. Joe A would be a good candidate.
  • Some blog content perhaps wouldn't be interesting to the general public. There are various ways in which we might control which postings are shared on the main LIS blog.
  • Generally, it seems that there are tools to accommodate most if not all concerns that have been raised about the blog.


Next week, the team will discuss LIS website contacts.

2009: August 05

Present: Jim, Ian (notes), Barbara, Jess, Doreen, Liz (moderator).

Announcements

  • Ian will attend AD meeting tomorrow in place of Elin who is on vacation.
    • One team member would like to let ADs know that some people on the team are having trouble devoting the time they'd like to the team because of other work responsibilities
    • Pointed out that people will contribute to the team in different ways as project progresses
    • Our timeline is very aggressive, but is required to be due to the nature of the project
  • We will devote 10-15 minutes at tomorrow's meeting to go over topics to be discussed in AD meeting
    • Vision
    • Creation of team blog & wiki
    • Scope
    • Timeline
    • Recommendations preview / meeting with Jeff on Aug. 20

Contacts for Site Content Management

  • Start with top-level sites and work down
  • Include everyone who expressed interest in the survey in being contacted
Part of Site Team Contact External Contact
Library Carrie Macfarlane Bryan Carson
Library Portal Barbara Merz Mike Lynch
MediaWiki/Helpdesk Jim Beauchemin Petar Mitrevski
About LIS/Landing Page Doreen Bernier Doreen Bernier*
Blogs Ian McBride Joe Antonioli
Telephone Services Liz Whitaker-Freitas Peggy Fischel
Banner, etc. Documentation Liz Whitaker-Freitas Marcy Smith
Circulation Documentation Elin Waagen Elin Waagen*
Special Collections Jess Isler Andy Wentink
Music Library Jess Isler Dan Frostman
Media Services Jim Beauchemin Adam Dobucki
Help(desk) Jim Beauchemin Jim Beauchemin*
Emergency Doreen Bernier Joseph Watson
Collection Management Barbara Merz Terry Simpkins
Teaching/Learning Ian McBride Curricular Technology Team (Adam Franco)
  • To be determined. Primary Contacts should coordinate to find someone to assist with this. (Essentially, these should not be the same people. Primary external contacts could still be the people we identified, but they would need internal contacts other than themselves. The point being that responsibility for keeping the external contact on track/schedule, objective, and open-minded about the process lies with someone not so close to the content.)

2009: August 06

Present: Ian, Barbara (moderator), Jess (notes), Doreen (time), Liz

Announcements

  • PM meetings: are all the same, only go to 1 of the 3

Ian's run-through of topics for AD meeting this afternoon:

  • Not discussing vision, since it was already announced
  • Showing Blog & Wiki, encouraging ADs to follow and participate
  • Scope of project overview
  • Timeline overview: sense that we're making good progress; some individual team members feel time-strapped and some difficulty balancing increased responsibilities
  • Mentioning 8/20 meeting with Jeff to formally review and approve recommendations, but also giving a high-level overview of our recommendations as they currently exist
  • Ian will post brief overview following the meeting; will go over more thoroughly in our team meeting next week

Contacts -- how to proceed?

  • We'll want to talk about different systems we'll be using and how best to use them, appropriate content, etc.
  • Dispelling concerns about extra work--much of what needs to happen is what you're already in charge of anyway
  • Instilling the idea that we cannot do the work for you; we'll be moderating, guiding, and recommending, and we will also be supportive--if you need help doing the work we will help you get additional resources/people, but the work ultimately resides with you! And FYI, the MCMS will not be operational after January 4th.
  • May use web redo PM workbooks if desired

Looking ahead:

  • Goal: meet with primary contacts by the end of August (will add to timeline)
  • Send out reminder to student employees to fill out the survey (Friday morning?)

Agenda for Wed 8/12:

  • Liz will moderate meeting
  • Ian will give an overview of the AD meeting and reactions
  • More discussion of meetings with primary contacts/working with them if needed
  • Finalizing recommendations on the wiki; we want buy-in by the meeting!
  • Going over student employee survey feedback

2009: August 12

Present: Ian, Barbara, Jess (notes), Liz (moderator/time), Jim

Curricular Technology Team meeting recap-Ian

  • Went to CT team meeting yesterday and explained 1 link on the LIS landing page for CT, and that CT team decides what happens when people click that link--what it leads to, etc. It can be a work in progress, since the final solution will not be decided by our launch date!
  • Discussed Google Analytics, various options with them, etc.
  • A sense that the process with CT team does not need to be overly formal, but that if they need additional resources, we can help them get some
  • The team has been referred to our wiki and blog to see our docs about our overall approach/what we envision

AD meeting recap-Ian

  • Recap is on blog
  • Further discussion of personnel challenges/need to build in some redundancy in work roles
  • Re: question about tracking system not being in line with our scope: Since it is not yet solved, we will keep it in mind but may fall within scope when it's decided

...This lead to a discussion of forms and a replacement for HEAT system

  • Discussion of disparate forms and tools for forms
  • Limitations of open source forms, Cforms preventing the Wordpress upgrade, some here want to custom build a self service forms creation tool, etc.
  • Helpdesk cares a lot about efficiencies and consistency across their forms
  • Helpdesk is replacing HEAT this year
  • At this point, Jim strongly recommends Helpdesk moving to Parature, which has its own forms tool (Jim will send us all info. on this)
  • Sense that we should bring up this issue in our meeting with Jeff on 8/20
  • Decided that we will add a section in our Recommendations doc discussing the need to solve the problems relating to forms
  • Can we find a tool that encompasses all forms across campus (not just LIS)--public safety, facilities, library, helpdesk, etc.?
  • We will inventory current web forms, solicit feedback on what paper forms could be switched to web forms, and make recommendations for a central place(s) on the web for forms to be organized and accessed
  • Try out the Drupal add-on forms tool (Amherst has been running all their web forms on this for 3 years)
  • We will add a section on soliciting feedback on forms from our primary contacts in our version of the web redo workbooks
  • General discussion of costs and benefits of open source options, in light of budget cuts and staff reductions

LIS student employee survey results

  • Brief overview of results
  • Pretty much concurs with our results from the LIS staff survey
  • See more on the Blog

Tomorrow: Finalizing our Recommendations document in preparation for our meeting with Jeff.

2009: August 13

Present: Liz, Barbara, Ian, Doreen, Jess

Recs Doc editing

  • Going over suggested changes
  • Barbara will add in paragraph on changing the LIS Wiki Main page sections to include gateways for different users
  • Doreen emailing Elin for clarification about her question on workflows, for other input

Other

  • Discussion of whether having PCs internal and external as same person make sense or not; a sense that perhaps these should be different people

August 19 agenda:

  • Team approves Recs doc, prepares for meeting with Jeff R.
  • Possible further discussion of meetings with PCs

2009: August 19

Present: Elin, Carrie, Liz, Barbara, Ian, Jess

Plan for meeting tomorrow with Jeff re: Recommendations.

  • (See aganda on blog)
  • To start with emphasizing certain points: Parature; overall design with wiki, blog, library page etc.; one blog concept
  • Ask Jeff about impact of changes at media services.
  • In considering our design, issue of how LIS will be accessed from the larger college web is important. Carrie to add issue to recs. document.
  • Make sure there's time for Jeff to be clear on what he's taking on to the ADs.
  • Elin to send link to recs to Jeff again in preparation for meeting.

Other - future meeting needs to revisit Team contact / External contact assignments. E.g. AD team could be responsible for "About LIS" content.

2009: August 26

Present: Elin, Carrie, Liz, Barbara, Ian, Jess, Doreen, Jim

Announcements - Discussion

Doreen reported a wish from Mike Roy for the LIS "one blog" concept to be implemented right away and used as the platform for LISt. Some proceedural & technical issues make this timing difficult. Technical: development of blog template functionality; ability to import current blog content. Re:LISt other issues include interest & work flow.

Q. Are we to meet with ADs tomorrow? A. Yes - likely at 2:30pm.
Tomorrow's 11:15am meeting canceled.

Agenda item - "map out new IA" - agreed that the next step in this process is the IA meeting to approve (or not) the high level IA we propose.

Contacts for site make over.
Changes:
Circ, external contact Kellam Ayres.
LIS landing page, external contact Jeff R.
Media, add Mary Backus as second ext. contact
Helpdesk wiki, Topher ext. contact in practice.

Additions:
Digital Collections, int. Barbara, ext. Mike Lynch
Armstrong Library, int. Carrie, ext. Todd/Nancy

Note: ask Mike L. as part of above how slide library should be accessed from LIS.

Ian reported that WW thought linking to Subj Guides from academic pages was a good idea & would add such to the suggested IA.

Forms.
Ian reported that cForms is officially going away. Replacement is the Wordform module in Drupal (drupal.org/project/webform). Form users will need to migrate their own forms - preferably by January but leeway given. In addition, Parature will be used if & when available & custom forms will be programmed on a project basis.
We all need to get lists of forms in current use on the LIS site from our external contacts to combine into a master list.

Training.
Drupal training for us likely late September after a suitable template is constructed. Followed by training for external contacts in early October.


2009: September 2

Meeting notes 9/2/09

Present: Liz, Jim, Jess (moderator), Doreen, Carrie, Ian, Elin (notes)

Announcements etc.
Jess and Ian are following up with Joe A to adjust permissions for LIS to access the web makeover folder in middfiles
Elin - will be meeting with Fred and other team leaders on Wed afternoon. Anything to bring to the table? No major concerns noted; small change to protocols (shared team responsibility to moderate meetings), that things are going well, some concerns regarding scope creep/changes to scope
Liz – created a spreadsheet in middfiles that lists the entire LIS website URL’s; the team will review to ensure we identify all pages, and eliminate overlap
Carrie – question about WW/web makeover meeting invites; they are optional; open process to increase involvement and invite comments; round 3 of section landing pages meeting and Amherst profile demo scheduled for today
Carrie – advisory groups? Will add to recommendations doc

Meeting with AD’s
Summary and discussion
We have the green light on our recommendations - great work by the team!
No follow-up required for AD’s not present
Discussed pix issue – all LIS staff pix in directory not part of initial scope; top down instead of team driven; or a reflection of empowering team; hr/legal issues – cannot require; maybe phase 2; wait -impact of org/staffing changes; promote who we are; visual big bang; helpful to users; not included in initial survey; will ask MR to initiate this discussion and post on webteam blog (or LISt?); ask for comments and feedback; make arrangements if resources are needed to implement, one work area already did this easily and quickly on their own; will include or not based on feedback
One blog – some tech/design issues to be worked out but may be able to implement prior to go-live dates; maybe an interim solution/rolling schedule – open permissions, change address of LISt blog, change template (Nov.), tag for internal or external, set up categories
Support for landing page idea and concept that user does not need to know we are merged – sign of a mature merged org
Real-time status of everything - check out laundry.mit.edu for real-time status update model
General support for need for new ticketing platform capable of web forms, tracking, and self-service; Jim will edit Parature section of recommendations to be more generic since no decision has been made regarding platform recommendation
Questions about public v. private blogs, documentation etc. – we recommend encourage but not require
Question about user v. staff documentation
Hope for improved search functionality on LIS pages and catalog
Quick links from college page? Library – info products; collections and resources. Technology – user centric support
Next phase? Promote self-services
Blog post on LISt regarding recommendations – Elin will post by next deadline 9/11; invite LIS comments

Primary contacts stuff
Post questions that come up when meeting with LIS contacts on the wiki contacts page
May need to adjust CMS permissions to allow full access to contacts
OK to start building documentation on the LIS wiki – it will work better with more users
Need tips and tools to help new users; training?
Circ will add borrower documentation to the LIS wiki – not the separate Circ wiki
Dokutek? Link to external platform (Amherst created own eres system in Drupal – evaluate Midd eres in phase 200?)
Wiki Q’s:
Include screenshots? Yes
Photographs etc. from proprietary systems? No
Link to pdf’s instead
Recommend store vendor manuals in middfiles
Use discretion
Goal to decrease use of embedded objects on web and increase direct linkage
May be other solutions in the future for shared docs etc.

Timeline
Added Drupal training schedule – last week of Sept for PM’s; mid-Oct for all
When could we realistically expect to implement the one blog?
When will we meet with WW – Ian will follow up
Freeze dates for CMS

Thursday agenda proposals
Spreadsheet of over 6,000 URL’s – how to manage existing url content
One LIS blog


2009: September 3

Meeting notes 9/3/09

Present: Liz(notes, Jim, Barbara, Carrie, Ian, Elin (moderator), Jess


Announcements

  • Ian will inquire with Joe A re: Wiki Training
  • Elin provided summary of meeting with Fred
  • Mike Roy would like to visit with the team. Date and time to be set after his blog posting re: photos
  • Carrie mentioned attending Amherst Profiles presentation. Team members to read Ian's post regarding this at go/ian. Ian indicated that it is not likely that we would implement this.


2009: September 9


LIS Website URLs

  • Went through URLs Inventory Spreadsheet and assigned URLs to Project Managers

Participants: Liz, Jim, Elin, Carrie, Jess, Barbara, Ian


Discussed One Blog

> Discussion of categories was discussed (see Ian's blog)
> Categories/break-outs discussed for Breadloaf
> Carrie - should we have an all LIS category?
> Internal versus external classification (where will things be displayed?)
> example of internal = gate count in Main Library; external example = "suscribe to feeds"
> Important distinction
> Barbara - Discussion insued regarding internal LIS content - who should be reading it?
> Internal may translate to private - is this what we want to send for a message?
> External - "Did you know" category?
> Ian - suggests removing "Internal" completely
> Private blogs should not be in One Blog
> Sensitive information must be protected
> "One Blog" = public information
> Document should be created to talk about use of blog and discuss private issues
> We should create a new section on our Contacts Page for above document - Barbara will create section
> Discussed Home pages - determined by category? Categoroes --> Tagging (Should tag everything)
> Ian - use conversion script to standardize tags
> Carrie - Areas to be categorized? By function?
> Rules for blogging discussed briefly
> Should we have author-based feeds?

NEXT STEPS:

- Need function names (categories)
- Breadloaf: School of English and Writers Conference (use sub-categories?) Are there more?
- Eliminate Internal classification
- Use "Did you know" for all public postings (default)



2009: September 16

Present: Liz, Jim, Jess, Carrie, Ian, Elin, Barbara

Met with Tonya Langford from White Whale. Issues discussed:

  • Quick links to LIS content from college homepage and elsewhere - how many? wording?

T. thought several quick links would be appropriate. We should consider immediate needs of constituencies and their knowledge of LIS. Consider also how they'll get to what they need by searching - it won't always be possible to provide links. Searching could be "tuned" to give good answers to oddball searches.** We should come up with a list of recommended quick links **

  • Where other than homepage does LIS appear?

Academics page.

Offices & Services

Constituency based areas for faculty / staff / students.

we should look again to see how we're refered to in these areas. OK?

  • Advice on wiki for documentation, answers to questions.

We discussed the implications of FAQs - would need data collection, entry, search mechanism etc. College wide FAQ database? Wiki and/or FAQs need energy to make work. Conclusion - wherever the answers are, the search mechanism should be on the main site with direct access to the answers. We already have "answers" but access to them is the problem - good tagging necessary.

  • Where to put Music & Armstrong library pages?

They should live "under the library page". Side discussion - library or libraries page? What needs to be on their individual pages - hours, locations, explanation of what they provide. Possibly library page needs short text for external audience - including existance of branches!

  • How to include info on liaisons, advisory groups etc.?

To be included in academic depts' resource pages - subject guides already proposed for inclusion there. Who should maintain info? - liaisons. Carrie to make up sample section(s).



2009: September 17

Present: Barbara, Liz, Jim, Jess, Elin Carrie and Doreen

We held a lengthy discussion on College homepage Quick Links. 2 landing pages named Library and Technology. Should technology be included on a universal “support” page for the college site.

Should telephone services be listed under telephone and offices. We need to review the analytics and discuss further.

Blog vote – Elin has crafted text in the wiki for voting purposes. Terminology choices to make: • Use “function” names instead of area names for categories (ex, Circulation instead of User Serv.) Lower level functions can be listed as tags to assist in searchability

Should we change the name? Should we make it public? Before we vote, we need to be sure of what the catagories are, before going forward.

It was agreed that we move to the blog for continued discussion of terminology.

Possible external names: • Bringing the Knowledge to You • Runed In • Good to Know • Need to Know • Essentials

Jess will create post for voting

Vote: we agreed to proceed with one blog after a new name has been decided.

Next agenda – How to launch the blog.



2009: September 23

Present: Barbara, Carrie, Doreen, Elin, Ian, Jess, Jim

One blog stuff confirmed:

  • The Blog name is Library and Information Services (the link is changed to .../LIS)
  • Blog tagline is Bringing knowledge to you
  • Category default is (star) The Essentials
  • Categories will have parent/child hierarchy
  • Adding a tab in the one blog for How-To do things like subscribe, comment, post, etc.
  • Ian made a list of things he'll do to change LISt blog and will move our blog over
  • Ian is making how-to for others to move their own blogs
  • Should we have formal training right now for people who don't already use blogs for how to post, subscribe & comment?
  • We'll have a formal announcement: saying contact us if you want to learn the above, how to meet with or drop in with a media tutor or have a rep from the team/LIS meet with a workgroup, or pointing to the How-To section of the blog
  • The announcement is going to be a draft blog post, so add and edit it as you see fit (Click save when you edit, NOT publish!)

Quick links:

  • Discussion of 2 vs. 3
  • We voted and decided to have 2 links: Library and Technology support

LIS landing page:

  • Remember, it is one page (i.e. no subpages)
  • Doreen thinks we as a team have a stake in deciding how this page should look/be organized
  • Do we want the blog link or feed on this page to be external? Probably, but we'll decide later
  • Doreen will share progress for LIS landing page thus far

Discussion of work with Primary Contacts:

  • A sense that we should meet to see where there are overlaps
  • A sense that we should have a show and tell of what our PCs have been doing, that they're not "free agents" and we should make sure they're doing what they're supposed to be doing, even though the workbook is optional... (I didn't really understand this part of the discussion so feel free to edit if this isn't correct)
  • More discussion on this tomorrow

2009:  September 24

Present: Barbara, Carrie (notes), Elin, Ian, Jess, Liz

New LIS one-blog has been launched!

  • Thanks to Ian.
  • A few tweaks needed, a few training points noted. Bugs will be reported at chisel.middlebury.edu/pool. As yet, it's not possible to subscribe to a category.  Barbara will add content from FAQS to "How do I..." section.  Ian has asked Alex for links to screencasts and tutorials.  "The Essentials" is the default category but a check-mark doesn't appear beside this category in a new post until the new post has been published.  "Areas and Workgroups" category doesn't automatically assign a post to the categories below it in the hierarchy.  "Feed" links provide URL for feed for just "The Essentials."  Blog authors who wish have their content moved to the new one-blog should be alerted that content like "resources" and calendars will need a new home (won't be migrated).
  • To do:  a) Elin started an announcement in the new blog. Others should contribute. Deadline is end of Friday 9/25. b) Announcement will be posted to blog. Elin will send it out via email too. c) Add content to "How do I..." and "Subscribe" pages.  d) Publicity: Suggest to your workgroups that the topic be discussed. For example, it will be introduced in an all-ETI meeting next Tuesday.
  • If other blog authors want to move their blogs, they can send us a request and Ian will migrate the content. (It's a complicated process.)

Checking in with team about work with primary contacts

  • After Oct 6 (workbook deadline), team members will bring to a team meeting: a) list of content considered "essential" by their primary contact/s, and b) ideas for where else on the LIS site links to their content should appear. Based on this info, the team will create an IA modeled after what White Whale has created for other sections of the College site.

Wiki and blog training for primary contacts

  • info forthcoming. (Ian's meeting with Joe was canceled.)

Freeze date for changing the CMS:

  • December 1, 2009.

Elin will be out next week. Doreen won't be able to attend on Wednesday. Wednesday meeting canceled

  • get out and show someone else how to blog!

2009:  October 1

Present: Barbara, Carrie, Ian (notes), Jess, Doreen

  • NERCOMP conference for Library websites at Amherst

Because of cost, it is probably not efficient to attend as a team.

Who would like to go? Barbara (yes), Jess (perhaps), people outside of the team (perhaps). We should compile a list of people who would like to attend and then find out what budget is available for this event. Doreen will check interest based on people who fill out the travel request form.

  • Drupal Training Sessions

Carrie, Jess, Liz, Elin and Ian attended various sessions.

When will additional training be offered? There will be workshops/worksessions offered each day of the week beginning later in October. The schedule will be sent to the project managers list, which can then be forwarded to people in each area who are interested in attending by the project manager.

  • LIS Landing Page

Hours: these should be entered into Resource25 so that we can build dynamic feeds and calendars to show up on the LIS landing page. Each of the branches could be listed as a location with their hours of availability scheduled through that central calendaring application. Events and room schedules should also be part of this plan.

The landing page shouldn't just be a list of links. There should be headers for each of these sections and then text with links in it. It could end up looking and working something like this: http://www.mahalo.com/vermont

Where should emergency information end up? There should be a link off of the LIS landing page for this information which will be hosted on a remote server to ensure that it can stay up during an emergency. We'll work with Public Safety to get this information updated.

Where should Telephone Services be listed? There will be a link on the Offices & Services page to the telecom site and there should also be a link on the LIS landing page right after the Helpdesk.

Where should Curricular Technology be on the Staff Directory? Rather than listing out workgroups, we'll link directly to the LIS listings in the staff directory. There will be a link to the content generated by the Curricular Technology team on the LIS landing page.

Should also list out the LIS liaisons and advisory groups on the landing page in the contact section along with Helpdesk, Circulation Desk, etc.

Library Disambiguation page: this will only show up if you searched for "Library". All other paths to the library take you directly to the library page on the website. Links to Special Collections, Armstrong and the Music library will be shown on the Library page of the website.

Newsletters and alert postings on the website: these should just be posts on the new LIS blog now, rather than produce these as separate areas.

System status: widget on the LIS landing page, but not something that takes up a lot of space.

Ticket tracking: new version of HEAT up by end of year. Self-service and forms modules to be implemented ongoing into the new year.

We'll need to see what shows up in the dynamic search once the site goes live and then adjust our landing page.

Will there be a specific template for the library? No, it will use the same once we're using for Offices.

  • Permissions on LIS blog

Currently all people are administrators. We looked at roles and privileges. Admins can change themes, install plugins and import content. We voted on whether to leave these permissions in place or change all users to Editors. Voting record:

Doreen: change to Editors Barbara: change to Editors Jess: leave as Admins Jim: change to Editors Ian: leave as Admins Carrie: change to Editors

  • Link checker

This will be submitted to the web programming request field.

  • Analytics

We'll be using Google Analytics to track site usage. Chris Norris will be offering training at a later date.

  • Wiki Workflow

Currently this is being managed by Jim. What does "manage workflow" mean in the context of this project? Is this going to be a document delivered to our site users? Is this in reference to a publishing workflow? This will likely be different for the library, since some of the information will be in subsplus or other systems. We'll discuss content workflow at a future meeting.

2009:  October 7

Present: Barbara, Carrie, Ian, Jess, Doreen, Elin, Jim, Liz

General:
Discussed how to proceed about collection descriptions. Carrie will consult with potential authors of descritions. A collections page is possible.The team is responsible for big picture overview but not details of descriptions.

Carrie reminded us to look over the text she wrote for resource links from Academic Depts. and comment on the blog.

NERCOMP meeting Nov 9th: "Usability in Libraries and Beyond". Funding is available for team members to attend. Barbara, Elin & Jess are possible attendees.

Mike Roy proposes adding review of LIS internal communications to our team charge. We will think about & blog about this before responding to him.

Agenda: workflow
What does it mean in our timeline that we should "Design staff workflow for moving content." Conclusion - we should pull together best practices for dealing with various types of content on the web. E.g. pdf, Word docs, video, audio. Problems in some cases of large numbers of documents. Should they all be part of web or could they be archived some other way?
Some sources for best practices: go/webhelp, Communications office style guide, materials on Segue, Use of PDF in accessible documents in our resources section. Team members to add appropriate links to resources section of wiki.

Actions - team members to pass info about Drupal workshops along to their primary contacts & content editors.

Agenda for Oct 14th. Review progress of LIS in web analysis/design - considering essaential site features & IA.


2009:  October 14

Present; Doreen, Jim, Ian, Barbara (moderating), Liz, Jess, Carrie, Elin (notes)

Feel free to edit/elaborate/clarify!

Announcements: Barbara, Jess and Elin attending NERCOMP Nov 9th: "Usability in Libraries and Beyond"

Remember to use shared folder in middfiles for easy access/sharing with team members and contacts (we merged 2 folders)

Reviewed IA word doc - basically OK - need to make a few edits/tweaks

Landing page - Drupal see previous discussion/meeting notes above

LIS wiki - move documentation from CMS

LIS blog - done! (in beta)

Library site - lots of questions - what to do about collections; overlap issues; how do we proceed? Do we need sub meetings? How-to guides?

Need to review IA to identify overlap and gaps; avoid duplication and maintaining content in more than one place

Build a beautiful skeleton, with some flesh - that we can build on after the go live dates

Keep user at forefront

Web team can determine IA as it pertains to the LIS website

Jim reviewed buckets organized around concept of How do I; I have a problem; I have a request

Limit to 8 sub pages (8 links on left hand navigation)

Offices and Servcies template will be similar to academic, but with distinctive features

We should recommend features - what we do/do not want - to Joe A

Sub level sites will have their own navigation

Hours will be dynamically generated to our landing page

Look at: midd2.middlebury.edu/offices/technology

Ian has set up permissions for the team

Create a FAQ data base? Aggregate content across site?

Questions about duplication of effort and content

Workflow for content; identify existing content to avoid duplication (search; contact primary content provider)

Preference is to NOT upload exisiting PDF's into wiki, but could be workable temporary solution to time/skill contraint

Agenda 10/15 - more IA


2009:  October 15

Present: Doreen, Jim, Barbara, Jess (moderating), Carrie, Elin, Liz(notes)

Feel free to edit/elaborate/clarify!

Announcements

  • Jim: Linda K. developed a project plan for migrating all helpdesk documentation to wiki
  • Elin: Mike R. asked when do we plan to add email subscription option? Elin to check with Ian on installing plugin.
  • Jess: Published How do I on LIS blog. To update it to include information on posting guidelines (privacy)


Library IA Outline (Carrie)

  • Review of 1st level IA for Library site
  • Carrie will publish IA on blog for discussion
  • Usability testing will happen and IA may be revised as necessary


Curricular Technology

  • IA document can be found here: \\middlebury.edu\middfiles\orgs\WebMakeover\LIS\Curricular%20%Technology


Library Portal (Barbara)

  • Review of 1st level IA


Digital Resources (Barbara)

  • Review of 1st level IA


Collection Management (Barbara)

  • Where will they live? About?


IA discussion to be continued…

2009: October 21

Present: Jim, Barbara, Jess, Carrie (notes), Elin, Liz, Ian


IA for library page

  • due next week. Include names and associated privileges.
  • IA for subpages of library page tbd but content creators
  • Is college directory enough? Do we need to create departmental directories too?
  • Feedback: Put Hours in sidebar, not subpage.


Photos in new web site

  • Where will they be stored? Drupal has a resource manager
  • Ian sent message to project managers with middfiles location of images in current CMS resource manager
  • Staff can take own photos.  Must be less than 10 mb. Drupal will resize automatically and provide choices for display.
  • Pam in Communications is sorting through College photos. We might be able to use some of those, too.


Tech Support page

  • Will be in Drupal, with links to tech support content in wiki etc.
  • LIS landing page will link to the Drupal page
  • Will probably have a smaller "footprint" because of "Search"


Chart on Recommendations page should be revised to show that some sections will have transitional page (eg, Tech Support link won't go straight to wiki; it'll first go to a Drupal page)


Wiki will eventually get a "skin" or "template" so that it matches the rest of the Midd site


Collection Management page

  • Barbara will talk with CM about internal vs external content


Blog

  • Alex is making changes to the template
  • White Whale will give us a template
  • LIS landing page will link to it and contain a feed too


Telephone Services

  • Will have Drupal landing page with links to content that lives elsewhere including wiki
  • LIS landing page will link to Drupal landing page


Circulation Services

  • LIS wiki now has borrowing info
  • LIS landing page and library page both will link to a Drupal landing page
  • The current Circ wiki is primarily for internal use. It will remain separate from the LIS wiki for now, but might be merged eventually.
  • Ian suggested a Circ landing page that directs people to the wikis and other circ pages. Alternatively, search queries could be set to go to circ's Drupal landing page.


Special Collections

  • Drupal page with content and links. Some content will feed to Collections page.
  • Library Collections should link to the SC page
  • Resources sections of relevant Academic Depts should link to the SC page.


College Archives

  • Drupal page with content and links. Some content will feed to Collections page.
  • Offices & Services—Alumni page should link to the CA page
  • Administration page should link to the CA page
  • Advancement page should link to the CA page
  • Resources sections of relevant Academic Depts should link to the CA page
  • “Made by Midd” and “Library Collections” pages should link to the CA page

2009: October 22

Present: Jim, Barbara, Jess, Carrie, Elin, Liz, Ian

AI Discussion continued

Jess/Carrie/Barbara - Meet with Collection Management for further discussions

> Workbook and Pages will need to sync-up > Further structure discussions needed

Elin - Digital feed on recently acquired aquisitions to the Library should be on the Library Page.

> Carrie - should news item from the News Area be present in feed form on Lib Page as well? > Ian - Might be problematic to pull News feed into Lib Page from Middcat (should go on wish list)

Team - There will be Wiki training workshops for staff in November - Carrie made mention that there were a few edits by Topher on the Music Library site. Jim to update Topher on the big picture. - Digital Media Tutors will make house calls to assist with Wiki and other related media technologies - Two work sessions which are on-going for Drupal training (Joe A.). These training sessions will continue through November and December. - Review AI content posted in site folders on MIDDFILES

Carrie - Suggested merging News Letter into LIS Blog; also merge "Did you know" content - discussion insued; tabled for now.

Elin/Team - Brief discussion on "driving directions" - where to post thaat content? About section? Central Map section? - Printing support - there is overlap - where to post support content - how to consolidate? - Visiting people to the Library - should we have a seperate place on web for these folks? Jess mentioned an Intro Page of sorts for this purpose.

Next Week's Agenda:

- Contrinue Workflow discussions - Discuss protocols - Discuss when a good time to connect with AD's and Sponsor for updates.

2009: October 28

Present: Jim, Barbara, Jess, Carrie, Doreen, Liz, Ian

Announcement - we will meet with Jeff R. next Wednesday, Nov 4th.

1) IA continued

In preparation for meeting next week, we looked over the AI materials we have on the wiki and identified items that should be added:

  • Help desk IA - Jim
  • LIS landing page - Doreen
  • List of identified cross-LIS content – e.g. LIS Links for Faculty, loaner equipment, request for film screening. Plus rules for ownership of same. - Barbara
  • LIS WIKI section - Jess

2) LIS WIKI some details

WIKI landing page to have links to audience specific subpages: faculty, staff, students, LIS staff, visitors. Ian has already put together an example of the Staff audience wiki page which gives us a good template to work with for the other pages: https://mediawiki.middlebury.edu/wiki/LIS/Main_Page_Staff

Category pages will be created:

  • General staff - Ian
  • Faculty - Carrie
  • LIS staff - Jess
  • Students, visitors - Elin

3) Blog discussion.

Blog features have already been added; e-mail plug-in, improved style. Decision has been made not to advertise or encourage private posts.

Should "*The Essentials" remain the defauly category? Should it exist at all or be renamed? Discussion to continue on LIS blog itself: http://blogs.middlebury.edu/lis/2009/10/28/blog-categories/


2009: October 29

Present: Barbara, Jess, Carrie, Doreen, Liz, Ian, Elin

Announcements: Jeff Rehbach will come to next week’s meeting to discuss IA

Computer/printer alerts: We have no solution for adding computer availability and printer status as an alert at the present time. We will investigate and perhaps include this feature in a future phase of the webpage development. Currently tech alerts are setup for only web-based products. Elin will discuss with Jim and Brian

Permissions and workflow for LIS content:

Cross departmental on IA document. Review IA document, discuss and make a recommendation for what platform to choose.

Add permission to pages and let people know

Where should the recommendations be placed? Add recommendations to the guideline page for type of content (video, Word doc., audio, PDF, etc.) Create a page of guidelines for each. Jess will create pages and add content types. Everyone should contribute whey they know to this document.

Develop technology uses and fill in our recommendations with links to content

Pull content from the Curricular Technology IA document

What is needed by 11/9? Is this being addressed by training? Clarify with Jeff We need to consolidate in one place, everything from our wiki page that is related to this deliverable. Elin will create preliminary response document on the wiki (i.e., style guides, blog permissions, best practices for video, audio, etc.) Whoever manages content in Subject Plus will need to access this document. Next week’s meeting with Jeff: Elin to remind Jeff of the link to the IA on the wiki. Carrie to update library IA.

Agenda items for the next meeting:

Essentials status – vote Lab/printer status (ask Jeff if we need to meet with ADs soon)

2009: November 4

Present: Doreen, Barbara, Carrie, Liz, Jess, Elin, Ian

  • Cancel Wed. before Thanskgiving meeting due to absences
  • Jeff will probably come to our meeting tomorrow
  • Checkin--are there any concerns about team cohesion? No
  • We need clarification on the workflow charge from Jeff
  • Doreen's LIS SEARCH landing page image on the IA Doc (see prior meeting minutes for more on this, including an example of how a search landing page can look)
    • Doreen can be a primary contact for updating hours in R25 (with others as needed)
    • Elin had questions about duplicating content re: spaces
    • Discussion about tech gadgets: where should it be, what it actually means and encompasses, tabled for future discussion
    • About on Blog page will become not "About the blog" but rather "About LIS" and including org chart stuff, mission statement, et al... (this is because there are no subpages from the LIS Search Landing Page on which to put this content)
    • Change the News/Events Feed and Blog feeds to be 3 sections: Blog feed | Events/R25 | Search results
  • What are we asking Jeff tomorrow?
    • Does he have questions about the IA Doc?
    • Clarification on the workflow charge
    • Do we need to check in with the ADs?
  • Blog questions:
    • Ian's meeting with WW on Friday and will make sure their design can support Alex's Shadowbox theme and the widgets we currently use
    • Categories can have tags listed underneath (requested addition of this functionality)
    • Clarification that yes, you can subscribe to tags. Go to the tag page and append "/feed"
    • More discussion about the blog on the blog...

2009: November 5

Present: Jim, Barbara, Carrie, Liz, Jess, Elin, Ian, Jeff

Q. From team: What does the "workflow" task in our charge mean? A. Jeff - Defining who is authorized to manage/edit the parts of the LIS site. How is content to be reviewed and changed & regular update encouraged?

Points of discussion:

List of tools (CT list) - this is more generally useful than just for faculty. Where could it be accessed? - Add to wiki.

IA - redundancy of content? No - access to shared content from multiple locations.

LIS page - adjustments - add search results, have fewer separate feeds areas.

Do we need library disambiguation page? Or - do we send that search to the LIS page? Or add links on the library page to CTLR? Or leave until testing is possible (phase 2)?

Provision of a branding object for LIS?

All pages + blog + Wiki need to link back to LIS page. Will this be in the left navigation panel?

Where should policies go? Wiki - with links from the faculty wiki start page.

Where should "About LIS" go? Blog - inculding vision, org chart etc.

To do:

Blog entry pointing to IA on wiki (done)

Add emphasis that LIS landing page is a single page. (done)

Jeff - encourage ADs to examine IA and respond quickly with any concerns. Team can make presentation to ADs as requested. No feedback = mandate to press ahead with build out.

2009: November 11

Wed 11/11 Meeting Notes Present: Carrie, Jess, Ian, Jim, Barbara (moderating), Doreen, Elin (notes)

  • Announcements:

Congratulations to Liz and family on the birth of Mariana Luz :-)

Summary of NERCOMP Usability conference - see LIS blog for Jess' fabulous and articulate write-up; with links to presentations

Brief report from Ian on WW meetings. Blogs - in addition to themes there may be sets of genres with 2-3 themes to simplify design interface; default colors/text interface. Search - going forward with w/current strategy. Recent presentation by WW available on Makeover blog

Alex -will join us at next Wed meeting

Jim will be out all next week

Ian will be out next Thurs


  • Demo of Office Theme by Ian - links to new design now avaialble on Midd2; OK to use carousel and juicebar
  • Staff and dept profiles -include dept contact info at top to encourage customer contacting dept/workgroup for help, not individuals (who may be out that day) for better customer service/response to user needs and tracking of requests; team oversight?; some standardization across LIS?; let's not turn the new system into the old; indiv dept choice?; who maintains?; what about cross-dept stuff; what is best for the user point of view?; guidance for user to know who to contact for what
  • About LIS - on blog
  • System alerts - identify list of systems to monitor  - underway with Systems, Lynch, Norris etc.
  • Planned downtimes - post on blog? Ian will talk with Jeff
  • Find a PC - underway (update post-meeting - there may be some privacy issues with this functionality)
  • Rooms, Carrels, lockers, labs... - work in progress with sub-groups
  • Usability - next phase...(NYPL using interesting on-going web-based usability system - Infomaki - open-source (in very early development)
  • Color - no interest in being the color police; College pages - will not dictate color despite WW recommendations; WW color schemes all have high standard of usability; same color scheme can help guide user through our pages
  • LIS Suggestions - what/where?
  • Landing page and Library page intersects - Doreen and Carrie will connect


Thursday meeting canceled

Next week - Alex, Mike/AD's; banner - unifying element; LIS suggestions; system downtime widgets

2009: November 18

In attendance: Elin, Barbara, Doreen, Jess, Carrie, Ian Notes: Ian Timekeeper: Barbara

December 3 meeting to be from 10-11:30 AM with Sheila and Fred to review team progress. We will try to schedule LIB 145 for this, but the location is TBD at this time. LIB 221 likely won't fit all attendees.

Presentation this afternoon: pass out card and ask these questions

  1. Who is your user?
  2. What have we missed?

While people fill out the cards we will give a quick presentation on

  • Landing page
  • Library page
  • Tech pages

with questions after, time permitting

Future agenda item: the LIS banner image for sites. What is possible? What should this be?

Meeting with Mike Roy and Jeff Rehbach

  • We should get all the AD feeback and AD questions resolved now so that work on the site can be completed without interruption
  • Do we have the resources we need for this?
  • LIS website 'sets the stage' for future web work and communications
  • Do people understand the top level information architecture / separate Library and Tech sites.

Feedback from librarians: people want to know where particular items are in the new site, but are not questioning the overall LIS site IA

Useability

  • We want to collect feedback on item names, detailed item placement, etc. in IA
  • We will conduct usability tests based on 'how would you find this particular resource'
  • We might use the usability testing software shown at the usability conference attended by team members
  • We might set up a form to collect task suggestions from our community
  • When would this testing occur? There are no students here in December, we want to have a well-formed site on which to conduct tests, and we want to collect information from an outside perspective.
  • We will likely want to do useability testing after the hard launch of the site.
  • We will collect direct feedback from LIS staff at the presentation this afternoon.

What help do you need?

  • Tech site
    • Difficult to allocate staff time for this section
    • Platforms for information have been defined by Jim and Mary
    • Site information architecture has been defined by Jim and Mary
    • Need to port content from current site
    • Recommending that we discontinue use of PDFs in the future, but acknowledging that using existing content is realistic for site launch

Information Architecture suggestions

  • LIS home page: should we change Library Help to Library Resources?
  • Dynamic search results: these will display popular pages from a search engine
  • LIS blog feed to LIS home page: should we filter what is displayed here? How?
  • Should we move Reporting the the Tech Help section?
  • About LIS: is the blog too informal for this content? How do we best represent this content?
  • LIS home page: do we need subpages? What content would go on these pages?
  • Staff and department profiles
    • Do we need a set for LIS Administration? Where should these go?
    • Are we handling other profiles correctly?
  • Should we link to 'About LIS' directly from the LIS home page

Meeting with Alex about ShadowBox theme

LIS blog is the biggest blog using this theme

Alex likes the use of the seal in the O+S design, so it is used as the background. Also borrowed MiddTag styles and used for both tags and categories. Dotted underlines and highlights used for link styles.

Links to related sites in the top bar

Added RSS feeds to the bottom bar with hover previews of the RSS item

Custom author pages for blog authors

Related tags and categories on those pages. We want to emulate how delicious manages tagging. Ian will forward Alex some code for tags within categories.

Meta links: related services to be displayed at top and bottom.

Gray text on sidebar header and comments to automatically adjust to contrasting colors

Should we use ShadowBox for theme designs from White Whale? These can be applied across multiple systems. We probably need to remove the branding elements at the direction of College Communications.

2009: November 19

In attendance: Elin, Barbara, Doreen, Jess, Carrie Notes: Jess

  • Review and discussion of feedback from staff meeting
  • Major points and responses, if we had them (NOT an exhaustive list):
Policies (link to College handbook; departmental policies live on dept. pages)
Staff directory (link to LIS listings)
Computers (Addressed) / Printers (Addressed)
"Ask a Tech/Techie" (Good idea! Follow-up with Jim)
Databases name change (Agreed--work in progress)
LIS for staff? (LIS resources for staff? There's a Wiki page for it)
Maps for Depts. (Depts. can include Google map link in address, bottom left-hand corner of their pages)
Blog front page ("front page" category?--this is an ongoing discussion!)
Video lectures/digital lecture archives (Yes--in Made by Midd section)
LIS in QuickLinks (Sorry, but we voted no on this; just Lib. and Tech., both have links to LIS search landing page)
Lib purchases vs. tech. purchases
Computing missing from Technology
Teaching and Learning name change (Since Lib. and Tech. are also tabs, it'll be clear to users what Teaching and Learning is NOT)
Communications Dept. style guides: i.e. phone numbers 802.XXX.XXXX instead of (802) XXX-XXXX (Great point;
Departments should follow style guides wherever possible)
LIS for Faculty add Digital Media Tutors (Will do)
Reserve links from Faculty pages
  • We will clarify in the IA Doc that the Directory link from the LIS search landing page is to the LIS directory listing not the whole directory (apparently this wasn't clear)
  • Make sure profiles are shared cross-departmentally
  • We voted to create 1 subpage off of the LIS search landing page: About LIS (We'll add this to the IA doc).
  • About LIS page contains:
      • slightly more fleshed-out description of LIS, probably including mission and values statements
      • Administrative profiles (ONLY profiles for truly cross-LIS Administrative staff will go here, other profiles for staff go on departmental profile pages if they so desire!)
      • Another link to the LIS-focused directory listing
      • Annual reports

Item for next meeting:

  • Vote on whether or not to add 1 more subpage from the LIS Search landing page: LIS liaison profiles

2009: December 3

Present:  Ian, Jess, Jim, Barbara, Liz, Elin, Carrie (notes)

  • How to monitor comments on all-LIS blog: For now, the committee will review comments waiting for approval informally. If that doesn’t work then we’ll consider appointing one or two people. Team:  If you log in and see comments waiting, please approve.
  • LIS landing page subpage for liaisons: We vote yes on including a liaison subpage.
  • LIS landing page: Change name of "Teaching and Learning" tab to “Curricular Technology”
  • Add links to LIS blogs to all-LIS blog: We decided to add links to active blogs, eg, Circ blog. Could also include instructions on how to find other LIS blogs.
  • Merge "Faculty Main Page" with "Staff Main Page" on wiki: Yes, go for it.
  • Middlebury College Libraries vs Middlebury Libraries: Table this decision for now.
  • Can individual posts in all-LIS blog display a search box? Elin will ask Alex.
  • Will links we enter in Drupal break when we go live? We should enter the links as relative links, eg,  /academics/lib/whatever. Web services will try to do search and replace for midd2 URLs but some links might be missed. "Go" links will be updated and should be fine.
  • Feedback from all-LIS meeting: Everyone should review the feedback on the wiki in the meeting notes from Nov 19. If there are topics to discuss, propose them as agenda items.  Regarding the suggestion that we include a button/link called "Ask a Tech/Techie"  – Jim will consider this. Concern that inconsistent terminology will cause confusion.
  • Banner for LIS pages: It will have text over an image. Communications will decide on the image; we can give input. It will say “Library and Information Services.” Ian will ask Pam and Tim for this.
  • Web team assessment: Date and time change is okay. 12/17, 9:30-12.
  • New timeline: Do we need to adjust our timeline? Deadline is extended but no other dates are influenced.

Usability testing: Ian will be working with Mary, Mike and Ben to create a usability framework. We should submit tasks for the testing. Copied from web redo blog:

We have created another simple form, where you would chose the constituent (or add one) and write a task that a visitor would need to complete. We’ll gather these and incorporate them into the user testing. 
http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA

  • Goals: We will work toward the 3 items from our charge.
  • Cancel 12/23 meeting

2009: December 10

Present:  Ian, Jess, Jim, Barbara, Liz, Elin, Carrie, Doreen

Announcements

Ian: take a look at go/draftblog (can subsitute 02 - 06 for the default 01 in the URL) to see progress by Alex on the blog features.

Jess: should new categories being added to LIS blog be converted by us to tags? Decision - yes. Advice to that effect to be added to instructions on the blog.

Elin: handed out draft of the "Goal Setting Process - Web Tea" document. Team members to comment by 5pm Friday 11th.

Items


1. Banner images for LIS site. After some discussion, we decided that we wanted to use different images for each of the major areas of the LIS site and assigned the banner images to the sites as follows:

    1. 1: Helpdesk, Administrative Systems (i.e. Banner, Hyperion) documentation, and Telephone Services (reflection of Old Chapel)
      #2: Library (looking in - reading room)
      #3: LIS Home Page (wall, sky, window)
      #4: Curricular Technology (birds-eye view - main library atrium)

Images can be changed later - different images created etc.


2. Content build. There needs to be a static library & helpdesk hours page. Elin will ask Dan for help in creation of a page for this, with links from several places.

3. Forms. Currently on a hidden page for ease of displaying all forms together. Alternative - each could have own page and be shared.

4. Need for WIKI workshop. Currently only Joe could provide this on short notice. Ian will follow up on some way to get a workshop at least for LIS staff who need it.

5. List of systems being monitored. Liz is expecting this info from Chris. Also, how to communicate planned down times to the community? Blog? Ian will enquire of Jeff, Rick.

2010: January 6th

Present:  Ian, Jess, Jim, Barbara, Liz, Elin, Carrie, Doreen

Announcements

Ian: IE6 & IE7 stylesheets are up for the website.

Elin: met with managers - LIS communication under discussion. Blog generally approved of for internal communication but still issues of buy-in. Team members - e-mail Elin with comments to share with managers re: communication.

Agenda

1. Progress on web build. Generally good progress with much effort ongoing.

Actions for group - push web editors to reduce long text secions & follow guidelines. Submit questions for useability testing at http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA

Usability study to be scheduled.

2. WIKI training - send names to Ian by 1/8. Joe will arrange training session if sufficient interest.

3. Basecamp. Decided to test use of this tool. Not retrospective but for end of phase I and continuing into phase II of this team. Use for to-do, agenda items, agenda planning. Look at writeboard as equivalent to Google docs. Note from Ian - if used for sending a message, need to check off subscribers for the message at the bottom - or no-one gets the message!

Elin will use Basecamp to share materials related to our recent assessment.

Barbara will start on task list - all should add to it.

4. As we go forward - team members to scan site (web, wiki) each week for progress, issues. Report tech issues to go/webtasks

Decide on wiki next steps - when to replace front page, set up links for user categories.

Jess will add search function to single blog postings.

2010: January 13

Present: Barbara, Carrie, Doreen, Elin (moderator, time), Ian, Jess (notes)

News/Updates/Miscellaneous:

  • Discussed email options for Basecamp—digest only sends summary of newly added to-dos, completed to-dos, newly added milestones, and completed milestones (doesn’t stop you from getting an email every time someone posts a comment, but you can unsubscribe yourself manually from receiving messages)
  • Elin will be away next Wednesday
  • Doreen will run the meeting and post the agenda on the Agenda Items Writeboard in Basecamp

Discussions:

  • How can we make our profiles look like business cards?
    • After creating subpages for all profiles and adding profiles to the subpages, navigate to the page where the profiles will appear. Create a basic content node. In the body, enter “[view:Profiles==MMID]” where MMID is the Monster Menus ID aka, the number in parentheses at the top left of the edit console. Save. Business cards appear. Yippee (Thanks, Ian!)
  • Carrie will add a redirect on the Offices & Services Academics LIS page to the LIS landing page (http://midd2.middlebury.edu/offices/academic/lis)
  • Doreen asked about having the 3 quick link tabs at the top right of the banner appear on the 3 major subsections of the LIS sites: Library, Technology & Curricular Tech. As of this writing, it had been implemented for the Library site and Ian will touch base with CT to ask if they want the option added to their site.
  • A general middlebury.edu web makeover status meeting happens this afternoon. Ian will share with us any relevant feedback. Mary started outlining a plan for usability testing but is out of the office.
  • Where are the major gaps? Around the table: search portal, database list from subsplus, hours/calendar, r25, room reservations (scheduled for 2/1), media services (Barbara and Jess will contact Jim to see if we can assist with this part of the site)
  • Wiki training: Ian forwarded Joe A. the list of interested parties
  • Wiki main page transformation: Via an LIS Blog posting Carrie will solicit additional content recommendations for the main audience-specific wiki pages, to be submitted by next Wednesday 1/20. We’ll review and assess Wiki main page readiness at our 1/20 meeting.
  • Deleting a wiki page: delete all content on the page, and add “blanked for deletion” [IN THE SUMMARY FIELD] and a Wiki administrator will delete it
  • Scheduled system downtimes: Mary and Jeff signed off on sharing these via the Blog. Of course, these will not include explanation of WHY a system is down, just WHICH systems will be down. This is an accompaniment to email notifications, not a substitute.
  • Team agreed to Ian creating a new main category for Scheduled downtimes, with several subcategories for specific system names (i.e. Banner, Library databases, et al.) Ian mentioned the need to discuss Banner downtimes again with Marcy
  • Carrie and Bryan will follow-up with Chris N. on getting the library database outages posted somewhere
  • Team will use the Agenda Items Writeboard to post specific agendas (future agenda items will be at the bottom of the board).
  • Creating a Writeboard to record likes and dislikes about Basecamp as a project management tool so please weigh in with your comments there.

Agenda for next week:

  • Status of usability testing, Assess readiness of wiki main pages for changeover to main page by audience, Check-in for launch readiness and any updates from Ian (check Basecamp Agenda writeboard for most current version!)

2010: January 20

Present:  Jim, Barbara, Jess, Liz, Doreen, Carrie (notes), Ian

  • Usability testing – waiting for word from Mary
  • Wiki main pages –
    o Jim will change “LIS public documentation” to “Tech Helpdesk public documentation”
    o Wiki main page will include links to a few wiki pages (no more than 7) that are common among all audiences AND links to audience-specific pages.  Barbara will start a writeboard with proposed links.
    o Create “go” link for each audience-specific page and share the go link on each audience-specific page.
    o After we decide on content of new main page, we’re ready to go, except:  before making changes, comb thru existing page and confirm that all links have been accounted for.
  • Check-in on readiness for launch
    o Last Wednesday, priorities for college site were determined. Tasks were finished sooner than expected. Will get to at least some of the post-launch priorities.
    o Library search widget (aka library portal) is 13th on the list of post-launch priorities. Adam is assigned to it.  AT the very least, the library will have the MIDCAT search window that's on the current library site.
    o Hours from R25 is 16th on before-launch list (?I'm not confident about this).
    o Subsplus integration is 30th on after-launch launch
  • Status updates
    o Updated progress on some sections in writeboard
    o Helpdesk goal is to have something presentable for launch, get it proofread, then add to it over time
    o Keep overall estimate at 90% on college spreadsheet.
  • Should we send our sites to Communications for review? Yes, send LIS search landing page Feb 1. Doreen will do this.
  • Carrie will tell Alex he can make the changes he suggested to the LIS blog.  Ian says Alex already has editing privileges at a higher admin level, so we don't have to give him additional privileges. Carrie also will ask Alex if he still wants to meet with us, and tell him that the LIS web team has chosen to stay out of the discussion of a logo since it is our understanding that departments are prohibited from having their own logos.
  • Doreen can access Communications and Public Affairs photos. She can help us go in and get photos for web site.
  • http://midd2.middlebury.edu/offices/technology - This will have content, perhaps a subpage list.  It's Ian's responsibility.
  • Home pages for public computers: Should our team recommend which homepage should display on public computers in libaries and labs?  Nah--HelpDesk can determine this on their own.
  • Agenda for next week: Team members should add suggestions to agenda item list

2010: January 27

Present: Liz, Barbara, Carrie, Elin, Ian, Jess

News/Updates/Miscellaneous:

Launch is officially Feb 4th. Editing can continue through Feb 3rd. We'll make sure this goes on LIS blog after it's on the Webmakeover blog.

Wiki process - to remove pages, tag as "blank for deletion" in summary field. Ian will follow up on who will actually delete the pages.

Building & service point hours - wiki page will provide access to various hours wherever they reside, until 25Live system gets going.

Tech page - page at level above Helpdesk, Banner etc. pages - currently empty. Suggestion - it redirects to LIS homepage. Ian to do.

Agenda:

  • Help & Support Drupal pages. Not ready for prime time. How can we help get this done? Ian has asked Joe A. - Joe will have Ben provide assistance. Vaious meetings are coming up where this issue can be addressed. Team remains ready and willing to assist. Concludes that efforts now need to focus on web presence rather than wiki docs.
  • Quick links. We had a suggestion that all 4 Quick Links tabs should remain throughout the LIS site. After discussion, vote was tied so current structure - 3 tabs without the one refering to the page you're at - remains for launch.
  • Summary of web process to launch: Ian reports - this week functionality is still being added. Next week cross browser checking, formatting issues etc. will be happening. All team members should continue to browse the whole LIS site to spot & report glitches etc.
  • Usability testing. Conclusion - it's a priority for after launch. Continue to add suggestions for usability testing at http://spreadsheets.google.com/viewform?hl=en&formkey=dEZ5Nk8wbEZrYWt3T0xUaUdqQzF0MlE6MA Plan - LIS will conduct testing in addition to college-wide. Will ask for access to suggestions from above spreadsheet.

To do:

Add to agenda items - identification of material that will become dated. Larger issue - maintenance plan.

Check wiki start page design writeboard. Get new wiki start page in place (who?)

Team to check % complete figures writeboard & update

2010: February 3

Present: Elin, Ian, Carrie, Jess (notes), Barbara, Liz, Jim

News/Updates/Miscellaneous:

  • Sparkling apple juice, ginger cookies, and apples were enjoyed by all.
  • Elin's last work date will be June 30th.
  • Discussed lib. page node for feedback--is it necessary? may be removed
  • Library spotlight section of library page-fed with tag feed from blog "library spotlight" (name to be finalized)
  • Help & support pages much improved and ready for launch
  • Wiki workshop was well-received. Next time have the workshop focused to skill levels.
  • LIS page CAN be sent to Communications after removing the events feed (will not be ready by launch) (Doreen)
  • Tech banner doesn't click-will be resolved (Ian)
  • Carrie will tweak Helpdesk quicklinks drop down
  • Filling out the PFDP team 360 reviews: Sponsor will not see; just individuals and managers
  • Tags on the Drupal site: Unfinished business. This will be discussed in the coming months. Sense that at the moment it's more helpful for news and events, and not so much for basic content, but the functionality with regard to search will be changing.
  • Should we have table-tent or computer monitor signs encouraging people to give feedback on the site?

Launch business:

  • The site will be uneditable 2/4 starting at 9 a.m. until the College community receives an email from Ron Liebowitz stating that it is live.
  • MCMS will transition tomorrow to cms.middlebury.edu. Most of it will not be publicly available. You will be prompted to log in to view your pages. If there is something on the old site that needs to be accessible, inform Ian.
  • Elin will create a blog post about the launch of the new Midd Drupal site thanking all LIS staff members for their contributions, will also include thank-yous to wiki editors.

Wiki homepage:

  • Barbara will implement the main page switch [done]
  • Carrie will make a blog post about the switch [done]

Future agendas:

  • Discussion and formal recommendation for implementing the White Whale blog themes for both the LIS and other Middlebury blogs
  • Suggestions blog and Circ blog--discuss if they should merge or not
  • Revisit the tabled item of meeting with Alex to discuss recent Blog changes
  • Discuss the need to end the business of the team as it currently exists by 6/30 since we will be losing both our team leader and out team sponsor.

2010: February 10

Present: Elin, Ian, Carrie, Jess, Barbara, Jim

News/Updates/Miscellaneous:

Elin announced that Mike R. wants to have lunch with us. Cynicism ensued. Noonies was suggested as location.

Ian will give Jim a list of "go" links pointing to the Tech Help page - some of these should point elsewhere!

Agenda items:

  • Feedback on website - how to handle? Ian sees the form feedback and passes it on to appropriate primary contacts. Items relevant to the library pages go to Carrie. Decision was made to post these on the Basecamp "to-do" list, with responsibility assigned. Meeting time need not be given to discussion of these individual feedback items unless requested by a team member.
  • There are issues with browser IE6 - Ian will post to LIS blog about browsers supported/recommended.
  • End of the team. Elin will talk to Jeff about rearranging the team goals so that our work can be completed by June 30th. Our charge includes "develop site refresh strategies". We believe we can tackle that as well by June 30th as by the original date in August.
  • Search issues - Ian was to post next week about Google search updating, but he has already found a possible solution to the "Google providing links to the old site" problem & is trying it out as I write.
  • Blog themes. Does the team wish to recommend a White Whale theme to be used by the LIS blog? Or are we OK with the locally developed theme currently in use? Team vote next week - Jess will post links to WW theme examples in the agenda.
  • Blog merging. Should Circ blog merge into LIS blog? In principle yes, in practice it is very active and specific to circ and could deluge the public interest content of the LIS blog. Elin can make the decision. Similarly, the suggestions blog. Carrie will think about workflow, & consider any suggestions the team wants to make. Q. Where is the suggestions form? Should there be a separate suggestion page in the LIS blog? How can spam comments be prevented? - try "enable comment spam blocking".
  • Blogs review -  many inactive LIS related blogs still exist. All team members should examine the blog roll (sorry but the Brit in me can't help but think "bog roll") and contact the owners in their areas to see if these can be merged or just deleted.


2010: February 17

Present: Ian, Carrie, Barbara, Doreen, Liz. Elin (notes); Jess and Jim absent

  • Announcements/updates - Elin meeting with Jeff re: goals (re-scheduled to Mon 2/22); there will be a party to celebrate the web makeover on 3/12 in Atwater - stay tuned for details; Carrie will give a grand "tour" of the new LIS website to MBH faculty; Doreen will schedule the lunch (done!)
  • Absences - team will meet as long as there is an agenda and a majority; upcoming absences - Elin out 3/1-8 and 4/12 - 25; Liz out 3/22-26; Carrie out 3/3; Ian out 3/15-4/3 and last week in April
  • Forms - Ian did inventory - very few forms left on old web - he will follow up; Carrie will follow up on the Library forms question/feedback
  • Basecamp to-do items as a way to record feedback issues? May not work as hoped by Carrie - she will revisit how she plans to track feedback for Lib pages
  • Blog theme - general discussion; features, columns, headers, images, visuals, aesthetics, custom options and pros/cons of each theme. Width and number of columns are fixed on each theme, but each theme has customizable features. Rather than vote on 1 theme, and change the current theme at this moment, we would like to recommend that all WW themes be made available as an option - in addition to the themes developed by Alex. The team acknowledged Alex's good work in customizing our current theme; the team can offer valuable feedback in the development of custom themes. Ian will follow up with Alex and others and create a blog refinements/questions/suggestions Writeboard page on Basecamp. Ian will also follow up with Alex about the Media wiki template (http://chisel.middlebury.edu/~achapin/mediawiki/); changes need to be made to wiki template - header/footer, search box placement, meta links and style guide
  • Question about current placement of the Pages on the LIS blog. Ian will move the Pages section up.
  • LIS Blog changes to inform the LIS Enews(letter) better. Suggestions from Mike R. Agreed that this was a done deed and a good idea - Carrie will make the changes as proposed: New “Suggest a topic” form and spreadsheet https://spreadsheets.google.com/viewform?formkey=dElSV0JhU2pNcnJIME9ablI1bWFCbWc6MA. To be administered by ADs; revisions to LIS blog page “Good to Know”; create a new page called “How to post”? It would have instructions on how to post, a link to “Suggest a topic” form, and a link to “Good to Know”; change “Good to know” back to “How to…”? 
  • Trackback/pingback settings? Ian will make sure it's enabled.
  • Next steps for makeover PM’s? Now that the website is launched, a fellow project manager was wondering if it would be possible to be removed from the project managers email list, and also, if the questions and answers could be made available on the form questions and answers page - Ian will follow up
  • Lib page node for feedback – still there and links to college form. Ian will forward relevant feedback to team member primarily responsible; team member will evaluate and incorporate as appropriate; will bring to team any items that need broader input
  • Any feedback from Communications? Not yet.
  • Wiki  and blog training – next steps? Ian will check with Joe; there may be others - Alex, Ben - who may be able to provide workshops
  • Library hours on 25Live - Ian has a meeting scheduled
  • Thanks to Ian for taking on many follow-up items from this meeting

Future agenda items - add/edit items on Writeboard

  • Refresh strategies
  • Usability
  • Usability testing – add content to the Writeboard that Jess started


2010: March 3

(Meeting canceled due to <5 team members present)

  • Informally discussed need to focus on Usability testing and Refresh strategies-Check Basecamp!

2010: March 10

Present: Ian, Jess, Jim, Barbara, Doreen, Carrie, Elin (notes, sort-of...), Liz out

Ian or others, please flesh out these meeting notes when/if you get a chance :-)

Announcements:

  • Web party - there will be awards!
  • Ian out 3/15 - 4/3 (gone next 3 meetings)
  • Lunch - maybe re-schedule for April?
  • Elin met with Jeff briefly to ask about next steps for Web Team; stay tuned
  • Barbara and Ian working on custom search results pages (see Ian's blog post)
  • Jim - will not be able to dedicate much time to usability until mid-April

Usability

  • Many thanks to Jess and Ian for organizing our usability timeline, recommending ideas/software and testing possible software etc.
  • Ian set up instance of Infomaki for testing; will take resources to set up, let's make sure we really want to use this before we ask Ian to develop; are other tools that can do the Infomaki thing just as well? Infomaki does random questions very well
  • Ian described Silverback, Mac app uses iSight and audio, records interaction, Elin will request $50 to cover cost (check out the short video on the Silverback site)
  • Jess described Five-second test, 2 types - memory and clicking, Elin will request $50 to cover cost
  • Google Analytics - team will need to develop targeted questions for Chris, Ian will talk to Chris about GA
  • Key Survey
  • Survey Monkey
  • Heat Maps
  • Jing or other screencasting tools? Screenr? Community Clips?
  • Usability testing will include all LIS platforms
  • Does it matter if we test only on Macs?
  • Involve primary contacts in Usability?
  • Pull in other staff resources? Helpdesk/LIS student employees?
  • What about user agreements for testing?
  • Other budget requests? Incentive prizes and awards?


Mini-teams will come up with questions for each site: Technology Help: Barbara, Jim, Liz, Ian LIS pages: Elin and Doreen Library pages: Elin, Carrie, Jess

Remember to check Basecamp regularly for updates!

2010: March 17

Present: Liz, Jess (notes), Barbara, Doreen, Carrie, Elin

Announcements:

  • Website launch party was tasty. Blue cake was consumed (and worn, apparently) by many. Ian won the MVP award for the College Web makeover. Congrats, Ian!!
  • Elin postponed our team lunch at Noonie's until April since she'll be out
  • Confirmed that we have AD support for usability testing
  • ADs approved budget for Silverback and enhanced 5-sec. testing purchases
  • No budget for student incentives
  • We may be able to have student employees (either at the Helpdesk or at Circ.) test during their regular shifts. If needed, we may also revisit an idea to use some of the extra student employee budget to pay students to test
  • We may also consider enlisting the help of the Digital Media Tutors in the actual testing environment
  • Barbara will make survey for LIS staff on website (based on our previous key survey)
    • Team agrees that since LIS Staff were involved with building the site and have already voiced lots of feedback about it, and given our time constraints, this will suffice for the usability testing as far as LIS Staff is concerned. As a whole, the primary audience for LIS pages is students, (with faculty and staff being second)
  • Clarification that click heat testing is for data gathering but not for our observational usability testing phase
  • Clarification that Web feedback about LIS pages sent to Ian is passed along to the primary contacts
  • Bryan expressed interest in being involved with usability testing of library pages. Jess will put out a call to all LIS staff via the blog to see if anyone else wants to help or has additional questions or concerns they want to include for the testing

Goals & Next steps?:

  • Move ahead with small group work
  1. Think about the questions you have and match tools to questions.
  • Keep in mind we'll be coming back together as a group to combine questions from each of the 3 subgroups and our testing sessions as a whole should be no longer than 30 minutes (ballpark at this point)
  1. Aim for 5 (ballpark) questions for the Silverback portion of the testing
  2. 5 second tests can be essentially unlimited
  • Each small group should download one 30 day trial version of Silverback and test out their 5 questions and see how long it takes to complete them (need a Mac with a webcam to do this)
  • Questions about how to proceed with the Helpdesk questions. Liz and Barbara will muddle through as best they can
  • Start thinking about when and how we will advertise the call for student testers (see new writeboard in Basecamp)
  • Jess will clean up some writeboards (delete them) and put them in the Files section for archival purposes

Team direction:

  • Elin will formally ask ADs to tell us their plan for the LIS Website team. It doesn't make sense for us to propose changes until we know what they're planning. We'll review their response and if necessary form a counter-proposal.

2010:  March 24

Present: Liz, Bryan, Jess, Doreen, Elin, Barbara, Carrie (notes)

Announcements:

  • Elin has asked Jeff for AD input on fate of web team. Jeff will ask ADs via email.
  • Carrie has observed that people who are used to the old website have a harder time with the new site. We should consider supplementing this semester's testing with testing done in the future. We'll get some baseline measurements now, at least.
  • The Web Services workgroup has begun discussing usability testing for the whole college site. They're aware that we're doing it for the LIS site.
  • Carol has purchased Silverback; we have a license now. We'll wait til Ian returns to install.
  • 5-second test is different. You purchase tokens as you go. Doreen might be able to purchase with her p-card.

Review Silverback Questions:

  • HelpDesk has 5-6 questions. Will split into students and faculty/staff.
  • Library has 5 questions for students, 5 for faculty (with some overlap). Some questions are duplicated for the LIS landing page. We can remove these.
  • LIS has 5-6 questions. Will remove questions from external audience. Will split into students and faculty/staff.

Next steps for testing:

  • Jess will put all questions in 1 writeboard. Sort Silverback by destination (eg, LIS landing page, Library page, HelpDesk page) and audience. Might not need to sort 5-second tests; will investigate.
  • Goal for Silverback is 12 questions for students, 12 for faculty/staff.
  • Questions will be grouped by destination, but not labeled as such.
  • Carrie and Elin will add HelpDesk questions.
  • Add a question: How to get to course website/Segue
  • Bryan will ask Joe for permissions for the LIS website section of basecamp so that he can work on the usability questions there

LIS Survey:

  • Carrie and Barbara added 3 questions about LIS communications due to Mike Roy's interest in creating an internal LIS blog. Barbara will remove these, and Carrie and Barbara and Doreen will work on the issue through other venues.
  • Barbara will fix typos as reported by team

Marketing:

  • We will use Dean of LIS email account to invite all students and all faculty/staff to participate in observational testing.
  • After we've met with [target number=?] users, the remainder can be sent a link to our 5-second tests.
  • Need to list next steps (eg, who will do the scheduling, where will the testing be done?). Add to writeboard?


2010: March 31

Present: Liz, Jess, Barbara, Jim, Carrie, Elin

Announcements:

  • Circ has arranged an RSS workshop - watch the blog for details
  • Office 2007 is now recommended for use at Midd. & is available for download. Jim will post details to the blog.
  • Elin has updated the team goals document & will move this document to Basecamp.
  • Jess is going to moonlight at the Digital Archives team!!
  • Elin is asking all members to consider if they'd want to stay on any on-going version of this team.
  • We have 6 staff & 9 student responses to our web survey so far. Elin we e-mail LIS staff & student workers with a reminder.

Agenda items:

  • Silverback usability testing questions. Liz edited the questions during the discussion. See Basecamp writeboard for latest versions.
  • 5 second testing has been determined to be unsuitable for our needs. Carrie will conduct further testing of Usabilla instead. (note if we'd used Survey Monkey, we could have had an all ape software suite)
  • All team members are asked to check the e-mail format for soliciting usability test subjects. Writeboard here.
  • Elin will check out a faculty Mac laptop and get Silverback installed. Current plan for testing - Carrie, Jess, Barbara (anyone else?) will conduct 20 - 30 individual tests during the period April 12th - 23rd. Elin will look into using an empty ref office to conduct the testing.

2010: April 7

Present: Liz, Barbara, Elin, Ian, Doreen, Jess, Jim, Carrie

Announcements:

  • All campus email about usability testing was sent out. Barbara has already received several replies, including one from Faculty.
  • Jim will soon be making a post about Office 2007 support on the blog.
  • April 28th 3:00-4 PM will be an RSS workshop hosted by the Circulation Services team in LIB 105 with Alex Chapin.
  • Goals are up on basecamp and will be posted to the Project Directory.
  • Liz, Jess and Elin will be out next week. Ian will be out the following week. There will be no all team meeting next week, but the people working on Usability Testing may meet.

Agenda items:

  • LIS blog. Barbara advocates allowing LIS to set up a "private blog" as she suspects that there will be very little posted there and we can use this to prove our point about the utility of a private blog for LIS.
    • Do we have any stats comparing the current LIS blog with the old LISt blog? Ian will follow up and check on this.
    • Comment from Managers meeting: "Blog is not very interactive".
    • Jess: we should not assume that this is the end-all-be-all of communications and we should try other methods.
      • From the survey: people don't understand the benefit of the information coming from the blog.
    • If LIS is going to set up a private blog, this team does not need to be a part of setting that up.
    • Liz: we need to make sure that people having the training and tools to use the blog before moving on to other schemes.
    • Doreen: people were spoiled by email because there were summaries and links to articles for more information.
    • Barbara: we should have a time at an all LIS meeting where we discuss communication within LIS. The requirement to stay informed of the work within LIS should be stated to employees.
    • Ian: make recommendations to the area directors that we (1) have a discussion at an all LIS meeting to discuss LIS communications, and (2) if you want to set up a private blog, go for it. Our team will continue to offer support and training for using these tools
    • Team decision: we will post these recommendations to the blog and solicit feedback. This item is off the agenda for a month.
  • Usability testing
    • Jim will talk to Joe about having Ben help out with Usability Testing.
    • Testing timeline: we are on target
    • Ian and Barbara will look at the Usabilla questions and come up with screenshots with 5 questions for each area
    • Jim will look at that section as well and add questions for his area
  • Survey Report
    • Barbara has created another Writeboard with links to summaries of both surveys. Barbara will make spreadsheets available.
    • The majority of responses said that the site has improved over its past version.
    • Team members should comment on the results or add other observations on the Writeboard that Barbara has started.
    • Ian will compare results from current and past survey and share results with the group.
    • Noted: 0 survey responses from LIS Administration (well, 1 who marked themselves as 'AD' in the workgroup section

2010: April 21

Present: Jim Barbara Carrie Doreen Jess Liz

  • Thanks to Jim for posting on the Blog about MS Office 2007
  • Silverback testing discussion
    • Getting more students from LIS Student employees
    • How are we going to use the results? Combine individual findings and create general guidelines for persons responsible for content
    • Technical issues with Silverback and storing the video files mostly resolved
    • Is debriefing okay for our testers? i.e. helping them understand the things they find confusing-yes, it's okay
    • Searching is still an issue for many users contacting the Helpdesk, but we've seen an improvement when it switched to the Google search (away from local)
    • We're relatively on-track
  • Future of the team: Elin will post the AD email response to Basecamp
  • Usabilla finalizing questions and inputting the screenshots (Ian was tasked with starting this) Barbara will take a look and will see what Ian has done so far
  • LIS Staff survey comments: Barbara will extract and put in a spreadsheet stored in middfiles and will put the pathway to this in Basecamp
  • LIS Blog (mini-note!) seems like there's a sense that it'll stay in one blog form for the time being

2010: April 28

Present: Barbara, Elin, Carrie, Ian, Jess, Liz
Notes: Ian

  • Announcements
    • Jess is done with her internship and is in the last week of classes for her MLS
  • Revised LIS Website Team to be formed this summer
    • Recommendation (from Elin): four people is probably enough for this team
    • Recommendation (from Barbara): continuing members from the current team is preferable
    • Recommendation (from Ian): if the new team will be focused on refresh workflow, our team will spend the remainder of our time working on the usability review
    • Recommendation (from Carrie): membership of the new team should be based on sections of the website, not LIS areas
  • Usability Testing
    • Jess has three more students to work with
    • We will have about 20 usability reviews completed through Silverback
    • Jess will transfer the spreadsheet to Google Docs
    • Silverback testing to be completed by next week
  • Usabilla
    • Team will review the questions on the Usabilla Writeboard
    • Ian will create the tests in Usabilla tomorrow morning after the team's review
    • Ian will add widgets from Usabilla to each of the sites under review
  • Usability Analysis
    • We should create a heading for each area of the site, plus the blog, plus the wiki with recommendations under each
    • We'll create this in Google Docs
    • Some discussion of what platforms we're using to do this

2010: May 5

Present: Barbara, Elin, Carrie, Ian, Jess, Liz, Ian, Jim

Powered by MediaWiki