Go to:
Discussion
Online Doc
File
Poll
Event
Meeting Request
Suggestion
Jenny Levine (staff)'s picture

Conference Scheduler Requirements Document

4/5 UPDATE: I think I've incorporated all of the new suggestions so far. Thanks for the input!

4/4 UPDATE: Here's what I've put together for the Requirements Document. Please leave additional comments or make changes by Wednesday, April 7, so that we can move forward with this. I'd appreciate feedback about the objectives, risks, and success metrics in particular.

Thanks,
Jenny


  1. Objectives
    1. Create a conference scheduler (CS) that is easy-to-use, fully accessible, and offers a robust feature set to enhance participation attendance.
    2. Facilitate members connecting with each other through sessions and content from the conference.
    3. Provide an archive of the conference program with materials from sessions for future reference and access.
  2. User roles
    1. Public -- Non-authenticated users cannot see the conference scheduler. A PDF of session information will be available online for users who don't want to register on Connect.
    2. Authenticated user -- Non-ALA members can create an account on Connect and user the conference scheduler, but there will be no tie to iMIS.
    3. ALA member/staff -- ALA members and staff can use their regular Connect accounts to access the conference scheduler, regardless of whether they're registered for the conference. The CS will use iMIS affiliations and interests from Connect profiles to match and recommend sessions.
  3. Functional requirements
    1. One-time welcome screen
    2. Conference scheduler dashboard
      1. Search box with link to advanced search; allows for truncated searching
        1. Checkbox to exclude closed meetings
      2. Conference days listed for navigation
      3. Recommendations based on iMIS affiliations and profile interests (ALA members/staff)
      4. Display the next 25 upcoming meetings with a "more" link to current place in the schedule
      5. Link to the "browse" page
      6. Link to "tracks" page
      7. Tag cloud
      8. Link to "my schedule" if previously saved on exists
      9. Conference hashtag and display of current tweets
      10. Link to conference tracker
    3. Advanced search (filter by)
      1. Title
      2. Keyword
        1. Keyword search should include title, description, sponsoring unit(s), and location at minimum
      3. Presenter
      4. Location
      5. Time
      6. Date
      7. Track
      8. Audience
      9. Sponsoring unit
      10. Session type
      11. Exclude, as well as include, options (eg, exclude YALSA but include ACRL)
      12. Include all sponsoring units
      13. Hashtag
      14. User
    4. Search results
      1. For sessions
        1. Title (serves as link to individual session details page)
        2. "Closed" notice for closed committee meetings after title
        3. Time/date
        4. Sponsoring unit
        5. Track
        6. Description and hashtag on hover
        7. Button to add session to my schedule
        8. Option to mark attendance as "tentative"
        9. Option to hide attendance
        10. Sort by day, time, title, sponsoring unit, and location
        11. When viewing lists of sessions, indicate if user has already added it to her schedule
      2. For users with saved schedules
        1. Name (link to Connect profile)
        2. Picture
        3. Link to user's schedule if you have permission to see it/Message that you don't have permission to view this user's schedule
        4. "Send firstname a message"
      3. Sort by
        1. Day
        2. Time
        3. Title
        4. Sponsoring unit
        5. Location
    5. Individual session record
      1. Title
      2. Sponsoring unit(s) (link to other sessions by sponsoring unit)
      3. If sponsoring unit is identified, display unit's logo
      4. Presenters/Conveners (link to other sessions by same people)
        1. Uses Connect profiles for ALA members and staff because they synchronize with iMIS
        2. For non-members, staff can add their Connect profiles by updating the record in the conference scheduler
        3. Allows associated profiles to upload files to session record
        4. Notifies staff liaison listed in database record via email when session information is updated
      5. Day, date, and time
      6. Location information
        1. Map of location
        2. Transportation options
        3. Route number
        4. Link to nearby food options (Yelp, OpenTable, etc.)
      7. "Add to my schedule" button that toggles with icon to indicate it's already on user's schedule
      8. Option for user to display attendance (including a note that "show attendance = public") or tentative/maybe (with "public" option)
      9. Option to set priority for appearing to display of schedule
      10. Audience
      11. Description
      12. Cost (show free if no cost) and registration status (open/full/onsite); include a note for any session that is included as part of general registration
      13. Deadline for purchasing ticket if ticketed event
      14. Open/closed status for committee meetings
      15. Track (link to other sessions in same track)
      16. Session hashtag
      17. Threaded comments (authenticated users only)
      18. Tags (links to other sessions with those tags)
      19. Ability for user to add tags (links to other sessions with those tags)
      20. Space for user to add a personal note that only she can see
      21. Avatars for session attendees
        1. List view of session attendees
        2. Display attendees from your networks first
      22. Share options (Twitter, Facebook, etc.)
        1. Include an option to suggest session to other attendees
      23. Ability to favorite session
      24. "Find more like this session"
      25. Link to notify a Connect group about the session (visible only to iMIS IDs associated with the session)
      26. RSS feed for changes
      27. Automatic email updates for session changes (setting can be changed in the user's Connect profile)
      28. Link back to search results (if applicable)
      29. View tweet and Flickr archive for session's hashtag
      30. Display links for any uploaded materials (file type, file size, uploaded by)
      31. Show trackbacks
      32. Display revision history
    6. Browse sessions
      1. Tabbed navigation to move between days
      2. Browse by:
        1. Date and then time
        2. Location
        3. Presenter
        4. Session type
        5. Sponsoring unit
        6. Subject
        7. Title
        8. Track
      3. Sort by title, day, time, sponsoring unit, and location
      4. Button to "add all" for a specific group (eg, Executive Board, Council)
      5. When viewing lists of sessions, indicate if user has already added it to her schedule
    7. Recommendations (sessions listed with same information as search results)
      1. Based on iMIS affiliations
      2. Based on profile interests
      3. Based on expressed subject interests
      4. Include session tags in matching by subject
      5. By track
      6. By audience
    8. My schedule
      1. Ability to add unlimited number of sessions to my schedule
      2. No limit on the number of sessions that can be added to a time slot
      3. Daily, weekly, and date range views
      4. Let user color code sessions based on priority
      5. Ability to change priority of conflicting sessions
      6. Include day and full date as part of the header
      7. Session block displays title, time, and location with description, sponsoring unit, and hasthag on hover
      8. Ability to edit times of sessions without creating a new event
        1. Toggle to list view
      9. 24-hour display with ability to schedule in 15-minute increments on each
      10. Option to expand or condense blank times to display or not
      11. Icon to delete sessions
      12. Display travel times between sessions
      13. Toggle for privacy permissions
        1. None (default)
        2. Sub-networks (available to members only)
        3. ALA members
        4. Public
      14. List of favorited sessions
      15. Public view of my schedule
        1. Name
        2. Picture
        3. Link to Connect profile
        4. "Send firstname a message" (visible to authenticated users only)
    9. Add a personal/custom session to my schedule
      1. Title
      2. Date
      3. Time
      4. Location
      5. Description
      6. Display to none/sub-networks/ALA members/public
      7. Option to invite other attendees
      8. Share options
    10. Exhibitor listings
      1. Dashboard page
        1. Search box (name, subject, booth number)
        2. Recommendations based on interests listed in Connect profile
        3. Link to browse by subject
        4. Link to online map and PDF version
      2. Search results
        1. Name
        2. Booth number
        3. Subject
        4. Description on hover
        5. Button to add vendor to visit list
        6. Button to add vendor to my schedule
        7. Button to favorite vendor
      3. Browse vendors
        1. Sort by name, subject, booth number
      4. Individual exhibitor listing
        1. Add vendor to visit list
        2. Add vendor to my schedule
        3. Add personal notes to vendor listing
        4. Booth information
        5. Description
        6. Subjects
      5. Create list of exhibitors to visit
      6. Map view of vendors on visit list
      7. Ability to make a visit list public
      8. Map view of all vendors
      9. List of favorited vendors
      10. Future phase: let vendors add tags to their records and make those tags searchable and clickable
    11. My trip details, with blank spaces for users to fill in
      1. Transportation
      2. Hotel
      3. Other
        1. Pre-populate if user with data from Experient if member registered for housing through ALA
      4. Option to share this information with none/sub-networks/ALA members/public
    12. Local information
      1. Link to city maps
      2. Links to local transportation
      3. Food options by location (Yelp, OpenTable, etc.)
      4. Links to contact information for hotels and important contact numbers
      5. Hotel map
      6. Bus routes map
      7. Links to get directions
      8. Links to local libraries and museums
      9. Mashups of all of these things
    13. My networks' schedules
      1. Tabbed navigation to each sub-network
      2. Names listed by sub-network within each page
      3. Gantt chart-like view of when attendees in sub-networks with saved schedules will be at the conference, based on housing data from Experient
        1. Attendee's name (also a link to their Connect profile, if user has permission to view it)
        2. Dates at conference
        3. "Send firstname a message"
        4. Hotel name and address (also a link to its location) if user has permission to view this information
    14. Export schedule
      1. CSV for download
      2. Google Calendar export
      3. HTML5 version for offline access
      4. iCal download
      5. iCal subscription
      6. Outlook download
        1. Ability to set the busy/free/tentative setting and remove reminders before exporting
      7. PDF download
      8. Print option
    15. Get help
      1. Contact ALA
        1. Text-an-Ambassador
        2. Direct Message on Twitter
        3. Phone numbers
        4. Email
      2. Guide to acronyms and abbreviations
      3. Links to contact information for hotels and important contact numbers
      4. Links to get directions
  4. iMIS integration
    1. Authenticate ALA members and staff and recognize their iMIS affiliations
    2. Match member iMIS affiliations against session data to produce a list of recommended sessions to add to schedule
    3. Display an "I'm attending" badge on registered users' Connect profiles
    4. User can toggle the privacy settings on this badge when editing their Connect profile, but default is to display to sub-networks
  5. Third-party integration
    1. Wingate Web
      1. Ability to handle data import of session information from Wingate Web scheduling software (csv)
      2. Need to figure out how to update session records and get the most current information into the conference scheduler so that it can send out updates
    2. Experient
      1. Ability to use API access to hotel registration data to match against authenticated iMIS users in order to display dates when individual members are attending conference
  6. Session types
    1. Affiliate event
    2. Author event
    3. Award presentation
    4. Committee meeting
    5. Discussion/Interest group
    6. Event with free food
    7. Keynote & Auditorium speaker series
    8. Governance/Membership Meeting
    9. Library school/Alumni reunion
    10. New attendee/member session
    11. Opening/Closing session
    12. Poster session
    13. Preconference
    14. Presentation/Session
    15. Presidents program
    16. Reception
    17. Social event
    18. Table talk
    19. Ticketed event
    20. Vendor demonstration/activity
    21. Virtual session
    22. Volunteer opportunity
    23. Webinar
  7. Accessibility
    1. All features and content will be completely accessible to users with disabilities.
  8. Analytics
    1. How many users save schedules
    2. Sessions with most self-identified attendees
    3. Attendees with schedules by sponsoring unit
    4. Most favorited sessions
    5. Most share/recommended sessions
    6. Most commented on sessions
    7. Most-viewed sessions
    8. Most active tracks
    9. Sessions with most tweets
    10. Most downloaded session materials
  9. Materials archive
    1. Each individual session will include any materials or links relevant to it
    2. iMIS IDs associated with the session can upload files, which will trigger an email notice and RSS update to subscribed users
    3. Uploaded files can be designated as viewable by:
      1. Sponsoring unit members only
      2. ALA members only
      3. Public (default)
    4. The conference scheduler will then serve as a permanent archive of content generated from the event
  10. Risks
    1. Many of these features rely on accessing clean data from iMIS.
      1. We'll need to use iMIS group codes when entering data in order to link session information with the group.
      2. We'll need to associate presenters/conveners with their sessions using iMIS IDs for members.
    2. Some of these features rely on third-party integration.
      1. The above risks will require changes to the data entry process in Wingate Web, which will require additional resources and planning.
      2. In order to display dates attending and hotel information, we'll need to access attendee registrations in Experient's database, linked on iMIS ID for members and staff. It's unclear at this time if there is a web service available from Experient to provide this functionality.
    3. Because of the need to integrate data from iMIS and third-party services in order to implement some of the features, some pieces will have to be implemented in phases. This will require additional resources beyond the first release.
    4. In order to maintain current information in the conference scheduler, we'll need to figure out a way for those responsible for the data to update it, whether that's in Wingate Web or Connect. Otherwise, we won't be able to provide email, RSS, and iCal updates.
    5. Search and browse will continue to fail if changes are not implemented at the back-end during data entry.
      1. Unit acronyms need to be included in session titles, and those entering titles need to explicitly note working group meetings versus sessions (eg, "Annual Session Planning Committee" vs "Annual Session").
      2. We need to standardize data entry of session information so that all sessions for a particular group are uniform and can be affiliated with each other through use of iMIS group codes.
      3. We need to require those doing data entry to input a full description or else attendees won't have the information they need to use the conference scheduler effectively.
  11. Success metrics
    1. User satisfaction -- In the 2009 survey of users conducted by the Website Advisory Committee, only 25.5% said the event planner "was pretty easy to use." Since it will take at least one year for data issues to be resolved, the WAC Conference Scheduler Subcommittee will run a second survey when the data has been verified as "clean" and "useful" by the full Website Advisory Committee. The percentage of respondents who will rate the conference scheduler as "pretty easy to use" will triple to 75% for this project to be considered successful.
    2. ADA-compliance -- All functionality and information will be provided or replicated in a way that is completely accessible for users with disabilities. Success will be determined by a positive report from the Accessibility Assembly.
    3. Compatibility -- This metric will be achieved when we have confirmation that the conference scheduler works the same across current browsers and operating systems. As of April 2010, we're defining "current" as Firefox 3.x, Internet Explorer 8.x, and webkit-based mobile browsers.
Rebecca Jackman's picture

Wow!!  What a list of requirements.  It's a little overwhelming to just look at them all.  I don't see anything left off the list, but I'll try and look at it again later tonight.

Aaron Dobbs's picture

Just sent the following to the webadv email list:

Hi all,

I was just poking around Connect (after being poked by Jenny, who keeps me honest *grin*) and see that we need to share some feedback on the Conference Scheduler Document, ASAP.
http://connect.ala.org/node/96539

If you are not a member of the Conference Scheduler group, you can still comment on the list of requirements - you just won’t be able to edit directly.

Jenny needs to get the requirements document together *by Thursday this week* (eeep) and would dearly love our feedback on what is there, what is missing, etc.  The itemized list currently has only the points from the member survey feedback from last summer - any nuts & bolts needs would be good additions.

I'm looking at the doc, but I'm only one guy, could you please make some time to review this and add your thoughts... by Wednesday? :)

Thanks!

(this is going out on the old email list so it will stand out from your "regular" Connect emails :)

-Aaron
:-)'

-Aaron
:-)'

"Always remember everyone is working to make the organization better in their own way."
-Eli Mina, ALA Parliamentarian

Marissa Ball's picture

The outline looks good to me, it's pretty comprehensive. 

One comment, under I. Functional requirements, A. Search/Browse-- would we also want to allow users to tag events with thier own descriptions/keywords? 

 

 

Marissa

 

Marissa Ball, MLIS
Emerging Technologies Librarian
Florida International University, Green Library
ballm@fiu.edu
305.348.8030

Aaron Dobbs's picture

Is the Tagging in II.E.1. sufficient - or should it be measured in more than one subsection?

& thanks!

-Aaron
:-)'

"Always remember everyone is working to make the organization better in their own way."
-Eli Mina, ALA Parliamentarian

Aaron Dobbs's picture

That is brilliant.

Also, how about "estimated travel times"
(once venues are set, a mapping feature to get from one session to the next would be great)
(tho double-bookings would make that pretty complex)

-Aaron
:-)'

"Always remember everyone is working to make the organization better in their own way."
-Eli Mina, ALA Parliamentarian

Louise Gruenberg. MAE. MLS. MIAKM-UXD (staff)'s picture

I also would like to have some way to map routes between locations, and also save maps and have them ready when I need them. It helps to know how far away a prospective meeting or event is from where I am now, how much time I have, and whether it seems doable. Also useful for helping with the "Can I hoof it, chance waiting for the bus, or should I grab a cab?" decisions.

Louise

 

Louise

Louise Gruenberg | Sr. Usability Officer | Information Technology & Telecommunication Services | American Library Association

Margaret Alexander's picture

Looks great!  Super features.

Would it be possible to allow tentative plans to be saved, before even registering, to help people bolster their requests to supervisors to attend, showing all the great sessions they think would be beneficial?

What about any Virtual sessions being included?

Can users "favorite" sessions or events?

 

Jennifer Reiswig's picture

As wired as I am, I usually find myself printing out my schedule before leaving, as a backup and also something I can make a quick note on while chatting in a bus line or some other place that I'm offline.  I'd like to see printing fleshed out a little - maybe with options like a daily agenda and a multi-day schedule view? 

I'd also LOVE it - although I probably wouldn't consider it a requirement - if the mobile version could store your schedule data on the device for those times when you suddenly have no connection, to be synced later when a connection is restored. I suppose if it is easily exportable to (say) Outlook that would work since that stays on the device.  I know we like to think the network is everywhere, but it's always everywhere except the one restaurant/bar/subway that you're in when you need it.

Thanks so much for considering input - if we get something as described above? Woo hoo!

Jason Griffey's picture

Just a note re: Jenny's "offline access" note. If the scheduler can output HTML5, all of the major mobile browsers (Safari, Android, Opera) support HTML5's offline capabilities, which would allow for just exactly that functionality.

Follow me on Twitter! http://twitter.com/griffey

Jenny Maurer's picture

As I have been to several recent conferences, I felt I should look at this. I went back to my notes and everything that I had noted in pen on my conference scheduler is included except Flight plans.

I copy/paste into my document my incoming/outgoing flight information so I have one document to keep track of.

I understand this is probably not possible but I can still do it my way.

Your information above is outstanding.

Jenny Mae Maurer
Library Technology Services Manager
Pennsylvania College of Technology
One College Avenue DIF 69
Williamsport, PA 17701

Michael Golrick's picture

Allow for choice of adding all of a meeting or just part, plus the option of adding all meetings of a group. Here is what I mean.

When I was on the Exec Board, I had liaison assignments, so I needed to know where and when committees and division boards met, and put them on my schedule, but usually was only there for a part of them.

For the second, there are those on Council, the Exec Board, and other Boards or committees which have meetings in multiple parts, and it would be cool if they coul *all* be added with just one click.

You also need to be sure that *if* there is a limit to the number of events, it is high enough....like at least triple digits. I claim that I am the reason why there is a message on the current planner about the maximum number of events after I crashed it for four meetings in a row when I tried to have 60 or so events. If you are letting people add their own events, then the need for the higher limit is even more important!

A "conflict" is not always a conflict. You may need to be at two meetings at the same time, or may want to have choices. Not having limits on those is important as is the display.

Display options are important. Some like to have the whole conference on one page (which Outlook is very bad at since we meet over a weekend). I like to have mine one day at a time. And having the opportunity to color code is great. Also some folks prefer a list, and others a more graphical view.

I am not sure you should "hide" or "pre-populate" closed meetings. First of all, I might need to find someone (say on Caldecott) and therefore need to know where or when it meets. Also, if I am not attending, do you want my name showing up on lists of potential attendees. Let members choose to use this or not.

Thanks for your work on this!

Peter Murray's picture

In terms of "K: Export Functions", I'd also like to see a way to set up an iCal subscription.  Better than an iCal file (an import-and-your-done method), an iCal subscription would allow modifications to appear in the calendar application as well.  (I mean, if we're shootin' for the moon, that is a feature I'd like to see...)

Nothing selected

Aaron Dobbs's picture

By the numbers:

III.B.4. Display the next 25 upcoming meetings...
     [Why "25" ? -- option could be configurable - and possibly browser dependent? Maybe mobile browser default ~10?]

III.C. Advanced search (filter by)
     [On the data entry side of things, for at least III. C. 7, 9, 10, & 12, there *must* be a way to eliminate the free-text option for assigning these data.  If a Unit does not exist in a drop-down field for the data entry portion, then either the Unit would need added by a CS admin or the data-entery person needs to select a correct Unit. Otherwise the filtering will not be effective.]

III.E.12-32
     [These are great, but maybe should be "desired" as opposed to "reqiured"?]

III.H.13.b Sub-networks (available to members only)
     [*confused* what does this mean?]

III.J Exhibitor Listings
     [It would be great to be able to setup an exhibit hall map with a tentaitve/planned route, possibly with notes on planned discussion points, and made public so attendees could plan a group visit, based on similar interests (and which vendors could use in booth staffing planning) - yes, totally pie-in-the-sky]

III.J.1.a Search box (name, subject, booth number)
     [If vendors would tag their products and product aresa (say in a vendor profile in Connect?) then I'd want these searchable, too]

III.J.2.g & III.J.5 Favorite a vendor
     [Seems like similar functionality - is J.2.g just specifying presence of the button? If so, is this redundant?]

III.K.3.a Pre-populate if user with data from Experient if member registered for housing through ALA
     [This is an excellent value-add for the ALA/Experient experince -- now if they would just stop sending out "hotel block full" alerts on day one of the housing requests, haha]

III.L. Local information
     [Mashups with Conference Venues, Public Transportation, Walking distance/details, etc. would be a good add here]

III.M. My networks' schedules
     [It would be a great thing to be able to get a (subscribable) list of people debating on attending a given session - both for potential attendees as well as for presenters... think of the possibilities from the presenter point of view: "what is the possible  experience level of the audience going to be"]

Last thought, will all of this be integrated, somehow, into Connect or another ALA branded webspace?
(especially section IX. Materials Archive)

This should not end up in a proprietary archive which might disappear or cost ALA any sort of subscription monies later.

Thanks!

-Aaron
:-)'

"Always remember everyone is working to make the organization better in their own way."
-Eli Mina, ALA Parliamentarian

Jenny Levine (staff)'s picture

> III.B.4. Display the next 25 upcoming meetings...
>     [Why "25" ? -- option could be configurable - and possibly browser dependent? Maybe mobile browser default ~10?]

I picked 25 as a somewhat arbitrary number, but it will be difficult to show everything that's coming up when there are sometimes 200+ simultaneous sessions. Sigh. We can make it smaller if you'd like, but I think we're going to have to define the mobile interface separately. That's something we'll likely have to flesh out and add to this document, because we can't include *all* of the features listed in this document in a version designed specifically for cellphones. I just don't think that's feasible.

> III.C. Advanced search (filter by)
>      [On the data entry side of things, for at least III. C. 7, 9, 10, & 12, there *must* be a way to eliminate the free-text
>      option for assigning these data.

I tried to stress this in the "risks" section, but ultimately this change has to be made in the Wingate Web software. Karen Muller, director of ALA's Library, is working on data cleanup and making recommendations for how to fix the data entry side of things. I'm pretty sure she will push for this, too, and I was trying to back up that position by noting that the only way to fix this is to change the input form, regardless of which event planner we use.

> III.E.12-32
>     [These are great, but maybe should be "desired" as opposed to "reqiured"?]

I think some of them should be required but at this point, they're not all feasible for the reasons stated in the "risks" section. I left them listed the way they were because I think they shoudl all be doable in a future phase. LMK if you disagree with that.

> III.H.13.b Sub-networks (available to members only)
>     [*confused* what does this mean?]

Your Connect sub-networks are your friends, contact, co-workers, etc. Non-members don't have networks on Connect, so that feature would be available to members only.

> III.J Exhibitor Listings
>     [It would be great to be able to setup an exhibit hall map with a tentaitve/planned route, possibly with notes
> on planned discussion points, and made public so attendees could plan a group visit, based on similar interests
> (and which vendors could use in booth staffing planning) - yes, totally pie-in-the-sky]

I like pie-in-the-sky, so I added this one. :)

> III.J.1.a Search box (name, subject, booth number)
>     [If vendors would tag their products and product aresa (say in a vendor profile in Connect?) then I'd want
>     these searchable, too]

The tags would have to be added by vendors on the Wingate Web side of things, so they'd get imported into Connect with the listings. I added this to the list, in case we can implement it in WW.

> III.J.2.g & III.J.5 Favorite a vendor
>     [Seems like similar functionality - is J.2.g just specifying presence of the button? If so, is this redundant?]

Good catch - I removed the second one.

> III.K.3.a Pre-populate if user with data from Experient if member registered for housing through ALA
>     [This is an excellent value-add for the ALA/Experient experince -- now if they would just stop sending out
> "hotel block full" alerts on day one of the housing requests, haha]

Sorry - can't do anything about this one. :-p

> III.L. Local information
>     [Mashups with Conference Venues, Public Transportation, Walking distance/details, etc. would be a good add here]

I added this one, even though we didn't really define what it means. We should be able to link to pretty much anything.

> III.M. My networks' schedules
>     [It would be a great thing to be able to get a (subscribable) list of people debating on attending a given
>     session - both for potential attendees as well as for presenters... think of the possibilities from the presenter
>     point of view: "what is the possible  experience level of the audience going to be"]

Subscribable how? I don't know that a trickling RSS feed of new tentatives would do much. The list would be available on the session record for those willing to mark they're tentative attendance as public. Does that suffice?

> Last thought, will all of this be integrated, somehow, into Connect or another ALA branded webspace?
>    (especially section IX. Materials Archive)

Yes, that's the intent. That's why the document notes use of interests listed in Connect profiles, adding badges to Connect profiles, etc. If Connect ever changed platform, it would migrate with the platform, but we'd certainly have all of the content.

Did I miss answering anything?

Jenny

Aaron Dobbs's picture

> > III.M. My networks' schedules
> >     [It would be a great thing to be able to get a (subscribable) list of people debating on attending a given
> >     session - both for potential attendees as well as for presenters... think of the possibilities from the presenter
> >     point of view: "what is the possible  experience level of the audience going to be"]

> Subscribable how? I don't know that a trickling RSS feed of new tentatives would do much.

> The list would be available on the session record for those willing to mark they're tentative attendance as public. Does that suffice?

I was thinking like an iCal subscription, as attendees update possible attendance the change would get pushed to the profile - maybe that is too social-media forward-think? :)

-Aaron
:-)'

"Always remember everyone is working to make the organization better in their own way."
-Eli Mina, ALA Parliamentarian

Michael Golrick's picture

Here are two additions/comments:

 

VI. Session types: add "Governance (Boards, Council, etc.)"

 

IX. Archive: Will the prior meeting (or two) be saved and be able to be viewed later. If so, a way to link from a "last time" event with the equivalent "this time" event would be huge. If I go an look at my last several calendars, there are things which *always* show up. For me it is Council (all three full meetings, the Info Session, the APA Council, etc.), some committees and boards, and even some "standing" social events like the ASCLA/COSLA reception.

If you can't do the links, that is OK...having access, for at least a while is useful in writing reports of activities at Midwinter/Annual....

I will respond to you privately about your other questions.

Jenny Levine (staff)'s picture

Thanks, Michael. Coming from you, that means a lot! :)

>VI. Session types: add "Governance (Boards, Council, etc.)"

I added it and combined with the Membership Meetings - is that okay?

>IX. Archive: Will the prior meeting (or two) be saved and be able to be viewed later. If so, a way to link
> from a "last time" event with the equivalent "this time" event would be huge.

We'll have to figure out the best way to handle this, but hopefully there will be an easily guessable URL. Something like connect.ala.org/annual/2010. The old conference scheduler just becomes the archive, and you can get to any past one. That's the intent.

In the long run, we also then have a record of a member giving a presentation or otherwise participating in a conference, so that would add to their points to let them "level up" to become a "master ALA member." :)

Hopefully your iMIS affiliations would already put the Council, board meetings, and standing social events in your "recommendations" to easily add them to your schedule, but that's a good point that maybe you could import last year's sessions that are associated with iMIS codes. Kind of like you can import your 2008 tax return information into your 2009 one. We'd just have to figure it out logistically, based on your current iMIS affiliations (eg, maybe your committee appointment ended this year).

Jenny

David Schuster's picture

I stumbled on this discussion and thought I would ask - after using the boopsie app now for at least 2 conferences has it held up?

Personally I say no the scheduler and boopsie don't match.

I'm going to promote the TxLA mobile app again as I find it superior to boopsie at this time.  Take a look...  I guess from my discussions with TxLA this week it is a bit expensive, but man it is a FABULOUS conference tool.

The interloper from ALA Midwinter - Dallas.

David

David Schuster

Director of Library Information Technology 

Texas Woman's University

Denton TX

Tall Texan class of 2010

dschust1@gmail.com

Aaron Dobbs's picture

Hi David, Jenny can answer better (and correct my errors) when she gets back from vacation...

Here is my understanding:

  • There are efforts underway (& possibly code in the works) to build a mobile [app/version] of the Conference Scheduler
  • Going forward the datastore underneath the Connect-based Conference Scheduler (built on Drupal) will be the same datastore used for the app/version mentioned above

I may have conflated several items in arriving at my understanding, but it makes sense (to me) to have one datastore serve out the same data to all access points (apps, pages, etc.)

Does that help any? Feel free to email from my profile if you have specific questions (which I will possibly defer back to ITTS for accuracy)

-Aaron
:-)'

"Always remember everyone is working to make the organization better in their own way."
-Eli Mina, ALA Parliamentarian

Mary Ghikas's picture

I believe Aaron is correct -- but need Jenny for details.  Just so you know, Jenny is *unplugged* this week -- for a very well-deserved holiday.  I'm sure she'll catch up with this thread when she returns -- but not until after 2/21.

And, "interlopers" are welcome -- and encouraged.  That's what this is all about,  yes?

Have a good weekend, all.

 

Jenny Levine (staff)'s picture

Hi, David --

Aaron and Mary are correct that we're going to build our own app for the Scheduler starting with the 2012 Annual Conference. In fact, we want to build something that's platform independent and works well on tablets, too.

To answer your specific question, though, I haven't seen any usage data about the Boopsie app, but I know a lot of people were unhappy that they couldn't access their Connnect Conference Scheduler info in it, which defeated the point for them.

The problem with just going with the company that created the TxLA app is that we'd run into the same problem because they wouldn't authenticate against ALA's servers and personalize the app to the user's already-created Scheduler.

Our intent is to build the Frankenstein of conference apps to make the best possible one. Well, that didn't sound quite right, but I have several apps I want to look at (with the TxLA one at the top of the list thanks to your recommendation), take the best of each one, and then build an uber-app for ALA conferences. This will require a big initial cost, and we might have to take a phased approach, but just being able to log in without creating a separate username/password to see your full schedule should be a big leap forward.

So this is probably a good time to poll the current members of the WAC Conference Scheduler Subcommittee to see if they still want to be involved in the project. I know three of you are no longer on WAC, so I'd understand if you don't want to continue here (although I'm thrilled if you want to stay, too). I was going to post a call for redesign beta testers in the regular WAC group, so I could also call for volunteers for the subcommittee, as well.

David, you're a yes, right? ;)

Just to give a sense of timeline, we'll continue work on the redesign next month (March) and begin getting the Annual Scheduler ready to launch in April. We'll probably still have to spend some time in April on the redesign, but then we'll also start working on the Scheduler app. My hope is to launch it in late May.

So everyone, please chime in about whether you'd like to continue working on this project, and I'll adjust the roster accordingly.

Thanks!
Jenny

Aaron Dobbs's picture

Hi Jenny, I'm in (of course) ;)

-Aaron
:-)'

"Always remember everyone is working to make the organization better in their own way."
-Eli Mina, ALA Parliamentarian