20110603 Quick Review

From ImageWeb

Jump to: navigation, search

Contents

Activities from 21-May-2011 to 03-June-2011

See also:

Outstanding issues at high or medium priority, not including those that are specifically for Databank, are covered here.

Last Week

Addressed Media wiki's security issue. Restored the security restrictions from backup.(GK, BA)

Attended the ADMIRAL partner's meeting held on: 26-5-2011 (http://imageweb.zoo.ox.ac.uk/wiki/index.php/ADMIRAL_20110526_project_partners_meeting)

Issue 42: (User Admin interface) (Work in progress) (BA)

  • Developed other services around the same pattern implemented for modifying the system user information and continued stabilizing the interface.
  • Developed test case to modify the ADMIRAL user information.
  • Issues regarding httplib requestes were resolved.
  • Familiarized with web.py APIs available at: http://webpy.org/docs/0.3/api#web.http
  • Investigated and implemented error handling for one of the services. Will apply the same pattern across further services that will be developed later.

Silk issues: (GK, BA)

         - Investigated on how to resolve Mac problems with visibility of RGLeader's shared and collab areas by RGMembers.
           This strange problem appears only on Mac clients, and seems to be related to file group ownership.

Submission Interface UI :(DS, BA, GK)

         - Discussed on the UI changes that are immediately necessary to make the submission interface more clear.
         - Silos per research group were created by the Oxford DataBank.

Admin Interface UI :(DS, BA, GK)

         - Discussed the UI changes necessary to make the Admin Interface more clear.

This week

Fix the collab area issue. Perform some tests on to see if/how to create a new user account with multiple user read/write access to shared and collab areas. (GK, BA)

Continue with UI changes for the submission interface (BA,GK,DS)

Future scheduled

Issue 42: (User Admin interface) (Work in Progress) (BA)

         - To change from direct usage of httplib to httpsession and refactor the common code into a common area in the src directory to reduce redundancy, 
          improve visibility and readability. 
         - Adoptmodwsgi to deploy the AdmiralUI.py application.
         - Familiarize with modwisgi setup and Apache configuration.
         - Deploy the application for production environment using modwsgi. This will eliminate the need to run a stand-alone application. 
           (Deploying webpy applications: http://library.linode.com/frameworks/webpy/ubuntu-10.04-lucid#sph_id4)

Issue 45: (Debian package) (Continue building up a simple package) (BA)

Review old test suites (be aware of issue 39 - maybe schedule this)

Refactor common code and eliminate duplicates.

Deployment of Admin UI.

Blockers

Issue 25: Samba permissions problem (issue 25)

Issue 53: Rethink web access control

Stable Databank for research data publication

  • Feature stability (i.e. managed change only); this probably means separation from the development instance
  • Deployment stability (i.e. managed changed only) with managed back-end storage
  • Stable authentication framework with adequate security for user data (in case of confidentiality)
  • Stable URI for accessing deposited data
  • See also: http://code.google.com/p/admiral-jiscmrd/issues/list?q=label:Databank


Blocked

Issue 15: (Logout) Blocked on issue 53.

Issue 16: (area in which RGMembers can collaboratively update files) Blocked on issue 25

Issue 37: (Databank authentication request unclear) Blocked on issue 53.

Personal tools
Oxford DMP online
MIIDI
Claros