| TSWeb Technical Team Minutes, Jan. 11, 2006 Attending: Michal Jacyna, Sally Lockwood, Nathan Rupp, Nancy Solla 1. Navigation We have two options for a navigational scheme for the site – the neat and cool scheme like the one engineering uses (http://www.engineering.cornell.edu/) – or the one built into CommonSpot. We need to determine by Friday, February 10, which we will go with. Action: Nate will contact someone in engineering to learn if they will share their code with us. [I emailed Paul Davis in engineering; he’s going to put us in touch with the best person to answer our questions.] Action: Michal will meet with Jim Reidy before our next meeting about how to do this on our site. 2. Web site sections We should all continue thinking about "our" sections of the site, how they should be structured, and what content they should include so we are ready to move the content into the second level templates when they are ready. Functions: Who We Are – Nate Projects and Initatives – Michal Resources and Tools – Sally Services – Sally Training – Training group Procedures – Jim Alberts’ group Divisions : Database Management – Michal Metadata Services – Nancy Electronic Resources and Serials Management – Nate Acquisitions and Information Organization – Nate The LTS training group will consider the Training section of the web site, and Jim Alberts’ procedures group will work on the Procedures section. Nancy will work with the Metadata Services group to develop their section. That leaves the rest for us to work on. Michal is working on a page for Database Management, and I will talk to Bill and Scott about pages for their divisions. I’m ok with the Who We Are section and Michal has a handle on Projects and Initiatives. That leaves Resources and Tools/Services. Action: Take a look at the notes Sally has put together from our initial (September) discussions about the web site content and we will talk about the Resources and Tools/Services sections at our next meeting on January 25. Action: Continue to gather content for your sites and we will talk about them at our meeting on February 15. 3. Demo-ing the site We need to begin thinking about how we will demo the site to LTS staff; we held a catered lunch to demo the current vision, and may wish to do the same thing this time around. We also could include a link prominently displayed on the site that would enable staff to provide us with feedback during the first couple weeks that the site is up. Action: Nate will talk to Karen about scheduling a lunch demo; perhaps it can be one of the agenda items for her next all LTS staff meeting. [I’ve set up spring TS Web meetings with Karen and Jim Alberts; we’ll bring this and other issues up with her then.] 4. Maintenance after the site is finished We need to think about how the site will be maintained once it is completed. The model that has been used in the past has been the TS Web maintenance team. All along we have thought that this model could be eliminated when all staff is encouraged to use CommonSpot (CS) to update their section of the site. CS is not that simple to use and we may want to follow Mann’s model of identifying "owners" of the sections of the site as staff to whom everyone else concerned with a particular section can send updates. These "owners" will be trained in CS, not everyone in LTS. Action: Nate will run this new maintenance model by Karen to get her impressions of the site. 5. Training We discussed the CS training session held Tuesday, January 10, and what further training was needed. If a number of "owners" of site sections need to be trained, we will probably be responsible for that training. But we need to be trained first, and we do not feel adequately trained, even with Tuesday’s session. Since Nate is on the CUL CS Steering Group, he will work with them to develop another training model. It may be that CUL needs to develop its own CS training sessions. Action: Nate will continue to interface with the Steering Group about these training issues. Action: We will each review the training document distributed at the Tuesday session and look at the training documents posted at http://www.commonspot.cornell.edu/. Action: Nate will talk to Jim Reidy about the sandbox he is setting up so we have a place to play around with CS. [Email sent and waiting on a response from Jim.] 6. Next meeting Our next meeting will be Wednesday, January 25, from 9-10:30 AM. |