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.
- Timestamp:
-
07/29/11 08:58:29 (13 years ago)
- Author:
-
jmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
- Property Cc jmoore added
-
Property
Priority
changed from
major
to
critical
- Property Keywords paris2011 added
-
|
v11
|
v13
|
|
| 7 | 7 | Would be nice to allow population of OMERO.tables with this data, to support some of the features of Batch Annotation #4271. |
| 8 | 8 | |
| 9 | | Questions: |
| | 9 | === Questions / Answers: === |
| | 10 | - When users import, do you want to give them a choice of templates they fill out? |
| | 11 | - ''If possible this would be great. We had thought of just using a very broard set of fields that would cover all the gaps from all the file types but, (if I understand correctly) if a user could select their template, say one for an AxioVision file import, and or another for a SPOT RT file import that would be much nicer.'' |
| | 12 | - Would there be anyway to restrict who has permissions to create a template, so that only adamins can? |
| | 13 | - How complex is the template? E.g. Simple list of attributes (like column headers in a table)? Or "fully featured" like OMERO.editor, with a "type" for each parameter (boolean, String, integer etc), options for some fields, default values, "required" vv optional parameters etc. |
| | 14 | - ''Fully featured would be great, as there are some fields that are required and others optional, some fields will need to have a set list of options (e.g. checkboxes, radio buttons), and others just open text. A webform like template. A simple list of attributes isn't really sophisticated enough as we would like to ensure the naming of the fields is consistent and all relevant metadata is captured correctly for the publishing and discoverability component. '' |
| | 15 | - If I'm importing 100 images with 10 fields each, when do I fill these out? E.g. after I hit "Import" (before importing starts), after import is finished (but how to enforce this) or before Import. E.g. Create an Excel table of images (identified by name) and fill out the values, then pick this file on import. |
| | 16 | - ''Again ideally.... A) If I select multiple images (or a folder? not sure if this is possible?) at once from my local directory then hit 'import' to go to get ready for download to OMERO, a pop-up box would come up and ask for extra metadata to apply to that SET of images (i.e. all images selected will get the same extra metadata added) B) If I select a single image from my local directory then hit 'import', a pop-up box would come up and ask for the extra metadata to apply to that file.'' |
| 10 | 17 | |
| 11 | | - When users import, do you want to give them a choice of templates they fill out? |
| 12 | | - How complex is the template? E.g. Simple list of attributes (like column headers in a table)? Or "fully featured" like OMERO.editor, with a "type" for each parameter (boolean, String, integer etc), options for some fields, default values, "required" vv optional parameters etc. |
| 13 | | - If I'm importing 100 images with 10 fields each, when do I fill these out? E.g. after I hit "Import" (before importing starts), after import is finished (but how to enforce this) or before Import. E.g. Create an Excel table of images (identified by name) and fill out the values, then pick this file on import. |
| | 18 | === Comments: === |
| | 19 | - ''It would also be good if the files would automatically upload to the appropriate folder/s based on the extra metadata added, such as Proejct name or Chief Investigator.'' |
| | 20 | - ''Can we ensure that users importing images HAVE to specify the missing metadata before any import is successful?'' |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.22917 sec.)
