Middlebury

LIS Documentation

LIS Documentation

LIS Website Primary Contacts

This page contains archived information, and the content is no longer current. See the list of LIS Content Manager here LIS Website Content Managers 2010-2011

This is a space for the LIS Website Team to discuss approaches for meetings with primary contacts for major content areas of the LIS website, and to share resources with the primary contacts if so desired. It may include FAQs, checklists or deliverables, and lists of resources to help us work through the process of reviewing content and planning for the new site.

Contents



Contacts for Site Content Management

Part of Site Team Contact External Contact
Library Carrie Macfarlane Bryan Carson
Library Portal Barbara Merz Mike Lynch
MediaWiki/Helpdesk Jim Beauchemin Jim Beauchemin / Ben Molberger
About LIS/Landing Page Doreen Bernier Jeff Rehbach/AD Team
Blogs Ian McBride Joe Antonioli
Telephone Services Liz Whitaker-Freitas Peggy Fischel
Banner, etc. Documentation Liz Whitaker-Freitas Marcy Smith
Circulation Elin Waagen Kellam Ayres
Special Collections Jess Isler Andy Wentink
Music Library* Jess Isler Dan Frostman
Armstrong Library* Carrie Macfarlane Todd Sturtevant/Nancy Reynolds
Media Services Jim Beauchemin Petar Mitrevski
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)
Digital collections Barbara Merz Digital team (Mike Lynch)


  • These are the major content areas defined by the team. Other departments and work groups will be deal with the primary contacts applicable to their area. i.e., the Reserves page(s) will be handled by Kellam since she is the PC for Circulation, and Reserves is part of Circulation(/User Services).
  • We should evaluate whether or not Music Library and Armstrong are essential on top-layer of the IA, or whether links within departmental pages and LIS landing page/Library landing pages suffice

Deliverables/Checklist

  • DIY Workbooks due October 6, 2009
  • Late October: Training workshops and sessions for content editors. Content editing in the Drupal CMS may commence!
  • Old CMS expires January 4, 2010

One Blog Concept Explained

One recommendation of the LIS Web Makeover team is for LIS to maintain a single, unified blog: truly "All Things LIS".

Adapted from our recommendations document:

LIS staff contribute to a wide array of blogs on Middlebury's Wordpress installation. As new working groups and teams are formed, each has a tendency to create their own blog. This blog then needs to be publicized, requires people to subscribe to a new feed of information, and requires the content authors to switch contexts between the many blogs they may edit. On July 1, 2009 we identified 22 blogs run by members of LIS, with the majority belonging to working groups or projects. The number has since grown.

We recommend that LIS unify their blog-based communications within a single blog. All LIS staff will be made authors of this blog, with the ability to approve their own posts. We will encourage, but not require, LIS working groups and teams to move their communications into this blog, using categories to separate out posts and allow subscribers to focus on the content which most interests them. For working groups with established blogs, we can migrate the existing posts and comments into the new "All Things LIS" blog and add categorization. LIS personnel who maintain personal blogs will be allowed to migrate their communications into the central blog, provided the content is related to their profession. The completion goal of this effort is the creation of a blog which is truly "All Things LIS".


One Blog FAQ's

  • Q: Can everyone at Middlebury/in the world see the contents of the blog?
    • A: Yes! None of the content is private. Sensitive information, whether technical or administrative, would not be part of the blog.

  • Q: Who can post on this blog?
    • A: All LIS staff members can post.

  • Q: How will we prevent inappropriate posts?
    • A: There will be no gate-keeping, or pre-approval of posts. The blog will be part of the LIS work world. Staff can be expected to apply professionalism and good sense just as when they talk or e-mail at work. Posts could feature in pfdp evaluations after all! Inappropriate behavior would be an issue for the manager to deal with.

  • Q: What about information that is only of interest to some LIS staff?
    • A: Categories and tags will be used to divide up the posts into content areas, enabling readers to find the posts they might be interested in and in particular set up feeds so they can easily keep up-to-date.

  • Q: What is the difference between a category and a tag, and how do I know when to use them?
    • A: Categories are pre-defined by the LIS Website team, and they reflect audience, functional LIS work areas, LIS teams, and Middlebury Institutions. If additional categories are needed, we reserve the right to add them. Tags are an additional way to define post content. We may create an initial pool of terms when we transition to the One Blog, but in general, these are user-supplied.

  • Q: What if I only care about reading posts with a specific tag or a specific category?
    • A: You can subscribe using RSS to receive posts for the specific tags and specific categories in which you're interested.
      When subscribing to Wordpress Categories and Feeds via Google Reader: Add /feed to the end of the category or tag URL

  • Q: How many categories and tags should my posts have?
    • A: Each post will need at least one category. You may use more than one category. Tags are optional but encouraged. You may use as many tags as you wish.

General FAQs

  • Q: Will a link to my department/content exist on the LIS landing page?
    • A: If it is one of the sections on listed in the recommendations document, yes, otherwise, no. The idea is for the landing page to be a quick reference to all things LIS, but we won’t be able to list every division, office, and department of the organization because we want a simple list of options for people to choose. This does not necessarily mean that the department is not prominent in other parts of the information architecture of the site. It may have its own search landing page or be one of the links on the top-level landing pages in the Drupal site, such as with the Library.

  • Q: Will there be a “featured departments/events/exhibits/goings-on” spot on the LIS landing page?
    • A: I think the LIS landing page should have a calendar widget listing space availability, but events should be advertised via another calendar widget that appears on the LIS blog, since that will be our public outreach system. This calendar would feed events out of R25.

  • Q: If I have an exhibit or event or online project being launched, can I advertize it on the LIS landing page?
    • A: It could be advertised on the LIS Blog either through an event listing in R25 or a blog post about the event, or both. This is one of the reasons why I think allowing all LIS staff to contribute to the blog is beneficial: it allows easy announcement of LIS related events without delay until publication or approval through committee.

  • Q: Can I name my part of the LIS site whatever I want? (What if I want to name it something other than what my department is called?) Can I separate out parts of my site as I see fit?
    • A: I see no reason not to allow the site naming to be done by the people in charge of that area. I’ve already told the Curricular Tech team that there will be a link on the LIS landing page to something about CT and they get to decide what that link is called. I would encourage people to name their area of the site something related to its content rather than related to the organizational name, should such a difference exist. I see no problem with separating out content into multiple section, provided its done with the intent of making the content easier to browse as I’m sure is the case here.

  • Q: Is creating my content in a Drupal page the best way to display and organize my department’s dynamic content (video, images, audio, etc.)?
    • A: Drupal is the best system available for creating a site with a hierarchy of information, managing the permissions for that hierarchy, and including content from other sources (other pages in Drupal, other blogs, etc.). All of the systems we maintain can include multimedia like images, video, and audio. In fact, for video and audio, we recommend uploading that to MiddMedia, which can then be used to include the content in Drupal, Wordpress, and/or MediaWiki. Still, if you’re trying to build a site that will be a tree of related information with multiple authors, you’re best served creating it in Drupal. That’s not to say that it *can’t* be done in those other systems, just that you will find they aren’t as well suited for the task.

  • Q: What if I want to use blogging tools than Wordpress as part of my department’s web presence?
    • A: Wordpress is the blogging tool that is run locally at Middlebury and will be supported by staff. We won’t stop you from using other blogging tools and you will be able to include feeds from any blog you like in a Drupal site, but we won’t offer support or assistance for design, plugins, authentication, etc. for other blogging platforms.

  • Q: How can I use MiddLabs, and other tools of the new College website to best communicate my department’s services and collaborative activities?
    • A: We don’t know what MiddLabs is yet, so this one is harder to answer. The Web Redo Coordinating Committee will receive White Whale’s recommendations for content in MiddLabs on 9/11. Joe has been very good about forwarding these to the relevant groups as they come in. Still, this does not mean that the recommendation will be approved by Middlebury on that date. We’ve been curious to see how MiddLabs will work without adding to the curricular workload and I personally expect there will be some negotiation on that point after we receive the recommendations.

  • Q: Can I start building my department's Wiki pages now? Will the new LIS Wiki structure require any content migration of my current pages?
    • A: Yes, you can start building Wiki content now. The changes made to the Wiki Main Page will not require migration of your content.

  • Q: Should I (or can I) consider restricting access to certain kinds of content I include on the Wiki, like screenshots of proprietary systems in my documentation guides, or, say, excerpts from copyrighted documents that I am sharing for educational use?
    • A: Entire vendor-provided manuals should be stored on Middfiles. Screenshots should be fine. Copyrighted documents, etc., use your discretion, or contact Jeff Rehbach if you're unsure.

  • Q: To clarify, ALL Middlebury Users, once logged in, can edit LIS Wiki pages?
    • A: Yes. ALL Middlebury Users (those with Middlebury username and password credentials) once logged in, can edit ALL LIS Wiki pages. Since users must log in to edit, all changes are therefore linked to the user making the changes (Viewable in the History tab at the top of the page).

Personal pages on the new website (Some DRAFT definitions from the Web Redo Group):

  • Customizing and personalizing post

  • Portal= a personalized & customized user page for interacting with Middlebury.edu. Not published for others to see. Comparable to iGoogle, MyYahoo, etc. (but probably not widget-y in first iteration).

  • Directory Listing= public presentation of the data coming from Banner (departments, address, email, phone, office hours, etc.) Accessed through online directory search, and departmental sites pulling staff/faculty info. Can link to profile. Please note: A link to your profile will enable you to display additional info (e.g. family, education), but this information will _no longer_ be displayed through the directory listing (per LIS, College Communications, and HR policy).

  • Profile= public presentation of your information, fully customized and editable (by you). Can include feeds, images, video, links (internal & external). Set-up templates for defaults by classification (faculty, staff, student, etc.). Can feed from other dynamic systems - faculty pulling current course offerings, calendar of relevant events, etc.

  • Personal Website= anyone can build and maintain their own website independent of the core Middlebury.edu design and IA - using WordPress, HTML, or other platforms. Web services will support building such sites on WordPress and other currently supported platforms (like Segue for the time being).

Resources

Powered by MediaWiki