[ietf-sow] comments on Agenda tool

"George, Wes" <wesley.george@twcable.com> Wed, 09 November 2011 21:32 UTC

Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf-sow@ietfa.amsl.com
Delivered-To: ietf-sow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09FB81F0C34 for <ietf-sow@ietfa.amsl.com>; Wed, 9 Nov 2011 13:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.969
X-Spam-Level:
X-Spam-Status: No, score=0.969 tagged_above=-999 required=5 tests=[AWL=-1.169, BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqndrytymqJa for <ietf-sow@ietfa.amsl.com>; Wed, 9 Nov 2011 13:32:35 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 64F4C21F86D0 for <ietf-sow@ietf.org>; Wed, 9 Nov 2011 13:32:35 -0800 (PST)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos; i="4.69,484,1315195200"; d="scan'208,217"; a="280215257"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 09 Nov 2011 16:27:51 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Wed, 9 Nov 2011 16:32:30 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: "ietf-sow@ietf.org" <ietf-sow@ietf.org>
Date: Wed, 9 Nov 2011 16:32:29 -0500
Thread-Topic: comments on Agenda tool
Thread-Index: AcyfJxUzi3MrR/x4S16YP+DbHxhA5A==
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791451A6ECD9@PRVPEXVS03.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DCC302FAA9FE5F4BBA4DCAD4656937791451A6ECD9PRVPEXVS03cor_"
MIME-Version: 1.0
Subject: [ietf-sow] comments on Agenda tool
X-BeenThere: ietf-sow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SOW Feedback List <ietf-sow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-sow>, <mailto:ietf-sow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-sow>
List-Post: <mailto:ietf-sow@ietf.org>
List-Help: <mailto:ietf-sow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-sow>, <mailto:ietf-sow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2011 21:32:38 -0000

I have the following comments and recommendations:


*         there should be an alternate way to input things like room information (eg import from csv or XLS file) so that we don't necessarily require the secretariat and others to have to sit and do data entry for all of the rooms. I would expect that often the hotel or conference center already has a lot of this information that they could make available such that swivel-seating may not be necessary.

*         Ability to import building map location data to allow for presentation of a visual representation of the agenda overlaid on the map - would need to specify the acceptable formats for the map, probably VSD, jpg, etc.

*         There should be fields for due dates for room requests, agenda uploads, along with the ability to trigger systematic "nag" emails to WG/BoF chairs who have missed a due date for a schedule request or agenda upload, as well as for those with Level 1 or 2 access to pull reports. - this may drive the need to represent the hierarchy so that the system shows the appropriate AD the WGs/BoFs that they are responsible for.

*         There should be a back-end link (eg the system uses it as a source of data) to the current list of active WGs and BOFs maintained on the IETF webpage, so that placeholder sessions and the drop-down list for schedule conflicts can be generated based on those, or at a minimum those can be used to ensure completeness and assist in notification/validation as in the previous bullet without requiring extensive data entry.

*         Fields to track session actual start/stop time, attendance numbers, and the ability to recall previous meeting info within the scheduling request - this will help WG/BoF chairs to more accurately plan their schedule requests.

*         Integration with Android/iOS - this is a nice to have, but it is preferable that this is designed into the system from day one, rather than relying on someone in the community to write an app  to scrape the published agenda. It may even be useful to design the app such that it can be managed by staff from a tablet or mobile device, whether via a dedicated app or a mobile-optimized version of the agenda.

*         Another nice to have - integration or at least hooks for future integration with an electronic attendance system (such as the electronic blue sheet experiment from Hiroshima). While this may not happen immediately, it would be nice to have the system pull and track attendance data so that no one has to manually enter that data if we ever get away from the paper blue sheets.



Thanks,

Wes George


________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.