Reference Repository
From Open Source Publishing 2.0
[edit] Web Sites
http://www.arl.org/sparc/media/07-0507Forum.html
http://www.taxpayeraccess.org/media/Advisory07-0503.html
http://octavia.zoology.washington.edu/publishing/BergstromAndBergstrom04b.pdf
http://www.fundcdc.org/documents/CDC_FY2008_PJ.pdf
http://www.osti.gov/communications/publications/2007/workshop.pdf
Elsevier Earnings [1]
Harvard Crimson Article [2]
Knuth Letter [3]
Scientific Publishing: A Mathematician's Viewpoint [4]
PHP Leads Web 2.0 [5]
Richard Stallman article in Nature [6]
Peter Suber's Open Access Overview [7]
Remote Authentication against Drupal [8]
Extension:AuthDrupal [9]
LDAP Integration for Drupal [10] and MediaWiki [11]
Drupal-like skin for MediaWiki [12] [13]
PLoS FAQ [14]
ACP Publication Process [15]
HyperJournal [16]
American Scientist Open Access Forum [17]
ASME Financial Report [18]
GuideStar - Financial Information about Non-profits [19]
PLoS Form 990 [20]
UC Letter to Faculty about Reed Elsevier Negotiations [21]
Nature article on PLoS [22]
Real Web 2.0: Meet digg.com and Reddit, heirs of Slashdot [23] [24]
[edit] NSF Requirements
- EVO structure and justification: Vision and mission; organizing and governing structure; members and recruitment; end users; stakeholders; and shared community resources (e.g., experimental facilities, observatories, data collections), their associated service providers, and access / allocation methods. Identify frontier research and education goals of the EVO, including compelling research questions and the potential for broad participation. EVOs will extend beyond small collaborations and individual departments or institutions to encompass wide-ranging, geographically dispersed activities and groups.
- A plan for obtaining and formally documenting user requirements that will inform the EVO design, e.g., through workshops, surveys, and other means. Integration of research and education must be addressed. User requirements must address community cybersecurity and identify other challenges and barriers to design, development, implementation, management and operations, evaluation and assessment, and long-term sustainability.
- Project management plan for implementation of the EVO's prototype. This plan should include a description of the project team and key individuals, their recent or ongoing involvement in VOs and related CI research and development, an organizational chart, and a project schedule for the two-year project, including its prototype deployment with a limited number of the potential CI features.
- Conceptual design for designing a future full-scale implementation. This design process would identify any CI research and development needed for software tools and components currently not existing to meet user requirements either commercially or in a research-and-development phase (e.g., through federally funded projects). Projects must cite any related and existing CI software tools and components with similar functionality, and make a compelling case for the need for new software development work.
- Plan for disseminating the conceptual design to inform CI investments for other scientific and engineering VOs.
