Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
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"

User Story #8177 (new)

Opened 12 years ago

Last modified 8 years ago

Investigate for provenance other standards (dublin core)

Reported by: jamoore Owned by:
Priority: critical Milestone: GatherReqs
Component: Specification Keywords: n.a.
Cc: ajpatterson, jburel, jrswedlow, mlinkert, cxallan, rleigh Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description (last modified by jmoore)

As discussed during #7843, much of what is currently stored as "experimenter" or "group" is actually provenance information that cannot be imported directly to the server.

Previous versions of the server would create users and groups as needed. This no longer happens for security reasons, and therefore this information is more or less ignored on import.

If instead, we were to store, say, a structured annotation containing a block of dublin core or similar with who created the file, when, what license it's under, etc., then this information would be stored in the DB and re-attached on export.

This would allow us to move many of the ome.xsd types/properties like user/experimenter/leader/contact out to omero.xsd or remove them outright, and would provide a more flexible, extensible way for users to express the provenance of their data.

Note: this may also be the appropriate place for info like "Image.format", including not just the reader used by Bio-Formats as currently, but also the software version, the JVM, etc. etc.

See also: #1636 (rights management)

Change History (7)

comment:1 Changed 12 years ago by jmoore

  • Description modified (diff)

comment:2 Changed 12 years ago by jmoore

  • Description modified (diff)

comment:3 Changed 12 years ago by jmoore

  • Cc cxallan added

comment:4 Changed 12 years ago by jmoore

  • Milestone changed from OMERO-Beta4.4 to OMERO-Beta4.4.1

Moving to 4.4.1

comment:5 Changed 12 years ago by jmoore

  • Cc rleigh added

This is certainly still an option but no investigation took place. New tickets should be opened for specific tasks if desired.

comment:6 Changed 11 years ago by ajpatterson

  • Milestone changed from OMERO-4.5 to Future

comment:7 Changed 8 years ago by jamoore

  • Milestone changed from Future to GatherReqs
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.67197 sec.)

We're Hiring!