Website User Interface

From Open Siddur Project Development Wiki

Jump to: navigation, search

Open Siddur Website User Interface

Most comments are in the discussion tab.

Outline Summary

  1. Organization of Content
  2. User Hierarchy
  3. User Interface Design Requirements


Outline

  1. Organization of Content
    1. Core Content
      1. Content is siddur text, metadata, audio, images & video, fonts and layout templates. Aka “ingredients”
      2. nusach preserved arrangements aka “recipes” of content
      3. nusach specific translations, commentary and instructional content
      4. encoded by section according to TEI JLP extension standard
      5. Digitized and encoded by the Core Content Group is shared to all users.
      6. User edits of core content do not modify core
      7. Contributions to core can be made as the result of participation with community users and user-group projects.
      8. Storage of core content managed by open siddur project development team.
      9. Content licensed zlib, CC0 or CC-BY
      10. Required features: online server, internet access, domain name, website hosting and storage, shell access, TEI, JLP/OS TEI extension, python, open source CMS (to be determined), SFTP/SCP, CVS, open source fonts
    2. Community contributed content
      1. User edits of core content, shared to whole
      2. User rearrangements of core content, edits, and additions, shared to whole
      3. User generated siddur “recipes” shared to whole
      4. User/Group contributed new content shared to “friends”
      5. Content encoded via encoding engine (see below)
      6. Edits and new content saved in user storage space
      7. Group collaboration space “owned” by user/adminstrators
      8. Users choice of content to be licensed as CC0, CC-BY, or CC-BY-SA
      9. Siddurim generated with shared CC-BY-SA content to inform users of license obligations
    3. Partner contributed content
      1. Content linked offsite
      2. Requires partner negotiations for redistributing content under CC0, CC-BY or CC-BY-SA EDF -- Can this possibly be right?
    4. Offline and offsite content
      1. Offline or online products or projects built on top of (or using) the Open Siddur must acknowledge use of the Open Siddur, its developers and community of participants EDF -- JLPPL and CC0 only request acknowledgement
      2. Printed content to carry license specific to Open Siddur content used
      3. software projects building on JLP/OS code must be open source EDF -- only if directly derived from our LGPL software
      4. generated content may be commercial or non-commercial but remain open for culture hacking.
  2. User Hierarchy EDF -- This section confuses me. Not sure if we want to store any private data at all
    1. Users and Groups
      1. A “user” is synonymous with a user account at Open Siddur
      2. Users can befriend other users, ie. “friends” by default, for sharing user-defined shared content. (For other permissions, see below).
      3. Collaborating friends form a “group,” content only sharable within that group. (User-contributed Content Group, or UCG)
    2. User/Group Privacy EDF: Do we really want to create a second-rate social networking site?
      1. All user edits, by default, private, not shared EDF -- defaults are powerful suggestions, this doesn't sound right
      2. Sharing occurs with by invitation to friends
      3. User editable friend permissions: viewing, editing, sharing
      4. Friends and groups can opt to share collaborated content and choose licenses with whole only with consensus decision using polls (majority polled? 2/3? 3/5?) EDF: far easier than this -- just use one of the allowed licenses, and everything will be compatible and free
    3. Core Content Group (CCG)
      1. CCG users preparing core content for all (see above, section 1a)
      2. CCG group is a group like any other group
      3. CCG users are users like all other users
  3. User Interface Design Requirements
    1. User Space
      1. Access to Open Siddur toolbox for viewing and all siddur “recipes” (nusach arrangements) and “ingredients” (nusach variant content) from CCG and UCG.
      2. Upload of content to media library (images and video)
      3. User settings for user choice of default license to use for edited content and sharing privileges to friends and whole. (default is private, see above. License is default cc-by-sa). EDF: default derives from original, see comment about private data
      4. Choice of Open Siddur layout templates with fonts, font sizes, colors, and layout of sections. Also, layout of translations, commentary, marginalia, and transliterations, if desired)
      5. Layout’s include (x) marks for removing sections, (+) for adding sections at upper right corner of section, and (^^) for editing the text displayed.
      6. Clicking (+) shows a layer for choosing all other “missing” ingredients that appear in other recipes.
      7. Text in one recipe that is variant in other recipes is shown in RED. Clicking on RED text brings up a clickable layer to see variants in all the other nusachim. EDF: red color as only indicator of difference is a bad idea. See WCAG
      8. (+…) can also appear within a section of text. Clicking on it will reveal a choice of variants that appears in other variations of that section.
      9. Clicking on (^^) opens the text for editing.
      10. Auto saving text in text area.
      11. Choice of fonts/colors/size.
      12. User can also apply upload, but not share their own (not necessarily open source) fonts for application to specific text, or for automatic application to text already tagged as certain sections or from certain periods/sources of authorship. EDF-- this feature might be dangerous to support re: proprietary fonts
      13. Renedered siddur in pdf, content exportable as XML.
      14. Updates available as RSS
    2. Group space
      1. Group space administered by user founding group, fellow administers (invited).
      2. Dropped users: Administrators can drop users, users can leave groups. Users can access all shared content in group worked on in group up until the moment they are dropped. Further shared edits and additions inaccessible
      3. Accessible text of group appears in user space, simply as additional user contributed content when clicking on (+) or in a section as (+…).
      4. Users can edit group shared text without sharing back into group. (See user settings).
      5. Updates available as RSS
    3. Siddur Library
      1. Users, User groups, and the whole (non-user visitors) can access siddurim in various formats (e.g., pdf, xml) and shared universally
      2. Library can be sorted by date of origin, author, name, user-group, community or nusach (and sub-nusach) of origin.
Retrieved from "http://wiki.jewishliturgy.org/Website_User_Interface"
Personal tools
NAVIGATION