Possible way to develope collaboration for Omero

[atarkowska]

OMERO.collaboration is the web application based on Django http://www.djangoproject.com/ - high-level Python Web framework and cooperates with Blitz server to manage and share datas from the OMERO.server.
The application is not only the "thin client" to manage images, datasets, projects, annotations, tags, etc., it will refer to a trend in web design and development - WEB 2.0 - a perceived second generation of web-based communities and hosted services (such as social-networking sites, wikis, blogs, and folksonomies) which aim to facilitate creativity, collaboration, and sharing between users.

The functionality and attitudes of the application:
Dictionary:
user - member of the system,
group - group with users,
people - users and rest of the world,
CMS - Content Management System.
Object – type of file or object which is supported by the server (image, container, attachment, tag, etc.)

1. Manage:

1. Users Own images, files etc. no one has access to and not shared as default configuration.
2. Multi-objects work.
3. Permissions based on Unix approach - read, write for: private, group, everyone - default permissions for item is private can be changed if required.
4. Accessible/available files stored inside the system by other users
   1. Intranet items - shared items for the place where system is installed.
   2. Internet items - shares and publications.
5. Importing files.

2. View:

1. Supported images by the viewer.
2. Not supported file by the software installed on the user's computer like PDF, MsOffice? documents.
3. Building user’s own viewer for printing out (for example to PDF)

3. Annotate:

1. By attaching personal notes, remarks, links and relationships to other resources, terms from ontologies or controlled vocabularies, ratings and local files such as images, or PDF, MsOffice? documents.

4. Tagging.

5. Search:

1. Search and analyze data to find relevant content.

6. Collaborate:

1. Prepare package you would like to share with people.
2. Define list of users who can have an access to this package (don't have to think about changing permissions for file if they are private).
3. Collaborative discussions (over single thread) about the content with people from your contact list.

7. Publish:

1. Finalize your work by the publishing chosen content.

8. History and tasks:

1. Managing calendar
2. Creating tasks

9. Custom area:

1. Front page - place for information about institution, work, etc. (about us, what does lab do, etc.).

10. Private area:

1. Pages for single user with CMS.
2. Pages for groups with CMS.

[atarkowska]

The functionality and attitudes of the application:
Dictionary:
user - member of the system,
group - group with users,
people - users and rest of the world,
CMS - Content Management System.

1. Manage:

1. Users Own images, files etc. no one has access to and not shared as default configuration - can be changed if required.

(Permissions based on Unix approach - read, write for: private, group, everyone - default permissions for item is private).

1. Accessible/available files stored inside the system by other users
   1. Intranet items - shared items for the place where system is installed.
   2. Internet items - shares and publications.

2. View:

1. Supported images by the viewer.
2. Not supported file can be seen by the software installed on the user's computer like PDF, MsOffice? documents.

3. Annotate:

1. By attaching personal notes, remarks, links and relationships to other resources, terms from ontologies or controlled vocabularies, ratings and local files such as images, or PDF, MsOffice? documents.

4. Search:

1. Search and analyze data to find relevant content.

5. Collaborate:

1. Prepare package you would like to share with people.
2. Define list of users who can have an access to this package (don't have to think about changing permissions for file if they are private).
3. Collaborative discussions (over single thread) about the content with people from your contact list.

6. Publish:

1. Finalize you work by the publishing chosen content.

7. Custom area:

1. Front page - place for information about institution, work, etc. (about us, what does lab do, etc.).

8. Private area:

1. Pages for single user with CMS.
2. Pages for groups with CMS.

[atarkowska]

Preparing interface r2557

[atarkowska]

r2558

[atarkowska]

r2559