Proposed Agenda for Thursday 9/17
Feel free to add/edit agenda items
The One-Blog readiness vote
Timeline – CMS freeze date for changes/additions
Updates on work with our contacts
Curricular Technology – where in the IA?
Wiki training for our primary contacts?
Permissions for primary contacts access on web makeover folder in middfiles?
Great news!
Tonya from White Whale will be able to meet with us next Wednesday at our regularly scheduled meeting time. I have changed the meeting location to Lib 221. Hope this works for everyone – this opportunity to meet with WW/Tonya came up rather suddenly. Thanks for arranging this, Ian!
Agenda
Information Architecture discussion with Tonya from WW
So that we can dedicate the full meeting to this topic, I propose that we vote on the One-Blog readiness at our Thursday meeting.
Please post suggestions for questions we’d like to ask Tonya about the site IA in the comments section of this post.
For discussion.
What should we call the External category instead of External? Suggestions in the running:
Do we need an All LIS category?
In this meeting we took a step back and reviewed what we have done to date and how to proceed this fall.
The new Curricular Technology site will be built in Drupal using the templates to be delivered by White Whale. The site will feature largely static HTML content with descriptions of the services offered by LIS in this field, with some videos and RSS feeds to help explain the offerings. The Curricular Technology team will build out the site’s content, reusing already developed versions of these pages in several systems. Where documentation for these services already exists in the LIS Wiki, it will remain there and be linked to from the Curricular Technology site.
As there is not currently a place in the information architecture for the Middlebury web site for Curricular Technology, per se, it will be up to the LIS Website team to determine an appropriate place and confirm the location with the Curricular Technology team.
Here are my initial ideas of how this could be organized.
Existing Infrastructure
We’ll take the current LISt blog, rename it to just “LIS” and grant all staff in LIS Editor access to the blog. Student workers and LIS-related people like department advisory groups will have Author access granted as needed.
Porting Content
Users and groups with existing blogs may move their content into the LIS blog by going to Tools -> Export -> Download Export file in their blog, then Tools -> Import -> WordPress -> Upload file and Import. After doing so, they should go to Posts -> Categories and use the Category to Tag Converter to change any custom categories their blog had into tags on the LIS blog.
Categories
The LIS blog will start with this set of categories:
All other existing categories in the LIS blog will be changed to tags. In general, we’ll encourage the use to tags to mark things like posts that have photos in them, posts about particular workgroups, posts about particular projects, or other things that tend to have a more temporally mutable quality to them. Categories will be used chiefly for broad categories that change infrequently.
Private Blogs
The LIS blog will not be used to store private content. Groups, such as ACS, who wish to have a private blog should continue to use and maintain their blog in its present form or create new private blogs if one has not yet been set up.
Internal vs. External
Posts that are likely to be interesting only to LIS staff should be marked with the Internal category. Examples of this content might include a notice about LIS goal setting. Note that these posts would still be readable by the public, but that those subscribed to the public feed wouldn’t see them in the feed. Posts that are likely to have broader appeal, like a cookie party for students, should be marked with the External category, or both the Internal and External categories.
There will be links to both the External and Internal feeds on the blog homepage with a description of the content featured in each so that site visitors can choose how they will read about LIS.
The Curricular Technology team did a lot of brainstorming over the summer. This seems like a good time to step back and compare what we have done to what our priorities are:
We have a lot of projects started whose focus is to find one or more replacements for Segue including a CT feature matrix, a CT needs “knowledge grid” (i.e. what do we know and not know about technologies that faculty and students need), course site platform survey questions.
Agenda 9/9
Notes: Jim
Moderator: Liz?
Ian will be away; Carrie may be out
Announcements etc. (10 min)
One blog – discuss when and how; decide on categories (bring your list of possible categories); private v.public; external v. internal use (30 min)
Timeline – set freeze date/s for changes/additions to current LIS site. (10 min)
Agenda for Thurs? (5-10 min)
Upcoming/continuing project timeline items:
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
You must be logged in to post a comment.