Page History

...

Sprint 2: Use ActiveTriples instead ActiveFedora

TBA

...

Ontology Questions

User

• How to represent a user?
  • Possibility <foaf:person>
• How to represent ownship/authorship of a user?
  • <co:list> <dc:creator> <foaf:person>
• How to represent user role to list type relationships
  • <foaf:person> owns <co:list>
  • <foaf:person> canEdit <co:list>  –  facilitates collaboration
  • <foaf:person> canView <co:list>
• How to represent user to group to list type relationships
  • <foaf:person> isIn <group>
  • <group> canEdit <co:list>
  • <group> canView <co:list>
• Are groups and roles in the triplestore?  
  • Or are they maintained separately and in the triple store on as a uri to the group?  
  • Issue:  Any privacy issues with user data being repeated in our triplestore?
  • Issue:  What information do we have access to and permission to put in a public triplestore?

Virtual Collection

• How to represent metadata about the virtual collection?
  • basic metadata
    • title – use <rdf:label>?
    • description
  • controlled vocabulary metadata
    • list of selected vocabularies (ordered list) – use <co:List>?
    • what metadata about each controlled vocabulary will be stored in the triplestore?
      • name – use <rdf:label>?
      • description
      • id:label for each term in the vocabulary – use <co:List>?
    • Are these stored in the main triplestore or as a test file in the file system that is accessible via URL? 
      • NOTE: Questioning Authority has them as files in the rails app structure at /config/authorities, which is not accessible via URL and has a non-triple format.
  • access controls - How to record metadata about?  How to limit access to triples related to virtual collections based on access level?
    • private (only the owner & collaborators can view)
    • shared (semi-private, only those with the access URL can view)
    • public (everyone can view)
    • collaborative (multi-editors)

UI Questions

• How does user stayed logged in to facilitate multiple searches to build a single Virtual Collection? 
  
  • Currently, every time a user clicks My Account, a prompt for logging in is displayed, which implies users are logged out as soon as they leave the My Account page.  (Ask Adam the history of this.)
  • Can we add the notion of a public and private computer?
  • Can we keep an IP address (or other identifier) for a computer that allows us to know this user is accessing the system from a previously authorized private computer?
  • What default length of time forces a log out?  Is this settable by the user?
• How to find a Virtual Collection to watch?
• How to search only within the user's owned Virtual Collections?
• How to search only within the user's watched Virtual Collections?
• How are user public Virtual Collections exposed to the public?
• How are works from external library catalogs searchable and available for inclusion in a Virtual Collection?  (Potential Demonstration B)
• The UI Mockup implies that items in a Virtual Collection can be dynamically sorted (show in title A-Z).  Are dynamic sorts sufficient (title A-Z/Z-A, author A-Z/Z-A, year ASC/DES)?  Potential Demonstration C states that the user can apply an order to items.

...

• UI Mockup is fairly well developed for Potential Demonstrations A and D.  See outstanding questions UI Questions above for areas that may not be represented in the mockup.
• Requirements – TBA – under development.  Not sufficiently complete for review.are fairly well developed for Potential Demonstrations A, C, and D.
• Working on Ontology Questions and creating example triples.

...