Edit WYSIWYGattachfile Attach PDF Raw View►More Actions▼More Actions

Restore topic to revision: You will be able to review the topic before saving it to a new revision

Copy text and form data to a new topic (no attachments will be copied though).
Name of copy:
You will be able to review the copied topic before saving

Rename/move topic... scans links in all public webs (recommended)
Rename/move topic... scans links in UMeetings web only
Delete topic... scans links in all public webs (recommended)
Delete topic... scans links in UMeetings web only

Revision Date Username Comment
1222 Nov 2011 - 09:40dahl0842? 
1129 Aug 2011 - 10:58sumer001? 
1017 Jun 2011 - 10:36SantiagoFG 
926 Feb 2010 - 15:23sumer001? 
817 Feb 2010 - 11:54sumer001? 
729 Oct 2009 - 13:58afreeman? 
629 Oct 2009 - 13:05AdamOverland? 
529 Oct 2009 - 12:53sumer001? 
421 Jan 2009 - 10:47DrewStevenson 
330 Sep 2008 - 13:07DrewStevenson 
earlier first

Render style:     Context:

 History: r12 < r11 < r10 < r9 < r8
[X] Hide this message.
Notice: On June 30, 2016, UMWiki service will be decommissioned. If you have information in UMWIki that needs to be preserved, you should make plans to move it before that date. Google Sites is anticipated to be the most popular and appropriate alternative for users because it offers a more modern and user-friendly interface and unlimited capacity. To learn more about the features of Google Sites and other alternatives, and to identify which one best fits your needs, see the University’s Website Solution Selection Guide. If you have concerns or would like help regarding this change and your options, please contact Technology Help at help@umn.edu
You are here: UMWiki>UMeetings Web>WebHome (22 Nov 2011, dahl0842)

UMeetings: A wiki of U of M Standing Meetings

This is the beginning of a compilation of standing meetings, by functional area, at the University of Minnesota. Such a list has never been compiled before and its comprehensiveness, and therefore usefulness, will depend on contributions from many. We invite you to add to this new resource. Meetings that are relevant to this list are those that are open to guests for consultation or sharing of information.

Skip to:

Budget and Finance
Data and Analysis
Student Affairs/Student Services
Human Resources
University Libraries
University Services
Coordinate Campuses

1. Leadership

President's Executive Committee
What: The President's Executive Committee is comprised of the U's three senior vice presidents, the vice presidents and general counsel, the coordinate campus chancellors, the director of athletics, associate vice president for the department of internal audits, and the president of the University of Minnesota Foundation. The purpose of the committee is to advise the President on key issues facing the University and to provide a weekly opportunity for U leaders to discuss these issues.

When: The committee meets weekly from 8-9:30 on Mondays and its agenda is often set far in advance.

Contact: To discuss opportunities to meet with the Executive Committee, contact the office of Vice President and Chief of Staff at 612-625-1501.

Twin Cities Deans
What: The Senior Vice President for Academic Affairs and Provost convenes a monthly meeting of the deans of the 18 colleges and schools on the Twin Cities campus. Additional academic deans also attend. The purpose of this committee is to discuss items of importance/relevance to deans such as policies, financial changes, and academic and other issues common to many deans. It is also an opportunity to hear from the president and provost

When: The meeting is held on the second Monday of every month from 1-3 p.m.

Contact: To discuss opportunities to meet with the Twin Cities Deans, contact the Office of the Senior Vice President for Academic Affairs and Provost at 612-625-1105 or provost@umn.edu.

Chancellors monthly meeting
What: The Senior Vice President for System Academic Administration convenes a meeting of the four coordinate campus chancellors on the Wednesday afternoon prior to each Board of Regents meeting.

When: The meeting is held from 3:30-5:00 p.m.

Contact: To discuss opportunities to meet with this group, contact Deb Cran at cranx001@umn.edu.

3. University Budget & Finance

RRC Managers
What: The RRC Managers act as the primary liaison between their Resource Responsibility Center (RRC) and University Budget & Finance; overseeing the budget process for their RRC; reviewing and approving financial transactions on behalf of the RRC; and monitoring RRC financial transactions for compliance with University, State, and Federal policies. A current list of RRC Managers is maintained on the University Budget & Finance website, accessible at http://www.budget.umn.edu/other.htm.

When: The RRC Mangers hold an informational meeting on the third Wednesday of every month, except August, when there is no meeting, and December, when they meet on the second Wednesday. Meetings are not open to the general University population due to the capacity of the meeting room. Agendas are set and circulated to members one week in advance of each meeting, following a call for items.

Contact: To be included on the agenda, to be added to the distribution list for the group's monthly Call for Agenda Items, or to correspond with the RRC-L listserv, please communicate with University Budget & Finance at 612-625-4517 or ubudget@umn.edu.

5. Data and Analysis

University of Minnesota Analysts Group

What:The University of Minnesota Analysts Group is an informal group of university staff who perform data analysis as part of their responsibilities. The group works to share knowledge and perspectives related to university data, systems, and policies, analysis tools and techniques, and approaches to research questions.

When: The group meets monthly

Contact: For more information on the group, please contact: Peter M. Radcliffe, Director of Planning and Analysis, Academic Health Center, radcl002@umn.edu, (612) 624-1992 or Steve Gillard, Director of Data Management and Business Intelligence, College of Food, Agricultural, and Natural Resource Sciences (CFANS), sgillard@umn.edu, (612) 625-6792.

4. Student Affairs/Student Services

Office for Student Affairs Directors Meeting

What: The leadership of the various units within the Office for Student Affairs meet regularly with the Vice Provost for Student Affairs to discuss issues and share updates about their programs and services.

When: Generally every other month, but the schedule varies

Contact: To discuss opportunities to meet with this group send an email to osaum@umn.edu.

Student Affairs Student Advisory Board (SASAB)

What: The purpose of the SASAB is to provide advice to the Vice Provost for Student Affairs regarding the out-of-classroom student experience, and to provide a forum for students to discuss concerns or issues which impact the student experience. The Board consists of approximately 25 representatives of different student organizations in addition to several at large members. For more information about the SASAB please go to

When: The SASAB generally meets once a month during the academic year.

Contact: To discuss opportunities to meet with the SASAB send an email to osaum@umn.edu.

Registrar's Advisory Committee (RAC)
What: RAC serves as a consultative body to the University Registrar and ASR Director. RAC members collaborate with ASR to improve critical services for students, faculty, and staff including: process improvement, policy clarification and creation, system enhancements, and reporting features.

This is an open meeting and all interested parties are encouraged to attend. Attendees come from every college, campus, and departments throughout the institution. This monthly meeting plays an important role in ensuring that ASR is providing meaningful support and services to collegiate staff in their role of supporting the University's mission. https://asr.umn.edu/rac

When: First Monday of every month from 10:00-11:30 a.m. (If the first Monday of the month falls on a holiday, the meeting is held the second Monday. In January and August, the group meets from 9:00 a.m. until noon.)

Contact: To discuss opportunities to meet with this group contact the ASR communications coordinator at communications@rt.asr.umn.edu .

Scholarship Administrators meeting
What: The purpose of this meeting is to discuss best practices in scholarship administration, from fund raising to payment. Attendees include any staff who have a piece of scholarship administration as a part of their job, including stewardship professionals, student services staff, accountants, etc.

When: First Wednesday of every month at 1:00pm in RM 101 Walter Library

Contact: To discuss opportunities to meet with this group, contact the OSF Scholarship Unit at srhelp@umn.edu.

5. Human Resources

HR Pros
What: The Office of Human Resources convenes meetings of human resources professionals from across the University. This meeting is geared toward individuals performing human resources functions. In general, these meetings are used to address new initiatives and changes in human resources policies and procedures; provide status reports on human resourses-related projects; and share pertinent information to keep the community current.

When: The group meets quarterly. The day and time varies and is announced on the HR Pro web site at http://www1.umn.edu/ohr/hrpros/meetings

Contact: To discuss opportunities to meet with this group, contact the Director of Human Resources Policy Development at 612-625-9872.

6. Technology

Enterprise Planning Group
What: The Enterprise Planning Group (EPG) plays a strategic and shared leadership role in helping the Office of Information Technology (OIT) and the University achieve its commitment to advancing excellence in information technology. The EPG brings together key core University business-process leaders from across the system to provide insight and input on the University’s Enterprise Resource Planning (ERP) systems as well as its strategic technology directions and priorities.

When: The groups meets quarterly.

Contact: To discuss opportunities to meet with this group, contact the Director of Enterprise Project Management at 612-626-1984.

7. Research

Council of Research Associate Deans
What: The Council serves an advisory role to the Vice President for Research (VPR). Members assist the VPR in formulating University-wide policies and systems, promoting faculty productivity, and advancing strategic goals. Each college, school, and coordinate campus may be represented by an Associate Dean for Research or another academic representative having broad responsibility for the research for that particular unit. For more info, see http://www.research.umn.edu/crad

When: Third Thursday of each month from 1:30-3pm in 101 Walter Library.

Contact: To discuss opportunities to meet with this group, contact the Chair, Judy Garrard, at 612-625-8772

8. University Libraries

Librarian’s Cabinet
What: The Librarian’s Cabinet is comprised of Libraries senior leadership. The purpose is to shape strategic planning processes and resource allocation, assess campus issues and priorities for Libraries’ engagement, develop agenda for LLC, communicate about activity and inter-division coordination, consult on critical organization issues.

When: Weekly. 8:00-10:00 a.m.

Contact: To discuss opportunities to meet with this group, contact Jennifer Reckner, University Librarian’s Office, 612-624-9338, reckn001@umn.edu.

The Libraries Leadership Council (LLC)
What: The Libraries Leadership Council serves as an advisory council, comprised of program directors, that reviews issues and recommends courses of action to the University Librarian. The purpose is to set Libraries priorities and goals, and review divisional goals; manage resource allocation processes, review requests, and recommend allocations; identify and analyze cross-cutting and systems-wide issues and recommend action; review and endorse policies; integrate operations and programs across the organization; charge councils and ad hoc groups to address specific issues.

When: Libraries Leadership Council meetings on the second and fourth Thursday of each month, 8:30-10:30 a.m.

Contact: To discuss opportunities to meet with this group, contact Jennifer Reckner, University Librarian’s Office, 612-624-9338, reckn001@umn.edu.

Libraries Staff Assembly
What: The Library Assembly serves as the legislative body of the University Libraries and is held on a quarterly basis. It provides a forum for discussion of policies, procedures, and other pertinent issues. The Libraries' Constitution and Bylaws detail the definition and function of the Assembly.

When: Quarterly

Contact: To discuss opportunities to meet with this group, contact Jennifer Reckner, University Librarian’s Office, 612-624-9338, reckn001@umn.edu

9. University Services

The BRIDGE group
What: BRIDGE members act as the primary liaison between their Department/Division and University Services. Appointed by their Dean, members provide feedback to University Services regarding facilities issues and program priorities while serving as a communications focal point for their organization.

When: The BRIDGE group meets the third Tuesday every other month from 10 am to Noon in room 325 of the Ed. Sciences building.

Contact: To discuss opportunities to meet with this group, contact Brad Hoff, 612-624-2420, hoffx110@umn.edu.

10. Coordinate Campuses
Some of the meetings listed in this document are systemwide. Most are specific to the Twin Cities campus. To find out more about meeting opportunities at each coordinate campus, visit these Web sites:

Crookston: Chancellor’s Office; University Relations

Duluth: Chancellor’s Office; University Relations

Morris: Chancellor’s Office; University Relations

Rochester: Key Contacts

Site Tools

Utilities for searching, navigation, and monitoring site activity

Site Tools include utilities for navigating, searching and keeping up with site activity.

In particular, you have two highly configurable, automated site monitoring tools, WebNotify, to e-mail alerts when topics are edited, and WebStatistics, to generate detailed activity reports.

WebNotify - recent changes alert

Web Changes Notification Service

Each Foswiki web has an automatic e-mail notification service that sends you an e-mail with links to all of the topics modified since the last alert.

Users subscribe to email notifications using their WikiName or an alternative email address, and can specify the webs/topics they wish to track, Whole groups of users can also be subscribed for notification.

The general format of a subscription is:

three spaces * subscriber [ : topics ]

Where subscriber can be a WikiName, an E-mail address, or a group name. If subscriber contains any characters that are not legal in an email address, then it must be enclosed in 'single' or "double" quotes.

topics is an optional space-separated list of topics:

  • ... without a Web. prefix
  • ...that exist in this web.
Users may further customize the specific content they will receive using the following controls:
  • Using wild-card character in topic names - You can use * in a topic name, where it is treated as a wildcard character. A * will match zero or more other characters - so, for example, Fred* will match all topic names starting with Fred, *Fred will match all topic names ending with Fred, and * will match all topic names.
  • Unsubscribing to specific topics - Each topic may optionally be preceded by a '+' or '-' sign. The '+' sign means "subscribe to this topic". The '-' sign means "unsubscribe" or "don't send notifications regarding this particular topic". This allows users to elect to filter out certain topics. Topic filters ('-') take precedence over topic includes ('+') i.e. if you unsubscribe from a topic it will cancel out any subscriptions to that topic.
  • Including child-topics in subscription - Each topic may optionally be followed by an integer in parentheses, indicating the depth of the tree of children below that topic. Changes in all these children will be detected and reported along with changes to the topic itself. Note This uses the Foswiki "Topic parent" feature.
  • Subscribing to entire topic ("news mode") - Each topic may optionally be immediately followed by an exclamation mark ! and/or a question mark ? with no intervening spaces, indicating that the topic (and children if there is a tree depth specifier as well) should be mailed out as complete topics instead of change summaries. ! causes the full topic to be mailed every time even if there have been no changes, and ? will mail the full topic only if there have been changes. One can limit the content of the subscribed topic to send out by inserting %STARTPUBLISH% and %STOPPUBLISH% markers within the topic. Note that the script mailnotify can be run with the options -nochanges or -nonews so that you can run the two mode on different schedules (see details).

Examples: Subscribe Daisy to all changes to topics in this web.

   * daisy.cutter@flowers.com
Subscribe Daisy to all changes to topics that start with Web.
   * daisy.cutter@flowers.com : Web*
Subscribe Daisy to changes to topics starting with Petal, and their immediate children, WeedKillers and children to a depth of 3, and all topics that match start with Pretty and end with Flowers e.g. PrettyPinkFlowers
   * DaisyCutter: Petal* (1) WeedKillers (3) Pretty*Flowers
Subscribe StarTrekFan to changes to all topics that start with Star except those that end in Wars, sInTheirEyes or shipTroopers.
   * StarTrekFan: Star* - *Wars - *sInTheirEyes - *shipTroopers
Subscribe Daisy to the full content of NewsLetter whenever it has changed
   * daisy@flowers.com: NewsLetter?
Subscribe buttercup to NewsLetter and its immediate children, even if it hasn't changed.
   * buttercup@flowers.com: NewsLetter! (1)
Subscribe GardenGroup (which includes Petunia) to all changed topics under AllnewsLetters to a depth of 3. Then unsubscribe Petunia from the ManureNewsLetter, which she would normally get as a member of GardenGroup?:
   * GardenGroup: AllNewsLetters? (3)
   * petunia@flowers.com: - ManureNewsLetter
Subscribe IT:admins (a non-Foswiki group defined by an alternate user mapping) to all changes to Web* topics.
   * 'IT:admins' : Web*

A user may be listed many times in the WebNotify topic. Where a user has several lines in WebNotify that all match the same topic, they will only be notified about changes that topic once (though they will still receive individual mails for news topics).

If a group is listed for notification, the group will be recursively expanded to the e-mail addresses of all members.

__ALERT! Warning: Because an email address is not linked to a user name, there is no way for Foswiki to check access controls for subscribers identified by email addresses. A subscriber identified by an email address alone will only be sent change notifications if the topic they are subscribed to is readable by guest users. You can limit what email addresses can be used in %NOTIFYTOPIC%, or even block use of emails altogther, using the {MailerContrib}{EmailFilterIn} setting in =configure.

TIP Tip: List names in alphabetical order to make it easier to find the names.

Note for System Administrators: Notification is supported by an add-on to the Foswiki kernel called the MailerContrib. See the MailerContrib topic for details of how to set up this service.

Note: If you prefer a news feed, point your reader to WebRss (for RSS 1.0 feeds) or WebAtom? (for ATOM 1.0 feeds). Learn more at WebRssBase and WebAtomBase, respectively.

Related topics: WebChangesAlert, Main.WikiUsers, UserRegistration

WebSearch - search the site

WebSearch is a flexible search facility, part of the core feature set. WebSearchAdvanced offers more options, including:

  • topic title or full-text search
  • regular expressions
  • query search over form data
  • search within web or site-wide
  • index-style A-Z alphabetical listing sorted topic title
  • many more

See also: SearchHelp for help; Macros and FormattedSearch for including hard-coded searches in text.

WebChanges - what's new

To check for the most recently edited topics while on-site, use the WebChanges link, usually located in the toolbar. It lists the most recently modified topics, newest first, along with the first couple of lines of the page content.

This is simply a preset SEARCH. The number of topics listed by the limit parameter.:

%SEARCH{ ".*" web="UMeetings" type="regex" nosearch="on" order="modified"
reverse="on" limit="50" }%

WebRss and WebAtom - news feeds on recent changes

You can point your news reader at WebRss and WebAtom to find out what is new in a web. WebRssBase and WebAtomBase have the details. Like WebChanges, this is based on a %SEARCH{}%.

WebIndex - list of topics

WebIndex lists all web topics in alphabetical order, with the first couple of lines of text. This is simply a preset SEARCH:

%SEARCH{ "\.*" scope="topic" type="regex" nosearch="on" }%

WebStatistics - site statistics

You can generate a listing manually, or on an automated schedule, of visits to individual pages, on a per web basis. Compiled as a running total on a monthly basis. Includes totals for Topic Views, Topic Saves, Attachment Uploads, Most Popular Topics with number of views, and Top Contributors showing total of saves and attachment uploads. Previous months are saved.

Configuring for automatic operation

  • You can automatically generate usage statistics for all webs. To enable this:
    • Make sure configure settings {Log}{view}, {Log}{save} and *{Log}{upload} in are set in configure. This will generate log file entries (see below).
    • The WebStatistics topic must be present in all webs where you want to have statistics. You can use the topic in the Main web as a template.
    • Call the bin/statistics script from a cron job, once a day is recommended. This will update the WebStatistics topics in all webs.
    • Attention: The script must run as the same user as the CGI scripts are running, which is user nobody on many systems. Example crontab entry:
      0 0 * * * (cd /path/to/bin; ./statistics >/dev/null 2>&1)
    • There is a workaround in case you can't run the script as user nobody : Run the utility tools/geturl.pl in your cron job and specify the URL of the bin/statistics script as a parameter. Example:
      0 0 * * * (cd /path/to/tools; ./geturl.pl mydomain.com /urlpath/to/bin/statistics >/dev/null 2>&1)
    • NOTE: geturl.pl will do a CGI request as the WikiGuest user, so if you use this workaround, the WebStatistics topics you are updating will have to be writable by WikiGuest.

When running from the command line or a cron job, you can pass parameters to the script like this:

./statistics -logdate 200605 -webs Userweb,Sandbox

Generating statistics manually by URL

  • The bin/statistics script can also be executed as a CGI script, just enter the URL in your browser. Examples:
    • Update current month for all webs you have access to:
    • Update current month for Main web only:
    • Update Jun 2016 for Main web:
    • Update Jun 2016 for the ProjectX, ProjectY and ProjectZ webs:

Log Files

Foswiki generates monthly log files which are used by the statistics script

  • The log file is defined by the {LogFileName} setting in configure
  • The file name is log<year><month>.txt
  • Example path name: logs/log201606.txt
  • Each access gets logged as:
    | <time> | <wikiusername> | <action> | <web>.<topic> | <extra info> | <IP address> |
  • Example log entry:
    | 25 Jun 2016 - 19:50 | WikiGuest | view | WebRss |  | |
  • Actions are logged if enabled in configure by the {Log}{action} flags
  • Logged actions:
    Script Action name Extra info
    attach attach when viewing attach screen of previous uploaded attachment: filename
    changes changes  
    edit edit when editing non-existing topic: (not exist)
    rdiff rdiff higher and lower revision numbers: 4 3
    register regstart WikiUserName, e-Mail address, LoginName?: user attempts to register
    register register E-mail address: user successfully registers
    register bulkregister WikiUserName of new, e-mail address, admin ID
    manage rename when moving topic: moved to Newweb.NewTopic
    manage move when moving attachment: Attachment filename moved to Newweb.NewTopic
    manage renameweb when renaming a web: oldweb moved to newweb
    save save when replacing existing revision: repRev 3
    when user checks the minor changes box: dontNotify
    when user changes attributes to an exising attachment: filename.ext
    save cmd special admin parameter used when saving
    search search search string
    upload upload filename
    view view when viewing non-existing topic: (not exist)
    when viewing previous topic revision: r3


Configuring outgoing mail

Outgoing mail is required for UserRegistration and for recent changes alert.

Foswiki will use the Net::SMTP module if it is installed on your system. Set this with the SMTPMAILHOST preference setting.

The notify e-mail uses the default changes.tmpl template, or a skin if activated by a preference setting.

mailnotify also relies on two hidden files in each data/Web directory: .changes and .mailnotify. Make sure both are writable by your web server process. .changes contains a list of changes; go ahead and make this empty. .mailnotify contains a timestamp of the last time notification was done.

You can use an external mail program, such as sendmail, if the Net::SMTP module is not installed. Set the program path in {MailProgram} in configure.

! * HELP Net::SMTP can be easily disabled (if there is an installation error) by setting the SMTPMAILHOST preference setting to an empty value.

  • TIP You can set a separate SMTPSENDERHOST preference setting to define the mail sender host (some SMTP installations require this).

Setting the automatic e-mail schedule

For Unix platforms: Edit the cron table so that mailnotify is called in an interval of your choice. Please consult man crontab of how to modify the table that schedules program execution at certain intervals. Example:

% crontab -e
0 1 * * * (cd /path/to/bin; ./mailnotify -q)
The above line will run mailnotify nightly at 01:00. The -q switch suppresses all normal output.

For ISP installations: Many ISPs don't allow hosted accounts direct cron access, as it's often used for things that can heavily load the server. Workaround scripts are available.

On Windows: You can use a scheduled task if you have administrative privileges.

Site Permissions

  • AccessControl describes how to restrict read and write access to topics and webs, by users and groups
  • SitePermissions lists the permissions settings of the webs on this site

Help with crontab

The crontab command is used to schedule commands to be executed periodically.

  • Wikipedia.org:Crontab - crontab documentation
  • pycron - crontab for Windows

Related Topics: AdminDocumentationCategory?, AdminToolsCategory

Topic revision: r12 - 22 Nov 2011 - 09:40:37 - dahl0842
UMWiki UMWiki
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding UMWiki? Send feedback