Changes between Initial Version and Version 1 of Ticket #1396
- Timestamp:
- Oct 5, 2009, 6:17:31 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1396 – Description
initial v1 12 12 Naturally, a user could export item properties, e.g., scanner, and then annotate the scans with scanner name using an annotation type. This is, however, not a particularly pretty solution as: the information is redundant (inputted twice), and there is no association between the property and the annotation type, i.e., if scan properties are changes the annotation values remain unaltered. 13 13 14 Some thoughts: 14 15 - Could a special form of annotation types be connected to item properties so that annotation values are derived from the item property value? 15 16 - Alternatively, could item properties be used directly as experimental factors?
