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"

Task #3759 (new)

Opened 13 years ago

Last modified 13 years ago

Preservation Priority

Reported by: ajpatterson Owned by:
Priority: minor Milestone: Unscheduled
Component: Model Version: n.a.
Keywords: schema Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

Moved from ​http://www.ome-xml.org/ticket/97

It would be great to add an estimate (on a scale of 1-5 or something along those lines) for how essential it is to preserve a particular file or dataset. I am still trying to find some decent guidelines for this—I’m not sure any even exist right now for image data. Examples of criteria you might use to determine preservation priority would be: cost and difficulty of acquisition, whether a similar data set can be reconstructed or not, and historic value.

Changed by andrew

Could this be related to archiving?

Change History (1)

comment:1 Changed 13 years ago by ajpatterson

  • Keywords schema added
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.65758 sec.)

© 2000-2014 University of Dundee & Open Microscopy Environment. Creative Commons Attribution 3.0 Unported License
OME source code is available under the GNU General public license or through commercial license from Glencoe Software

We're Hiring!