Difference between revisions of "OneShare"

From EPrints Documentation
Jump to: navigation, search
Line 7: Line 7:
 
Tasks
 
Tasks
  
What is a bare minimum for metadata?
+
# What is a bare minimum for metadata?
What do we do with Uni divisions/hierarchy? Part of extended schema? Part of core-data?
+
# What do we do with Uni divisions/hierarchy? Part of extended schema? Part of core-data?
What do we do with the security model eg viewing/editing permissions? see below.
+
# What do we do with the security model eg viewing/editing permissions? see below.
Do we include or provide different subjects hierarchies (eg JACS...)? As an optional feature?
+
# Do we include or provide different subjects hierarchies (eg JACS...)? As an optional feature?
  
What is the name of a 'resource'? A 'Resource' or a 'Share'?  
+
# What is the name of a 'resource'? A 'Resource' or a 'Share'?  
What are the basic data types?? On EdShare we have shares, collections, bookmarks, shoppbasket. On LBox we have resources, "resource_collection" -> need to harmonize.
+
# What are the basic data types?? On EdShare we have shares, collections, bookmarks, shoppbasket. On LBox we have resources, "resource_collection" -> need to harmonize.
  
 
  Also see sections on Collections, Bookmarks.
 
  Also see sections on Collections, Bookmarks.
  
 
Priority: high, core feature!
 
Priority: high, core feature!
Time: dev < 1 week, politics < 1 month hopefully
 
  
 +
Time: dev < 1 week, politics < 1 month hopefully
  
 
==(User) Worflow==
 
==(User) Worflow==
  
Define a user workflow i.e. how does the user interact with the repository? What is their path thru the site for creating, managing their resources?
+
Define a user workflow i.e.:
 +
 
 +
# how does the user interact with the repository?  
 +
# What is their path through the site for creating, managing their resources? Is it consistent?
  
 
On Edshare, this needs loads of improvements :)
 
On Edshare, this needs loads of improvements :)
Line 30: Line 33:
  
 
Priority: low
 
Priority: low
 +
 
Time: 1-2 dev, 1 week politics
 
Time: 1-2 dev, 1 week politics
  
Line 43: Line 47:
 
# <add more>
 
# <add more>
  
Or use a dedicated server for the task?
+
# Or use a dedicated server for the task?
 
+
# Where do we store the previews on the filesystem? In the thumbnails dir? etc... Backport the EP3.2 model?
Where do we store the previews on the filesystem? In the thumbnails dir? etc... Backport the EP3.2 model?
+
# Do we need to re-factor Pat's work on queuing (for audio/video)?
Do we need to re-factor Pat's work on queuing (for audio/video)?
+
  
 
If local:
 
If local:
 +
 
Priority: med-high
 
Priority: med-high
 +
 
Time: < 1 week
 
Time: < 1 week
  

Revision as of 15:23, 20 October 2009

This page provides information on what makes EdShare/Language Box/OneShare different from a standard EPrints installation.

Add to this page any packages that are relevant to EdShare/LBox.

Data Model

Tasks

  1. What is a bare minimum for metadata?
  2. What do we do with Uni divisions/hierarchy? Part of extended schema? Part of core-data?
  3. What do we do with the security model eg viewing/editing permissions? see below.
  4. Do we include or provide different subjects hierarchies (eg JACS...)? As an optional feature?
  1. What is the name of a 'resource'? A 'Resource' or a 'Share'?
  2. What are the basic data types?? On EdShare we have shares, collections, bookmarks, shoppbasket. On LBox we have resources, "resource_collection" -> need to harmonize.
Also see sections on Collections, Bookmarks.

Priority: high, core feature!

Time: dev < 1 week, politics < 1 month hopefully

(User) Worflow

Define a user workflow i.e.:

  1. how does the user interact with the repository?
  2. What is their path through the site for creating, managing their resources? Is it consistent?

On Edshare, this needs loads of improvements :)

Make links to all features (browsing, searching etc) intuitive/easy to find/consistent.

Priority: low

Time: 1-2 dev, 1 week politics

Preview

Generating previews

Generating previews for:

  1. Microsoft Office formats (+ newer OpenXML standards)
  2. HTML pages
  3. Multimedia files (video + audio)
  4. <add more>
  1. Or use a dedicated server for the task?
  2. Where do we store the previews on the filesystem? In the thumbnails dir? etc... Backport the EP3.2 model?
  3. Do we need to re-factor Pat's work on queuing (for audio/video)?

If local:

Priority: med-high

Time: < 1 week

Previews/Coverflow-like interface

This will be a part of another conversation.

Decide of a nice "player"?!

Priority: super high Time: ? months?

MePrints Profiles

Any new Ed/LB/OneShare install should come with the MePrints package installed.

It would be great to have widgets specific for EdShare/LangBox. Ideas? stats, comments, feeds...

Priority: low, finished project Time: 0

Social Tools

Add tools for commenting on resources. Maybe use SNEEP or Pat/Marcus' updated version. Test on HTTPS :)

Decide!

Priority: low Time: 1-2 days

Collections

Add virtual collections to EPrints. A virtual collection contains links to other resources.

Priority: low, quite mature code Time: 1-2 days

Bookmarks

A special virtual collection available for every user. Bookmarks are persistent and can be shared to other users.

AJAX Tools exist to easily populate bookmarks from search results, summary pages etc. (cf EdShare Soton).

Using a separate dataobj for bookmarks? This would allow more powerful features eg. "who has bookmarks share X"? Also, this would hide My Bookmarks from my list of resources.

Priority: low, quite mature code Time: 1-2 days

Folder/Shopping Basket

A special virtual collection that allows people to aggregate shares during their current session. This allows easy creation of collections or download of several resources in one go.

Emptied when user logs out. Cannot be shared with other users.

Using a separate dataobj for bookmarks? This would allow more powerful features eg. "who has bookmarks share X"? Also, this would hide My Bookmarks from my list of resources.
Do we need this?

Collections Organiser

The AJAX tool to easily create, edit and manage collections.

Need storyboards from the management layer!
We know that we need a special tool to manage resources/collections but is this the appropriate one?
Could this replace the 'Manage Deposit' screen altogether (whether collections are enabled or not)?

Priority: need requirements Time: unknown

Security

Viewing Permissions

Use EdShare Soton's advanced viewing permissions to share with selected users, schools etc.

Previews are also included into that model i.e. you cannot see previews for a resource if you're not allowed to view/download the resource.

Editing Permissions (TO DO)

Cf. Viewing Permissions but for editing.

Maybe merge viewing + editing perms into a more generic ACL system.

ACLs for Viewing and Editing items

We could create a system of ACL (Access Control List) for each share/resource and add the appropriate hooks in the code:"can_user_edit", "can_user_view".

The idea on EdShare Soton is good (share with school, uni, x/y) but need refactoring/rewriting.
How do we generalise this to EPrints and add the right hooks to the existing eprints code? Maybe ask TimB for advice.

Priority: low Time: 3-4 days to refactor/generalise

UI Styling

Create a unique, generic style for OneShare. This should be eye-catching but generic/neutral enough (cf. a vanilla EPrints install).

This include: default citations for resources and files, site template, frontpage, <add more>.

Also we could package the LBox & EdShare styles as optional themes?

Priority: low Time: unknown?

Embedding content (TO DO)

To allow embeddable objects that present a resource (maybe looking like the coverflow tool).

What do we expect from such a feature? Needs requirements.

Priority: low Time: <1 week

Enforced HTTPS

Make HTTPS compulsory? At least, make all the code COMPLIANT to HTTPS :)

Extra Tools (as optional packages?)

  1. Anti-Virus Scanning: cf. use of Sophos on the EdShare Soton server.
  2. IRStats: improved integration of IRStats with EPrints.
  3. Bulk Upload & related features
  4. Tag cloud
  5. Presentation of latest additions on the frontpage
  6. LBox's remixed resources (cf. cloning on EP).
  7. <add more>

Blackboard integration (TO DO)

Single-deposit paradigm i.e. dissemination from OneShare to BB.

This will be part of a separate conversation.