|
Managing the Content of Your Collection: Content Development, Cataloging, and ArchivingJanet Kahkonen Smith, ENC / The Ohio State University Karen Cariani, WGBH Elizabeth R. Blackmer, Washington and Lee University Edward Almasy, University of Wisconsin Paul Berkman, The New Media Studio / EvREsearch LTD Stephen Miller, Scripps Institution of Oceanography Presentations Recorder: Judy Ridgway, ENC/The Ohio State University Collection builders will talk about the decisions that they made as they built their collections and the reasons behind the choices that were made. Examples to be shared include collection development policies, content management systems, indexing guidelines, archiving policies, and much more. Notes - Managing the Content of Your Collection: Content Development, Cataloging, and ArchivingManaging the Content of Your Collection 10/14/2003 Content management systems, metadata, and archiving Moderator Janet Kahkonen Smith Karen Cariani WGBH Overview of WGBH Wanted to narrow the audience to K-12 teacher - Talked to audience (teachers of various grade bands, discipline, and geographical influence such as urban and rural) What were their needs. What are the subjects that would be best supported by digital resources. How would they organize the materials? Their decisions came through the audience and the advisory group. Used the topics to search the archives. All of the materials that are gathered for the production of the videos as well as the videos and ancillary materials themselves. Wanted to be deep not broad. The report has been published. Demonstrated the Teachers Domain - Showed the formats of resources. A straight lift from a video wouldnt work because the grade band might not be appropriate. They spliced parts together and re-narrate to make it appropriate for the grade band. The video clips should be around 5 minutes or less. Putting the resources into context. They are cross-referenced and have associated lesson plans. The lesson plans are meant to be a suggestion to the teacher. The resources are linked to the national and state standards. The standards are hand assigned an indexer looks at the terms in the standards and uses the terms to assign. Project management system is Filemaker. Production people, education, and tech developers are working on the project. They find that Filemaker is easy to use. The data from Filemaker are put into a database that is split into two systems (media ID and the Media Application ID) that feed the website. Cataloging- As they are moving along they are hoping that this cataloging feeds back into the WGBH cataloging. Rights issues are complex. They have the rights to the program, the individual still shots, the narrator everyone has rights. Part of the selection is based on the rights because they want the resources to be up for a while. Price also plays a part of the decision about selection. Accessibility - All of the resources are cataloged for the hearing impaired. Archiving - They are archiving by burning CDs with all of the data and project tracking, and decision paths. On the to do list to get the documentation for the developers. Make sure that staff can work well together and talk to one another. John Saylor emphasized the fact that you dont have to be middle school for active participation in the NSDL. They will do an assessment of teachers needs with for the physical science portion of their collection. Elizabeth R. Blackmer Alsos - Please refer to the PowerPoint presentation on the Swiki (19). Questions after the presentation: Is it a problem that resources are on your site one day and gone another? That might happen. It was suggested that they use Tombstone or something like that. Edward Almasy University of Wisconsin. CWIS Please refer to the PowerPoint presentation on the Swiki (19). Questions after the presentation: If you fill out the fields will I be done? Tell the OAI people where your collection is and it is a turnkey process. Do you need to fill out all of the 54 fields? No. There are more in there than what CI requires. How modular is CWIS? It is self contained. Most of the components are PHP compents. It is not designed to pieces or parts, but you could use it that way. Are there limitations if the collection has heterogeneous resources? The issue is that it was designed to maintain one metadata schema. Some collections have a schema that encompasses heterogeneous resources, but if your resources diverge too far and in too many directions that can be difficult. Paul Berkman Marine Mammal Commission Digital Library of International Environmental and Ecosystem Policy Documents - Please refer to the PowerPoint presentation on the Swiki (19). Questions after the presentation: Regarding granularity. There has to be diminishing returns some place. The granularity is user defined. Each figure could be treated as an individual object. Your collections are not in the NSDL repository right now? Yes, that is right. Building a strategy that is compliant with NSDL and not redundant. At the minimum, your collection should be reflected. You could have a document and break it down. Stephen Miller Scripps Institution of Oceanography - Please refer to the PowerPoint presentation on the Swiki (19). Questions after the presentation: Your collections are not in the NSDL repository right now? Yes, that is right. OAI compliant, but the question is what records are important for the NSDL. We want to get them to our site. We want to get them intrigued but not buried. What happens when they request the data? What did you mean by mediating the proprietary nature of the data being downloaded. Oceanic data are fought over and we mediate that process. We are in the midst of a system to mediate the requests. Andrew Chase-Out at sea on assignment! CommentsPlease enter any comments in the following format.
|
