In attendance: Peter, Elaine, Ranjani, Kris, Kate, Ann, Molly
1.) Discuss ideas around the structure of the portal
Start with talking about use cases.
Organizing by who we assume someone is, not a good idea. Blue Sky: Q1 is it pub or priv, Q2. A branched flow chart, or tree.
Heather Ann has a template that does this branching. Maybe we could use it. It is Drupal module, Ranjani thinks. She will find out about it. It is part of the IS&T site. Uses jQuery. Ranjani has done jQuery in Drupal.
So maybe we'll do both. Do the path for users, but also supply the details.
IS&T site also has "top five answers" which would be good for our purposes.
Ranjani and Ann are going to do a mock-up. Send her some sites that you like to Ranjani. Elaine and Kris could do a wire-frame.
We're thinking about a showcase, examples. But we want it to be supportable.
2.) Identify constraints around the portal
One important caveat, it needs to be up-datable by multiple content up-daters. Drupal benefits: distributed administrated. Drupal con: steep learning curve.
3.) Standards for capture - follow up thoughts
4.) Some next steps
5.) Begin a list of recommended hardwar
6.) Draft a mock-up of our portal
2. Identify constraints around the portal
3. Standards for capture- follow up thoughts
4. Some next steps
a. Begin a list of recommended hardware
b. Draft a mock-up of our portal