Last meeting!

A few updates... 

  • UIG meeting on Thursday @ 3:15: Peter, you still want to go?
    • YES, he would love to!
  • I'll make first pass at creating/organizing documentation, then I'll hand it back to group by next week for contributions.  (I tried to think of a good way to break it up, but I just couldn't!!  I don't think there will be much more than what we already have...)
    • Angie can help if needed.  We can also make a video, but they already have one....
  • I'll schedule the trainings in July and send out an e-mail asking for volunteers.  (If you have a favorite day/time you'd like to sign up for, let me know...)
    • Training primarily for people creating/editing PUBLIC pages.  Need to ask UIG about using this for staff pages.  Focus to start needs to be for public pages, especially for training and support to start.
  • This will be presented to RISG next week.  Update on what happened in UIG, etc.

Discussion:

  • Where should list of databases & descriptions go?  Here are a few samples I just threw together (don't pay attention to the content, just the placement of the list).
    • In main body of front page: http://libguides.mit.edu/content.php?pid=10932
    • In separate tab: http://libguides.mit.edu/content.php?pid=10933
    • Which do we like?  Everything under a tab, or everything on the page?
    • Have default be one big box as the home page, including profile box.  People can then customize this list as they see fit, or just leave it and it will all be in one place.  People can copy this box to use it in other ways.
    • Not sure if these "templates" Marion is creating will be updated by Marion, or if they will not.  So should we link to the box, or copy the box?  Who's responsibility will it be to keep database lists updated?
  • Anything else we'd like to ask Darcy change about the look and feel?
    • Box headings need to be more apparent... bolder, bigger, etc.
    • Font should be consistent.  Can this be locked down, or do we need to tell people what font to use?  Verdana?     Will the automated text at the top of the screen be the Libguides default (non verdana) and will that look weird?
    • Text colors?  Links are always blue.  Use Web Guideline policies for use of text color, to be consistent.
    • White space is nice within a box.
    • Which box to use for database descriptions?  Rich text or web links with more info?   Default (for Marion) will be Rich Text.  Need more white space around each database.  Descriptions should NOT be in italics, and maybe indented or set apart somehow.
    • People do NOT need photos.  Just contact info in the top right corner.
  • Custom fields:  LibGuides allows each institution to set up 5 custom fields for profile pages...  (ex., what's your favorite color?)  Ideas?   
    • Who will decide what questions to put on the profile?  It's not us.  These will NOT be required for the profile box.
  • No labels