Personal tools
You are here: Home → Documents → SKEN Requirements → Requirements Table
Navigation
Log in


Forgot your password?
New user?
 
Document Actions

Requirements Table

by ploneadmin — last modified 2005-01-31 11:24

Latest release of the complete list of Project Requirements for the Science Knowledge and Education Network


SKEN Project Requirements

Revision 1.0 - January 26, 2005

0. SKEN shall create a Content Management Framework (CMF) for dissemination of scientific knowledge.
0.1. SKEN CMF shall provide a framework for managing scientific content for any discipline.
0.2. SKEN CMF shall provide a framework for developing interactive content delivery applications.
0.3. The SKEN software platform and documentation shall be delivered as an open-source product.
0.3.1 The SKEN software platform and documentation shall be available at no charge.
0.4. SKEN shall have three demonstration cases.
0.4.1. SKEN shall use Cornell Lab of Ornithology's Birds of North America as it's primary demonstration case (proof of concept).
0.4.2. SKEN may use Cornell Lab of Ornithology's Home Study Course in Bird Biology as a secondary demonstration case.
0.4.3. SKEN may use the Smithsonian Institution's Encyclopedia of Life as a secondary demonstration case


1. SKEN CMF shall provide an information architecture that enables online management of scientific content.
1.0. Content is defined as any informational object that is pertinent to the purpose or intention of an application.
1.0.1. Primary content is defined as that content that provides the key information to be presented by an application.
1.0.2. Complementary content is defined as content that provides information that supplements or extends the primary content.
1.0.3. Published content is defined as any content that has been made publicly available within the application.
1.0.4. Unpublished content is defined as content that has been created but has not been made publicly available.
1.1. SKEN CMF shall provide an content management infrastructure that enables the construction and maintenance of scientific content.
1.1.1. The content management infrastructure shall provide a mechanism for creating new content.

1.1.1.1. The content creation mechanism shall not require creators of content to be familiar with XML.

1.1.1.2. The content creation mechanism shall not require creators of content to be familiar with HTML.
1.1.2. The content management infrastructure shall provide a mechanism for editing of existing content.

1.1.2.1. The content editing mechanism shall not require creators of content to be familiar with XML.

1.1.2.2. The content editing mechanism shall not require creators of content to be familiar with HTML.

1.1.2.3. The content editing mechanism shall maintain previous versions of content.

1.1.2.4. The content editing mechanism shall provide a method to compare differences between content versions.

1.1.2.5. The content editing mechanism shall provide a transaction log of all changes.

1.1.2.6. The content editing mechanism shall provide a method to audit change transactions.
1.1.3. The content management infrastructure shall provide a mechanism for peer review of changed content.

1.1.3.1. The peer review mechanism shall provide a method to specify which content is to be reviewed.

1.1.3.2. The peer review mechanism shall provide a method to assign content to a reviewer.
1.1.4. The content management infrastructure shall provide a mechanism to validate new content or content changes against publication standards.

1.1.4.1. The content management infrastructure shall provide a mechanism to accept valid content for publication.

1.1.4.2. The content management infrastructure shall provide a mechanism to prevent invalid content from being published.
1.1.5. The content management infrastructure shall support multiple content types.

1.1.5.1. The content management infrastructure shall support textual content.

1.1.5.2. The content management infrastructure shall support digital image content.

1.1.5.3. The content management infrastructure shall support content consisting of figures and their captions.

1.1.5.4. The content management infrastructure shall support table-style content.

1.1.5.5. The content management infrastructure shall support digitial video content.

1.1.5.6. The content management infrastructure shall support digital audio content.

1.1.5.7. The content management infrastructure shall support bibliographic content.
1.1.6. The content management infrastructure shall provide a mechanism to facilitate online, realtime collaboration among multiple contributors.

1.1.6.0. Contributor shall be defined as any user whose role entitles them access to unpublished content. For example, the author(s), reviewers and editor(s) of a particular document are all contributors to that document.

1.1.6.1. The content collaboration mechanism shall provide a forum for interaction among authorized contributors.
1.2. SKEN CMF shall provide an content management infrastructure that enables online publishing of scientific content.
1.2.1. The content management infrastructure shall provide a mechanism for separation of content and presentation.

1.2.1.1. The content managment infrastructure shall support alternative presentation templates for content.
1.2.2. The infrastructure shall support integration of multiple content types in a single presentation.
1.3. SKEN CMF shall provide an authorization infrastructure for identification and authorization of individual users.
1.3.1. The authorization infrastructure shall provide a mechanism for registration of users of the content.
1.3.2. The authorization infrastructure shall provide a mechanism to assign and manage content access privileges on a per user basis.

1.3.2.1. The authorization infrastructure shall provide a mechanism to define and verify access privileges for Authors.

1.3.2.2. The authorization infrastructure shall provide a mechanism to define and verify access privileges for Editors.

1.3.2.3. The authorization infrastructure shall provide a mechanism to define and verify access privileges for Reviewers.
1.4. SKEN CMF shall provide an access control infrastructure to protect content and prevent unauthorized access.
1.4.1. The access control infrastructure shall provide a mechanism to prevent publishing of new content by unauthorized users.

1.4.1.1 Users that are registered and authorized as Authors shall have sufficient privileges to create new content.
1.4.2. The access control infrastructure shall provide a mechanism to prevent changing of existing content by unauthorized users.

1.4.2.1. Users that are registered and authorized as Authors shall have sufficient privileges to change published content.

1.4.2.2. Users that are registered and authorized as Editors shall have sufficient privileges to change published content.
1.4.3. The access control infrastructure shall provide a mechanism to restrict peer review to authorized users.

1.4.3.1. Users that are registered and authorized as Reviewers shall have sufficient privileges to review changed content.

1.4.3.2. Users that are registered and authorized as Editors shall have sufficient privileges to review changed content.
1.4.4.
 The access control infrastructure shall provide a mechanism to restrict publication activities to authorized users.

1.4.4.1. Users that are registered and authorized as Editors shall have sufficient privileges to publish valid content.

1.4.4.2. Users that are registered and authorized as Editors shall have sufficient privileges to reject invalid content.
1.4.5. The access control infrastructure shall provide a mechanism to restrict attachment of complementary content to published content.

1.4.5.1. The access control infrastructure shall provide a mechanism to restrict attachment of annotations.

1.4.5.2. The access control infrastructure shall provide a mechanism to restrict attachment of comments.
1.4.6. The access control infrastructure shall provide a mechanism to prevent conflicting content changes in situations where there are multiple users working on the same document.
1.5. SKEN CMF shall provide a metadata management infrastructure.
1.5.1. The metadata management infrastructure shall provide a mechanism for collection of content metadata.

1.5.1.1.The metadata management infrastructure shall provide a mechanism to collect technical metadata.

1.5.1.1.0. Technical metadata is defined as information that describes the location, version, ownership, and provenance of managed content.

1.5.1.1.1. Technical metadata shall be collected in a form that is compatible with metadata standards established by NSDL in metamanagement.comm.nsdlib.org/outline.html

1.5.1.1.2. The metadata management infrastructure shall provide a mechanism to collect technical metadata from all primary content.

1.5.1.1.3. The metadata management infrastructure shall provide a mechanism to collect technical metadata for harvested content.

1.5.1.2. The metadata management infrastructure shall provide a flexible mechanism for defining contextual metadata.

1.5.1.2.0. Contextual metadata is defined as discipline-specific information that is intrinsic to the objects, entities and concepts specified in the primary content.

1.5.1.2.1. The metadata management infrastructure shall allow for definition of different types of contextual metadata in each installation or application of SKEN.

1.5.1.2.2. The metadata management infrastructure shall provide a browser-based mechanism to collect contextual metadata.
1.5.2. The metadata management infrastructure shall provide a mechanism to query collected metadata.

1.5.2.3. The metadata management infrastructure shall provide a mechanism to query metadata from harvested content.
1.5.3. The metadata management infrastructure shall provide a mechanism for exploration of collected metadata.

1.5.3.1. The metadata management infrastructure shall provide a mechanism to explore metadata from harvested content.

1.5.3.1. The metadata management infrastructure shall provide a mechanism to explore primary content for the purpose of extracting contextual metadata.
1.5.4. The metadata management infrastructure shall provide a mechanism for the exchange of collected metadata.

1.5.4.1. The metadata management infrastructure shall provide a publication mechanism that conforms to the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH; www.openarchives.org/OAI/openarchivesprotocol.html)

1.5.4.2. The metadata management infrastructure shall provide a mechanism for publishing technical metadata.

1.5.4.2.1 The metadata management infrastructure shall provide a method to publish technical metadata that conforms to metadata standards established by NSDL in metamanagement.comm.nsdlib.org/outline.html

1.5.4.3. The metadata management infrastructure shall provide a mechanism for publishing contextual metadata.

1.5.4.4. The metadata management infrastructure shall provide a mechanism for importing technical metadata.

1.5.4.4.1. The metadata management infrastructure shall provide a method to import technical metadata that conforms to metadata standards established by NSDL in metamanagement.comm.nsdlib.org/outline.html

1.5.4.5. The metadata management infrastructure shall provide a mechanism for importing contextual metadata.
1.6. The content management infrastructure shall provide a mechanism for the enforcing a workflow in the publication process.
1.6.1. The workflow mechanism shall provide flexibility in specifying workflow.
1.6.2. The workflow mechanism shall be able to handle complex interactions among authors, reviewers and editors.
1.6.3. As a minimum, the workflow mechanism shall support the following steps :

1.6.2.1. Author screates new new content of changes existing content.

1.6.2.2. Author submits new/changed content for validation.

1.6.2.3. Editor reviews new/changed content.

1.6.2.3.a. Editor makes changes to content before publishing.

1.6.2.4. Editor publishes content.

1.6.2.4.a.Alternatively, Editor rejects content and returns to Author rework.
1.7. The content management infrastructure shall provide a mechanism to create complementary content.
1.7.1. The content management infrastructure shall provide a mechanism to attach annotation to content.
1.7.2. The content management infrastructure shall provide a mechanism to attach comments to content.
1.7.3. The content management infrastructure shall provide a mechanism to abridge (abstract) content.

1.7.3.1. The content management infrastructure shall provide a mechanism to create an abridging template.
1.8. The content management infrastructure shall provide a mechanism to explore published content.
1.8.1. The content management infrastructure shall provide a mechanism to compare content.
1.9. The content management infrastructure shall provide a private workspace for each authorized site member.
1.9.1. The workspace infrastructure shall provide a mechanism for each member to create original content.

1.9.1.1. The workspace infrastructure shall provide a mechanism for a member to post experimental or observational data.

1.9.1.2. The workspace infrastructure shall provide a mechanism for a member to create preliminary or provisional documents.
1.9.2. The workspace infrastructure shall provide a mechanism for each member to create abstracts of primary content.
1.9.3. The workspace infrastructure shall provide a mechanism for each member to create alternative presentations of primary content.
1.9.4. The workspace infrastructure shall provide a mechanism for each member to publish their complementary content.


2. SKEN CMF shall provide an information architecture that supports online discussion forums.
2.1. The discussion forum infrastructure shall support open participation by members of the ???? community.
2.1.1. By default, all members of the ???? community shall be authorized to participate in discussions.
2.1.2. By default, all members of the ???? community shall be authorized to initiate discussions.
2.2. The discussion forum infrastructure shall support unmoderated discussions.
2.2.1. Authors shall be authorized to remove inappropriate discussion postings.
2.2.2. Editors shall be authorized to remove inappropriate discussion postings.
2.3. The discussion forum infrastructure shall support discussions that cross the organizational structure of the primary content.


3. SKEN CMF shall provide an information architecture that facilitates the integration of content from complementary sources with published primary content.
3.1. SKEN CMF shall provide an infrastructure for integrating content from external sources with primary content.
3.1.1. The content integration infrastructure shall provide a mechanism for integrating harvested metadata with primary content.

3.1.1.1. The internet search infrastructure shall provide a mechanism to integrate metadata for bibliographic references with primary content.
3.2. SKEN CMF shall provide an infrastructure for integration of discussion forums with primary content.
3.3. The content integration infrastructure shall provide a mechanism for integrating private complementary content with primary content.
3.4. The content integration infrastructure provide an mechanism for integrating derived educational content with primary content.


4. SKEN CMF shall provide an information search infrastructure.
4.1. SKEN CMF shall provide an infrastructure for locating complementary information on the Internet.
4.1.1. The internet search infrastructure shall provide a mechanism to search online digital repositories.

4.1.1.1. The internet search infrastructure shall provide a mechanism to specifiy target repositories.

4.1.1.2. The internet search infrastructure shall provide a mechanism to search for bibliographic references that are related to primary content.
4.1.2. The internet search infrastructure shall provide a mechanism to harvest metadata from digital repositories.

4.1.2.1. The internet search infrastructure shall provide a mechanism to harvest metadata for bibliographic references.
4.1.3. The internet search infrastructure shall conform to the Open Archives Initiative-Protocol for Metadata Harvesting (OAI-PMH; www.openarchives.org/OAI/openarchivesprotocol.html)
4.1.4. The internet search infrastructure shall provide a mechanism to automate searches.
4.1.5. The internet search infrastructure shall provide a mechanism to organize collected information.

4.1.5.1. The internet search infrastructure shall provide a mechanism to organize collected information by taxonomy.

4.1.5.2. The internet search infrastructure shall provide a mechanism to organize collected information by subject.
4.1.6. The internet search infrastructure shall provide a mechanism to browse collected information.

4.1.6.1. The internet search infrastructure shall provide a mechanism to browse collected information by taxonomy.

4.1.6.2. The internet search infrastructure shall provide a mechanism to browse collected information by subject.
4.2. SKEN CMF shall provide a search infrastructure based on content metadata.
4.2.1. The metadata search infrastructure shall provide an interface to technical meatadata.

4.2.1.1. The metadata search infrastructure shall provide a mechanism to use technical metadata as criteria in searches.

4.2.1.2. The metadata search infrastructure shall provide a mechanism to include technical metadata in search results.

4.2.1.3. The metadata search infrastructure shall provide a mechanism to use technical metadata to filter search results.
4.2.2. The metadata search infrastructure shall provide an interface to contextual meatadata.

4.2.2.1. The metadata search infrastructure shall provide a mechanism to use contextual metadata as criteria in searches.

4.2.2.2. The metadata search infrastructure shall provide a mechanism to include contextual metadata in search results.

4.2.2.3. The metadata search infrastructure shall provide a mechanism to use contextual metadata to filter search results.
4.3. SKEN CMF shall provide an infrastructure for searching primary content.
4.3.1. The content search infrastructure must provide a mechanism to retrieve a subset of primary content.
4.3.2. The content search infrastructure must provide a mechanism to retrieve an atom??? of a published document.
4.4. SKEN CMF shall provide an infrastructure for searching derived educational content.
4.5. The search infrastructure shall provide a mechanism for ranking the relevancy of search results.
4.5.1. The search infrastructure shall provide a rule-based mechanism for ranking the relevancy of search results.
4.5.2. The search infrastructure shall provide a heuristic mechanism for ranking the relevancy of search results.
4.6. The search infrastructure shall support context sensitive data comparison mechanisms.
4.6.1. The search infrastructure shall support a text comparison mechanism.
4.6.2. The search infrastructure shall support a numeric comparison mechanism.
4.6.3. The search infrastructure shall support a date comparison mechanism.
4.7. The search infrastructure shall provide a mechanism for saving search criteria.


5. SKEN CMF shall provide an information architecture that permits published primary content to be repurposed.
5.1 SKEN CMF shall provide an infrastructure for repurposing primary content as educational material.
5.1.1. The education infrastructure shall provide a mechanism to create course modules from primary content.

5.1.1.1. SKEN shall investigate the feasibility of providing a mechanism to restructure primary content into CNXML course modules.
5.1.2. The education infrastructure shall provide a mechanism to publish derived educational material.

5.1.2.1. SKEN shall investigate the feasibility of publishing derived educational material using CNXML ( cnx.rice.edu/technology/cnxml/0.5/spec/)

5.1.2.2. SKEN shall investigate the feasibility of publishing derived educational material using the the iLumina Digital Library project ( www.ilumina-dlib.org) method of sharing materials.

1.5.1.2.3. The metadata management infrastructure shall provide a mechanism to select keywords from primary content for inclusion in contextual metadata.


6. SKEN CMF shall provide a digital library infrastructure.
6.1 The digital library infrastructure shall provide a mechanism for close integration with elements of the NSDL.
6.2 The digital library infrastructure shall provide a mechanism for sharing educational content.
6.3. The digital library infrastructure shall provide a mechanism to publish metadata according to standards established in the Open Archives Initiative-Protocol for Metadata Harvesting (OAI-PMH; www.openarchives.org/OAI/openarchivesprotocol.html).
6.3.1. The digital library infrastructure shall provide a mechanism to publish technical metadata in the format specified by the Dublin Core Metadata Initiative.
6.3.2. The digital library infrastructure shall provide a mechanism to publish contextual metadata in a format compatible with OAI-PMH.


99. SKEN CMF shall be built using open-source software products.
99.1. SKEN CMF shall use Plone as the base Content Management System.
99.2. SKEN CMF shall use Zope as the base Application Development Framework.
99.3. SKEN CMF shall use Python as the primary programming language.
« October 2008 »
Su Mo Tu We Th Fr Sa
1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31
 
Powered by Plone CMS, the Open Source Content Management System

This site conforms to the following standards: