Blueprint Subject Areas

The OnCoRe Blueprint will endeavor to provide users with a comprehensive guide to all areas that warrant consideration when establishing an Online Content Repository. Below is list of subject areas that will be addressed in the OnCoRe Blueprint. This is a preliminary list and subjects will be added, expanded, and reorganized as the project develops. There will also be a wiki established for interested parties to discuss these topics and provide information.

Policy

• Standards
  • Quality review — which criteria will be used to evaluate items for possible inclusion in the repository?
  • Tagging—what metadata schema will be used to identify and label content?
  • Workflow— what is the process for naming and sequencing the steps needed for creation, review, editing, and acceptance of items prior to their inclusion in the repository?
• Vocabularies—which controlled vocabularies will be selected to describe repository items?

Communication

• What are the most effective method for communicating with the various constituencies that will use the repository? (e.g., users, contributors, development team, technical support)
• What is the most effective method for communicating with the various constituencies that will use the repository? (e.g., users, contributors, development team, technical support)
• What is the best ways to inform and engage users and contributors in the repository?
• Which marketing tools, vehicles, and venues are available? (e.g., web, wikis, paper base)

Technology

• Hardware—how will the repository be physically housed? What are the system and server needs?
• Software—which software will be needed to sustain the project ?
• Interaction—which methods will the repository be able to use to interact with: other repositories, other collections, content management or learning management systems (e.g., OSIDS, Z39.50, SRU, SRW)?
• Interoperability standards—which standards will be used or mandated to ensure interoperability among user systems (e.g., SCORM).
• Technical Standards—which other technical standards will be mandated for the repository (e.g., 508 compliance)?

Sustainability

• Funding
  • What sources of funding are available for the project (e.g., legislative appropriations, grants, institutional, private donors)?
  • What is the time period for which funding has been committed?
  • What additional funding needs should be addressed?
• Staffing—What repository functions must be staffed? Blueprint will provide suggested repository roles and sample job descriptions
• Training—What type of training will be needed for users, contributors, and administrators (e.g., online, tutorials, personal training sessions) Blueprint will suggest training topics and provide examples of training modules.

Content

• What is the purpose of the repository (e.g., instructional content for students, professional development materials for educators, institutional archives for administration/research)?
• How is content acquired for the repository?
• Copyright/Digital Rights Management

Dissemination/Change Management

• What strategies will be used to help repository users accommodate new ways of teaching and new ways to create content?

Evaluation