| TSWeb Technical Team Minutes, Sept. 7, 2005 Subgroup in attendance: Sally Lockwood, Nate Rupp, Nancy Solla We continued walking our way through and inventorying the content of the TS Web site. Post Cataloging Authorities Local Resources
External Resources
Bulk Import/Export General
Project Specifications
We wondered what exactly is in the Voyager Manual and why is it called that if it has so much other stuff in it? Why was a Voyager Manual created separately from CTS procedures? Could the other stuff be taken out and combined with the procedures? Catalog Management Special Update Procedures
Other Processing
Database Management Services – Links to CTS site, but should be part of TS Web; it should be a site within TS Web that is self contained and includes much of the information we’ve mentioned here that should be pulled from the Voyager Manual Retrospective Conversion – Links to CTS site, but should be part of TS Web; it should be a site within TS Web that is self contained, or part of Database Management Services CTS Site 1. Voyager Manual – links to Voyager Manual which doesn’t have any links off the front page to all the bulk import information we identified as being in the Voyager Manual. Is the bulk import info in the Voyager Manual just because there is no other place for it? 2. CUL Technical Services – Links to larger TS site; content will remain. 3. Macro Express – Links to CTS procedures. 4. Network Administration – Links to Network CTS site, but should be part of TS Web; it should be a site within TS Web that is self contained. 5. Recon in Progress – Links to CTS site, but should be part of TS Web; it should be a site within TS Web that is self contained, or part of Database Management Services. 6. CTS Future Search – Links to CTS site, but all this material is from three to four years old; it’s a project that may need to be archived. 7. Department Information – Links to a list of people with language skills; this should be moved to something like an "About Us" section. 8. Metadata Services – Links to Metadata Services; should the metadata services site be a site within TS Web, or should it lie outside both TS Web and DCAPS since it is a part of both, but not fully part of either? 9. Post Cataloging Services – Links to CTS site, but should be part of TS Web; it should be a site within TS Web that is self contained and includes much of the information we’ve mentioned in our review of TS Web that should be pulled from the Voyager Manual. 10. Working Documents – A number of different documents that could be archived or deleted. 11. Archived Resources – A half dozen reports / projects that should continue to be archived. This could be the start of a larger archive that could include materials from the CTS "Working Documents" section and CTS Future Search. Archived materials should be marked as such. Repetitive Motion Injury information in both Working Documents and Archived Resources. 12. CTS Procedures – Procedures; Jim’s group is working on combining these with Voyager procedures. Is there a better way to identify procedures instead of with sequential numbers? 13. LC Online Catalog – Links to LC online catalog; could be one item in a "Tools" section. 14. Music Cataloger – Procedures for cataloging music; could be moved to procedures manual. 15. Procedures by Number – Another way of accessing procedures. 16. MARC Record Sets – Could fall under a LTS "Products" page. 17. Vision statement: CTS has a vision statement on its home page. Nate emailed Karen after the meeting to ask if the new LTS organization would be rewriting a mission/vision statement. The new LTS site will need to have a section for this kind of statement. For next week, we’re going to take a look at other technical services web sites to get a sense of what other library technical services organizations are including. In addition, Nate will look over the survey that was sent out to people two years ago in preparation for the current TS Web site to get a sense of what people were looking for in a web site. This will help us determine what different audiences (external / internal) are looking for in a CUL LTS web site. Also for next week, we’ll be thinking about different ways to organize the site. We could organize it structurally, along the lines of the four groups (Acquisitions and Information Organization, Metadata Services, Database Management, and E-Resources and Serials Management) that make up the new LTS. Or we could organize it functionally, so people can go to the site and easily find the tools and resources they need to do their jobs. How can we design a site that meets both these criteria? |