Proposed Version 1 of Lenses:

1. Data: Content Selection Lenses as described in "Lenses: Proposed functional descriptions and high level design" from these source files. A page on Connexions will display the selected content with a tag cloud that shows how the lensing person or organization has tagged content and allows narrowing the content by clicking on tags. Each piece of content will display the lensing organization's comments. Version ranges should be supported.
2. Data: Organizational Account : Implementation of rganizational accounts so that lenses can be created by Organizations. These accounts will be almost identical to the user accounts. For Version 1 we think that an account that simply changes the metadata to make a sensible organization name appear will suffice. For version 2, the ability to associate author accounts and use inherited permissions can be supported. Cameron, Ross -- make sure this will suffice. Also, if we change the account metadata -- how will it look when displaying Module by: and Collection by: and how will the Author pages be affected. Will these show up in Browse by? Implementation Page http://rhaptos.org/development/ongoing/lensv1/orgAcct
3. Data: Import/Export XML http://rhaptos.org/development/ongoing/lensv1/xml
4. Pseudocode : http://rhaptos.org/development/ongoing/lensv1/plan
5. Development Breakdown: http://rhaptos.org/development/ongoing/lensv1/breakdown
6. Lens Licensing : Lenses will explicitly be CC-By licensed. We will not provide versioning and deriving capability.
7. Workflows
   1. Create an organizational account
   2. Display a list of lenses
      Lens listing pages will be available at
      • cnx.org/lenses/ which will list all lens types (under the creating accounts)
      • cnx.org/endorsements which will list only lenses that consider themselves to be endorsements, and
      • cnx.org/affiliations (We need a better name for this) which will list lenses that collect content associated with a authors affiliated with a particular institution or organization.
   3. Display a Particular CS Lens Pages:
      Individual lens pages will be available under those hierarchies:
      • cnx.org/lenses/[account name]/[lensname]
      • and cnx.org/[lenstype]/[account name]/[lensname]
   4. Workflow: Finding a lens
      • Know of one and need to find it (Browse Endorsers, Browse Lenses)
      • Advertising them -- Front page and on browse.
   5. Workflow: Retrieve lens data programmatically : Lens data will be available programmatically using RSS and OAI. The design should include the structure of the feed but the implementation can come out in August if need be.
   6. Workflows: Create and populate a CS Lens:
      • Create an Organizational Account and then Create a Lens:
      • Create a lens: Lens setup interface within Connexions accounts for setting up a lens. This might involve giving the delicious account information. The interface will provide a way to select the lens type (endorsement, affiliation thing, reviews, just a list). At this point how these types translate into display on content found outside the lens will be arbitrated by Connexions but eventually will be controlled by Trust Profiles.
      • Select Content for a Lens
        • Add a module to a lens using the "Save to " button on content
          • Find out account information and which lens to save to
          • Versioning: ask appropriate version information - "This version only", "This version and updated versions, but notify me when changes are made." Cameron thinks that notification can be implemented for version 1.
          • Allow to add tags and comments.
          • For version 2, we will support pathways for adding content from search, but not for version 1. Collection adding is the most common case, so should not be a huge burden on the lens maker.
        • Add a collection to a lens from the collection home page only (for version 1 at least): Endorsing a collection will cause all modules within that collection to be endorsed when they are viewed within the collection, but will not appear endorsed outside the module. The selector can be given the choice of endorsing the modules within the collection even when the modules are found from google outside the collection. We think that this will be a common desire -- organizations want their endorsements seen, and don't necessarily want to have all the individual modules show up in a long list on their lens page. We will figure out a reasonable way to implement looking up whether a module is implicitly endorsed by being a member of an endorsed collection efficiently.
   7. Workflow: Import lens data: Create a lens and import an XML document that contains the lens data. Must define this structure and make sure we are capable of handling it.
   8. Workflow: Export lens data for edit and reimport
   9. Workflow: Viewing a module:
      1. Displaying Quality Information on modules -- display what lenses, lists, endorsements etc the module is listed in.
         1. Viewing a module :
            • Display the endorsement and affiliation lenses that the module is included in under Quality Box.
            • Display the selection lenses that the module is included in under "Lenses" box.
            • Display the lenses that the module is implicitly endorsed in (part of a lensed collection with the implicit flag set)
            • Future -- Tags -- Display the tags and comments that have been applied through the lensing mechanism on this module/collection. When the tag is clicked, display all items with this tag.
         2. Viewing a collection home page:
            • Display the endorsement and affiliation lenses that the module is included in under Quality Box.
            • Display the selection lenses that the module is included in under "Lenses" box.
            • Future -- Tags -- Display the tags and comments that have been applied through the lensing mechanism on this module/collection. When the tag is clicked, display all items with this tag.
         3. Viewing a module within a collection: In addition to displaying the lenses that the module is included in, also display the lenses that the collection is included in -- don't distinguish in the interface between whether the lenses endorsed the module or the collection.
   10. Workflow: Publish a module included in a lens
       • No change from publisher's perspective.
       • Find in lenses and in collections in lenses, Notify lens makers of changes.
   11. Workflow: Publish a collection included in a lens
       • No change from publisher's perspective.
       • If implicit endorsement of contained modules, ppdate data structures about contained modules.