Right now students are offered a spot and they have 5 days to complete offer and then they are put into cancelled mode. Students also can be trying to complete their offer online and for courses where you have to pick field trips they often navigate away from the screen to check calendars and when they come back the 30 minutes is up and they have been kicked into cancelled mode. Both of these cancellations usually result in the student reaching out to the course leader and the course leader is unable to offer them a spot so instead member services has to get involved. Its just an annoying two step process instead of a one step process that empowers leaders to handle their rosters.

Participant Note Types:

Enhance participant notes capability so that users with the ability to add participant notes may select from a range of pre-determined “note types” (still to be determined, but could include “positive comment, future leader potential, conditioning issue, behavior issue, other comment”) when entering participant notes in addition to entering free text notes. Note types as well as free text become a part of a member’s profile.

Filtering Note Types:

Users with the ability to research participant notes are able to filter participant notes by the pre-determined note types. This allows activity leaders and committee leaders to quickly review participant notes for specific types of notes.

Anonymous Participant Notes:

Prevent users from viewing participant notes about them entered by other users. Note that this includes leaders and admins (the group who can review these notes) being prevent from viewing notes that other leaders add to activities about them,

Currently even if a listing or document is marked private by the creator it can still be viewed by ANYONE who is listed as a leader for any committee on the mountaineers website., except for member profiles. On occasion we create and want to archive documents and trip listings that the creator does not currently, or ever, want those hundreds of Mountaineers leaders to be able to see (trip postings that aren't ready for prime time, participant information for a Global Adventure that may include passport details, etc.) I'm guessing that few people who click 'private' on the status bar mean 'private EXCEPT FOR all those hundreds of trip leaders'. I would like to have a category that is TRULY private, viewable only by the creator and those the creator wants to share it with (and the website staff ok).

As a member of the activity leaders group allow me to clone an activity so that I can more easily create the series of activities I need.

Fields that can be different in clones:
- Start Date
- End Date
- Registration Opens: Default to 9 am on Start date + 1 day
- Registration Closes: Default is noon on the Thursday preceding the Start date
- Leader
- Member and Non-member Prices (NOT cancellation fee) if either of those fees is >0 on the activity being cloned.

Notes:
- This is similar to what we do for lodge stays
- Add an "Allow activity cloning?" checkbox field to Route/Place so we can control what activities may be cloned (probably the Program Centers and Lodges, but it could be a few others). This determines whether the "Clone" action is visible.

Uses cases:

- Meany Lodge's "Day Use" activities

- Meany Lodge's "Snowshoe Trek + Lunch" activities

- Course lectures and field trips at program centers

----- Original Request -----
As an admin, I need to create a complex set of lodge stay events for each weekend of the winter season. Doing this via the UI is error prone, time consuming, and painful. Provide a way that I can write a script in powershell, python, php, etc that will create the appropriate entities in the backend database. I'm willing to generate entities in xml, json, or the flavor of your choice.

If you can't give me the ability to write a script to do, then consider providing a script that does the work needed.

The script I want will do the following
- Accept a list of dates for Fridays on which the lodge will open
- Create a Saturday Lodge Stay event
- Create a Friday Night Lodge Stay event
- in the body of the Saturday event, include text and a link pointing to the Friday event
- in the Friday night event, link it as a bundle to the Saturday Lodge stay
- in the Saturday event include links to the appropriate course events that are running that weekend (either an A series or B series ski lesson course, and a drop-in course roster)
- set the reservation date cutoff for both Friday and Saturday Events to be 1pm the Thursday before

the current Lodge stay event templates that are available cannot handle this kind of specific linking of events to other events. rather than trying to improve that feature, I'd rather have access to this kind of scripting ability.