Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Requirement #1733 (closed)

Opened 11 years ago

Closed 8 years ago

Public data

Reported by: atarkowska Owned by:
Priority: critical Milestone: OMERO-4.4
Component: General Keywords: n.a.
Cc: omero-team@… Business Value: n.a.
Total Story Points: n.a. Roif: n.a.
Mandatory Story Points: n.a.

Description (last modified by jmoore)

As the consequence of the sharing data, OMERO needs to allow people to make their data public (accessible in Internet).

Web Usage

User should be able to generate a link to the public data, for example:

  • http://host/user_name/public/image/1/
  • http://host/user_name/public/dataset/2/

This feature was based on the webmobile prototype, and is now implemented using decorators that can automatically login an "anonymous" user for all supported groups.

Other supporting features that went into this requirement include:

  • the decorator support in web itself
  • differentiation of read-annotate and read-write groups
  • easier (and faster) changing of group permissions

Change History (11)

comment:1 Changed 10 years ago by atarkowska

  • Description modified (diff)
  • Type changed from User Story to Requirement

comment:2 Changed 10 years ago by atarkowska

  • Description modified (diff)
  • Keywords jmoore added
  • Summary changed from Accessing the data to Public data

comment:3 Changed 10 years ago by atarkowska

  • Description modified (diff)

comment:4 Changed 10 years ago by atarkowska

  • Milestone changed from OMERO-Beta4.2 to Unscheduled

comment:5 Changed 10 years ago by jmoore

  • Milestone changed from Unscheduled to OMERO-Beta4.3

comment:6 Changed 10 years ago by jmoore

  • Cc jburel jrswedlow jmoore added
  • Keywords jmoore removed

A few requirements from Jason:

  • User should be able to look at Project, Dataset, Image, Screen, Plate, Well, Tag, TagSet? and immediately that container 'published'. This specifically means that from that point on, that data can be access from a simple URL, without a sessionid in standard web browser.
  • In the fullness of time, we can think about wiki's, etc, but I wouldn't do this right away.
  • We will need to standardise annotation strategy and expression of those annotations, for access by search engines and other machines. For examples on this, we might look at Uniprot, at least for functional annotations, OME-XML for microscope annotations and so on.
  • Annotations on data, including analyses etc., should be optionally published.
  • A published image should contain whatever metadata is necessary (metadata in a web sense, of which our standard understanding of metadata is a subset) so that image data can be indexed and found using queries the world now uses . "Swedlow taxol kinetochore' doesn't get me to the JCB DV (or wherever such data should reside), but it should. This point is probably most important-- published data should be searchable, in the way the world understands the word 'searchable'. We may need to do some work to define how doi's are expressed, and what opportunities there are for self publishing-- whatever is the standard way of doing this on the web is what we will have to do, preferably in the first release of this.

Releasing data, systematising the annotations on data (while continuing to allow all the freeform stuff), and making data searchable, are probably the priorities here.

comment:7 Changed 9 years ago by cxallan

  • Milestone changed from OMERO-Beta4.3 to Unscheduled

comment:8 Changed 9 years ago by jmoore

  • Cc omero-team@… added; jburel jrswedlow jmoore removed
  • Component changed from Web to General
  • Milestone changed from Unscheduled to OMERO-Beta4.4
  • Owner atarkowska deleted
  • Priority changed from major to critical

Closed #320 ("chgrp") as duplicate of this requirement. #3532 (chgrp server side) branch is at Jean-Marie will start an insight branch and new story under this req which shows multiple servers/groups in the UI (for dragging from one to the other, etc). We will need to evaluate the same work on the web side in the new year.

Though not all of the user stories list here will be completed, some of these features will likely be the most user-impacting part of 4.4 so changing to "critical" and 4.4.

comment:9 Changed 8 years ago by jmoore

  • Description modified (diff)

Original "Initial public data work" text from #3527:

== Day 3 (Wed., the 17th) ==

Public data disussion
    * Implementation options that were discussed
        * Using the "user" group, i.e. the common space
        * One share per image or one big share
        * Multiple public groups v. one public group
        * Using world flag per row (in addition to group)
        * Subgroups
        * Copy to a public server
        * ACLs
    * Requirements that were discussed
        * Google-able
        * Optional annotations
        * Object URL
        * Collaborative containers
        * Unpublish
        * in-group, between-group, public sharing
        * protecting binary data
    * Other items
        * @@check share performance
        * adding licensing/copyright information on "publication"
        * any form of writing or linking on public data?
        * refactor or rollback or add shares to Insight. Needs UI investigation.
    * Two primary solutions to be investigated
        * Use chgrp for collaboration and row-level world-read for publishing
        * Subgroups

comment:10 Changed 8 years ago by jburel

This requirement is very large and will probably be pushed from milestone to milestone.

comment:11 Changed 8 years ago by jmoore

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

Open stories are all in other milestones (Unscheduled or Future). I've linked them into a follow-up requirement #9303. Closing.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.212757 sec.)

We're Hiring!