|
|
Content Standing Committee
Mission: This committee recommends and implements policies to ensure that NSDL content is high quality, is appropriate and consistent, has technical integrity, and is accessible for use by global audiences of learners at all levels.
Committee Website: http://content.comm.nsdl.org
Content Standing Committee Meeting
NSDL Annual Meeting 2003
Wednesday, October 15, 2003
2:30-5pm
South American B
CSC DraftAgenda 100903.doc
Agenda Items
A. Meeting the needs of projects:
- What do projects (new and established) need from the CSC? How do we find out?
- How do we communicate what we are doing?
- How do we solicit input from projects on an ongoing basis so our work is reflecting their changing needs?
- How can we help projects promote and assist in the development of the collection of the NSDL?
- How can we help projects promote and assist in defining the scope of the NSDL?
- How can we help projects promote and assist in helping all STEM collections (whether NSF-NSDL funded or not) to contribute their metadata to the NSDL central repository?
- What will be the overall areas of focus for the CSC based on the above questions?
B. Review the Draft NSDL Collection Development Policy (document can be found at http://content.comm.nsdl.org/docs/) a subcommittee needs to be formed; they will bring their findings back to the Content Standing Committee so that we can recommend it to the Policy Committee using the guidelines in PC-1 Policy on Developing and Approving NSDL Policies (http://policy.comm.nsdl.org/docs/).
C. Review of the new NSDL middle-school focus in general, and discuss its implications for upcoming CSC tasks and coordination with other SCs and the CI. Provide recommendations to the Middle School Portal developers on the following points:
- Identify requirements, test and adopt NSDL-wide methods of linking resources with state and national standards, including automated methods.
- Identify requirements for the annotation framework especially with regards to the types of information to be managed.
- Identify "approved" tools for collection builders to use, such as Internet Scout's CWIS, or tools to rate the grade level of text.
- Help with collection development, including identifying potential editorial groups (professional societies, agencies, etc) with whom we can partner to recommend new (non-NSDL funded) collections.
D. How does the CSC support the work of the NVC, CI, and PC? See attached document for recommendations from NVC - NVC Pres Julu03.doc.
E. Plans for the election of CSC officers.
Associated Sessions:
15 - Evaluating the Content of Your Collection
16 - Implementation of Metadata Standards
17 - Innovative Metadata Development and Implementation
18 - Introduction to Metadata
19 - Managing the Content of Your Collection
Notes - Content Standing Committee
CSC Meeting Notes Uncut Version
October 15, 2003
Interests of attendees:
Annotations
Linking from discovery system into collections
Correlation to standards (esp. K-12 engineering, TeachEngineering already has 4 states with standards)
Evaluate quality of metadata records in NSDL Union Catalog
With technology committee, Content Standing Committee can add questions, review survey to see whats related to collections. Including annotations, state/national content standards - Volunteers with special interest in this committee: Karon Kelly, John Saylor, Howard Burrows.
Will add all participants of CSC meeting to the Content Standing Committee mailing list. - Action Kim Lightle will add the email addresses.
Will send additional call for participation to the CSC meeting. Make sure that everyone knows that they can participateespecially following the email lists. Consider this an special interest group or working group. - Action Kim Lightle to send out this call.
Standards:
K-12 content/state standards
Technical standards
Vocabulary
Does the CSC:
Include metadata?
Know the profile of age-/grade-levels of content covered within collection (see p.13 of 2003 NSDL Annual Report for results of work by EIESC: currently looking at collections records (audience and discipline (80 terms), have 95% of 300-someodd collections in NSDL) and item level metadata to gain this kind of profile of the collections)
Overall, can the NSDL Community:
Identify the key issues and then relate them to individuals in the project
Tag the sessions that people attended to gain a notion of what issues they might be interested in
Have mentors for new projects (based on similarity of projects)
Document contents of posters that the projects created at the Annual Meeting: include the poster files themselves (could be stored in a DSPACE-like institutional repository) along with context form (see Cathy Manduca and her experiences with GSA conference), along with metadata
At a broader-level, develop an institutional repository for all kinds of content about the projects that projects might create (toolsex. Cataloging tools, publications and presentations, etc.) - Susan Jesuroga and John Saylor will look into this issue.
Sites of Interest on NSDL main portal - John Saylor suggests a Task Force to work on the process: suggested members include Holly Devaul at DLESE Program Center, Faith Ann Myers at ENC, and Carol Terizzi at Cornell/CI; John Saylor will put out call to other collections and/or all projects as a whole.
Develop a process to select the Sites of Interest from the NSDL development community
Collect existing feeds of similar things from DLESE, ENC, etc.
Possibly special area with focus outside the circle of developers, teachers and educators
Document describing life-cycle of collection-building
Review existing draft Collection Development Policy - John Saylor asks for a Task Force to review the policy, hopes to be formed by the end of October 2003.
Develop outline for best practices document; will resurrects results of the best practices document from 2002-2003 CSC - Kim Lightle will send out to email list.
Comments
Please enter any comments in the following format.
- (commenters' initials) - month/day [comment date]
- comment
|
|